Performance Work Statement REV 1.pdf

PR: FD2060-20-30982 PWS REVISION: 1 1

Distribution Statement: D

Performance Work Statement for

BRAT Sustaining Engineering: Study to Identify a Replacement Phase Noise Measurement

Module

Purchase Request: FD2060-20-30982

26 March 2020

Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD

Contractors only, Administrative or Operational Use, 4 April 2017. Other requests shall be referred to the Automatic Test Systems Program Office, AFLCMC/WNA, Robins AFB, GA 31098

WARNING- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Disseminated in accordance with provisions of DoD Directive 5230.25.

PR: FD2060-20-30982 PWS REVISION: 1 2

1.0 Description of Services

Automatic Test Systems Division (AFLCMC/WNA), the program office for Benchtop Reconfigurable Automatic Test (BRAT) system, requires varying levels of support for sustainment of managed system. The BRAT Engineering Section, AFLCMC/WNAEA, is the overall system technical authority and has Operational Safety, Suitability, and Effectiveness (OSS&E) responsibility. BRAT systems are experiencing problems with decreased sustainability of Original Equipment Manufacturer (OEM) hardware and software components, incompatibilities with advanced state of the art hardware and software component functionality, and age-related operation performance deficiencies. The system’s service life has been extended well beyond its anticipated design life. The scope of this effort includes sustainment engineering tasks for the aging system and sub-systems specifically the identification of a replacement phase noise measurement module.

1.1 Objective(s): This Performance Work Statement (PWS) describes the services required to obtain information that the Government will utilize to make an informed decision on a path forward for sustainment of BRAT systems. This PWS describes the need to acquire Contractor sustaining engineering support to identify a replacement phase noise measurement module for BRAT systems. This effort is intended to continue the focus on system-level operational and technology-obsolescence deficiencies. This service will generate technical analysis, analysis of alternatives with procurement costs and technical specification, determination of replacement BRAT phase noise measurement module, prototype, integration of solutions into the overall system, and First Article& Qualification Testing.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by ensuring the three (3) Air Force Depots, Air Combat Command (ACC), Air Force Reserve Command (AFRC), Air National Guard (ANG) units can perform repair/testing of Line Replaceable Units (LRUs)/Shop Replacement Units (SRUs) in support of C-5, EC-130, E-3, E-4, E-6, E-8, F-15 and RC-135 aircraft platforms.

1.3 Background: The BRAT is a family of testers made-up of a collection of Commercial-Off-the-Shelf (COTS) instruments and components, installed in multi-bay chassis. There are currently 81 separate testers that make up eight (8) different configurations. Since 1992 the BRAT has provided analog, digital, and radio frequency (RF) testing capabilities in support of a diverse range of LRUs, such as the C-5 Roll/Yaw Proximity Warning System Computer, E-3 Transmit Phase Detector, E-8 RF Amplifier/High Power Combiner (HPC), and the Joint Tactical Information Distribution System (JTIDS).

Due to the rapid and continuous evolution of the electronic arena, many of the current BRAT components have been rendered obsolete by technological developments in automatic test systems thus creating operational deficiencies which must be resolved. Additionally, numerous systemic deficiencies exist across the system at the component level due to the age of the technology as well as the age of the industry which produced it.

2.0 Services Summary

PR: FD2060-20-30982 PWS REVISION: 1 3

Performance Objective PWS

Reference Performance Threshold

Quality of CDRL deliverable

4.2.1 There shall be no more than one (1) rejection of any

deliverable. There shall be no more than one (1) total rejection(s) of deliverables per contract year.

The Government will reject a deliverable if one (1) or more technical errors or ten (10) or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within five (5) business days of notification of Government rejection.

Receipt of CDRL deliverable

4.2.2 There shall be no more than one (1) late

submission(s) of deliverables per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Adherence to Contractor Quality Management System (QMS )

5.8 100% compliance with the QMS is required.

