21R0022 Amendment 1.docx

N6893621R0022

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 08-Apr-2022 03:00 PM to 19-Apr-2022 03:00 PM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0001

The CLIN description has changed from Air Weapons Syst. Analysis - Completion to Air Weapons Syst. Analysis - Fixed Price.

The following have been modified:

*This clause only applies to work under Section B CLIN 0002 (Term Type Orders) of the contract.

B-TXT-STRMLND Streamlined Ordering Procedures for Cost Plus Fixed Fee Term Level of Effort (LOE) Orders (MAR 2020)

LOE Orders will be issued under this contract using the following streamlined ordering procedures:

(1) For each proposed order, the contracting officer will provide the contractor with a Statement of Work (SOW) and an Independent Government Cost Estimate (IGCE). The IGCE is an estimate of labor hours by labor category utilizing the estimated and negotiated Composite Labor rates table below to calculate the total estimated cost for the proposed Task Order (TO). The TO fixed fee is calculated using Section H Clause 5252.232-9510 PAYMENT OF FIXED FEE (NAVAIR).

(2) These Composite rates are estimates, and invoicing will be based upon actual costs incurred. Ceiling for Other Direct Costs (ODC) will be priced in accordance with the Government estimate. TOs crossing multiple years will be estimated by the Government using the composite rates for each year in proportion to the period of performance of the TO.

(3) Within three (3) working days of receipt of the SOW and IGCE, the contractor will respond:

(i) If the contractor agrees that it can perform the TO within the parameters of the SOW/IGCE, they will notify the contracting officer within three (3) working days of receipt of the SOW and IGCE. If the requirement remains valid, a priced order will be issued to the contractor.

(ii) If the contractor does not agree with the SOW or IGCE the contractor shall submit a proposal to the contracting officer within five (5) working days of receipt of the SOW and IGCE, addressing only the specific areas of difference in labor categories and/or hours in the IGCE. Once the differences are resolved between the contracting officer and the contractor, and the requirement remains valid, a priced order will be issued to the contractor.

(iii) If the contractor fails to respond to the proposed order within five (5) working days of receipt of the TO, the contracting officer may unilaterally issue the TO or extend the deadlines above when in the best interest of the Government.

(Exclusive of Fee)

Program Manager (Senior)*

Aerospace Engineer (SME)*

Aerospace Engineer (Senior)

Proj Engineer (SME)*

Proj Engineer (Senior)

Proj Engineer (Journeyman)

Proj Engineer (Jr.)

Scientist (SME)

Proj Analyst (SME)

Proj Analyst (Senior)

Tech/Admin Assist

*Indicates Key Personnel

For reference purposes only.

Below is a table of the corresponding BLS Standard Occupation Classification (SOC) Title and BLS Occupation Code:

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

PERFORMANCE WORK STATEMENT

Performance Work Statement for Air Weapons Systems Vulnerability Analysis, Systems Safety Analysis, Vulnerability Testing, Modeling and Simulation and Verification, Validation and Accreditation

22 March 2022

Prepared by Naval Air Warfare Center Weapons Division China Lake, CA 93555

DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense (DoD) and U.S. DoD contractors only; Critical Technology; 14 November 2012. Other requests for this document shall be referred to Commander: Naval Air Warfare Center, Weapons Division (Code 47L300D), 1 Administration Circle, China Lake, CA 93555-6100.

1.0 SCOPE

This Statement of Work (SOW) defines the effort to provide Research Development Test and Evaluation (RDT&E) analysis to the Naval Air Warfare Center Weapons Division (NAWCWD) in the areas of air weapons systems survivability; lethality; test and analysis support; Modeling and Simulation (M&S); and M&S Verification, Validation, and Accreditation (VV&A) support. Elements of contract support include Research & Development (R&D) of the following: (1) Navy platform survivability; (2) weapon system lethality and safe escape analysis; (3) survivability simulations; (4) survivability systems engineering analysis; (5) test and analysis support; and (6) the documentation inherent in the engineering or analysis process.

1.1 BACKGROUND

