REWP - HANGS (Revision 2).pdf

Hardware-in-the-loop of Advanced Navigation & Guidance Sensors (HANGS)

1 | P a g e

Request for Enhanced White Papers for

Hardware-in-the-loop of Advanced Navigation & Guidance Sensors

(HANGS)

Issued by:

The 96th Test Wing (TW) / 782d Test Squadron (TS) Guided Weapons Evaluation Facility (GWEF)

Point of Contact: Heather Stiles (Agreement Officer), heather.stiles@us.af.mil & Logan Deming (Agreement Specialist), logan.deming@us.af.mil

Enhanced White Papers are due by 31 January 2026 mailto:heather.stiles@us.af.mil mailto:logan.deming@us.af.mil

2 | P a g e

Contents

CAUTION NOTICE

Section A: Acronyms/Abbreviations Section B: Definitions

1.0 GENERAL

1.1 Introduction / Mission

1.2 Project Description / Scope

1.3 Technology Areas

1.4 Anticipated Awards / Performance Schedule

1.5 Other Transaction Authority / Eligibility Requirements

1.6 Security Requirements

1.7 Cost Sharing Definition and Requirements

1.8 Consortium

1.9 Procedures

1.10 Technical Data Rights, Software, & Intellectual Property

1.11 Non-Government Personnel

1.12 Agency Contact Information

1.13 Applicable Laws & Instruction

2.0 ENHANCED WHITE PAPER INSTRUCTION

2.1 Format of Enhanced White Papers

2.2 Content of Enhanced White Papers

2.3 Initial Screening

2.4 Submission of Enhanced White Papers

3.0 WHITE PAPER EVALUATION

3.1 Evaluation Factors

3.2 Evaluation Ratings

4.0 OTHER INFORMATION

4.1 System for Award Management (SAM)

4.2 Wide Area Work Flow (WAWF)

4.3 Follow-On Production Work

3 | P a g e

CAUTION NOTICE

• Request for white papers, solution briefs or proposals does not guarantee that the Government will make an award.

• Offerors bear all costs to prepare and submit responses to this solicitation.

• By submitting a response, offerors agree that the Government:

o Shall reproduce the response, or any portions thereof, to the extent necessary to evaluate the offer;

o Shall use information contained in the brief only for evaluation purposes. DoD shall not disclose, directly or indirectly, such information to any person including potential evaluators unless that person has been authorized to receive such information.

• Any Prototype Other Transaction Agreement (“OTA”) awarded in response to this solicitation may result in the award of a follow-on production contract or transaction without the use of further competitive procedures. The follow-on production contract or transaction will be available for use by one or more organizations in the Department of Defense and, as a result, the magnitude of the follow-on production contract or agreement could be significantly larger than that of the Prototype OTA. As such, any Prototype Other Transaction Agreement will include the following statement relative to the potential for follow-on production:

o In accordance with 10 U.S.C. § 4022, and upon a determination that the prototype project for this transaction has been successfully completed, this competitively awarded prototype OTA may result in the award of a follow-on production contract or transaction without the use of competitive procedures.

4 | P a g e

Section A: Acronyms/Abbreviations

Terminology Acronym/Abbreviation Air Force AF Air Force Instruction DAFI Air Force Test Center AFTC Digital Visual Interface DVI Department of Defense DoD Department of Defense Instruction DoDI Electro-Optical EO Enhanced White Papers EWP Generally Accepted Accounting Principles GAAP Global Navigation Satellite System GNSS Guided Weapons Evaluation Facility GWEF Hardware-In-The-Loop HITL Hardware-in-the-loop of Advanced Navigation & Guidance Sensors HANGS High-Definition Multimedia Interface HDMI In Accordance With IAW Infrared IR Long-Wave Infrared LWIR Mid-Wave Infrared MWIR Modeling & Simulation M&S Non-Traditional Defense Contractor NDC Other Direct Costs ODC Other Transaction OT Other Transaction Agreement OTA Period of Performance PoP Peripheral Component Interconnect Express PCIe Position, Navigation, and Timing PNT Point of Contact POC Procurement Integrity Act PIA Radio Frequency RF Rough Order of Magnitude ROM Short-Wave Infrared SWIR Special Publication SP System for Award Management SAM Tax Identification Number TIN Technology Areas TA Test Squadron TS Testing & Evaluation T&E Test Wing TW Ultraviolet UV Verification & Validation V&V Visible Vis Wide Area Workflow WAWF