3.0 Government Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 Government Property to be Provided: Government property will be provided after the acceptance and DD250 of the two (2) prototypes required for this effort. The two (2) prototypes will be modified COTs phase noise measurement modules which once identified and purchased will be added to this contract by noun, part number, and serial number.

3.3 Reporting of Government Property: The Contractor shall create and maintain records of all Government property accountable to the contract/order. The Contractor shall record receipt and return of Government-Furnished Property (GFP) in the Item Unique Identification (IUID) Registry.

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of

PR: FD2060-20-30982 PWS REVISION: 1 4

Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.4.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property using the Government-Furnished Property (GFP) module of the Procurement Integrated Enterprise Environment.

3.5 Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order will extend for 14 months.

4.1.2 Place of Performance: These services will be performed at a combination of U.S.

Government and non US Government installations. Specifically, Robins AFB, GA, the Contractor’s facility, off-site temporary duty (TDY) to other USAF Command facilities, other DOD facilities, and private industry facilities.

4.2 Contract Data Requirements List(s) (CDRL)

Document Identifier

DID Title PWS Reference(s)

A001 DI-SESS-81253C Configuration Status Accounting (CSA) Information 4.3 A002 DI-NDTI-80603A Test Procedure 4.3.2.1 A003 DI-MGMT-80227 Contractor’s Progress, Status and Management Report 4.3.2.3 A004 DI-NDTI-80809B Test/Inspection Report 4.3.2.5 A005 DI-MGMT-80368A Status Report 4.3.3 A006 DI-MISC-80508B Technical Report-Study/Services 4.3.1,4.3.4 A007 DI-MISC-81943 NOT1 Trip/Travel Report 4.4.4

A008 DI-MGMT-82247

Contractor’s Systems Security Plan 4.4.7.1, 4.4.7.2

PR: FD2060-20-30982 PWS REVISION: 1 5

A009 DI-ENVR-81840 Programmatic Environmental Safety and Health Evaluation (PESHE) Plan

5.5.2

A010 DI-QCIC-81187 NOT1 Quality Assessment Report 5.8 A011 DI-QCIC-81722 Quality Program Plan 5.8 A012 DI-QCIC-81794A Quality Assurance Program Plan 5.8

4.2.1 Quality of CDRL Deliverable: There shall be no more than one (1) rejection of any deliverable. There shall be no more than one (1) total rejection(s) of deliverables per contract year. The Government will reject a deliverable if one (1) or more technical errors or ten or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within five business days of notification of Government rejection.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Multi-user ECP Automated Review System (MEARS). There shall be no more than one (1) late submission(s) of deliverables per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date.

The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.2.3 The Contractor shall electronically deliver all contractual data using the Government-controlled method of delivery, Multi-user ECP Automated Review System (MEARS), https://mears1.redstone.army.mil/mears/Default.aspx. The Contractor shall work with the Government to ensure that an adequate number of Contractor personnel obtain and possess Public Key Infrastructure (PKI) certification from an accepted Government source. The Contractor shall be receptive to the training offered by the Government on the MEARS system. The Contractor shall prepare, maintain, and track the contract data status, schedule and ensure timely data deliveries. An alternate method of delivery when MEARS is down for maintenance will be the DISA application, known as DOD SAFE, https://safe.apps.mil/. It will be available to all DOD Common Access Card (CAC) holders or Contractor personnel who possess Public Key Infrastructure (PKI) certification from an accepted Government source.

4.3 Engineering Services

The Contractor shall identify a replacement for the phase noise measurement module, part number 94101130-01, currently installed on BRAT systems. The Contractor’s identified replacement part shall ensure the system baseline performance is retained, that design improvements satisfy the minimum performance requirements and that risk is sufficiently reduced to warrant fielding of the solution. The Contractor shall make every effort to identify a replacement which is form, fit, function and two-way interchangeable across all BRAT stations regardless of the BRAT configuration which it is installed. If a form, fit, function two-way interchangeable replacement cannot be identified, the Contractor shall identify a replacement which meets all of the functional requirements of the current BRAT and all current configurations. Two (2) each prototypes of identified replacement phase noise measurement https://mears1.redstone.army.mil/mears/Default.aspx https://safe.apps.mil/

