Section_SF_1449_Final_May_10_2016.docx

M68909-16-Q-7621 Page 53 of 53

Section SF 1449 - CONTINUATION SHEET

3.1 Copyediting and Proofreading

FFP

Copyediting and Proofreading IAW PWS. Period of Performance: 03 June 2016 through 02 June 2017 FOB: Destination

NET AMT

3.2 Project Management Support

Project Management Support IAW PWS. Period of Performance: 03 June 2016 through 02 June 2017

NET AMT

3.3 Test Process Development Support

Test Process Development Support IAW PWS. Period of Performance: 03 June 2016 through 02 June 2017

NET AMT

3.4 Operations Support

Operations Support IAW PWS. Period of Performance: 03 June 2016 through 02 June 2017

NET AMT

3.5 Meeting Support

Meeting Support IAW PWS. Period of Performance: 03 June 2016 through 02 June 2017

NET AMT

3.6 Technical Department Records Mgmt

Technical Department Records Management IAW PWS. Period of Performance: 03 June 2016 through 02 June 2017

NET AMT

3.7 Technical Department Training

Technical Department Training Coordination IAW PWS. Period of Performance: 03 June 2016 through 02 June 2017

NET AMT

3.8 Lab Technician Support

Lab Technician Support IAW PWS. Period of Performance: 03 June 2016 through 02 June 2017

NET AMT

CDRLS for Base Year

NET AMT

FFP

Copyediting and Proofreading IAW PWS. Period of Performance: 03 June 2017 through 02 Jun 2018

NET AMT

FFP

Project Management Support IAW PWS. Period of Performance: 03 June 2017 through 02 Jun 2018

NET AMT

FFP

Test Process Development Support IAW PWS. Period of Performance: 03 June 2017 through 02 Jun 2018

NET AMT

FFP

Operations Support IAW PWS. Period of Performance: 03 June 2017 through 02 Jun 2018

NET AMT

FFP

Meeting Support IAW PWS. Period of Performance: 03 June 2017 through 02 Jun 2018

NET AMT

FFP

Technical Department Records Management IAW PWS. Period of Performance: 03 June 2017 through 02 Jun 2018

NET AMT

FFP

Technical Department Training Coordination. Period of Performance: 03 June 2017 through 02 Jun 2018

NET AMT

FFP

Lab Technician Support IAW PWS. Period of Performance: 03 June 2017 through 02 Jun 2018

NET AMT

NET AMT

FFP

Other Direct Costs (ODC). Travel charges are limited and shall be IAW FAR 31.205-46

NET AMT

FFP

Copyediting and Proofreading IAW PWS. Period of Performance: 03 June 2018 through 02 June 2019

NET AMT

FFP

Project Management Support IAW PWS. Period of Performance: 03 June 2018 through 02 June 2019

NET AMT

FFP

Test Process Development Support IAW PWS. Period of Performance: 03 June 2018 through 02 June 2019

NET AMT

FFP

Operations Support. Period of Performance: 03 June 2018 through 02 June 2019

NET AMT

FFP

Meeting Support IAW PWS. Period of Performance: 03 June 2018 through 02 June 2019

NET AMT

FFP

Technical Department Records Management IAW PWS. Period of Performance: 03 June 2018 through 02 June 2019

NET AMT

FFP

Technical Department Training Coordination. Period of Performance: 03 June 2018 through 02 June 2019

NET AMT

FFP

Lab Technician Support IAW PWS. Period of Performance: 03 June 2018 through 02 June 2019

NET AMT

NET AMT

FFP

NET AMT

FFP

Copyediting and Proofreading IAW PWS. Period of Performance: 03 Jun 2019 through 02 June 2020

NET AMT

FFP

Project Management Support IAW PWS. Period of Performance: 03 Jun 2019 through 02 June 2020

NET AMT

FFP

Test Development Support IAW PWS. Period of Performance: 03 Jun 2019 through 02 June 2020

NET AMT

FFP

Operations Support IAW PWS. Period of Performance: 03 Jun 2019 through 02 June 2020

NET AMT

FFP

Meeting Support IAW PWS. Period of Performance: 03 Jun 2019 through 02 June 2020

NET AMT

FFP

Technical Department Records Management IAW PWS. Period of Performance: 03 Jun 2019 through 02 June 2020

NET AMT

FFP

Technical Department Training Coordination IAW PWS. Period of Performance: 03 Jun 2019 through 02 June 2020

