The following tables for each BEP category include the information item and description from Section 5. The tables also include example values, a field name for each information item, a field type for the information, and the time that the information may or shall be added to the BEP.
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| BEP Path | A path to the BEP location. This location could be an online data source or a file location and file name. | http://bim.psu.edu/sampleBEP.pdf | BEPPath | URL | R | R | R |
| BEP Data Format | A description of the format used for storing the BEP data elements. | .PDF, .XLS, .DB, .JSON | BEPDataFormat | Text | R | R | R |
| BEP Executive Summary | A summary description of the BEP document developed to briefly communicate the contents and status of the BEP. | This BIM Execution Plan documents the team’s approach to managing the information regarding the facility throughout the planning, design and construction process, and including information delivery to support operations. | BEPExecutiveSummary | Text | R | R | R |
| Cover Page Image | A path to an image of the BEP cover. | http://bim.psu.edu/samplecoverimage.png | BEPCoverPage | URL | O | O | O |
| BEP Version Log | A table that includes all BEP versions. | (a table) | BEPVersion | Array | R | R | R |
| BEP Version Number | A version number for each BEP version. | Version 1.1 | BEPVersion.Number | Text | R | R | R |
| BEP Version Date | The date for the BEP version. | 20-Jun-22 | BEPVersion.Date | Date | R | R | R |
| BEP Version Description | A description of the specific BEP Version. | Original BEP developed by the Architect from the RFP BEP. | BEPVersion.Description | Text | R | R | R |
| BEP Version Creator Organization | The lead author organization who released the version of the BEP. | XYZ Architects | BEPVersion.CreatorOrganization | Text | R | R | R |
| BEP Version Creator Contact | The lead author contact who released the version of the BEP. | Jane Doe | BEPVersion.CreatorContact | Text | R | R | R |
| Approval Organization | The organization that may or should approve the BEP, depending upon contractual requirements. | ABC Owner | BEPVersion.ApprovalOrganization | Text | O | O | O |
| Approval Contact | The contact that may or should approve the BEP, depending upon contractual requirements. | Jim Doe | BEPVersion.ApprovalContact | Text | O | O | O |
| Approval Status | The status of the approval from the approval organization/contact. | Draft or Approved or Shared | BEPVersion.ApprovalStatus | Text | O | O | O |
| OPR Waivers | A table of all requested and approved waivers to the Owner Project Requirements. | Table | OPRWaiver | Array | O | O | O |
| Waiver Name | A name that represents the content of the Owner Project Requirement waiver. | Architectural Modeling Software Modification | OPRWaiver.Name | Text | O | O | O |
| Waiver Description | A description of the Owner Project Requirement waiver. | Request the use of Software A instead of Software B for the development of the Architectural Model and corresponding native file delivery modification. | OPRWaiver.Description | Text | O | O | O |
| Waiver Requested By | The organization requesting the Owner Project Requirement waiver. | Contractor A | OPRWaiver.RequestedBy | Text | O | O | O |
| Waiver Status | The waiver review or approval status. | Approved by Owner; Requested and In Review; Rejected | OPRWaiver.Status | Text | O | O | O |
| BEP Standard Used for Development | The BIM Execution Planning standard that is used to defined the required information categories, elements, and attributes contained within the BEP. | NBIMS-US™, BEP Standard Version 4.0 | BEPStandardUsed | Text | O | O | O |
| Acknowledgements | Acknowledgement of any creative commons or other copyrighted sources used for developing the BEP and any specific individual or organizational acknowledgements. | NIBS for BEP Standard Creative Commons license. | BEPAcknowledgements | Text | O | O | O |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| Project Name | A unique name for the project scope. | Bridge Project ABC | ProjectName | Text | R | R | R |
| Project Owner Name | The formal organizational name for the owner of the project. | Department of Transportation ABC | ProjectOwnerName | Text | R | R | R |
| Project Legal Address | The legal address for the project location. | Street, City, State Zip | ProjectAddress | Address | R | R | R |
| Project Description | A brief description of the project. | The project includes the construction of a new 100′ long bridge over the xyz stream along with all associated paving, guard rail, associated with the project. | ProjectDescription | Text | R | R | R |
| Project Delivery Method | A description of the project delivery method used for contracting with the prime contracted entities with the owner. | Design-Bid-Build with low-cost selection of the prime construction contractor | ProjectDeliveryMethod | Text | O | O | O |
| Team Selection Procedure | Description of the approach to select the team members to complete the project. | Low Cost; Best Value Selection | TeamSelection | Text | O | O | O |
| BIM Contracting Procedure | A description of any specific BIM-related contracting procedures to be used on the project. | The designer will have clear BIM requirement, etc. | BIMContracting | Text | O | O | O |
| Owner Modeling Guide Title | The title of the owner modeling guide(s) to meet the owner project requirements. | State XYZ Design Modeling Guide, Version 1.0 | OwnerModelingGuide | Text | O | O | O |
| Owner Modeling Guide Location | The path to the owner modeling guide(s). | http://dot.gov/modelingguide | OwnerModelingGuideLocation | URL | R | R | R |
| Project Information Requirements Title | A title for the Project Information Requirements for the project. | Project X Information Deliverable Requirements | ProjectInformationRequirementsTitle | Text | R | R | R |
| Project Information Requirements Location | The path to the Project Information Requirements. | http://dot.gov/projectinformationrequirements | ProjectInformationRequirementsLocation | URL | R | R | R |
| Facility Type Classification | The classification value for the type of facility. This number could be the OmniClass Table 11 number or a unique value system from the owner. | 11-12 21 31 | FacilityTypeClassification | Text | O | O | O |
| Facility Type Name | The name of the type of facility. The owner may have a proprietary list of facility types or the team should include the facility type from OmniClass Table 11. | High School | FacilityTypeName | Text | O | O | O |
| Project Identification Table | A table with the identification numbers used by project team members to identify the project. | (a table) | ProjectID | Array | O | O | O |
| Project Identification Description | A description of the type of project identification used. | Bridge Identification Number; Owner Project Reference Number | ProjectID.Description | Text | O | O | O |
| Project Identification Value | The value of the project identification item. | District 2, Bridge 234; Project 12345 | ProjectID.Value | Text | O | O | O |
| Project Certifications Table | A table that identifies the relevant project certifications along with the value of each certification. Examples of certifications can include environmental sustainability certification (e.g., LEED or Green Globes), structural facility certifications (e.g., OSHPD compliance), or other relevant certifications. | (a table) | Certification | Array | O | O | O |
| Certification Information | Title of the type of certification. | LEED | Certification.CertificationName | Text | O | O | O |
| Certification Value | The goal (if the project is in progress) or value achieved (if the project is complete). | Gold | Certification.CertificationValue | Text | O | O | O |
| Project Metrics Table | A table that defines core metrics for categorizing or classifying the project scope, scale or characteristics. | (a table) | MetricsTable | Array | O | O | O |
| Project Metric Name | The name of the project metric type used on a project. | Bridge Length | MetricsTable.MetricName | Text | O | O | O |
| Project Metric Value | Quantitative value of the metric on the project. | 100 | MetricsTable.MetricValue | Number | O | O | O |
| Project Metric Unit | Unit of measure for the metric. | Feet | MetricsTable.MetricUnit | Text | O | O | O |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| Organization | A table with all core organizations related to BIM scopes of work on the project. | (a table) | Organization | Text | R | R | R |
| Organization Name | The formal name of the organization. | ABC Owner | Organization.OrganizationName | Text | R | R | R |
| Abbreviation | Abbreviation of the organizational name for use in BEP tables. | ABC; Construction | Organization.Abbreviation | Text | O | O | O |
| Phone Number | The main phone number for the organization. | +1 (202) 555-0144 | Organization.PhoneNumber | Phone Number with Country Code | O | R | R |
| Office Location | The primary office location for the organization. | 02 Street, Washington, DC 20001 | Organization.OfficeLocation | City, State, Country | O | R | R |
| Organization Role | The primary role of the organization on the project. | Owner, Prime Designer, Prime Constructor | Organization.OrganizationRole | Text | O | R | R |
| Contact | A table for all core contacts related to BIM scopes of work on the project. | (a table) | Contact | Array | R | R | R |
| Organization Name | The formal name of the primary organization for a contact. | ABC Owner | Contact.Organization | Text | R | R | R |
| Contact Name | The name of the contact. | Jim Doe | Contact.ContactName | Text | R | R | R |
| Contact Role | The primary role of the contact on the project. | Information Manager | Contact.ContactRole | Text | R | R | R |
| Email Address | The primary email address of the contact. | jmcbim@abcowner.gov | Contact.EmailAddress | R | R | R | |
| Phone Number | The primary phone number for the contact. | +1 (202) 555-0198 | Contact.PhoneNumber | Phone Number | R | R | R |
| Primary Location | The primary location for the contact. | 01 Street, Washington, DC 20001 | Contact.PrimaryLocation | Address, City, State, Country | O | O | O |
| INFORMATION ITEM | DESCRIPTION | Examples | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER)) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| BIM Roles | A table to define the roles and responsibilities related to the information management process on the project. | (a table) | Role | Array | O | R | R |
| Role Name | The name of a role, e.g., BIM Manager, Project Manager, etc. | Information Manager, BIM Manager | Role.Name | Text | O | R | R |
| Role Description | A general description of the role. | (reference the Core BIM Requirements for common role definitions) | Role.Description | Text | O | R | R |
| Role Responsibility | The responsibilities of individuals within this role as it relates to the information management processes of the project. | (reference the Core BIM Requirements for common role responsibility) | Role.Responsibility | Text | O | R | R |
| Required by Contract | A value to define whether the role is required by contract. | Yes, No | Role.ContractRequired | Text | O | O | O |
| Role Code | A unique role categorical value if an entity uses a code value. | IM, PM | Role.Code | Text | O | O | O |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| Project Phases | A table of project phases. A phase is a duration of time associated with a project task(s). | (a table) | Phase | Array | R | R | R |
| Phase Name | The name of the project phase. | Conceptual Design | Phase.Name | Text | R | R | R |
| Phase Description | The description of the project phase. | The initial design phase to identify the general form and function of the facility to an approximate level of 30% design completion. | Phase.Description | Text | O | O | O |
| Estimated Start date | The estimated start date for the phase. | 1/1/2022 | Phase.EstimatedStartDate | Date | R | R | R |
| Estimated Completion Date | The estimated completion date for the phase. | 6/30/2022 | Phase.EstimatedCompletionDate | Date | R | R | R |
| Actual Start Date | The actual start date for the project phase (if started). | 2/1/2022 | Phase.ActualStartDate | Date | O | O | O |
| Actual Completion Date | The actual completion date for the project phase (if complete). | 7/1/2022 | Phase.ActualCompletionDate | Date | O | O | O |
| Project Milestones | A table of project milestones. A milestone is a discreet point in time associated with a project outcome. | (a table) | Milestone | Array | R | R | R |
| Milestone Name | The name of the project milestone. | Conceptual Design Complete | Milestone.Name | Text | R | R | R |
| Milestone Description | The description of the project milestone. | Date of completion for the building program. | Milestone.Description | Text | O | O | O |
| Estimated Date | Estimated schedule date for the milestone (prior to milestone completion). | 12/1/2022 | Milestone.EstimatedDate | Date | R | R | R |
| Actual Date | Actual milestone completion date (if complete). | 11/1/2022 | Milestone.ActualDate | Date | O | O | O |
| Phase (key reference to Phase) | The project phase in which the milestone exists (reference Phase table). | Conceptual Design | Milestone.Phase | Text (reference Phase) | R | R | R |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| Project Goals | A table of project goals that identifies actions and outcomes that add value to the project. | (a table) | Goal | Array | R | R | R |
| Goal Description | A project goal defines a desired outcome needed for project success. Some project goals are most effectively achieved using BIM. The goals, aligned BIM Uses, and the desired outcomes and deliverables are documented in the BEP. | Increase design quality by clearly documenting the initial program requirements and performing design reviews with stakeholders. | Goal.Description | Text | R | R | R |
| Priority | The priority of the defined goal. Goals and BIM Uses are prioritized based upon need for project success and any constraints to achieving the desired outcome. | Essential, High, Medium, Low | Goal.Priority | Text | O | O | O |
| Potential BIM Uses to Support Goal | A BIM Use that has the potential to enhance the goal. See the NBIMS-US™ BIM Use Definition section for BIM Uses. | Author Design, Review Design Models, Coordinate Design Models | Goal.PotentialBIMUses | Text | O | O | O |
| Goal Customer | The customer for the goal who requires the deliverable to move the project forward. | Owner | Goal.Customer | Text (reference Organization) | R | R | R |
| Goal Primary Responsible Party | The primary party that will be responsible for achieving the goal through BIM. | Architect | Goal.ResponsibleParty | Text (reference Organization) | R | R | R |
| Constraints | The constraint(s) that limits the ability to achieve a goal. | Software availability; model federation; level of development | Goal.Constraints | Text | O | O | O |
| Goal Phase | The phase(s) of the goal. At what point in the project does execution of the BIM Use provide the most value to the project. | Design phase | Goal.Phase | Text (reference Phase) | O | O | O |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| BIM Use Table | A table to define attributes of each BIM Use along with evaluation criteria used to select the BIM Use. | (a table) | BIMUse | Array | R | R | R |
| BIM Use Name | The name of the BIM Use | Author Design | BIMUse.Name | Text | R | R | R |
| BIM Use Method | The method used to achieve the BIM Use purpose. | Using 3D parametric modeling software | BIMUse.Method | Text | O | R | R |
| BIM Use Outcome | The outcome desired from the implementation of the BIM Use. | Develop design intent model. | BIMUse.Outcome | Text | R | R | R |
| BIM Use Definition | The definition of the BIM Use. | Develop design using BIM for the architectural, mechanical, structural and electrical systems. | BIMUse.Definition | Text | R | R | R |
| BIM Use Value to Project | The value of the BIM Use to the project. | High | BIMUse.Value | Text | O | O | O |
| BIM Use Responsible Party | The primary responsible party for implementing the BIM Use. | Architect | BIMUse.RP | Text | O | O | O |
| Value to Responsible Party | The value of the BIM Use to the primary party. | High | BIMUse.ValueToRespParty | Text | O | O | O |
| Resource Availability for BIM Use | The resource availability for implementing the BIM Use. | Designers and tools are available. | BIMUse.ResourceAvailability | Text | O | O | O |
| Competency Level with BIM Use | The competency level of the responsible party for implementing the BIM Use. | Designers are competent with BIM software. | BIMUse.CompetencyLevel | Text | O | O | O |
| Experience Level with BIM Use | The historical experience of the key team members of the responsible party for implementing the BIM Use. | Designers are experienced with developing models. | BIMUse.ExperienceLevel | Text | O | O | O |
| Additional Resources/Competencies Required to Implement | Additional resources needed to implement the BIM Use. | None | BIMUse.NeededResources | Text | O | O | O |
| Additional Training Required for BIM Use Implementation | Additional training needed to implement the BIM Use. | None | BIMUse.NeededTraining | Text | O | O | O |
| Proceed Decision | The decision regarding whether to proceed with the BIM use. | Yes, Maybe, No | BIMUse.Implementation | Text | R | R | R |
| Software Required for Use | The requirement for a specific software application to be used for the BIM Use, if any. | Software XYZ is Required | BIMUse.Software | Text | O | O | O |
| BIM Use Project Phase | The phase(s) in which the BIM Use will be implemented. | Design Phases | BIMUse.Phase | Text | O | O | O |
| Notes | Notes regarding the BIM Use. | The architectural model will provide the reference for the mechanical, structural and electrical systems models. | BIMUse.Notes | Text | O | O | O |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| BIM Process Diagram – Level 1 | The path to a detailed process diagram for the execution of each BIM Use, which also identifies the information exchanges and process workflow. | http://BIMMaps/Level1Diagram.pdf | BIMProcess | URL | O | R | R |
| BIM Use Process Diagrams – Level 2 | A table of the BIM uses with their associated BIM Use process diagram. | (a table) | BIMUseProcess | Array | O | O | R |
| BIM Use Name (link to BIM Use) | BIM Use name for the Level Two process diagram. | Author Design | BIMUseProcess.Name | Text | O | O | R |
| BIM Use Process Diagram Path | A path to the process diagram of the activities, information exchanges, and process workflow for the BIM Use. | http://BIMDiagrams/Level1Diagram.pdf | BIMUseProcess.ProcessDiagramPath | URL | O | O | R |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER)) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| Information Exchange Table | A table that defines the characteristics of each information exchange on the project. | (a table) | IE | Text | R | R | R |
| Information Exchange Name | The name of the information exchange. | Design Model | IE.Name | Text | R | R | R |
| Information Exchange Description | A description of the purpose and general contents of the information exchange. | The design intent model at the completion of the design phase including architectural, structural, and MEP design content. | IE.Description | Text | R | R | R |
| Milestone | The milestone that is associated with the information exchange. | Design phase | IE.Milestone | Text | R | R | R |
| Information Sender | The responsible party for creating the information. | Designer | IE.Author | Text | O | O | R |
| Information Receiver(s) | The organization(s) to receive the file. | Constructor | IE.Receiver | Text | O | O | R |
| Frequency | The frequency of the information exchange. | One Time, Every Month | IE.Frequency | Text | O | O | R |
| Due Date | The date that the initial (if iterative) or final (if one time) submission is due. | 11/11/2022 | IE.DueDate | Date | O | O | R |
| Information Location | The path to the location of the information exchange. | https://sample_data_location | IE.ModelFile | URL | O | O | R |
| Information Modeling Authoring Software | The software used to develop the information. | Revit, ArchiCAD, OpenRoads | IE.ModelSoftware | Text | O | O | R |
| Native Information Source Format | Native data source type, e.g., a specific file format. | .rvt, .dgn, .xls | IE.NativeFileFormat | Text | O | O | R |
| Information Exchange Format(s) | Information exchange format, e.g., IFC, other open formats, other proprietary formats. | .ifc, .xls, .pdf, .idsxml | IE.ExchangeFileFormat | Text | O | O | R |
| BIM Use | The BIM Use that develops the information exchange. | Author Design | IE.BIMUse | Text | R | R | R |
| Required by Contract | A value to define whether an information exchange is required by contract. | Yes, No | IE.ContractRequirement | Text | O | O | R |
| Permitted Use | The future BIM Uses that can rely upon this information. | Coordinate Design | IE.PermittedUse | Text | O | O | R |
| Required Approvals | The approvals that are necessary for the information exchange. | Yes | IE.RequiredApprovals | Text | O | O | R |
| Required IE Delivery Procedure | The process to be completed to deliver the information exchange. | The files should be transmitted via xyz with email to abc upon transfer. | IE.DeliveryProcedure | Text | O | O | R |
| Information Exchange Definition | The location of the information exchange definition requirements which could be a defined Information Definition Specification (IDS), a Model Element Table (MET) definition, or another information exchange. | IFC 4 Design Transfer View by BuildingSMART International or MET Schematic Architectural Design | IE.IEDefinition | Text | O | O | R |
| Model Element Table | A table that defines the level of development and level of information required for the content to be included in an information exchange. | (a table) | MET | Array | O | O | O |
| Information Exchange Name | The name of the information exchange. | Design Model | MET.IEName | ||||
| Model Element Category | The categorical number or value for the model elements, e.g., Omniclass, Uniclass, etc. | OmniClass Table 21 10 10 10 | MET.MECategory | Text | O | O | O |
| Model Element Category Name | The name of the category, e.g., foundations. | Standard Foundations | MET.MEName | Text | O | O | O |
| Level of Development | The level of development value from the defined LOD definitions. | BIMForum LOD 300 | MET.LOD | Text | O | O | O |
| Level of Information | The model information that can be relied upon within the information exchange. | BIMForum LOD 300 Attributes | MET.LOI | Text | O | O | O |
| Information Format | The geometric format for the modeled geometry (2D/3D/data). | 3D with Attribute Data | MET.Format | Text | O | O | O |
| Model Element Author | The model element author for the category of elements. | Architect | MET.Author | Text | O | O | O |
| Notes | Notes of value for the model planners or developers. | MET.Notes | Text | O | O | O |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| Collaboration Strategy Description | A description of the BIM collaboration procedures to be used on the project. | Parties will collaborate via meetings, an information sharing platform, and colocation during the design and construction phases. | CollaborationDescription | Text | O | R | R |
| Collaborative Activity Table | A table to define the collaborative activities such as meetings or workshops that will be performed on the project. | (a table) | CollaborativeActivity | Array | O | O | R |
| Collaborative Activity Type | The type of collaborative activity to be performed on the project. | Design Coordination Meeting, Construction Coordination Meeting, Design Review Workshop | CollaborativeActivity.ActivityType | Text | O | O | R |
| Responsible Party | The organization or contact who is responsible for convening the collaborative activity. | General contractor, Architect, Engineer | CollaborationActivity.ResponsibleParty | Text | O | O | R |
| Project Phase | The project phase(s) for the collaborative activity. | Design phase | CollaborationActivity.ProjectPhase | Text | O | O | R |
| Frequency | The frequency of the collaborative activity on the project. | Weekly | CollaborationActivity.Frequency | Text | O | O | R |
| Participants | The participants for the collaborative activity. | Architect, Structural engineers, MEP | CollaborationActivity.Participants | Text | O | O | R |
| Location | The location of collaborative activity. | 01 Street, Washington, DC 20001 | CollaborationActivity.Location | Text | O | O | R |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| Quality Management Strategy | Overall strategy to manage the quality of model and derivative information. | A text discussion of the overall quality management strategy. | QualityManagementStrategy | Text | O | R | R |
| Quality Control Activity | A table of information regarding the quality control activities on the project. | (a table) | QualityControl | Array | O | R | R |
| Quality Control Activity Type | The type of QC activity that will be performed. | Standards Check; Interoperability Test for 2 Software Applications | QualityControl.ActivityType | Text | O | R | R |
| Required by Contract | An indication of whether the quality check is required by contract. | Yes, No | QualityControlCheck.Required | Text | O | R | R |
| Activity Description | A description of the quality control activity. | Ensure that the BIM and AEC CADD Standard have been followed (fonts, dimensions, line styles, levels/layers, etc.) | QualityControlCheck.Description | Text | O | R | R |
| Responsible Party | The organization responsible for performing the quality control activity. | Designer, Information Management Consultant | QualityControlCheck.ResponsibleParty | Text | O | R | R |
| Software Application | The software application(s) to be used to perform the quality control activity. | Name of Software Product | QualityControlCheck.SoftwareApplication | Text | O | O | O |
| Frequency | Frequency of performing the quality control activity. | Monthly, Once | QualityControlCheck.Frequency | Text | O | R | R |
| Location | The location of performing the quality control activity. | XYZ City, State, Zip | QualityControlCheck.Location | Text | O | O | O |
| Reference Document | A path to any reference documentation describing or defining the quality control activity. | http://company.com/reference_document | QualityControlChecks.ReferenceDocument | URL | O | O | O |
| Model Data Accuracy | A table of information regarding the model data accuracy of the project. | (a table) | ModelAccuracy | Array | O | O | O |
| Discipline | The discipline that compiled the model data. | Survey | ModelAccuracy.Discipline | Text | O | O | O |
| Existing Conditions Data Source Name | The name of the data source containing existing conditions data. | Existing Field Survey | ModelAccuracy.DataSourceName | Text | O | O | O |
| Survey Data Type | The data type of the captured data, e.g., laser scan, photogrammetry, or field survey. | Laser scan, photogrammetry, field survey | ModelAccuracy.SurveyDataType | Text | O | O | O |
| Level of Accuracy | The level of geometric accuracy for the data source. | USIBD LoA20 | ModelAccuracy.LOA | Text | O | O | O |
| Software Compatibility Testing | A table of tests for BIM software that will exchange files. | (a table) | SoftwareCompatibility | Text | O | O | O |
| Export Software Application | The exporting software of a software compatibility test. | Software Name A | SoftwareCompatibility.Export Application | Text | O | O | O |
| Import Software Application | The importing software of a software compatibility test. | Software Name B | SoftwareCompatibility.ImportApplication | Text | O | O | O |
| Test date | The date of the compatibility test. | 1/1/2022 | SoftwareCompatability.TestDate | Date | O | O | O |
| Notes | Notes from the software compatibility test. | Description of any exceptions or important notes from the compatibility test. | SoftwareCompativility.Notes | Text | O | O | O |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| Software Table | A table with the software to be used on the project. | (a table) | Software | Array | R | R | R |
| Software Name | The title of the software application. | Company A’s Modeling Software | Software.SoftwareName | Text | O | R | R |
| Software Version | The version of the software application. | Version 2022.1 | Software.SoftwareVersion | Text | O | O | R |
| File format | The native file format(s) used to save models within the software application. | .xyz | Software.FileFormat | Text | O | O | R |
| Maximum Model Size | The maximum size of the models within the software application. | Maximum size of 100 GB | Software.MaxModelSize | Text | O | O | O |
| BIM Use(s) | The name(s) of the BIM Use(s) that will require the software. | Author Design Model | Software.BIMUse | Text | R | R | R |
| Responsible Party | The name of the organization that is the responsible party for the software. | Architects Name | Software.ResponsibleParty | Text | R | R | R |
| Discipline | The discipline of the responsible party. | Architecture | Software.Discipline | Text | O | O | R |
| Contact | The contact responsible for the identification and selection of the software | John Doe | Software.Contact | Text | O | O | R |
| Hardware Considerations | Identify any specific hardware needs related to the software. | Requires large graphics card and 32 GB of RAM | Software.HardwareConsiderations | Text | O | O | O |
| Software Update Process | A description regarding whether the software will or will not be updated on a project if new software versions are released during the project duration. If so, the detail to update will be provided in this field. Examples would be to update to new versions, meet to discuss, test impact on others, or no updates. | The project will not update to new versions since it is a very short project. | Software.UpdateProcess | Text | O | O | R |
| Notes | Notes regarding the software application’s selection and use on the project. | Modeling Software was selected due to the existing content libraries and general modeling efficiency. | Software.Notes | Text | O | O | O |
| Hardware Table | A table with the different types of hardware needed for the project, including computers, tablets, network infrastructure, etc. | (a table) | Hardware | Array | O | O | R |
| Hardware Name | The hardware that will be used on the project. Examples include computers, survey devices, data capture devices, and visualization hardware. | Computer Vendor A’s Model XYZ | Hardware.Name | Text | O | O | O |
| Hardware Owner | The organization that owns or will own the hardware on the project. | Project Architect | Hardware.Owner | Text | O | O | R |
| Hardware Specification | The specifications for the hardware. | XYZ Graphics Card and 64 GB of RAM | Hardware.Specification | Text | O | O | O |
| Hardware Quantity | The quantity needed for the specific type of hardware. | 2 | Hardware.Quantity | Number | O | O | O |
| BIM Use(s) | The name of BIM Use(s) supported by the hardware. | Author Design | Hardware.BIMUse | Text | O | O | R |
| Procurement Approach | The procurement approach for the hardware, e.g., purchase, rent, or available within an organization. | Must be purchased for project | Hardware.Procure | Text | O | O | O |
| Notes | Notes regarding the hardware selection and use on the project. | This hardware will support multiple use cases. | Hardware.Notes | Text | O | O | O |
| Internet Access (Communication Access) | A table of internet access needs and plans for different project locations. | (a table) | InternetAccess | Array | O | O | O |
| Location Description | Project location description that requires internet access for all locations on the project that require internet access. | Jobsite; Constructors Office | InternetAccess.Location | Text | O | O | O |
| Access Method | Method(s) to be used to provide internet access at the location, e.g., Wi-Fi, cellular, wired, or satellite. | Distributed WiFi on jobsite | InternetAccess.AccessMethod | Text | O | O | O |
| Speed | The speed of the connections that are required for the tasks to be completed at the location. | 1 GB/second | InternetAccess.Speed | Text | O | O | O |
| Security Requirement | Security requirement(s) for the internet access/communication location. | Access points to be secured with password protection. | InternetAccess.Security | Text | O | O | O |
| Shared Model Development Resources | A table of families, workspaces, and databases that are shared resources for information creation or use. | (a table) | Resources | Table | O | O | O |
| Shared Resource Name | The name of the shared model development resource. | XYZ Model Authoring Content Library of Template Objects | Resources.Name | Text | O | O | O |
| Version | The version of the shared model development resources. | Version 2.0 | Resources.Version | Text | O | O | O |
| Shared Resource Owner | Name of the organization or entity who owns the shared resource. | Owner | Resourses.Owner | Text | O | O | O |
| Description | A description of the shared model development resources. | The owner’s library of content families that should be used to author the parametric design model. | Resources.Description | Text | O | O | O |
| BIM Use | The BIM Use(s) that will leverage the shared resource. | Author Design | Resources.BIMUse | Text | O | O | O |
| Information Sharing Platform(s) | A table to defines the common data environment and information sharing platforms that will be used on the project. | (a table) | Platform | Array | R | R | R |
| Platform Name | The name of the information sharing platform. | XYZ Online Sharing Platform Service | Platform.Name | Text | R | R | R |
| Platform Version | The version of the information sharing platform. | Version 3.0 | Platform.Version | Text | O | ||
| Platform Owner | The organization that either owns or has purchased the information sharing platform for the project. | Project Owner | Platform.Owner | Text | R | R | R |
| Platform Manager | The organization responsible for managing and maintaining the platform. | Project BIM Coordinator Entity | Platform.Manager | Text | R | R | R |
| Platform Capability Breadth | The level of breadth of the capability of the platform, e.g., information sharing, automated version control, statusing of information, information security, change management, etc. | Online file storage with automated version control; individual status for each file; integrated workflow management; request for information; change management tracking system; submittal management. | Platform.Capabilities | Text | O | O | O |
| Complies with CDE Requirements | A value to specify whether the information sharing platform complies with the Common Data Environment requirements. | Fully complies with Owner CDE Requirements. | Platform.CDE | Text | O | R | R |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER)) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| Model Federation Description | A description of whether the model includes the complete asset, or are model(s) to be broken into different sections, e.g., floors, road segments, etc. | The design intent model will be federated into separate models for the architectural, structural and MEP models for the primary building. | FederationDescription | Text | O | R | R |
| Naming Convention | A table that defines the naming conventions that will be used for data sources and common naming requirements for elements within the modeled content. | (a table) | NamingConvention | Array | O | R | R |
| Convention Type | The type of naming convention to be used, e.g., files, models, levels, or elements. | Design Model Files; Building Level Names; Equipment Names; Room Names | NamingConvention.Type | Text | O | R | R |
| Naming Convention Title Requirement | The title of the naming convention requirements to be used for the content type. | NBIMS-US™ Core BIM Filename Convention; Owner Building Level Naming Convention; Owner Equipment Naming Convention; etc. | NamingConvention.Requirement | Text | O | R | R |
| Naming Convention Version | The version of the naming convention to be used for the project. | Version 4 | NamingConvention.Version | Text | O | R | R |
| Description of Naming Convention | A description of the naming convention systems. The description may be a complete description, or may be a summary description with additional detailed contained in the Location of Naming Convention Details. | All design model files should have the file naming conventions as follows: (list of naming convention); Rooms will be named … | NamingConvention.Description | Text | O | R | R |
| Location of Naming Convention Details | A path to a source with additional details regarding the naming convention. | https://omniclass.table10 | NamingConvention.Location | URL | O | R | R |
| Reference Coordinate System | Underlying global rectangular Cartesian coordinate system to which all geometry refers. | State Plane, UTM | ReferenceCoordinateSystem | Text | R | R | R |
| UTM Zone | The Universal Transverse Mercator Zone for the project location | 18T | UTMZone | Text | R | R | R |
| Horizontal Units of Measure | The units of measure for horizonal measurements. | Meters, US survey feet, international feet | HorizontalUnitOfMeasure | R | R | R | |
| Vertical Units of Measure | The units of measure for vertical measurements. | Meters, US survey feet, international feet | VerticalUnitOfMeaasure | R | R | R | |
| Horizontal Datum | The specified horizontal datum for all horizontal position. | NAD 83/2011 | GeodeticDatum | R | R | R | |
| Vertical Datum | The specified vertical datum for all vertical position. | NAVD 88 | VerticalDatum | R | R | R | |
| Project Origin Longitude | The longitude for the project coordinate system to be used on the project. | 42 (deg) | OriginLatitude | Number | O | O | R |
| Project Origin Latitude | The latitude for the project coordinate system to be used on the project. | 43 (deg) | OriginLongitude | Number | O | O | R |
| Project Origin Elevation | The elevation for the project coordinate system to be used on the project. | 1000 | OriginElevation | Number | O | O | R |
| Project Grid Offset from True North | The number of degrees that the project grid is offset from True North. | 25 (deg) | GridNorthOffset | Number | O | O | R |
| Reference Grid | A path to a reference grid for use in modeling. | https://project/reference.grid | ReferenceGrid | URL | O | O | O |
| Reference Survey | A path to the referenced survey to be used for the project. | https://project/survey | ReferenceSurvey | URL | O | O | O |
| Building Information Management Standards | A table of standards that will be used to define requirements for a specific purpose. | (a table) | Standard | Array | O | O | O |
| Standard Name | The name of the referenced standard. | NBIMS-US™ Core BIM Requirements, NCS, CSI OmniClass Table 21, etc. | Standard.Name | Text | O | O | O |
| Standard Version | The version of the referenced standard. | Version 4 | Standard.Version | Text | O | O | O |
| Standard Purpose | The purpose of referencing the standard for defined requirements. | Core BIM Requirements apply to all… or OmniClass tables used for all model element categories and project phases. | Standard.Purpose | Text | O | O | O |
| INFORMATION ITEM | DESCRIPTION | EXAMPLES | FIELD NAME | FIELD TYPE | RFP BEP (BY OWNER) | PROPOSAL BEP (BY PROPOSER) | PROJECT BEP (BY TEAM) |
|---|---|---|---|---|---|---|---|
| Risk Register | A table of the primary risks that impact the information practices on the project. | (a table) | RiskRegister | Array | O | R | R |
| Risk Name | The name of the risk. | Inadequate trained modelers for design authoring | RiskRegister.Risk | Text | O | R | R |
| Risk Description | A description of the risk. | Availability of design authoring modelers is limited and could cause schedule delays. | RiskRegister.Description | Text | O | R | R |
| Probability | The probability that a risk may occur on the project. | Low | RiskRegister.Probability | Text | O | R | R |
| Consequence | The consequences that may occur if the risk is encountered. | Design schedule will be extended and/or poor quality design models. | RiskRegister.Consequence | Text | O | R | R |
| Mitigation Methods | A description of the mitigation method(s) to be used to mitigate or manage the risk. | Train additional modelers within the design firm. | RiskRegister.MitigationMethods | Text | O | R | R |
| Risk Category | A category for various types of risk, e.g., training, information approval, or information sharing. | Training | RiskRegister.RiskCategory | Text | O | R | R |
| Risk Status | The status of addressing the risk, e.g., open, closed, etc. | Open | RiskRegister.Status | Text | O | R | R |
| Responsible Party | The lead party responsible for managing the specific risk. | Architect | RiskRegister.ResponsibleParty | Text | O | R | R |
Note: The IM risk register elements are focused on the risks associated with the information management process, and ideally, will be incorporated into the project risk register.
The NBIMS-US™ v4 is a consensus-based national-level standard focused on defining standard approaches and guidelines to defining requirements, planning BIM adoption, and exchanging information between project team members. MORE
Established by the United States Congress, NIBS’ mission is to serve the public interest by advancing building science and technology to improve the built environment.
Subscribe to receive NIBS news and information.
Follow us:
