Statement of Work Template Version.docx

GOVERNMENT SOW TEMPLATE

(Cover Page)

AIR FORCE RESEARCH LABORATORY

INFORMATION DIRECTORATE

ROME, NEW YORK

STATEMENT OF WORK

FOR

(INSERT TITLE – MUST MATCH Title on 2916 or PAW))

PCSN X-X-XXXX

DD MM YYYY

(Contract Number FA8750-22-C-XXXX)

TABLE OF CONTENTS

1.0 OBJECTIVE

· Objective is a brief overview

· Description of why this is being procured

· What are you trying to accomplish

· Stated objective should be consistent with RRS form 2916 and section 4.0 of SOW Example: The objective of this effort is to develop novel software systems that enable rapid and efficient adaptation of the resulting software system to radical changes in requirements and computational environments. SymLang, new programming language and its associated toolchain will allow for the rapid development and adaptation of code that is efficient at run-time over a wide range of operating conditions.

2.0 SCOPE

· Scope is an overall picture of the work to be accomplished and the desired end result. Outlines the various major requirements of the effort

· Must be consistent with the requirements of paragraph 4.0 (Technical Requirements) of the SOW.

· If a requirement is not in paragraph 4.0, it is not binding.

· The Scope is used for “in-scope” determination of additional work or changes to effort Example: The scope of this effort is to research, design, develop, demonstrate, test, integrate, and deliver the SymLang software system that will enable rapid adaptation of software to changes in requirements, platforms, and computational resources at a scale and speed appropriate for the complex software ecosystem upon which the U.S. Government, military, and economy depend.

3.0 BACKGROUND

· Background includes information, explanations or constraints

· Who, what, where, when and why this effort is needed

· Helps readers understand the need for this effort

· Can include applicable documents (which must be referenced in 4.0) and reference documents (nice to know info) Example: The Department of Defense (DoD) is highly dependent on software. The increasing complexity and scale of this software is creating new attack surfaces for adversaries and reducing the DoD’s ability to react to new threats. As currently practiced the cost of software engineering is constraining the ability of the U.S. Government to deploy new software-based capabilities, as more than 70% of the federal Information Technology (IT) budget is dedicated to Operations and Management (O&M). Software today is brittle with respect to changes in requirements and computing resources, requiring frequent and ultimately unaffordable modernization efforts to maintain adequate functionality.

Example Reference Document: AFRLI 61-103, Titled AFRL Research Test Management

4.0 TECHNICAL REQUIREMENTS. The Contractor shall accomplish the following:

· Defines the work to be accomplished

· Only legally binding section

· Indicates the main steps and action for the contractor, make sure all Government requirements are included

· Based on the contractor’s proposed sow and proposal

· Adding requirements not originally proposed may increase the cost of the effort

· Should not reflect a “how to” but a “what” is to be accomplished

· States the minimum performance that will satisfy the government

· For example, 4.1-Design, develop, test and evaluate multimode optical transceiver for military avionic communications.

· For example, 4.1.1-Design the transceiver to meet the following requirements:

· Besides Technical Requirements, paragraph 4.0 may include Management, Hardware and Software, Testing and Demonstration and Documentation Requirements

· Management requirements: project information, technical and financial status,

· Oral presentations: technical interchange or exchange meetings, reviews, working group meetings, etc.

· Hardware and software requirements: delivery, documentation, COTS, licensing and maintenance agreements, etc.

· Testing: in-plant testing, acceptance testing, site testing, certification testing, technical support during testing and test plans and reporting

· Demonstrations: prototype, rough example, applications, feasibility, performance or method; demonstration plans and reports

· Documentation: reports, software or hardware, summary reports, final technical report etc.

If you need assistance or have questions, please feel free to contact RIKA