Attachment 8 - Statement of Work Template.docx

STATEMENT OF WORK

PROJECT/PROGRAM TITLE

XX Month XXXX

(TEXT PROVIDED FOR REFERENCE/OUTLINE ONLY)

1.0 OBJECTIVE:

1.1 The objective of this effort is to…

2.0 SCOPE:

2.1 The scope of this effort is to...

3.0 BACKGROUND:

3.1 XXXXXX

4.0 TASKS/TECHNICAL REQUIREMENTS:

4.1 The Contractor shall accomplish the following:

4.1.1 XXXXX

4.1.2 Reporting. (*This may simply cross-reference to the CDRL package (e.g. Contract Section J Exhibit A), although it is preferred that the applicable CDRL be identified by number (e.g. A001) within the paragraphs below. For instance: “At the conclusion of testing, the Contractor shall compile findings within, and deliver, a Test Report (CDRL A009)”)

5.0 DELIVERABLES

5.1 In addition to the reporting and data deliverables identified in the previous section [insert Section reference], the Contractor shall deliver the following:

5.1.1 Hardware deliverables & schedule (*Only include if Applies*) a.

b.

c.

5.1.2 Software deliverables & schedule (*Only include if Applies*) a.

b.

c.

5.1.3 Prototype deliverable requirements & schedule (*Only include if Applies*) a.

b.

c.

5.2 All prototype(s), software and/or hardware developed under this contract shall be delivered to the Government. The Government shall receive Unlimited Rights in all other than commercial technical data and computer software. Any third-party software shall be approved by the Contracting Officer prior to incorporation and in accordance with DFARS 252.227-7014. (*Change to align with proposed assertions as applicable)

6.0 BASE SUPPORT/FACILITIES

6.1 See Supplemental SOW Requirements at Section J Attachment 2. (*Remove if base support is not required)

7.0 SECURITY AND OPSEC

7.1 All documents, including papers, abstracts and posters shall be cleared by AF prior to public release.

7.2 The Contractor shall provide OPSEC protection for all sensitive/critical information and indicators involved in execution of this contract/Task Order, as defined by AFI 10-701 (Operations Security). 711 HPW Critical Information and Indicators are protected under the 711 HPW Operations Security Program and the 711 HPW Critical Information and Indicators List (CIIL). Contractor employees granted access to critical information and indicators will be provided initial OPSEC training by the 711 HPW OPSEC Coordinator upon in-processing and prior to being granted access to CIIL items related to the contract/Task Order. The Contractor will also participate in 711 HPW’s annual OPSEC training and education programs, which includes periodic updates and refresher training on CIIL items applicable to the contract/Task Order. The 711 HPW OPSEC coordinator will evaluate the OPSEC posture of AF contract activities and operations. (*Applicable to classified efforts only; delete if unclassified*)

7.3 All Contractor personnel require a minimum of a Tier 1 background check (T1)/SF85 for any position that requires access to the internet, use of automated information systems to cover standalone computers or unescorted entry into restricted or controlled areas prior to reporting for duty in support of any requirement. The investigation is not for a security clearance; it is for a position of trust. This is a mandatory requirement set forth in DoDM 5200.02_AFMAN 16-1405, Air Force Personnel Security Program. All documentation required for security certification shall be the responsibility of the Contractor. (*Applicable to classified efforts as well as unclassified*)

7.4 Highest Security Classification: [Insert]

8.0 SAFETY REQUIREMENTS

8.1 The Contractor shall comply with all applicable federal, state, and local safety, occupational health and environmental regulations.

8.2 Contractor must cooperate with any DAF investigation in the event of any reportable damage or injury, to include toxicology testing per DAFI 91-204 paragraph 2.14 and 2.6.4.3.4.

8.3 An approved Safety Plan IAW AFI 91.202, AFRL Supplement 1 is required before any experiment may be conducted. The Contractor must comply with all Air Fore safety environmental regulations.

8.4 The Contractor must immediately notify the Contracting Officer of any work-related mishap that involves, or appears that it may involve a fatality, total or partial permanent disability of any employee, inpatient hospitalization of any employee, or property damage over $2,000, regardless of whether such matters involve government or private personnel/property. The Contracting Officer should notify the contracting element safety office of reported contractor mishaps normally within 24 hours of occurrence. Additionally, the Contractor should also notify the Contracting Officer of any illness or injury that is, or appears that it may be, an OSHA recordable illness/injury as defined by 29 CFR 1904 as soon as reasonably possible, but not later than on the first business day following the day on which the illness/injury occurred, regardless of whether such matters involve government or non-government personnel. Contractor is required to investigate all mishaps, illnesses, and injuries, report the results of such investigations, and cooperate with any government investigation of such matters, as requested by the Contracting Officer.

9.0 USE OF LIVE ANIMAL SUBJECTS (*Only include if Animal Use Applies*)

9.1. Should the use of animal models be required for this effort, the Contractor shall comply with the provisions of the following directives/regulations:

a. DoD Directive 3216.01, "Use of Animals in DoD Conducted and Supported Research Training" (20 March 2019); and

b. DHA-MSR 6025.02/AR 40-33/AFMAN 40-401(I)/SECNAVINST 3900.38D/DARPAINST18/USUHSINST 3203 “The Care and use of Animals in DoD Research, Development, Test and Evaluation (RDT&E) or Training Programs” (18 June 2019).

9.2. The use of live animals shall not commence until:

a. The Contractor’s Institutional Animal Care and Use Committee (IACUC) has approved the animal protocol.

b. The appropriate DoD/service veterinarian has reviewed and approved the animal protocol.

c. The appropriate DoD/service veterinarian has conducted, if necessary, a site visit to the Contractor’s facilities.

10.0 PROTECTION OF HUMAN SUBJECTS (*Only include if Human Use Applies*)

10.1 Should the use of human subjects be required for this effort, the Contractor shall comply with the provisions of the following directives/regulations:

a. Title 32, Code of Federal Regulations, Part 219 (32 CFR 219), "Protection of Human Subjects"

b. Department of Health and Human Services Regulations, "Protection of Human Subjects" (45 CFR Part 46)

c. DoD Instruction 3216.02, "Protection of Human Subjects and Adherence to Ethical Standards in DoD Supported Research”

d. Air Force Instruction 40-402, “Protection of Human Subjects and Adherence to Ethical Standards in Air Force Conducted and Supported Research”

e. Air Force Research Laboratory Instruction 40-402, “Protection of Human Subjects in Research”

10.2 Interaction with human research subjects shall not commence until approval from the Air Force Human Research Protection Official (HRPO) has been obtained. Interaction includes communication or interpersonal contact between investigator and subject for the purposes of conducting research.

10.3 If an IRB exemption is granted, the provisions above are still applicable, and the standard ethical principles shall still be adhered to as well as any other regulation or requirement applicable to a specific human-subject research protocol.

11.0 AFRL POLICY ON EMPLOYMENT OF NON-US CITIZEN CONTRACTORS

11.1 Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S. Government Information Technology networks in connection with the work on this contract must be U.S. citizens. Possession of a permanent resident card (“Green Card”) does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC).

12.0 FEDERAL HOLIDAYS

12.1 The prices / costs in Section B of the contract include holiday observance; accordingly, the Government shall not be billed for such holidays, except when services are required by the Government and are actually performed on a holiday. The following days are contract holidays: New Year’s Day, Birthday of Martin Luther King, Jr., Washington’s Birthday, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving Day, and Christmas Day.