When BIM data is finally intended to be operationally usable in facility management, choosing the right BIM viewer often turns out to be the first critical point of failure. To get straight to the point: A BIM viewer in FM is not a toy for high-gloss renderings from the planning department. It is the merciless tool that translates BIM geometries into usable CAFM data – or fails to do so. In this post, I will show you a compact, reproducible test matrix. You will learn how to systematically uncover performance, metadata quality, and integration capabilities before you purchase expensive licenses or rely on marketing formats.
Why the Viewer Decides Your FM Processes
The core message is simple: Whether your BIM viewer can cast photorealistic shadows is, for building operations completely irrelevant. The truth lies in data integrity. The viewer is the bottleneck between planning (IFC or Revit) and operations. It shows you whether the planner has done their homework before the data is poured into the CAFM system unchecked. What truly matters to us in FM can be reduced to three hard criteria:
- Uncompromising Metadata Display: Are Pset_Space, Pset_Asset and your custom fields reliably read, or does the viewer hide them behind proprietary filters?
- Export Determinism: Usable REST APIs, clean CSV or COBie exports for handover to CAFM.
- Offline Capability: Functional caching on the tablet for maintenance inspections deep in the third basement level. With lots of concrete and steel.
The vendors don't make it easy for us. Many software users tune their cloud viewers for maximum 3D performance with 100,000 components, but sacrifice API integrity for it. Field names are suddenly rewritten during export, or room numbers are forgotten. Anyone who blindly trusts marketing-driven exchange formats like the historically narrow CAFM Connect will quickly have a rude awakening when importing into Planon, RIB FM, or pit.
The Audit Matrix: 12 Points for the Reality Check
The following matrix makes the evaluation of a BIM viewer reproducible. Say goodbye to mere feature lists and measure actual behavior. Rate each point strictly from 0 (unusable) to 3 (fully functional). A viewer that runs visually extremely smoothly but messes up the UUIDs of the assets during CSV export will mercilessly fail in the FM environment.
| Test point | What is really tested | The hard FM minimum requirement |
|---|---|---|
| Format & Interoperability | Readability of IFC2x3, IFC4, RVT, and BCF | IFC4 (specifically IFC 4.3) fully readable, BCF import/export mandatory |
| Property Sets (Psets) | Targeted search for Pset_Space & Pset_Asset | Over 90% of sample Psets are correctly displayable and exportable |
| Dimensional Accuracy | Remeasuring three representative rooms | Maximum 2% deviation from planning data (or more, if you think so) |
| Export & API Stability | Quality of CSV/COBie export, REST APIs | CSV export with deterministic field names, documented REST API |
| Mobile & Offline | Offline cache, synchronize markup on tablet | Complete offline view & error-free markup sync after re-connect |
| Security & Roles | TLS, data access log, AD integration | Strict role-based access control (e.g., Azure AD) |
The practical example: In a large handover project, the FM team filtered the room numbers in a well-known cloud viewer. Visually, everything looked good. However, during the CSV export for the CAFM, the viewer placed the numbers in a completely different column field. It wasn't exactly sexy...
The One-Day Stress Test: Find Blockers Before You Sign
You don't have weeks for an academic evaluation. You need certainty. Perform this quick test with a real IFC file to immediately uncover integration blockers.
- Loading and Visibility Check: Load the model and note the time until interactive use. Are all IFC geometries present? Are MEP layers missing?
- The hard Pset check: Search specifically for Pset_Asset and check if custom fields have been retained.
- Search and BCF export: Create an issue (aka "defect"), export it as BCF or CSV, and re-import it. Does the viewer corrupt the IDs? If yes: This can go.
- The offline test: Deactivate Wi-Fi on the tablet, open the model, record a defect, activate Wi-Fi. If the sync fails now, the app is usable for basement operations. Not.
Automation: Benchmarks for Data Integrity
A manual click test is not enough for final acceptance. Those who automate CAFM workflows must also measure viewer quality automatically. Use tools like IfcOpenShell to extract a clean baseline of your IFC file. Let a Python script query the viewer's API and compare the JSON or CSV export byte by byte with the baseline (Whaaaat? You can't do that? Ask your trusted IT person.).
The bitter realization in many projects: Viewers with the fastest cloud streaming often fail miserably when it comes to deterministic mapping of field names. Rely on pull patterns or webhooks, but don't trust never a direct import without a minimal ETL (Extract, Transform, Load) script acting as a firewall in between.
The Short Comparison: What the Market (Really) Offers
Forget the all-in-one solution. Choose your poison wisely instead:
- Solibri: The dominant player for formal model checks and hard Pset validation. Not suitable for mobile inspections, but unbeatable in quality assurance.
- Trimble Connect: Cloud streaming at its finest. Runs extremely smoothly, but you must check the CSV export very carefully for lost attributes (like maintenance intervals).
- Dalux: Mobile-first, great for the construction site and maintenance. Unfortunately, the software reaches its limits when it comes to hard attribute validation via APIs.
And one more thing: Write never "We would like something like IFC support..." in your tender. Demand proof from the provider. proofThe provider must process your provided problem IFC and deliver an exported CSV to you within 48 hours, exactly according to Your the CAFM template. If they don't deliver, they're out. It's that simple.
