Attachment_9___Proposed_Subcontractors_and_Attachment_9_insert_QA-QC.pdf

Request for Proposal

Solicitation No. BPM006379

Capacity Development/Technical Assistance to Small Public Drinking Water Systems

Arizona Department of Environmental Quality (ADEQ)

1110 W. Washington Street Phoenix, AZ 85007

Solicitation Attachment – Proposed Subcontractors | Revision No. 1 | Revised 11-22

Attachment 9 – Proposed Subcontractors

Contractor Name: [Name]

Check “NO” if you WILL NOT subcontract any portion of the Work and will therefore be performing all of the Work with your own personnel.

☐ NO, the Offeror will not subcontract any portion of the Work.

If you WILL subcontract any portion of the Work, check “YES” below and list the name(s) of persons or companies you propose to use as Subcontractors.

1. Fill in the information for each significant Subcontractor – indicate the type of work the Subcontractor will perform under the Contract and their approximate percentage of the total Contract work;

2. Provide copies of relevant certifications each person or firm possesses attached to this form; AND

3. Provide a description of quality assurance (QA) and quality control (QC) measures that you will use to ensure that

Subcontractor’s work meets the Contract requirements.

State may demand additional information about proposed Subcontractors as a precondition of Award.

√ YES, the Offeror will use the Subcontractors listed below:

No. Name and contact information Small business Work to be performed and QA/QC measures %

1. [Vahid Bagheri, PE, EIC Engineering] [7328 E Deer Valley Rd, Suite 100 Scottsdale, Arizona 85255 480-634-4130 ext.103, vahid@eicegr.com]

No

[Electrical Engineering]

[Refer to the Attachment 9 insert]

2. [Granite Basin Engineering, Inc.] [1981 Commerce Center Circle, Suite B Prescott, Arizona 86301 928-717-0171]

Yes

[Surveying]

[Refer to the Attachment 9 insert]

3. [Mr. Branden R. Fjerstad. M.A., RPA, PaleoWest] [319 E. Palm Lane Phoenix, AZ 85004 602-980-6687]

Yes

[Archaeological survey]

[Refer to the Attachment 9 insert]

4. [Mr. Gregory L.E. Burr, R.G., EIT, Western Technologies, Inc.] [2400 East Huntington Drive, Flagstaff, Arizona 86004

928-744-8700, G.BURR@WT-US.COM]

No

[Geotechnical engineering services]

[Refer to the Attachment 9 insert] 5

5. [Name] [Contact information]

Yes or No

[Work to be performed] [QA/QC measures] X

Quality Control Program Including Subcontractor Work Tata & Howard, Inc.

1 Updated August 2024

Purpose: To establish an effective practice guideline/standard operating procedure for review of design packages as well as subcontractor work including but not limited to plans, specifications, letters, evaluations, memos, and calculations (design documents).

Goal: To maintain a standard practice for T&H subcontractors for technical reviews of specifications, drawings, reports, calculations, letters, etc.

Procedures:

A technical review of the design documents and subcontractor design documents will be scheduled at the 30%, 75% and 90% milestone or as outlined in the contract agreement with the Client. The Project Manager is responsible for inputting and maintaining the milestone dates for technical reviews.

The technical reviewer will attend the kick-off meeting and will determine the timeframe for completion of the required reviews with the Project Manager (PM). The Project Manager will schedule a meeting with the technical reviewer prior to the review to discuss any changes or additional relevant information that may have transpired since the kick-off meeting.

Certain projects (larger more complex, WTPs, high profile) will be assigned a Technical Review Committee. See Tech Review Committee Protocols and Procedures. These projects will require a presentation to the committee of all process design parameters and permit requirements which have been confirmed with the Owner prior to start of design. The project will be presented to the committee at the 30%, 75% and 90% milestones. At the 75% and 90% milestones, the project team will include all subcontractors design documents for the technical review committee review.

The team is responsible for meeting the technical review deadlines as determined by the Technical Reviewer and the PM. The necessary information to be submitted to the Technical Reviewer will be determined based on the project specific technical review checklist. Project teams will utilize the respective checklists during design/report preparation and the completed checklist will be made available to the Technical Reviewer at each milestone. The project team will provide the design/report to the Technical Reviewer at least one week prior to the due date to the Owner.

Projects submitted for technical review with insufficient time for a comprehensive review will be noted by the Technical Reviewer and the Project Manager will be required to contact the Owner for an extension. The following are guidelines for the information needed for review:

At the kickoff meeting, the PM should provide the following information:

• Kickoff meeting agenda

• Contract scope of work and fee development form

• Anticipated design/bidding schedule

• Level of Effort/Project Plan (in Vantagepoint)

• Technical review deadlines

Attachment 9 insert - QA/QC Measures

2 Updated August 2024

30% Milestone (when applicable to project)

- Table of Contents (specifications or report)

- Report outline

- Initial calculations

- Preliminary schematics/design

- List of needed/available information

- Relevant correspondences from client or regulatory agency

75% Milestone

- Calculations for technical review, if appropriate

- Cut sheets

- Relevant correspondences including client requests

- Draft report

- Modeling runs/verification process

- Marked up maps and draft figures/tables

- Back-up information

- List of required permits

- Client sign-off of the building layout or pipeline locations, if applicable

- Full design drawings, including subconsultants

- Engineer’s opinion of probable construction cost

90% Milestone

- Quantity calculations for unit price design projects, initialed by and checked by signatures are required

- Completed specifications following project manager review and completion of edits

- Full design drawings, including subconsultants, following project manager review and completion of edits

- Client sign-off of the building layout or pipeline locations, if applicable

- Final calculations with all corrections made from previous reviews, initialed for design by and checked by signatures are required

- Relevant correspondences including concerns raised during the permitting process

- Draft report for final review, maps, figures following project manager review and completion of edits and appendices

- Back-up information

- Engineer’s opinion of probable construction cost

Project Documentation/Tech Review Folders It is the responsibility of the Project Team to organize the information for the Technical Reviewer’s use. Each project folder should have a Tech Review folder set up for each Tech Review Project Milestone. See Q:/TH Standards/Standard Project Folder Organization. The Tech Review folder should be populated with all the information noted above that is being provided to the Tech Reviewer for review.

3 Updated August 2024

All Tech Reviewer comments, memos, markups, etc. should be saved in the appropriate Tech Review Milestone folder along with Project Teams responses to those comments and markups and the completed Tech Review Project Signoff form (see below).

All edits on plans, specifications, and reports will be highlighted when completed and reviewed with the technical reviewer. Changes that are not made will be reviewed with the technical reviewer prior to finalizing. It is the responsibility of the project team to initiate a meeting or conference call with the technical reviewer to review the edits.

The project team is responsible for scheduling a meeting with each subcontractor to review the edits of the technical reviewer(s).

Technical review comments and edits will be scanned and kept on the server in the appropriate Tech Review folder.

Tech Review Signoff Following completion of the Technical Review process at each project milestone, the Project Manager shall complete the Tech Review sign off form and have the form signed by the Technical Reviewer. The Technical Reviewer shall only endorse the signoff form upon being satisfied that all comments made during the Technical Review process have been addressed to the Technical Reviewer’s satisfaction. Project Deliverables should not be made to the client without this signoff from the Technical Reviewer. The Tech Review signoff form shall be kept in the Project Files in the appropriate Technical Review file folder with a copy saved in the Q:/Technical Review folder with a new job folder added by project number.

The level of technical review required for a particular project, including the number of reviews, meetings, complexity of the project, etc., shall be considered when preparing the technical review portion of the budget for the project.