◆Recommended workflow

Open Parambulator from the Revit ribbon while a model is active. No active model, no parameter party.

Review the selected packs, affected Revit categories, instance/type binding choices, values, inferred IFC entities, skipped unsupported rows, ignored parameters, and optional parameter prefix before accepting. Parambulator shows the map before it starts drawing roads.

If preflight reports issues, open the Parambulance to filter findings, select one or more matching rows, and repair fixable schema problems before Apply.

Choose the apply target: current project, selected elements, selected project file, or selected family file. Then choose Add, Update, Remove, Update value, or No-Op. Remove shows a final warning after Apply with a chance to cancel.

Enable Also export IFC mapping and IDS XML when you want the same accepted parameter set captured as Revit IFC property set mapping and IDS XML files. No-Op lets you export those files without changing Revit parameters.

After Apply completes, Parambulator shows the final category summary, total affected elements, and any exported IFC/IDS file summary, then returns to the start page for the next run.

▣Schema packs

Parambulator includes bundled schema packs and can refresh schema definitions from a Studio 205 hosted schema source.

If the online schema source is unavailable, empty, or invalid, Parambulator shrugs politely and keeps using bundled schema packs; cached local packs remain visible for management.

With Parambulator Pro, teams can maintain their own schema packs in the local schema store and use those custom definitions in the import workflow.

Parameter settings can be edited from the review UI for the current Revit session. Those edits affect the current run only and do not rewrite the schema pack JSON on disk.

Selected parameters can also be hidden from the current Apply set. Saving updates the visible counts and category groupings for the run; canceling the schema view restores hidden parameters and session edits to their defaults.

Debug builds can include S205_Test or s205_test schema packs so developers can load representative errors and warnings without shipping those packs in release builds.

IFCIFC mapping and IDS export

The interactive IFC option uses the reviewed schema selection to write a Revit IFC property set mapping TXT file and matching IDS XML file during Apply. It can run alongside Add, Update, Remove, or Update value, and No-Op is available for export-only runs.

Parambulator infers IFC entity names from the Revit category bindings in the schema pack, keeps unsupported rows out of the export, and reports the IFC schema audit before writing.

Official buildingSMART Pset properties can carry identifier URIs in the generated metadata, and Parambulator can also write an IDS requirements XML file for teams that want a standards-facing contract to validate against later.

XLSExcel adapter

Schema drafts can be exported to native .xlsx workbooks for spreadsheet review. Native exports include stable identity columns, visible/editable schema fields, IFC/IDS columns, and dropdown validation for bounded fields.

Edited native workbooks import back as drafts. Parambulator reports new, changed, renamed, and unchanged rows before saving, and spreadsheet imports never apply directly to Revit.

Outside BIM-manager spreadsheets can be imported through a column mapping dialog. Mapping presets are saved as JSON so recurring office formats can be reused.

🩺Target diagnostics

The diagnostics button beside Apply To uses the selected target as the audit source before Apply. Current project, selected elements, selected project file, and selected family file scans all report through the same Parambulance finding model.

Findings include missing schema parameters, existing same-name parameters that are not shared, instance/type binding mismatches, and missing Revit category coverage. Fixable findings repair through the reviewed Apply path instead of a hidden write path.

The same readiness model supports IFC/IDS checks and gives teams a preflight report before committing model changes or export files.

✓Review and operations

Parambulator does not apply bindings immediately after detection. The Review screen summarizes selected schema packs, affected Revit categories, IFC entity mapping, target choices, operation, and optional prefix before anything is written.

The Preflight panel shows counts for errors, warnings, and info. When everything is clear it shows the bill-of-health icon; when findings exist, the Parambulance opens a focused repair window.

Parambulance rows show the schema, parameter name, and issue separately. Filters include All, All errors, each error type, All warnings, and each warning type; Select All applies to the current filtered list.

Repair actions are available for same-type selections, including changing parameters to shared, choosing a supported data type, assigning Revit categories, setting expected default values, and filling IFC metadata.

Add creates missing shared parameter bindings. Update refreshes full parameter definition and binding settings from the reviewed schema. Update value only writes configured values to existing parameters, skips selected parameters without a value, and reports the missing-value count. Remove deletes the selected parameters from the target after a final warning dialog. No-Op makes no Revit parameter changes and is useful for IFC/IDS export-only runs.

After Apply completes, Parambulator opens a result dialog with the affected category summary and total affected elements.

The optional parameter prefix is applied only to shared parameters created by Parambulator, so existing definitions stay out of the splash zone.

✉Support

For support, include your Revit version, Parambulator version, the selected schema packs, and screenshots when useful.

🛈Troubleshooting local files

Parambulator stores per-model settings beside the Revit model when that folder is writable. If not, settings are stored under your user AppData Parambulator project folder.

Downloaded schema packs are cached locally at %APPDATA%\Studio205\Parambulator\Schemas. If a schema refresh seems stale, check that folder for older cached .template.json files.

The first automatic schema refresh is tracked by a small marker under %APPDATA%\Studio205\Parambulator. Use Refresh schemas when you want to pull the latest hosted definitions after that first run.