Embedded Files
LINK TO ORIGINAL PDFThis citation of the original document made available for free in the public domain (link is provided in the sources at the end of the document) - has not been approved by the authors and has not been submitted for approval. The translation is carried out in the automated google translation system, translator with interference in text formatting in order to enable it to be heard in text reading applications
Nantional Institute of BUILDING SCIENCES
2013-03-12-COBieGuide-Public-v05
COBie Guide: Commentary on NBIMS-US COBie [draft]
COBie Guide: Commentary on NBIMS-US COBie [draft]
dr Bill East, PhD, PE, F.ASCE 1 , Mariangelica Carrasquillo-Mangual 2
SUMMARY: The Building Construction Information Exchange Format (COBie) is an international standard format for the exchange of information about the managed assets of a facility. COBie does not add a new contract requirement; it simply reformats existing paper-delivered products documents and proprietary formats to an open, international standard format. While COBie provides a format for the exchange of required resource information, it does not do so by providing details of what information to provide, when and by whom. This guide provides best practice guidelines for these requirements. This guide can be considered a "comment" that accompanies the COBie specification. To use this guide, adjustments reflecting regional practices, specialized project types, and customer requirements should be documented in Appendix A. Correct application of the COBie Guide can then be referenced directly in the relevant specifications. As of 2012, over twenty commercial software supports COBie. These products cover the entire facility life cycle from planning, design, construction, commissioning to operation, maintenance and space management. Software implementers will find this information in Appendix B to help map the required properties to a low level.
1 Research Civil Engineer, Engineer Research and Development Center, 2902 Newmark Dr, Champaign, IL 61822, bill.east@us.army.mil, 271-373-6710.
2 Research Civil Engineer, Engineer Research and Development Center
ACKNOWLEDGMENTS: The authors of this Guide would like to thank those who participated in the three-month opening review of this guide, which ended on October 1, 2012. There were 1195 views posted on this forum worldwide. The following people are especially grateful for their detailed review of the original design: Nicholas Nisbet (AEC3UK), Igor Starkov (EcoDomus), Richard Mitrenga (AutoDesk) and Marty Chabot (FMSystems). Danielle Love, formerly a Research and Development Center Engineer, is also appreciated for his original contribution to the first draft of this draft document.
"The COBie Guide is the result of years of efforts to develop and test the use of COBie in real-world projects. In order to reflect the experience gained, the" COBie Guide, Public Edition 1 "was published for comment on Jul 2-12 and reviewed for three (3) months. Based on these comments, a voted draft COBie Guide was developed. The "COBie Guide Public Release 2" is expected to be submitted as a "code comment" to NBIMS version 3. " National Institute of BUILDING SCIENCES: nbs.org
1. INTRODUCTION
1. INTRODUCTION
Building Information Modeling (BIM) technology has demonstrated its overall ability to reduce project cost by identifying physical conflicts between building elements prior to construction. Solving such problems during design eliminates costly detachment and rework that would otherwise have occurred during construction. The application of BIM to geometry collision detection was the starting point for understanding the potential application of the Information building. The buildingSMART 3 alliance has begun to block non-geometric information content in BIM by standardizing contracted information exchange, which will eventually replace the paper exchange of documents currently stipulated in contracts. The purpose of these standards is to provide the required information content once it is created and to securely share and update certain parts of this information with authorized team members during the course of the project. Rather than producing wasteful paper documents whose content is impractical to extract many times in the facility's lifecycle, standard information exchange streamlines the current process to eliminate waste and increase profitability. The first of these standards, Construction, Operation Building Information Exchange (COBie 4), provides information about a facility's assets. These resources are simply planned equipment, products, and exposures that appear in design drawings. Readers unfamiliar with COBie should start by viewing the following two online presentations: • Grade 1. Overview 5 • Grade 2. How to complete 6 It is assumed that readers of this document have viewed these two online presentations.
2. PURPOSE OF THIS COBie GUIDE
2. PURPOSE OF THIS COBie GUIDE
This guide is intended to define the requirements for COBie products for design and construction contracts. This document is not a software manual. The document consists of two parts. First, there are common requirements that must be met regardless of the customer. The second part is a set of customer-specific requirements that need to be additionally met with general requirements. Customer-specific requirements can be found in “Appendix A - Owner Requirements Requirements. ”There are over twenty commercial off-the-shelf products that support the production and / or consumption of building resource information through COBie. Instructions for using these systems for the production or consumption of COBie data should be obtained directly from the software company. The results of independent software testing conducted by the National Institute of Building Sciences are documented on the COBie Means and Methods 7 website. Given the differences in configuration and programming version, commercial software solutions producing or consuming COBie products should conduct their own test using one of the three common test models.
3. COBie PROCESS
3. COBie PROCESS
The process of creating COBie products follows the same processes as in modern design and construction. COBie simply transforms information in paper documents into information that can be reused in a project. The figure below summarizes the COBie process
Figure 1. COBie process: design - build - use
During early design, Architects develop the spaces and space groups needed to support the activities required under the owner's program. This information is provided via Schematic Drawings. COBie provides a subset of schematic design information related to spacing, zoning, and "room datasheets". Project diagram Stage Information COBie This is used to check if the designed object meets the owner's program guidelines. Because COBie is an extract from the items delivered within the schema, the information in the COBie data files must match the information about the spaces and architectural products and schedules found in the Project Submission schema. When a project comes to an end, engineers design systems that provide the required services, such as electricity, water, temperature, fire protection, security etc ... to enable the activities to be performed. This information is provided at the design stage of construction documents. In addition to updated architectural information, COBie provides a subset of construction Documents product and equipment asset information that will ultimately be owner managed. This resource information is included in design drawing equipment and product schedules. Since COBie is an excerpt from the Design Documents provided, the information in COBie should ideally match the drawings printed from that product. During construction, the general resource information found in the Construction Documents step is filled in to provide COBie structural members. Message COBie in advance of favorable Occupation allows the facility manager to begin managing his facility efficiently after seizure. A post-production COBie report was also provided to reflect all final changes and conditions after submission. During construction, this information is combined from other sources, such as validated application documents, warranty certificates, etc. As a result, construction information can be collected directly from electronic records. Other information, documenting the specifics of installing and testing the equipment, includes some detailed information such as the serial number and installation dates of each important building resource. The resulting dataset is not less than or less than the set of operation and maintenance manuals that can actually be used by operations, maintenance and asset management personnel. After providing information on a facility's assets, maintenance, and operations, the owner uploads this information directly to their COBie-compliant maintenance management system and starts running the facility immediately. COBie data updates resulting from a work order should be documented directly in the next-generation maintenance management systems. The restoration results simply update this subset of the existing COBie data with changes from the restoration project.
4. BUSINESS COBie
4. BUSINESS COBie
COBie delivery is not a new requirement. COBie, from the designer side, is simply a report of an existing design asset to be delivered. COBie, on the contractor's side, converts existing paper materials into data to support the facility. COBie requirement project participants can create delivery items in the same way as they produce current paper documents, or use this new format to eliminate wasted time and effort producing error-prone paper documents after the fact. In this view, COBie is a direct application of lean methodology to eliminate unproductive waste from administrative contracting procedures. Here is one example where you can transform your current process with the right set of technologies to eliminate wasted effort associated with producing paper operations and maintenance instructions. The current labor-intensive process of creating O&M manuals involves the physical "crawl task" to gather information from the equipment nameplate, then person-month sorting of existing documents into O&M binders. The contract may also include the capture of electronically transmitted information and installation information as they arise and reduce their costs. The National Institute of Building Sciences is developing a COBie calculator that will provide a life-cycle overview of the cost cycle of such waste and the savings that can be made. Once published in January 2013, the COBie calculator and related reports can be found in the Entire COBie Home Page of the Building Design Guide (COBie Home)
5. DUTIES OF THE TEAM
5. DUTIES OF THE TEAM
During the course of a project, different team members are primarily responsible for creating COBie Products. As many teams will use Building Information Modeling tools, especially during the design phase, to create the required contract drawings, the identification of COBie Responsibilities should be explicitly included in the team's BIM execution plan. One Tool That Can Help Teams Determine Manufacturing Responsibilities The items provided by COBie are the COBie Responsibility Matrix (COBie Responsibility Matrix). This matrix allows the team to color code the various parts of the COBie delivery to define precise requirements as to which person and company will be responsible for creating specific COBie data. While project teams will identify specific people in their companies, the following should be adhered to overall responsibility for creating COBie data.
1. Regardless of the form of the contract, the design company is responsible for the design company Rozwoju (project 35%) Deliverable.
2. Regardless of the form of the contract, the architectural firm is responsible for the Coordination of all data entered by the disciplines in the design of the construction document (100%) Deliverable.
3. Regardless of the form of the contract, the General Contractor will be responsible for the favorable occupancy and components after completion of construction.
4. For projects that use third party outsourcing, the outsourcing agent may assist the General Contractor to coordinate and validate the General Contractor's quality for favorable use and post-construction products.
6. COBie DELIVERED
6. COBie DELIVERED
The requirements for the COBie delivery schedule in typical facility acquisition projects are provided as follows in this section. Contractual participants should review the individual contract requirements for any changes to these general requirements, including, but not limited to: Appendix A to this document. One COBie file must be provided for each object in the project. If there are multiple objects, then an additional COBie file identifying the Site's assets must also be provided. The information in the COBie file should accurately reflect the related project information and as-built drawings at this stage of the project. All COBie files must be sent for customer approval. Sufficient progress payment for the entire deliverable package must be denied for non-compliant COBie products to cover the potential cost of manually creating accurate COBie products. The content of the COBie products delivered over time reflects the increasing maturity of the project or the completion of the construction project. See "Deliverable Assessment Criteria" for information on what content is required for each submission. In addition, see "Resource Requirements" for a minimum list of resources to include in the model and the minimum required properties of such resources. All products should comply with the management object transfer model view definition described in National BIM Standard - United States. Unless otherwise stated COBie items are provided in either IFC (Industry Foundation Class) (STEP Part 21) or COBie 2.4 Spreadsheet Format. The files listed in the COBie.Documents worksheet are the Portable Document Format (PDF), Tag Image File Format (TIFF), or Joint Photograph Experts Group (JPEG) files provided with the COBie file. Delivering developed projects (Design 35%) Regardless of the form of the contract, the architectural firm is responsible for the development of the project (Design 35%) Deliverable. This phase may also be referred to as the schematic design phase. The delivered design study must be provided in one file for each object in the design (and page if applicable) containing information about the design developed by people in the architectural discipline. The aim of the project development is to ensure the accuracy of the presentation of surface resources and architectural objects. Attributes of space assets should be completed to allow presentation of reports with room datasheets corresponding to the level of detail in the associated drawings. Architectural product types such as door and window schedules should be identified if such assets are included in the associated drawings. If the plumbing and lighting resources are in the related drawings, then those assets should also be identified in the information provided. The design document should also outline the expected systems required to provide heating, cooling, electricity, water, fire protection and other services. At this stage of design, the information provided about the system must be given only in the name and classification, without reference to the specific elements that make up these systems. All such information is given in detail during the next design stage. The content of the result should be assessed on the basis of compliance with the data format (IFC or spreadsheet) and content. The listed COBie worksheets (or equivalent IFC file data) in the figure below should be provided as indicated in the "Asset Requirements" and "Delivery Sections" Assessment Criteria ". The purpose of these requirements is to standardize product and equipment schedules in design drawings and reflect this information in these schedules for the associated COBie delivery. The content of the provided development project should reflect the space and planned products and equipment assets as depicted in the relevant deliverable drawings. The architect is responsible for correcting any deviation in content between the associated design development, drawings and information provided in this section
Table 1. Schematic Design COBie Provided: COBie Sheet - Content Required,
Contact. Provide one line for the designer BIM.
Object: One object per COBie file.
Floor: One row for each vertical level to cover the foundations, floors, roofs and terrain.
Space: One row per functional space, per room. Mult. possible places in the room.
Zone: One line for each COBie.Space and COBie.Zone.
Type: One row for each planned product type found on design drawings.
Component: One row for each scheduled product found on design drawings.
System: One row for each system to be defined at the next design stage.
Document: One line for each linked deliverable document with the appropriate sheet. Selected Row URL listing the target COBie.Type product.
Attribute: One line for each required COBie.Space attribute. One line for each required COBie.Type attribute. One line for each required COBie.Component attribute
Construction Documents Deliverable (100% design): Regardless of the form of the contract, the architectural firm is responsible for coordinating all contributions of the design disciplines to the design of the construction document (100%). If COBie data is extracted from multiple BIM files during the design phase of construction documents, each of the required BIM files must be provided as part of this COBie. Regardless of the native file format for BIM models, you must provide a single merged COBie file in the project (and location, if applicable) for each object. This set of COBie files will be the basis for the client's assessment of compliance. The party uploading the COBie file is responsible for verifying that the upload does not contain duplicate resources or geometry. Models with duplicate assets or geometry will be rejected by the customer. The content of the result should be assessed on the basis of compliance with the data format (IFC or spreadsheet) and content. The listed COBie worksheets (or equivalent IFC file data) in the figure below should be provided as indicated in the "Asset Requirements" and "Delivery Sections" Assessment Criteria ". The purpose of these requirements is to standardize the product and hardware is planned on the design drawings and is to reflect this standardization in the product and provided hardware information.
Table 2. Design Documents Provided to COBie: COBie Sheet - Content Required
Contact: Provide one line for the designer BIM.
Object: One object per COBie file.
Floor: One row for each vertical level to cover the foundations, floors, roofs and terrain.
Space: One row per functional space, per room. Mult. possible places in the room.
Zone: One line for each COBie.Space and COBie.Zone.
Type: One row for each planned product type found on design drawings.
Component: One row for each scheduled product found on design drawings.
System: One line for each COBie.Component identifying the associated COBie.System.
Document: One line for each related deliverable document. Related to the relevant worksheet. Selected Row URL listing the target COBie.Type product.
Attribute: One line for each required COBie.Space attribute. One line for each required COBie.Type attribute. One line for each required COBie.Component attribute.
There are two main differences between the products delivered in the Design Phase and the Construction Document Phase. First, the contents of the Provided Construction Document should reflect the full set of all spaces, planned products and hardware resources depicted on the corresponding drawings document. At the Design Documents stage, this list of products and equipment is expected to be complete. The scheduled property attributes of these products will be updated to reflect the attributes that reflect the design basis. Again, this is no different from simply picking up information from a construction document's phased drawing and providing that information in an open COBie format. The second difference in outcomes between design development and construction documentation stage is that the construction document stage model groups products and equipment into systems that deliver specific services throughout the building. As with design drawings in the Construction Documents stage, the architect's responsibility to coordinate design drawings across multiple disciplines extends to the architect's responsibility to ensure that the data provided from these design drawings are also coordinated.
Structure for the Benefit: The general contractor will be responsible for the welfare and development of Building Products. For projects using a third party outsourcing, the Contracting Agent can assist the General Contractor in coordinating and confirming the quality of the General Contractor's products with favorable use and as-built design. Delivered Products The following COBie sheets (or equivalent IFC file data) must be provided as indicated in the Deliverable evaluation criteria ”. The shipped structural component to the benefit people will be provided as a separate COBie file for each object in the project (and site, if applicable) that reflects the installation and commissioning of the object during favorable occupancy. This file updates the Model Construction Documents to reflect any additions, updates, or deletions to the underlying buildings and associated COBie Data. Complete set of information to run completed in favorable time Seizure should be provided with this result. Scheduled Attributes The properties of the installed products will be updated to reflect any differences between the installed hardware and the attributes that reflect the design basis. Information needed for operation and maintenance Occupied parts of the facility will also be included in this COBie delivery.
Table 3. COBie Beneficial Seizure Deliverable: COBie Worksheet - Content Required
Contact: Provide one line for the designer BIM.
Object: One object per COBie file.
Floor: One row for each vertical level to cover the foundations, floors, roofs and terrain.
Space: One space for functional use.
Zone: One line for each COBie.Space and COBie.Zone.
Type: One row for each planned product type found on design drawings.
Component: One row for each scheduled product found on design drawings.
System: One line for each COBie.Component identifying the associated COBie.System.
Spare: Lines for each replacement, part or lubricant for each type of COBie
Rescue: One row for each material, labor, training, or other resources required
Work: Rows for each COBie.Type identifying PM schedules. Rows for COBie types. Types that identify schedules for operations. Rows for COBie.Components that identify the schedules of operations.
Document: Poems for each COBie. Enter a list of each approved movement document. Rows (lines) for each COBie.Type containing a list of all requests to run. Rows (lines) for each COBie.Component containing a list of all requests to run. One row for each COBie unit picture Component Name tag
Attribute: One line for each required COBie.Space attribute. One line for each required COBie.Type attribute. One line for each piece of information on the COBie.Component nameplate
Structure Delivered Complete: The general contractor will be responsible for the welfare and development of Building Products. For projects using a third party outsourcing, the Contracting Agent can assist the General Contractor in coordinating and confirming the quality of the General Contractor's products with favorable use and as-built products. described in the "Deliverable assessment criteria" section. The delivered construction product will be delivered as a single COBie file for each object in the project (and page, if applicable) that reflects the as-built design documents provided as fiscal project completion. This file updates the Favored Jobs delivery model to reflect any additions, updates, or deletions to buildings and related COBie data. A complete set of commissioning information is provided with this output. The information needed to operate and maintain the facility will also be included in this COBie deliverable.
7. EVALUATION CRITERIA AVAILABLE
7. EVALUATION CRITERIA AVAILABLE
COBie models must conform to all format and business rules specified in NBIMS-US. The quality requirements must be met by combining the use of the tested COBie software and the use of the software according to the manufacturer's recommendations. Identified quality guidelines in this section outlines the problems that arose while testing the software due to incorrect software configuration or incorrect use of this software. The design team is responsible for understanding how to use the selected software to ensure compliance. In addition, there may be specific customer requirements set out in a more detailed contract requirements. Participants in specific contracts should review individual contract requirements and Appendix A of this document to clarify or amend these general requirements. COBie files that do not meet NBIMS-US requirements, including but not limited to those rules highlighted below, and owner-specific requirements will need to be manually corrected and resubmitted until approved by the customer.
One instrument per COBie: COBie represents a set of assets managed in a single object. If there are multiple facilities and joint site work related to a given project, COBie files will be prepared for each individual facility. Site work should be identified in a separate COBie page file, even for standalone buildings. It is the responsibility of the designer, consultant or contractor team member designated in the team to implement the COBie Implementation Plan to provide easy information from multiple sources integrated to produce one COBie information set for each plant, at each delivery stage, so that the information in the COBie file is consistent with information provided on design drawings. If the current agency provides specific toolkits to support integration activities, these tools will also be listed in Appendix A - Owner Requirements.
Unique resource naming: Without unique names, specific resources cannot be effectively maintained. All managed spaces, products, and equipment in schedules and design drawings should have a unique name. These names must contain resource information outside the context of the design schedule. The names in the design drawings must match those in the COBie shipment. During the design phase, the Architect will be responsible for resolving all duplication conflicts of names by his own staff and all consultant engineers. Software failure either by configuration, configuration, use, or basic inability to implement unique naming algorithms requires the Architect to manually update all drawn drawings, building models and COBie files. During construction, the General Contractor will be responsible for resolving any conflicts that duplicate the nomenclature of the components except those provided at the design stages. Software failure due to configuration, configuration, use or inability to implement unique naming algorithms require the General Contractor to manually update all changes made to drawings, building models and COBie files. The following are the minimum quality guidelines for the nomenclature of the COBie resources that the subject of the contract should use.
COBie.Space.Name Quality Guidelines:
• Each value in this column should be unique.
• Characters in this field are in the ASCII character range between [0-9], [az], [AZ] and the two symbols a dash ("-") and an underscore ("_"). Unless otherwise noted that ASCII space characters, CHR (20), in Name fields are forbidden due to software parsing inconsistency. Other characters, including non-printing ASCII control characters, are expressly prohibited.
• For each functional area in each physical room in. Provide one row of COBie.Space for each object. For large rooms with many functional areas, each functional area should be identified and marked with a dash followed by a letter starting with "A" and progressing through the fields
• COBie.Space.Name must exactly match the space names shown in the associated project and construction products.
• The COBie.Space.Tag field will be used to tag the building.
• COBie.Space.Name requirements for a unique name of functional areas should cover different work areas on large roof surfaces or discrete geographic regions in terrain models.
• COBie.Space.Description values not published in contract drawings should be general descriptions for spaces.
COBie.Type.Name Quality guidelines
• Each value in this column should be unique.
• Characters in this field are in the range of ASCII characters between [0-9], [az], [AZ], and two symbols a dash ("-") and an underscore ("_"). Unless otherwise noted that ASCII space characters, CHR (20), in Name fields are prohibited due to inconsistency in programming parsing. Other characters, including non-printing ASCII control characters, are expressly prohibited.
• Planned devices and products in the drawings should have a unique name.
• Unless otherwise specified by the customer, the name of each COBie. The product type and hardware starts with a product type tag that would be recognizable to the facility manager outside the context of the specific project. For example, the designation "DOOR-A" uniquely distinguishes this COBie. Type from the "LIGHT-A" luminaire.
• The designer will either use the template objects provided by the customer or explicitly coordinate the names of all product types, ahead of time with the owner, and document all decisions.
COBie.Component.Name Quality guidelines
• Each value in this column should be unique.
• Characters in this field are in the ASCII character range between [0-9], [az], [AZ] and the two symbols a dash ("-") and an underscore ("_"). Unless otherwise noted that ASCII space characters, CHR (20), in Name fields are forbidden due to software parsing inconsistency. Other characters, including non-printing ASCII control characters, are expressly prohibited.
• The individual instances of each type must also be unique. For large scheduled pieces of equipment such as air handling units, such unique names are commonly found in project schedules.
• Unless otherwise specified by the customer, for items whose descriptions relate only to the project schedule, resource types, such as luminaire or plumbing schedules, the following formula should create a unique component name. COBie.Type.Name & "-" and COBie.Space.Name & "-" and the number of items in the space. For example, if in space "100" there were two "Sink-A" sinks with unique names, each of these items according to the algorithm would be "Sink-A-100-01" and "Sink-A-100-02".
COBie.Type Product Specification: When a COBie is delivered, the specifics of COBie.Type information will typically increase from a hypothetical performance specification to identifying the basis of a specific manufacturer's design, to a product actually approved and installed by a Contractor. Given the differences between the various COBie implementation programs and their relation to the life cycle of this product, the Design Basis documentation requirements identified in this document must be met.
Component spatial constraint: All COBie.Component records must be identified in the COBie.Space where the asset is located or the COBie.Space from which the resource is served.
Component spatial layout: For each COBie.Component component, you must provide a COBie.Attribute attribute named "SpatialPlacement". This Attribute identifies the information needed by the facility manager, operator, or maintainer to access this component. Common SpatialPlacement values include "UnderFloor", "AboveCeiling", "InWall", "InSpace", "OnRoof", "OnSite".
Site spatial space: For each facility complex or campus with collaborative work, there will be a separate COBie page file uploaded on the site. A single COBie.Floor line will be created for this page file and marked as COBie.Floor.FloorType "Sites". The definable areas on this site will be identified in lines on the COBie.Space Sheet. Examples of typical COBie.Space lines in COBie.Floor = Sites are parking lots, utility boxes, loading docks, etc. The default list of site spaces to be included for a given customer is set out in Appendix A
Facility Geolocation: To ensure COBie data is coordinated with campus management and geographic information, the following COBie attributes must be provided in the systems. For each COBie record, based on (in the northern hemisphere) the "bottom left spatial" coordinate of each feature. • Longitude • Latitude • Height • Rotation
Categories: Large public clients manage all sorts of facilities on multiple campuses. To effectively manage these portfolios, COBie delivery items are required to receive building information in a consistent manner. In COBie this is achieved through the use of several different types of Classifications. Classifications are "category codes" of different types used in COBie. NBIMS- United States requires the following COBie sheets to be classified. • Contact • Object • Space • Type • System. NBIMS-US designates OmniClass (OMNIClass Structural Classification System) as the default classification method to be used if no other method is specified in the contract. The default list of mandatory COBie classifications to be considered for a given customer is listed in Appendix A. Please note that customer relying solely on OmniClass may not provide compatibility between time projects. The OmniClass classification tables, like all classification systems, change over time as updates are turned on. It is up to the customers to define and publish the precision of the classification scheme required for all projects.
Zones: Buildings contain groups of spaces that, when combined, provide specific opportunities for the owner. COBie.Zone worksheet identifies the spaces that make up a given zone. In general, zones should be identified according to the type and characteristics of the zone. Large object zone names should also be marked as attached to the floor and wing. The names of zones and sub-zones should: be approved by the owner. The default list of zones that will be used for a given customer is that specified in Appendix A. The COBie.Space area may only be listed once per zone type. However, it can be COBie.Space part of many types of zones. As an example, consider Space "100" in a building where "Circulation Zone" and "Fire Protection" zone information is requested by the owner. In this example, Space 100 could be part of a "Circulation Zone - Public" Circulation Zone and "Fire Protection Zone - First Floor West Wing" Fire Protection Zone. However, it is not possible for Space 100 to be part of both "Fire Zone Zone - First Floor West Wing" and "Fire Protection Zone - First Floor East Wing." Zones can be nested. Nesting must be by zone name. For example, there may be common spaces that serve both the "Fire Protection Zone - First Floor East Wing" and the "Fire Protection Zone - First Floor East Wing". Such zones can be identified in the zone "Fire protection zone - first floor". If the design team agrees, zone nesting can be achieved by using COBie. Attributes that identify the parent zone of the current zone.
Systems: Buildings contain groups of components that, when connected, provide specific required services. COBie.System worksheet identifies the components that make up a system. Basically, systems need to be identified by building, floor and wing. The names of the systems under each type of system must be approved by the owner. Subsystems, if required, are identified using an owner approved naming convention. A list of possible systems for a typical project for your current agency can be found in Appendix A - Owner Requirements. COBie.Component may be replaced only once per system type. The COBie.Component may or may not be part of many types of systems. As an example, consider a "Sensor - Temperature 101" component in a building where the "HVAC system" and "Sensor System" information are requested by the owner. In this example, the sensor can be part of both the "HVAC - Chilled Water" system and the "BAS - HVAC sensors" system. However, it is not possible for the sensor to be part of a "HVAC - Water Cooled" and "HVAC System - First Floor Heating Distribution System" system. Systems can be nested. Nesting must be done using the system name. For example, a fire system may have a set of devices supporting "Common Fire Protection" and equipment to support specific areas of a building, such as "Fire Protection - First Floor, West Wing" and "Fire Protection - First Floor, East Wing". The question may arise about the relationship between systems and zones. This is important because some systems and zones have overlapping boundaries. The link can be found directly in the COBie data specification from component or space direction. To find COBie.Components and COBie.Systems which support specific spaces, you can query for all components found in COBie.Spaces identified in a given COBie.Zone area. You can also do a reverse query to identify the COBie.Spaces supported by the given COBie.System. If the design team agrees, systems nesting can be achieved by using COBie.Attributes, which identify the ParentSystem of the current system.
Units of Measure: COBie models require one standard set of measurement units for linear, area, and volumetric measures. This unit of measure standard is applied to all units that otherwise have no units attached. Designers assign the owner the required units of measurement for their designs approval before design begins. All other disciplines will be required to use the same units of measure specified by the designer. The architectural model and all other models should be "project" oriented to the north. The difference between the project north and the magnetic north is determined by the architect. The designer should determine the project elevation for the po a single starting point. The latitude and longitude should be defined from a single point of origin. All other disciplines are required to reference Project North Rotation and the designer specified elevation origin. Units on attributes must be identified with each numeric value in the COBie.Attributes Worksheet. This is true regardless of the type of attribute shared. Given the differences in unit software implementations, it is very important that the design team evaluate their product with small test models to ensure that this requirement can be met. It is to be expected that the COBie contact points of a commercial product will need to be identified and we have been contacted to restrict manual post-design updates or post-construction COBie product updates. During the design process, the architect will be responsible for manually updating all COBie automatically provided by the design software. During construction, the Contractor or Commissioning Agent will be responsible for manually updating all COBies. The attributes will not be automatically provided by the software used to build the required products.
Use of commercial software: Many commercial products can automatically generate COBie data. When using them, it is extremely important products, the software vendor's configuration instructions are followed prior to use. Without the correct initial configuration, the designer, commissioning agent, or contractor may be prompted to manually retype the information required in the products provided by COBie. All products provided by COBie are accompanied by a report showing that the shared file meets the formatting requirements of the COBie specification. Different proofing tools have different possibilities. Some check both IFC and spreadsheet based files. Others only check files based on the spreadsheet. A list of available tools can be found on the COBie Means and Methods page. If there are specific proofing tool requirements for an owner, these can be found in Appendix A - Owner Requirements.
Merge Multiple Models: Given the variety of technologies, COBie data delivery approaches, and emerging COBie data joining know-how, those preparing COBie items shipped from multiple underlying source files should pay particular attention. The following discussion may help clear up the problems for those trying to aggregate COBie data from multiple sources. There are two general classes of problems that can occur. In the first case, the problems are rooted in design practice. In the second case, problems arise from the open incomplete adoption of the standards of software development companies. Consider the workflow during the design phase, when the architect creates a reflected ceiling plan file that includes lighting fixtures and a plumbing schedule. Later, during the Building Documents, the schedule of the lighting fixtures of the Electrical and Mechanical Engineer will be completed. The schedule of the engineer's plumbing installations will be completed. It is sometimes the case with design to practice so that such information does not match exactly. The general rule for interpreting an inconsistency figure is that the more detailed information is about the less detailed information. The practical impact of this principle is that construction bids will almost always be made against an electric lighting schedule and not a reflected ceiling plan by an Architect. The second type of problem that can affect the merging of COBie data from multiple sources is that software that imports the original Architect model may not preserve the unique space, type, or component name. In some cases, data from this additional software is merged back into one file, there may be multiple spaces and hardware, and related properties and geometry found. It is recommended that when preparing a COBie product from multiple models, "lot" checks should be performed on the model merging operation to determine if resources are duplicated across multiple models. If automated methods to support design quality control are not available through the design team's commercial product, the BIM designer manager will need to complete this review and / or link manually. If a question arises regarding the order of priority in a merger, the merger should take place under Standard Contract Interpretation Rules. The standard approach is that more precise information (provided by the appropriate design discipline) takes precedence over more general Architectural information. The team should develop a specific set of rules when joining multiple files. Alliance buildingSMART (Council of the National Institute of Building Sciences) has now published a document containing a sample set of merge rules at the construction document stage.
8. EQUIPMENT AND PRODUCT REQUIREMENTS
8. EQUIPMENT AND PRODUCT REQUIREMENTS
COBie provides information on assets under management. The spatial assets are identified in the COBie.Space Worksheet and have properties that correspond to architectural room datasheets as defined by the customer. For a description of the hardware and products described in this section, see COBie.Type and COBie.Component Worksheets. The attributes of such resources appear in the COBie.Attribute sheet. As of COBie Challenge events beginning in January 2013, all software producing or using COBie data is required to contain clear instructions to the end user regarding the application of real estate kits for a region, country or customer. An example of a regional property mix project in the United States is undergoing a Property Specifier (SP) information exchange project. In the future, customers are expected to specify the use of prepared template objects for mandatory properties that reflect their unique requirements. In the absence of customer-specified regional, national, or customer-specific property kits, the project team may develop equipment and product schedules in accordance with current business practices and submit these schedules for customer approval to be checked against the quality standards set out in this guide. When developing equipment and product schedules, designers and consultants: ensure that schedule headers are standardized to eliminate duplication, resolve synonyms between disciplines, and name objects consistently to provide information based on which an object can be effectively maintained, operated and managed. Units for all attributes should also be identified and coordinated by designers and consultants. Regardless of the source of the properties specified in customer contracts, COBie.Attributes for all COBie.Type and COBie.Component records should match the properties found in the equivalent project to draw equipment and product schedules. Section 8.1 identifies common COBie quality attributes that apply to all projects, regardless of region, country, or customer property mix. Subsections starting with section 8.2 identify the properties identified by resource type. They are listed in rough order of the pace required for maintenance and operational activities on these assets. Those donkeys needing the most attention will appear at the top of the list.
8.1 General requirements
Deliveries of all types of equipment and products found are governed by the following requirements in all COBie shipments
8.1.1 Responsibilities of the design team: In the absence of specific regional, national or customer specific property combinations, the design team should co-ordinate the initial identification of the required equipment and product properties. Documentation of this pre-coordination should be submitted for customer approval prior to design. This message should include a listing of planned equipment and product schedules, and the headers are expected to appear on all schedules for drawings. This handover must be approved by the customer. The pre-coordination message aims to eliminate any possible subsequent design rework team that may be needed to align the COBie results with the data quality standards set out in this guide. The customer may explicitly require the design team to conform to the properties stated in this Guide. These properties were selected from design schedules found in the standard designs of several United States federal government agencies. This information has been compiled, standardized to eliminate duplication and resolve synonyms, and ordered consistently in the tables provided in this section. The units for each attribute were also identified. Effort to solve such a problem The problems contained in this Guide are expected to save the project team significant effort until regional, national or customer-specific requirements are met. The customer's first COBie data quality check will be an overview of all planned equipment and products. In the event of a discrepancy, the customer will reject the COBie delivery and hold the maintenance until the COBie quality standards are met. A COBie delivery customer detention is based on the time required to manually document all scheduled assets.
8.1.2 Unique Component Name and Type Name: All device schedules that identify each item begin with the attributes listed below. The resource name "Component.name" and the resource type name "Component.Type" are provided in all project schedules should be unique for all asset classes. • Name • Type, Default sc hematizing for schedules that identify individual components and only those that only identify devices or product types that were previously given in this guide
8.1.3 Irrelevant Attributes: The attributes provided in the COBie deliverables are limited to those that provide information about the specifications or performance of the asset being managed, and not information regarding the internal software system configuration or output formats provided by the software systems implementation.
8.1.4 Type and component attributes: Common attributes for a given type of equipment or product must be associated with the COBie.Type Record. Attributes unique to a particular component can be associated with a COBie.Component Record.
8.1.5 Specification Reference: Design Documents provided and beyond any COBie.Type records should be identified with the specification section that references their requirements. This is done through the COBie.Type attribute named "SpecificationSection".
8.1.6 Electrical Properties: All equipment schedules that identify the individual electrical components must have the next three schedule headers containing the following resource information. This information must be included in the COBie as the asset type attributes. • Present • Voltage • frequency
8.1.7 Placement: All assets under management are identified by placing them on site. On Site Documents Design Stage This requirement will apply to all COBie.Component records using the COBie.Attribute "SpatialPlacement". At the stage of taking advantage of the favorable and as-built construction, this requirement will apply to both planned and marked resources. The values that can be used for the "SpatialPlacement" attribute include, but are not limited to, the following list items. • Above the ceiling • In the space • In the wall • On the roof • On site • Under the floor
8.1.8 Delivered Building Documents - Design Basics: These properties will be added to the COBie.Attribute sheet and associated with each COBie.Type Record in Construction Documents (100% Design) Deliverable. The "BasisOfDesign-Notes" field recreates the notes associated with each type of planned resource as found in design drawings. • Design basis - manufacturer. • Design model number basis. • Design notes basis
8.1.9 Occupancy and As-built Features - Common Properties When Installed: COBie Utility and As-built products update the following additional attributes for all designed assets based on the properties of the installed products. COBie sheet - COBie field. Type: Manufacturer, Kind: Model number, Kind: Warranty Warranty Warranty, Type: Warranty Duration Labor, Type: Warranty Duration Unit, Attribute (type): Approved deviations, Component: Serial number, Component: Installation date, Component: Number marker
8.1.10 Occupancy and post-assembly delivery - post-installation electrical circuit: Each scheduled / named asset that uses electricity, in addition to the other required properties, has the following two properties that identify the electrical circuit required to de-energize the equipment. These properties will be added to the COBie.Attribute worksheet for Benefient COBie Occupancy and Asset. • ElecticalPanelName • ElectricalPanelCircut
8.1.11 Workload and As-built Components - Part Systems After Installation: Each scheduled / named system resource should be identified in the COBie System worksheet to identify the grouping of various components into systems in a facility.
8.1.12 Placement and components after assembly - Assembled assemblies of components: Custom-built products consist of individual products that differ in preventive maintenance schedules and spare part requirements. To properly include those in COBie, they must contain COBie.Type and COBie.Component for both the kit and the individual pieces of equipment within the entire assembly. BOD and As-built - Required Properties of Type Consumables and As-built COBie items update the attributes of all scheduled resource types to match the properties of the actually selected product types.
8.1.13 Occupation and Delivery in Built-in State - Installed Resource Type Properties: Utility Products and As-built COBie items update the attributes of all designed resources to match the properties of the installed products.
8.2 HVAC system assets required
8.2 HVAC system assets required
8.2.1 Chiller: The following minimum set of information should be provided at the Construction Documents stage Plan the delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products.
Table 4 Design - Chiller Schedule Minimum Headers: Header - Typical Unit, Refer to Original Table
8.2.2 Boiler: The following minimum set of information should be provided at the Construction Documents stage Plan delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products.
Table 5 Design - boiler schedule minimum headers: Header - Typical unit, Name: Boiler type XX-Space # -01, Type: Boiler type XX, Specification: (according to customer's agreement), Location: (Site name), current: Amperes , Voltage: Volts, Frequency: Hz, Input power: kW, Output power: kW, Water flow: m 3 / h, Inlet water temperature: up to, Temp. Outlet water: to, Vent diameter: mm, Season tickets: -, Pressure drop: kPa, Energy source: -, Fuel type: -, Output media: -, SpatialPlacement: (from approved list of destination types), Project basis - Manufacturer: (If found on drawing schedules), Design Base - Model Number: (If found on Drawing Schedules), Design Base - Annotation: (If found on drawing schedules), Structural features will be updated to reflect installed equipment and other information described in the General Requirements section. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: • Name of the electrical panel • Circuit of the electrical panel
8.2.3 Air Handling Units: The following minimum set of information should be provided at the Design Documents Stage Plan a Delivery Schedule and reflected in the CD COBie Delivered and Subsequent Construction Products.
Table 6 Design - Minimum number of ventilation units schedule headers: Header - Typical unit, see original table
8.2.4 Fan coil units: The following minimum set of information should be provided at the Construction Documents stage Plan delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products.
Table 7 Design - minimum fan coil number schedule headers: Header - Typical unit, see original table
8.2.5 Filters: The following minimum set of information should be provided at the Construction Documents stage of Plan a Delivery Schedule and reflected in the CD COBie stage Delivered and subsequent construction products. The maximum airflow rate is included in this table as it was found in the footnote to each filter. The efficiency index specified in the table is too general and needs to be explained either NominalCountedEfficiency or NominalWeightedEfficiency. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 8 Design - Minimum filter schedule headers: see original table
8.2.6 Pumps: The following minimum set of information is to be provided at the Construction Documents, Plan Delivery Schedule step and reflected in the CD COBie Delivered and Downstream, Construction Products step. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 9 Design - Minimum pump schedule headers: Header - Typical unit
8.2.7 Fans: The following minimum set of information should be provided at the Design Documents stage of the Plan delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 10 Design - See the original table for the minimum fan schedule headers
8.2.8 Engines: The following minimum set of information should be provided at the Design Documents stage of the Plan Delivery Schedule and reflected in the CD COBie Delivered and Downstream Construction Products stage. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 11 Design - Minimum headings for the list of engines: Header - Typical unit, see original table
8.2.9 Compressors: The following minimum set of information should be provided at the Design Documents Stage for Delivery Schedule and reflected in the CD COBie Delivered and Subsequent Construction Products stage. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 12 Design - Minimum compressor schedule headers: Header - Typical unit, see original table
8.2.10 Fields with variable air volume: The minimum infos set below the information must be provided in the Construction Documents step. Plan a delivery schedule and reflected in the CD COBie Delivered and subsequent construction products.
Table 13 Design - Minimum VAV kit headers: Structural members will be updated to reflect installed hardware and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: • Name of the electrical panel • Circuit of the electrical panel.
8.2.11 Valves: Schedules for this type of equipment are not required for COBie delivered materials but will be required for COBie Favorable Use Conditions and As-built models. These schedules will consist of: the following parts. • One COBie.Type record for each item type; • One COBie.Component for each individual component, identifying the component space; • COBie.Component name must be created unambiguously using the following rule about "Valve -" and COBie.SpaceName & "-" and the number of items in the specified space; • Two COBie.Attribute records for each component: OperatingPositionNormal (open / closed), OperatingPositionEmergency (open / closed); • One COBie.Connection record for each component whose flow is controlled by this device.
8.2.12 Traps: Schedules for this type of equipment are not required for COBie delivered materials, but will be required for COBie Favorable Terms of Use and As-built models. These schedules will consist of: the following parts. • One COBie.Type record for each item type • One COBie.Component for each individual component, identifying the component space • The COBie.Component name must be created uniquely using the following rule about "Trap -" and COBie.SpaceName & "-" and number of items in specified space • The PM plans for this COBie.Type define the frequency of inspection / maintenance required for that type of item.
8.2.13 Strainer: Schedules for this type of equipment are not required for COBie delivered materials but will be required for COBie Favorable Use Conditions and As-built models. These schedules will consist of: the following parts. • One COBie.Type record for each item type • One COBie.Component for each individual component, identifying the component space • The COBie.Component name must be created uniquely using the following rule about "Filter -" and COBie.SpaceName and "-" and number of items in specified space • The PM plans for this COBie.Type define the frequency of inspection / maintenance required for that item type.
8.3 Required resources of the hydraulic system
8.3 Required resources of the hydraulic system
8.3.1 Water treatment units: Water treatment systems are a set of three basic element types that should be included in COBie supplies. The three types are • Pre-Treatment Equipment • Drinking Water Treatment Equipment • Pressure Vessels If the water treatment plant is internal to the facility, then there must be one type of 'water treatment' facility. The following minimum set of information should be provided at the Construction Documents stage Plan a delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products.
Table 14 Design - schedule headers for minimum water treatment units - see original table, Structures will be updated to reflect installed equipment and other information described in General Requirements
8.3.2 Valves: Schedules for this type of equipment are not required for COBie shipped materials but will be required for COBie Favorable Use Conditions and As-built models. These schedules will consist of: the following parts. • One COBie.Type record for each item type • One COBie.Component for each individual component, identifying the component space • The COBie.Component name must be created uniquely using the following rule about "Valve -" and COBie.SpaceName & "-" and number of items in the specified space • Two COBie.Attribute records for each component o OperatingPositionNormal (open / closed) o OperatingPositionEmergency (open / closed) • One COBie.Connection record for each component whose flow is controlled by this device.
8.3.3 Plumbing fixtures: Although there are many different types of plumbing fixtures, they usually use the same schedule type as each type of fixture has a similar function. The following minimum set of information should be provided in the Design Phase Document Delivery Schedule and reflected in CD Stage COBie Deliverable and Subsequent Hardware.
Table 15 Design - Minimum Hydraulic Schedule Headers - See Original Table, Structures will be updated to reflect installed equipment and other information described in General Requirements.
8.4 Fire system resources required
8.4 Fire system resources required
8.4.1 Pumps: The following minimum set of information should be provided at the Design Documents step of Plan a delivery schedule and reflected in the CD COBie phase Delivered and subsequent construction products. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 16 Design - Minimum headers for pump schedule - see original table. The structural elements will be updated to reflect the installed hardware and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes:
8.4.2 Valves: Schedules for this type of equipment are not required for COBie delivered materials but will be required for COBie Favorable Use Conditions and As-built models. These schedules will consist of: the following parts. • One COBie.Type record for each item type • One COBie.Component for each individual component, identifying the component space • The COBie.Component name must be created uniquely using the following rule about "Valve -" and COBie.SpaceName & "-" and number of items in the specified space • Two COBie.Attribute records for each component o OperatingPositionNormal (open / closed) o OperatingPositionEmergency (open / closed) • One COBie.Connection record for each component whose flow is controlled by this device.
8.4.3 Sprinkler heads: The design plans for this type of equipment on the design drawings only identify each type of component. The location of each component is usually identified by a drawing note. As a result, Design The products supplied for this type of device include the following COBie information: • One COBie.Type record for each item type • One COBie.Attribute record for each type o Head type • One COBie.Component for each individual component, identifying the component space . For beneficial activities and as-built products, project schedules should be updated as announced below. • One COBie.Type record for each element type • Two COBie.Attribute records for each type o Head type o Thread size • One COBie.Component for each individual component, identifying the component space • The COBie.Component name must be uniquely created using the following rules about "SprinklerHead -" and COBie.SpaceName & "-" and the number of items in the specified space
8.4.4 Fire Extinguishers: The following minimum set of information must be provided at the Design Documents Stage Plan Delivery Schedule and reflected on CD Stage COBie Deliverable.
Table 17 Design - For minimum fire extinguisher schedule items - see orgy table. The structural elements will be updated to reflect the installed hardware and other information described in General Requirements.
8.5 Required electrical installation resources
8.5 Required electrical installation resources
8.5.1 Lighting fixtures: The design plans for this type of equipment only identify each type of item in the design drawings. The location of each component is usually identified by a drawing note. The minimum set of information below should be stated in the construction documents of the schedule of the delivered stage design and reflected in the CD Stage COBie Deliverable and subsequent structural elements. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 18 Design - headings of the minimum luminaire type listings - see the orgial tables. For beneficial activities and as-built products, project schedules should be updated as announced below. • One COBie.Component for each individual component, identifying the component space • Two COBie.Attribute records for each element o ElecticalPanelName o ElectricalPanelCircut • The name COBie.Component must be created uniquely using the following rule o "Outlet -" and COBie.SpaceName & " - "and the number of items in a given space
8.5.2: The design plans for this type of equipment on the design drawings only identify each type of item. The location of each component is usually identified by a drawing note. As a result, Design Products supplied for this type of device include the following COBie information: • One COBie.Type record for each element type • Three COBie.Attribute records for each type o voltage o current o Frequency • One COBie.Component for each individual component, identifying the component space • Two COBie.Attribute records for each element: o Electrical panel name, electrical panel circuit. For beneficial activities and as-built products, project schedules should be updated as announced below. • One COBie.Type record for each item type • Three COBie.Attribute records for each type o Voltage o Current o Frequency • One COBie.Component for each individual component, identifying the component space • Two COBie.Attribute records for each item o ElecticalPanelName o ElectricalPanelCircut • The name COBie.Component must be created uniquely using the following rule about "Outlet -" and COBie.SpaceName & "-" and the number of items in the specified space
8.5.3 Switches: The design plans for this type of equipment on the design drawings only identify each type of item. The location of each component is usually identified by a drawing note. As a result, Design Products supplied for this type of device include the following COBie information: • One COBie.Type record for each element type • Three COBie.Attribute records for each type o voltage o current o Frequency • One COBie.Component for each individual component, identifying the component space • Two COBie.Attribute records for each item o Name of the electrical panel, electrical panel circuit • With favorable coursework and as-built products, the project schedules will be updated as noted below. • One COBie.Type record for each element type • Two COBie.Attribute records for each type o voltage o current o Frequency • One COBie.Component for each individual component, identifying the component space • Two COBie.Attribute records for each element o ElecticalPanelName o ElectricalPanelCircut • The name COBie.Component must be created uniquely using the following rule about "Switch -" and COBie.SpaceName & "-" and the number of items in the specified space • One COBie.Connection record for each device, socket or device controlled by the component .
8.5.4 Distribution Panel: The following minimum set of information should be provided at the Design Documents Stage for Delivery and reflected in the CD COBie Delivered and Downstream Construction Products stage. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 19 Design - Minimal Distribution Panel Type Listing Headings - See Original Tables. The structural elements will be updated to reflect the installed hardware and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel for the electrical panel circuit Please note that the complete specification of the electrical system can be developed using COBie.Connection and COBie.Assembly Worksheets. Unless otherwise specified by the customer, use worksheets are not required to meet the overall COBie Guide.
8.5.5 Switchgear: The following minimum information must be provided on etConstruction Documents Plan a delivery schedule and reflected in the CD COBie phase Delivered and subsequent construction products. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 20 Design - Minimum headers of switchgear type listings - see original tables. The structural elements will be updated to reflect the installed hardware and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.5.6 Generator: The following minimum set of information should be provided at the Construction Documents stage Plan delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 21 Design - minimum generator type list headings - see original tables. The structural elements will be updated to reflect the installed hardware and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.6 Control system assets required
8.6 Control system assets required
8.6.1 Sensors: The following minimum set of information should be provided in the Design Documents step of the Schedule Delivery and reflected in the CD COBie Delivered and Downstream Construction Products step. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 22 Design - Minimum Sensor Types Schedule headers - see original table, Structures will be updated to reflect installed hardware and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.6.2 Controllers: The following minimum set of information should be provided at the Design Documents stage for Delivery Schedule and reflected in the CD COBie Delivered and Downstream Construction Products stage. Note that the expected nomenclature of this component should reflect the type and component specific use on the system.
Table 23 Design - minimum controller type schedule headers - see original table, Structures will be updated to reflect installed hardware and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit. Controllers will also be identified with one more attribute to allow operators to specify the main component controlled by that device. • Controlled device.
8.7 Elevator system resources required
8.7 Elevator system resources required
8.7.1 Elevator: The following minimum set of information should be provided at the Design Documents stage of the Plan delivery schedule and reflected in the CD COBie Delivered and subsequent construction products stage. Note that the expected naming of this component should reflect the type and component specific use on the system.
Table 24 Design - Minimum Headers for Elevator Type Schedules - see original table, Structural members will be updated to reflect installed equipment and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.8 The required resources of the catering system
8.8 The required resources of the catering system
8.8.1 Sinks: The following minimum set of information should be provided at the Construction Documents stage Plan delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 25 Design - Minimum Sink Types List of items - see original table, Structures will be updated to reflect installed equipment and other information described in General Requirements.
8.8.2 Waste Disposal: The following minimum set of information should be provided at the Construction Documents stage. Plan a delivery schedule and reflected in the CD COBie stage. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 26 Design - Minimum Waste Disposal list headings - see original table, Structures will be updated to reflect installed equipment and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.8.3 Dishwasher: The following minimum set of information should be provided at the Construction Documents stage Plan the delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 27 Design - minimum dishwasher type schedule headers - see the original table, Structures will be updated to reflect the installed equipment and other information described in the General Requirements section. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.8.4 Fridge: The following minimum set of information should be provided at the Construction Documents stage. Plan delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 28 Design - minimum refrigerator type schedule headers - see original table, Structures will be updated to reflect installed equipment and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.8.5 Ice Maker: The following minimum set of information should be provided at the Construction Documents stage Plan a delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 29 Design - Minimum headers for refrigerator type kits - see original table, Designs will be updated to reflect installed hardware and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.8.6 Scope: The following minimum set of information should be provided at the Construction Documents stage of Plan Delivery Schedule and reflected in CD COBie Delivered and Downstream Construction Products stage. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 30 Design - Minimum Scope Type Schedule Headers - See Original Table, Structures will be updated to reflect the installed hardware and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.8.7 Fryer: The following minimum set of information to be provided at the Design Documents step of Plan a Delivery Schedule and reflected in the CD COBie Delivered and Subsequent Construction Products step.
Table 31 Design - minimum fryer type schedule headers - see original table, Note that the expected nomenclature of this component should reflect the component type and component specific use in this system The structural members will be updated to reflect ia installed equipment and other information described in the section General requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.8.8 Freezer: The following minimum set of information should be provided at the Construction Documents stage of Plan a Delivery Schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 32 Design - minimum freezer type schedule headers - see original table, Structures will be updated to reflect the installed equipment and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.9 Architectural Resources Required
8.9 Architectural Resources Required
8.9.1 Doors: The following minimum set of information should be provided at the Construction Documents stage of Plan a Delivery Schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that for an interior door a comma separated list of two space names is required. The first location listed (or if only one seat is provided) is where the door opens.
Table 33 Design - Minimum Door Type Schedule Headings - see the original table, Structural members will be updated to reflect the installed hardware and other information described in General Requirements
8.9.2 Windows: The following minimum set of information should be provided at the Design Documents Stage for Delivery and reflected in the CD COBie Delivered and Subsequent Construction Products stage. Note that for the inner windows, a comma separated list of two space names is required.
Table 34 Design - Minimum Window Type Schedule Headings - See the original table, Structural members will be updated to reflect the installed hardware and other information described in General Requirements.
8.9.3 Finishes: The following minimum set of information should be provided at the Design Documents Stage for Delivery and reflected in the CD COBie Delivered and Downstream Construction Products stage.
Table 35 Design - Minimum Finish Schedule Headers - see the original table, Structural members will be updated to reflect the installed equipment and other information described in the General Requirements section.
8.10 Equipment assets
8.10 Equipment assets
While there are many different types of equipment, they usually use the same type of schedule. The following minimum set of information should be included in the construction documents the schedule for the delivery of the set and reflected in the CD Stage COBie Delivered and subsequent construction products.
Table 36 Design - minimum equipment inventory headings - see the original table, Structures will be updated to reflect installed equipment and other information described in General Requirements.
8.11 Site assets
8.11 Site assets
8.11.1 Local water distribution system
8.11.1.1 Water Pumps: The following minimum set of information should be provided at the Construction Documents stage Plan delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 37 Design - Minimum pump schedule headers - see the original table, Structures will be updated to reflect installed equipment and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.11.1.2 Water valves: Schedules for this type of equipment are not required for COBie delivered materials but will be required for COBie Favorable Use Conditions and As-built models. These schedules will consist of: the following parts. • One COBie.Type record for each item type • One OBie.Component for each individual component, identifying the component space • The COBie.Component name must be created uniquely using the following rule about "Valve -" and COBie.SpaceName & "-" and number of items in the specified space • Two COBie.Attribute records for each component o OperatingPositionNormal (open / closed) o OperatingPositionEmergency (open / closed) • One COBie.Connection record for each component whose flow is controlled by this device.
8.11.1.3 Water Tanks on Site: The following minimum set of information should be provided at the Design Documents Stage Plan Delivery Schedule and reflected in the CD COBie Delivered and Subsequent Construction Products Stage. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 38 Design - schedule headers for minimum tanks - see the aoriginal table, Structures will be updated to reflect the installed equipment and other information described in the General Requirements section.
8.11.2 On-site fire suppression system
8.11.2.1 Fire hydrants: The following minimum set of information should be provided at the Construction Documents stage Plan a delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 39 Design - Minimum headings for a hydrant listing - see the aoriginal table, Structures will be updated to reflect the installed equipment and other information described in the General Requirements section.
8.11.2.2 Fire valves - see original table, Schedules for this type of equipment are not required for COBie delivered materials but will be required for COBie Favorable Use Conditions and As-built Models. These schedules will consist of: the following parts. • One COBie.Type record for each item type • One COBie.Component for each individual component, identifying the component space • The COBie.Component name must be created uniquely using the following rule about "Valve -" and COBie.SpaceName & "-" and number of items in the specified space • Two COBie.Attribute records for each component o OperatingPositionNormal (open / closed) o OperatingPositionEmergency (open / closed) • One COBie.Connection record for each component whose flow is controlled by this device.
.11.2.3 Fire Pumps: The following minimum set of information should be provided at the Construction Documents stage Plan a delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 40 Design - Minimum pump schedule headers - see the original table, Structures will be updated to reflect the installed equipment and other information described in the General Requirements section. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.11.3 Water supply wells
8.11.3.1 Water Pumps: The following minimum set of information should be provided at the Construction Documents stage Plan delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected naming of this component should reflect the component type and specific usage in this system.
Table 41 Design - Minimum pump schedule headers - see the original table, Structures will be updated to reflect installed equipment and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.11.3.2 Water valves: Schedules for this type of equipment are not required for COBie delivered materials but will be required for COBie Favorable Use Conditions and As-built models. These schedules will consist of: the following parts. • One COBie.Type record for each item type • One OBie.Component for each individual component, identifying the component space • The COBie.Component name must be created uniquely using the following rule about "Valve -" and COBie.SpaceName & "-" and number of items in the specified space • Two COBie.Attribute records for each component o OperatingPositionNormal (open / closed) o OperatingPositionEmergency (open / closed) • One COBie.Connection record for each component whose flow is controlled by this device.
8.11.4 Site Sanitary Sewer
8.11.4.1 Sewer manholes: The following minimum set of information should be provided at the Construction Documents stage Plan a Delivery Schedule and reflected in the CD COBie Delivery and subsequent construction products stage. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 42 Design - Minimum Manhole Listing Positions - see the original table, Structural members will be updated to reflect the installed equipment and other information described in the General Requirements section.
8.11.4.2 Wastewater pumps: The following minimum set of information should be provided at the Construction Documents stage Plan a delivery schedule and reflected in the CD COBie stage Delivered and subsequent construction products. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 43 Design - Minimum pump schedule headers - see the original table, Structures will be updated to reflect installed equipment and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, electrical panel circuit.
8.11.4.3 Drain Valves: Schedules for this type of equipment are not required for COBie delivered materials but will be required for COBie Favorable Terms of Use and As-built models. These schedules will consist of: the following parts. • One COBie.Type record for each item type • One OBie.Component for each individual component, identifying the component space • The COBie.Component name must be created uniquely using the following rule about "Valve -" and COBie.SpaceName & "-" and number of items in the specified space • Two COBie.Attribute records for each component o OperatingPositionNormal (open / closed) o OperatingPositionEmergency (open / closed) • One COBie.Connection record for each component whose flow is controlled by this device.
8.11.4.4 Drainage Tanks: The following minimum set of information should be provided at the Construction Documents Stage Plan a Delivery Schedule and reflected in the CD COBie Construction Products Delivered and Downstream Stage. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 44 Design - minimum tank schedule headers - see the original table, Structures will be updated to reflect the installed equipment and other information described in the General Requirements section.
8.11.5 Fuel distribution
8.11.5.1 Fuel Distribution Pumps: The following minimum set of information should be provided in the Design Documents Phase Deliver Delivery Schedule and reflected in CD COBie Delivered and Downstream Construction Products. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 45 Design - Minimum Fuel Pump Schedule Headers - See the original table, Structures will be updated to reflect the installed hardware and other information described in General Requirements. In addition, favorable terms of use and as-built Products delivered must contain the following additional attributes: o Name of the electrical panel, circuit at the electrical panel.
8.11.5.2 Fuel Spool Valves: Schedules for this type of equipment are not required for COBie delivered materials but will be required for COBie Favorable Use Conditions and As-built Models. These schedules will consist of: the following parts. • One COBie.Type record for each item type • One OBie.Component for each individual component, identifying the component space • The COBie.Component name must be created uniquely using the following rule about "Valve -" and COBie.SpaceName & "-" and number of items in the specified space • Two COBie.Attribute records for each component o OperatingPositionNormal (open / closed) o OperatingPositionEmergency (open / closed) • One COBie.Connection record for each component whose flow is controlled by this device.
8.11.5.3 Fuel Distribution Tanks: The following minimum set of information should be provided at the Design Documents Phase for Delivery and reflected in the CD COBie Delivered and Downstream Construction Products step. Note that the expected naming of this component should reflect the type and component specific use on this system.
Table 46 Design - minimum fuel tank schedule headers - see the original table, Structures will be updated to reflect installed equipment and other information as described in General
8.11.5.4 Fuel distribution switches: The design plans for this type of equipment on the design drawings only identify each type of item. The location of each component is usually identified by a drawing note. As a result, the Design Products delivered to this type of device include the following COBie information: • One COBie.Type record for each element type • Three COBie.Attribute records for each type o voltage o current o Frequency • One COBie.Component for each individual component, identifying component space • Two COBie. Attribute per Element o PanelBoard o Perimeter For profitable activities and as-built products, project schedules should be updated as announced below. • One COBie.Type record for each element type • Three COBie.Attribute records for each type o voltage o current o Frequency • One COBie.Component for each individual component, identifying the component space • Two COBie.Attribute for each element o PanelBoard o Circuit • COBie.Component name must be created uniquely using the following rule about "Switch -" and COBie.SpaceName & "-" and the number of items in the specified space • One COBie.Connection record for each device, socket or device controlled by the component.
9. PARTS AND CONSUMABLES
9. PARTS AND CONSUMABLES
Identify the following types of parts: 1. General Consumables 2. General Right of Custody 3. General Store Equipment 4. Equipment 5. Tools 6. Equipment Specific Materials
9.1 Consumables for shared facilities:
9.1 Consumables for shared facilities:
The following minimum set of information should be provided in the favorable use information. COBie Design Deliverable and reflected in the building structure delivered.
Table 47 Minimum attributes for consumables for common objects and COBie mapping - see the original table,
9.2 Device-specific consumables
9.2 Device-specific consumables
The following minimum set of information should be provided in the favorable use information. COBie Design Deliverable and reflected in the building structure delivered.
Table 48 Minimum consumables and COBie mapping attributes - see the original table,
APPENDIX A - OWNER REQUIREMENTS
APPENDIX A - OWNER REQUIREMENTS
NOTE: Before this document is used by the specified owner. This section should be updated to reflect the individual procedures and technologies used by this owner to facilitate the production and delivery of COBie products.
This appendix lists the requirements for your specific agency in addition to or clarification of the general COBie product requirements identified in the previous sections.
1 Automated tools:
1 Automated tools:
Using this guide, the Agency is advised to identify the necessary automated tools to be used during the different phases of the project.
Design: The agency will need tools to capture design information required in the COBie. There are several design tools available for creating a design COBie file. More information related to such tools can be found on the COBie Means and Method website (http://www.buildingsmartalliance.org/index.php/projects/cobie).
Construction: The agency will need tools to capture the information needed in the COB during construction. Tools can be used to capture asset serial numbers or to electronically create and submit tickets. There are several tools to achieve this goal. More information can be found in the COBie Means and Method page (http://www.buildingsmartalliance.org/index.php/projects/cobie).
Commissioning: The Agency will need tools to capture and update information during the commissioning phase. There are several tools available to assist with this process. For more information on such tools, see the COBie Means and Method page (http://www.buildingsmartalliance.org/index.php/projects/cobie).
2 Compulsory classification
2 Compulsory classification
Instead of the customer providing a specific classification scheme, the project team will submit it to the owner for approval, which classification scheme is used. Identification COBie.Sheet.Classification Column data is a single text string with a classification number, and a separator (usually a colon) and classification name, such as "11-12 11 34 00: New Object". The best classification should be used. If there is no specific subcategory used, the higher one should choose a level classification. You can add spaces to the classification records for readability to ensure readability.
COBie.Contact Classification: Required classification for COBie.Contact records identifies the roles of the organization. In this section, insert an agency-specific table for the classification of contacts. If no specific agency table is available for this classification, by default, table 34 OmniClass - Organizational Roles should be used.
COBie. Object Classification: The required classification to be applied to COBie.Facility records identifies the function of the object. In this section, insert an agency-specific table for the classification of the facility. If no specific agency table is available for this classification, Table 11 OmniClass - Construction Entities by Function should be used as default.
COBie. Space Classification: Classification required for COBie records. Space identifies the function of space. In this section, insert an agency-specific table for the classification of spaces. If there is no specific agency table available for this classification, by default the table 13-Spaces by OmniClass should be used.
COBie classification. Zone: It is recommended to include the following zones in COBie models, if such zones are appropriate for the specific object being modeled. They are provided in alphabetical order. • Circulation zone • Fire alarm zone • Historical protection zone • Lighting zone • Occupied zone • Ventilation zone
COBie classification. Type: The classification required for COBie.Type records is the resource type. Agency in this section a special table should be inserted for type classification. If no specific agency table is available, the OmniClass Table 23-Products should be used by default for this classification.
COBie classification. System: Classification required for COBie records. System identifies the system type. Agency in this section a special table should be inserted for type classification. If no specific agency table is available, the 21-OmniClass table should be used by default for this classification.
APPENDIX B - EQUIPMENT MAPPING / ASSET SCHEDULE REQUIREMENTS
APPENDIX B - EQUIPMENT MAPPING / ASSET SCHEDULE REQUIREMENTS
1 HVAC system assets required
1 HVAC system assets required
1.1 Chiller: The following minimum set of information should be provided at the design stage of Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie template Chiller_AIRCOOLED _USType Product
Table 49 Minimum chiller schedule headers mapping - see original table
1.2 Boiler: The following minimum set of information should be provided at the design stage of the Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Boiler_Steam_US template
Table 50 Mapping of minimum boiler schedule headers - see original table
1.3 Air Handling Units: The following minimum set of information should be provided at the design stage of Building Documents Delivery schedule and reflected in CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie template UnitaryEquipment_AIRHANDLER _USTypeProduct
Table 51 Minimum number of HVU schedule headers mapping - see original table
1.4 Fan coil units: The following minimum set of information should be provided at the design stage of Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Coil_NOTDEFINED_US 20 template.
Table 52 Minimum fan coil number schedule headers mapping - see the original table
1.5 Filters: The following minimum set of information should be provided at the design stage of Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie Format and the current SPie Filter_AIRPARTICLEFILTER _US 21 template. The maximum airflow was included in this table as it was found in the note associated with each filter. The performance ratings specified in the table are too general and should be explained as Nominal Counting Efficiency or Nominal Weighted Efficiency.
Table 53 Minimum Filter Schedule Header Mapping - See Original Table
1.6 Pumps: The following minimum set of information should be provided at the design stage of the Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current template SPie Pump_CIRCULATOR_US 22.
Table 54 Minimum Pump Schedule Header Mapping - See Original Table
1.7 Fans: The following minimum set of information must be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie template Fan_CENTRIFUGALAIRFOIL _US 23
Table 55 Minimum fan schedule headers mapping - see original table
1.8 Engines: The following minimum set of information should be provided at the design stage of the Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current ElectricMotor_DC_US 24 SPie template.
Table 56 Minimum Engine Schedule Header Mapping - See Original Table
1.9 Compressors: The following minimum set of information should be provided at the design stage of the Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Compressor_RECIPROCATING_US 25 template.
Table 57 Minimum Compressor Schedule Header Mapping - See Original Table
1.10 Variable air volumes: The following minimum set of information should be provided at the design stage of Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie Format and the current SPie AirTerminalBox _VARIABLEFLOWPRESSUREDEPENDANT_US template 26
Table 58 VAV minimum set headers mapping - see original table
2 Required resources of the hydraulic system
2 Required resources of the hydraulic system
2.1 Water Treatment Units: The following minimum set of information should be provided at the design stage of Building Documents Delivery Schedule and reflected in CD Stage COBie Deliverable.
Table 59 Mapping schedule headings for minimum water treatment teams - see the original table
2.1 Hydraulic Equipment: The following minimum set of information must be provided at the design stage of the Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. COBie data mapping is based on the COBie format and the current SPie template SanitaryTerminal _WASHHANDBASIN_PlumbingFixtures_US, SanitaryTerminal _TOILETPAN_PrumbingFixtures_US, SanitaryTerminal_URINAL_PrumbingFixtures_US
Table 60 Mapping of the minimum plumbing equipment schedule headers - see the original table.
3 Fire system resources required
3 Fire system resources required
3.1 Pumps: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current template SPie Pump_CIRCULATOR_US
Table 61 Minimum Pump Schedule Header Mapping - See Original Table
3.2 Fire extinguishers: The design plans for this type of equipment on the design drawings only identify each type of item. The location of each item is usually identified by a drawing note. Consequently, the design elements for this device type consist of the following COBie information: • One COBie.Type record for each item type • Two COBie.Attribute records for each type o Capacity (kg) o Rating • One COBie.Component for each individual component , identifying the component space. Schedules for this type of equipment are not required for COBie deliverables but will require COBie Favorable occupancy and as-built models. These schedules will consist of the following parts.
Table 62 Minimum Fire Extinguisher Schedule Headings Mapping - See Original Table
4 Required electrical installation resources
4 Required electrical installation resources
4.1 Luminaires: The following minimum set of information must be provided at the design stage of the construction document delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie Format and the current SPie LightFixture _DIRECTIONSOURCE_LightFixture_US template
Table 63 Mapping list headings for the minimum type of luminaire - see the original table
4.2 Distribution panel: The following minimum set of information should be provided at the design stage of Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie Format and the current ElectricDistributionBoard_DISTRIBUTIONBOARD_DistributionPanel_US template.
Table 64 Mapping of minimum distribution panel type report headers - see the original table
4.3 Switchgear: The following minimum set of information should be provided at the design stage of Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable.
Table 65 Mapping the minimum headings of switchgear type listings - see the original table
4.4 Generator: The following minimum set of information should be provided at the design stage of Building Documents delivery schedule and reflected in CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie ElectricGenerator_STANDALONE_US template.
Table 66 Minimum generator type report headers mapping - see original table
5 Control system assets required
5 Control system assets required
5.1 Sensors: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Sensor_MOVEMENTSENSOR_US and Sensor_LIGHTSENSOR_US templates.
Table 67 Mapping the minimum headers of sensor types - see the original table
5.2 Controllers: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie Format and the current SPie Controller_PROGRAMMABLE_US template.
Table 68 Minimum controller type list headers mapping - see original table
6 Elevator system resources required
6 Elevator system resources required
6.1 Elevator: The following minimum set of information should be provided at the design stage of Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie TransportElement_ELEVATOR_US template.
Table 69 Mapping the headings of the minimum elevator type - see the original table
7 Catering system assets required
7 Catering system assets required
7.1 Sinks: The following minimum set of information should be provided at the design stage of Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie SanitaryTerminal_SINK_PlumbingFixtures_US template.
Table 70 Mapping the headings of the listings of the minimum types of sinks - see the original table
7.2 Waste disposal: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie template ElectricAppliance_USERDEFINED_FoodServiceEquipment_US.
Table 71 Waste minimizing type list headings mapping - see original table
7.3 Dishwasher: The following minimum set of information must be provided at the design stage of Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie ElectricAppliance_DISHWASHER_US template.
Table 72 Mapping the headings of the minimum dishwasher type listings - see the table of the original
7.4 Refrigerator: The following minimum set of information should be provided at the design stage of the Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie ElectricAppliance_REFRIGERATOR_US template.
Table 73 Minimum refrigerator type schedule headers mapping - see original table
7.5 Ice Cube Maker: The following minimum set of information should be provided at the design stage of the Building Documents Delivery Schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie template ElectricAppliance_USERDEFINED_FoodServiceEquipment_US.
Table 74 Mapping of list headings with minimum refrigerator types - see original table
7.6 Scope: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie ElectricAppliance_ELECTRICCOOKER_US template.
Table 75 Minimum range type list header mapping - see original table
7.7 Fryer: The following minimum set of information should be provided at the design stage of the Building Documents Delivery Schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie ElectricAppliance_ELECTRICCOOKER_US template.
Table 76 Minimum Fryer Type Schedule Headings Mapping - See Original Table
7.8 Freezer: The following minimum set of information should be provided at the design stage of Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie ElectricAppliance_FREEZER_US template.
Table 77 Minimum freezer type list headings mapping - see original table.
8 Architectural Resources Required
8 Architectural Resources Required
8.1 Doors: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie template Window Door_DOOR_SecurityDoorsandFrames_US.
Table 78 Mapping the list headings of the minimum door types - see the original table
8.2 Windows: The following minimum set of information should be provided at the design stage of Building Documents delivery schedule and reflected in CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Window_WINDOW_SecurityWindows_US template.
Table 79 Minimum window type list headings mapping - see original table
8.3 Finishes: The following minimum set of information should be provided at the design stage of Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable.
Table 80 Minimum Final Schedule Header Mapping - See Original Table
9 Equipment assets
9 Equipment assets
While there are many different types of equipment, they usually use the same type of schedule. The following minimum set of information must be provided at the Design Documents stage of Plan Delivery Schedule and reflected on CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Furniture_SHELF_US 48 and Furniture_TABLE_US templates.
Table 81 Mapping the headings of the minimum equipment inventory - see the original table
10 Site resources
10 Site resources
10.1 Water distribution system at the installation site
10.1.1 Pumps: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current template SPie Pump_CIRCULATOR_US 50.
Table 82 Minimum Pump Schedule Header Mapping - See Original Table
10.1.2 Tanks: The following minimum set of information should be provided at the design stage of the Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Tank_STORAGE_US template.
Table 83 Mapping of minimum tank list headings - see table of the original
10.2 Site fire suppression system
10.2.1 Hydrants: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie FireSuppressionTerminal_FIREHYDRANT_US template.
Table 84.Mapping the minimum headings of the hydrant list - see the original table
10.3 Water supply wells
10.3.1 Pumps: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Pump_CIRCULATOR_US template.
Table 85 Minimum Pump Schedule Header Mapping - See Original Table
10.4 Site Sanitary Sewer
10.4.1 Manholes: The following minimum set of information should be provided at the design stage of Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie DistributionChamberElement_MANHOLE_US template.
Table 86 Minimum Hatch Schedule Header Mapping - See Original Table
10.4.2 Pumps: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Pump_CIRCULATOR_US template.
Table 87 Minimum Pump Schedule Header Mapping - See Original Table
10.4.3 Tanks: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Tank_STORAGE_US template.
Table 88 Minimum Tank Schedule Header Mapping - See Original Table
10.5 Fuel distribution
10.5.1 Fuel pumps: The following minimum set of information should be provided at the design stage of the Building Documents delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Pump_SUBMERSIBLEPUMP_US template.
Table 89 Minimum Fuel Pump Schedule Header Mapping - See Original Table
10.5.2 Fuel tanks: The following minimum set of information should be provided at the design stage of the Building Documents Delivery schedule and reflected in the CD Stage COBie Deliverable. The COBie data mapping is based on the COBie format and the current SPie Tank_STORAGE_US template.
Table 90 Minimum Fuel Tank Schedule Header Mapping - See Original Table.
SOURCE:
SOURCE:
National Institute of BUILDING SCIENCES You can download March 2013, Public Release 5, The COBie Guide (publicly available in English: https://www.nibs.org/page/bsa_cobieguide )
Seriws plBIM has made, partially automated, citation of this document from the original English version into Polish by members of BIM4WORLD Group and BIM4POLAND Group. The link to the original can be found at the bottom of the document in the sources.
Page updated
Google Sites
Report abuse