CREATE SOW PH-2.pdf

Controlled Unclassified Information (CUI)

Statement of Work (SOW)

For Coherent Radar Electronic Attack Test Environment (CREATE)

1 Introduction

1.1 Overview

The Coherent Radar and Electronic Attack Test Environment (CREATE) project is sponsored by the Test Resource Management Center (TRMC) through the Central T&E Investment Program

(CTEIP). CREATE is an approved CTEIP Joint Improvement and Modernization (JIM) project that kicked off in August 2022, developing Navy and Air Force test capabilities to address three current Navy and Air Force Installed Systems Test Facility (ISTF) shortfalls in ground-testing modern aircraft radar modes.

I. No capability to ground test air-to-air (A/A) Advanced Signals Type 2 (AS-2) and future

AS (AS-N)

II. Limited capability to test cognitive radar (CR) detection processing

III. Limited capability creating realistic synthetic targets with integrated jamming to advanced and cognitive radar systems

Figure 1 shows the operational view (OV-1) of the CREATE system. The aircraft with an installed radar system is placed in an anechoic chamber facility and racks of CREATE radio frequency (RF) and computer equipment provide a virtual combat environment for the systems under test (SUTs).

Figure 1 – CREATE Operational View (OV-1)

CREATE expands upon and leverages past and current prototype systems (e.g. Advanced Radio

Frequency Simulator (ARFS), Navy Advanced Test Equipment (NATE), TRMC JIM (e.g. Radar

Air to Ground Environment (RAGE) and Pre Planned Product Improvement (P^3I) projects (e.g.

Waveform Agnostic Test Target Simulator (WATTS) that have pushed the state of the art in delivering A/A advanced signals (AS) capabilities. Investing in improved radar test and evaluation (T&E) capabilities is necessary for testing complex Fifth Generation aircraft sensor fusion algorithms and cognitive processes. Modern Radar systems are rapidly increasing in complexity, such as waveform/RF diversity, dynamic waveform creation and increased instantaneous bandwidth (IBW). CREATE intends to provide an ultra-wideband multi-target and jammer generator capability for testing AS that are both known (AS-1, AS-2) and unknown (AS-

N) and therefore waveform agnostic in nature. A classified decoder describing AS use cases has been provided.

1.2 Team Roles and Responsibilities

CREATE is a joint project with the US Navy and Air Force. The Government team, led by the

Navy’s Integrated Battlespace Simulation and Test (IBST) Department at Patuxent River, MD, will be the Lead System Integrator (LSI). The developers of the CREATE system are Mercury

Systems (MS) located in Cypress, CA and Georgia Tech Research Institute (GTRI) located in

Atlanta, GA. MS previously developed the Advanced Radar Environment Simulator (ARES) systems and the Radar Air to Ground Environment (RAGE) systems for the Navy and Air Force.

MS and GTRI shall be responsible for the design, development, delivery, integration, test and validation of the CREATE systems. This Delivery Order covers the scope of the MS tasking for

CREATE.

The IBST Department will provide guidance and oversight to coordinate the system design, development, integration, test and validation delivery activities of the CREATE team for the effort. IBST will maintain oversight control of the CREATE capability and performance through the Government review and approval of the contractor and vendor documented capabilities, performance specification and interface design and control linked allocations to the existing

System Requirements Specification (SRS) and the contractor developed Requirements

Traceability Matrix (RTM). IBST will manage and execute an integrated Test and Evaluation

(T&E) strategy for CREATE to verify system performance, integration, and certification requirements.

1.3 Scope

1.3.1 Scope Overview

This Statement of Work (SOW) supports the full scope of the CREATE project’s lifecycle from requirements to system delivery. To more effectively manage the CREATE project’s development, the SOW is divided into two, independently executed phases. The Government may incrementally fund each phase based on successful completion of intermediate milestones within each phase. Ceiling and Period of Performance (PoP) shall be established prior to award of each phase.

The scope of this SOW is divided as follows:

• Phase 1: Requirements and Preliminary Design (CLIN 0001)

• Phase 2a: Detailed Design, Critical Design Review (CDR) and Post-CDR Actions (CLIN

0002)

• Phase 2b: System Development, Integration, Test, and Delivery (CLIN 0002 - Future

Option)

• J-PRIMES Build to Print RAGE Advanced Signals Test Capability (ASTC) System

(CLIN 0003)

Phase 1 of the SOW addresses system requirements and preliminary design activities. Key deliverables shall include a revised RTM with system requirements and functions traceable to the

SRS, a system functional specification (SFS), and a preliminary design delivered in conjunction with a preliminary design review (PDR), and critical long lead item (LLI) material procurement.

The original draft RTM is being developed on a separate firm-fixed-price (FFP) bridge contract currently underway as of December 2024.

Phase 2 (CLIN 0002 Option) is divided into two sub-phases. Phase 2a addresses the detailed critical design activities through a Critical Design Review (CDR) and post-CDR action item resolution. Phase 2b covers system development, integration, test, and delivery to the

Government. Both sub-phases shall include material procurements. Phase 2b shall conclude with factory acceptance testing (FAT) at the Contractor’s facility, as well as site acceptance/integration testing (SAT) support and training at the Government sites.

CLIN 0003 addresses the J-PRIMES requirement for a delivered build to print RAGE Advanced

Signals Test Capability (ASTC) System to be delivered to the J-PRIMES facility in Eglin AFB, FL.

1.3.2 Phase 1: Requirements and Preliminary Design (CLIN 0001)

Using the studies and preliminary architecture work previously performed under separate contracts, the Contractor shall propose an approach for completing the CREATE system’s requirements and preliminary design. The Contractor shall base the proposed approach to meeting system requirements, design and architecture on the current technology maturity of key components. The Contractor shall perform requirements decomposition, technology feasibility and maturity assessments, early design activities, and project planning. The requirements and design approach shall address the areas of interest specified in this SOW. Phase I may include material procurements identified as critical long lead items (LLI) that could impact the project’s critical path to delivery. The Contractor is encouraged to address other areas of interest, not specifically highlighted by the Government, that the Contractor considers relevant to the

CREATE capability.

1. Develop materials for and support a kick-off (KO) meeting for the CREATE requirements and preliminary design phase. The KO meeting shall consist of

a) A programmatic presentation of the Contractor’s plans to complete the requirements and preliminary design phase

i. A detailed work breakdown structure (WBS)

ii. A technical and programmatic risk analysis with burn-down plan for all high-level risks

iii. A spend plan with funding requirements associated by Contract Line Item

(CLIN) for each month required for requirements and preliminary design that is updated at a minimum on a monthly basis

iv. A detailed WBS-based Integrated Master Schedule (IMS) in Microsoft

Project that is updated at a minimum on a monthly basis

v. A staffing plan indicating the number of full-time equivalents (FTE) proposed to perform the work by labor category. Contractor shall indicate the number of filled billets and the number of vacant billets remaining to be filled to complete the proposed tasking.

b) A review of the referenced CREATE specification as led by the Contractor.

Deliverables include draft programmatic information two weeks prior to the meeting, and final updated documentation within one week following the meeting

2. Develop materials for and support a System Functional Review (SFR). The SFR shall consist of:

a) An updated programmatic presentation of the Contractor’s plans to complete the

