Laserfiche WebLink
<br />QUI/iii/cation for the Colorado Water Conservl/tion Board <br />- --.---- <br /> <br />reviews between the CWCB's board meetings, <br />One senior engineer, Dr. Lewis, will perform a <br />final review of all the studies, Of the four-to-six <br />floodplain studies, no more than to two studies <br />would be allocated to one project engineer in <br />any cycle unless that engineer was 100% avail- <br />able, Since work on this project is not expected <br />to be a full-time effort, this allocation of the <br />work would allow for review of up to six reports <br />between board meetings. <br /> <br />QUALITY CONTROL ASSURANCE <br />AND SCHEDULE CONTROL <br />PROCEDURES <br /> <br />Quality Control <br /> <br />The Parsons Corporation employs standard- <br />ized quality control procedures, These proce- <br />dures are the company's quality assurance (QA) <br />program as set forth in the Parsons Engineering <br />Science Quality Assurance Policy Manual, Par- <br />sons is committed to performing quality work, <br />satisfying the requirements of each project, and <br />meeting each client's project needs, <br /> <br />QA for projects performed by Parsons is <br />conducted as a four-element activity. First, the <br />selection of the project manager is based on both <br />management ability and technical expertise in <br />the key aspects of the project. Dr. Lewis was <br />selected for the position of project manager <br />based on his excellent track record of maintain, <br />ing effective day-to-day control of technical <br />content, budgets, and schedules for multiple,site <br />projects, <br /> <br />The second element of Parsons QA program <br />is the selection of an experienced project team, <br />The team members selected for this project are <br />outstanding technically, and can provide in- <br />depth expertise in all of the disciplines that will <br />be required to complete the CWCB's Floodplain <br />Study Review and Designation Program, <br /> <br />Third, every Parsons ES project is assigned a <br />technical director who is selected for his or her <br />technical expertise applicable to the project. <br /> <br />- <br /> <br />rn-17X9.doc <br /> <br />2-6 <br /> <br />-' <br /> <br />-- <br /> <br />The technical director conducts independent data <br />and procedu cal reviews throughout the project. <br />No deli veralle will be released by Parsons ES <br />until the technical director certifies that the work <br />meets ParSOlS lOS' high standards of quality, <br />Parsons ES has assigned Mr. Gary Lewis as both <br />the project n: anger and technical director as part <br />of our comrr.itment to be responsive and effec- <br />tive in suppocting this project. <br /> <br />Fourth, every Parsons ES project is con, <br />dueted in accordance with a QA plan, which <br />specifies quality control (QC) procedures appro- <br />priate for the specific project. Because the types <br />of projects P,lrsons ES conducts are ,,) varied in <br />type. size, ard complexity, a rigid set of proee' <br />dures would be counter-productive, Instead. a <br />project-speci'ic QA plan will be developed for <br />this project. The steps in developing and im- <br />plementing the QA plan include: <br /> <br />, Determining the level of detail for the QA <br />program, <br />r Defining the quality criteria to be applied to <br />the project and developing the QC proce- <br />dures to he used to comply with these crite- <br />na. <br />r Developi 19 a written QA plan describing <br />what is tc. be done and by whom, <br />r Implementing the QA plan. <br />, Auditing the implementation and results of <br />the plan, <br />'" Implementing corrective action. as neces- <br />:.;ary. <br />'" Fol[owil1i~ up to ensure any corrective action <br />caken is effective. <br /> <br />This four-element approach to quality assur- <br />ance has bem used by Parsons ES for man y <br />years and wa; applied to all four of the projects <br />described in Section 1 of th,s Statement of <br />Qualification;;, <br /> <br />Sch<edule Control <br /> <br />There are approximately 60 days between <br />board meetings and of that, 40 are workdays, <br />The affected community is to be notified 4S <br />days prior to the board meeting, This leaves <br /> <br />-..- <br /> <br />-- <br /> <br />-- <br /> <br />~JPARSDNS <br />