5 | P a g e

Section B: Definitions

A “Non-Traditional Defense Contractor (NDC)” is defined in 10 U.S.C. § 3014 as “an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the Department of Defense (DoD) for the procurement or transaction, any contract or subcontract for the Department of Defense that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section.” A NDC or nonprofit research institution can be a prime contractor, team member, subcontractor, lower tier vendor, or "intra-company" business unit, provided the business unit makes a significant contribution to the initiative (i.e., is a key participant). Examples of what might be considered a significant contribution include supplying new key technology or products, accomplishing a significant amount of the effort, or in some other way causing a material reduction in the cost or schedule or increase in the performance. Please note that there is both a quantitative and qualitative aspect to nontraditional defense contractor or nonprofit research institution participation, and the lack of one aspect may require a more significant contribution in the other.

“Unlimited rights” for technical data means the rights to use, modify, reproduce, perform, display, release, or disclose technical data in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so.

“Unlimited rights” for computer software and/or computer software documentation means the rights to use, modify, reproduce, release, perform, display, or disclose computer software or computer software documentation in whole or in part, in any manner and for any purpose whatsoever, and to have or authorize others to do so.

“Prototype Project” includes a project that addresses –

(A) A proof of concept, model, or process, including a business process;

(B) Reverse engineering to address obsolescence;

(C) A pilot or novel application of commercial technologies for defense purposes;

(D) Agile development activity;

(E) The creation, design, development, or demonstration of operational utility; or Any combination of items (A) through (E)

“Teaming” – Teaming is a collaboration between two or more contractors to provide a complete solution. Each team member is responsible for their part of the solution, and the combined offerings of the team members provide a comprehensive solution to the government's need.

6 | P a g e

1.0 GENERAL

1.1 Introduction / Mission

The mission of the Air Force Test Center (AFTC), 96 Test Wing (TW), and 782d Test Squadron (TS) – Guided Weapons Evaluation (GWEF), is to test and evaluate weapon systems performance through development, fielding, and sustainment. Exercising open and closed Hardware-in-the-loop (HITL) simulations of tactical hardware provide a high-fidelity performance assessment for weapon system development, risk mitigation prior to live flight tests, testing scenarios that are not feasible for live flight, and evaluation of candidate components and technologies for system improvements.

The 782d TS GWEF is seeking Enhanced White Papers (EWPs) for the design, development, integration, and deployment of prototype technologies for Hardware-in-the-loop of Advanced Navigation & Guidance Sensors (HANGS). Offeror EWP’s must express interest and demonstrate a thorough understanding of project scope and potential solutions.

HANGS will improve Air Force (AF) capabilities to efficiently develop, test, and evaluate the performance of current and future weapon systems in realistic, credible, and non-destructive synthetic flight and mission environments. Open and closed loop HITL simulations that exercise the tactical hardware and software components in a relevant synthetic environment provide high fidelity performance assessment for system development, risk mitigation prior to live flight tests, testing scenarios that are not feasible for live flight, and evaluation of candidate components and technologies for system improvements.

1.2 Project Description / Scope

The Government seeks prototype technologies that improve Government test and laboratory facility capabilities, to perform HITL in the Technology Areas (TAs) listed in Section 1.3, Technology Areas. This effort will evaluate the technical feasibility and military utility of existing and emerging weapon system technologies such as seeker/sensor; position, navigation, and timing (PNT); Guidance, navigation, and control (GNC); Radio Frequency (RF) data link communications; mission control computer; and integrated flight software (IFS).

Prototype deliverables must include the development and delivery of a fully functional HANGS prototype technology, applicable to weapon system missions (tactical, missile offense, missile defense, and strategic nature), and the full gamut of capabilities required to test weapon systems in real-time, closed loop HITL simulation, and mitigate the overall technical risk.

Although a full solution is desirable, the Government is willing to accept a partial solution that includes a minimum of two (2) technology areas. A full solution is defined as a solution which addresses all four (4) technology areas.

Deliverables will include the following:

DELIVERABLE QUANTITY

Technology prototype identified in the scope 1 Per Technology Area Modeling & Simulation (M&S) and Testing & Evaluation (T&E) plan/report 1 Per Prototype Interface control document 1 Per Prototype Acceptance and Verification & Validation (V&V) plan/report 1 Per Prototype Software. Hardware, and firmware documentation, specifications, source code, executable codes, libraries, scripts, tables, and supporting operation, maintenance, and user manuals/reports 1 Per Prototype All meeting/briefing materials, meeting minutes, and action items As needed