The Vulnerability Analysis Branch, Code D512400, of the of the Naval Air Systems Command (NAVAIR), NAWCWD supports Department of Defense (DoD) Agencies by providing survivability and lethality analysis, testing, and product assurance support to Integrated Product Teams (IPT’s) for Naval aviation aircraft and weapons systems operating in a non-nuclear threat environment. As such, they support both Navy and Tri-Service Programs for aircraft and air weapon systems survivability, lethality, vulnerability, susceptibility, safe escape, mission effectiveness, and battle damage reparability design, analysis and test efforts. NAWCWD also provides cognizance over live-fire testing of air weapon systems, including fixed and rotary wing aircraft, unmanned air vehicles, and missiles and/or ordnance that are air, surface, or subsurface launched. Also included are the integral components and subsystems of these platforms, and their operational support systems. Air weapon systems are evaluated in air and surface environments against air, surface, and/or subsurface launched threats. Threats encompass conventional, chemical, and directed energy weapons. Simulations include threat encounters while on the surface as well as in the air, operational support facilities, and related systems.

2.0 APPLICABLE DOCUMENTS

The most current version of each document shall apply throughout the performance of this order.

2.1 DEPARTMENT OF DEFENSE SPECIFICATIONS

2.1.1 DoD 5220.22-M, National Industrial Security Program Operating Manual, Change 2, 18 May 2016

2.1.2 SECNAV M-5510.36, Information Security Program, 1 Jun 2006

2.1.3 DoDM 5200.01, DoD Information Security Program: Controlled Unclassified Information (CUI) Vol. 4, 9 Sept 2018

2.1.4 DoDM 5400.07, Freedom of Information Act (FOIA) Program, 25 Jan 2017

2.1.5 DoDI 5230.24, Distribution Statements on Technical Documents, Change 3, 15 Oct 2018

2.1.6 SECNAV M-5510.30, Personnel Security Program, 1 Jun 2006

2.1.7 OPNAVINST 3440.17A, Navy Installation Emergency Management Program, 1 Aug 2014

2.1.8 OPNAVINST 2221.5D, Release of Communications Security Material to U.S. Industrial Firms Under Contract to the Department of the Navy (15 Aug 2016)

2.1.9 OPNAVINST 3432.1A, Operations Security (4 Aug 11)

2.1.10 DoDI 5200.02 Department of Defense Personnel Security Program (PSP), Change 3, 24 Sep 2020

2.1.11 DoDI 5000.61, DoD Modeling and Simulation (M&S) Verification, Validation and Accreditation (VV&A), Change 1, 15 Oct 2018)

2.1.12 NAVAIRINST 5510.38, Naval Air Systems Command National Security Program, 7 Feb 2013

2.1.13 NAWCWDINST 5500.01, Command Security Program Regulation, 13 Feb 2012

2.1.14 NAWSINST 5530.1B, Physical Security Plan, 31 Jan 2012

2.2 OTHER GOVERNMENT DOCUMENTS

2.2.1 MIL-STD-3022, Department of Defense Standard Practice: Documentation of Verification, Validation and Accreditation (VV&A) for Models and Simulations (April 2012)

2.2.2 MIL-HDBK-336-1, Survivability, Aircraft, Nonnuclear, General Criteria - Volume 1 (25 Oct 82)

2.2.3 MIL-HDBK-336-2, Survivability, Aircraft, Nonnuclear, Airframe – Volume 2 (21 Sep 83)

2.2.4 MIL-HDBK-336-3, Survivability, Aircraft, Nonnuclear, Engine – Volume 3 (4 Feb 83)

2.2.5 MIL-HDBK-336-4, Survivability, Aircraft, Nonnuclear, General Classified (U) – Volume 4, (5 Apr 85) (Classified)

2.2.6 MIL-HDBK-2069, Military Handbook, Aircraft Survivability (10 April 97)

2.2.7 MIL-HDBK-2089, Military Handbook, Aircraft Survivability Terms (30 May 97)

2.2.8 JTCG/AS-95-M-005, Configuration Management Requirements Study

2.2.9 JASPO-03-M-002B, Accreditation Support Package (ASP) Specification, Rev B (May 05)

2.2.10 JTCG/AS-97-M-008, VV&A from A to Z, A SMART Approach to VV&A for Acquisition M&S (Oct 97)

2.2.11 JTCG/AS-97-M-009, How to VV&A Without Really Trying, SMART VV&A Lessons Learned, (Nov 97)

2.2.12 Defense Modeling and Simulation Office (DMSO) VV&A Recommended Practices Guide (RPG) Build 2.5 or current issue at http://vva.dmso.mil

2.2.13 EKMS 1B EKMS, Policy and Procedures for Navy Electronic Key Management System Tiers 2 & 3, (5 Apr 10)

2.3 INDUSTRY DOCUMENTS

2.3.1 Robert E. Ball, The Fundamentals of Aircraft Combat Survivability Analysis and Design, Second Edition, (Reston, VA: American Institute of Aeronautics and Astronautics, 2003)

