Page Operations
Browse Space
(COBIE-ER-02) Exchange Project Handover - Floor Layout
NBIMS Development Stage
| Stage | Name | Status |
|---|---|---|
| 0 | Draft, not yet approved as NBIMS project | |
| 1 | Part of a 'pilot' project | |
| 3 | Part of a project out for 'consensus' review |  |
| 4 | Part of an operational standard | |
| 5 | Superseded by: | |
| 6 | Retired |
Note: For information on the specific stages of NBIMS project development, please visit www.nbims.org.
Project Stage
| Stage | Name | Valid |
|---|---|---|
| 0 | Portfolio requirements | |
| 1 | Conception of need | |
| 2 | Outline feasibility | |
| 3 | Substantive feasibility | |
| 4 | Outline conceptual design | |
| 5 | Full conceptual design | |
| 6 | Coordinated design and procurement | |
| 7 | Production information | |
| 8 | Construction | |
| 9 | Operation and maintenance | |
| 10 | Disposal |
Note: While the information exchange described in the COBIE project occurs following construction during building handover, as noted in the table above, the data contained in this particular exchange requirements is generally applicable throughout the facility life-cycle.
Overview
COBIE contains information information describing the operations, maintenance, and assets in capital facilities. The authoritative sources for this information include designers, builders, installers, and manufacturers. On the design side of the exchange, BIM-based design tools may be used to capture COBIE data. From construction, information about approved submittals are included in COBIE exchanges. Builders identify products to be installed. Manufacturers provide operating and maintenance information. Installers provide serial and tag numbers. Quality Control/Assurance staff provide test and certification reports. All these parties can capture building handover data through the COBIE standard, tying their diverse set of software together for the purpose of providing a consistent data set of operations, maintenance, and asset management to building staff.
This exchange requirement defines floors and spaces at the level needed for construction-operation information handover. An example scenario for this stage is shown in the table below:
| Task | Scenario |
|---|---|
| Floor Name | Provide the name of each conceptual/physical vertical level of each of the facilities identified in the project wrapper. |
| Floor Volume (Coordinates) | Identify the floor height, elevation, and bounding box. Coordinates are provided using an internal frame of reference only. |
| Floor Area (Asset) | Provide one or more values required to manage the floor asset. These values are defined by ANSI/ASTM or other authoritative source that is explicitly identified in the exchange |
| Floor Nesting | Identify the conceptual or physical "floors" within the facility that contain other floors. An example of this type of nesting would occur in a mixed-use vertical facility or the identification of multiple "wings" within horizontal structures. |
The information provided through this information exchange should be a subset of information that already exists in the design building information model, as appended/changed during construction. Information related to the facility that may be exchanged include:
- All floors must link to a single facility.
- Floors may be organized into "super floors."
The following information auditing is also required for all COBIE file exchanges that occur in a batch file transfer mode. Software that mediates that transmission of COBIE data may capture this data automatically based on process model implementations:
- The party who created the data provided. This is required for individual record.
- The full history of all changes to the data must be included in the data file.
The authoritative source for this information is the design building information model. Ideally the information in this project wrapper will have been created during early design and "handed down" with the project as work progressed from design through to construction.
Information Requirements
| Context | Information Needed | MAN | REC | OPT | Actor Supplying | Functional Part |
|---|---|---|---|---|---|---|
| Precursor | The provisions of the exchange requirement COBIE-ER-01 must be provided as a wrapper that identifies the facility to which these floors and spaces belong. | |
Designer or Constructor | fp_model_project | ||
| Precursor | Site (General) information must be provided to identify the site upon which the the facility is placed. | |
Designer or Constructor | fp_model_site | ||
| Precursor | Facility (General) information must be provided to identify the facilities in which floors and spaces may be found. | |
Designer or Constructor | fp_model_building | ||
| Floor Name | Provide the name of each conceptual/physical vertical level of each of the facilities identified in the project wrapper. | |
Designer or Constructor | fp_building_storey | ||
| Floor Elevation (Quantity) | Elevation value and units above local project datum. | |
Designer or Constructor | fp_building_storey | ||
| Floor Height (Quantity) | Floor to Floor height and units. | |
Designer or Constructor | fp_building_storey | ||
| Floor Footprint (Coordinate) | X and Y coordinates of the bounding corners of floor area using local project datum. | |
Designer or Constructor | fp_building_storey | ||
| Floor Asset (Quantity) | Identification of the following values with associated quantities: Exterior Gross Area, Interior Gross Area, Plannable Gross Area, Rentable Area Usable, Interior Plannable Area | |
Designer or Constructor | fp_building_storey | ||
| Floor Asset (Method) | Identification of asset management method used to create Floor Asset (Quantity) data. | |
Designer or Constructor | fp_building_storey | ||
| Floor Nesting (Reference) | The identifier for the higher-level conceptual grouping in which the current floor is nested. | |
Designer or Constructor | fp_building_storey | ||
| Authoritative Source | The user responsible for creating the project wrapper data set. | |
Designer or Constructor | fp_apply_owner_history | ||
| History | All versions of information captured during the project will be provided in the file. Superseding data is explicitly identified. | |
Designer or Constructor | fp_apply_owner_history |