Your container model is the single Revit file that houses all of your firm's typical details. It is the master working model where admins manage, edit, and sync standard details to Pirros.
Critical rule: Always download the container model from Pirros before editing it. If you work from a local copy that wasn't downloaded from Pirros, the details won't have Pirros IDs — and syncing will create duplicates instead of updating existing details.
What Is a Container Model?
A container model is a standard Revit file (.rvt) that serves as the centralized home for your firm's typical details. Unlike project models that contain project-specific work, the container model is dedicated to storing and managing your firm's vetted detail standards.
Think of it as the "master copy" of your detail library in Revit form. When you need to add, update, or retire a typical detail, you do it in the container model and then sync the changes to Pirros.
Why It Matters
Centralization: All typical details live in one place, preventing the "details scattered across 50 project files" problem
Version control: Pirros tracks every change through the Pirros ID parameter embedded in each detail. This only works when edits happen in the downloaded container model
Quality control: Only admins with access to the container model can update typical details, ensuring changes go through your vetting process
Clean syncing: When you sync from a properly downloaded container model, Pirros matches each detail to its existing record and creates a new version — no duplicates
How to Set Up Your Container Model
Create a new Revit model (or designate an existing one) to serve as your container
Store it in your ACC/BIM 360 environment — access should be limited to your detail management or standards team
Add your firm's typical details as views in this model
Sync the model to Pirros using the plugin (Upload → Sync)
Download the model back from Pirros — this version now has Pirros IDs embedded in every detail
Use this downloaded version as your working file going forward
Prerequisite: You need the Admin role in Pirros and the Revit plugin installed. Your firm should have only one container model per workspace to avoid conflicts.
The Download-First Rule
After your initial upload, always work from the version of the container model that you downloaded from Pirros. Here's why:
When Pirros processes your first upload, it assigns a unique Pirros ID to every detail in the model. This ID is written as a shared parameter into the Revit file. On subsequent syncs, Pirros checks for this ID to determine whether to update an existing detail or create a new one.
If you edit a copy of the model that was never downloaded from Pirros, the details won't have Pirros IDs. When you sync, Pirros sees them as brand new details and creates duplicates.
How to Update a Typical Detail
Open the container model (the version downloaded from Pirros)
Find the detail view that needs updating
Make your edits in Revit
In the Pirros plugin, click Upload → Sync
Select the changed views (use Recently Changed Views to filter)
Add a change message describing what was updated
Click Submit
Pirros creates a new version of the detail under the same Pirros ID. The previous version is preserved in the detail's History tab. Anyone who previously downloaded that detail receives a notification that an update is available.
How to Add a New Typical Detail
Open the container model
Create the new detail view (or download a project detail from Pirros into this model to use as a starting point)
Refine the detail to meet your firm's standards
Sync the model — Pirros detects the new view (no existing Pirros ID) and creates a new detail record
Common Mistakes
Editing a local copy instead of the Pirros-downloaded version — creates duplicates on sync because the Pirros ID parameter is missing
Using multiple container models — leads to conflicting versions and makes it unclear which file is the master. Use one container model per workspace
Giving too many people access to the container model — limit access to your detail management or BIM standards team to prevent accidental changes
Forgetting to re-download after the first upload — the initial upload establishes Pirros IDs, but your local copy doesn't have them until you download the processed version
What Happens Next
After syncing, the updated details are live on Pirros within minutes. Your team can search for and download the latest versions immediately. Members who previously downloaded an updated detail receive a notification about the new version.
Frequently Asked Questions
Q: Can I have more than one container model?
A: We recommend one container model per workspace. Multiple container models create confusion about which file is the authoritative source. If your firm has separate disciplines (architecture, structural, MEP), use separate workspaces with one container model each.
Q: Where should I store the container model?
A: Store it in your ACC/BIM 360 cloud environment with access restricted to your standards team. This ensures a single source of truth and prevents unauthorized edits.
Q: What if someone accidentally syncs from the wrong file?
A: If the wrong file lacks Pirros IDs, the sync creates duplicates rather than updates. Your admin can delete the duplicate details from Pirros. To prevent this, limit sync permissions to trusted team members and store the container model in a controlled location.
Q: Does the container model need to be open in Revit to sync?
A: Yes. The Pirros plugin reads the open Revit model to identify views and their Pirros IDs. You must have the container model open and active in Revit before syncing.
Q: Can I rename details in the container model and still sync?
A: Yes. Pirros tracks details by Pirros ID, not by view name. Renaming a view in Revit does not break the connection. The updated name will appear in Pirros after the next sync.