How can I prevent BCF import errors when using the Coordination Issues tool?
Answer
To import coordination issues from third-party software programs (e.g., Navisworks®, Solibri®, Revizto®) into Procore's Coordination Issues tool, your company's BCF files must comply with the BIM Collaboration Format (BCF) v2.1 standard 
, from buildingSMART International .
Important
- Import failures typically occur when your third-party software does not export files in the required format.
- To ensure a successful import, always ensure that your third-party software's export settings are configured to export a valid BCF v2.1 file.
Pre-Import Checklist
For a successful import, your BCF file must meet these five (5) conditions:
| # | Step | Details |
|---|---|---|
| 1 | Include Required Attributes | Ensure every issue includes the Mandatory Attributes. To create a clear and effective issue in Procore, issues should also include the Additional Attributes. |
| 2 | Attach Visual Context | Attach at least one (1) snapshot or viewpoint to every issue. |
| 3 | Link to Model Elements | Link each issue to at least one (1) model element so Procore can place it correctly. |
| 4 | Use the Correct BCF Version | Set your software to export using the BCF v2.1 format, which generates a BCF file. |
| 5 | Prevent File Corruption | If an import fails unexpectedly, the file may be corrupt. Always try re-exporting it from your software. |
Technical Requirements for BCF 2.1 Imports to Procore
For a successful import, Procore requires a specific file structure and mandatory data fields as defined by the BIM Collaboration Format (BCF) v2.1 standard .
File Structure
A .bcf file is a ZIP archive that must be structured as follows:
At the root of the archive:
- bcf.version: A required XML file that identifies the file as BCF v2.1.
- project.bcfp: An optional file for referencing a project.
Inside each issue's subfolder:
- markup.bcf: Contains the core issue details.
- viewpoint.bcfv: Contains the camera and model data for a viewpoint. If the source software exports multiple viewpoints, there will be multiple .bcfv files.
- snapshot.png: A snapshot image of the viewpoint. Multiple .png files may be present.
Mandatory Attributes
At a minimum, the markup.bcf file must contain these attributes for a successful import.
| Element/Attribute | Description |
|---|---|
| Topic.GUID | The globally unique identifier for the issue. |
| Topic.Title | The title of the issue. |
| Topic.CreationDate | The date the issue was created. |
| Topic.CreationAuthor | The email address of the issue's creator. |
Additional Attributes
To create clear and effective coordination issues in Procore, your BCF files should include topic and comment information, viewpoint and component data, and detailed camera and snapshot settings. While Procore only requires the Mandatory Attributes to be present when importing an issue, including these additional attributes provides essential context for your team.
When configuring your third-party BIM software's export settings, it's recommended to include the following data:
Topic and Comment Information
This data identifies the core issue and preserves any related discussions.
- Topic Details:
- GUID
- Title
- CreationDate
- CreationAuthor
- Comments:
- Comment
- CommentDate
- CommentAuthor
Viewpoint and Component Data
These attributes capture the specific 3D view and the exact model elements involved in the issue.
- BIM Snippet:
- SnippetType
- Reference
- Viewpoint & Snapshot:
- Viewpoint (defines the camera position and settings)
- Snapshot (the saved image file)
- Linked Component:
- IfcGuid (the unique ID for the model element)
Detailed Camera and Snapshot Settings
These attributes define the precise camera orientation used to create the viewpoint.
- Orthogonal Camera:
- CameraViewPoint
- CameraDirection
- CameraUpVector
- ViewToWorldScale
- Perspective Camera:
- CameraViewPoint
- CameraDirection
- CameraUpVector
- FieldOfView
- Bitmap (Snapshot Image):
- Reference
- Location
- Normal
- Up