Attachment_3_-_SOO.pdf

Attachment 3

FA8650-19-S-1031

RF Analysis and Validation Engineering Software (RAVEnS)

STATEMENT OF OBJECTIVES

November 7, 2018

1 Technical Background:

This announcement focuses on research and development in the area of computational electromagnetics. This RF Analysis and Validation Engineering Software (RAVEnS) effort will serve to fund research, development, and quality assurance within the CREATE-RF suite of tools. Computational tools that meet government requirements for modeling RF components integrated into next generation weapons systems do not exist. CREATE-RF’s mission is to develop the algorithms and tools to bridge this gap and provide decision makers and designers with high quality RF modeling data that meets requirements in terms of accuracy, schedule, security, and budget.

The CREATE-RF program is one of five programs under the High Performance Computing Modernization Program Office (HPCMPO) Computational Research and Engineering Acquisition Tools and Environments (CREATE™) program. HPCMPO CREATE™ develops a suite of physics-based HPC Tools for the design and analysis of DoD platforms supporting many stages of DoD current, future, and next generation acquisition programs.

Computer Software tools currently developed under the CREATE-RF program include:

• SENTRi Generation 2: a hybrid finite-element/boundary-integral computational electromagnetics physics engine. The current version of SENTRi consists of over 300k lines of code. The core of the engine is implemented using C++, an interface layer is implemented using python, and numerical heavy lifting is implemented by interfacing with LAPACK.

• SENTRi Generation 1: a hybrid finite-element/boundary-integral computational electromagnetics physics engine. It is a combined engine and user interface written in C++ using Qt as a library for the graphical interface. This version of SENTRi is currently in a maintenance mode involving only minimal changes.

• Aurora: a high-frequency asymptotic solver implemented using a Shooting and Bounding Rays (SBR) method.

• FLO_K: a finite-element periodic solver. FLO_K allows the user to solve a single unit cell in order to obtain a solution in an infinitely periodic domain.

• SENTRi User Interface: a web and standalone application built using javascript, closure, python, protobuf, and CWF (Chrome Web Framework). The user interface currently consists of over 245k lines of code. The intent of the user interface is to provide a convenient way for the user to set up scenarios to be executed by the numerical engines provided by the CREATE-RF program.

Simulation results of a Rotman lens as computed by CREATE-RF tools.

The CREATE-RF project follows an annual release cycle consisting of the following events: a planning stage, followed by a Preliminary Design Review (PDR) early in the development cycle, a Final Design Review (FDR) midway through the development cycle, an alpha testing period (internal users) for a few months, a beta testing period (external users) for a few months, software release, a retrospective review of the previous release, and bug fix releases. New features and capabilities are road map targeted individually for each release cycle. CREATE developers also meet annually at the CREATE Software Developers Review, and the CREATE- RF team leads meet regularly for coordination and status updates.

2 Scope:

Advance all aspects of computational electromagnetics tool development including basic research, software development, infrastructure, testing, verification, validation, and quality assurance with an emphasis on frequency domain analysis.

Requirements are defined and refined on a daily basis. The selectee and subcontractors will be expected to participate in the refinement process.

Topics relevant to this program.

Computational Electromagnetics Research

• Conduct independent research into numerical techniques, computational electromagnetic formulations, and algorithms

• Develop tests to verify the accuracy and performance of newly developed methods

• Develop hybrid CEM techniques

• Develop scalable parallel algorithms targeted toward execution on distributed high performance computing systems

• Collaborate with universities on far-term and incubational research topics

Software Research and Development

• Extend and improve existing code bases

• Develop new methods, techniques, approximations, and algorithms

• Implement ease of use interfaces

• Conduct internal validation and verification

• Develop a graphical user Interface, provide a web interface for connecting to and running simulations on remote systems

• Write internal documentation of the software and its user-facing interfaces

Infrastructure

• Host code development network

• Host task tracking system

• Maintain computer systems and clusters

• Develop and maintain code testing and evaluation infrastructure

Quality Assurance

• Write user and developer facing documentation

• Conduct beta testing

