Skip to main content

Solibri Webchecker (Beta)

  • Updated

Notice

All Solibri WebChecker features are exclusively available in Solibri Advanced and Premium

Solibri Webchecker is a cloud-based validation service for checking your BIM models with Solibri rulesets. This guide explains availability, access, detailed workflows, and how to work with results so you can use Webchecker end to end.

Note

Webchecker is currently released as Beta and may change over time. Performance and feature set are still being optimized, and you can send feedback directly from within the product.

1. Availability and Regions

2. Access and Permissions

3. Quota Model

4. Supported Models and Files

5. Creating and Managing Projects

6. Project Settings and BCF Version

7. Default Model Health Check

8. Using Custom Rulesets

9. Viewing Checking Results

10. Exporting and Retaining Results

11. Working with Results in Solibri Desktop

12. Known Limitations (Beta)

13. Providing Feedback

14. Typical Use Scenarios

15. Summary

1. Availability and Regions

1.1 Beta status

  • Webchecker is available as a production service with a Beta label.

  • Features, performance, and supported rulesets may change as the service evolves.

    Solibri_Web_Checker_Beta.png

1.2 Service regions

Webchecker is available in two regions:

  • EU: https://webchecker.solibri.com

  • US: https://us.webchecker.solibri.com

2. Access and Permissions

  • Webchecker is accessed with the same Solibri ID you use for other Solibri cloud services.

  • Organization-level administrators manage access and subscriptions through your Solibri account (for example, assigning Advanced or Premium tiers).

  • The available features in Webchecker (e.g. custom rulesets, SMC download) depend on your subscription tier:

    • Advanced: Ability to consume quota and, where enabled, run some custom rulesets.

    • Premium: Full Webchecker capabilities, including custom rulesets and SMC download.

      Capabilities.png

3. Quota Model

Webchecker usage is controlled by an annual quota that is shared across your organization.

  • Quota is assigned per organization for the full year.

  • Each check you run consumes from this shared quota.

  • Subscriptions contribute to quota:

    • Each Premium subscription adds 150 check units to the yearly quota.

    • Each Advanced subscription adds 25 check units to the yearly quota.

  • If you run out of quota, you cannot start new checks until:

    • Additional quota is assigned, or

    • The organization’s subscription is updated for the next quota period.

You can view remaining quota in the Webchecker UI (quota indicator in the main view). Use this to plan which models and milestones to check in the cloud.

4. Supported Models and Files

4.1 Model types and size

  • Webchecker currently validates IFC models.

  • You can upload one or more IFC files to a check.

  • Each individual model can be up to 5 GB in size.

  • Larger IFC files may lead to longer processing times.

  • If the upload fails, verify that the file size is under 5 GB and that the IFC is valid.

4.2 Ruleset files

  • Webchecker uses Solibri rulesets (.cset).

  • For the default Model Health check, the ruleset is provided and updated by Solibri.

  • For custom checks (Advanced/Premium tiers), you can upload your own .cset created in Solibri Desktop (see section 7).

    Upload_Image.png

5. Creating and Managing Projects

5.1 Creating a new project

  1. Open Webchecker in your browser in the desired region or via Solibri Center (Products and Services)

  2. Click New project.

  3. Enter a Project Name.

  4. Click Add files and select your IFC file(s) from your computer.

  5. Confirm the upload.

  6. Click Continue to create the project.

You will see the project overview page: project name, list of model files, and a section for Checks (system checks and custom checks).

Drag_and_Drop_upload.png

5.2 Updating model files

  • To replace or update an IFC file, click Update next to the model file and upload a new version.

  • Use versioning in your file names (for example, Project_Arch_V3.ifc) to keep track of which design revision was checked.

Model_Files.png

5.3 Deleting model files or projects

  • To remove a model from a project, click the trash icon next to the file.

  • To archive or stop using a project, simply stop starting new checks; stored results are automatically removed after the retention period (see section 10).

Deleting_Models.png

6. Project Settings and BCF Version

You can configure how issue data is exported from Webchecker using the Project Settings.

6.1 Opening Project Settings

  • Open your project.

  • Click the gear icon or Project settings.

  • The BCF Version dropdown appears.

6.2 Selecting the BCF version

  • Supported BCF versions:

    • BCF 1.0

    • BCF 2.0

    • BCF 2.1

    • BCF 3.0

  1. Open the BCF Version dropdown.

  2. Select the version your CDE or issue-management platform supports.

  3. Click Update to save the setting.