CREATE early preliminary design phase

b) Presentations demonstrating system functions and their relationship and traceability to the RTM

c) Preliminary modeling results of performance. Deliverables include an updated

RTM with system requirements and functions traceable to the SRS, a draft

System Functional Specification (SFS) in contractor format, a draft SFR presentation two weeks prior to the meeting, and final presentations within two weeks following the meeting

3. Develop materials for and support a Preliminary Design Review (PDR). The PDR shall consist of

a) An updated programmatic presentation of the Contractor’s plans to complete the

CREATE critical design phase

b) Presentations demonstrating system design maturity and how the design is decomposed to the functional baseline

c) Updated modeling results of performance. Deliverables include updated RTM with system requirements and functions traceable to the SRS, updated SFS with inputs from the system design, draft PDR presentations two weeks prior to the meeting, and final presentations within two weeks following the meeting

4. Develop post-PDR materials and develop draft materials in support of the Critical Design

Review (CDR). Post-PDR/pre-CDR shall consist of

a) Tracking and resolving post-PDR actions items

b) Updated requirements and design documentation based on results of PDR

c) An updated programmatic presentation of the Contractor’s plans to complete the

CREATE project through final delivery of all CREATE capabilities

1.3.3 Phase 2a: Detailed Design, Critical Design Review and Post-CDR Actions (CLIN

0002)

Phase 2a addresses detailed design activities to get to the Critical Design Review (CDR) milestone, and the subsequent resolution of action items to establish a final design baseline.

Phase 2a may include material procurements identified as critical long lead items (LLI) that could impact the project’s critical path to delivery. The Contractor is encouraged to address other areas of interest, not specifically highlighted by the Government, that the Contractor considers relevant to the CREATE capability.

1. Develop materials for and support a Critical Design Review (CDR). The CDR shall consist of

a. An updated programmatic presentation of the Contractor’s plans to complete the

CREATE project through final delivery of all CREATE capabilities.

b. Presentations demonstrating system design maturity and how the design satisfies the RTM down to the component level.

c. Updated and final modeling results of Advanced Signals performance.

d. Deliverables include detailed design specifications, an updated RTM with system requirements and functions traceable to the SRS, an updated SFS, and a draft

Factory Acceptance Test Plan (FATP) (CDRL A006). Design shall be traceable to all requirements in the RTM with validation methods identified in the documentation. Draft CDR presentations two weeks prior to the meeting and final presentations within two weeks following the meeting.

2. Develop post-CDR materials and develop draft materials in support of post-CDR. Post-

CDR shall consist of

a. Tracking and resolving post-CDR action items

b. Finalizing and delivering all design documentation based on the results and action items from the CDR

c. Providing an updated programmatic baseline (IMS, Spend Plan, Risk Register) for the execution of Phase 2b through final delivery of all CREATE capabilities

1.3.4 Phase 2b: System Development, Integration, Test, and Delivery (CLIN 0005 -

Future Option)

Phase 2b (Unfunded Future Option). Following the successful completion of Phase 2a and

Government approval to proceed, phase 2b covers the full system development, integration, test, and delivery to the Government. This phase shall include all remaining material procurements required for the full system development, fabrication, and assembly of software, hardware, and firmware components. Throughout development, the Contractor shall conduct risk reduction and demonstration events. Phase 2b shall conclude in both factory acceptance testing (FAT) at the

