Coordination View Version 2.0 Summary

SYNOPSIS
      Official Name:     Coordination View Version 2.0     |  Official abbreviation:     CV V2.0
      Keyword in Header: CoordinationView_V2.0             |  Applicable to IFC Release: IFC2x3 TC1

Purpose of Coordination View Version 2.0

The Coordination View targets the coordination between the architectural, mechanical and structural engineering tasks during the design phase. It has been the first view definition developed by buildingSMART International and is currently the most implemented view of the IFC schema. The main purpose of the Coordination View is to allow sharing of building information models between the major disciplines of architecture, structural engineering, and building services (mechanical). It contains definitions of spatial structure, building, and building service elements that are needed for coordinating design information among these disciplines. The shared building information model is supposed to be re-editable by the receiving application. It includes the definition for spatial structure, building, and building service elements with shape representations, including both, parametric shapes for a limited range of standard elements, and the ability to also include non parametric shape for all other elements. Property sets, material definitions and other alphanumeric information can be assigned to those elements. The support of round-trip scenarios is excluded from the support of the coordination view.

The Coordination View has been first developed (as a binding) implemented for the IFC2x release, later adopted for the IFC2x2 release and is available as the Coordination View (Version 1.0)  for the IFC2x3(TC1) release. It has been used for IFC Certifications until 2009. It is currently replaced by the Coordination View Version 2.0. Main targets of the new Version 2.0 are:

• to provide a full and syntactically complete and correct sub model of the IFC2x3 TC1 schema
• to be compatible with extension by so called "Add-on" views 
• to be more strictly defined and suitable to automatic checking.
  
• to fix issues and scope creep that have been detected with the previous version 1.0
  

The Coordination View Version 2.0 is defined as a single Model View Definition, MVD. It should support several exchange requirements:

• Exchange Requirement "Architecture" (Architectural Model for Coordination) for exporting the IFC2x3 file corresponding to the Coordination View Version 2.0 from an architectural software application
• Exchange Requirement "BuildingServices" (Building Services Model for Coordination) for exporting the IFC2x3 file corresponding to the Coordination View Version 2.0 from an MEP software application
• Exchange Requirement "Structural" (Structural Model for Coordination) for exporting the IFC2x3 file corresponding to the Coordination View Version 2.0 from a structural engineering software application

• Coordination View V2.0 EntityList for IFC2x3 (Version 1.3 from 2010-03-08) PDF
• Coordination View V2.0 EntityList for IFC2x3 (Version 1.3 from 2010-03-08) XLSx  
  (note: Excel compatibility issues have been reported, when opening it in Excel 2003 or earlier - use PDF as the binding document)
• Coordination View V2.0 EXPRESS-G WALL PAPER for IFC2x3 (Version 1.0 - applies to Entity List Version 1.1 - V1.3) PDF
  (note: the wall paper is formated to print on A0 paper)
  
• Coordination View V2.0 EXPRESS sub model for IFC2x3 (Version 1.0 - applies to Entity List Version 1.1 - V1.3) PDF
  (note: The EXPRESS sub model is ONLY provided for reference and validation, NOT for implementation)
  

previous document versions

• Coordination View V2.0 EntityList for IFC2x3 (Version 1.2 from 2010-02-12) PDF
• Coordination View V2.0 EntityList for IFC2x3 (Version 1.2 from 2010-02-12) XLSx
• Improved CoordinationView EntityList for IFC2x3 (Version 1.1 from 2010-01-30)
• Improved CoordinationView Submodel Listing for IFC2x3 (Version 1.1 from 2010-01-30)
  

for explanations on how to read and understand the entity list for the Coordination View Version 2.0

Note: a detailed, per entity (or concept) requirement definition for the Coordination View Version 2.0 is currently developed and will accompany the sub schema and entity list. Automatic compliance checking code is developed in parallel.