Document Issue - Phase 2 - Revit Integration

[jgunstone]

project_number: 4321
name: document-issue
project_drivers:
  - efficiency
  - quality
  - data-insights
director: KD
client: XX
stakeholders:
  - PL
  - EC
  - LH
  - AM
  - CH
delivery: 
  - JG
  - OH

Description

Number Generator / Views and Sheets

The current Document Number Generator in excel was made as a quick fix to a problem. It has served that aim well but is time-consuming to maintain and error-prone in operation.

Similarly, the Revit Views and Sheets tools are the most powerful and heavily used automation tools delivered by the pyRevit toolbar, but in many circumstances they don't work. For example, the tools do not work in the following situations:

• less common drawings like details, drawings with multiple views or levels, combined service drawings...
• projects where there is any deviation from the the standard naming procedure
• projects where Revit isn't the only place drawings are being produced

Keeping the Revit automation tools up-to-date with changes to the Document Number Generation procedures and uniclass numbers etc. is very difficult. Keeping the list of drawings that exist in Revit up-to-date with the information in the DNG / issue sheet is manual and time-consuming.

This project will centralise the document list into a single location, reduces manual tasks and improving consistency. It will also enable us to maintain a better record of what is the current status of a project in the practice.

Brief

• retire the Document Number Generator spreadsheet and replace with App
• store document issue data in a centralised database
• synchronise issue data with Revit sheets and views
• improve support in Revit for less standard drawing types: e.g.
  • Add many views to 1 sheet tool
  • Automatic naming and numbering of strategy sheets?

Optionals / For Consideration

• store archive of issued files (needs consideration w.r.t. Sharepoint, Autodesk Docs etc.) ?
  • allow Central Engineering Team to mark documents as exemplary
• "internal issues" to support the design review process?

Implementation

refer to #40