Contractor’s facility as well as site acceptance/integration testing (SAT) support and training at the Government site.

3. System Development

a. Procure remaining materials

b. Develop firmware, software, and hardware in accordance with the approved design

c. Perform risk reduction events, to include demonstration of development on a quarterly basis

4. System Test and Integration

a. Perform Test Readiness Review (TRR)

i. Deliver a revised and final FATP following the test methods established for each requirement in the RTM (CDRL A006)

ii. Deliver Dry Run data of final system configuration following the FATP

iii. Deliver an updated RTM with pass/fail results for each requirement

b. Perform Factory Acceptance Test (FAT) at Contractor’s facility with Government participation

iv. Deliver a FATP within one week following the FAT with detailed results of each test documented (CDRL A006)

c. Support Facility Integration Testing (FIT) to include System Acceptance Testing

(SAT) and training at both the Air Force and Navy sites.

d. Deliver all technical manuals, User Guides, drawings and schematics prior to

SAT in accordance (IAW) with (CDRLs A007-A008 and A022).

Each CREATE capability shall be developed and tested independently. Successful development and test of each capability will represent the capability’s Initial Operating Capability (IOC). Full

Operating Capability (FOC) will be achieved at the fully integrated system test of all delivered capabilities.

1.3.5 J–PRIMES RAGE ASTC Build to Print RAGE Advanced Signals Test Capability

(ASTC) (CLIN 0003- Option)

1.3.5.1 Description of Work

Joint Preflight Integration of Munitions and Electronic Systems (J-PRIMES) requires a build to print Radar Air-to-Ground Environment (RAGE) system, Advanced Signals Test Capability

(ASTC). The Contractor shall fabricate, deliver, integrate, and test an ASTC to the J-PRIMES anechoic chamber located at Eglin Air Force Base (AFB), Florida. The ASTC shall have identical capability as those developed and delivered to the Air Force Benefield Anechoic Facility and Naval

Air Station Patuxent River. System shall be traceable to requirements defined in the System

Specification for the Radar Air-to-Ground Environment (RAGE) v16, 29 May 2020 and further refined in the Technical Requirements Specification for Installed System Test Facility (ISTF)

Target Generator at J-PRIMES, Eglin Air Force Base (AFB), dated 17 September 2024.

1.3.5.2 Documentation

The Contractor shall fabricate, integrate, and test the sub-system and components to reduce risks and achieve technical performance. The Contractor shall provide documents and artifacts for review and closeout of a fully integrated ASTC sub-system (CDRL A025-A027, A031, A032, A033, A034, and A035).

The contractor shall provide monthly status reports electronically (CDRL A028). The Contractor shall conduct Technical Interchange Meetings (TIMs): as necessary in the performance of this task. TIMs shall be scheduled when there is need for technical interchange between the

Government and the Contractor (CDRL A030).

1.3.5.3 Contractor Integrated Master Schedule (IMS)

The Contractor shall develop, deliver, and update monthly a Contractor Integrated Master

Schedule (CIMS) in contractor format (CDRL A029).

1.3.5.4 Training

The Contractor shall provide on-site training to facility personnel which may include Government support contractors.

2 Applicable Documents

2.1 Government Furnished Information (GFI)

The Contractor shall use the latest Government (or associated/institution) approved version of the documents listed below at task initiation. In the event of a conflict between requirements and reference documents that may affect design or performance, the Contractor shall identify the conflict to IBST and the Contracting Officer’s Representative (COR) for resolution.

Document Number Name of Document

DRAFT – dated 12 November 2025 CREATE System Requirements Specification (SRS)

2.2 Government Furnished Equipment (GFE)

The Government is providing Government Furnished Equipment (GFE) for development and integration of CREATE to support calibration and measurement of CREATE signals. Specific

GFE part numbers shall be identified by the Contractor no later than the Critical Design Review

(CDR) milestone. GFE template will be provided at CDR. The Government will also provide documentation to the Contractor to support creation of the facility Interface Control Document

(ICD).

2.3 Reference Documents:

Document Number Name of Document

N0042124G0003 Mercury Systems, NAWC-AD Basic Ordering Agreement

ANSI/ISO/ASQ Q9001 Quality Management System Requirements Standard

ASTM D 3951-10 Standard Practice for Commercial Packaging

DoDAF 2.02 DoD Architecture Views

DoDI 8500.2 Information Assurance (IA) Implementation

DoDI 8510.01 Risk Management Framework for DoD IT

DoDI 8520.02 Public Key Infrastructure (PKI) and Public Key (PK) Enabling

DoDM 5200.01 DoD Information Security Program: Controlled Unclassified

Information (CUI) Vol 4

DoDM 5205.02M DoD Operations Security (OPSEC) Program Manual

32 CFR Part 117 National Industrial Security Program Operating Manual (NISPOM)

DoDM 5230.24 Distribution Statements on Technical Documents

EIA-649 Configuration Management Standard

ISO 10007:2017 Quality Management Systems -- Guidelines for Configuration

Management

MIL-HDBK-237 Electromagnetic Environmental Effects and Spectrum Certification

Guidance for the Acquisition Process

MIL-HDBK-454 General Guidelines for Electronic Equipment

