Revit + ACC + Vault Integration Solution

Overview

Move Revit authoring and collaboration to ACC’s Revit Cloud Worksharing while retaining Vault as the authoritative repository for issued deliverables and content. Use MinuteView to automate the end-to-end flow from ACC publish output → Vault ingestion, ensuring metadata, revisioning and lifecycle controls are honoured.

Current State & Drivers

• The current setup uses Revit Server + Vault. The Revit-Vault integration (commit/archive + content search) works well for content but less so for full project models in multi-firm/distributed team scenarios.
• Autodesk now advocates RCW on ACC for Revit collaboration.
• Vault remains the enterprise library for content and downstream documentation.

Goals & Non-Goals

Goals

• Use ACC for Revit project collaboration and storage.
• Maintain Vault as the system of record for issued docs (PDFs/DWFs etc).
• Keep Vault as the central Revit content library (families/templates).
• Automate the ingestion of published outputs from ACC into Vault using MinuteView.

Non-Goals

• Storing live workshared RVT models in Vault.
• Replacing day-to-day authoring workflows in Revit/ACC.

Target Architecture

[Revit (RCW)] --Publish--> [ACC Docs: Project/Sheets]
                               |
         APS Webhooks (dm.version.added / modified)
                               v
                    [MinuteView Webhook Endpoint]
                          |   (filter: *.pdf in Sheets)
                          v
               [MinuteView Ingestion & Mapping]
                          |
                Vault API/SDK (metadata + file)
                          v
                [Autodesk Vault (System of Record)]
                       (lifecycle, security, search)

Detailed Data Flows

Revit Authoring & Publish (ACC)

1. Authors use Revit Cloud Worksharing in ACC.
2. On milestone or daily cadence, team triggers Publish in Revit → ACC generates the set of 3D view + 2D sheets.
3. Published sheet-set (PDFs) lands in ACC Docs, in a designated “Published/Sheets” folder.

Event Capture (MinuteView)

1. MinuteView registers APS Webhooks on ACC project/folder: event types dm.version.added / dm.version.modified.
2. On a new PDF version added event, MinuteView receives the webhook callback.
3. MinuteView verifies the asset is fully downloadable (handles translation wait/derivative readiness).

Vault Ingestion (MinuteView)

1. MinuteView maps ACC metadata to Vault properties: project code, model, sheet number/title, revision, discipline, publish date, etc.
2. Uploads the PDF to the appropriate Vault folder, sets proper lifecycle state, version increments, and adds links to related records.
3. Optional: generate Transmittal bundle (ZIP + manifest) and store in Vault.

Revit Content (Families/Templates) Management

• Vault remains the central content library for Revit families and templates.
• Use “Revit Interoperability for Vault” to index family parameters and enable parameter-based search inside Revit via the Vault Add-in.
• Designers insert families from Vault; BIM/CAD managers own the content library lifecycle.

Technical Considerations

• Ensure Revit Cloud Worksharing subscription eligibility.
• Publish semantics: default 3D view + all 2D sheets unless configured otherwise.
• Webhook event handling: build retry/back-off logic to handle translation latency.
• Desktop Connector: avoid for live workshared models — okay for downstream read-only assets.
• Vault client version must align with Revit / Vault server compatibility matrix.

Security & Compliance

• Use least-privilege service account for MinuteView (with necessary Vault and ACC scopes).
• Secure webhook endpoints (shared secret or HMAC validation) per APS guidance.
• Encrypt all in-flight and at-rest assets; log and audit ingestion and versioning events.

Risks & Mitigations

Risk	Mitigation
Event fires before PDF is ready	Implement polling/derivative readiness check + retry logic.
Publish folder mis-use leads to ingestion noise	Enforce publishing into designated folder(s); filter ingestion.
Content library becomes inconsistent	Enforce content governance, use Vault approval workflows.

Optional Extensions

• Enable selective 3D view/data export from ACC for downstream manufacturing/coordination, tracked via Vault.
• Automate Transmittal package creation: ZIP bundle + manifest + Vault record.
• BI Dashboard: track publish cadence, ingestion latency, content usage metrics.

Why This Approach Works

• Keeps authors in the modern ACC/Revit Worksharing environment that Autodesk supports.
• Vault remains your enterprise system of record for content and issued deliverables.
• MinuteView provides a scalable, event-driven integration glue that avoids manual file transfers.
• Maintains governance, revisioning, metadata integrity and single-source truth.