NET AMT

FFP

Lab Technician Support IAW PWS. Period of Performance: 03 Jun 2019 through 02 June 2020

NET AMT

NET AMT

FFP

NET AMT

FFP

Copyediting and Proofreading IAW PWS. Period of Performance: 03 Jun 2020 through 02 June 2021

NET AMT

FFP

Project Management Support IAW PWS. Period of Performance: 03 Jun 2020 through 02 June 2021

NET AMT

FFP

est Process Development Support IAW PWS. Period of Performance: 03 Jun 2020 through 02 June 2021

NET AMT

FFP

Operations Support IAW PWS. Period of Performance: 03 Jun 2020 through 02 June 2021

NET AMT

FFP

Meeting Support IAW PWS. Period of Performance: 03 Jun 2020 through 02 June 2021

NET AMT

FFP

Technical Department Records Management IAW PWS. Period of Performance: 03 Jun 2020 through 02 June 2021

NET AMT

FFP

Technical Department Training Coordination. Period of Performance: 03 Jun 2020 through 02 June 2021

NET AMT

NET AMT

SECTION C DESCRIPTION

Performance Work Statement Amphibious Vehicle Test Branch (AVTB) Technical Support Services

1 INTRODUCTION

1.1 Background

The Amphibious Vehicle Test Branch (AVTB) provides Test and Evaluation (T&E) of amphibious and ground combat vehicles to Marine Corps Systems Command (MCSC) and Program Executive Officer Land Systems (PEO LS). AVTB is responsible for the T&E of combat vehicles throughout the vehicle lifecycle. AVTB applies deliberate, documented processes in the execution of combat vehicle tests which are continuously under development and improvement.

Upcoming events include the Assault Amphibious Vehicle (AAV) reserve buoyancy test, personnel egress test, hull measurement, the Reliability, Availability, and Maintainability (RAM) baseline assessment. Additionally, AVTB will support vendor demonstrations and studies for the Marine Personnel Carrier (MPC). As a component of the current tactical ground vehicle strategy for the Marine Corps, the vendor demonstrations and studies will aid decision makers with future source selection decisions.

T&E projects at AVTB follow a standardized business process. This process consists of seven phases (Initiate, Plan, Prepare, Execute, Analyze, Report, and Close). The contractor will assist with all phases, depending on project scope, duration, and technical requirements. AVTB typically conducts between 10 and 20 projects per year.

1.2 Scope

The scope of this effort is to provide technical writing and project management for AVTB engineering tasks and test events. In addition to technical writing and project management, the Electronics & Metrology lab, one of the seven main functional areas at AVTB, requires reinforcement of the current electronics technical support, which supports the organizational mission by providing instrumentation, data acquisition, and audio/video recording. The electronic technician holds primary responsibility for the installation, maintenance, and operation of these systems discussed in the instrumentation statement below:

Instrumentation – The term instrumentation refers to the electronic and electromechanical sensors and systems used to measure and record physical phenomena in the form of usable data. Instrumentation includes, but is not limited to, pressure transducers, current meters, tachometers, flow meters, accelerometers, thermocouples, inclinometers, spectrometers, telemetry systems, load cells, survey equipment, video capture systems, and data acquisition systems. Instrumentation is used to acquire data from vehicle reactions over various terrains and in various environmental conditions. Parameters measured include temperature, fluid pressure, fluid flow, air pressure, mechanical pressure, mechanical movement, position, inclination, control and maneuverability, tracking, speed, ride quality, and vehicle behavior on land and water.

2 APPLICABLE DOCUMENTS

2.1 Compliance Documents

The following documents are applicable to this PWS:

a. American National Standards Institute (ANSI), Z39.18-2005 (R2010), Scientific and Technical Reports – Preparation, Presentation, and Preservation, 13 May 2010.

b. Department of the Navy, SECNAV M-5216.5, Correspondence Manual, June 2015.

c. HQMC, MCO 5216.20A, Marine Corps (MC) Supplement to the Department of the Navy (DON) Correspondence Manual, 15 August 2013.

d. HQMC, MCO 4733.1C, Marine Corps Ground Test, Measurement and Diagnostic Equipment (TMDE) Calibration and Maintenance Program (CAMP), 23 June 2015.

e. NISPOM, DOD Directive 5220.22-M

2.2 Resources

