PRODUCT GUIDE

Toolbox Handbook for ExyViewer and ExyRev

Use this page as a working manual for ExyViewer and ExyRev. Find each tool, understand its required inputs, follow the workflow, and review the expected result before you begin.

The guide covers ExyViewer model review and drawing tools together with supported ExyRev setup, compatibility, licensing, and Revit command workflows.

ExyViewer

ExyViewer is a browser-based workspace for model review, coordination, validation, and technical drawing. Its tools are available through the viewer toolbar, side panels, and drawing module.

This section documents the available viewer controls, including advanced analysis panels and technical drawing tools.

Navigation, Viewing, and Focus

Start here when you need to load a model, move through the scene, or control what stays visible.

Jump to a section

Load IFC or FRAG Navigation Controls Visibility and Focus Controls

Load IFC or FRAG

Purpose

Open a model file into the viewer.

When to use it

Use this at the start of a session or whenever you want to add another model to the current workspace.

Where to find it

Top toolbar: `Load` button. The structure panel can also add another model.

Before you start / main inputs

Accepted formats: `.ifc` and `.frag`.
`.frag` is the preprocessed fast-loading format generated by ExyViewer.

How to use it

1. Click `Load` and choose an IFC or FRAG file.
2. Wait for the viewer canvas and structure tree to populate.
3. If you are working with multiple models, use the structure panel to unload or add more files.

Expected result

The model appears in the scene, becomes available in the structure tree, and its data can be used by the analysis panels.

Notes and limits

A model must be loaded before visibility, markup, IDS, clash, classification, drawing, or reporting tools become useful.
FRAG files are intended for faster repeat opening, not for authoring changes back to IFC.

Best practice

If you review the same large file often, export a FRAG version once and reopen that for later sessions.

Navigation Controls

Purpose

Move around the scene and reset your viewpoint quickly.

When to use it

Use these controls whenever you need to inspect geometry from another angle or recover a lost view.

Where to find it

Top toolbar: `Orbit`, `Pan`, `Zoom All`. Top-right overlay: `ViewCube` and quick view buttons.

Before you start / main inputs

Navigation mode: `Orbit` or `Pan`.
Orientation shortcuts: front, back, left, right, top, bottom, and isometric views from the ViewCube.

How to use it

1. Choose `Orbit` to rotate around the model or `Pan` to shift the camera target.
2. Click `Zoom All` if the model is off-screen or you want to frame everything again.
3. Use the ViewCube to jump to a standard orthographic or isometric direction.

Expected result

The camera updates immediately and the ViewCube stays synchronized with the current orientation.

Notes and limits

Reset also returns the viewer to orbit mode and performs a zoom-all action.
The ViewCube is an orientation helper, not a saved-view manager.

Best practice

Use `Zoom All` before creating reports, screenshots, or BCF issues if you want a clean overall framing.

Visibility and Focus Controls

Purpose

Cut, hide, isolate, restore, and declutter the scene.

When to use it

Use these tools when you need to inspect a dense area, compare only a few elements, or recover the full scene after focused work.

Where to find it

Top toolbar: `Section`, `Hide`, `Isolate`, `Reset`, and `Grid`. Section settings open from the split button chevron.

Before you start / main inputs

Section edge options: show edges, edge color, and edge thickness.
Grid visibility is remembered in local storage between sessions on the same browser.

How to use it

1. Select one or more elements if you want to hide or isolate only those items.
2. Toggle `Section` to enable clipping planes, then adjust edge settings if you need stronger cut-line feedback.
3. Use `Hide` or `Isolate` for focused review, and use `Reset` to clear section planes, restore visibility, close split views, and return to the default navigation state.

Expected result

The scene becomes easier to read and you can focus on a problem area without permanently changing the source model.

Notes and limits

Hide and Isolate require an active selection.
Reset is intentionally broad: it clears sectioning, restores visibility, disables markup mode, closes drawing split views, and zooms back to the full scene.

Best practice

Isolate is faster than repeated hide actions when you already know the exact elements you want to review.

Selection and Inspection

Use these tools to locate elements, inspect shared metadata, and move from model structure to element detail.

Jump to a section

Structure Tree and Properties Panel Markup Overlay

Structure Tree and Properties Panel

Purpose

Browse the IFC hierarchy, select elements, and inspect their metadata.

When to use it

Use this when you need to understand where an element sits in the model, compare multiple selections, or read IFC properties and property sets.

Where to find it

Top toolbar: `Structure` opens the model structure panel. Side panel tab: `Properties`.

Before you start / main inputs

The structure panel can add and unload models.
The properties panel supports searching and multi-selection summaries.

How to use it

1. Open `Structure` to browse the loaded model hierarchy and select an item.
2. Open `Properties` to inspect identity data, IFC information, property sets, materials, layers, and shared values across multi-selection.
3. Use the search field in Properties to narrow long property lists.

Expected result

You can move from spatial structure to exact element metadata without leaving the viewer.

Notes and limits

With multi-selection, only shared properties are shown and differing values are marked explicitly.
The structure tree also lists loaded models and lets you unload them individually.

Best practice

Use the structure tree to get to a known storey or assembly quickly, then switch to Properties for detailed checks.

Markup Overlay

Purpose

Create lightweight review annotations directly over the 3D scene.

When to use it

Use this during coordination or review meetings when you need quick visual notes without opening the full drawing module.

Where to find it

Top toolbar: `Markup`.

Before you start / main inputs

Overlay tools include text, cloud, arrow, and coordinate annotations.
Markup anchors can follow scene geometry through camera updates.

