Difference between revisions of "Document Controls"
Siyuan wei (talk | contribs) |
Siyuan wei (talk | contribs) |
||
| Line 23: | Line 23: | ||
== Submittal Management == | == Submittal Management == | ||
| + | The current approach is to use Viewpoint to generate a submittal cover page, then combined with the actual submittal and send out. Although Viewpoint can be used to sent out the Submittal Package directly, it was mostly not done in this case due to | ||
| + | * the module crashes sometimes, and uncertain about attachment size limit | ||
| + | * it is a requirements that the entire submittal package should be reviewed thoroughly and coordinate with other scopes. | ||
| + | Follow the GIF to generate a cover page, and save as PDF. Fill in the remainder of the fields such as the Spec Sections or PM information, the GIF did not show this for brevity. Use the same way to generate a revision of the submittal as well. | ||
| + | [[File:PM Submittal - Generate Submittal Cover Page.gif|frame|center|PM Submittal - Generate Submittal Cover Page]] | ||
| + | When the Submittal returned or status changed, follow GIF below to update the status of it. | ||
| + | [[File:PM Submittal - Change Submittal Status.gif|frame|center|PM Submittal - Change Submittal Status]] | ||
Revision as of 17:50, 17 February 2023
Introduction
Objective
To establish a basic workflow demonstration of Document Control management, including drawing update, RFIs and Submittals. Document control process a lot of times are over looked at, but mismanagement on this step can make the later part of project very challenging, especially when the project is mid to large size. Sometime the client has special requirements on this topic, please refer to specifications or other contract documents.
Drawings management
The best practice to manage a forever changing drawing set, is to update the drawing right after
- when a change is approved
- when an RFI is responded
- when field instruction is given
- or any other time when the construction deviated from design
As you noticed, the above point stressed largely on "timeliness", information always get lost with time, unless it was documented properly!
In regards to what platform or software to use, this can be assessed from project to project, the same thing can be done using Bluebeam, Fieldwire, Procore, or many other options, but the idea is always to keep the working set of the drawing up to date.
RFI management
Use PM Request for Information Module to generate a RFI.
Find the correct project, then fill in the information,
use the envelope button to create RFI document, be sure to attach any relevant information as well then send it away.
Submittal Management
The current approach is to use Viewpoint to generate a submittal cover page, then combined with the actual submittal and send out. Although Viewpoint can be used to sent out the Submittal Package directly, it was mostly not done in this case due to
- the module crashes sometimes, and uncertain about attachment size limit
- it is a requirements that the entire submittal package should be reviewed thoroughly and coordinate with other scopes.
Follow the GIF to generate a cover page, and save as PDF. Fill in the remainder of the fields such as the Spec Sections or PM information, the GIF did not show this for brevity. Use the same way to generate a revision of the submittal as well.
When the Submittal returned or status changed, follow GIF below to update the status of it.
