PWS (MIT).doc

CUI

Performance Work Statement (PWS)

Armored Multi-Purpose Vehicle (AMPV) Component Criticality Analysis 14 September 2021 C.1 Background:

The Department of Test and Evaluation (DOT&E) is interested in developing analytical methods of improving the efficiency of its Live Fire testing processes. One method of achieving this goal is by better ensuring that Live Fire test matrices correctly prioritize components of interest for vulnerability assessments; this maximizes the advantage of finite testing resources for discerning the suitability of the tested system. Systems Capability Analysis Process (SCAP) is a relatively novel method for mapping component dysfunction to the eventual availability (or lack thereof) of discrete mission-relevant capabilities of the subject platform(s). Data Analysis Center (DAC) uses SCAP in concert with a systems-engineering approach, Massachusetts Institute of Technology (MIT)’s System-Theoretic Accident Model and Processes (STAMP), to get a more holistic picture of potential failures during a mission scenario.

C.2 Objective:

DAC has agreed to perform a SCAP-based vulnerability analysis on the AMPV platform as a complement to its simultaneously executed Live Fire test and evaluation program by providing subject-matter expertise (SME), guidance, review, and development assistance to a STAMP-based vulnerability analysis of the AMPV platform. The anticipated deliverable output is a systematic ranking of components by essentialness to the completion of defined missions, commentary on appropriate prioritization of test events in a Live Fire context, and suggestions for reducing mission-based vulnerability. STAMP is required for consideration of non-threat sources of component failure that might aggravate typical threat events.

C.3 Requirements:

C.3.1 The Contractor shall assist in defining a mission context for the SCAP analysis that is also amenable to consideration in STAMP methodology.

C.3.2 The Contractor shall review DAC’s proposal for the analysis scope; that is, definition of subject platforms and failure modes appropriate for both SCAP and STAMP consideration within the available time and manpower resources.

C.3.3 The Contractor shall provide instruction on implementing STAMP in vulnerability analyses.

C.3.4 The Contractor shall provide assistance with identifying a comprehensive (or nearly so) set of potential failure modes within the defined problem, and guidance on how to categorize and define the failures.

C.3.5 The Contractor shall provide advice on how to incorporate STAMP output into the SCAP model “ecosystem” without misrepresenting or oversimplifying the results.

C.3.6 The Contractor shall provide assistance with identifying potential risk-mitigation strategies for identified vulnerabilities.

C.3.7 The Contractor shall review DAC’s usage of STAMP upon completion of the project and provide verification of appropriateness.

C.3.8 The Contractor shall participate in weekly status update meetings with DAC via telephone or video conferencing system.

C.3.9 The Contractor shall prepare and furnish educational material on STAMP implementation as required by DAC.

C.3.10 The Contractor shall review, comment on, and return documents submitted by DAC within fifteen (15) business days.

C.3.11 The Contractor shall perform any necessary external research for assisting DAC with its completion of the AMPV analysis.

C.3.12 The Contractor shall participate in regularly scheduled program reviews hosted by DOT&E along with DAC.

C.3.13 The Contractor shall participate in status meetings, to be held at least quarterly, with the Contracting Officer’s Representative (COR) and Contracting Officer (KO), to be scheduled by the KO to discuss the progress of the contract, performance of the Contractor, and any problems that have arisen or are expected to arise.

C.4 Deliverables:

C.4.1 The Contractor shall provide a summary report of DAC’s STAMP implementation from the subject-matter expert perspective, focusing on lessons-learned, ways for DAC to improve or ensure standardization of its STAMP implementation going forward, and suggestions for avoiding observed problems. The report shall be due thirty days (30) before the end of Period of Performance (PoP).

C.4.2 The Contractor shall provide a Final Report implementing a review of SCAP/STAMP’s applicability to the AMPV analysis problem, with suggestions for how to tailor their implementation to Live Fire requirements (or vice versa) and a list of ideas for how to expand the use of SCAP/STAMP within the tri-service context of survivability/vulnerability modeling. The report shall be due thirty days (30) after the end of the PoP.

C.5 Period of Performance:

The PoP for this project will be Fiscal Year 2022 with dates to be determined.

C.5 Non-Personal Services:

ARL/ALC/GARRISON NON-PERSONAL SERVICES (JUL 2012)

The contractor, as an independent contractor and not as an agent of the Government, shall provide the necessary resources (except those furnished by the Government) to accomplish tasks of the type set forth in the Performance Work Statement.

Contractor employees performing services under this contract shall be controlled, directed and supervised at all times by management personnel of the contractor. The contractor's management shall ensure that employees properly comply with the performance standards outlined in this Performance Work Statement and as required by the contracting officer or the contracting officer's representative (COR). Contractor employees shall perform independent of and without the supervision of any Government official. Actions of contractor employees may not be interpreted or implemented in any manner that results in any contractor employee creating or modifying Federal policy, obligating the appropriated funds of the U.S. Government, overseeing the work of Federal employees, providing direct personal services to any Federal employee or otherwise violating the prohibitions set forth in Parts 7.5 and 37.1 of the Federal Acquisition Regulation (FAR). The Government shall control access to the facility and shall perform the inspection and acceptance of completed work and tasks.

C.6 AT-OPSEC Requirements:

ANTI-TERRORISM (AT) – OPERATIONAL SECURITY (OPSEC) REQUIREMENTS

The following AT-OPSEC requirements apply:

For information assurance (AA)/information (IT) training. All contractor employees and associated subcontractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 which must be completed upon contract awards.

For information assurance (IA)/information technology (IT) certification. Per DoD 8570.01-M, DFARS 252.239.7001 and AR 25-2, the contractor employees supporting IA/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

C.7 Distribution Statement D:

DISTRIBUTION STATEMENT D

Distribution authorized to the Department of Defense and U.S. DoD contractors only critical technology, dated 14 September 2021. Other requests shall be referred to the Army Research Laboratory, ATTN: Andrew Drysdale, RDRL-SED-P, Aberdeen Proving Ground, MD 21005.

Contracting Officer:

CUI