MIL-HDBK-46855 Department Of Defense Handbook: Human Engineering Program

Process and Procedures

MIL-HDBK-61 Configuration Management Guidance

MIL-HDBK-896 Manufacturing/Quality Program

MIL-PRF-28800 Performance Specification: Test Equipment for Use With Electrical and

Electronic Equipment

MIL-STD-217 Reliability Prediction of Electronic Equipment

MIL-STD-2401 World Geodetic System, WGS-84

MIL-STD-3022 Documentation of Verification, Validation, and Accreditation (VV&A) for Models and Simulations

MIL-STD-31000A DoD Standard Practice: Technical Data Packages

MIL-STD-461 Requirements for the Control of Electromagnetic Interference

Characteristics of Subsystems and Equipment

MIL-STD-464 DoD Interface Standard Electromagnetic Environmental Effects

Requirements for Systems

MIL-STD-499 Systems Engineering

MIL-STD-881C Work Breakdown Structures for Defense Materiel Items

MIL-STD-882E DoD Standard Practice for System Safety

National Aerospace Standard

(NAS) 411

Hazardous Materials Management Program

NAVAIRINST 4355.19E System Engineering Technical Review Process

OPNAV 5239/14 System Authorization Access Request - Navy (SAAR-N)

OPNAVINST 3432.1A Operations Security (OPSEC)

OPNAVINST 5239.3 Navy Implementation of Department of Defense Intelligence

Information System (DoDIIS) Public Key Infrastructure (PKI)

SECNAVINST 5239.1 Department of the Navy Information Assurance Program: Information

Assurance Manual

SECNAVINST 5239.3 Department of the Navy Information Assurance Policy

Application Security and

Development STIG

Defense Information System Agency (DISA) Application Security and

Development Security Tech. Implementation Guide (STIG) https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_ASD_V6R1_STIG.zip

3 Technical Requirements

3.1 Project Management

The Contractor shall provide the non-recurring engineering (NRE) and design activities, documents and artifacts for a final design review and closeout of a fully integrated and allocated

CREATE system that meets the CREATE SRS. The Contractor shall perform requirements definition, functional requirements allocation, design, analyses and documentation activities. The

Contractor shall develop and test subsystems and components to reduce risks and achieve technical performance. The Contractor shall develop, design, document, integrate and test the

CREATE capabilities.

a. The Contractor shall perform administrative and technical reporting and shall maintain a status of all technical activities and efforts, problems/deficiencies, impacts, risks, and recommended solutions.

b. The Contractor shall support recurring (weekly) discussions to provide status on all PM and technical tasking. (CDRL A002)

c. The Contractor shall conduct Technical Interchange Meetings (TIMs): as necessary in the performance of this task. TIMs shall be scheduled when there is need for technical interchange between the Government and the Contractor. The content of the meeting can include the discussion of any information that has impact upon the task activities, including supporting documentation and presentation material. The Contractor shall support travel trips supporting the

TIMs to Pax River, MD, Edwards AFB, CA, or other vendor or contractor sites.

When acceptable, virtual meetings (e.g. Teams) may replace the need for physical in person meetings.

d. Reviews shall follow contractor-tailored NAVAIR systems engineering technical review (SETR) guidelines (available on the internet). Contractor tailoring may be used to reduce cost and complexity of deliverables and reviews based on work required. For example, separate deliverables not explicitly required by this SOW, but defined in the SETR guidelines, are not required for this effort. SETR guidelines are referenced to ensure that something is not overlooked in the development of CREATE.

e. Programmatic presentations shall at a minimum contain relevant cost, schedule and risk information. Cost information shall include a current and projected monthly spend plan (CDRL A019). Schedule information shall include for each

WBS element, an approved baseline start and finish, updated forecast start and finish, and percentage complete. Risks shall be identified as technical, cost and schedule related risks with rankings of low, medium and high based on likelihood and consequence.

f. Monthly reports are due the 5th of each month in Microsoft Word format. The monthly reports shall include at a minimum:

i. Summary of work performed during the prior month

ii. Summary of work to be performed in the coming month

iii. Risk Status and mitigation plan

iv. Issues and Open Action Items (CDRL A018)

v. Schedule update figure (also provided in Microsoft Project format)

vi. Spend Plan update figure (also provided in Microsoft Excel format) showing amount spent in prior months, and spending planned in future months (CDRL A019).

vii. Material commitments report listing the materials on order, awaiting delivery to the Contractor. Report shall include part name, number of parts ordered, per unit cost, total cost, order date and expected delivery date.

Additional information may be provided at the Contractor’s discretion, Contractor format for the report is acceptable (CDRL A024).

3.1.1 Contractor Work Breakdown Structure (CWBS)

The Contractor shall create and maintain a Contractor Work Breakdown Structure (CWBS) in the contractor’s format (CDRL A001). The CWBS shall be incorporated into the Integrated

Master Schedule (IMS)(CDRL A020). Updated status of the CWBS and IMS shall be provided in the monthly status reports (CDRL A003) to the Government.

3.1.2 Contractor Integrated Master Schedule

The Contractor shall develop, deliver, and update monthly a Contractor IMS (CDRL A020). The