The following resources will be provided to the contractor:

1. Government Printing Office Style Manual

1. AVTB style and formatting guidance

1. Access to the digital AVTB Process Asset Library

1. Access to the digital AVTB Project Center

1. Instructions for updating information on the AVTB Project Center

1. Instructions for the application of the AVTB file naming convention

1. Computer program for converting Level 1 data to Level 2 data

1. Access to the AVTB Records Management System.

3 PERFORMANCE REQUIREMENTS

The contractor shall report all contractor labor hours (including subcontractor hours), required to perform the services provided under this contract with AVTB, via a secure data collection site. The contractor is required to fill in all required data fields using the following web address: https://doncmra.nmci.navy.mil.

Reporting inputs will be for the labor executed during the period of performance for each government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data for each FY shall be reported by the contractor no later than 31 October of each calendar year. Contractors may direct questions to the help desk at: https://doncmra.nmci.navy.mil.

3.1 Copyediting and Proofreading

The contractor shall edit AVTB test planning, test managing, and test reporting documents. The AVTB civil service employees will author the documents and forward written copies, or proof sheets, to the contractor for proofreading. The contractor shall return the documents (CDRL A001) to the author with corrections and comments within two days of receipt. The contractor-edited documents shall be technically accurate and grammatically correct. For planning purposes, the typical workload involves processing between 1 and 6 documents per week, ranging in length from 1 to 50 pages for each document.

3.2 Project Management Support

3.2.1 During the Initiate Phase of Every AVTB T&E Project

The contractor shall update the four below listed CDRLS to reflect the information provided by AVTB civil service employees regarding the new project.

CDRLS are as follows:

Integrated Project Schedule (IPS) – used to reflect a new project with the default planning duration in accordance with CDRL A003.

AVTB Master PowerPoint Slides – used to maintain the list of potential projects, project status, and pending test requests in accordance with CDRL A004.

Charter Template – used to reflect current details about the project in accordance with CDRL A002.

Project Launch/Closeout Checklist – used to reflect the status of the tasks in accordance with CDRL A005.

After the CDRLs are completed, the contractor shall notify AVTB Operations Officer of the project launch.

3.2.2 During the Close Phase of Every AVTB T&E Project

The contractor shall ensure archiving Project Data is complete when reviewed and accepted by the Project Manager. The contractor shall apply proper naming conventions as detailed in AVTB file naming convention instructions to all project documents, populate required metadata fields, and upload the documents to the AVTB records management system, per the instructions for updating information on the AVTB Project Center.

The contractor shall update the four CDRLS listed in (paragraph 3.2.1), to reflect the information provided by AVTB civil service employees regarding the closed project. The contractor shall notify AVTB Operations Officer of the project closure within one day when action is complete.

3.3 Test Process Development Support

During all process phases, except the initiate and close phases, the contractor shall update and proofread existing forms, templates, checklists, and flow diagrams authored by AVTB civil service employees. The contractor shall proofread and apply formatting standards listed in paragraph 2.2 (e) & (f) to the process assets in preparation for the AVTB internal review process. AVTB generates approximately three new process assets per month.

The contractor shall facilitate the approval and launch of process assets by updating the signature documentation, scanning the documents after approving signatures are applied, and uploading the documents to the AVTB Process Asset Library within five working days of receipt of signature documentation, as listed in Paragraph 2.2 above.

3.4 Operations Support

During all process phases, except the initiate and close phases, the contractor shall transfer project summary information from the weekly Project Sync Working Group (PSWG) slides to the executive level Branch Biweekly slides to facilitate staff coordination and decision support.

3.5 Meeting Support

The contractor shall upload the audio recordings of meetings, provided by AVTB civil service employees, to the AVTB audio repository, listed in paragraph 2.2. above, to support configuration management and decision traceability.

The contractor shall update the existing master list of action items provided by the Operations Officer for the weekly meetings and keep running tallies of action items from previous weeks.

The contractor shall archive meeting records by uploading them to the AVTB records management system, listed in paragraph 2.2 above, or other designated areas.

Per CDRL 004, the contractor shall update the Master PowerPoint Slides template to maintain consistency across the organization prior to the meetings scheduled below.

The following list provides an estimate for the meeting volume at AVTB:

Project Sync Working Group Meetings (one per week) Process Review Committee Meetings (one per week) Branch Biweekly Review Meetings (two per month) Test Readiness Reviews (approximately two per month) Ad Hoc Meetings (approximately two per month) Project Management Team Meetings (approximately two per month)