2.3.2 ANSI/EIA-649-1998 National Consensus Standard for Configuration Management IEEE Standard 828-2005, IEEE Standard for Software Configuration Management Plans, August 2005

3.0 REQUIREMENTS

3.1 GENERAL REQUIREMENTS

3.1.1 Compatibility

The Contractor shall prepare documents and software packages compatible with the Government IT environment through the security classification of TOP SECRET. The current operating environment required for this contract includes:

· Microsoft Windows 10

· Microsoft Project 2019

· Microsoft Office Professional Plus 2016

· Adobe Acrobat Reader DC

· Internet access

· LINUX

The Contractor shall interface with, and transfer data to and from, requiring office software applications and their upgraded versions. The Contractor shall have state-of the-art anti-virus software and ensure that all media are virus free when delivered. The Contractor shall use Internet and LAN communications with the Vulnerability Analysis Branch. Contractor personnel shall have real-time communications, both voice and data transfer capabilities, with the Vulnerability Analysis Branch during working hours whether at Contractor work site or on travel.

3.1.2 Work Location, Facilities and Telework

3.1.2.1 Work Location

Approximately 0% of work will be performed at Government site and 100% of work will be performed at Contractor site.

3.1.2.2 Meeting Support

In support of the tasking outlined in this SOW, the Contractor shall host and conduct meetings at the classification levels up to SECRET with the capacity to support a minimum of 10 persons and have contractor furnished telephone and VTC capability as well as sufficient equipment to conduct meetings with presentations including compatible software as required in paragraph 3.1.1.

3.1.2.3 Telework

The Contractor, upon notification to, and concurrence from, the Contracting Officer's Representative (COR) that the employees' work tasking is eligible for telework, may utilize alternate worksites/locations and telework to support continued performance of its contract in accordance with company policy. Contractor discretion is required when making alternate worksite and telework decisions based upon the nature of support provided by the employees. In the event telework is utilized, the Contractor remains responsible for performance, and compliance with any applicable cost accounting standards and contract cost principles / procedures. The Contractor shall adhere to all applicable federal laws, regulations, and individual (DoD) Service guidelines.

3.1.3 Contract Status Reporting

3.1.3.1 Monthly Progress and Financial Status Report

The contractor shall provide a progress and financial status report in accordance with the Contract Data Requirement List (CDRL A00A). The report shall include progress on all outstanding Task Orders (TO), and both monthly and cumulative man-hour labor costs expended by labor category, material, and travel costs.

3.1.4 Work Schedule: Compressed Work Schedule (CWS), overtime, holidays, and installation closure

3.1.4.1 Work Schedule

The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hours (including at a minimum 30-minute lunch break), from 0800 to 1700 Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.1.2).

3.1.4.1.1 Compressed Work Schedule (CWS)

CWS is an alternative work schedule to the traditional five 8.5-hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period of time: Eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch), and one weekday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the second week.

The Contractor may allow its employees to work a CWS schedule provided the requirements of this SOW are met. If the contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule, vice the standard schedule, are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage as required by the Government to the ACOR/COR.

3.1.4.1.2 Holidays

The Government observes the following holidays:

New Year’s Day, January 1 Martin Luther King’s Birthday, the third Monday in January President’s Birthday, the third Monday in February Memorial Day, the last Monday in May Juneteenth, June 19 Independence Day, July 4 Labor Day, the first Monday in September Columbus Day, the second Monday in October Veteran’s Day, November 11 Thanksgiving Day, the fourth Thursday in November Christmas Day, December 25

With the exception of the events in section 3.1.4.1.3 below, the Contractor is permitted to observe the above Holidays in accordance with its corporate policy.

3.1.4.1.3 Installation Closure

When Federal facilities are closed by the Government, or when Federal employees are officially excused from work due to a holiday, special event, severe weather, a security threat, or any other Government facility related problem, that prevents Federal personnel from working at the Government facility, Contractor personnel assigned to work at that facility, in support of such Federal employees, shall follow their parent company’s policies.

While generally Contractor personnel may not perform work on-site at a Government facility without oversight from Federal personnel, in very limited circumstances, work being performed by Contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility, despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by Contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Procuring Contracting Officer (PCO) must concur with any determination that work being performed by contractor personnel is mission essential.

3.1.4.1.4 Overtime

Overtime cannot be charged directly to the contract unless first approved in writing by the Contracting Officer.

3.1.5 Other Direct Costs

3.1.5.1 Travel

Travel may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of program tasking may be required. If required, temporary travel locations include: China Lake, CA; Philadelphia, PA; Aberdeen, MD; and Patuxent River, MD. This list is not all inclusive as locations may change over the life of the contract.

3.1.6 Subcontractors and Consultants

Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this SOW shall flow down to subcontractors providing support under this contract.

3.1.7 Management of Contractor Personnel

The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will the Government assign tasks to, or prepare work schedules for individual contractor employees. The Contractor shall manage its employees and guard against any actions related to personal services, or give the perception of personal services.

3.1.8 Transition Out Strategy

The Contractor’s overall transition out strategy shall be built around maintaining the mission of the Vulnerability Analysis Branch with minimal impact, not only in terms of timeliness of performance, but also to ensure that critical data and knowledge transfer occurs. Upon termination or expiration of the contract, the Contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The Contractor shall submit a Transition Out Plan, to include the minimum elements listed below in accordance with CDRL A00D.

· Work Turnover. The Contractor shall provide a plan of action to effectively transfer tasked work that is in-process at the expiration or termination of the contract to the successor company. Establish and maintain effective communication with the incoming Contractor or Government personnel for the period of transition via weekly status meetings.

· Quality Assurance. The Contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.

· Risk Mitigation Strategies. The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

· Data/Information Transfer. The Contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

3.2 SECURITY

3.2.1 Citizenship Requirements

Only U.S. citizens may perform under this contract. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

1) The individual's name, date and place of birth, position title, and current citizenship.

2) A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

3) A statement of the unusual expertise possessed by the applicant.

4) A statement that access will be limited to a specific government contract (specify contract number).

5) A statement that the Contractor has obtained an export license for the information required to perform the contract.

3.2.2 Personnel Security

The Contractor shall provide personnel with the appropriate personnel security clearance levels for the work to be performed. Access to TOP SECRET information is required in the performance of this contract and will be in accordance with the DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), incorporating change 2, 18 May 2016, applicable DoD personnel security regulations, and DoD Contract Security Classification Specification (DD Form 254). The Contractor shall maintain sufficiently cleared personnel to perform the tasks required by this SOW in accordance with the DD Form 254 and the contract. All Contractor personnel shall possess the requisite security clearance, accesses, and need-to-know commensurate with the requirements of their positions. All contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable Tier 3 (T3) investigation.

3.2.3 Security Requirements

All Contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the Contract's DD-254, Contract Security Classification Specification Form.

Contractor personnel shall require access to classified information in performance of this contract up to and including TOP SECRET with a safeguarding level of TOP SECRET. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

The Contractor shall comply with security requirements specified in the DD-254. Information or data that the Contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled in accordance with the appropriate designation (CUI; Covered Defense Information). Distribution is authorized to the Requiring Office's Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the COR of this contract for approval.

CUI including Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoD Instruction 5200.48, CUI available at:

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF

Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24 (Distribution Statements on Technical Documents); and have this statement displayed per DoDI 5230.24, Enclosure 3.

3.2.4 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR-N)

3.2.4.1 SAAR-N

All Contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within thirty (30) days of their first day of work. Instructions for processing the SAAR-N forms are available at:

http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf

SAAR-N forms shall be submitted to the Contracting Officer’s Representative (COR), Government Technical Point of Contact (TPOC), or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate.

3.2.4.2 Command Access Cards (CAC) / Local Badges

Contractor CACs and facility specific identification badges will be issued by the Government to on-site Contractor personnel and shall be visible at all times while personnel are at the Government site. The Contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to all DoD and NAWCWD instructions. All CACs and identification badges issued to Contractor employees shall be returned to the COR following completion of the contract, relocation or termination of an employee, or upon request from the COR. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with local security and facility requirements.

In order to maintain access to Navy IT resources, the Contractor shall ensure completion of the most current initial and annual DoD Cyber Awareness Challenge training. The Contractor shall ensure completion of a Cyber Awareness Training Certificate or the latest version thereof, monitor expiration of requisite background investigations, and initiate re-investigations as required.

If requested, the Contractor shall provide to the COR/ACOR or designated SAAR-N Government Sponsor documentation sufficient to prove that it is monitoring/tracking the SAAR-N requirements for its employees who are accessing Navy IT resources. For those Contractor personnel not in compliance with the requirements of this clause, access to Navy IT resources will be denied/revoked.

3.2.4.3 DD-254

The Contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as CUI. Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the TPOC/COR of this contract for approval.

3.2.5 Information Security

