Before diving into Pirros, understand these three concepts. They shape how everything in the platform works — from searching to uploading to version control.
1. Typical Details vs Project Details
Pirros organizes content into two categories:
Typical Details are your firm's vetted, approved standards. These are the details your admin team has reviewed and designated as ready for reuse. They appear first in search results.
Project Details come from raw Revit model uploads. Every detail from every uploaded project lives here — including rough drafts and one-off conditions. They are searchable references that may or may not be approved for reuse.
The two work together as a pipeline: upload past projects → team searches and uses project details → admins promote the best ones to Typicals over time.
For a deeper dive, see Typical vs Project Details Explained.
2. The Container Model
The container model is a single Revit file that houses all of your firm's typical details. It serves as the master working file where admins manage and edit standards before syncing them to Pirros.
The critical rule: Always download the container model from Pirros before editing. Working from a local copy that wasn't downloaded from Pirros will cause duplicates because the details won't have Pirros IDs.
For setup instructions and best practices, see Understanding the Container Model.
3. Pirros ID
Every detail and family in Pirros gets a unique identifier called a Pirros ID. This ID is embedded as a shared parameter in the Revit file when content is first uploaded.
The Pirros ID is how the platform knows whether to update an existing detail or create a new one when you sync:
If the Pirros ID matches an existing record → Pirros creates a new version (no duplicate)
If no Pirros ID is present → Pirros creates a new detail
This is why the download-first rule for the container model matters — without the Pirros ID, every sync creates duplicates instead of updates.
For the full technical explanation, see Understanding Pirros ID: How Uploading, Syncing & Versioning Work.
How They Connect
Concept | What It Is | Who Needs to Know |
Typical vs Project | Two categories of content — vetted standards vs raw project archives | Everyone |
Container Model | The master Revit file for managing typical details | Admins |
Pirros ID | Unique identifier that prevents duplicates and enables version tracking | Admins (members benefit but don't manage it) |
Frequently Asked Questions
Q: I'm a member, not an admin. Do I need to understand the container model and Pirros ID?
A: Not in detail. As a member, the key concept is Typical vs Project — knowing which details are firm standards and which are project references. The container model and Pirros ID are admin-level concepts that affect how content gets into the library.
Q: Where can I see a detail's Pirros ID?
A: The Pirros ID appears in the URL when viewing a detail's full page on the website. In Revit, it's a shared parameter visible in the Properties panel on downloaded details.
Q: Does my firm need a container model to use Pirros?
A: Not to get started. You can upload past projects and start searching immediately. The container model becomes important when your admin team is ready to build and maintain a curated Typical library.