3.6 Technical Department Records Management

The contractor shall organize and manage the Technical Department’s paper and electronic records. The Technical Department’s electronic records include files on the Technical Department network drives, SharePoint portal spaces, and Technical Department inputs to the Records Management Library. Access to these drives, portals, and libraries shall be in accordance with paragraph 2.2. The contractor shall either scan into digital format or file Technical Department paper files according to the SECNAV M-5210.1 Department of the Navy Records Management Manual, listed in paragraph 2.2 above.

3.7 Technical Department Training Coordination

The contractor shall coordinate on-site training events for the Technical Department by scheduling dates and times, ensuring the availability of correct equipment and materials (e.g., laptops, conference room, notebooks, easels), completing and submitting funding documentation, and managing training certificates. On-site training events occur approximately twice per year.

3.8 Lab Technician Support

3.8.1 Lab Test Planning Support

The contractor shall support test planning activities by coordinating lab resources, gathering information, furnishing technical advice, and solving issues. The contractor shall provide Operation Officer with lab related information, which will be included in detailed test plans by AVTB civil service employees. This Lab related information includes instrumentation specifications, measurement capabilities, and data collection methods.

3.8.2 Lab Instrumentation Preparation

The contractor shall assemble and maintain instrumentation according to the needs and requirements described in the detailed test plans. The contractor shall prepare, align, and calibrate instrumentation to include pressure transducers, current meters, tachometers, flow meters, accelerometers, thermocouples, inclinometers, spectrometers, telemetry systems, load cells, survey equipment, video capture systems, and data acquisition systems. The contractor shall bench test and verify instrumentation in accordance with instructions and procedures established by the AVTB Lab personnel prior to test vehicle installation.

3.8.3 Instrumentation Installation

The contractor shall install instrumentation onto one to four (1 to 4) test vehicles according to the Government-provided detailed test plan for a single event. The contractor shall ensure that the sensors accurately measure the intended physical phenomenon as stated in the detail test plan for each event. The contractor shall ensure that the installations are robust against heat, vibration, snags, impacts, and fluids in accordance with the test plans. After each installation, the contractor shall submit a written report as detailed in CDRL A006 to the lab director. This report will describe what, where, and how the instrumentation was installed, including the extent of possible deficiencies and the plans for correction.

3.8.4 Active Monitoring of Instrumentation

The contractor shall observe instrumentation operation to detect malfunctions and ensure the electronic data being collected by the data acquisition system is complete, valid, accurate, and sufficient to characterize the system under test. The contractor shall conduct this observation via wireless telemetry or through direct physical observation and active video recording. The contractor shall provide real-time verbal reports to test team members concerning instrumentation status. The contractor shall notify the test team immediately if a problem is observed. Previously established go/no-go criteria in the Detailed Test Plan for each event will be used to determine if the test should continue.

3.8.5 Data Processing

The contractor shall retrieve and process instrumentation data collected from test vehicles during the course of formal testing. Data processing involves converting raw data (i.e., Level 1 data) into Level 2 data, using the Government-provided computer programs and knowledge gained from the active monitoring of instrumentation during test execution. Level 2 data is defined as “reduced data or data taken from the raw form and consolidated with invalid or unnecessary data points identified as such with supporting rationale.” The contractor shall record the data during formal test execution and shall provide to the Operations Officer

3.8.6 Lab Contributions to Technical Reports

The contractor shall provide technical information concerning possible instrumentation problems and exceptions, a description of data acquisition system performance, an assessment concerning the accuracy of final measurements, and any possible caveats accompanying measurement results for technical reports.

3.8.7 Lab Inventory Control

The contractor shall support quarterly lab inventory reviews by completing the provided inventory checklists from the lab team lead. Inventory reviews involve locating the government-owned item, verifying that the serial number matches the record, and if necessary, returning the item to its appropriate location.

4 DELIVERABLES

Prior to the submission of any deliverable, the contractor shall provide the Contracting Officer’s Representative (COR) with a copy of the formatted deliverable for format approval, unless otherwise stated. Contract Data Requirements Lists (CDRLs) are contained in Section J, Exhibit A

4.1 Copyediting and Proofreading

The contractor shall provide a weekly progress status report to track the volume of documents reviewed, a list of current review tasks, and issues related to the ongoing review tasks.

CDRL A001 – CONTRACTOR’S PROGRESS, STATUS, AND MANAGEMENT REPORT

4.2 Project Management Support

4.2.1 During the Initiate Phase of Every AVTB T&E Project

The contractor shall update the four tracking documents to reflect the information provided by AVTB civil service employees regarding the new project.

CDRL A002 – COMPLETED PROJECT CHARTER

CDRL A003 – UPDATED INTEGRATED PROJECT SCHEDULE

CDRL A004 – UPDATED AVTB MASTER POWERPOINT SLIDES

CDRL A005 – UPDATED PROJECT INITIATE/CLOSE CHECKLIST

4.2.2 During the Close Phase of Every AVTB T&E Project

The contractor shall ensure the WBS Element 6.5 – Archive Project Data is complete. The contractor shall update the four tracking documents to reflect the information provided by AVTB civil service employees regarding the closed project.

CDRL A002 – COMPLETED PROJECT CHARTER

CDRL A003 – UPDATED INTEGRATED PROJECT SCHEDULE

CDRL A004 – UPDATED AVTB MASTER POWERPOINT SLIDES

CDRL A005 – UPDATED PROJECT INITIATE/CLOSE CHECKLIST

4.3 Lab Technician Support

4.3.1 Instrumentation Installation

The contractor shall submit a written report to the lab director after each installation that describes what, where, and how the instrumentation was installed, including the extent of possible deficiencies and plans to correct them in accordance with CDRL A006 – INSTRUMENTATION INSTALLATION REPORT

4.3.2 Lab Contributions to Technical Reports

The contractor shall provide technical information concerning possible instrumentation problems and exceptions, a description of data acquisition system performance, an assessment concerning the accuracy of final measurements, and any possible caveats accompanying measurement results for technical reports in accordance with CDRL A006.

4.3.3 Instrumentation System Development

The contractor shall update and create SOPs for deployed instrumentation solutions in accordance with CDRL A006. These SOPs are used to inform planners and to cross-train electronics technicians in the operation and maintenance of lab instrumentation. The contractor shall update these procedures when changes are applied to the standardized instrumentation suites.

4.4 Unclassified End Products

Unclassified end products shall be delivered with a letter of transmittal to the COR.

5 PERIOD OF PERFORMANCE

The contract period of performance for this task is anticipated to be one year in duration from date specified in the award, with four one-year option periods.

6 GOVERNMENT FURNISHED EQUIPMENT & FACILITIES

6.1 Government Furnished Equipment

No government furnished equipment will be provided.

6.2 Access to Government Property

The government will provide a work space for up to ten personnel. Access to government telephone services will be made available in the designated work area, but restricted to government and contractor coordination or as necessary to conduct business relevant to this PWS. All off-site calls shall be logged by the contractor in the log book maintained by the lab team lead. The time, number, and official nature of the call made over government telephones shall be recorded.

6.3 Access to Government Facilities

The government will provide access to the engineering labs and other environments within AVTB to execute the tasks within this PWS during normal working hours (0700 to 1600, Monday through Friday). The contractor must seek prior approval of the COR for access to AVTB during government holidays.

6.4 Government Furnished Material

No government furnished material will be provided under this PWS.

The government will not reimburse the contractor for cell phone charges or commercial internet service under this PWS.

6.5 Government Furnished Information

The government will provide the contractor access to the following information and automated services in support of this PWS:

1. The technical information required for the performance of this PWS. The contractor shall submit a written request to the COR, at least two calendar days in advance, for specific information.

2. A user account and email account on the Marine Corps Enterprise Network (MCEN), to include a Common Access Card (CAC) to support Public Key Infrastructure (PKI) access and Marine Corps Web Services, if determined as necessary for the performance of this PWS. Contractors are required to complete two classes before being issued an email account.

DoD-IAA-V12.0 DoD Cyber Awareness Challenge V2 DoD-PII-2.0 Privacy and Personally Identifiable Information (PII) Awareness

7 PERSONNEL

The contractor shall provide sufficient key personnel with the following experience and qualifications:

7.1 Lab Technician(s)

Ten years of experience or technical training relevant to the tasks listed in paragraph 3.8.1 through 3.8.7.

7.2 Operations Analyst

College degree or six years of business experience relevant to the tasks listed in paragraph 3.2 through 3.7.

7.3 Technical Editor

College degree or six years of editorial experience relevant to the tasks listed in paragraph 3.1.

7.4 Personnel Availability

In the event an individual is not able to perform a role due to illness, death, termination, or other reasons, the contractor will provide a substitute with the requisite skills to ensure uninterrupted performance. The contractor shall provide the Contracting Officer with notification of the substitution, including a resume for the proposed individual. Since this is a performance based requirement, failure of the contractor to provide personnel with the requisite skills to perform the contract task may result in a breach.

8 TRAVEL REQUIREMENTS

The contractor is may be required to travel outside Camp Pendleton, CA. There is no travel anticipated for the base year. The contractor may be required to travel in support of this PWS to the locations listed below, when notified by the COR for each option year. If additional travel is required, the contract will be modified by the Contracting Officer. Authorized travel shall be in accordance with the contract. The actual travel required will vary, depending on test requirements and schedules as they evolve throughout the performance period. The travel table below is for planning purposes only Table 101 Off-Site Test Support

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

DELIVERY INFORMATION

02-JUN-2017

AVTB ATTN: SUPPLY OFFICER

BLDG 210536 KRAUS ST

CAMP PENDLETON CA 92055-5217

760-763-4428

M90133

02-JUN-2017

02-JUN-2017

02-JUN-2017

02-JUN-2017

02-JUN-2017

02-JUN-2017

02-JUN-2017

02-JUN-2017

02-JUN-2018

02-JUN-2018

02-JUN-2018

02-JUN-2018

02-JUN-2018

02-JUN-2018

02-JUN-2018

02-JUN-2019

02-JUN-2018

02-JUN-2018

02-JUN-2019

02-JUN-2019

02-JUN-2019

02-JUN-2019

02-JUN-2019

02-JUN-2019

02-JUN-2019

02-JUN-2019

02-JUN-2019

02-JUN-2019

02-JUN-2020

02-JUN-2020

02-JUN-2020

02-JUN-2020

02-JUN-2020

02-JUN-2020

02-JUN-2020

02-JUN-2020

02-JUN-2020

02-JUN-2020

02-JUN-2021

02-JUN-2021

02-JUN-2021

02-JUN-2021

02-JUN-2021

02-JUN-2021

02-JUN-2021

02-JUN-2021

SECTION G CONTRACT ADMINISTRATION DATA

G.1 ADMINISTRATIVE AUTHORITY

G.1.1 Contracting Officer Only the Contracting Officer has the sole authority to authorize deviations from the terms and conditions of this contract, including deviations from the specifications and requirements stated herein. In the event of a contractor deviation, without the issuance of a duly executed contract modification, such deviation shall be at the risk of and any costs related thereto shall be borne of the contractor.

G.1.2 Contracting Officer’s Representative (COR) Robert Lamont at (760) 763-7431 or at robert.lamont@usmc.mil, is the COR for this contract. The COR is limited to providing program specific clarification to the contractor’s task leader for this contract. The COR does not have the authority to take action (directly or indirectly) that would change the pricing, quality, place of performance, delivery schedule, or other terms and conditions of this contract, or to direct outside the scope of this PWS. If the contractor perceives the COR or other government personnel is requesting an effort outside the scope of this contract, the contractor shall promptly notify the Contracting Officer in writing. No action shall be taken by the contractor until the Contracting Officer has issued a contractual change or otherwise resolved the issue. The government reserves the right to reassign the COR position.

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013)

(a) Definitions. As used in this clause—

Department of Defense Activity Address Code (DoDAAC) is a six position code that uniquely identifies a unit, activity, or organization.

Document type means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

Local processing office (LPO) is the office responsible for payment certification when payment certification is done external to the entitlement system.

