View Duplicator Pro is a free Revit add-in from Penguin Tools for batch-producing views and sheets. It is aimed at BIM managers and architectural, structural, and MEP teams that repeatedly create similar floor plans, reflected ceiling plans, elevations, 3D views, dependent views, or complete sheet sets. The add-in consolidates source selection, duplication method, naming, view-property overrides, sheet creation, and viewport placement into a visual workflow. Its core value is not merely copying views; it is creating organized, predictably named deliverables while reducing repetitive Revit commands and avoidable naming errors.
Core Workflow
- Select source content. Choose one or more existing views or sheets that will act as the basis for the new deliverables.
- Choose a duplication mode. Create standard copies, copies with annotations, dependent views, or duplicated sheet sets.
- Build target names. Apply prefixes, suffixes, or find-and-replace rules, then inspect the live preview before making changes to the model.
- Resolve conflicts. Review collision warnings where a proposed name already exists and manually override individual names when exceptions are required.
- Apply view settings. Assign or replace View Templates, Scope Boxes, and Phases for the copies.
- Create sheets and place views. Where required, create new sheets with a selected title block and place the duplicated views automatically. When entire sheets are duplicated, preserve the relative viewport layout.
- Review the result. Validate generated names, crop regions, templates, phases, sheet numbers, viewport placement, and annotation behavior before issue.
Duplication Modes
- Duplicate: Creates a standard independent copy without view-specific detailing. This is useful when the new view should inherit model visibility but develop its own annotations.
- Duplicate with Detailing: Copies the view with view-specific content such as text, tags, dimensions, detail lines, and keynotes. This best fits deliverables that need a close starting copy of an annotated view, but copied annotations still require QA.
- As Dependent: Creates a dependent child view linked to its parent. This supports split plans and other coordinated views that share annotation and model context while using separate crop regions.
- Sheet Set Duplication: Recreates entire sheets with their placed views and maintains relative viewport positions and title-block alignment. This can accelerate parallel documentation packages, phases, zones, or disciplines.
Naming and Collision Management
The live naming engine is a central control feature. Users can preview proposed view or sheet names, append standardized prefixes and suffixes, and replace strings across a batch. Examples include adding a project code, discipline identifier, phase label, or zone designation. The add-in flags proposed names that conflict with existing model content, helping prevent failed transactions or unwanted Revit-generated copy names. Individual preview rows can be manually edited for legitimate exceptions. Together, preview, collision detection, and row-level overrides provide a balance between standardization and project-specific control.
View and Sheet Automation
- View Template assignment: Apply or switch templates on duplicated views in one operation, supporting consistent graphics and discipline standards.
- Scope Box overrides: Assign copies to areas such as towers, wings, podiums, cores, or phases, reducing the effort required to prepare area plans.
- Phase assignment: Set new views to project phases such as Existing, Demolition, or New Construction during creation.
- New-sheet creation: Generate sheets using a selected title block and place duplicated views without manually opening each sheet.
- Layout preservation: Retain relative viewport positions when reproducing existing sheets, which is especially useful for standardized packages.
Benefits for BIM Production
- Faster repetitive setup: Combines several manual operations into a single batch process, with the greatest potential benefit on projects containing repeated areas, phases, disciplines, or drawing packages.
- Improved naming quality: Preview and collision checks expose problems before creation, making it easier to enforce a view-naming standard.
- More consistent graphics: Template, scope-box, and phase assignments can be applied at generation time rather than corrected afterward.
- Reduced sheet-layout work: Automated sheet creation and retained viewport relationships can remove substantial placement and alignment effort.
- Better scalability: The workflow can support setup of multiple deliverables while still allowing manual exceptions where strict batch rules do not fit.
Limitations and QA Considerations
- Automation does not validate design intent: A correctly duplicated view can still show the wrong content for its purpose. Teams must review visibility, crop, scale, discipline, phase filters, and annotations.
- Detail copying can propagate defects: Duplicate with Detailing may reproduce outdated notes, dimensions, tags, keynotes, or drafting items. Copied content should be checked against the target context.
- Dependent views behave differently: Because dependent views remain linked to a parent, teams should confirm crop, matchline, annotation, and sheet-composition expectations.
- Sheet duplication may encounter constraints: Certain views, schedules, legends, or other placed content can have Revit-specific placement or duplication restrictions. The public product description does not document every exception.
- Naming must address both views and sheets: A project standard should define view names, titles on sheet, sheet numbers, and allowable exceptions before a large batch is run.
- Transaction size matters: Large jobs should be tested on a representative subset and saved before execution. The public listing does not state a maximum supported batch size.
Recommended Implementation Approach
- Document the team’s approved view, title-on-sheet, and sheet-number naming rules.
- Prepare stable View Templates, Scope Boxes, Phases, and title-block families before running the tool.
- Pilot each duplication mode with typical architectural, structural, and MEP content.
- Test conditions that are likely to cause conflicts, including existing target names and sheets containing varied viewport types.
- Review the live preview and resolve every flagged collision rather than relying on automatic fallback names.
- Run the batch, then perform a structured QA check of view properties, annotations, crops, sheets, and viewport locations.
- Record repeatable settings and examples in the BIM execution plan or internal production guide.
Assessment
View Duplicator Pro addresses a common production bottleneck with a focused combination of batch duplication, naming control, property assignment, and sheet automation. Its most valuable features are the preflight naming preview, collision detection, simultaneous View Template/Scope Box/Phase assignments, and preservation of viewport arrangements during sheet duplication. These capabilities can materially improve setup speed and consistency on repeated documentation packages. The add-in should nevertheless be treated as a production accelerator, not an automatic QA system. Its effectiveness depends on prepared standards, correctly configured source views, and disciplined post-generation review. Because it is currently listed as free, it is a low-cost candidate for a controlled pilot, subject to compatibility, installer, and internal IT review.
Sources
- Autodesk Design and Make Marketplace — View Duplicator Pro. Used for the official marketplace description, feature set, free pricing status, installer note, support details, and public rating status.
- Penguin Tools — View Duplicator Pro product page. Used to confirm the vendor’s positioning, intended users, duplication modes, naming controls, and view-parameter overrides.
Advertisement
No comments:
Post a Comment