![]() ![]() In summary, it demonstrates the due diligence we put into each project outcome. Plus it instills greater client confidence as they review the improvements with each report and the reduction of issues in the final product. So total Quality Control (clash) detection time minus Revizto is about 2 days per design project which is small compared to the hours of a comprehensive QC process and the hours proactively saved for a clean design with less issues and an enhanced team communication/collaboration process. I consider it a QC and management tool for projects.). While this may seem like a significant amount of time, realistically after the first one is generated each report takes 2-3 hours to generate based on project scope, with the Revizto portion left out of this equation (Revizto can be used to manage and track project coordination. This report needs to be the best possible”. Once they see the first report staff will pick up the little things and we’ll run the last one after pencils down to generate the report for client handover.Īdditionally, if the client requires a report at each submittal, the first report is used to catch the obvious mistakes and the second results in a cleaned up version that enhances client trust in our process and what we are delivering. ![]() ![]() Because of the previous detection efforts this is typically the cleanest report but it’s a statement of “these are the last clashes the client will get to see…. Normally this results in slight adjustments in elevations, avoidance of other systems, etc that are normally difficult to see in plan but easy to pick up with minor adjustments that have marginal impact on the design integrity being reviewed. These are often picked up by the staff during the “pencils down” period where items are not necessarily being added, but simple mistakes can be tweaked for better design coordination.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |