Attachment_1_-_PWS.pdf

As of June 19, 2018

ATTACHMENT 1

PERFORMANCE WORK STATEMENT (PWS)

For

ENVIRONMENTAL DOCUMENTS

SPE600-18-R-0532

Contents

1.0. INTRODUCTION

1.1 General Description

2.0. BACKGROUND

2.1 DLA Energy Mission

3.0. SCOPE

3.1. General Scope of Work

3.2. Contract Specifications

4.0. STATUTORY REQUIREMENTS

4.1. General

5.0. PERFORMANCE REQUIREMENTS:

5.1. Staffing

5.2. Site Visit or Data Gathering (as appropriate)

5.3. Document Format Requirements

5.4. Draft Documents

5.5. Draft Final

5.6. Final Documents

5.7. Monthly Status Reports (MSR)

5.8. Meetings

APPENDICES

APPENDIX A - CONTRACT SPECIFICATIONS

APPENDIX B - KEY CONTRACTOR PERSONNEL

ENCLOSURES

ENCLOSURE (1) Copy of Document Comments Matrix

1.0. INTRODUCTION.

1.1 General Description

This PWS is for the Defense Logistics Agency (DLA) Energy contracted support for the preparation of environmental documents for DoD petroleum storage facilities worldwide. A four-year Requirements contract shall be awarded to support the completion of these required environmental documents. Once the contract is awarded, the Contracting Officer (CO) will issue a Task Order (TO) for each required task or project as needed. The PWS provides the overall scope and types of services for which specific work under Task Orders (TOs) will be issued.

2.0. BACKGROUND.

2.1 DLA Energy Mission

Defense Logistics Agency (DLA) Energy is the Department of Defense’s (DoD) Executive

Agent for bulk petroleum products and associated storage facilities. DoD Instruction 4140.25 and DoD Manual 4140.25 direct DLA to plan, program, manage and budget, in coordination with the Military Departments, for sustainment, restoration, modernization, maintenance, repair, and environmental compliance of bulk petroleum storage and distribution facilities including

Government-Owned/Government-Operated (GOGO) and Government-Owned/Contractor-

Operated (GOCO) Defense Fuel Support Points (DFSPs). This authority extends to DoD petroleum facilities within the United States (U.S.), the U.S. Territories, and DFSPs located in foreign countries. There are approximately 500 DoD petroleum facilities worldwide eligible for

DLA Energy funding support as outlined in DoD 4140.25-M. Many of these facilities are located on or near U.S. military installations. These fuel terminals can be equipped with, but not limited to, one or more of the following: aboveground and/or underground storage tanks, tank truck and rail car loading racks, piping systems, cross-country pipelines, marine piers, and flight line hydrant systems.

3.0. SCOPE.

3.1. General Scope of Work.