Direct Support contractor personnel working under the purview of a DoN Commanding Officer/Commander shall comply with the local security provisions and the requirements of SECNAV M-5510.36B (series). The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of CUI and to control distribution of CUI in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), and SECNAV M-5510.36B

For Official Use Only information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDI 5200.48, Controlled Unclassified Information. The Contractor shall not store or transmit CUI on personal information technology systems or via personal e-mail. Unclassified e-mail containing any DoD CUI shall be encrypted. Prior to sending CUI to any non-Navy Marine Corps Internet (NMCI) addressees, the sender must first positively verify all recipients are authorized access to CUI and have need-to-know. Non-NMCI recipients must have a DoD compliant Private Key Infrastructure (PKI) certificate that enables electronic transmission via unclassified networks while protecting the CUI with a digital signature and encryption.

3.2.5.1 Marking

All information generated by the Contractor shall be properly marked. CUI information generated and/or provided under this contract shall be marked in accordance with DoDM 5200.01. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDD 5230.24 and program Security Classification Guidance

3.2.5.2 Public Release

Disclosure of information is covered by DFARS 252.204-7000 Disclosure of Information, incorporated in Section I of the contract. In regards to subsection (a)(2), “information otherwise in the public domain” is information officially released into the public domain (e.g. via Distribution Statement A) and does not include information in the public domain that has not been officially released. For disclosure of unclassified information that has not been officially released, the Contractor must seek specific approval from the PCO, with approval from the NAWCWD Public Affairs Office (PAO).

3.2.5.3 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information

All instances of loss, compromise and electronic spillage of classified or CUI shall be reported to the COR, TPOC and Government Security Office within 24 hours of the incident.

3.2.6 Operations Security (OPSEC)

The Contractor shall comply with the OPSEC requirements outlined within the DD Form 254.

The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. The OPSEC program shall be in accordance with DoD and DON operations security (OPSEC) requirements, to include:

1) Assignment of responsibility for OPSEC direction and implementation.

2) Planning guidance for the use of OPSEC practices and principles to identify vulnerabilities and apply applicable countermeasures. (Contact NAWCWD Industrial Security Office for a current OPSEC Annex and CI Guide).

3) Establishment of OPSEC education and awareness training.

4) Provisions for management, annual review, and evaluation of OPSEC programs.

5) Flow down of OPSEC requirements to subcontractors when applicable.

While performing aboard NAVAIR or NAVAIR sites, the Contractor shall comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts. Include OPSEC as part of its ongoing security awareness program and take all required Agency training. The Contractor shall be responsive to the Supporting OPSEC Manager on a non-interference basis. The Contractor shall protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by Digital Precision Strike Suite (DPSS) and contractor in support of the mission.

The Contractor shall prepare an Operations Security Plan for Government review in accordance with CDRL A00C.

3.2.7 Communications Security (COMSEC)

The Contractor will require access to COMSEC at Government/Contractor locations. U.S. cryptographic equipment inventory information, as well as the systems and manner in which each particular equipment is used, is for official use only. Publication or release of any related COMSEC information, by the Contractor, without prior written approval of the PCO is prohibited. The Contractor must be a U.S. citizen, have a final Government security clearance with the appropriate personnel security background investigation for the level of classification involved, have strict need-to-know, have the appropriate COMSEC briefing before access is granted, and granted access only in conformance with procedures established for the particular type of COMSEC information involved. The Contractor shall adhere to the DD Form 254 COMSEC security requirements, facility COMSEC material control and operating procedures, and all applicable COMSEC regulations, instructions, and policies. Prior approval from the Government Contracting Activity is required in order for a prime Contractor to grant COMSEC access to a subcontractor.

3.2.8 Anti-Terrorism Force Protection and Emergency Management

The work performed on this contract is not Emergency Essential in accordance with OPNAVINST 3440.17A and Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans and directives. Contractor personnel shall not report for work at Government facilities upon declaration of Force Protection Condition CHARLIE or in any event or emergency where Government officials direct curtailment of operations to “Mission Essential Only”. All Contractor personnel assigned to a Government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.

3.3 DETAILED SUPPORT REQUIREMENTS

The Contractor shall perform the following research and development requirements under this contract:

· Research and Analysis of Air Weapon Systems

· Test and Analysis Support

· Simulation Development Support

· M&S VV&A

· Technical Meetings

· Reporting