Contractor shall provide monthly updates to the Government’s IMS for their tasking via previously agreed upon “schedule touch points” and milestone events. The Contractor shall include in the IMS, at a minimum, discrete tasks/activities, consistent with all authorized work, and relationships necessary for successful task completion. The Contractor shall incorporate subcontractor discrete work (if any) as tasks within the IMS at a level necessary for a realistic critical path. The Contractor shall integrate the IMS as a logically driven network-based schedule that is vertically and horizontally traceable. The Contractor shall include in the IMS the milestones, accomplishments, criteria, discrete tasks/activities, work packages and planning packages, as applicable, from task initiation to task completion. The Contractor shall show traceability of the Contractor’s IMS to the Government IMS, CWBS and approved tasking. The

Contractor shall include custom project fields and data that enable access to the information by product and organizational lines in the IMS. The Contractor shall include all necessary project or task calendars that define working and nonworking time periods or other information that may impact the schedule.

3.1.3 Technical Data Packages (TDP)

The Contractor shall develop a TDP that consists of a critical design review (CDR) documentation slide set and an updated system functional specification (SFS). The SFS shall be in the contractor’s format but shall document the CDR baseline and associated functional information in one document with detailed written descriptions to explain system components and operations at a design level. A draft SFS (CDRL A004) shall be updated and maintained, and a CDR slide deck and draft Acceptance Test Procedures (ATPs) (CDRL A006-A008) shall be delivered two weeks prior to CDR, and an updated version of all materials shall be delivered two weeks after CDR.

3.2 Data and Configuration Management

3.2.1 Integrated Data Environment

The Contractor shall upload all unclassified data listed in their current tasking using the Intelink

SharePoint site or similar document repository as an Integrated Data Environment (IDE). All items posted, including drafts that are not final versions, shall be considered delivered for the purposes of DFARS data rights clauses 252.227.7013, 7014 and 7017 (and subject to the same rights asserted for final deliveries). However, these non-final versions shall not constitute acceptance for purposes of inspection and acceptance requirements. The contractor shall utilize the IDE to post all unclassified CDRLs. Prior to Intelink access, DoD SAFE or similarly secure methods are an acceptable means to share up to CUI data.

The Contractor shall support updating and maintaining data established under the overall contract, within the IDE and deliver classified data and information via appropriate methods for all technical data and computer software used on or produced in the performance of this effort as defined within this tasking.

3.2.2 Requirements and Requirements Verification Traceability

The Contractor shall maintain configuration control of and traceability of requirements and interfaces via the Requirements Traceability Matrix (RTM). The Contractor shall ensure traceability of all system performance specification, interface design definitions and/or interface controls to the System Specification and associated CDR documentation, including the SFS.

3.2.3 Configuration Management Program

The Contractor shall establish, document, implement, and maintain configuration management for the development of their deliverables and artifacts. The Contractor shall, at a minimum, implement Configuration Management (CM) processes in regard to how the Contractor shall select and make recommendations to the Government regarding configuration item identification, establish and perform configuration management planning and management, configuration change management, configuration status accounting, configuration verification/audit and configuration management of digital data. The Contractor shall ensure management, control and execution of CM necessary to control the technical documents used to produce functional and physical characteristics of hardware, firmware, and software and demonstrate during design reviews their ability to achieve a fully integrated CREATE architecture and system performance capability. The Contractor shall also address process flow relative to configuration change documentation that includes Engineering Change Proposals

(ECP), waivers, deviations, specification change notices and Notices of Revision (NOR) as applicable.

3.2.4 Integrated Product Team (IPT)

As the lead system integrator, the Government will form an Integrated Product Team (IPT) consisting of both Government and Contractor support personnel for subsystem development and system integration.

The Government will conduct IPT meetings, as required, to coordinate development and finalization of system interfaces, ensuring timely and complete interface definitions. Interface definition and coordination efforts will be conducted for any combination of interconnected subsystems as necessary to ensure overall system functionality. The Contractor shall support the

CREATE system level IPTs and provide interface definition and design engineering throughout development.

As part of the interface development, the Contractor shall participate with other CREATE subsystem contractors to fully develop the shared interfaces and documentation: Interface

Requirements Specifications (IRSs), and Interface Control Documents (ICDs). IRSs and ICDs will be baselined, controlled, and managed by the Government. Critical interface issues between subsystems or Contractors shall be brought to the immediate attention of the Government.

Contractors shall document updates and implement solutions with Government approval.

3.3 Systems Engineering

The Contractor shall support an iterative and collaborative systems engineering (SE) process and technical reviews that will assess CREATE performance, maturity, risks and the Contractor’s readiness to proceed from system requirements to functional performance baseline, to allocated baseline, and finally to a product baseline that is ready for fabrication and build. The Contractor shall conduct and participate in Technical Interchange Meetings (TIMs) and Working Groups

(WGs) that will be led and chaired by the Government. The Contractor shall deliver products in support of the systems engineering process and reviews, including agendas and action item lists

(CDRL A018).

3.3.1 Software Engineering

The Contractor shall design and develop software in accordance with the Application Security and Development Security Technical Implementation Guide (STIG). The Contractor shall use software management and engineering best processes that are known to reduce cost, schedule, and performance risks. The Contractor shall use software management and engineering that emphasize a modular approach. Software development shall emphasize logical functional requirements definition, high-level and modular design creation and coding, and testing for modules, integration of modules, and system testing. The Contractor shall conduct software security testing, code reviews, and vulnerability scans in accordance with DoD 8510.01 and the applicable STIGs for all software installed on the system. The Contractor shall coordinate with the cybersecurity representative to ensure that all installed software is approved/authorized for use (e.g. approval within the Department of the Navy (DoN) Application and Database

Management System - DADMS).