How to use it

1. Toggle `Markup` on from the toolbar.
2. Place notes, clouds, arrows, or coordinates over the area you want to explain.
3. Exit markup mode when finished so regular viewer interactions stay clean.

Expected result

You get fast in-scene visual comments that can also be captured into manual BCF snapshots.

Notes and limits

Markup is separate from the paid technical drawing editor.
The toolbar tracks whether markup is active and whether unsaved overlay changes exist.

Best practice

Capture a BCF snapshot after adding markup if you want the note to travel with an issue package.

Validation, Coordination, and Reporting

These panels support compliance checks, clash review, issue packaging, classification, and exports.

Jump to a section

IDS Validation Clash Detection BCF Issues Classification Drawing Module Report Export ExyGIS

IDS Validation

Purpose

Load an IDS XML file, validate the model against its rules, and turn failures into trackable issues.

When to use it

Use this when you need to confirm that model content matches exchange requirements or office standards.

Where to find it

Side panel tab: `IDS`.

Before you start / main inputs

Input file: IDS XML.
Result filters: `FAIL`, `PASS`, or `ALL`.

How to use it

1. Open the `IDS` tab and load an IDS file.
2. Click `Run Validation` once the model and IDS file are both ready.
3. Filter the grouped results, click a failing element to isolate and zoom it, and create or open the related BCF issue if needed.

Expected result

You get rule-based pass and fail results grouped by specification, plus element-level issue details.

Notes and limits

Validation needs model metadata to be loaded first.
Failing elements can be highlighted in batch or converted into BCF issues for follow-up.

Best practice

Start with the `FAIL` filter so you review only exceptions before checking the wider pass summary.

Clash Detection

Purpose

Run model-to-model or in-model clash checks with a configurable entity matrix and tolerances.

When to use it

Use this for BIM coordination, model auditing, and targeted checks between selected IFC entity types or model pairs.

Where to find it

Side panel tab: `Clashes`.

Before you start / main inputs

Mode: `internal` for one model or `federated` for model-to-model checks.
Clash matrix: enable or disable IFC type pairs.
Tolerances: horizontal, vertical, optional volume tolerance, and minimum reportable volume.
Clash classes: duplicate, inside, and overlapping.
Optional `.clss` import to limit scope using a classification file.

How to use it

1. Choose the clash mode and, if needed, the active model or model pair.
2. Adjust the matrix so only the relevant type combinations stay enabled.
3. Set tolerances and run the clash detection pipeline, then inspect grouped results, isolate clash pairs, or export selected clashes to BCF.

Expected result

You receive grouped clash results with viewer integration, clash metrics, and exportable issue selections.

Notes and limits

A custom imported `.clss` scope can restrict the run and may block detection until the imported file resolves correctly.
The panel supports docking and undocking for longer review sessions.

Best practice

Reduce the matrix first. Smaller, intentional checks are easier to review than one large catch-all run.

BCF Issues

Purpose

Create, edit, import, and export coordination issues with viewpoints, comments, and snapshots.

When to use it

Use this when review findings need to leave the viewer and become shareable coordination tasks.

Where to find it

Side panel tab: `BCF`.

Before you start / main inputs

Issue fields: title, description, priority, status, type, assignee, and due date.
Optional snapshot capture and linked selected elements.
Import and export formats: `.bcfzip` and XLSX.

How to use it

1. Select one or more elements if the issue should stay linked to model components.
2. Capture a snapshot if you want a visual reference, then create the issue.
3. Edit existing issues to add comments, update metadata, restore viewpoints, or export the issue list.

Expected result

You get BCF-style coordination issues that can be reviewed inside ExyViewer or handed off externally.

Notes and limits

Snapshots can combine the model view with the current markup overlay.
Imported BCF packages can be reopened, edited, and exported again from the panel.

Best practice

Use clear assignee and due-date fields when you expect the issue list to become an action register.

Classification

Purpose

Create rule-based classification layers, color the model, calculate metrics, and export scope files or workbooks.

When to use it

Use this when you need a reusable filtered view of the model based on metadata, property sets, property values, or nested classifications.

Where to find it

Side panel tab: `Classification`.

Before you start / main inputs

Classification layers with colors and duplicate support.
Criteria sources: query-based rules or existing classifications.
Query dimensions include IFC type, metadata fields, property-set names, property names, and property values.
Export options include templates, custom headers, chosen columns, formula rows, element rows, XLSX export, and `.clss` scope export.

How to use it

1. Create a classification and add one or more layers.
2. Choose the rule source, define the query or referenced classification, then review the matched candidates and metrics.
3. Apply colors in the viewer, isolate a result if needed, and export either the workbook or the `.clss` scope file.

Expected result

The model can be filtered and color-coded by a repeatable logic set, and the result can be reused in clash scope workflows or downstream reporting.

Notes and limits

Later classifications visually override earlier ones when the same element belongs to more than one layer.
A `.clss` export requires at least one resolved classification with matched elements.

Best practice

Use classification exports when you want the same scope to drive both reporting and clash review.

Drawing Module

Purpose

Generate technical views, place measurements and annotations, and export sheet outputs.

When to use it

Use this when you need review drawings, paper-space style dimensions, or lightweight technical deliverables from the viewer.

Where to find it

Side panel tab: `Drawing`.

Before you start / main inputs