The contractor shall be responsible for developing, updating, revising, and/or completing technical amendments to environmental documents to include but not limited to: environmental condition of property reports (ECOPs) (e.g. Environmental Baseline Surveys (EBSs) ASTM

D6008-96 (2014); spill prevention, control, and countermeasures plans (SPCCs); spill prevention and response plans (SPRPs); facility response plans (FRPs); operations and maintenance (O&M) plans; etc. The current estimate is approximately 1-50 documents each year but could exceed that number as required.

Preparation of these documents may entail considerable research, analysis, data collection, proofreading, editing, and close coordination with federal, state, local, military, or foreign government regulatory agencies, and the end-user. In addition, the Government may require the

Contractor to conduct site visits to complete the environmental documents. When available, previous versions of the requested documents and other supporting documentation will be included as part of the requests for proposal.

3.2. Contract Specifications.

Additional contract specifications and considerations can be found at Appendix A.

4.0. STATUTORY REQUIREMENTS.

4.1. General.

The Contractor shall prepare environmental documentation in accordance with Federal, State and local laws and regulations. In addition, the contractor shall be required to prepare/update/create documents that comply with all applicable requirements for foreign locations where DLA conducts operations to include: Final

Governing Standards (FGSs), Standard of Forces Agreements (SOFA), or other laws, rules, regulations, or directives negotiated between the United States Government and a host nation.

5.0. PERFORMANCE REQUIREMENTS:

5.1. Staffing.

The Contractor’s staff must be listed and have the specific qualifications in accordance with

(IAW) Appendix B – Key Contractor Personnel

5.2. Site Visit or Data Gathering (as appropriate).

5.2.1. Site Visits. The Contractor may be required to conduct site visits as required by the

Government issued TO. In addition, the Contractor shall schedule the site visit during the kick-off meeting and all stakeholders identified by the Government will be notified of the site visit dates, schedule, and what is required (Stakeholder(s) are the program manager or installation personnel requesting the document(s) as described per the TO). The Contractor shall ensure any additional stakeholders identified during the site visit are engaged in the process. Should identified stakeholders not be available during the site visit, the contractor shall notify the

Contracting Officer’s Representative (COR) as soon as possible and shall provide an explanation on how the issue will be resolved.

5.2.2. Data Gathering. When a site visit is not required, the Contractor may be required to conduct research and obtain data as required by the Government issued TO. An example of data gathering would be an EPCRA Form R report. The Contractor shall gather data in order to complete the report. The tasks required to complete the TO shall be completed within specific task completion timelines. The Contractor shall ensure all identified stakeholders are notified of the data gathering process and what is required to accomplish the task. The Contractor shall document the interaction with the stakeholders and provide the name of the stakeholder and note the date(s) contacted. In addition, any additional stakeholders identified through the data gathering process will also be contacted to ensure all applicable information is obtained. Should identified stakeholders not be available during the data collection process, the contractor shall notify the COR as soon as possible and the contractor shall provide an explanation on how the issue will be resolved.

5.3. Document Format Requirements.

The Contractor shall provide all documents, drawings, site maps, and other deliverables prepared under this contract in an electronic format or hard copy as specified by the TO. The electronic formats to be used for site maps and drawings will be one of the following: AutoCAD, GIS format, or Adobe Acrobat. The electronic format for all text portions of documents will be one of the following: Microsoft (MS) Word or MS Excel, in addition to being provided in Adobe

Acrobat. The source file for all electronic files must be included as part of all deliverable items and shall be editable. Electronic file names shall not exceed 50 characters to include sub folders.

Large electronic files shall be sent via the U.S. Army Aviation and Missile Research

Development and Engineering Center (AMRDEC) Safe Access File Exchange (SAFE) https://safe.amrdec.army.mil/safe or other DLA specified and approved file exchange service.

The AMRDEC exchange shall include in the description, at a minimum, the TO Number, Sub-

Task notation (if applicable - A, B, C, etc.), site name, plan type (EBS, SPCC, SWPPP, etc.), and plan status (draft, final, etc.).

5.4. Draft Documents.

The Contactor shall draft documents and deliver to the COR for review no later than 60 days after TO award, unless the TO specifically requires an alternate timeline based on requirement needs. A copy of the Document Comments Matrix, provided as Enclosure (1), shall be included with all draft documents and reviews must be accomplished and corrections made as detailed in the TO. If the Government has no comments, the COR will provide the contractor documentation of approval of the draft document. All pages of the document shall be marked

“For Official Use Only” and all main bodies of draft documents shall contain continuing line numbers to assist in review. Preparation of these documents may also include a requirement for developing and/or editing any site maps and/or drawings required to be included in the applicable documents being updated or developed. The draft document shall be developed as to require minimum feedback and changes (e.g. be free of typographical errors, contain accurate and sufficient information, etc.). The draft stage of the document is not complete until the COR provides the Contractor written approval of the document. At no additional cost to DLA, the

Contractor will be required to complete as many corrections and draft documents as necessary to address the comments made by the government until the draft document is approved by the

COR.

5.4.1. Receipt of Comments and Incorporation of Comments. The contractor shall schedule and conduct a comment resolution meeting with the COR to ensure all comments are understood and appropriately addressed.

5.5. Draft Final.

The Contractor shall provide the draft final to the COR and stakeholder no later than 10 business days of receipt of the COR’s written approval of the draft document. If the Government has no comments, the COR will provide the contractor written documentation of approval of the final document. Performance under this element will not be complete until the COR provides the

Contractor written approval of the draft final document. The Contractor shall, at no additional cost to the government, accomplish all corrections based on previously submitted comments and then provide proof of correction to the COR that the correction was properly remedied. Should the COR agree, the corrections can be documented by the submission of impacted section/pages.

All pages of the draft final document shall be marked “For Official Use Only” and all main bodies of the documents shall contain continuing line numbers to assist in review.

5.5.1. Additional Changes. Only the CO is authorized to make changes to the Task Order.

5.6. Final Documents.

The Contractor shall provide the final version of the document no later than 10 days after receipt of government concurrence with the draft final document or as specified in the TO. The

Contractor shall provide the quantity and type (electronic and/or hard copy(ies)) of the final deliverable as described in the TO. Electronic files shall include both MS Word (MS Excel files if applicable) and PDF versions. Line numbers shall be removed from all final deliverables. All pages of the document shall be marked “For Official Use Only” and the final document shall not contain any Contractor information or logos except on the cover page which could be removed without affecting the substance of the document.

5.6.1. Regulatory Review. The Contractor, at no additional cost to the Government, and as detailed in the TO, shall be responsible for coordinating regulatory review of the draft document, to obtain regulatory approval. The Contractor will coordinate this process with the COR. The regulatory coordination and approval process for each TO may extend beyond the term of the contract in accordance with FAR Clause 52.216-22 but shall not exceed December 31, 2025.

5.7. Monthly Status Reports (MSR).

The Contractor shall provide to the COR, on the first business day of each month, a monthly status report on each incomplete TO.

5.7.1. Track Progress. The Contractor shall track the progress of the TOs and invoicing. The

MSR shall be a cumulative report. The MSR shall include, at a minimum, the following:

contract number; task order number; date TO issued; sub tasks (if applicable); site name;

program manager name (phone and email); plan type (e.g. SPCC, FRP, etc.); due dates for all deliverables, invoice status (with original TO, sub task if applicable) amount and cumulative totals invoiced), and a comments section. All due dates shall be color-coded and the color-code should be: green – due dates will be met; yellow – due dates might not be met; and red - due dates will not be met. All items coded yellow or red shall include information within the comment section to explain and justify the delay and what actions the Contractor will take to minimize the impact of the delay. All extensions shall be requested through the CO within (5) business days of the due date and a new due date shall be negotiated with the site personnel to ensure their requirements will be met. The comments section shall also contain any other notable information to assist in understanding the status of the task. Please note: A notation of a delay in completion of a TO or a milestone within a TO within the monthly report does not take the place of properly notifying the COR, Contract Specialist (CS) and/or CO directly before a due date is not met. Any request for an extension of the completion of a TO or a milestone within a TO must be requested in writing by the Contractor (5) business days prior to the due date and approved in writing by the CO prior to the due date.

