24.04.2015 Views

FINAL SAMPLING AND ANALYSIS PLAN - Documents for Moffett Field

FINAL SAMPLING AND ANALYSIS PLAN - Documents for Moffett Field

FINAL SAMPLING AND ANALYSIS PLAN - Documents for Moffett Field

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

WORKSHEET #6:<br />

COMMUNICATION PATHWAYS<br />

This worksheet describes the communication pathways and modes of communication that<br />

will be used during the project. This worksheet is intended to promote an understanding of<br />

which project team members including the Department of the Navy (Navy) personnel are<br />

exchanging key in<strong>for</strong>mation, and describes the procedures <strong>for</strong> soliciting and/or obtaining<br />

approval between project personnel, between different contractors, and between samplers<br />

and laboratory staff. Also described in this worksheet are the procedures that will be<br />

followed when any project activity requires real-time modification to achieve project goals,<br />

or when a SAP amendment is required. Procedures and personnel responsible <strong>for</strong> stopping<br />

work are also defined herein.<br />

Communication<br />

Drivers<br />

Point of Contact<br />

with Regulators<br />

Navy Quality<br />

Assurance<br />

Manage All<br />

Project Phases<br />

Manage All <strong>Field</strong><br />

Tasks<br />

<strong>Field</strong> Quality<br />

Assurance<br />

Daily <strong>Field</strong><br />

Progress Reports<br />

Responsible<br />

Affiliation<br />

Navy RPM<br />

Navy QAO<br />

AMEC<br />

Project<br />

Manager<br />

AMEC<br />

Construction<br />

Manager<br />

Navy ROICC<br />

AMEC<br />

Construction<br />

Manager<br />

Table 6-1. Communication Matrix<br />

Name<br />

Angela Lind<br />

Narciso<br />

Ancog<br />

Mike Schulz<br />

Mark Maniaci<br />

Gary<br />

Munekawa<br />

David Smith<br />

Mark Maniaci<br />

Phone Number<br />

and/or e-mail<br />

619-532-0922<br />

angela.lind@navy.mil<br />

619-532-3046<br />

narciso.ancog@navy.mil<br />

505-821-1801<br />

mike.schulz@amec.com<br />

618-401-3758 (mobile)<br />

mark.maniaci@amec.com<br />

650-603-9834<br />

gary.munekawa@navy.mil<br />

650-603-9836<br />

david.r.smith2@navy.mil<br />

618-401-3758 (mobile)<br />

mark.maniaci@amec.com<br />

Procedure<br />

(timing, pathway to<br />

& from, etc.)<br />

All project documentation will be<br />

<strong>for</strong>warded by the Navy RPM to<br />

the regulators.<br />

RPM will notify BRAC Cleanup<br />

Team members including the<br />

EPA within 7 days of significant<br />

changes to the SAP.<br />

The QAO will coordinate with the<br />

Navy RPM and AMEC Program<br />

QCM.<br />

The AMEC Project Manager will<br />

direct and approve of all<br />

communication to the Navy<br />

RPM. The AMEC Project<br />

Manager will notify the Navy<br />

RPM of field changes or<br />

modifications by email within 24<br />

hours of first occurrence.<br />

Acts as alternate point of contact<br />

at AMEC in the absence of the<br />

Project Manager. Responsible<br />

<strong>for</strong> direct oversight of field<br />

sampling activities and<br />

en<strong>for</strong>cement of SAP Accident<br />

Prevention Plan (APP) and Site<br />

Health and Safety Plan (SHSP).<br />

Per<strong>for</strong>m QA that all field work is<br />

completed in accordance with<br />

contract and project<br />

requirements.<br />

The AMEC Construction<br />

Manager will send field progress<br />

reports to the AMEC Project<br />

Manager daily via email.<br />

Final Sampling and Analysis Plan<br />

Installation Restoration Site 29, Hangar 1<br />

Former Naval Air Station, <strong>Moffett</strong> <strong>Field</strong>, <strong>Moffett</strong> <strong>Field</strong>,<br />

Cali<strong>for</strong>nia<br />

DCN: AMEC-8816-0005-0039<br />

April 2010<br />

Page 6-1

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

Saved successfully!

Ooh no, something went wrong!