Measurement tools: dimension, angle, slope, tape, and area.
Measurement preferences: colors, units, precision, font size, and text offset.
Technical editor tools: leader, callout, and symbol placement.
View tools: smart views, storey plans, context elevations, capture current view, open split view, and close views.
Export formats: SVG, PDF, PNG, and DXF with toggles for measurements, annotations, and custom drawings.

How to use it

1. Generate a smart view, storey plan, elevation, or capture the current scene.
2. Open a generated view in split mode when you need official technical editor tools such as dimensions, angles, slope tags, leaders, callouts, or symbols.
3. Add annotations or manual drawings, then export the sheet in the format that matches your downstream workflow.

Expected result

You get view-based measurements and annotations tied to a drawing workspace, plus export-ready technical outputs.

Notes and limits

Official technical editor tools only work on generated plan or elevation views opened in the split pane.
Manual SVG markup inside the drawing module is separate from the lighter top-toolbar markup overlay.

Best practice

Use `Smart Views` first. It prefers storey plans for buildings and falls back to context elevations for infrastructure-style models.

Report Export

Purpose

Export validation results, clash results, and BCF issue data in report-friendly formats.

When to use it

Use this after running IDS validation, clash detection, or issue creation when you need files for review, archiving, or handoff.

Where to find it

Side panel tab: `Report`.

Before you start / main inputs

Formats: JSON, CSV, and XLSX.
Include toggles: IDS validation, clash results, and BCF issues depending on available data and selected format.

How to use it

1. Open `Report` after the relevant analysis has been completed.
2. Choose the export format and enable the data blocks you want to include.
3. Run the export and use the generated file names based on the model name and timestamp.

Expected result

You receive machine-readable or spreadsheet-friendly output without re-running the analysis.

Notes and limits

XLSX supports validation and BCF issue export, while clash CSV export stays in the CSV path.
The panel stays disabled until at least one analysis result or issue exists.

Best practice

JSON is best for system-to-system reuse; CSV and XLSX are better for review meetings and manual follow-up.

ExyGIS

Purpose

Place IFC model context and supported 2D geospatial layers on a WGS84 map, inspect coordinates, and export a clipped federated CAD package.

What it does

ExyGIS runs an independent IFC map workspace inside ExyViewer. It loads one or more IFC files progressively, reads IFC georeferencing, renders Map or 3D Terrain views, imports GeoJSON and ASCII DXF into canonical WGS84 vector layers, supports feature and coordinate inspection, and exports GeoJSON or a ZIP CAD package containing ASCII DXF, PRJ, manifest, README, and export-area GeoJSON.

When to use it

Use this when BIM coordination needs a geospatial map context, external GeoJSON or DXF reference layers, coordinate checks, or a clipped 2D CAD handoff. It complements ExyViewer review tools; it is not a general GIS editor or IFC authoring tool.

Where to find it

ExyViewer side panel: `ExyGIS` (Pro access). The panel opens its independent map workspace and exposes IFC loading, GeoJSON/DXF imports, layer controls, coordinate inspection, and federated CAD export.

Before you start / main inputs

`ExyGIS` access and a browser that can run the map and IFC workers.
IFC input: one or more `.ifc` files for BIM context; `.frag` is not accepted by ExyGIS.
GeoJSON input: `.geojson` or `.json`, maximum 50 MB, using WGS84 or a supported declared legacy CRS.
DXF input: ASCII `.dxf`, maximum 50 MB; source units, a supported source CRS, and coordinate confirmation are required.
Exact IFC footprint export requires high-confidence `IfcMapConversion` georeferencing, a supported projected CRS, metre-based target units, and indexed mesh triangles.

How to use it

1. Open ExyViewer and select the `ExyGIS` side-panel tab.
2. Click `Load IFCs`, choose one or more `.ifc` files, and wait for the progressive load. Use `Add IFCs` or the remove controls to manage the loaded set.
3. Review `Georeferencing` for status, method, CRS, anchor, elevation, and warnings. Choose `Map` or `3D Terrain` once geometry and a usable geographic anchor are available.
4. Choose a basemap. Use `Add GeoJSON` for WGS84 or supported declared CRS data, or use `Add DXF`, inspect the file, select source units and CRS, confirm the coordinates, and import it.
5. Use the layer controls to show, hide, reorder, fit, change opacity or role, and export vector layers. Inspect features, read or copy WGS84/projected coordinates, place a temporary marker, or export IFC anchors and bounds.
6. For CAD handoff, draw an export area, select vector layers, eligible IFC footprints, or the marker, choose an enabled target CRS, preview the scope, and click `Export CAD package` to download the ZIP.

Expected result

You get an ExyGIS map or terrain workspace with the loaded IFC context and canonical WGS84 vector layers. Separate GeoJSON actions download `.geojson` files; a successful CAD export downloads a ZIP with the DXF, CRS sidecar, manifest, README, and WGS84 export-area file.

Notes and limits

A basemap or fallback center is map context only; it does not prove that the IFC model is correctly georeferenced.
Exact IFC placement requires a supported CRS and complete linked `IfcMapConversion`. A valid `IfcSite` latitude/longitude can provide a documented fallback anchor, but the placement is approximate; without a safe anchor, Map and 3D Terrain remain unavailable.
GeoJSON without a supported legacy CRS declaration is treated as EPSG:4326. Projected-looking coordinates in that mode are rejected instead of guessed; unsupported CRS declarations are rejected.
DXF import is ASCII model-space only for supported POINT, LINE, LWPOLYLINE, POLYLINE, CIRCLE, ARC, and INSERT entities. Paper space is skipped; curves and bulges are approximated; external-reference blocks, non-default 3D extrusion, local-looking projected coordinates, and oversized conversions are not supported.
CAD export currently enables EPSG:25832 only. EPSG:5683 is disabled pending authoritative transformation control points. CAD XY is absolute projected Easting/Northing in metres, Z is flattened to 0, and no vertical-datum transformation is performed.
An IFC footprint is a derived whole-model maximum-plan projection of indexed mesh triangles, not IFC element or solid semantics. It is available only for eligible high-confidence metre-based IFC georeferencing and within the current footprint-engine triangle guard.