5.8. Meetings.

5.8.1. Post Contract Award Kick-Off Meeting and Minutes. Within five (5) business days of contract award, the Contractor shall schedule and conduct a Post Award Kick-Off Meeting between, at a minimum, the CO, CS, and COR, to discuss the terms of the contract and to establish a timeline for the actions required under the contract.

5.8.2. Ad Hoc Meetings and Minutes. These are Ad Hoc meetings and not post contract award or post TO award meeting. The CO may require the Contractor’s Program Manager

(PM) to meet with the CO, and/or other government personnel such as the CS, COR and stakeholders as deemed necessary in accordance with Federal Acquisition Regulation (FAR)

Subpart 42.5. The Contractor may request a meeting with the CO when it believes such a meeting is necessary. At the periodic progress meetings, the CO will apprise the Contractor of how the government views the Contractor’s performance and the Contractor will apprise the government of problems, if any, being experienced. Appropriate action will be taken to resolve outstanding issues. If the Contractor does not concur with any of the findings or decisions discussed during any meetings, such non-concurrence shall be provided, in writing, to the CO, in conjunction with the meeting minutes. Meeting minutes shall be prepared by the contractor for any meeting with the CO and the meeting minutes shall be provided to the government within (5) business days. The minutes shall include, at a minimum, the following:

