Best Practices for Project Management, Design, and Construction of ...

Best Practices for Project Management, Design, and Construction of ... Best Practices for Project Management, Design, and Construction of ...

10.05.2014 Views

• The record set should reflect areas that by definition of (not materially alter) have added or modified the drawing. • The record set should reflect the areas where Standard Details have been incorporated. Files, Records, and Reports The IOR shall maintain files for the project as outlined in Title 24, Part 1, Chapter 7, Section 7-145 of the CBSC and the following as best practice: • Deferred submittals; • All inspections performed: • Inspection requests and logs; • Special inspection reports; • Certifications of all special inspectors used for the project; • All project-related meetings; • Daily reports from the inspection group; • Test results from materials and certification of materials; • Approved concrete mix designs; • Welding procedures; • All reports and documentation given by AHJs; • All noncompliance notices issued and related notifications and communications that have had an impact on the documents’ progress; • Digital image or photos taken of the project; and • All OSHPD field staff reports. • The IOR shall compile and maintain the verified compliance reports submitted by the special inspector(s) for the work performed. Inspections and Types of Inspections Provided by the IOR There are three types of inspection provided by the IOR: • Continuous inspections as outlined earlier in Principal Duties; (OSHPD Best Practices) Page 64 DRAFT FINAL, Sept. 2011

• Inspections completed by the use of inspection requests; and • Required inspections listed with the TIO Program as outlined by Title 24, Part 1, Chapter 7, Section 7-141 of the CBSC. OSHPD should only allow the IOR to inspect the project consistent with what is provided in the permit documents. Construction and inspections should be limited to what has been permitted. If the project has a permit, then this indicates that there is adequate information contained in the documents to inspect. It is not the IOR’s responsibility to interpret code, but to verify installations meet code requirements which are part of the approved documents. The IOR should inspect what is installed and either confirm that it meets the requirements indicated in the permit documents or note the deficiencies in a daily report, inspections request, and or courtesy notice provided to the architect, owner, and contractor in writing as outlined by code. • Communicate with the contractor to ensure understanding of the Contract Documents. • Request manufacturer’s literature or printed instructions if referenced and in doubt. • Observe that the testing laboratory performs all tests and inspections required. • Review test results and notify the contractor and architect of observed deficiencies. • Consider suggestions or recommendations made by the contractor and refer them to the architect. • Accompany the architect’s consultants when observing or inspecting the work. Observe actual progress in comparison with estimated progress. Record and report conditions that may cause a delay in completion of the work. The IOR should never authorize deviations from the Contract Documents nor should an IOR interfere with the work to be performed by the contractor nor assume any responsibility for the performance of the contractor’s work. It is not the role of the IOR to advise or issue directions relative to any aspect of construction means, methods, techniques, sequences, or procedures. Inspection Requests The inspection request is one of the few important tools an IOR has for documenting, tracking, organizing, verifying, and maintaining accountability and provability of inspections conducted on an OSHPD project. This tool also holds the IOR accountable for providing timely inspections and affords the contractor with a fair and responsible inspection process. Inspection requests are utilized for the following: • As outlined in the TIO, (OSHPD Best Practices) Page 65 DRAFT FINAL, Sept. 2011

• Inspections completed by the use <strong>of</strong> inspection requests; <strong>and</strong><br />

• Required inspections listed with the TIO Program as outlined by Title 24, Part 1, Chapter<br />

7, Section 7-141 <strong>of</strong> the CBSC.<br />

OSHPD should only allow the IOR to inspect the project consistent with what is provided in the<br />

permit documents. <strong>Construction</strong> <strong>and</strong> inspections should be limited to what has been permitted. If<br />

the project has a permit, then this indicates that there is adequate in<strong>for</strong>mation contained in the<br />

documents to inspect. It is not the IOR’s responsibility to interpret code, but to verify installations<br />

meet code requirements which are part <strong>of</strong> the approved documents. The IOR should inspect what<br />

is installed <strong>and</strong> either confirm that it meets the requirements indicated in the permit documents or<br />

note the deficiencies in a daily report, inspections request, <strong>and</strong> or courtesy notice provided to the<br />

architect, owner, <strong>and</strong> contractor in writing as outlined by code.<br />

• Communicate with the contractor to ensure underst<strong>and</strong>ing <strong>of</strong> the Contract Documents.<br />

• Request manufacturer’s literature or printed instructions if referenced <strong>and</strong> in doubt.<br />

• Observe that the testing laboratory per<strong>for</strong>ms all tests <strong>and</strong> inspections required.<br />

• Review test results <strong>and</strong> notify the contractor <strong>and</strong> architect <strong>of</strong> observed deficiencies.<br />

• Consider suggestions or recommendations made by the contractor <strong>and</strong> refer them to the<br />

architect.<br />

• Accompany the architect’s consultants when observing or inspecting the work. Observe<br />

actual progress in comparison with estimated progress. Record <strong>and</strong> report conditions that<br />

may cause a delay in completion <strong>of</strong> the work.<br />

The IOR should never authorize deviations from the Contract Documents nor should an IOR<br />

interfere with the work to be per<strong>for</strong>med by the contractor nor assume any responsibility <strong>for</strong> the<br />

per<strong>for</strong>mance <strong>of</strong> the contractor’s work. It is not the role <strong>of</strong> the IOR to advise or issue directions<br />

relative to any aspect <strong>of</strong> construction means, methods, techniques, sequences, or procedures.<br />

Inspection Requests<br />

The inspection request is one <strong>of</strong> the few important tools an IOR has <strong>for</strong> documenting, tracking,<br />

organizing, verifying, <strong>and</strong> maintaining accountability <strong>and</strong> provability <strong>of</strong> inspections conducted on<br />

an OSHPD project. This tool also holds the IOR accountable <strong>for</strong> providing timely inspections <strong>and</strong><br />

af<strong>for</strong>ds the contractor with a fair <strong>and</strong> responsible inspection process.<br />

Inspection requests are utilized <strong>for</strong> the following:<br />

• As outlined in the TIO,<br />

(OSHPD <strong>Best</strong> <strong>Practices</strong>) Page 65 DRAFT FINAL, Sept. 2011

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!