This setting controls the version used for all BCF exports for that project.

BCF_Version.png

7. Default Model Health Check

Webchecker provides a predefined Model Health ruleset. This is the quickest way to get a first quality assessment for your models.

7.1 What the Model Health ruleset checks

The Model Health ruleset focuses on:

  • Model structure and entities

    • Checks that components use appropriate IFC entities instead of generic IfcBuildingElementProxy.

    • Validates that required building elements and spaces exist.

  • Naming and identification

    • Checks that components have names and identifiers so elements can be clearly understood and cross‑referenced.

  • Key information properties (IDS-based checks)

    • Uses IDS rules to verify that important properties exist on components and spaces, such as:

      • Fire rating.

      • Whether a component is a fire exit.

      • IsExternal (yes/no) and similar basic classification flags.

  • Hard clashes

    • Identifies geometric clashes using a Clash Detection Matrix.

    • Reports:

      • Clashes between different disciplines (e.g. Structure vs Architecture).

      • Clashes within a discipline (e.g. Architecture vs Architecture).

      • The specific components involved.

  • Specialized teasers (example)

    • Some model health sets may include teaser checks such as recirculation checks (for example, whether air recirculation is present in certain rooms).

      Model_Health_and_Cons_and_info.png

7.2 Running the Model Health check

  1. Open the project that contains your model.

  2. Under System Checks, locate Model Health.

  3. Click Start to run the check.

  4. The check is queued and executed in the cloud. Processing time depends on:

    • Model size.

    • Number of rules in the ruleset.

    • Current system load.

Once checking is complete, the status changes and you can open the results.

8. Using Custom Rulesets

Users with Advancedor Premium subscriptions can upload and run custom rulesets (.cset) from Solibri Desktop.

8.1 Supported Rules for uploading as custom checks

The following rule templates are supported in Webchecker (as long as they are included in the uploaded .cset):

If your ruleset contains other templates, Webchecker may ignore those rules or fail to run the ruleset

8.2 Preparing a .cset for Webchecker

  1. Open Solibri Desktop.

  2. Configure your ruleset:

    • Add only supported templates (see list above).

    • Configure any IDS-based rules and attach the corresponding IDS file(s).

    • For clash detection, define the Clash Detection Matrix and save it inside the ruleset.

  3. Save the ruleset as .cset.

  4. Make sure:

    • The IDS file is included in the .cset or available as required.

    • The clash matrix is stored with the ruleset (so Webchecker can execute it).

8.3 Uploading a custom ruleset

  1. Open your project in Webchecker.

  2. In the Custom Checks section, click Add check.

  3. Select Upload ruleset and browse to your .cset.

  4. Give the check a name (for example “Accessibility – Level 3”).

  5. Confirm to upload.

The custom check appears under Custom Checks and can be started in the same way as the Model Health check.

8.4 Running a custom check

  1. Go to the Custom Checks section.

  2. Click Start next to the custom ruleset.

  3. Wait for the processing to complete.

  4. Open the result to review rule-level and issue-level findings.

9. Viewing Checking Results

When a check is completed, click the check entry to open the Results view.

Checking_Results.png

9.1 Rules and rule status

  • On the left side, you see the rule hierarchy:

    • Chapters and groups (for example, “Chapter 5 – Sanitary Provision”).

    • Individual rules (for example, “Accessible Individual Washroom Internal Dimension”).

  • Icons indicate the status for each rule:

    • Passed.

    • Failed.

    • Not relevant / not checked.

You can filter results to only show failed rules to focus on issues.

Filtering_Results.png

9.2 Issue list and details

When you select a failed rule, the result view shows both a rule summary and the related issue cards.

At the top of the results panel, Webchecker shows:

  • Rule – the name of the selected rule, for example “Inside - Components inside of other components”

  • Description – a short explanation of what the rule checks, for example whether components are unintentionally located inside other components such as walls inside walls or slabs inside slabs.

  • Status – whether the rule passed or failed.

  • Components – how many components were checked and how many failed.

  • Issues – the total number of detected issues for the selected rule.

Below the summary, each issue card shows the affected objects in more detail. Depending on the rule, an issue card can include:

  • The issue title, describing the two components or locations involved.

  • A message with measured values or comparison details, such as depth, width, height, and volume of an intersection.

  • A preview image that helps identify the issue location.

  • Additional component details used to understand which objects are affected.

This means users can first understand the overall scale of the problem from the summary, and then inspect each individual issue one by one.

9.3 3D visualization

  • Each issue card includes a small 3D preview of the location.

  • You can open the 3D view to better understand the problem area.

10. Exporting and Retaining Results

10.1 Retention period

  • Each check result is stored for 30 days.

  • This applies to:

    • The interactive issue view.

    • All exported report formats (PDF, BCF, SMC).

  • After 30 days, the result and its reports are removed and cannot be restored.

10.2 Downloading reports

At the top-right of the results view, use the Download menu:

  • PDF report

    • Generates a printable summary of the check.

    • Typically includes rule statistics and issue lists.

  • BCF file

    • Exports issues as BCF using the project’s selected BCF version.

    • Use this file in:

      • CDEs.

      • Issue management systems.

      • Other BIM tools supporting BCF.

  • SMC file

    • (Premium users only.)

    • Creates a .smc that you can open in Solibri Desktop. Lets you continue investigation, use familiar Solibri workflows, or combine Webchecker results with additional local checks.

From the project or check detail:

  1. Click Download.

  2. Choose PDF report, BCF file, or SMC file.

  3. Save the file locally or directly to your project environment.

11. Working with Results in Solibri Desktop

Premium users can open Webchecker results in Solibri Desktop:

  1. Download the SMC file from the results.

  2. Open Solibri Desktop

  3. Use File → Open and select the downloaded .smc.

  4. Review issues in the Checking layout:

    • Navigate rules and issues.

    • Use classification, ITOs, and other Solibri tools.

    • Update and re-check locally if needed.

You can then decide whether to:

  • Fix the model in the authoring tool.

  • Use the local Solibri environment for more advanced analysis linked to the same ruleset.

12. Known Limitations (Beta)

  • Snapshot images in issue cards and PDF/BCF/SMC exports may not always be generated correctly.

  • Performance (processing time) can vary depending on:

    • Model size.

    • Current load on the cloud service.

  • Some Solibri Desktop rule templates are not yet supported in Webchecker; unsupported rules are ignored or may cause the ruleset to fail.

If you encounter issues:

  • Check that:

    • The IFC files are valid and under 1 GB each.

    • Your .cset contains only supported templates.

    • IDS and clash matrix data are correctly stored in the .cset.

  • If the problem persists, use the in‑product feedback channel (see below).

13. Providing Feedback

Because Webchecker is in Beta, user feedback is very important.

  • A dedicated feedback feature is available directly in the Webchecker UI.

  • Use it to:

    • Report bugs or performance issues.

    • Suggest new features or additional rule templates.

    • Comment on usability and workflows.

When sending feedback:

  • Include:

    • Project name and check ID (if available).

    • Short description of the issue or suggestion.

    • Browser, region (EU/US), and approximate time of the check.

This helps the Solibri team analyze and improve Webchecker more quickly.

14. Typical Use Scenarios

14.1 Quick model health assessment

  • Designers upload architecture IFCs to Webchecker early in the design phase.

  • Run the Model Health check to:

    • Detect missing IDs and names.

    • Ensure key information such as fire ratings and IsExternal are present.

    • Get an overview of geometric clashes between disciplines.

14.2 Sharing checks inside an organization

  • BIM managers create a standardized .cset (for example, project-specific accessibility rules).

  • The .cset is uploaded to Webchecker so:

    • All project participants can run the same check, if uploaded to their environment

    • Results are comparable across teams and design phases.

14.3 Cloud pre-check before full Solibri workflow

  • Company use Webchecker to quickly get an overview about the quality of the models.

  • Only models with significant issues or at key milestones are downloaded as SMC and opened in Solibri Desktop for deeper analysis.

15. Summary

Solibri Webchecker brings Solibri’s rules-based checking engine into a cloud service, enabling:

  • Upload of IFC models (up to 5 GB each).

  • Running predefined Model Health or custom project rules.

  • Viewing issues in a browser and exporting them as PDF, BCF, or SMC.

  • Leveraging Advanced/Premium tiers for powerful custom checks and integration with Solibri Desktop.

Use the steps and recommendations in this guide to configure projects, select BCF versions, prepare rulesets, and interpret results efficiently in your day‑to‑day workflows.