5.8.2.1. Attendees (name, phone number, email address, title, and organization).

5.8.2.2. Absent identified stakeholders, if applicable: (name, phone number, email address, title, and organization).

5.8.2.3. Provide details of meeting topics (include brief description and outcome/decision/assumptions).

5.8.2.4. Provide name of individual preparing meeting minutes.

5.8.2.5. Request comments on draft from all attendees and resolve the issues/and concerns

5.8.2.6. Convert the document to pdf and prepare the document for electronic signature of contract PM and the CO.

5.8.2.7. Provide a copy of the final document to all attendees.

5.8.3. Task Order Kick-Off Meeting and Minutes. The Contractor shall prepare and maintain minutes of the TO kick-off meeting between the Contractor, COR, and other government stakeholders identified in the TO or during the meeting.. Should a site visit be required per the

TO, the site visit shall be scheduled during the TO kick-off meeting to meet the needs of the stakeholders. Any stakeholders not participating in the meeting shall be notified of the site visit and what is required of them to accomplish the task by the contractor. Should data gathering be required, the data gathering process should be defined during the TO kick-off meeting. Any stakeholders that are required to support the data gathering effort that do not participate in the meeting shall be notified of the timeline of the effort and what will be required of them. The minutes shall be submitted to the COR for review within five (5) business days of the meeting.

Should one kick-off meeting be held for multiple TOs, the kick-off meetings minutes will be separate and distinct documents. The minutes will be signed by the Contractor’s PM. The minutes shall include, at a minimum, the following:

5.8.3.1. Contract number, TO number, Contractor name, location name, document type(s), and date

5.8.3.2. Attendees (name, phone number, email address, title, and organization).

5.8.3.3. Document any absent Identified stakeholders: (name, phone number, email address, title, and organization).

5.8.3.4. Provide details of meeting topics (include brief description and outcome/decision).

5.8.3.5. Provide name of individual preparing meeting minutes.

5.8.3.6. Provide name and contact information for the contract task order PM and sub task

PM(s) if applicable.

5.8.3.7. Request comments on draft from all attendees and resolve the issues/and concerns raised by attendees as directed by the Contractor. Note, only the CO is authorized to direct contractor performance.

5.8.3.8. Provide a copy of final to all identified stakeholders.

APPENDICES

APPENDIX A - CONTRACT SPECIFICATIONS

A-1.0. CONTRACTOR DELIVERABLES SCHEDULE. Except for final documents, if requested in hard copy form, deliverables shall be electronic as described within this PWS.

Alternate deliverable schedules must be reflected in the TO or in writing from the CO. The deliverables are required in accordance with the following schedule:

Deliverable Frequency Submit to:

Post Contract Award Kick-

Off Meeting Minutes

Within 5 business days of contract award

CS

Ad Hoc Meeting Minutes Within 5 business days of meeting

CS

Task Order Kick-Off Meeting

Minutes

Within 5 business days of meeting.

COR/Identified stakeholders in TO

Monthly Status Reports Due 1st business day of each month

COR

Draft Document

As Noted in PWS or TO COR/Identified stakeholders in TO

Draft Final

Within 10 business days of receipt of comments

COR/Identified stakeholders

Final Document

Final documents received by the Government within 10 business days after receipt of government concurrence with draft final.

COR/Identified stakeholders

A-2.0. QUALITY ASSURANCE SURVEILLANCE PLAN. The environmental documents shall be complete and in accordance with industry standards and in compliance with all Federal, state and local laws and regulations in addition to host nation requirements, where applicable.

Contractor performance will be measured as documented in A-2.1. below.

A-2.1. Performance Summary Requirements

Performance Objective Performance Standards Acceptable Quality

Level

Meet prescribed deadlines The Contractor shall meet all deadlines outlined in the PWS and TO.

100% compliant

Contractor will ensure they have an understanding of the requirement.

The Contractor shall maintain sufficient contact with the COR, other government personnel as authorized in the TO, and the

CO to ensure they have a complete

Maintain overall average satisfactory rating on feedback forms for this understanding of the requirement and expectations of what is should be included in the document. Note, only the CO is authorized to direct contractor performance.

