Resource search

Search DataDrivenAEC

Open the full search page →

BCFier

Open-source BCF (Building Collaboration Format) client for BIM coordination

Extensible, open-source client for creating, viewing, and sharing building coordination issues. Provides Revit and Navisworks plugins to create issues from 3D/2D views with comments and attachments, enabling interoperable coordination across different BIM platforms via standard BCF files (.bcfzip).

Bootstrapped (open source) raisedEarly StageOpen Source (GNU General Public License v3.0 (extended for Revit compatibility))
Founded 2016 · Not publicly specified; community-driven; no commercial customer database maintained
Website →← All Tools

Why This Tool Exists

The Problem

BIM teams across multiple disciplines (architecture, engineering, construction) struggle to coordinate design clashes and quality issues when using different BIM software. Proprietary coordination tools create vendor lock-in; teams lack a standard, open-source mechanism to exchange issues across Revit, Navisworks, and other BCF-enabled applications.

The Solution

BCFier is an open-source, modular BCF client that provides native plugins for Revit and Navisworks to create building coordination issues directly from 3D and 2D views, attach comments, and share them as standard BCF files (.bcfzip). This enables vendor-independent, interoperable coordination across any BCF-enabled platform without proprietary licensing.

How You Use It

Delivery Method
Desktop ApplicationRevit PluginNavisworks PluginStandalone Viewer
Integrations
Autodesk RevitAutodesk NavisworksBCF-enabled applications (BIM 360, Solibri, etc.)
Project Phases
Design Development, Construction Documentation, Construction Administration
Project Types
Commercial, Residential, Infrastructure, Mixed-Use, Industrial, Healthcare

Data Transparency

Exactly what this tool uses and how

Input
What it needs
Required:BCF file (.bcfzip), BIM model (Revit or Navisworks)
Optional:Previous BCF issues, Coordination comments, Markups, Screenshots
Formats:BCF 1.0, BCF 2.0, RVT (Revit), NWD/NWC (Navisworks)
Output
What you get
Format:BCF files with coordinated issue data and metadata
Fields:Issue title and description, Associated 3D/2D view snapshots (PNG), Coordinated element references (IFC GUIDs), Comments and discussion threads, Priority and status, Assigned to user, Attachment files
Algorithm
How it works
Model:Not applicable - coordination platform with no AI/ML
Accuracy:Not applicable
Privacy
How your data is protected
Retention:Client-side storage; no cloud backend; files stored locally on user machine
Training:Not applicable (open source, no machine learning)
Compliance:No compliance certifications (open source community project)
API
Integration
Endpoint:Not applicable (file-based exchange; no REST API)
Method:File-based BCF (.bcfzip) exchange

Use Cases

  • ·Create and track building coordination issues in Revit without third-party services
  • ·Exchange coordination data between Revit and Navisworks teams
  • ·Share BCF issues across different BIM platforms with standards-based interoperability
  • ·Standalone review of coordination issues for stakeholders without BIM software licenses
  • ·Manage design clashes and quality issues on multi-discipline projects
  • ·Track and resolve coordination items throughout construction administration

Pricing

Free
Free (open source)
Pro
Not applicable (open source software)
Enterprise
Not applicable (open source software)
Sources & Research NotesResearch date: 2026-04-03
Fields Checked (18)
problem, solution, deliveryMethod, integrations, disciplines, projectPhases, projectTypes, isOpenSource, license, maturityStage, yearFounded, input-formats, output-structure, input-required, output-fields, control-features, useCases, pricing-free
Not Found (9)
customerBase-specific-numbers, funding-total-specific, website-active-bcfier-com, api-documentation, privacy-policy, soc2-compliance, iso27001-certification, algorithm-accuracy-metrics, data-retention-policy
About this research: This record summarizes the cited sources and fields checked. A research date does not establish hands-on testing. Consult the original sources for current details and limitations.