Best practice

Confirm the source units and CRS before importing. A layer that opens on the map is not, by itself, proof that its coordinates are correct.

Related tools and resources

Open ExyViewer IFC Viewer guide Drawing Module

REVIT ADD-IN

ExyRev

ExyRev is a Revit add-in for parameter management, model QA, controlled data exchange, geometry workflows, IFC and IDS preparation, phasing, and georeferencing. The command groups below follow the current ExyRev ribbon.

The setup guidance and 15 current ribbon commands apply to the supported ExyRev editions for Revit 2024, 2025, 2026, and 2027.

Setup, Licensing, and Access

Choose the correct build, activate ExyRev, and use the always-available About command for product, license, update, and EULA information.

Jump to a section

Choose the Correct Revit Edition and License Term Install and Activate ExyRev About Check Compatibility Before Deployment

Choose the Correct Revit Edition and License Term

Purpose

Match the ExyRev installer to the user’s Revit year and purchased license term.

When to use it

Use this before purchase, deployment, or sending an installer to another workstation.

Where to find it

Exynix product selection, checkout details, dashboard downloads, and license email.

Before you start / main inputs

Supported editions: Revit 2024, 2025, 2026, and 2027.
Available license terms: 3 months, 6 months, and 1 year.

How to use it

1. Confirm the exact Revit year installed on the target workstation.
2. Choose the matching ExyRev edition and license term.
3. Download the MSI mapped to that exact combination.

Expected result

The user receives a version-specific installer that matches the purchased entitlement.

Notes and limits

ExyRev does not use one universal binary for every supported Revit release.
An installer for the wrong Revit year will not provide the intended deployment.

Best practice

Treat the Revit year as a hard compatibility requirement.

Related tools and resources

ExyRev downloads

Install and Activate ExyRev

Purpose

Install the matching MSI and validate the delivered license key and hash key.

When to use it

Use this after purchase, with an approved demo package, or when activating another workstation.

Where to find it

Exynix download flow, ExyRev installer, and the ExyRev tab in Revit.

Before you start / main inputs

You need the installer for the installed Revit year.
Activation uses both a license key and a hash key.
Licensed commands remain disabled until validation succeeds; About remains enabled.

How to use it

1. Download the MSI for the target Revit year.
2. Run the installer and enter the delivered activation values when requested.
3. Start Revit and confirm that the `ExyRev` tab appears.
4. If commands remain disabled, open `About` and run the purchase or activation path again.

Expected result

The ExyRev tab loads and licensed ribbon commands become available after validation.

Notes and limits

ExyRev checks stored license information at startup and refreshes ribbon availability.
Use About before reinstalling when the ribbon is visible but its commands are disabled.

Best practice

Keep the activation email available while installing.

Related tools and resources

ExyRev downloads About command

About

Purpose

Show the installed ExyRev version, license state, updates, EULA access, and activation options.

What it does

About loads the stored license type and expiry, checks for available ExyRev updates, opens the current EULA, and provides website, installer, release-note, purchase, and activation actions.

When to use it

Use it when commands are disabled, a license is near expiry, you need the installed version, or you want to check for an update.

Where to find it

ExyRev tab, `Info` panel, `About` button.

Before you start / main inputs

About is the only ribbon command that remains enabled without a valid license.
Update checking and refreshed license information require the relevant service to be reachable.

How to use it

1. Open `About` from the `Info` panel.
2. Review the installed version and license type, status, and expiry.
3. Use `Purchase/Activate License` if access must be restored.
4. Use `Check for updates`, EULA, website, or release-note actions as needed.

Expected result

You can identify the installed build, inspect licensing, restore command access, and reach the current update or legal information.

Notes and limits

About reports status and launches supported actions; it does not install an update while Revit remains open.
Close Revit before running a downloaded ExyRev installer.

Best practice

Check About first when the ExyRev tab is present but other commands are unavailable.

Related tools and resources

ExyRev downloads

Check Compatibility Before Deployment

Purpose

Confirm that the workstation and Revit environment match the supported ExyRev build.

When to use it

Use this before an individual installation or managed rollout.

Where to find it

ExyRev compatibility information, installer selection, and deployment planning.

Before you start / main inputs

Operating system: Windows 10 or 11, 64-bit.
Supported Revit editions: 2024, 2025, 2026, and 2027.
Each Revit release uses its matching ExyRev build.

How to use it

1. Verify the workstation uses a supported 64-bit Windows version.
2. Confirm the installed Revit year.
3. Select the ExyRev build for that Revit year.
4. Complete any organization-specific deployment checks before a wider rollout.

Expected result

The deployment uses the supported operating system and the correct Revit-specific ExyRev package.

Notes and limits

Organization-specific IT prerequisites should be documented separately.
This compatibility guide does not replace testing against a managed workstation image.

Best practice

Validate one representative workstation before batch deployment.

Related tools and resources

ExyRev downloads

Model Data

The current Model Data panel covers geometric parameter assignment, parameter completeness checks, database audits, guarded cleanup, and round-trip model-data enrichment.