7 | P a g e

1.3 Technology Areas

Technology Area #1: Dynamic real-time multispectral scene generation and projection/injection systems. Scene generation is the process of rendering band specific imagery intended for projection or injection into one or more sensors. Projection/injection is the process of transmitting the rendered imagery to the sensor, either “through-the- lens” (free-space projection) or electronically/digitally (injection).

• Simultaneous synchronized/correlated imagery for multiple spectra including Electrical-Optical (EO)/Infrared (IR) Ultraviolet (UV), Visible (Vis), Short-Wave Infrared (SWIR), Mid-Wave Infrared (MWIR), Long-Wave Infrared (LWIR) and RF (Ku, Ka, & W bands).

• High resolution complex and dynamic multi-object, clutter, and background scenes including empirical or physics-based sky, terrestrial, maritime, and celestial targets and backgrounds;

propagation/environmental attenuation; countermeasure effects.

• Target and background modeling systems that enable rapid model development, possibly utilizing readily available data (commercial, satellite, data collects, etc.).

• Compatibility with industry standard digital video interfaces such as Digital Visual Interface (DVI), High-Definition Multimedia Interface (HDMI), and DisplayPort, and existing high-bandwidth, high-speed transfer technologies such as Peripheral Component Interconnect Express (PCIe) over fiber.

• EO/IR characteristics - High apparent temperatures (≥ 2000 degrees Celsius), large frame sizes(≥2048x2048), high frame rate (≥400Hz), wide field-of-view (≥30 degrees), high radiance resolution(≥16-bit), low jitter (< 1 microradian) and low latency (< 1 frame or microseconds).

• RF characteristics – High image content (>2400 scatterers per-target X 8 targets plus backgrounds), high frame rates (>1200Hz), wide field-of-view (≥30 degrees), high dynamic range, low jitter (< 1 microradian) and low latency (< 1 microseconds).

Technology Area #2: Midcourse and navigation environment emulation/simulation. Simulation/emulation and real-time projection/injection capabilities for PNT such as Global Navigation Satellite System (GNSS) and alternative PNT solutions. Solutions shall include propagation, environmental, and countermeasure effects.

Technology Area #3: Datalink and radio communication emulation/simulation. Real-time projection/injection for multi- protocol datalink and radio communication to/from/between multiple guided weapon systems and/or digital simulations of weapon systems (e.g. swarm) including propagation, environmental, and countermeasure effects; emulation/simulation of large networks, network loading, and transport; emulation/simulation of commercial low earth orbit satellite communication networks.

Technology Area #4: High frame rate real-time simulation execution. Compute systems that can execute correlated real-time flight simulations for multiple systems at very high frame rates, for example, graphics processor-based computation.

1.4 Anticipated Awards / Performance Schedule

Anticipated individual awards: Multiple awards are anticipated; however, the Government will seek to minimize the quantity of individual awards and encourage industry teaming (see Section B: Definitions).

Types of instruments that may be awarded: Other Transactions for Prototype, under the authority of 10 U.S.C. § 4022.

Duration of Agreement: The duration of the agreement is to be provided by each Offeror with the white paper submitted. The Government’s anticipated duration of this agreement is 36 months as follows:

• Year 1: Design and development of the prototypes, includes the delivery of critical modular equipment to be integrated into the end capability in year 2 & 3.

8 | P a g e

• Year 2: Procurement, fabrication, integration and testing of sub-system prototypes.

• Year 3: Integration and complete prototype system test.

The Government is amenable to Offerors submitting an alternate schedule/duration of agreement with its EWP.

1.5 Other Transaction Authority / Eligibility Requirements

In accordance with of 10 U.S.C. § 4022(d)(1), each Prototype Project (see Section B: Definitions) awarded under this authority must meet at least one of the following conditions:

(A) There is at least one nontraditional defense contractor or nonprofit research institution participating to a significant extent in the prototype project.

(B) All significant participants in the transaction other than the Federal Government are small businesses (including small businesses participating in a program described under section 9 of the Small Business Act (15 U.S.C. 638)) or nontraditional defense contractors.

(C) At least one third of the total cost of the prototype project is to be paid out of funds provided by sources other than the Federal Government.

(D) The senior procurement executive for the agency determines in writing that exceptional circumstances justify the use of a transaction that provides for innovative business arrangements or structures that would not be feasible or appropriate under a contract or would provide an opportunity to expand the defense supply base in a manner that would not be practical or feasible under a contract.

