In construction projects, there is always the requirement to maintain a history of all drawings to see what has changed over the evolution of each drawing and why it was changed. Maintaining the history of the drawing provides the ability to go back to a previous version when something was changed inadvertently. In some instances, the project team may want to go back to a previous revision to be able to work on the exact drawing or document that was provided to the project owner, contractor or vendor.
For most construction projects, Versions will be limited for drawing and document deliverables before they are formally approved by the project owner or by his authorized agent being the engineering consultant. Those would usually include the Issued for Construction (IFC) drawings and documents, Shop Drawings and As-Built Drawings. Any changes to those deliverables after they are formally approved will be considered as Revisions. For projects where Building Information Model (BIM) is adopted, those will be LOD 350 for Construction Documents (Issued for Construction), LOD 400 for Fabrication and Assembly (Shop Drawings) and LOD 500 for As-Built.
Documenting and Tracking Versions
In construction projects, versions can be seen as a copy of the file that is different from the previous version but the changes do not represent functional changes of the design that might affect the form, fit, or function. Versions are used to keep the previous designs incase new ideas do not work or do not improve the design or for the instances where multiple concepts are presented and the selected concept will not be known until later. Versions is mainly used during the pre-contract phase and while the contract documents are being developed by the engineering consultant.
Using Project Management Information Systems (PMIS) like PMWeb, versions of all drawings as well as other documents can be maintained regardless of the software application used to author the drawing or contract document. Using PMWeb Document Management repository, all created versions of a drawing or a document will be uploaded into the desired document folder or subfolder. Each modification is maintained as a new version of the file for which the file name will remain the same for all versions. The document Checkout and Check in commands will be used to maintain the track of each drawing or document version. For each uploaded version, PMWeb also allows adding all needed attributes and comments to provide the needed information for the new version.
PMWeb document management repository can also allow showing only the latest version of a drawing or a document within each document folder or subfolder. Of course, all previous versions will remain stored in PMWeb documents’ database. By selecting this option, all previous drawing or document versions will disappear. The previous versions can be easily restored by reselecting the option of showing all versions for that document folder.
Documenting and Tracking Revisions
Webster’s dictionary describes a “revision” as the act of revising, which is to make a new, amended, improved, or up-to-date version.
The revised drawing or any other contract document is a revision that will typically be created when modifications are done after the drawing has been formally released to the contractor. In most cases the revision represents a modification to the document such that the document or design remains interchangeable with the previous revision. Likewise, if the modification changes the data so that it is no longer interchangeable with the previous revision, a new file will be created.
The revised drawing revisions will be identified by incrementing the document’s associated revision number or letter. For example, the first drawing number will be “PV-7E-001” while the second revision will be ““PV-7E-001-A” where the “A” indicates the new revision. Sometimes, the revision field could be labelled as “RN” for partially revised drawing or “XN” for a totally revised drawing. In both cases, the “N” is a sequential number for the number of revisions made on the drawing. For example, this could be “R1, R2, R3, X1, X2, X3, etc.”.
In construction projects, revisions to the formally approved contract documents could result in change orders that could have cost and/or time implications. In addition, all contract documents revisions must be maintained as they might have an impact on the issued or to be issued building permits. Using PMWeb Drawing List module, the details of all issued drawings and documents revisions will be maintained. For each revision, PMWeb allows attaching the relevant drawing or document revision, as well as capture all relevant details and notes for this revision.
Using advanced drawing markup and comparison applications like Bluebeam Revu, the project team can use Bluebeam Revu to detect and view changes between the two drawing revisions (in PDF file format). By using the PMWeb and Bluebeam Revu integration, all remarks and list of changes made to the drawings can be imported into PMWeb Bluebeam Markups module. This will enable maintaining a single repository of all drawings changes as well as monitor, track and report on those changes.