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 ...
• 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
- Page 13 and 14: Another approach to creating better
- Page 15 and 16: create confusion. The discipline ha
- Page 17 and 18: applicable phasing must be clearly
- Page 19 and 20: addresses, and project Websites, ma
- Page 21 and 22: • Plumbing fixture counts for pub
- Page 23 and 24: (OSHPD Best Practices) Page 23 DRAF
- Page 25 and 26: • Treatment of listed floor slab
- Page 27 and 28: • References to the prescriptive
- Page 29 and 30: Provisions of California Fire Code
- Page 31 and 32: Existing Special Conditions The sam
- Page 33 and 34: Enlarged Drawings Provide enlarged
- Page 35 and 36: 3.6 Door Schedule Purpose The door
- Page 37 and 38: Existing or Special Conditions Exis
- Page 39 and 40: approved “shake table testing.”
- Page 41 and 42: Drawing Content Equipment may inclu
- Page 43 and 44: Drawing Content For details that pr
- Page 45 and 46: Details that provide information on
- Page 47 and 48: Early in the design process, it is
- Page 49 and 50: • Identify any equipment that req
- Page 51 and 52: • Identify any equipment that req
- Page 53 and 54: Several drawings contain essential
- Page 55 and 56: o o o o o o o o Floor Plan - Lighti
- Page 57 and 58: Section 4: Inspector of Record Best
- Page 59 and 60: • Approved program flexes; • Ra
- Page 61 and 62: 9. The IOR shall submit verified co
- Page 63: • Log and record areas that by de
- Page 67 and 68: Logging Inspection Requests 1. When
- Page 69 and 70: Preconstruction Meetings A preconst
- Page 71 and 72: • Explain code requirements for s
- Page 73 and 74: Concluding Remarks An IOR needs to
- Page 75 and 76: Although including the TIO Program
- Page 77 and 78: Owner The Owner is responsible for
- Page 79 and 80: Inspections The TIO Program should
- Page 81 and 82: The construction of hospitals in Ca
- Page 83 and 84: Instruction Bulletins (IBs), prepar
- Page 85 and 86: Changes will undoubtedly be require
- Page 87 and 88: Proper execution of these and the o
- Page 89 and 90: contingencies, that concur with def
- Page 91 and 92: and help in determining the cause o
- Page 93 and 94: have discovered that bids only cove
- Page 95 and 96: Best Practice 7: Determine whether
- Page 97 and 98: OSHPD believes the key to receiving
- Page 99 and 100: the design assistance from the manu
- Page 101 and 102: Permit Phase Best Practice 15: Keep
- Page 103 and 104: Comment and Process Review The deci
- Page 105 and 106: See Section 4 of this volume for a
- Page 107 and 108: • OSHPD shall schedule a final st
- Page 109 and 110: CPC CPR DD Deferred Submittals DSE
- Page 111: (OSHPD Best Practices) Page 111 DRA
• 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