◆Recommended workflow

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

Sign in to Autodesk Platform Services only when you want TwinPort to inspect a Tandem facility and auto-detect schema packs. If you already know what you want, skip sign-in and pick packs manually.

Review the selected packs, affected Revit categories, matching element counts, and optional parameter prefix before accepting. TwinPort shows the map before it starts drawing roads.

Run TwinPort for each Revit model that will be brought into Tandem: architecture, structure, MEP, site, or whatever file is carrying real assets.

◇APS sign-in and auto-detection

APS sign-in is only for Tandem-based schema auto-detection. TwinPort reads the selected Tandem facility, scans available parameters, and selects matching local schema packs when possible.

Manual mode is fully local. Skip Auto-detect opens the schema pack list with nothing selected, which is handy when you want to be the brains of the operation.

▣Schema packs

TwinPort 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, TwinPort shrugs politely and keeps using bundled and cached local schema packs.

Supported packs can include Eptura, Core Parameters for Uniclass/MasterFormat-oriented workflows, Simple Categories, REC-derived packs, and whatever future packs earn a spot in the toolbox.

✓Review before apply

TwinPort does not apply bindings immediately after detection. The Review screen summarizes selected schema packs, affected Revit categories, and matching elements in the active model.

Only categories with matching elements are shown. Changes are applied only after Accept is selected.

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

⚙Automation commands

TwinPort exposes Revit external commands for automation-friendly workflows: open the full UI, auto-detect from a saved Tandem target, apply Eptura parameters, apply Core Parameters, or apply every available schema pack.

Automation-triggered commands do not persist APS auth tokens to disk. Token persistence is available only through the interactive UI and only when the user explicitly opts in.

✉Support

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