3.3.2 System Requirements Analysis

The Contractor shall complete the analysis of the CREATE requirements, to include:

a. Definition and elaboration of system use cases

b. Functional analysis to include decomposition, allocation and elaboration of functional and information exchange requirements between system (hardware and software) configuration items

c. Updating and finalizing functional performance, and constraint requirements at the system and subsystem level

d. Elaboration and documentation of the system external and internal interfaces at the system and subsystem levels

All requirements shall be defined to include verification method and software build allocation and be traceable to operator and maintainer use cases, system diagrams and other artifacts.

Functional, logical and physical architectures, system diagrams, use cases and interface descriptions shall be managed and delivered to the Government (CDRL A022). The Contractor shall update as required the system functional specification (SFS) created during CREATE preliminary design phase, which documents the traceability of requirements to system functions.

The Contractor shall develop, deliver and maintain throughout the contract period a system design document (SDD) in contractor format that documents the details of the systems engineering design. (CDRL A005)

3.3.3 Engineering Tests, Demonstrations, and Analysis

The Contractor shall conduct risk reduction and performance verification engineering tests, demonstration and analysis activities to demonstrate the ability of the Contractor’s design to meet the CREATE System Specification. The Contractor shall develop and deliver use cases for operations and maintenance of CREATE (CDRL A023). The Contractor shall work with the

Government to obtain inputs for the development of the operations and maintenance use cases.

The Contractor shall perform use case analysis and report results at TIMs/WGs. The Contractor shall develop and deliver test plans with detailed test procedures. (CDRL A006-A008)

3.3.4 Electromagnetic Environmental Effects

The Contractor shall design and integrate CREATE to meet Electromagnetic Environmental

Effects (E3) performance requirements as defined in the CREATE System Specification. The

Contractor shall document Electromagnetic Interference (EMI) Control Procedures for

CREATE. The Contractor shall document the results of the E3 analysis and results. The

Contractor shall provide information on E3 test planning, analysis and results as requested at

TIMs/WGs.

3.3.5 Modular Open Systems Architecture (MOSA)

The Contractor shall develop CREATE using an architecture that is layered and modular and uses standards-based Commercial off the Shelf (COTS)/ Non-Developmental Item (NDI) hardware, operating systems, and middleware wherever possible that utilize either non-proprietary or non-vendor unique key Application Programming Interfaces (APIs). The approach shall be applied to all subsystems and components. The Contractor shall be prepared to support a

MOSA assessment to describe how the proposed system architecture meets these goals, including the steps taken to use non-proprietary or non-vendor unique COTS or reusable (NDI) components as part of a Common Equipment open system management approach, plans, and assessments. The purpose of MOSA assessment is to assess the systems open architecture for future incorporation of technology refresh and upgrade capabilities into the hardware and software. The Contractor shall specify all planned and/or implemented proprietary interfaces and components at task acceptance and provide an updated status to the Government as part of the

Contractor technical reviews.

3.4 Logistics

3.4.1 Technical Documents and Manuals

The Contractor shall deliver all CREATE technical documentation with each test capability, including operator sheets/cards/guides/manuals, technical manuals, maintenance manuals, repair manuals in native format (CDRLs A010-A011). The Contractor shall deliver an Operations

Manual, Maintenance Manual (CDRL A013), and a Training Manual (CDRL A012). The

Contractor shall ensure that the following information is contained in the manuals:

a. The system description and principles of operation;

b. Functional block diagrams showing both external and internal line replaceable unit (LRU) interfaces;

c. Wiring/signal flow diagrams (level II drawings);

d. Illustrated parts breakdown;

e. LRU removal and installation procedures;

f. Installation test procedures;

g. System turn-on and checkout procedures;

h. Periodic maintenance procedures;

i. List of required spare parts and support equipment (SE) (CDRL A014-A015);

j. System/personnel safety precautions and any special precautions/handling requirements as applicable in accordance with MIL-STD 3001 (Series).

The Contractor shall incorporate a WBS matrix and associated repair tasks with required support equipment, troubleshooting procedures to the LRU level including all required SE, scheduled maintenance procedures including alignment, adjustment, and calibration in the maintenance manual.

3.4.2 DOD Security Classification Guides

The Contractor shall comply with applicable DoD Security Classification Guides (SCGs) and marking practices.

3.4.3 DoD Supply Chain Security

The Contractor shall validate that the Bill of Materials (BoM) does not violate the General

Services Administration (GSA) excluded parties list. The Contractor shall identify any BoM that has Foreign Ownership Control or Influence (FOCI) for Government Approval. The Contractor shall diagram the chain of custody for the BoM at the lowest replaceable unit.

3.4.4 Peculiar Support Equipment (PSE)

The Contractor shall use existing common support equipment to the maximum extent possible. If common support equipment is not used, the operations, maintenance and training of the Peculiar

Support Equipment (PSE) shall be incorporated into the Technical Manuals. The Contractor shall obtain Government approval prior to designing PSE(CDRL A015).