• Provide user assistance

• Apply software to relevant DoD analyses

• Conduct and develop material for new user trainings

Program Management

• Provide oversight and organization of subcontractors (if any)

• Collect, provide, and present software development metrics analyses on a regular basis

• Solicit and collaborate with end users, capture successes, and document results

• Software shipping and distribution (the CREATE-RF tools are shipped to end users on physical media)

• Organize and lead project and program reviews

3 Objectives:

1. Research, develop, verify, validate, test, and apply computational electromagnetic design tools – in concert with the government-led team to produce the next generation of HPCMP CREATE™ tools.

2. Research and develop advanced computational methods for the design and development of weapon systems – methods that exceed currently used techniques in accuracy, fidelity, time to solution, and usability.

3. Develop and deploy multi-physics engineering software applications on increasingly capable high performance computing systems. These applications will accurately predict the performance of weapon systems and enable the trade space optimization of new and retrofit designs.

4. Incorporate requirements and feedback from weapon systems analysts/designers (end users of the CREATE-RF tools) to develop and deploy next generation multi-physics engineering software applications. Goals are: 1) to enable the trade space optimization of new systems to avoid costly (time and money) retrofits when design flaws are discovered later in production; 2) create tools to upgrade fleeted systems to new performance requirements, 3) reduce build-and-test prototype cycles in new weapon acquisition programs.

5. Improve the productivity of the weapon system designers by incorporating new methodologies for CAD and mesh generation, analysis scenario descriptions, effective use of high-performance computer resources, management of models, and analysis results throughout design cycles, and use of computer graphical techniques to effectively display engineering analysis results.

6. Contribute to research performed by Air Force Institute of Technology students completing research related to their studies.

4 Tasks:

1. Develop new CEM engine features, including asymptotic methods, finite element, integral equation, accelerated, and hybrid techniques. Apply code optimization and parallel programming methods, fix software bugs, and other steps as needed in the software development process. Extend current features, and post processing capabilities.

2. Research and develop full wave CEM engine solvers for high fidelity analysis, e.g. finite element, integral equation, and hybrid techniques.

3. Research and develop asymptotic EM engine solvers for rapid, approximate analysis.

4. Research and develop acceleration algorithms to extend the applicability of CEM tools to higher frequencies and larger weapons systems.

5. Apply code optimization and parallel programming methods, fix software bugs, and other steps as needed in the software development process.

6. Extend current features and post processing capabilities.

7. Verify and validate analysis codes. Compare against commercial and GOTS tools and measurements for accuracy.

8. Develop internal and user documentation, including manuals, release notes, and product technical description.

9. Develop the user interface for the computational engine that supports multiple solvers and CAD workflows.

10. Conduct quality assurance efforts including training, user assistance, testing, application of simulation tools, installation and maintenance of analysis tools on HPCMP DSRC systems, and other tasks as needed for research and development.

11. Apply the CREATE-RF analysis tools to problems of interest to the Air Force.

5 Performance Period:

The overall period of performance for the contract will be 63 months; 60 months for the technical period of performance with an additional 3 months to complete the final report.

6 Reporting Requirements:

All data items: A001 through A011 for effort will be required. The contractor may propose additional deliverables as appropriate.

Contract Deliverable Requirements List (CDRLs):

CDRL

Data Item Description Delivery Schedule

A001 DI-FNCL-80331A/T, Funds and Man-Hour Expenditure Report Monthly A002 DI-MGMT-81468/T, Contract Funds Status Report (CFSR) Quarterly A003 DI-MGMT-80368A/T, Status Report Quarterly A004 DI-IPSC-81488/T, Computer Software Product As Generated A005 DI-IPSC-81443A/T, Software User Manual As Generated A006 DI-ADMN-81373/T, Presentation Material As Required A007 DI-IPSC-81438A/T, Software Test Plan As Required A008 DI-NDTI-80566A/T Hardware Test Plan As Required A009 DI-MISC-80711A/T Hardware User Manual As Generated A010 DI-MGMT-81453A Data Accession List (DAL) End of Tech Effort A011 DI-MISC-80711A/T, Scientific and Technical Reports, Final Report End of Tech Effort