In performance of these research and development requirements, the Contractor shall be required to use the following M&S “Core” and “Secondary” tools. “Core Tools” are those tools expected to be used regularly, while “Secondary Tools” are tools that are expected to be used occasionally. Specific tools to be utilized are determined in individual task orders. Tools operate in LINUX, Windows Operating System, or both, and are compatible with modern desktop workstation solutions. The Contractor shall provide personnel to setup and run the required tools listed below, as well as other M&S tools available from the DoD survivability community.

Core Tools:

Secondary Tools:

The Contractor shall be familiar with the functions and services performed by, and available from, the Defense Systems Information Analysis Center (DSIAC), the repository for Government owned M&S.

Task Orders for Information Technology (IT) Support Services are prohibited under this SOW. Examples of these services include the purchase, installation, and administration of individual computers or computer systems for Government use.

3.3.1 Research and Analysis of Air Weapon Systems

The Contractor shall perform research analysis of weapon systems (air/surface/sub-surface launched). The Contractor shall perform analysis of Navy and Tri-Service air weapon systems including aircraft of all types, unmanned air vehicles, missiles and/or ordnance that are air, surface, or subsurface launched. Contractor analysis shall combine the results of any or all of the following elements: vulnerability analysis, susceptibility analysis, survivability analysis, lethality analysis, safety or safe escape analysis, specification development, tradeoff analysis, mission effectiveness, cost and operational effectiveness analysis, analysis of alternatives, data acquisition and reduction, and air-vehicle battle damage repair. (CDRL A001)

3.3.1.1 Vulnerability Analysis:

The Contractor shall perform vulnerability analysis of air vehicles including: Fault Tree Analysis, Failure Mode Effects and Criticality Analysis (FMECA), Damage Mode and Effects Analysis (DMEA), Geometric Model Development, Vulnerability Index Development (for models such as COVART, AJEM, and UEDDAM), and Vulnerability to Directed Energy Weapons (DEW). All analysis products shall be submitted to the Government for review and approval. (CDRL A002)

3.3.1.1.1 Fault Tree Analysis

For Fault Tree Analysis, the Contractor shall acquire or develop detailed system schematics, fault trees and disablement diagrams, tactical manuals, mission/threat analysis results. The Contractor shall develop combat damage fault trees including specified critical subsystems from these inputs. The fault trees the Contractor prepares must be suitable for use in the appropriate vulnerability index generating code or process used in the vulnerability analysis. (CDRL A002)

3.3.1.1.2 Failure Mode Effects and Criticality Analysis (FMECA)

Based on the results of the fault tree analysis, the Contractor shall conduct an FMECA to establish the required criticality of components of the target. (CDRL A002)

3.3.1.1.3 Damage Mode and Effects Analysis (DMEA)

Based on the results of the FMECA, the Contractor shall conduct a DMEA for the target. Successful performance of this requirement includes Contractor selection and documentation of appropriate probability of kill given hit (Pk/h) function for each critical component. Determination of appropriate Pk/h functions may require the Contractor to develop a specific analytical methodology, exercise and/or ballistic test data analysis and evaluation. (CDRL A002)

3.3.1.1.4 Vulnerability Indices

The Contractor shall develop vulnerability indices for air vehicles. These analyses may use existing models (such as COVART or AJEM). The Contractor shall update the models as required to perform vulnerability analyses. (CDRL A002)

3.3.1.1.5 Geometric Model Development

The Contractor shall develop an accurate computer geometric model of the target with enough detail to evaluate specific components included in the DMEA and to ensure that shielding of critical components is treated adequately. The Contractor shall generate these geometric models in a format compatible with the vulnerability analysis codes in use. (CDRL A002)

3.3.1.1.6 Vulnerability Assessments

For vulnerability to directed energy weapons, the Contractor shall conduct vulnerability assessments of air vehicles to laser, high power microwave, or other advanced directed energy threat systems. (CDRL A002)

3.3.1.2 Susceptibility Research Analysis

The Contractor shall conduct susceptibility research analysis supporting susceptibility assessments for air vehicles, combining the effects of the following factors: Air Vehicle Performance; Tactics; Mission Profiles; Electronic Warfare Analysis; Signature Analysis; Detection, Acquisition, and Tracking Analysis; Threat Vehicle Simulation; Threat Missile Endgame Analysis; and Susceptibility to Directed Energy Weapons. (CDRL A001)

3.3.1.2.1 Air Vehicle Performance

The Contractor shall provide air vehicle performance estimates of existing developmental and conceptual air weapons systems and their major subsystems, including avionics and propulsion. Performance includes speed/altitude and energy maneuverability envelopes and cruise and flight characteristics. These analyses may use existing models such as BLUEMAX. (CDRL A001)