Jump to a section

Parameters Paraclean Parameter Checker PaRadar DataForge

Parameters

Purpose

Calculate or set selected shared-parameter values on Revit elements.

What it does

The modeless Geometric Parameter Assignment window reads a Revit shared-parameter text file, filters definitions by group and name, then calculates length, area, volume, or thickness from interactive selections or writes number, Yes/No, text, and multi-line text values.

When to use it

Use it when geometric measurements or controlled input values must be written into shared parameters.

Where to find it

ExyRev tab, `Model Data` panel, `Parameters` button.

Before you start / main inputs

An active Revit document and a shared-parameter `.txt` file are required.
The target parameter must exist on the elements and be writable.
Geometric operations prompt for elements, faces, or edges; press Esc to finish a selection sequence.

How to use it

1. Open `Parameters` and browse to the shared-parameter file.
2. Filter the group and choose the target parameter definition.
3. Click `Run` and follow the geometry prompts, or enter the number, Yes/No, text, or multi-line value requested for that data type.
4. Continue selections as needed, then press Esc and review the completion status.

Expected result

Writable parameters on the processed elements receive the calculated or entered value.

Notes and limits

Unsupported data types fall back to the thickness calculation path; verify the chosen definition before running.
Temporary geometry highlights are cleared when the calculation finishes; the command does not create missing parameter bindings.

Best practice

Test a new shared-parameter definition on a small model scope before processing repeated selections.

Related tools and resources

Parameter Checker Revit automation guide

Paraclean

Purpose

Preview, clear, or remove eligible project and family parameters with protection checks.

What it does

Paraclean scans project parameter bindings or selected families, reports where values exist and why definitions are protected, requires a matching preview snapshot, and then clears values or removes only eligible parameter definitions.

When to use it

Use it during parameter cleanup before template maintenance, family-library cleanup, or model handover.

Where to find it

ExyRev tab, `Model Data` panel, `Paraclean` button.

Before you start / main inputs

A valid ExyRev license and a writable active document are required.
Project scopes are Active View, Current Selection, or Whole Project.
Family cleanup uses the current family document or explicitly discovered and selected project families.

How to use it

1. Choose Project Parameters or Family Parameters and select the scope.
2. Scan, then filter by category, group, kind, or parameter name.
3. Select eligible rows and choose `Clear Values` or `Remove Parameters`.
4. Generate and review the preview, including protected and skipped rows.
5. Execute the operation and review the Result tab.

Expected result

Eligible values are cleared or eligible definitions are removed, with affected, skipped, protected, and failed items reported.

Notes and limits

Removing a project parameter removes its binding across the listed categories; removing a family parameter changes and reloads that family.
A document, selection, filter, operation, or scan change invalidates the preview and requires a new scan or preview.

Best practice

Use Clear Values before Remove Parameters when the binding may still be needed.

Related tools and resources

PaRadar Parameters

Parameter Checker

Purpose

Visualize parameter completeness for elements visible in the active Revit view.

What it does

Parameter Checker reads selected groups and parameter names from a shared-parameter text file, counts filled values per active-view element, applies a red-to-green completeness override, and lists missing parameters for a chosen result row.

When to use it

Use it for a quick parameter QA pass before delivery, data export, or IDS validation.

Where to find it

ExyRev tab, `Model Data` panel, `Parameter Checker` button.

Before you start / main inputs

Open the target Revit view before running the check.
Browse to a shared-parameter `.txt` file and select at least one group and parameter; without a file the current fallback checks Comments and Mark.

How to use it

1. Open `Parameter Checker` and browse to the shared-parameter file.
2. Select the required groups and individual parameters.
3. Click `Run` and review the completeness colors and Filled / Total values.
4. Double-click a result row to select that element and list its missing parameters.
5. Close the window to clear the overrides created by this check.

Expected result

Active-view elements receive temporary completeness colors and the results table identifies missing values by element.

Notes and limits

The check is limited to non-type elements collected from the active view.
Closing the window clears the overrides it tracked; this is not a persistent report export.

Best practice

Use a dedicated QA view so the checked scope is explicit and repeatable.

Related tools and resources

Parameters IDS Spec

PaRadar

Purpose

Audit shared-parameter definitions, usage, and duplicate database instances in the active document.

What it does

PaRadar scans the internal shared-parameter database, tracks parameter IDs and usage, filters by name, GUID, group, data type, status, or duplicates, inspects individual definitions, copies element usage, exports CSV, and can delete confirmed eligible definitions or duplicate instances.

When to use it

Use it when investigating unused definitions, duplicate shared parameters, GUID conflicts, or parameter-database growth.

Where to find it

ExyRev tab, `Model Data` panel, `PaRadar` button.

Before you start / main inputs

An active Revit project or family document is required.
Delete actions change the document and display confirmation prompts; save or back up the model first.

How to use it

1. Open `PaRadar` and run `Scan Parameter Database`.
2. Filter by search text, data type, usage, status, or `Show Duplicates Only`.
3. Use Inspect or Copy Elements to verify a definition and its usage.
4. Export the filtered audit to CSV, or use a confirmed delete action only after review.

Expected result

You receive a filterable parameter inventory and, when chosen, a CSV audit or a confirmed database cleanup result.

Notes and limits

Delete and Delete All are destructive model edits, not reporting actions.
A low usage count is not proof that a parameter is safe to remove; check schedules, tags, formulas, and delivery requirements.

Best practice

Export the CSV before deleting duplicate or unused definitions.