PR: FD2060-20-30982 PWS REVISION: 1 6

module shall be provided to the Government. The Contractor shall preform First Article & Qualification testing at either one (1) or both Robins AFB BRAT user sites (116th ANG and WR- ALC) with Government Program Office personnel and Government technicians present. The First Article & Qualification testing can only be completed after the Government has approved a qualification acceptance test procedure. The Contractor shall work with the assigned BRAT Program Office engineering staff throughout the execution of First Article & Qualification Testing. Activities include but are not limited to: Technical analysis, analysis of alternatives with procurement costs and technical specification, determination of replacement BRAT phase noise measurement module, prototype, integration of solution into the overall system, and First Article & Qualification Testing. [A001, Configuration Status Accounting (CSA) Information, DI-SESS-81253C]

4.3.1 Analysis/Investigations

The Contractor shall identify and evaluate a replacement of the phase noise measurement module 94101130-01. The Contractor shall develop an analysis of alternatives for each identified potential replacement to include all engineering, technical, and logistics support required to ensure the most cost effective approach. This analysis shall include but not limited to identification of any software and/or hardware modification which will need to be accomplished to the BRAT systems and any effects these modifications will have on sustainment and calibration of the BRAT system. The Contractor shall evaluate all possible, comparable solutions/approaches, and provide explicit, clear, and detailed justification to the Government for the solution/approach selected. Detailed justification of identified replacement part shall include itemized list of changes/modification to BRAT systems with cost breakout for successful implementation of replacement part. [A006, Technical Report-Study/Services, DI-MISC- 80508B]

4.3.2 First Article Test

4.3.2.1 First article test procedures. The Contractor shall develop detailed first article test procedures to address all requirements in this PWS. The test procedures shall include data record sheets, charts, graphs, identification of test instruments by manufacturer, model number, and serial number. The test procedures shall address modeling and simulation (M&S); if M&S is not applicable, the test procedures shall be so noted. [A002, Test Procedure, DI-NDTI-80603A]

4.3.2.2 First article testing. After Government approval of the first article test procedures, the Contractor shall coordinate with the BRAT Program Office to schedule the testing to be conducted 30 days in advance of testing need date. If shipping is required to move the item(s) to and from a test site away from the Contractor’s facility, the Contractor shall be responsible for all costs associated with the shipment. The test will be witnessed by one or more Government representatives.

4.3.2.3 First article test daily situation reports (SITREPs). Throughout the first article test, the Contractor shall submit a daily situation report (SITREP) that shall over all monitored daily test activates. To include:

a. Test logs

PR: FD2060-20-30982 PWS REVISION: 1 7

b. Observed data to include: Observations, comments, anomalous conditions, or other items completed for each first article unit

c. Recorded data as applicable to the type of equipment

d. Records of preventative maintenance activities performed

e. Software changes/updates performed during test [A003, Contractor’s Progress, Status and Management Report, DI-MGMT-80227]

4.3.2.4 Compatibility testing. During the first article test, a test item shall be used for compatibility testing. Government personnel will perform the test; Contractor personnel shall witness the test and advise the Government personnel.

4.3.2.5 First article test report. The Contractor shall submit a first article test report upon completion of the first article test. The test report shall document all testing performed, including results of any unsuccessful test attempts. [A004, Test/Inspection Report, DI-NDTI-80809B]

4.3.3 Quarterly Status Report

The Contractor shall report technical, schedule and cost status on a quarterly basis. Any reviews of the quarterly status report between the Contractor and the Government will not require formal deliverable such as Presentations, Agendas or Minutes. A final report shall be delivered that contains a summary of all previously submitted Status Report data. The Contractor report shall include [A005, Status Report, DI-MGMT-80368A]

• Summary of work performed and findings during the quarter

• Proposed changes to the Schedule