1.6 Security Requirements

Certain aspects of work performed under this prototype project will be done at the SECRET level and access to a DoD Installation may be required.

1.7 Cost Sharing Definition and Requirements

Cost sharing is defined as the resources expended by a party other than the federal Government in performance of the proposed requirement, and subject to the direction of the Government. If the Government determines that there is not at least one NDC participating to a significant extent, then at least one third of the total cost of the prototype project is to be paid out of funds provided by parties to the transaction other than the Federal Government.

1.8 Consortium

The Government may make an award to a consortium or as a single Offeror agreement. A Consortium can be structured in a wide variety of ways, and members may be technical performers, financial contributors, potential end users of products and technologies developed by the consortia, or other unspecified interested parties in the project or projects being funded. Offerors that are consortium members or anticipate becoming a consortium member will identify as such as instructed in Section 2.2, Content of Enhanced White Papers.

1.9 Procedures

EWPs must be submitted in accordance with (IAW) Section 2.0, Enhanced White Paper Instruction.

The Government will evaluate each EWP based on the criteria in Section 3.0, White Paper Evaluation. The Government may elect to request additional information or a solution presentation from any Offeror that submitted an EWP, or from only the Offeror(s) that submitted the most advantageous EWP solution.

9 | P a g e

Selected Offerors may be asked to submit full technical and cost proposals, which allows the government to evaluate and negotiate the final agreement.

1.10 Technical Data Rights, Software, & Intellectual Property The Government shall receive “Unlimited Rights” (see Section B: Definitions) to all computer software and/or technical data generated, developed, or delivered under this Agreement, unless the Offeror's EWP identifies computer software and/or technical data to be furnished to the Government with restrictions (less than Unlimited Rights). The extent and effect of such assertions may be evaluated by the Government and affect the EWP's rating.

1.11 Non-Government Personnel

Offerors are advised that employees of the firms identified below may serve as non-Government advisors in the review and evaluation of EWPs. Such firms are expressly prohibited from competing on the subject acquisition.

The non-Government advisors will be required to submit to the Government a Non-Disclosure Agreement reflecting the effort(s) that they will be supporting. The Offeror’s submission of an EWP under this REWP indicates concurrence with the use of non-Government advisors.

• Reliance Test & Technology, 4050 S Ferdon Blvd., Crestview, FL 32536

• Canvas, Inc., 701 East John Sims Parkway Suite 303 Niceville FL 32578

In accomplishing their duties related to the EWP evaluation, the aforementioned firms may require access to proprietary information contained in the Offerors' EWP. Offerors may execute an agreement with these firms that states that they will: (1) protect the Offerors’ information from unauthorized use or disclosure for as long as it remains proprietary; and (2) refrain from using the information for any purpose other than that for which it was furnished. If such an agreement is desired, Offerors are instructed to contact the reviewing firm before submitting their EWP to initiate and execute the agreement. If applicable, Offerors must include a copy of the executed agreement along with their EWP submission.

1.12 Agency Contact information

All questions regarding this REWP shall be submitted to the Point of Contact(s) listed on page 1 - Heather Stiles (Agreement Officer), heather.stiles@us.af.mil & Logan Deming (Agreement Specialist), logan.deming@us.af.mil.

1.13 Applicable Laws & Instruction

• 10 U.S. Code § 4022 - Authority of the Department of Defense to carry out certain prototype projects

• DoD Instruction (DoDI) 5000.02, Operation of the Adaptive Acquisition Framework

• DoDI 5230.24, Distribution Statements on Technical Documents

• DoDI 5200.48, Controlled Unclassified Information.

• Air Force Instruction (DAFI) is DAFI 63-101, Integrated Life Cycle Management

• Air Force Instruction (DAFI) is DAFI 63-138, Acquisition of Services

• National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171 (Rev 3), Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations

• Section 889 of the FY19 National Defense Authorization Act (NDAA)

• Section 1634 of Division A of the National Defense Authorization Act for Fiscal Year 2018 (Pub. L.

115-91)

• Procurement Integrity Act in Chapter 21 of Title 41, U.S.C. (PIA)

10 | P a g e

2.0 ENHANCED WHITE PAPER INSTRUCTION

2.1 Format of Enhanced White Papers

Offerors shall submit the EWP IAW the following:

• EWP must not exceed 25 pages.