Related tools and resources

Paraclean Parameter Checker

DataForge

Purpose

Export structured Revit data for spreadsheet enrichment, validate the edited file, and apply controlled updates back to the model.

What it does

DataForge builds or loads reusable data structures, exports current selection, active view, category, or active schedule data to XLSX or flat files, preserves round-trip identity mapping, validates imported edits, can create declared missing parameters, applies updates transactionally, manages Revit schedules, and exports a technical report.

When to use it

Use it when model data must be enriched in Excel or another tabular workflow and safely returned to Revit.

Where to find it

ExyRev tab, `Model Data` panel, `DataForge` button.

Before you start / main inputs

A valid license, an active writable document, a chosen Revit source, and at least one data column are required.
Structure inputs support XLSX, TSV, CSV, TXT, and legacy DataForge JSON; enriched imports support XLSX, TSV, CSV, and TXT.
Keep the hidden Excel mapping data or visible flat-file identity columns intact for reliable re-import.

How to use it

1. Load or create a Data Structure, then choose Current Selection, Active View, Category, or Active Schedule.
2. Select and order the enrichment columns and preview the source rows.
3. Export for Enrichment and edit only the intended data values outside Revit.
4. Load the enriched file and run `Validate Updates`.
5. Resolve blocking issues, then choose `Apply to Revit` and optionally create or update a schedule and export the technical report.

Expected result

Matched writable parameters are updated in one controlled transaction, with previews, issues, and apply results available for review.

Notes and limits

New spreadsheet rows do not create Revit elements, and read-only, calculated, combined, or unsupported fields are not writable.
If any parameter update fails during apply, the update transaction is rolled back; edited identity or mapping columns can prevent safe matching.

Best practice

Keep an untouched copy of the exported enrichment workbook and validate every return file before Apply to Revit.

Related tools and resources

Parameters Revit automation guide

Geometry Tools

The current Geometry Tools panel generates rail-aligned mass surfaces and adapts an existing floor slab shape to a Toposolid.

Jump to a section

Mass Surface FloorFromTopo

Mass Surface

Purpose

Generate left and/or right lofted mass surfaces along a rail-axis point file.

What it does

Mass Surface reads whitespace-separated axis coordinates, subtracts a base point, applies side, bottom, height, and inclination offsets, and creates loft forms in the active mass-family document.

When to use it

Use it to create repeatable corridor, rail, or infrastructure side surfaces that can later drive Revit Wall by Face workflows.

Where to find it

ExyRev tab, `Geometry Tools` panel, `Mass Surface` button.

Before you start / main inputs

Open or create a mass-family document before running the tool.
The text file needs at least two valid rows with an identifier followed by invariant-culture X, Y, and Z values.
Set base coordinates, left/right offsets, bottom offset, total height, inclination, and at least one side.

How to use it

1. Open a mass-family document and launch `Mass Surface`.
2. Browse to the rail-axis `.txt` file.
3. Enter the base point and surface offsets, height, and inclination.
4. Choose Left Side, Right Side, or both, then click `Generate`.
5. Review the created loft surfaces before loading the family into a project.

Expected result

The mass family receives the requested left and/or right lofted surfaces along the input axis.

Notes and limits

The tool rejects project documents and input with fewer than two valid points.
Numeric text is parsed with a dot decimal separator; malformed or short rows are skipped.

Best practice

Check axis order and base coordinates on a short sample file before generating a long surface.

Related tools and resources

Computational design guide

FloorFromTopo

Purpose

Reshape an existing floor from dense points sampled from a selected Toposolid.

What it does

The command asks for a Toposolid and an existing floor, resets the floor slab shape, samples points along Toposolid edges, keeps points inside the floor boundary, and draws them into the slab shape editor.

When to use it

Use it when an existing site floor must follow terrain geometry more closely than a flat slab.

Where to find it

ExyRev tab, `Geometry Tools` panel, `FloorFromTopo` button.

Before you start / main inputs

A writable project with one Toposolid and one floor that supports slab-shape editing is required.
The command uses the floor’s upper face and line-based boundary segments.

How to use it

1. Open `FloorFromTopo`.
2. Select the source Toposolid when prompted.
3. Select the existing floor to modify.
4. Wait for the slab-shape points to be rebuilt and review the reported point count.
5. Inspect the modified floor against the terrain before continuing.

Expected result

The selected floor’s slab shape is reset and rebuilt with topo-derived points inside its boundary.

Notes and limits

The command modifies the selected floor; it does not create a separate replacement floor.
Existing slab-shape edits are reset, and curved boundary segments are not converted into the polygon used for the inside test.

Best practice

Duplicate or back up the target floor before applying the workflow to production geometry.

Related tools and resources

Revit automation guide

OpenBIM Workflows

The current OpenBIM Workflows panel prepares IFC entity, property, and quantity mappings; edits and checks IDS; builds PH4D views; and validates IFC georeferencing.

Jump to a section

IFCmap Pset_map Qto_map IDS Spec IDS_Map PH4D BIMGeoRef

IFCmap

Purpose

Assign an IFC export entity and predefined type to eligible elements in the active view.

What it does

IFCmap loads a selectable IFC schema tree, filters entities by search, previews elements already matching the chosen mapping, and writes the entity and predefined type to every eligible instance in the active view or to their element types.

When to use it

Use it before IFC export and before Pset_map, Qto_map, or IDS_Map when export classifications must be explicit.

Where to find it

ExyRev tab, `OpenBIM Workflows` panel, `IFCmap` button.