3.3.1.2.2 Tactics

The Contractor shall perform analysis leading to the development of tactical alternatives, evaluation of tactics and development of measures of effectiveness (MOEs) for tactics analysis. These analyses may include air-to-air, air-to-ground, surface to air, surface to surface, manned and unmanned weapons systems. (CDRL A001)

3.3.1.2.3 Mission Profiles

The Contractor shall develop step-by-step mission profile models and flight paths to simulate penetration of integrated air defense systems (IADS). Theses mission profile models and flight paths shall be included in tactics and susceptibility investigations. (CDRL A001)

3.3.1.2.4 Electronic Warfare Analysis

The Contractor shall survey, acquire, develop, modify, test and exercise electronic warfare models and simulations to determine the effects of electronic warfare systems on air vehicle susceptibility and tactics. (CDRL A001)

3.3.1.2.5 Signature Analysis

The Contractor shall develop/improve the methodology to predict Radio Frequency (RF), Infrared Radiation (IR), visual, acoustic or other spectrum signatures for air vehicles; run computer simulation codes for predicting those signatures. The Contractor shall use simulation results, test data, and experience to develop signature predictions for specified air vehicles. (CDRL A001)

3.3.1.2.6 Detection/Acquisition/Tracking Analysis

The Contractor shall analyze the capability of various land, sea, and air sensor systems in order to detect, acquire and track air vehicles by utilizing appropriate computer simulation methodologies and intelligence information. The Contractor shall include the effects of command, control, and communication information (C3I) networks in the modeling process. (CDRL A001)

3.3.1.2.7 Threat Vehicle Simulation

The Contractor shall use M&S to evaluate the ability of surface-to-air and air-to-air missiles to launch, guide, and intercept air vehicles. The Contractor shall analyze the ability of land, sea, and air gun systems to hit air vehicles in a variety of tactical situations. The Contractor shall make improvements of existing methodologies and/or develop new models and simulations to perform these analyses as required. (CDRL A001)

3.3.1.2.8 Threat Missile Endgame Analysis

The Contractor shall analyze the ability of threat missile systems (land, sea and air launched) to fuze on air vehicles, and analyze the warhead effects on the probability of killing the air vehicle (making use of appropriate vulnerability models). The Contractor shall also participate in testing, model development and improvement, and analysis of fuzes and warheads. The Contractor shall conduct analysis of countermeasures effects on fuzes. The Contractor shall provide input in the design, exercise, data reduction, and analysis of tests designed to evaluate terminal trajectory characteristics of threat weapons systems. (CDRL A001)

3.3.1.2.9 Susceptibility to Directed Energy Weapons

The Contractor shall analyze the ability of threat directed energy weapons to intercept air vehicles, including lasers (high and low energy), high power microwave systems, or any other advanced threat systems. The Contractor shall include the effects of multiple threats and multiple targets, C3I effects, and the integration of advanced threats with conventional threat systems. (CDRL A001)

3.3.1.3 Survivability Analysis

The Contractor shall provide system survivability analysis of airborne weapons systems, including manned and unmanned aircraft, missiles, and fixed and rotary wing aircraft. These analyses shall include: integrating the results of vulnerability, and susceptibility analysis (3.3.1.1 and 3.3.1.2 above), mission/threat analysis, tradeoff analysis, and specification development. (CDRL A001)

3.3.1.3.1 Vulnerability and Susceptibility Analysis

The Contractor shall aggregate the results of vulnerability analysis and susceptibility analysis into an overall assessment of the survivability of the vehicle in the missions and scenarios evaluated. The Contractor shall collect the results of vulnerability and susceptibility analysis into the proper formats for inclusion into appropriate aggregated mission level survivability models such as BRAWLER for air-to-air applications, or SUPPRESSOR for air-to-surface missions. The Contractor shall include the effects of multiple threats and multiple targets, electronic countermeasures, integrated tactics, and air vehicle vulnerability and susceptibility factors. The Contractor shall participate in testing, model development and improvement, and documentation. (CDRL A001)

3.3.1.3.2 Mission and Threat Analysis

The Contractor shall evaluate the proposed scenarios, missions and threat systems postulated for employment of the air vehicle to determine the geographic locations, threat systems, C3I networks, mission profiles and integrated tactics to be evaluated. The Contractor shall research existing threat and operational requirements documents, survey air vehicle operational commands and developmental agencies, and provide close coordination with system developers. (CDRL A001)