• Include one (1) electronic copy of the following:

o Cover Sheet o Enhanced White Paper o Rough Order of Magnitude (ROM) Cost Estimate.

• Do not lock or encrypt any files uploaded as part of your white paper submission. Any locked or encrypted files will not be evaluated.

• Use of legible diagram(s) or figure(s) to depict the essence of the proposed solution is encouraged.

• All EWPs shall be UNCLASSIFIED.

• EWPs containing data that is not to be disclosed to the public for any purpose or used by the

Government except for evaluation purposes shall include a statement similar to the following on the cover sheet:

o “This WHITE PAPER includes data that shall not be disclosed outside the Government, except to non-Government personnel for evaluation purposes, and shall not be duplicated, used, or disclosed -- in whole or in part -- for any purpose other than to evaluate this submission. If, however, an agreement is awarded to this Offeror as a result of -- or in connection with – the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent agreed upon by both parties in the resulting agreement. This restriction does not limit the Government's right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets]” o Each restricted data sheet should be marked as follows:

“Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal.”

Questions regarding the objectives or preparation of the EWP shall be submitted to the Point of Contact(s) listed on page 1 - Heather Stiles (Agreement Officer), heather.stiles@us.af.mil & Logan Deming (Agreement Specialist), logan.deming@us.af.mil.

2.2 Content of Enhanced White Papers

EWP submissions must include the following:

• Cover Sheet - Offerors shall provide the following information on the cover sheet:

o Organization Information: name, mailing address, technical POC, phone number, e-mail address, CAGE code/Unique Entity ID (if applicable), and Tax Identification Number (TIN).

o Business point of contact name, phone number, and e-mail address. Include all individuals authorized to negotiate on the entity’s behalf (agent).

o Self-Certification of Offeror: (select all that apply)

Small business Large business Academic institution Non-traditional defense contractor (see Section B: Definitions) Other – i.e. Consortium, joint venture, or team (through its members or authorized agent), or a prime performer with subcontract relationships, among others.

• Description of the proposed technical approach, capabilities, and resulting contributions: for a minimum of two (2) Technology Areas. The EWP shall include the following information, as applicable:

o Background and benefits of proposed solution.

11 | P a g e o Experience with similar technologies, and a description of the technology achieved/developed that is similar (within scope) to the requested HANGS technologies.

o Technical Approach, including clearly defined prototype solutions.

A prototype solution that has a clear path for design, but an uncertain outcome, may be accepted as a solution, but the certainty (or limitations/assumptions) should be identified (or quantified).

Describe how the proposed technical approach is innovative, feasible, achievable, and complete. An 80% solution is adequate with a description of the limitations/assumptions identified.

The technical approach should address the approach to developing, integrating, prototyping, testing, and delivering the prototype deliverables for the Technology Areas listed in Section 1.3, Technology Areas.

o Schedule and Deliverables.

Provide a notional schedule with overview of tasks and methods planned to accomplish the technical approach and the prototype technologies to be delivered as part of the base agreement.

Present scalability of prototype production methods and resources to meet the Government’s schedule.

o Proposed capabilities of the Offeror’s prototype technologies.

o Process and procedures to inspect and accept prototype technologies. Approach to prototype technology integration and overall testing of the prototype technology.

o Identify any Government Furnished Equipment and/or Government Furnished Information that may be required.

• As discussed in Section 1.10, Technical Data Rights, Software, & Intellectual Property, identify and assert any restrictions on the Government's use, release, or disclosure of technical data and/or computer software pertaining to this EWP submission.

• Identify key technical and management resources proposed to execute the project.

• ROM Cost Estimate: A ROM cost estimate is a broadly scoped cost estimate used to provide a general cost range for a project.

o Describe the estimated costs for the proposed technical approach. Provide a ROM cost, and any assumptions pertaining to cost. The Offeror should describe general methods (e.g. expert judgment, analogous estimating, and parametric estimating) used to define estimated costs for the technical approach. Identify long lead items in terms of ROM costs. Provide assumptions of any Government Furnished Information and/or Equipment. If applicable, include any suggested cost share distribution or creative costing approaches to maximize successful completion within the constrained schedule.

12 | P a g e

Sample ROM Cost Table below:

• Identify team structure and/or teaming/cost sharing agreements. Performer team relationships are the Offeror’s responsibility. Teaming/collaboration is not required.

• If a consortium is involved, provide the Articles of Incorporation/Agreement/Memorandum of Understanding (MOU) documenting the legal basis for the consortium and defining its operations, to include the responsibilities and obligations of its members.

