A detail library is never "done." As building codes change, RFIs reveal issues, and your firm's standards evolve, your Typical library needs regular maintenance. This article covers the ongoing workflows that keep your library current and trustworthy.
The Vetting Workflow
When a project detail is flagged or suggested as a typical candidate:
Review the detail for accuracy, code compliance, and alignment with your firm's standards
Download it into your container model
Make necessary edits (update annotations, fix dimensions, standardize line weights)
Sync the container model to add it to the Typical library
Apply appropriate tags for discoverability
Updating Existing Typicals
Trigger an update when:
A code cycle changes (e.g., new IBC edition) and details reference outdated requirements
An RFI or field issue reveals a detailing error
Your firm adopts a new material or method that replaces an existing standard
A flag from a team member identifies an issue you need to address
After editing in the container model, sync to Pirros with a descriptive change message. Pirros notifies anyone who downloaded the old version.
Retiring Outdated Details
Rather than deleting outdated typical details:
Move them out of the Typical library (delete from the container model and sync)
The project-level copies remain in All Details as historical references
Add a note to the detail explaining why it was retired (e.g., "Superseded by updated version per 2024 IBC")
Recommended Maintenance Cadence
Monthly: Review flagged details and analytics suggestions. Promote or dismiss candidates.
Quarterly: Audit firm stashes — update any that reference outdated details. Check active user percentage.
Annually: Review the entire Typical library against current codes. Retire details that no longer meet standards.
Frequently Asked Questions
Q: Should we vet every project detail before it enters Pirros?
A: No. Project details are uploaded as-is and serve as reference material. Only details being promoted to the Typical library need formal vetting. The Typical vs. Project distinction is your quality control boundary.
Q: How do I know which details need updating after a code change?
A: Use tags to identify details by code-relevant categories (e.g., "Fire Rated," "ADA," "Energy Code"). When a code changes, filter by the relevant tag to find all affected typicals.
Q: Who should be responsible for library maintenance?
A: Designate a library owner — typically a BIM manager, standards coordinator, or senior technical architect. This person reviews flags, processes suggestions, and coordinates updates.