Before you start / main inputs

A valid license, writable document, active view, and visible eligible elements are required for mapping.
Choose the IFC schema, entity, optional predefined type, and whether to apply to instances or types.

How to use it

1. Filter the target elements in the active Revit view and open `IFCmap`.
2. Choose the IFC schema and search or browse for the target entity.
3. Choose a predefined type where applicable and use `Preview` to inspect current matches.
4. Select `Apply to Instances` or `Apply to Types` and review the completion message.

Expected result

Eligible active-view elements or their types receive the selected IFC export mapping.

Notes and limits

Apply operates on the eligible active-view scope, not only the current Revit selection; type mapping affects all instances of those types.
The visible Export JSON control is disabled because mapping export is not implemented.

Best practice

Use a tightly filtered working view and prefer instance mapping unless the whole type should share the classification.

Related tools and resources

Pset_map Qto_map IFC model checker

Pset_map

Purpose

Validate and attach standard IFC property sets for mapped elements in the active view.

What it does

Pset_map scans the active view against the selected schema, reports missing, wrongly attached, mandatory, empty, and deterministically populatable properties, attaches missing Psets, fills supported deterministic values, and exports CSV or JSON results.

When to use it

Use it after IFCmap and before IFC delivery or IDS checking when standard property-set coverage must be reviewed.

Where to find it

ExyRev tab, `OpenBIM Workflows` panel, `Pset_map` button.

Before you start / main inputs

A writable document and an active view containing elements with IFC entity mappings are required.
Choose the target IFC schema and run Preview before attach or populate actions.

How to use it

1. Prepare an active view and confirm IFC entity assignments with `IFCmap`.
2. Open `Pset_map`, choose the schema, and click `Preview`.
3. Review missing, wrong, mandatory, empty, and auto-populatable counts.
4. Attach missing Psets and populate supported deterministic values as required.
5. Run Preview again and export CSV or JSON if a review record is needed.

Expected result

Eligible active-view elements receive missing standard Pset parameters and supported deterministic values, with a refreshed validation summary.

Notes and limits

Population is limited to values the implementation can determine, including Reference, Status, IsExternal, and LoadBearing; other values still require project intent.
An empty active view cancels the command, and incorrect IFC entity assignments can produce irrelevant Pset expectations.

Best practice

Treat Preview as the gate before every write action.

Related tools and resources

IFCmap IDS Spec

Qto_map

Purpose

Validate and attach standard IFC quantity sets and populate geometry-derived quantities in the active view.

What it does

Qto_map scans mapped active-view elements against the selected schema, reports missing and wrongly attached Qtos and population readiness, attaches missing quantity sets, fills deterministic length, area, or volume values where supported, and exports CSV or JSON.

When to use it

Use it before IFC quantity exchange or measurement QA when mapped elements need standard Qto coverage.

Where to find it

ExyRev tab, `OpenBIM Workflows` panel, `Qto_map` button.

Before you start / main inputs

A writable document, active view with visible elements, and prior IFC entity mapping are required.
Choose the IFC schema and run Preview before attaching or populating quantities.

How to use it

1. Prepare the active view and verify entity assignments in `IFCmap`.
2. Open `Qto_map`, choose the schema, and click `Preview`.
3. Review missing, wrong, mandatory, empty, and population-readiness results.
4. Attach missing Qtos and populate deterministic quantities where appropriate.
5. Preview again and export CSV or JSON if needed.

Expected result

Eligible elements receive standard Qto parameters and supported geometry-derived values, with an updated readiness report.

Notes and limits

Only deterministic geometry-derived quantities are populated; quantities that need modeling or measurement intent remain unresolved.
Results are view-scoped and depend on correct IFC entity and predefined-type mappings.

Best practice

Review units and a sample of calculated quantities before using the export downstream.

Related tools and resources

IFCmap Pset_map

IDS Spec

Purpose

Create, edit, load, validate, and save IDS specifications inside Revit.

What it does

IDS Spec manages IDS documents and property requirements, lets users choose active specifications, validates the model or active view, optionally highlights pass and fail results, supports element selection from results, and exports validation data to CSV or JSON.

When to use it

Use it when authoring information requirements or checking Revit elements against an IDS before exchange.

Where to find it

ExyRev tab, `OpenBIM Workflows` panel, `IDS Spec` button.

Before you start / main inputs

A valid license and active Revit document are required; a loaded IDS file is needed unless you create a new document.
Choose whole-model or active-view scope and whether to apply result highlights.

How to use it

1. Open `IDS Spec` and load an IDS file or create a new IDS document.
2. Review or edit specifications, applicability, and property requirements.
3. Choose active-view scope if the check should be limited.
4. Click `Check Model` and inspect pass, fail, and message details.
5. Clear highlights, save the IDS, or export CSV/JSON results as required.

Expected result

You obtain an editable IDS document and element-level validation results for the selected Revit scope.

Notes and limits

Validation reports implementation results; it does not certify project or regulatory compliance.
View highlights are graphical overrides and should be cleared when the review is complete.

Best practice

Start with active-view scope while testing a new specification, then expand after the rules are verified.

Related tools and resources

IDS_Map IDS workflow article IFC model checker

IDS_Map

Purpose

Find wrong, empty, or missing IDS values in the active view and write supported required values.

What it does

IDS_Map loads an IDS file, matches active-view elements by IFC entity and predefined type, evaluates property and attribute requirements, filters rows by specification and status, applies exact or enumerated values to selected writable parameters, and exports a CSV report.