7 Hardware and Software Deliverables:

Hardware purchased or developed under this effort will be delivered to the Government at the end of the contract. Examples of items that may be purchased on this contract include:

Computational Hardware, Networking Equipment, and Software (compilers, CEM software, and so forth).

Computer Software developed under this contract will be delivered/integrated on a continuous basis.

8 Base Support:

Laboratory space/equipment (on a non-interference basis) and computer/network access in AFRL/RY for this contract shall be made available for the purpose of conducting this effort, if proposed. There is currently office space for 6 individuals, in support of CREATE RF Development task, located at AFRL/RYMH, Wright-Patterson AFB. These laboratories will be operated and maintained by the Government.

Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S.

Government Information Technology networks in connection with the work on this contract must be U.S. citizens. Possession of a permanent resident card (“Green Card”) does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S.

Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC).

9 Government Furnished Property (GFP):

The CREATE-RF program has a distributed private network which hosts source code and documentation. The network is commonly referred to as the JDC. The JDC network currently connects to several development locations, and includes connection to a 16 node MPI development cluster called Maxwell. Additional equipment includes a 4 node many core cluster system.

It is anticipated that the following equipment will be provided as GFP in support of this effort.

1) The 16 node computing cluster known as Maxwell.

2) The 4 node computing cluster.

3) Commercial compilers

4) Networking and encryption equipment in support of the JDC.

10 Export Control:

The contractor will be required to generate or require access to export-controlled items.

The software directly developed under the CREATE-RF program is subject to export control.

University-led research will have not have export restrictions, but US citizenship is required for all participants in efforts funded by the CREATE-RF program.

11 Security:

General Operations Security (OPSEC) procedures, policies and awareness are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of the contract. The Critical Information List (CIL) and the RY OPSEC Plan will be provided upon request by AFRL/ RYOY Information Protection Office. While working on the government installation, OPSEC guidance and OPSEC training will be provided by AFRL/RYOY Information Protection Office. This training will ensure contractors are familiar with RY’s CIL and RY’s OPSEC Plan as it pertains to their contract. The contractor shall apply OPSEC in their management of their current program IAW AFI 10-701 Operations Security and WPAFB Supplement to AFI-10-701.

The Contractor shall participate with the Government in the development of a Program Protection Plan (PPP), to include the identification of Critical Program Information (CPI), and shall also participate with the Government in determining countermeasures needed to safeguard the CPI throughout the acquisition process. The Contractor shall plan for and execute program protection in accordance with the PPP and program guidance.

12 Safety:

The contractor must comply with all federal, state, and local safety and environmental regulations.

Requires an approved Safety Plan IAW AFI 91-202 AFRL Supplement 1 before any experiment may be conducted. The contractor must comply with all Air Force safety and environmental regulations.

The contractor must comply with system safety requirements contained in MIL-STD 882D, Section 4 “General Requirements” for any deliverable systems or hardware. The contractor must identify safety-critical components of those systems or hardware, and software interfaces with those components. Must test and verify the safety-critical hardware and software for safety acceptance.

13 Associated Contractor Agreement (ACA):

(a) The Contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement.

The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the (insert name of the program or project), which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. Associate contractors are listed in (h) below.

(b) ACAs shall include the following general information:

(1) Identify the associate contractors and their relationships.

(2) Identify the program involved and the relevant Government contracts of the associate contractors.

(3) Describe the associate contractor interfaces by general subject matter.

(4) Specify the categories of information to be exchanged or support to be provided.

(5) Include the expiration date (or event) of the ACA.

(6) Identify potential conflicts between relevant Government contracts and the ACA;

include agreements on protection of proprietary data and restrictions on employees.

(c) A copy of such agreement shall be provided to the Contracting Officer for review before execution of the document by the cooperating contractors.

(d) The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

(e) Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

(f) All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended as required by the Government during the performance of this contract.

(g) The following contractors are associate contractors with whom agreements are required:

Contractor Address Program / Contract

To Be Determined at award