• Identification of technical problems/anomalies encountered

• Notification of problems in program management

• Identification of areas where the Contractor’s performance or deliverables are not projected to meet the requirements of the contract

4.3.4 Final Project Report

The Contractor shall deliver a final report at the conclusion of the effort which details the entire effort including First Article & Qualification Testing results and recommended implementation approach(es). [A006, Technical Report- Study/Services, DI-MISC-80508B]

4.3.5 After completion of the testing required to complete this effort, upon request of the Government the Contractor shall return the BRAT stations used for this effort to the current Government recognized configuration.

4.4 Other Requirements

4.4.1 The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronic parts being installed in end items or otherwise entering the USAF/DoD inventory.

4.4.2 Contract Management: The Contractor shall identify to the Government and maintain a single point of contact for all matters under this contract.

PR: FD2060-20-30982 PWS REVISION: 1 8

4.4.3 Holidays and Facility Closings: Contractor/subcontractor personnel shall observe holidays and facility closings as authorized for Government personnel. Contractor/subcontractor personnel shall only be permitted access to Government facilities when Government personnel are present.

4.4.4 Travel: The Contractor shall arrange and execute all travel necessary for the performance of the requirements of this PWS. Travel requests shall be made through email notification to the Program Manager and PCO no later than five (5) business days prior to travel. The Government is under no obligation to reimburse travel in which prior written approval from the PCO (AFLCMC/WNKAB) has not been provided. Receipts must be presented with the invoice for reimbursement of actual travel costs. Travel by Contractor personnel shall be conducted in accordance with FAR31.205-46, Travel Costs. Following each trip, a trip report shall be provided to the Government Program Manager [A007, Trip/Travel Report, DI-MISC-81943

NOT1]

4.4.5 Restrictions on use of proprietary material

Rights in software and data developed and delivered under the contract shall be governed by Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7013.7014 etc. In the event that it is necessary for the Contractor to use contractor-developed and/or proprietary hardware and/or software to fulfill its obligations under the contract, the Government shall be notified, and any requirement for delivery of such proprietary material shall be with Limited or Restricted Rights, as the case may be. In the event it is necessary for the Contractor to purchase licenses to third party software using contract funds in order to fulfill its obligations under the contract, those licenses shall be delivered to the Government; and the Government’s rights in such software will be determined by the provisions of those license agreements.

4.4.6 Subcontract Management

The Contractor shall ensure sub-contractor compliance with all applicable requirements of the contract.

4.4.7 Contractor’s Systems Security Plan

4.4.7.1 The Contractor shall, upon request, provide to the Government, a system security plan (or extract thereof) and any associated plans of action developed to satisfy the adequate security requirements of DFARS 252.204-7012, and in accordance with NIST Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations” in effect at the time the solicitation is issued or as authorized by the Contracting Officer, to describe the Contractor’s unclassified information system(s)/ network(s) where covered defense information associated with the execution and performance of this contract is processed, is stored, or transmits. System Security Plan and Associated Plans of Action for a Contractor’s Internal Unclassified Information System. [A008, Contactor’s Systems Security Plan, DI-MGMT-82247]

4.4.7.2 The Contractor shall, upon request, provide the Government with access to the system security plan(s) (or extracts thereof) and any associated plans of action for each of the

PR: FD2060-20-30982 PWS REVISION: 1 9

Contractor’s tier one level subcontractor(s), vendor(s), and/or supplier(s), and the subcontractor’s tier one level subcontractor(s), vendor(s), and/or supplier(s), who process, store, or transmit covered defense information associated with the execution and performance of this contract.

System Security Plan and Associated Plan of Action for a Contractor’s Internal Unclassified Information System. [A008, Contractor’s Systems Security Plan, DI-MGMT-82247]

4.4.8 Warranty

4.4.8.1 Prototype Warranty: The prototypes provided under this contract will come with a six (6) month functional and performance warranty commencing with delivery and installation.

