My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WORK PLANS
EnvironmentalHealth
>
EHD Program Facility Records by Street Name
>
R
>
ROTH
>
700
>
2900 - Site Mitigation Program
>
PR0542675
>
WORK PLANS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/17/2026 10:41:30 AM
Creation date
3/11/2025 2:50:43 PM
Metadata
Fields
Template:
EHD - Public
ProgramCode
2900 - Site Mitigation Program
File Section
WORK PLANS
RECORD_ID
PR0542675
PE
2954 - USEPA - SITE PROJECT
FACILITY_ID
FA0024553
FACILITY_NAME
SHARPE ARMY DEPOT
STREET_NUMBER
700
STREET_NAME
ROTH
STREET_TYPE
RD
City
LATHROP
Zip
95330
APN
19802001
CURRENT_STATUS
Active, billable
QC Status
Approved
Scanner
SJGOV\gmartinez
Supplemental fields
Site Address
700 ROTH RD LATHROP 95330
Tags
EHD - Public
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
395
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Fieldwork Documentation Field Standard Operating Procedure <br /> SWE-FSOP-001;Revision 1 Ahtna Southwest Environmental Operations <br /> 4.2.4 References to Locations <br /> This section applies to new locations. Established locations are referred to by the location name or code. <br /> Previously established locations are typically shown on site maps/figures. <br /> Whenever an activity (sample collection, field measurement/monitoring, etc.) is performed at a new <br /> location (i.e.,the location has not been surveyed and shown in a figure), mark the location with a survey <br /> stake or similar marker, a detailed description of the location must be recorded in the FLB/notepad or <br /> field form and accompanied by a photo, sketch, or point on an attached map as part of the daily field <br /> documentation package (sketches with accompanying photographs when appropriate, with north arrow <br /> and approximate scale). Record unusual site physical conditions or signs of contamination such as oily <br /> discharges, discolored surfaces, unusual odors, dead or distressed vegetation, including types of plants, if <br /> possible. <br /> 4.3 Notepads <br /> When notepads are used, the requirement and procedures for the FLB (Section 4.2) also apply to the <br /> notepad documentation. <br /> 4.4 Field Forms <br /> Field forms are used in addition to FLBs/notepads. Field forms are activity-specific and may be completed <br /> for each location/sample/well, etc., or one per field event as appropriate. Each form contains a heading <br /> block to bind the field form to the FLB/notepad. Field forms augment but do not replace the FLB/notepads. <br /> Avoid duplicating information recorded in the FLB/notepad and field form. <br /> The forms include space (check box, table cell, and underlined space) for recording the information <br /> necessary for the project to ensure complete and proper information is recorded. Each space must be <br /> completed on a field form, and if not needed, then struck out or listing "not applicable." Blank space can <br /> be misunderstood as missing information.Version-controlled template files of the forms are stored in the <br /> M:\Environmental\Quality Control Procedures\SWE Field Forms. <br /> Field forms may be modified for project-specific use with the SWE Quality Assurance Manager's approval. <br /> All unbound data documentation is a part of the field records and should be maintained with safe <br /> document handling and archiving procedures. These records should be recorded in the same manner as <br /> notes in the FLB/field notpad using black or blue waterproof, indelible ink, and on weatherproof paper as <br /> necessary (projects testing for PFAS cannot use products with fluorinated constituents). <br /> 4.5 Field Documentation Data Package <br /> After a short-term,specific event(e.g.,well installation,sample collection, landfill inspection,and similar), <br /> copies of the FLB pages and hardcopies of loose-leaf documentation and relevant correspondence(emails <br /> and phone records) should be organized assembled into an event-based data package. The package <br /> should include a cover page listing the Installation/Site, project number, and event description. <br /> The PL is responsible for the safe storage of the data package until project closeout.A copy of the package <br /> should be scanned and saved in the m:\\drive project folder. The scan file could replace other scanned <br /> files described in the project instructions (Section 4.0). <br /> Page 14 of 15 <br />
The URL can be used to link to this page
Your browser does not support the video tag.