• Describe the capabilities of the Offeror accounting system. For example, does the accounting system comply with Generally Accepted Accounting Principles (GAAP), with effective controls over all project funds, including Federal funds and any required resource share? Does the system have complete, accurate, and current records that document the sources of funds and the purposes for which they are disbursed?

2.3 Initial Screening

The Government will perform an initial screening to ensure compliance with the EWP format. The following items are primary reasons for non-compliance and elimination during this initial screening:

• Offeror does not meet eligibility requirements for Other Transaction Authority in accordance with 10 U.S.C. § 4022.

• Enhanced White Paper does not include a ROM estimate.

13 | P a g e

• Enhanced White Paper contains Classified material.

2.4 Submission of Enhanced White Papers

Issuance of this REWP does not commit the Government to pay for any preparation costs incurred by the Offeror in compiling a response to any aspect of this REWP and any such costs are not allowable or allocable to any US Government contract or agreement.

All EWPs must be sent directly to Heather Stiles (Agreement Officer), heather.stiles@us.af.mil & Logan Deming (Agreement Specialist), logan.deming@us.af.mil.. It is the responsibility of the submitting party to confirm receipt of submissions.

14 | P a g e

3.0 WHITE PAPER EVALUATION

All eligible EWPs will be evaluated in accordance with the selection process described below and will be evaluated on a rolling basis. As each solution in response to this REWP is likely to be unique, it is the Government's intent to evaluate each EWP submission as they are received. If an EWP is selected, a full proposal may be requested based upon the merit of the EWP solution offered, without regard to other submissions.

After EWP evaluation, the Agreements Officer will decide whether to:

• Select the Enhanced White Paper; or

• Place the Enhanced White Paper in the "basket" if funding currently is unavailable; or

• Reject the Enhanced White Paper (no award will be made based upon the submitted Enhanced White

Paper).

The Government reserves the right to evaluate all, some, or none of the EWPs received in response to this REWP. The Government reserves the right to cancel this REWP at any time. The government is not obligated to award an Other Transaction Agreement or follow-on contract.

3.1 Evaluation Factors

Enhanced White Paper evaluations will be based on an assessment of the factors below:

• Address at least two (2) of the Technology Areas described at Section 1.3, Technology Areas.

• Technical merit of the proposed solution.

• Clarity and soundness of the technical approach and the extent to which the objectives are addressed.

• Ability to meet project schedule.

• Adequacy of key management & technical resources to meet the requirements of the proposed technological solution.

• Evaluation of the potential impacts of the data rights assertions.

• Evaluation of conformance to the requirements at 10 U.S.C. 4022(d)(1).

• Affordability of proposed solution.

3.2 Evaluation Ratings

Overall ratings will be based on an integrated assessment of the above criteria, and submissions will be rated as "OUTSTANDING," "ACCEPTABLE" or "NOT ACCEPTABLE."

• UNACCEPTABLE: EWP does not meet requirements and contains one or more deficiencies.

• ACCEPTABLE: EWP meets requirements and indicates an adequate approach and understanding of the requirements. The proposal may contain weaknesses; however; these are offset by strengths.

• OUTSTANDING: EWP meets requirements and indicates an exceptional approach and understanding of the requirements. Strengths far outweigh any weaknesses.

15 | P a g e

4.0 OTHER INFORMATION

4.1 System for Award Management (SAM)

The Offeror must register in the System for Award Management (SAM) and maintain active registration, with current information, at all times during which they have an active federal award or a solution under consideration by the Government. Information on SAM registration is available at http://www.sam.gov.

4.2 Wide Area Work Flow (WAWF)

Invoices for payment must be submitted in Wide Area Workflow (WAWF) - https://wawf.eb.mil/. Registration in WAWF will be required prior to any award under this REWP. If invoicing through WAWF presents an issue, indicate this in the EWP response.

4.3 Follow-On Production Work

The authority at 10 U.S.C. § 4022, paragraph (f) provides the authority to enter into awards for follow-on production to successful participants of an agreement under the authority of an Other Transaction Agreement (OTA) for Prototype, utilizing competitive procedures.

This effort anticipates the need for possible follow-on production. The requirement for competition has been met through the REWP process, and upon successful completion of the prototype project and subject to the availability of funds, the Government reserves the right to proceed into a production OTA on a non-competitive basis.

http://www.sam.gov/