3.3.1.3.3 Tradeoff Analysis

The Contractor shall conduct analysis of alternative air vehicle designs, at the component, subsystem, and mission systems levels, to determine the effects of design changes on performance, survivability and on system cost, weight and volume requirements. (CDRL A001)

3.3.1.3.4 Specification Development

The Contractor shall provide recommendations for the development of design specifications for air vehicle survivability and conduct survivability analysis defining survivability requirements for new systems. (CDRL A001)

3.3.1.4 Lethality Analysis

The Contractor shall provide system lethality analysis of weapon systems and weapon effects against defined targets. Analysis shall include: fuze and warhead interactions with air and ground targets; weapon guidance and trajectory characteristics; weapon delivery effectiveness; and safe-arming analysis. (CDRL A001)

3.3.1.4.1 Fuze / Warhead Design and Optimization

The Contractor shall evaluate existing, developmental, and/or conceptual fuze and warhead designs, and perform tradeoff studies directed toward optimizing weapon terminal effectiveness. (CDRL A001)

3.3.1.4.2 Terminal Geometry Analysis

The Contractor shall perform analysis of weapon trajectory characteristics to determine the endgame geometry relationship between the weapon and selected targets. This may require design, exercise, data reduction and analysis of tests designed to evaluate terminal trajectory characteristics of weapons systems. (CDRL A001)

3.3.1.4.3 Weapon Delivery

The Contractor shall evaluate the influence of target acquisition, recognition, and designation on the ability of the weapon system to deliver ordnance to the target. (CDRL A001)

3.3.1.4.4 Safe Arming and Safe Escape Analysis

The Contractor shall perform analysis to determine the proper safe-arming distance or time for air launched weapons. Contractor generated analysis shall include all or part of the process required to quantify and analyze the hazards to air launch platforms from weapon detonations following weapon release as a function of time and/or distance after release. The contractor shall also evaluate the effects of various post launch evasive maneuvers on hazard levels associated with weapon release. (CDRL A001)

3.3.1.5 Mission Effectiveness Analysis

The Contractor shall conduct analysis of air combat weapon systems to accomplish their missions within the context of a well-defined operational environment. The Contractor shall propose MOEs, conduct tactical analysis, evaluate approved alternative systems and tactics against those MOEs, and perform system tradeoff analysis to optimize system mission effectiveness. Mission effectiveness includes, but is not limited to: system survivability, lethality, and sortie generation. (CDRL A001)

3.3.1.6 Analysis of Alternatives (AOA)

The Contractor shall conduct AOA to evaluate air/surface/sub-surface combat weapon systems and alternatives to those systems. The Contractor shall propose MOEs, conduct tactical analysis, evaluate approved alternative systems and tactics against those MOEs, perform cost analysis, and perform system tradeoff analysis of various alternative air combat systems. Cost and operational effectiveness includes, but is not limited to: system survivability, lethality, sustainability, reliability, mission effectiveness and cost. (CDRL A001)

3.3.1.7 Air-vehicle Battle Damage Repair (ABDR)

The Contractor shall conduct analysis of aircraft battle damage repair requirements for the development of battle damage repair manuals, logistics model inputs, and air-vehicle system specifications. Successful performance of this requirement involves Contractor evaluation of aircraft component vulnerabilities, susceptibility analysis, and association of damage levels to non-critical as well as critical components. The Contractor shall participate in Joint Live Fire testing and evaluation, which shall include, but is not limited to: test planning, test setup, test execution, test results and documentation. (CDRL A001)

3.3.2 Test and Analysis Support

The Contractor shall provide test and analysis support including, but not limited to: preparing test plans, making pre-shot predictions, observing tests, collecting and reducing test data, analyzing and evaluating data, and reporting on findings. Contractor generated test data shall include visual observation data, quantitative sensor measurement data, and associated test conditions. Contractor generated analytical data shall include analysis parameters, methodology, and results. These tests shall include vulnerability testing (blast, ballistic, and directed energy) and susceptibility testing (signatures, countermeasures, threat system performance, effects of survivability features on threat system performance). (CDRL A003, A004)

3.3.2.1 Test and Analytical Data Review

The Contractor shall review test and analytical data to ensure an accurate and complete database. Emphasis shall be placed on ensuring complete test records are available and any test anomalies identified. The Contractor shall provide complete descriptions of analytical methodologies used, parameters considered, and values used shall be identified and evaluated. (CDRL A004)

3.3.2.2 Assessment of Analytical Estimates

The Contractor shall assess the…