3.4.5 Environment, Safety, and Occupational Health (ESOH)

The Contractor shall assure the design of the system complies with applicable ESOH laws, regulations to include local, state, federal, Environmental Protection Agency (EPA), Executive

Orders (EO), and Federal Acts during the development, production, test, operation, maintenance, sustainment, and disposal of the system. The Contractor shall procure the necessary certificates of compliance to meet ESOH. The Contractor shall notify the COR of any required compliance waivers, prior to the Contractor submittal of waiver paperwork to the cognitive agency. The

Contractor designs shall provide for operations, maintenance, certification, and test to meet with environment safety and occupational health compliance. The Contractor shall address

Hazardous Materials (HAZMAT), ESOH and safety as part of the technical requirements. The

Contractor shall conduct an assessment addressing requirements for HAZMAT and elimination, minimization, substitution, and handling of HAZMAT, functional and system of system hazard analysis (SHA), health, operating and support hazard analysis, radiating hazards, and safety requirements/critical analysis. The Contractor shall prepare and submit a list of any HAZMAT contained in the design and/or used in the operation and maintenance of the system. The

Contractor shall perform a comprehensive evaluation of safety to identify any residual safety risks and procedural hazards that may be present in the system design prior to demonstration and identify critical safety items.

4 DoD Information Technology (IT) Security Assessment and Authorization (A&A)

Certification and Accreditation (C&A) Support in a Risk Management Framework

Environment (RMF)

The Contractor shall support the Assessment and Authorization (A&A) process IAW

Department of Defense Instruction (DoDI) 8510.01 RMF, the Navy Security Control Assessor

(SCA) RMF Guide, and the Integrated Battlespace Simulation and Test (IBST) Department

Cybersecurity Standard Operating Procedures (SOP). The Contractor shall support the determination concerning what is required of CREATE to meet system development and deployment as a National Security System (NSS) IAW DODI 8510.01. The Security

Categorization of the system is tentatively Confidentiality Medium, Integrity Low and

Availability Low. CREATE may be a potential A&A boundary. The Contractor shall research, analyze, advise, assist and make recommendations relevant to the Categorization of this system.

In accordance with DoD/Department of Navy (DoN) policies and requirements the Contractor shall prepare documentation and artifacts, as well as perform cybersecurity testing and analysis in support of obtaining approvals from the appropriate Authorizing Officials (AO).

SAP access will be allowed to specific personnel. Provide guidance and oversight to coordinate the system design, development, integration, test and validation delivery activities for assigned tasks related to Radar Laboratory requirements. Contract is for development of a Radar test capability supporting F-35 chamber testing. Access to SIPRNet authorized; Secure Terminal

Equipment (STE); Secure Video Teleconference (SVTC) use authorized.

5 Testing

5.1 Factory Acceptance Testing (FAT)

The factory acceptance test (FAT) for each test capability shall be conducted at Contractor’s facility. The FAT will test all CREATE contractor requirements in the CREATE specification.

Final FATP is due 60 days prior to TRR (CDRL A006). The FAT shall emulate, as much as possible, SUT signals and connections and the SAT test environment to support smooth transition from FAT to SAT.

5.2 Site Acceptance Testing (SAT)

The site acceptance test (SAT) for each delivered test capability will be conducted using operational test equipment and/or platforms as available at Air Combat Environment Test and

Evaluation Facility (ACETEF), Naval Air Station Patuxent River and at the Benefield Anechoic

Facility (BAF), Edwards Air Force Base (AFB). The Contractor shall provide draft SAT procedures 90 days prior to Test Readiness Review (TRR). (CDRLs A007-A008) The contractor shall deliver all test capability hardware, software, and firmware. (CDRL A009, A016, A017)

Government will coordinate Government-owned test assets, spectrum analyzers and general test equipment. The SAT will have two parts. The first part is a re-execution of portions of the FAT after shipping and assembly, with tests that re-demonstrate key parts of the FAT related to operations. The second part of the SAT will include everything required to verify CREATE system performance IAW the CREATE RTM for each test capability.

5.3 Validation

The Contractor shall provide a functional description of CREATE and its primary subsystems in a system functional specification (SFS) that is updated for each test capability. The documentation shall include diagrams that depict inputs, outputs, and process elements of essential functions. The Validation IPT shall leverage the SFS, FAT and SAT events to record and document Validation parameters in order to accomplish Validation objectives. The

Contractor shall identify all models used or incorporated into CREATE and describe their purpose and functionality with respect to operation. Technical references or standards upon which incorporated models are based shall be identified as appropriate. Validation of models used in each test capability will be conducted by the Contractor at Government facilities.

5.4 Risk Reduction Test Events

The Contractor shall plan and execute CREATE risk reduction (RR) quarterly test events that demonstrate operability of key components of the CREATE system to reduce the overall risk of the full system development. The Contractor shall develop test plans, documentation and provide system components and test apparatus to support RR events. The Contractor shall document the results of the RR events and provide a copy of RR materials to the Government. The risk reduction events shall be witnessed by Government personnel. At times this will be accomplished virtually via Microsoft Teams or Government’s choice in format.

6 Quality Assurance