(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall—

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.acquisition.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this Web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/.

(e) WAWF methods of document submission. Document submissions may be via Web entry, Electronic Data Interchange, or File Transfer Protocol.

(f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:

(1) Document type. The Contractor shall use the following document type(s).

2 in 1 for Services

(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer.

N/A

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table* Field Name in WAWF Data to be entered in WAWF

(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.

(5) WAWF email notifications. The Contractor shall enter the email address identified below in the “Send Additional Email Notifications” field of WAWF once a document is submitted in the system.

N/A

(g) WAWF point of contact. (1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

TBD

(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

(End of clause)

SECTION H - SPECIAL CONTRACT REQUIREMENTS

H.1 PERFORMANCE LOCATION

Work efforts in support of this task will be conducted at AVTB, Camp Pendleton, CA. AVTB will provide on-site workspace to ensure that sensitive information stays within the AVTB network. This on-site workspace supports information security and reduces costs by eliminating the need for an off-site facility to meet security regulations.

The government will provide access to the engineering labs and other environments within AVTB to execute the tasks within this PWS during normal working hours (0700 to 1600, Monday through Friday). Access to AVTB facilities outside normal working hours shall be scheduled with the AVTB COR and security officer at least one working day prior to the date access is required. The contractor must seek prior approval of the COR for access to AVTB during government holidays.

H.2 SECURITY REQUIREMENTS

This contract will require the contractor to have a Secret Facility Clearance and will require certain contractors to obtain and maintain classified access eligibility. The contractor shall have a valid Secret Facility Clearance prior to classified performance. The prime contractor and all sub-contractors (through the prime contractor) shall adhere to all aspects of DoD Directive 5220.22-M. All personnel identified to perform on this contract shall maintain compliance with Department of Defense, Department of the Navy, and Marine Corps Information and Personnel Security Policy to include completed background investigations (as required) prior to classified performance. This contract shall include a DoD Contract Security Classification Specification (DD Form 254) as an attachment. The contractor shall notify the Government (written notice) within twenty-four hours of any contractor personnel added or removed from the contract that have been granted classified access, issued a Common Access Card.

The contractor shall introduce themselves, or be introduced, as contractor personnel and display badges or other visible identification for meetings with government personnel. In addition, contractor personnel shall identify themselves as contractor employees in telephone conversations and in written correspondence.

H.2.1 Base Security The contractor shall comply with Marine Corps Base (MCB) Camp Pendleton, CA security regulations and policies. The contractor’s staff shall be U.S. or naturalized citizens, whose military duty was not terminated by a dishonorable or bad conduct discharge, are not subject to an outstanding criminal warrant, have no felony convictions, and have no more than three criminal misdemeanor convictions within the last seven years. Additionally, no criminal misdemeanor or felony conviction for crimes of a sexual nature, crimes of violence, crimes related to gang activity or hate crimes, or crimes resulting from the possession or distribution of any illegal drug are acceptable.

All contractor personnel aboard MCB Camp Pendleton, with the exception of emergency personnel, shall wear a properly issued badge at all times. All contractor personnel shall comply with all emergency rules and procedures established for MCB Camp Pendleton. All personnel aboard MCB Camp Pendleton are subject to random inspections of their vehicles, personal items, and themselves. Consent to these inspections is given when personnel enter MCB Camp Pendleton, CA.

H.2.2 OPSEC Requirements The practice of Operations Security (OPSEC) prevents the inadvertent compromise of sensitive unclassified and classified activities, capabilities, or intentions at the tactical, operational, and strategic levels. The contractor’s staff must adhere to all government OPSEC measures currently in place at the government facility. The contractor shall provide OPSEC training to all contractor personnel supporting this effort. Taking pictures from cameras or cell phones is not allowed while aboard the compound or in the test areas.

H.2.3 Common Access Card (CAC) Requirement The COR will identify and approve those contractor employees performing on this contract that require Common Access Cards (CACs) in order to perform their job function. In accordance with Headquarters, United States Marine Corps issued guidance relative to Homeland Security Presidential Directive – 12 (HSPD-12), all personnel must meet eligibility criteria to be issued a CAC. In order to meet the eligibility criteria, contractor employees requiring a CAC, must obtain and maintain a favorably adjudicated Personnel Security Investigation (PSI.) Prior to authorizing a CAC, the employee’s JPAS record must indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has been submitted and accepted (opened.) The minimum acceptable investigation is a National Agency Check with Written Inquiries (NACI.) If a contractor employee’s open investigation closes and is not favorably adjudicated, the CAC must be immediately retrieved and revoked.

Facility Security Officers (FSOs) are responsible for notifying the MCSC Security Director if any contractor performing on this contract receives an unfavorable adjudication after being issued a CAC. The FSO must also notify the MCSC Security Director of any adverse/derogatory information associated with the 13 Adjudicative Guidelines/Factors concerning any contractor issued a CAC, regardless of whether a JPAS Incident Report is submitted.

Each CAC is issued with a “ctr.usmc.mil” e-mail account that the individual contractor is responsible to keep active by logging in on a regular basis (at least twice a month), sending an e-mail and clearing any unneeded e-mails. Contractors are prohibited from “auto-forwarding” their .mil e-mail account to their .com e-mail account. If the ctr.usmc.mil e-mail account is not kept active, the G-6 will deactivate the account and CAC will lose its functionality.

Common Access Cards (CACs) will only be issued to those contractors supporting this contract that have been authorized by the COR. The COR will only authorize CACs for those contractors that meet current Homeland Security Presidential Directive – 12 (HSPD-12) criteria and have a definitive requirement.

If a contractor loses their eligibility for a CAC due to an adverse adjudicative decision, they have also lost their eligibility to perform on MCSC contracts. CACs are not issued for convenience.

H.3. ORGANIZATIONAL CONFLICT OF INTEREST

(a) “Organizational Conflict of Interest” means that because of other activities or relationships with other persons, a person is unable or potentially unable to render impartial assistance or advice to the government, or the person’s objectivity in performing the contract work is or might be otherwise impaired, or a person has an unfair competitive advantage. “Person” as used herein includes Corporations, Partnerships, Joint Ventures, and other business enterprises.

(b) The contractor warrants that to the best of their knowledge and belief, and except as otherwise set forth in the contract, the contractor does not have any organizational conflict of interest(s) as defined in paragraph (a).

(c) It is recognized that the effort to be performed by the contractor under this contract may create a potential organizational conflict of interest on the current programs or on a future acquisition efforts. In order to avoid this potential conflict of interest, and at the same time to avoid prejudicing the best interest of the government, the right of the contractor to participate in future procurement of equipment and/or services that are the subject of any work under this contract shall be limited as described below in accordance with the requirements of FAR 9.5.

(d) (1) The contractor agrees that it shall not release, disclose, or use in any way that would permit or result in disclosure to any party outside the government any proprietary information provided to the contractor by the government during or as a result of performance of this contract. Such information includes, but is not limited to, information submitted to the government on a confidential basis by other persons. Further, the prohibition against release of government provided information extends to cover such information whether or not in its original form, e.g., where the information has been included in contractor generated work or where it is discernible from materials incorporating or based upon such information. This prohibition shall not expire after a given period of time.

(d) (2) In accordance with DFARS 252.204-7000, the contractor shall not release to anyone outside the contractor's organization any unclassified information, regardless of medium (e.g., film, tape, document), pertaining to any part of this contract or any program related to this contract, unless the Contracting Officer has given prior written approval.

(d) (3) The prohibitions contained in subparagraphs (d)(1) and (d)(2) shall apply with equal force to any affiliate of the contractor, any subcontractor, consultant, or employee of the contractor, any joint venture involving the contractor, any entity into or with which it may merge or affiliate, or any successor or assign of the contractor. The terms of paragraph (f) of this Special Contract Requirement relating to notification shall apply to any release of information in contravention of this paragraph (d).

(e) The contractor further agrees that, during the performance of this contract and for a period of one year after completion of performance of this contract, the contractor, any affiliate of the contractor, any subcontractor, officers of the company participating in the contract, any joint venture involving the contractor, any entity into or with which it may subsequently merge or affiliate, or any other successor or assign of the contractor, shall not furnish to the United States Government, either as a prime contractor or as a subcontractor, or as a consultant to a prime contractor or subcontractor, any system, component or services which is the subject of the work to be performed under this contract. This exclusion does not apply to any re-competition for those systems, components, or services furnished pursuant to this contract. As provide in FAR 9.505-2, if the government procures the system, component, or services on the basis of work statements growing out of the effort performed under this contract, from a source other than the contractor, subcontractor, affiliate, or assign of either, during the course of performance of this contract or before the one year period following completion of this contract has lapsed, the contractor may, with the authorization of the cognizant Contracting Officer, participate in a subsequent procurement for the same system, component, or service. In other words, the contractor may be authorized to compete for procurement(s) for systems, components, or services subsequent to an intervening procurement.

(f) The contractor agrees that, if after award, it discovers an actual or potential organizational conflict of interest; it shall make immediate and full disclosure in writing to the Contracting Officer. The notification shall include a description of the actual or potential organizational conflict of interest, a description of the action, which the contractor has taken or proposes to take to avoid, mitigate, or neutralize the conflict, and any other relevant information that would assist the Contracting Officer in making a determination on this matter.