When to use it

Use it after IDS review when supported model values should be corrected rather than only reported.

Where to find it

ExyRev tab, `OpenBIM Workflows` panel, `IDS_Map` button.

Before you start / main inputs

A writable document, active view, IDS file, and correct IFC entity mappings are required.
Only requirements with a specific value or enumeration are auto-settable; the target parameter must exist and be writable.

How to use it

1. Prepare a focused active view and open `IDS_Map`.
2. Load the IDS file and click `Scan View`.
3. Filter by specification or status and review current versus required values.
4. Select only ready rows, choose an allowed value where required, and click `Apply - Set Values`.
5. Scan again and export the CSV report if needed.

Expected result

Supported selected values are written to matched elements and the rescan shows the remaining OK, Empty, Wrong, or Missing rows.

Notes and limits

Missing or read-only parameters cannot be set, and open-ended patterns, ranges, or requirements without a concrete allowed value require manual resolution.
The command writes model data; verify the active-view scope and selected rows before applying.

Best practice

Use IDS Spec to validate the rule set first, then use IDS_Map on a controlled correction view.

Related tools and resources

IDS Spec IFCmap IDS workflow article

PH4D

Purpose

Create and play construction-phase views from prepared phase numbers or schedule dates.

What it does

PH4D detects and maps phase-role or schedule-date parameters, scans the model, creates filters, templates, and duplicated phase views from a base view or sheet, stores schedule visibility and dates, and plays the generated views without changing the active working view.

When to use it

Use it to organize and present a construction sequence based on model parameters or imported schedule data.

Where to find it

ExyRev tab, `OpenBIM Workflows` panel, `PH4D` button.

Before you start / main inputs

A writable document and active view are required.
Choose Phase numbers or Schedule dates and map the numeric phase roles or activity/date parameters used by the model.
A base view, or a sheet containing placed views, is required when creating phase views.

How to use it

1. Open `PH4D`, choose the timeline source, and review the detected parameter-role mapping.
2. Map and save the phase-number or schedule-date parameters.
3. Scan the model and review phases, invalid rows, and group summaries.
4. Define the phase name, base view or sheet, filters, values, and colors, then click `Apply Phase`.
5. Set schedule dates and visibility, save them, and open Phase View Playback.

Expected result

Revit receives generated phase views, filters, templates, and stored schedule data that can be played as a construction sequence.

Notes and limits

PH4D reads prepared parameter values; parameter assignment is disabled and the command does not write phase values to elements.
Playback uses generated phase views and does not apply temporary overrides to the active working view.

Best practice

Resolve unmapped or invalid schedule rows before generating the final phase views.

Related tools and resources

DataForge Parameters

BIMGeoRef

Purpose

Validate, edit, transform, and export IFC georeferencing data up to LoGeoRef 50.

What it does

BIMGeoRef loads an IFC file, reports LoGeoRef 30, 40, and 50 checks, exposes site placement, IfcMapConversion, and IfcProjectedCRS data, applies edits, transforms coordinates to another EPSG CRS, saves a corrected IFC, and exports LOG, JSON, or Revit IFC configuration output.

When to use it

Use it before IFC delivery when site placement, projected CRS metadata, map conversion, rotation, scale, or GIS alignment must be checked.

Where to find it

ExyRev tab, `OpenBIM Workflows` panel, `BIMGeoRef` button.

Before you start / main inputs

Load an IFC file and know the intended coordinate reference system before editing or transforming coordinates.
Editable data includes EPSG metadata, eastings, northings, orthogonal height, axis values, and scale where supported by the schema.

How to use it

1. Open `BIMGeoRef`, click `Load IFC`, and select the exchange file.
2. Click `Validate` and review the LoGeoRef level, failed rules, and entity chain.
3. Edit the supported site, map-conversion, or CRS values, or use `Transform CRS` when a target EPSG is required.
4. Apply changes with `GeoRefUdt` and validate again.
5. Save the corrected IFC and export LOG, JSON, or Revit Config output as needed.

Expected result

You obtain a corrected IFC and/or a traceable georeferencing report or configuration export for the reviewed coordinate data.

Notes and limits

IFC2x3 is limited to site-placement LoGeoRef 30; IfcMapConversion and IfcProjectedCRS for LoGeoRef 40/50 require IFC4.
The tool edits IFC exchange metadata; it is not a general editor for native Revit project coordinates and does not certify geospatial correctness.

Best practice

Confirm the EPSG code and expected coordinates with the project geospatial authority before saving changes.

Related tools and resources

IFC model checker IFCmap

Visual references

Command names and interface locations are described in each workflow so you can find the corresponding controls in the product.

Need help choosing the right tool?

Use this handbook to self-serve first, then contact the team if you need a walkthrough, a demo, or help matching the right product to your workflow.

Request a Demo Open documentation

Toolbox Handbook for ExyViewer and ExyRev

Use this page as a working manual for ExyViewer and ExyRev. Find each tool, understand its required inputs, follow the workflow, and review the expected result before you begin.

The guide covers ExyViewer model review and drawing tools together with supported ExyRev setup, compatibility, licensing, and Revit command workflows.

ExyViewer

ExyViewer is a browser-based workspace for model review, coordination, validation, and technical drawing. Its tools are available through the viewer toolbar, side panels, and drawing module.

This section documents the available viewer controls, including advanced analysis panels and technical drawing tools.

ExyRev

The setup guidance and 15 current ribbon commands apply to the supported ExyRev editions for Revit 2024, 2025, 2026, and 2027.