4.4.8.2 The Contractor shall provide a four (4) month test program set (TPS), Warranty, limited to the 116th ANG eight (8) TPSs. ATTI’s TPS warranty certifies the prototypes replacement phase noise measurement modules will successfully run/execute all TPSs which were developed in accordance with the BRAT TPS Style Guide (Pub 96001).

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Commander or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2 Security Requirements

5.2.1 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with the following security regulations: DoD 5200.2-R Change 3, Personnel Security Program; DoD 5220.22-M Change 2, National Industrial Security Program Operating Manual (NISPOM);

DoDD 5205.02E, DoD Operations Security (OPSEC) Program; and DoD 5205.02-M, DoD Operations Security (OPSEC) Program Manual.

5.2.2 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall comply with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.)

Government interests. The Contractor shall ensure Contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

5.2.3 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with DoD 5220.22- M. Applicable equipment shall be safeguarded, maintained and operated in accordance with DoD 5220.22-M.

PR: FD2060-20-30982 PWS REVISION: 1 10

5.2.4 Security Clearance: It is not expected contractor/subcontractor personnel will require security clearances for proper accomplishment of contract/order requirements.

Contractor/subcontractor personnel shall not be authorized access to classified information and/or Controlled Unclassified Information (CUI) and classified items or be permitted to work on classified projects and/or programs without an appropriate security clearance and a need-to-know.

5.2.5 Security Incident or Violation: The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

5.2.6 Access to Government System(s): The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a National Agency Check with Inquiries (NACI) conducted. Upon completion/termination of the contract/order or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2.7 Access to Robins Air Force Base (AFB): The Contractor shall ensure contractor/subcontractor personnel who require access to Robins AFB comply with the security requirements of the installation. The Contractor shall provide the PCO a list of all contractor/subcontractor personnel requiring access to Robins AFB, the contract/order number and the period of performance. The Contractor shall also provide, if possible, the location of the work site and the days/hours during which the contractor/subcontractor personnel will require access to Robins AFB.

5.2.8 Identification (ID) Card/Badge

5.2.8.1 The Contractor shall ensure an ID card is obtained by all contractor/subcontractor personnel who require recurring access to a Government facility, but not local area network (LAN) access. The Contractor shall submit a letter to the PCO listing all contractor/subcontractor personnel requiring access to the facility. The PCO will approve the request and forward it to the issuing/registration office for processing. Contractor/subcontractor personnel shall report to the issuing/registration office to obtain the ID card(s).

5.2.8.2 The Contractor shall submit a letter to the PCO immediately if contractor/subcontractor personnel no longer require access, upon transfer/termination of contractor/subcontractor personnel or upon completion/termination of the contract/order. The letter shall identify the name(s) and social security number(s) of the contractor/subcontractor personnel. The Contractor shall return the ID card(s) to the issuing/registration office upon expiration, upon transfer/termination of contractor/subcontractor personnel, or once contractor/subcontractor personnel no longer require access to the facility. The Contractor shall return any and all ID cards to the issuing/registration office upon completion/termination of the contract.

PR: FD2060-20-30982 PWS REVISION: 1 11

5.3 Environmental Management System (EMS): Contractor/subcontractor personnel who perform work on any Government facility shall comply with the EMS requirements established by the facility. Contractor/subcontractor personnel may be required to complete EMS training prior to beginning work.