objective. COR will provide the

Contractor feedback forms.

Conduct site visit as scheduled.

The Contractor shall ensure all installation access requirements are completed prior to travel. Contractor shall meet with COR, CO and all personnel identified by the TO.

Contractor shall remain in contact with

COR during the site visit should the date/time for specific meetings change due to unforeseen circumstances. Note, only the CO is authorized to direct contractor performance.

Maintain overall average satisfactory rating on stakeholder feedback forms for this objective.

The draft document shall be complete and in accordance with the requirements dictated by the TO and in accordance with the applicable laws, rules, and regulations.

Require minimum feedback and changes due to proper preparation and data gathering (e.g. contain accurate and sufficient information and have no typographical errors, etc.).

Maintain overall average satisfactory rating on stakeholder feedback forms for this objective.

Final draft document shall be complete and in accordance with the TO.

Final draft document shall include all mitigated comments from the government and shall be free from typographical errors.

100% compliant

Final document shall be complete and in accordance with the TO.

Final document shall be in compliance with all applicable laws, rules, regulations, and directives and reflect any errors noted in the draft final, if any.

100% compliant

Ensure Customer

Satisfaction

Documents shall be prepared in accordance with the TO. All Contractor staff shall perform in a professional and business-like manner with no validated stakeholder complaints.

Maintain overall average satisfactory rating on customer feedback forms.

A-3.0. PERSONNEL

A-3.1. Government Personnel

A-3.1.1. Contracting Officer (CO). The CO is the person who can bind the Federal

Government of the United States to this contract. This is limited to the scope of authority delegated to the CO.

A-3.1.2. Contract Specialist (CS). The CS supports the CO and provides government contract oversight.

A-3.1.3. Contracting Officer’s Representative (COR). The contract COR shall function as the Government PM for this contract. The contract COR is a government official appointed in writing by the CO who provides technical direction, clarification and guidance with respect to the contract specifications and statement of work. The COR shall not direct or request work outside of valid TO requirements.

A-3.1.4. Installation stakeholders. A list of installation stakeholders shall be provided to the

Contractor for each TO. It is the responsibility of the Contractor as noted in the TO and as directed by the CO and COR, as authorized, to ensure all stakeholders identified by the government are engaged in the document development and the Contractor will document the communications such as through email and/or memorandums for the record. Changes to the draft, draft final, or final document due to the failure of the Contractor to engage with all of the stakeholders would be completed at the Contractor’s expense. The stakeholders are not allowed to authorize additional work or any changes to the requirements of the PWS and TO and the

Contractor shall only accept any changes to any of the terms and/or conditions of the contract from the CO. Stakeholders could be Contractors working on behalf of the installation.

A-3.2. Contractor Personnel.

Contractor personnel required in Addition to Personnel Staffing Identified in Appendix B

A-.3.2.1. Contractor Program and Task Order Program Managers. The Contractor shall assign (1) Contract Program Manager and (1) Task Order Program Manager for each TO. The contractor is authorized to designate the same contractor employee to serve as both the Contract

Program Manager and the Task Order Program Manager.

A-4.0. GENERAL INFORMATION

A-4.1. Hours and Days of Operation.

The Contractor may be required to travel to installations within different time zones and the

Contractor will be expected to defer to, and work within, the installation’s normal working days/times. It is the responsibility of the Contractor to coordinate with those personnel identified in the Task Order for the site visit.

A-4.2. Place of Performance.

Site visits may be required as stated in 5.2.1, but the Contractor may perform all other work at the Contractor’s normal location of operations.

A-4.3. Physical Requirements and Work Environment.

Work performed in accordance with this PWS could require travel to remote locations worldwide and could include field work where inclement weather could be a factor and field location would involve normal day-to-day risks and discomforts. The Contractor is required to ensure that employees are familiar with and follow safety precautions while visiting installations.

A-4.4. Government-Owned Documents.

