GSA BIM Guidelines for Revit: Data Submittal

First cost is only the beginning for BIM data. The expectation of GSA is that the data will live on past construction to support all phases of the buildings life-cycle. In order to achieve the goals of GSA BIM initiative rigorous standards for the submittal of BIM data to GSA must be adhered to.

Schedule

Unless otherwise specifically overridden within the project Scope of Work you are required to submit your BIM data to a BIM Champion on the completion of each of the five project milestones listed below.

All of the requirements for formal data submittals (with the exception of CD phase & As-built phase) may be waived by GSA if real-time access to all project BIM data is provided to GSA.

  1. Design Concept Phase - AE
  2. Design Development (DD) Phase - AE
  3. Construction Documents (CD) Phase - AE
  4. Construction Delivery Phase - GC
  5. Closeout Phase (As-Built and Record Drawings - GC / AE

Standards

These standards apply to all data formally submitted to GSA

General

  • All submitted BIM data shall comply to all GSA BIM standards as documented on the GSA BIM Guidelines for Revit site at the time of contract signing.
  • All submitted data must open without errors. This includes any missing links. Data submitted with unresolved links will be rejected by GSA.
  • The data submitted will meet the Level of Detail as defined within the Model Progression Matrix and will be in a condition for downstream uses as defined within the Approved Use Guide.
  • All submitted BIM data shall be cleaned of extraneous “scrap” or “working space” layers, stories, abandoned designs, object creation and testing places, empty layers, and other content which is typically produced in BIM production.
  • Any Revit data being submitted must be submitted with it's corresponding Shared Parameters file.
  • Any Revit data being submitted is to have it's Project Browser Organization set to the standard GSA-VIEWS
  • No data submitted to GSA is to have an expiration date, such as published NavisWorks files.

External References

  • Only data which belongs to the submitter shall be submitted. When data which is not owned by the submitter must be submitted, these files shall begin with an "x" in their name. For example, if a mechanical Revit BIM is being submitted and it requires a link to the architectural BIM, the file name for the architectural BIM must begin with an "x".
  • Care should be taken to reduce the hardware requirements for submitted data. To this end, only data which is of critical importance to the submitted BIM should be actively referenced to it. Any data that is not critical to the proper display or functioning of the BIM should be detached or unloaded (hidden) prior to the data being submitted. For example, point cloud data referenced into a Navisworks model should be hidden prior to that model being submitted to GSA.
  • All submitted data must have the reference paths verified as being correct and, wherever possible, be relative pathed.

3D Imaging Data

  • 3D Imaging (point cloud) data is to be delivered to the GSA at the conclusion of the project. This should take place during the creation of the record model. Delivered point cloud data must follow all standards outlined within the GSA BIM Guidelines for Revit and must:
    • Be in both native authoring format and ASTM E57 format.
    • Be named in accordance with the Naming Standards.
    • Contain one set of data ready to import into a BIM authoring platform.
    • Be separated into manageable areas as defined by the project's Area Map.
    • The import ready data-set must align to the BIMs project coordinates.
    • Include 100% of the collected data.
    • If photos were taken as part of the data collection, they must be included.
    • When available, free viewers for the native data are to be included as part of the deliverable.
    • Include a completed point cloud quality report.

Deliverables

Single Model Workflow

Single Model Workflow infographic

Over the course of a project, various deliverables are expected by GSA. The largest of these staged deliverables will be the final data submittal which must meet all requirements of the GSA BIM Guidelines for Revit. These deliverables are not only limited to the BIM data. As part of the project's BEP development, teams should address the specifics of how deliverable objectives will be met.

The Core and Shell Master Model

One of the core concepts of GSA's strategy is the concept of an Core and Shell Master Model. Unlike the the fractured workflows of the past where design and construction data were often contained in separate datasets, GSA requires a single model be delivered that contains only the completed building information. Duplication of data, especially at final submittal, will not be accepted. Teams who do not plan for this may find themselves having to recreate large amounts of the project's data in order to merge the datasets at the end of the project.

The Core and Shell Master Model is not only the final product of all design and construction BIM efforts; it is also to be prepared in a specific form that will assist GSA in it's efforts to extend the BIMs lifecycle. This means the model will be purged of all project specific views, sheets, and schedules. Only information needed for continued maintenance and future work on the structure will be kept in the Core and Shell Master Model.

Project Specific Native BIM Dataset Core and Shell Master Model
The Project Specific Native BIM Dataset will:

  • Have all information specific to both the project and building.
  • Contain all schedules, views, sheets, and details required for a complete design history of the project.
  • Be cleaned of all "working" views and sections.
  • In suitable condition for another design or construction firm to review the project as history for any new work.
  • Contain a start-up page which will contain a basic project summary and information specific to the use of the model.
The Core and Shell Master Model will:
  • Contain only information specific to the building. Information specific to the project will be removed.
  • Have only views and sheets specific to the building's ongoing use and development.
  • Contain only COBie2 and SDM schedules. All other schedules will be removed.
  • Be cleaned of all phasing and temporary objects.
  • Have one 3D view per discipline. These will be colored per the MEP Color Mapping standard.
  • Have all "working" views and sections removed.
  • A single floor plan per floor and per discipline.
    • These views will be complete sheets with proper title blocks in a form suitible for printing by GSA.

Typical Revit Browser structure in a Project BIM Dataset

Example of Typical Revit Browser structure in a Project BIM Dataset

Typical Revit Browser Structure in a Core and Shell Model

Example of Typical Revit Browser structure in a Core and Shell Model

Standard


  • All demolished and temporary objects such as shoring, construction walls, and placeholder objects will be removed from the Master Model.
  • The Core and Shell Master Model will be created as a duplicate of the project's primary Project BIM(s) and then have project specific information removed.
  • Both the Project Specific Native BIM Dataset and a Core and Shell Master Model will be supplied to GSA.
  • Only views and sheets which support the ongoing use of the building will remain in the Core and Shell Master Model. Project specific views, sheets, and schedules will be stripped from the Core and Shell Master Model.
  • All objects in the Core and Shell Master Model will be on an existing phase.
    • Exceptions may be granted when GSA specifically directs a team otherwise. For example, GSA may wish for a proposed addition to remain in the model on a future phase.
  • The Core and Shell Master Model will not contain any legacy information such as demolished items.
  • Working views, sheets, and schedules will be removed from the model.
  • The Core and Shell Master Model will conform to all GSA BIM Standards.
  • Only COBie2 and SDM schedules will be in the Core and Shell Master Model, all other schedules will be removed from the model.
  • A clean 3D view for each discipline will be included. This view should highlight the discipline specific objects and only show other disciplines as needed for context.
  • Floor plans and reflected ceiling plans sheets will be included with the Core and Shell Master Model. These will, at a minimum, be per floor, include a completed title block, and be cleaned of project specific annotation. These will include non-project specific information such as room names and equipment tags.

More information and suggested Revit workflows can be found on the Revit Model Sharing tutorial.

Defining Deliverables

Many deliverables are required as part of the GSA Region 5 BIM Standard. It will require cooperation and planning by the entire team to ensure that the deliverable requirements are met on a timely basis. Should your team have any questions on exactly what is contained in a deliverable, they should seek guidance from GSA as soon as possible to avoid data rework.

Standard 2D Deliverables

Typical Dataset LOD

  • The overall LOD must be conveyed to GSA. It is critical that GSA understands the development level of your submitted dataset. It is not expected that submittals prior to the final As-Constructed submittal have a single LOD. It is understood by GSA that the dataset will evolve at different rates. The expectation is only that you clearly define to GSA what parts of your dataset are developed to what LOD.

Project Specific Native BIM Dataset

  • These are all files used in the authoring of the BIM dataset, including not only the primary files, .RVT for example, but also all supporting files. This includes, but is not limited to:
    • Any supporting text files such as Revit Shared Parameters
    • Blocks or Families used on the project stored as individual
    • All referenced data; images, 2D drawings, etc.
  • Exclusions to the dataset are Digital Professional Stamps and GSA Classified Data.

Core and Shell Master Model

As part of the team's final deliverable to GSA, a cleaned version of the master model is required. This model is stripped of all design and construction specific information and contains only the information required for the ongoing maintenance and future renovations of the building.

Master Coordination Model

  • The Master Coordination Model is the model used by the team during the Integration Reviews. This is typically either an Autodesk Navisworks or Solibri file.
  • The coordination model is to contain all data assembled in a manner which can be easily understood. Naming is to be clear and adhere to the general naming guidelines outlined in the Region 5 BIM Standards.
  • If the coordination model is an Autodesk Navisworks file, the individual source files are to be provided (NWF, NWC, NWD).

Quality Control Report

BIM Manual

  • This is an evolving narrative that gives the reader a high level concept of the BIM dataset. How it was developed, design history, participants, and other key information should be covered in the BIM Manual. Much of this information should be part of your project's BEP, Section H, in particular.

IFC Files

COBie2 Files

BIM Support Files

  • These are all files used in the production of the BIM dataset, including shared parameters, families, blocks, and other related files. Even files supplied to the team by GSA, such as shared parameters, must be included.

Folder Structure

The final data submittal is to have all data organized into a folder structure as outlined in the File Structure and Organization Standard. The team is encouraged to use this folder structure over the course of the project. Doing so will put the team in a good position for final delivery to GSA.

Required Deliverables - Design Stage

GSA Region 5 has identified 3 phases to the Design Stage of a typical project: Design Concept Phase, Design Development Phase, and Construction Documents Phase. At the conclusion of each of Design Stage phase, a formal delivery of BIM data to GSA is required. As part of the BEP, the team will have planned out the specifics of the deliverables such as LOD based on the project's Model Progression Matrix.

Note: If real-time data access has been provided to GSA, the need for formal data submittal at this stage may be waived.

Deliverable Design Concept Phase Design Development Phase Construction Documents Phase
Standard 2D Deliverables X X X
Typical dataset LOD 100 - 200 200 - 300 300
Project Specific Native BIM Dataset X X X
Master Coordination Model Optional Optional X
Quality Control Report X X X
BIM Manual X X X
IFC Files - X1 X
COBie2 Files - - X2
BIM Support Files X X X
Dataset in Standard Folder Structure Optional3 Optional3 X

1. Limited IFC sample to verify that IFC exports are working on the project dataset.
2. It is understood that Design Stage COBie2 data will not be complete, however all fields will be present in the model and Excel sheets delivered.
3. Although optional, it is highly recommended that all project data be stored in the GSA Region 5 Standard folder structure from the very beginning of the project.

Required Deliverables - Construction Stage

At least one time during the Construction Delivery phase of the project, an informal submittal of data to GSA is to occur. The purpose of this submittal is to allow GSA an opportunity to assist and advise on preparing the data for As-Built and Record Drawings. If the team or specific members of the team are new to the GSA requirements, it is suggested that several submittals and meetings take place during the construction phase to ensure a smooth closeout to the project.

Deliverable Design Concept Phase Design Development Phase Construction Documents Phase
Standard 2D Deliverables X X X
Typical dataset LOD 300-400 400-500 500
Project Specific Native BIM Dataset X X X
Core and Shell Master Model - Optional1 X
Master Coordination Model X X X
Quality Control Report X X X
BIM Manual X X2 X
IFC Files X X X
COBie2 Files Optional X3 X
BIM Support Files X X X
Dataset in Standard Folder Structure Optional4 Optional4 X

1. It is highly recommended that teams which have not completed previous projects under the GSA BIM Guidelines for Revit submit a copy of their Core and Shell Master Model for review by GSA.
2. A nearly complete BIM Manual should be included in the Project Close-out Phase submittal for GSA approval.
3. Coordinate the submittal of COBie2 data with the building maintenance staff to ensure that it is the correct data that can be used.
4. Although optional, it is highly recommended that all project data be stored in the GSA Region 5 Standard folder structure from the very beginning of the project.

Final Model Delivery

The final delivery of As-Constructed data to GSA will be a complete set of data for the project. It is to conform to the GSA Region 5 Standard folder structure and all other BIM Standards. This data will be provided to GSA on either a USB hard drive or USB flash drive. The data will be verified as working on the supplied media. All links will properly resolve.

Standard


  • All links, references, and URLs will resolve correctly.
  • Complete data set will conform to all GSA BIM Guidelines for Revit.
  • A complete Quality Control Report will be included.
  • Data will be unencrypted unless required by GSA data rules.
  • No restriction will be placed on any of the supplied data. For example, coordination models will not have an expiration date.
  • IFC data will be verified as working by importation into a BIM authoring platform.
Example of Typical Revit Browser structure in a Project BIM Dataset
Example of Typical Revit Browser structure in a Core and Shell Model
print Share Icon Last Reviewed 2017-08-13