5.4 Agency Affirmative Procurement Programs: In accordance with FAR 23.404, Agency Affirmative Procurement Programs, 100% of purchases of Environmental Protection Agency (EPA)-designated products included in the Comprehensive Procurement Guidelines (CPG) list [http://www.epa.gov/cpg/products.htm] and/or United States Department of Agriculture (USDA)-designated products included in the bio-based product listings [http://www.biopreferred.gov] shall, at a minimum, meet the EPA or USDA standards for recovered materials or bio-based content, respectively, unless an item cannot be acquired competitively within a realistic timeframe, meet appropriate performance standards, and/or be acquired at a reasonable price.

5.5 Safety Requirements

5.5.1 Contractor Compliance: The Contractor shall comply with Government Safety and Health regulations including, Public Law 91-596 as amended by Public Law 101-552 [Occupational Safety and Health Act of 1970 (OSHA)] and DoDD 4715.1E, Environment, Safety, and Occupational Health (ESOH).

5.5.2 Safety and Health Plan/Program: The Contractor shall submit a Safety and Health Plan to the Multi-Functional Team (MFT) or as indicated by CDRL instructions. The Contractor shall establish and maintain a safety program in accordance with the contract/order, applicable Government regulations and the Safety and Health Plan. [A009, Programmatic Environmental Safety and Health Evaluation (PESHE) Plan, DI-ENVR-81840]

5.5.3 Mishap Notification/Investigation: The Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or private property or injury or illness to non-DoD personnel caused by Government operations.

The Contractor shall ensure the Safety Office and the PCO are notified of mishaps. The Contractor shall contact the MFT (COR, if available, or another MFT member) by telephone within four (4) business hours. The Contractor shall cooperate with Government safety investigations.

5.5.4 Voluntary Protection Program (VPP): Contractor personnel performing work on a USAF installation shall participate in the local VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html.

5.6 Inspection of Services: In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the Government reserves the right to inspect Contractor performance.

http://www.epa.gov/cpg/products.htm http://www.biopreferred.gov/ http://www.osha.gov/dcsp/vpp/index.html

PR: FD2060-20-30982 PWS REVISION: 1 12

5.7 Invoicing/Payment and Receipt/Acceptance: The Contractor shall submit/process payment requests and receipt/acceptance documents via WAWF.

5.7.1 The CDRL will determine submittal requirement; however, separately priced data must be accepted in WAWF in order for the Contractor to receive payment, and both separately priced and non-separately priced data must be accepted in WAWF in order the contract line item to be closed out.

5.7.2 Services will be accepted by the COR.

5.8 Quality Control Plan (QCP)/Quality Management System (QMS): The Contractor shall ensure the quality of services through a quality and/or inspection system. The Contractor shall submit a QCP addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur. The plan shall include the schedule of quality assurance/control inspections planned by the Contractor. 100% compliance with the QMS is required. [A010, Quality Assessment Report, DI-QCIC-81187 NOT1; A011, Quality Program Plan, DI-QCIC-81722; A012, Quality Assurance Program Plan, DI-QCIC-81794A]

5.9 Trafficking in Persons: The Contractor shall comply in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about Trafficking in Persons is available at the site for the Department of State’s Office to Monitor and Combat Trafficking in Persons. http://www.state.gov/j/tip http://www.state.gov/j/tip

PR: FD2060-20-30982 PWS REVISION: 1 13

6.0 Appendices

6.1 Appendix A, Reference(s)

Publication Title of Publication Date of Publication Sections(s) that Apply

DFARS

252.227-

Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation

February 2014 4.4.5

DFARS

252.227-

Rights in Technical Data- Noncommercial Items February 2014 4.4.5

DFARS

252.204-

Safeguarding Covered Defense Information and Cyber Incident Reporting

December 31, 2019 4.4.6

DoD 5220.22-M

National Industrial Security Program Operating Manual

(NISPOM).

February 28, 2006 Change 1 - March 28, 2013

5.2.1

DoD 5200.2-R

Procedures for the DoD Personnel Security Program

(PSP)

April 3, 2017 5.2.1

DoDD 4715.1E

Environment, Safety, and Occupational Health (ESOH) March 19, 2005 5.2.1

DoDD) 5205.02E

DoD Operations Security (OPSEC) Program June 20, 2012 5.2.1, 5.2.2

DoD Manual 5205.02-M

DoD Operations Security (OPSEC) Program Manual November 3, 2008 5.2.1, 5.2.2

Public Law 91- 596 as amended by Public Law 101-

Occupational Safety and Health Act of 1970 December 29, 1970 as amended through January 1, 2004

5.5.1