U.S. Government records, copies of original results and reports, verified original data, corrected data, and corrected supporting final reports must be maintained by the Contractor during the course of the TO, but remain the property of the U.S. Government. These files/results must be surrendered to the COR upon request and/or task order close-out. The Contractor is responsible to comply with all applicable Department of Defense (DoD) security regulations and procedures during the performance of this contract. The Contractor shall not disclose and must safeguard computer systems and data, Privacy Act data, and government personnel work products that are obtained or generated in the performance of this contract. This includes dissemination of protocols and papers not generally available through the public literature. Questions on this requirement may be directed to the CO through the COR.

A-4.5. Correspondence.

All correspondence shall include the Contractor name, task order number, site name, site city, site state, and document type(s).

A-4.6. Operations Security (OPSEC) and Safety.

A-4.6.1. Disclosures. Neither the Contractor nor any of its sub-contractors shall disclose or cause to be disseminated any information concerning any installation or the operations of military activities. Such action(s) could result in violation of the contract and possible legal action.

A-4.6.2. Conduct Business. The Contractor shall only conduct business with U.S. Government personnel or DLA-funded contract personnel. Only the CO shall direct the Contractor or authorize actions. The CS shall support the CO for this contract and the COR shall be the day-to-day DLA point of contact.

A-4.6.3. Common Access Cards (CAC). Contract employees are not eligible to receive a CAC from the DLA. It is the Contractor’s responsibility to ensure they are eligible to receive a visitor’s pass to visit an installation. The inability of Contractor personnel to access an installation due to lack of pre-planning and coordination will result in the Contractor assuming the cost of any travel associated with not being able to conduct the site visit. Should the

Contractor be able to show due diligence in obtaining proper advance permission for access and access is denied upon arrival at no fault of the Contractor, the Contractor can request from the

CO, in writing, reimbursement for such travel expenses.

A-4.6.4. Identification of Contractor employees. To avoid creating an impression that they are government officials, all Contractor personnel will identify themselves as contract personnel when attending meetings, visiting at installations, or otherwise communicating, orally or in writing, or working in other situations where their Contractor status is not obvious to third parties. The Contractor must also ensure all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.

A-4.6.5. Right to Inspect. While on an installation, government personnel have the right to inspect Contractor employee documentation for security violations at any time during the term of the contract.

A-4.6.6. Cellular Phone and Camera Usage on DoD Installations. The Contractor shall be aware of, and comply with, all restrictions concerning the use of cellular phones and cameras on all DoD installations.

A-4.7. Travel.

A-4.7.1. Travel Costs. Travel costs under CLIN 0012 will be evaluated at the Task Order level as part of the Contractor’s Task Order proposal.

A-4.7.1.2. Performance under this contract may require travel by Contractor personnel. If travel is required, the Contractor is responsible for making all needed arrangements for their personnel.

A-4.7.1.3. Travel costs for transportation, lodging, meals, and incidental expenses shall be proposed and evaluated as firm fixed price at the Task Order level. A breakdown of proposed costs along with any applicable airline or rental car quotations shall be included in Task Order proposals.

A-4.7.2. Travel Advisories. The Contractor is responsible for monitoring the United States

Government State Department Travel Alerts and Warnings Website at https://travel.state.gov/content/passports/en/alertswarnings.html for any travel alerts and warnings. Should there be an issue or concern with travel to any of the locations associated with this contract, the Contractor shall notify the COR as soon as possible.

A-4.7.3. Driver’s Licenses. The Contractor shall ensure contractor personnel have the proper driver’s licenses, to include international driver’s licenses, when public transportation is inadequate to support required work.

https://travel.state.gov/content/passports/en/alertswarnings.html

APPENDIX B - KEY CONTRACTOR PERSONNEL

B-1.0. PROJECT MANAGER. Advanced degree and/or graduate of a four-year college or university accredited by an accrediting institution recognized by the U.S. Department of

Education majoring in engineering, physical sciences, or other technical field, and at least ten years of specialized work experience involving environmental programs, proposal preparation and development, cost estimating, supervisory experience, project management, facilities and operations, data analyses, employee training, business software, and technical writing.

Professional certifications and licenses in technical fields are highly desirable.

B-2.0. SENIOR ENVIRONMENTAL CONSULTANT. Graduate of a four-year college or university accredited by an accrediting institution recognized by the U.S. Department of