CREATE development, production, and testing shall be conducted following a contractor quality manual and performance specifications. The Contractor shall plan, organize, and control operations in such a manner that the contractual requirements are systematically achieved, and deficiencies are detected, corrected, and prevented from recurrence. The Contractor shall retain copies of all quality control/inspection records for a minimum of 5 years from completion of the contract and shall not destroy any quality assurance records, within this period, without the prior written permission of the Government’s Quality Assurance Authority.

The procurement of material shall be planned and controlled. The Contractor’s quality system shall ensure that:

a. Specifications, drawings, and purchase orders adequately define the purchased product.

b. Appropriate material specifications are defined.

c. Receiving inspection controls are specified and carried out.

d. Subcontractor performance is measured and monitored.

e. Adequate records of all of the above are maintained.

Controls shall be established to ensure each product is uniquely identified. Serial numbers of scrapped items shall not be re-used.

Contractor shall use engineering best practices to ensure high quality supplies which have been received are properly verified and controlled. The system shall provide for the inspection and test status of any material at any stage during manufacturing and assembly operations to be quickly and properly determined. The system shall provide a positive way of knowing at all times whether items have:

a. Not been inspected.

b. Been inspected and passed as conforming.

c. Been inspected and rejected.

d. Test and inspection points identified in production documents.

The Contractor shall establish and keep current, an effective control system for the identification, segregation, handling, and disposition of non-conforming material to prevent its unauthorized use, shipment, and intermingling with conforming supplies. All repair, rework or refurbishment of non-conforming materials shall be carried out in accordance with Contractor documented procedures. All repaired/reworked items shall be approved by completion of the same tests and inspections applied to new items. The handling and storage of parts, sub- assemblies, and end products shall be undertaken in areas compatible with cleanliness and contamination-free requirements. Wherever practicable, items will be stored in their original packaging until required for use. The Contractor shall ensure that items which are sensitive to electrostatic discharge (ESD), deterioration, or contamination through exposure to air, moisture, or other environmental elements during handling and storage are preserved in a manner which provides maximum protection. All items that contain ESD-sensitive parts shall be adequately identified within the manufacturing process to prevent mishandling.

Any request by the Contractor for a deviation or waiver from the specified requirements shall be submitted to the Government at time of occurrence. The Government reserves the right to reject any deviations submitted.

7 Deliverables/Reporting

7.1 Deliverables and Reporting Requirements

Appendix A of this SOW contains a list of the data items required under this contract and the schedule by which they shall be delivered. In addition to providing the respective data and documents to the contracting officer, copies shall be electronically provided to the technical points of contact (TPOCs).

7.2 Notification of Rights

The Contractor shall identify and receive written Government approval from the Contracting

Officer prior to committing to the use of any privately developed items, components, processes, computer software, and/or technical data which they:

a. intend to deliver with Limited Rights

b. intend to deliver with Government Purpose Rights

c. intend to deliver with Restricted Rights

d. have not yet determined if such rights should apply.

7.3 Disposition of Excess Material and Contractor Acquired Property (CAP)

At completion of this effort, the Contractor shall identify and receive written disposition instructions from the Contracting Officer for all excess material and CAP.

8 Completion Period

The completion period for the Phase 1 effort is seven months after the date of award. This effort will be incrementally funded.

The completion period for the Phase 2a effort is seven (7) months after the date of award. This effort will be incrementally funded.

The completion period for the Phase 2b effort is twenty four (24) months after the date of award.

This effort will be incrementally funded.

The completion period for the J–PRIMES RAGE ASTC delivery effort is date of award plus 18 months.

9 Place of Performance

Work on this Task Order is to be performed at MS Contractor facilities and Government facilities at the NAWC-AD in Patuxent River, MD and the BAF at Edwards AFB, CA. Work for the J-PRIMES RAGE ASTC delivery effort (CLIN 0003) shall be performed at Contractor facilities as well as Government facilities at the J-PRIMES facility, Eglin AFB, FL. Technical interchange may occur at alternate locations, such as GTRI in Smyrna, GA. Performance at the

Government facility will be treated as temporary and covered under allowable travel costs incurred. No contractor shall be considered stationed at any Government site.

10 Invoicing

The Contractor shall send copies of invoices for payment approval prior to routing to the Wide

Area Work Flow (WAWF) / Defense Finance Accounting System (DFAS). Payment of invoices will be contingent on TPOC approval.

11 Security

The CREATE project will be operating up to the Collateral Secret level. Only personnel working with classified data must possess and maintain a SECRET clearance. This task will require access to SECRET information and meetings. The delivered project proposal shall be at the

Controlled Unclassified Information (CUI) level. Performance shall be in accordance with a required DD FORM 254. Relevant Security Classification Guide(s) (SCGs) are identified in

Block 11C of the associated DD FORM 254.

12 Data Handling

In the course of performing work under this order, the Contractor may have access to naval force structure, system performance, pre-decisional, program/business sensitive, and proprietary (FAR

52.215-1) material, herein referred to as “data”. This data shall not be disclosed by the

Contractor to any entity, Government or otherwise, outside of IBST unless specifically authorized in writing by the Contracting Officer. The Contractor shall not use the data for purposes other than performance of the requirements set forth in this order; nor shall the

Contractor release, reproduce, distribute, or publish any data or analysis that is provided by the

Government or produced by the Contractor in the performance of this contract; nor shall the

Contractor authorize others to do so without written authorization…