Education majoring in physical, biological, or natural science and at least ten years of specialized experience involving environmental programs, natural resources management, regulatory review and analysis, hazardous waste management, oil spill response planning, computer modeling, statistics, spreadsheets, and technical writing.

B-3.0. PROFESSIONAL ENGINEER. Graduate of a four-year college or university accredited by an accrediting institution recognized by the U.S. Department of Education majoring in engineering with professional registration and at least three years of specialized work experience involving project design, project planning and management, cost estimating, construction site management, field work, and computer aided design. Specialized experience in writing, reviewing, and certifying Spill Prevention, Control, and Countermeasure (SPCC) plans.

B-4.0. ENGINEERING TECHNICIAN. Graduate of a two-year college or vocational school majoring in engineering or two years of specialized experience involving engineering measurements, instrumentation, field surveys, studies, data collection and analysis, and project support.

B-5.0. ENVIRONMENTAL SCIENTIST. Graduate of four-year college or university majoring in physical, biological, or natural science and at least three years of specialized experience involving environmental programs, natural resources management, regulatory review and analysis, hazardous waste management, oil spill response planning, computer modeling, statistics, spreadsheets, and technical writing.

B-6.0. ENVIRONMENTAL TECHNICIAN. Graduate of a two-year community college accredited by an accrediting institution recognized by the U.S. Department of Education with an associate’s degree in science or two years work experience involving environmental protection programs, data collection, field studies, sample collection, data entry, hazardous material and solid waste management.

B-7.0. TECHNICAL WRITER/EDITOR. Graduate of a four-year college accredited by an accrediting institution recognized by the U.S. Department of Education with three years demonstrated experience in the preparation, editing, and review of comprehensive technical documents, reports, and publications.

B-8.0. MAPPING TECHNICIAN. Graduate of a college, university, vocational school accredited by an accrediting institution recognized by the U.S. Department of Education, or applicable professional industry-recognized course with a specialty in surveying, drafting, cartography, or geology. At least two years of work experience as a mapping technician required. Mapping technician should be proficient with geographic information systems (GIS), AutoCAD, and Adobe Acrobat.

B-9.0. OFFICE AUTOMATION SPECIALIST. Formal computer training from a public school, college, and/or university accredited by an accrediting institution recognized by the U.S.

Department of Education and at least two years specialized experience with Microsoft Office, desktop publishing, database administration, PowerPoint presentations, illustrations and charts, etc.

ENCLOSURES

ENCLOSURE (1) Copy of Document Comments Matrix

Instructions:

Column A – Comment #

Used to track the number of comments. Manually enter the comment number 1,2,3, etc.

Column B – SOURCE

Reviewer's Office Symbol (Can be abbreviated here but please include full office name spelled-out at bottom of matrix for clarification)

Column C – REVIEWER (INPUT BY)

Include reviewer name, phone number, and email address

Column D – COMMENT TYPE

C – Critical (Contentious issue that will cause non-concurrence with publication)

S – Substantive (Factually incorrect material)

M – Major (Incorrect material that may cause non-concurrence with publication)

A – Administrative (grammar, punctuation, style, etc.)

Column E – PAGE

Please provide the page number printed at the bottom page (e.g. iii, 1-2, 3-1, etc) or make note if you will be using the actual page number as counted by the computer.

Column F – PARA

Please count down the number of paragraphs

Column G – LINE

Please count down the number of lines in the paragraph (not sentences, but lines within the paragraph)

Column H – COMMENT/SUGGESTED CHANGE

Provide as much detail with your comment as possible. This will ensure your comment is put in proper context and is understood.

Column I - COMMENT/CHANGE RATIONALE

Provide a concise and objective explanation of the rationale for the comment to include regulatory references, etc., when applicable.

Column J – ADJUDICATION DECISION (to be used in reconciliation)

A - Accept

R – Reject

M - Accept with modification

Column K - RATIONALE FOR ADJUDICATION DECISION

This column will be used to explain the rationale for all rejection and exceptions with modification actions.

Column L - ADJUDICATION/RECONCILIATION POC NAME, NUMBER/EMAIL

This column will identify the person reconciling comments received.