Call 002 TAF VDS 15 July 2021-final1.docx

FA9302-21-S-C001

Finding Agile Solutions for Test (FAST) Commercial Solutions Opening (CSO) Call 002 “F-35 Threat and Friendly (TAF) Visual Display System (VDS)” This Call is issued against the above referenced Commercial Solutions Opening (CSO) solicitation in accordance with DoD Class Deviation 2018-O0016 “DoD Commercial Solutions Opening Pilot Program.”

1.0 Overview

1.1 Call Type. This is Call 002, under the FAST CSO FA9302-21-S-C002. This is a two-step closed Call, where potential industry partners provide white papers in the first step, the Air Force will review those white papers, and select those that best meet the objectives described within this call. Pay attention to “provide” in 2.6 et. seq. The second step is a request for full proposals, and the Air Force intends to negotiate with those industry partners.

1.2 The NAICS code associated with this requirement will be 334118, Computer Terminal and Other Computer Peripheral Equipment Manufacturing, with a size standard of 1,000 employees.

1.3 Due date and time. White papers are due 29 JUL 2021 by 9:00AM PST. White papers received after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3).

1.4 Submission SPOC. White papers must be submitted to the Contracting Points of Contact (POCs):

Contracting Officer Name: Ryan Coney Address: 5 S. Wolfe Ave. Edwards AFB, CA 93524 Phone: 661-277-1829 Email: ryan.coney@us.af.mil

Contract Specialist Name: Ryan Coney Address: 5 S. Wolfe Ave. Edwards AFB, CA 93524 Phone: 661-277-8317 Email: ryan.coney@us.af.mil

1.5 Air Force Mission Owner. 412 EWG, Christina J Greer christina.greer.3@us.af.mil

1.6 Type of Contract/Instrument. The Air Force reserves the right to award the instrument best suited to the nature of the solution proposed. This could be either a Federal Acquisition Regulation (FAR) based contract or an Other Transaction for Prototypes under 10 U.S.C 2371b. If an Other Transaction for Prototypes is issued, a follow-on Production contract or transaction may be issued. If a follow-on production effort is pursued the effort will likely encompass up to 3 other DoD locations. It is anticipated that the award under this call will be a Firm-Fixed-Price (FFP) contract.

1.7 Estimated Number of Awards. The Air Force anticipates awarding one (1) contract; however, the Air Force reserves the right to award zero, one, or more contracts for all, some, or none of the solicited effort based on the offeror's ability to perform the desired work and considering Air Force funding fluctuations.

2.0 Areas of Interest:

2.1. Brief Summary. The 412th EWG/EWJ has a requirement for Visual Display Systems (VDSs) to support the Threat and Friendly/Virtual Air Threat (TAF/VAT) Joint Simulation Environment (JSE). For the purposes of this document, a VDS is defined as an out-the-window (OTW) display screen, image projectors, auto alignment and calibration system, mechanical edge blending solution, and support structures and interfaces. The VDS contractor will integrate all the VDS components.

The Air Force is seeking innovative solutions with regards to the fidelity and Field-OF-View (FOV) of the proposed VDS within this Call. The solution offered will need to consider the human factor relationship or the physical relationship of the primary components of the simulator. The important aspects to retain are the physical relationships of the pilot eye.

2.2. Background. The JSE was initiated in 2016 to provide state of the art simulation facilities for the Air Force (AF) and Navy to accomplish Developmental Testing (DT), Operational Testing (OT), High-End Advanced Training and Tactics (HEAT2), and experimentation. Multiple MFC simulators and Fighter-In-A-Box (FIAB) Simulators will be integrated with the rest of simulation elements and services to become the JSE.

The TAF VDS are for simulation of single-seat fixed wing fighter aircraft simulation operating in the simulated world in dawn, day, dusk and nighttime Out-The-Window (OTW) visual scene conditions. The facilities have floor space restrictions, Field-Of-View (FOV) requirements, and a future use of a Government Furnished Equipment (GFE) Helmet Mounted Cueing System (HMCS) requirement with a 60 inch (1.5m) focal distance that requires a dome display system with a 1.3 – 1.5 m screen radius with the pilot’s eye point at the screen center. A heads-Up-Display (HUD) image will be projected on the TAF VDS in lieu of an actual glare shield-mounted HUD.

Each TAF Simulator will consist of an MFC, VDS, image generator, TAF host and audio-visual system. Integration of these elements is the responsibility of the US Air Force 412th EWG/EWJ (JSE Project Office) with assistance from each of the associated contractors.

The VDSs are going to be used continuously for training and test purposes, and solutions offered should be considerate of continuous use.

2.3. Inherently Governmental Function. The contractor shall not perform inherently governmental functions as defined in Federal Acquisition Regulation Subpart 7.5 - Inherently Governmental Functions.

2.4. Associated Contractor Agreement. AFTC/PZIEB will set up an associate contractor agreement required between the government, the MFC contractor, the TAF VDS contractor, and Aechelon image generation system vendor.

2.5. Call Objectives

2.5.1. Total of four (4) TAF VDS, which will be installed in JSE facilities at Edwards Air Force Base, California (JSE-E). There is an option for up to eight (8) additional TAF VDS at Nellis Air Force Base, Nevada (JSE-N) and an option for an additional one (1) at Wright-Patterson, AFB, OH.

2.6. Visual Display system Requirements The display system shall provide a seamless OTW visual image across the FOV and shall not have visible changes of brightness in areas where individual projected images overlap (blend zones). Night-Vision-Goggle (NVG) compatibility is required for F-16 and threats

2.6.1. Field of View (FOV) The VDS FOV as seen from the Pilot’s Eye point at the geometric center of the dome display screen is detailed in the Table 1 below. Horizontal FOV shall be the same in both the left and right directions. The minimum value shall not be less than 220° HFOV (-110°/+110°) and 120° VFOV (-30°/+90°), however contractors are strongly encouraged to provide possible innovative solutions that exceed the minimum required target value.

220° HFOV(-110°/+110°)

120° VFOV (-30°/+90°)

*Target Value

300° HFOV(-150°/+150°)

140° VFOV (-30°/+90°)

*If technically feasible

2.6.2. Display Screen

2.6.2.1. The display screen shall be spherical in shape with pilot eye point located at the spherical center to provide constant OTW image distance.

2.6.2.2. The radius of the screen surface shall be between 1.3m and 1.5m, with the 1.5m radius being preferred.

2.6.2.3. The Pilot Eye Point (PEP) for the MFC is 47.02in above the floor and 49 in. aft of the front edge. This MFC has a six (6) inch vertical seat adjustment and is being modified for 3 degrees more aft tilt, a four (4) inch longitudinal adjustment, and a means for re-positioning. This PEP may change with the modifications and it and its volume should be accommodated as much as practical. Deviations or restrictions shall be noted.

2.6.2.4. It is desired to have greater fields of view, depending upon availability and costs. Any horizontal or vertical FOVs in excess of the target values, to include any additional equipment or channels, shall be proposed as an option.

2.6.2.5. For any proposed vertical or horizontal FOVs, basic or option, there should be no head or equipment shadows within the FOV.

2.6.3. Resolution

2.6.3.1. Average resolution over the FOV shall be 5.2 arc-minutes / optical line pairs or better. It is desired to have a higher resolution approaching 4.0 arc-minutes / optical line pair, at least in the central display areas (-15 degrees to +40 degrees vertically and +/- 30 degrees horizontally). Any resolution increases in excess of the average shall be proposed as an option.

2.6.3.2. Minimum average resolution over the projected area for any single projector shall be 6 arc-minutes / optical line pair or better.

2.6.4. Luminance

2.6.4.1. The minimum average white square luminance shall be 10 foot-Lamberts or better measured using the ANSI 50/50 white/black checkerboard test pattern.

2.6.5. Contrast

2.6.5.1. The minimum average contrast ratio shall be 10:1

2.6.5.2. The contrast ratio measurement shall be made using the ANSI 50/50 white/black checkerboard test pattern with all displays simultaneously illuminated with the test pattern. The pattern shall provide at least 8 squares per display channel with 50 percent of the squares at the specified minimum acceptable luminance.

2.6.6. Display System Latency

2.6.6.1. The latency of rendering of a full scene, which is measured from the projector first pixel input data of a frame to the light of that pixel on the display surface, shall be 27 milliseconds or less.

2.6.7. Distortion Correction/ Image Blending

2.6.7.1. A solution shall be provided for projected image distortion correction, blending, color matching as required for seamless projected image across the FOV. Distortion correction and blending functions may be performed by a system provided by the Contractor or through software (CDRL A001) installed on the government supplied image generation system. Up to 6U of space in government supplied 19” electronics racks that will be located next to each display system can be made available for the Contractor’s equipment. This rack will also house the Aechelon Nucleus image generation system.

2.6.8. Non-discernable Edge Blending

2.6.8.1. The blending area between the projectors shall not be discernable to the human eye. The blending areas shall not be discernable for Dawn, Day, Dusk, and Night scenes. It is expected that mechanical/optical edge blending may be required for seamless night-time imagery. For dawn, dusk, and night (all) scenes there should be little to no light leaks onto the OTW display area.

2.6.9. Automatic Alignment System

2.6.9.1. The display system shall incorporate automatic alignment and calibration functionality allowing the user, without operator intervention, to correct geometric alignment, distortion, and blending to maintain a seamless image after installation. Distortion and blending maintenance corrections shall take less than an hour to perform.

2.6.10. Projector Control / Communication

2.6.10.1. There shall be a method for communicating with the projectors for the purpose of controlling on/off/standby status of all projectors from a government supplied host computer. Contractor shall provide essential specification for the computer

2.6.10.2. Contractor shall provide network diagram. For any networking, single mode fiber is preferred.

2.6.11. Projectors

2.6.11.1. The projectors supplied with the system shall use solid-state technology to minimize cost of ownership (lamp life). Part #FL40-4K MKII will allow for commonality between Nellis VTTC and Edwards-Nellis-Wright-Patterson TAF Visual Display Systems.

2.6.12. HUD Projector

2.6.12.1. A HUD projector shall be provided to project heads-up-display graphics on the screen in front of the crew-station covering a 30° x 30° degree area as viewed from the PEP when: 1) MFC is in a F-35 configuration and the aircrew is not wearing the HMCS, 2) MFC is in an F-16/Blue or VATs configuration and the aircrew is wearing an HMCS, 3) MFC is in an F-16/Blue or VATs configuration and the aircrew is not wearing an HMCS. The HUD projector shall have sufficient contrast so that the background is not visible during day-time simulation. Geometric image correction will be provided. The HUD projector shall have independent on/off/standby status from the host control when the HUD is not required.

2.6.13. Image Generation Aechelon

2.6.13.1. The contractor shall integrate the VDS with the Image Generator.

2.6.14. Medium Fidelity Crew station (MFC)

2.6.14.1. The contractor shall work with the MFC contractor to ensure compatibility. The 412th EWG/EWJ shall integrate VDS into MFC with VDS and MFC contractor assistance.

2.6.15. Security Requirements

2.6.15.1. Network equipment (such as could be required for projector communication) will require prior approval before it can be installed in the lab. Wireless electro-magnetic communications (such as Wi-Fi and Blue-Tooth) are prohibited in the installation space.

2.6.16. VDS Fit-check Drawing. The contractor shall include a drawing which details how the VDS dome interfaces with the MFC in their drawing package. The contractor shall also include a drawing which details how the VDS domes fit into the JSE-E facility, rooms 171 and 172. (CDRL A003)

2.6.17. VDS Compatibility/Fit-checks. The VDS shall be a stable, free-standing structure resting on a concrete floor. The contractor shall work with the 412th Electronic Warfare Group Maintenance and Logistic Operations Division to ensure installation and integration of VDSs into JSE-E and JSE-N facilities are compatible. JSE-E and JSE-N facility drawings and specifications will be provided upon request.

Use of 1.3 – 1.5m radius domes is driven by facility size constraints, pilot ingress/egress and the required FOV. The proposed VDS should fit 2 each Visual Display Systems plus four (4) 19” equipment racks in an area 17ft wide x 31ft long x 9ft H. The VDS shall have an adequate access portal to enable cockpit and equipment installation and pilot ingress/egress.

Dome infrastructure shall fit within a ceiling height of 5m, without obstructing fire sprinkler systems.

2.7. Deliverables. The following paragraphs discuss deliverables expected, should an award be made for this requirement. The contractor does not need to go into detail within the white papers provided for these deliverables, but should consider the required deliverables identified below when providing the Rough Order of Magnitude (ROM) value within the white paper.

2.7.1. System Requirements Review/Preliminary Design Review (SRR/PDR). The contractor shall host a SRR/PDR at a mutually agreed upon date at Edwards AFB, CA or Nellis AFB, NV, contractor facility, or via teleconference. This meeting will include a tour/survey of the installation site and requirements review/preliminary design review. Preliminary drawings showing the general design and arrangement of all equipment, defining all mechanical and electrical interfaces, Interface Control Document (ICD) updates, and compliance matrix shall be presented. Contractor approach and initial concept for the modifications; activity, fabrication, and delivery schedule shall be included. Contractor will have the opportunity to clarify any issues or concerns at the time of the review. (CDRL A002) (CDRL A004) (CDRL A005)

2.7.2. Critical Design Review (CDR). Final Design review shall include the installation plan presentation. The supplier shall host a CDR at a mutually agreed upon date. The design review may be held at the installation location, Edwards AFB, CA or Nellis AFB, NV, contractor’s facility, or via teleconference. The contractor shall provide the modified design and provide drawings digitally from both a CAD program (an editable source file) and as a read only pdf files. The contractor shall review compliance matrix, schedule, preliminary test plans, installation plans, and update any risks or mitigations. Drawing updates showing the general arrangement/installation of the update and defining any mechanical and electrical interfaces changes determined. The CDR shall include the installation plan. The supplier shall present: (CDRL A004) (CDRL A005)

2.7.3. Final detail drawings, general arrangement, and interface control documents / drawings. (CDRL A002) (CDRL A003)

2.7.4. An installation plan demonstrating the feasibility of assembling and locating the VDS systems within the available spaces.

2.7.5. Documentation detailing how all requirements of the system will be met. This information may be provided in PowerPoint or Excel format.

2.7.6. A Bill of Materiel and preliminary recommended critical spares list with current pricing based on Mean Time Between Critical Failure (MTBCF) and Mean Time Between Failure (MTBF) calculation constructed from system predicted use time.

2.7.7. A test plan, including schedule and equipment requirements.

2.7.8. Power requirements, power connector part numbers (or commercial connector specification), and any cooling requirements. (CDRL A006)

2.7.9. Maintenance Manual(s) that describes all preventive, corrective, maintenance requirements or procedures, including equipment overhauls or time change requirements, with recommended maintenance intervals shall be provided by the supplier. The Maintenance Manual(s) shall provide detailed fault tree analysis, detection and diagnostic information. (CDRL A006)

2.7.10. Operator’s Manual(s) with operational procedures for subsystems provided with the VDS shall be provided by the contractor. (CDRL A006)

2.8. Installation and Setup

2.8.1. The contactor shall ship, install, setup, and calibrate four (4) VDSs in a government facility located at Edwards AFB, CA. The on-site installation shall take place on a mutually agreeable schedule.

2.8.2. The contractor shall ship, install, setup, and calibrate up to eight optional (8) VDSs in a government facility located at Nellis AFB, NV. The on-site installation shall take place on a mutually agreeable schedule.

2.8.3. The contractor shall ship, install, setup, and calibrate one optional (1) VDSs in a government facility located at Wright-Patterson AFB, OH. The on-site installation shall take place on a mutually agreeable schedule

2.8.4. The contractor shall be responsible for furnishing all equipment and tools required for installation and testing of the MFC. The contractor shall coordinate with 412th EWG Maintenance and Logistic Operations Division who shall supply the forklift and scissor lift.

2.8.5. The contractor shall coordinate external electrical, serial communication and video connectivity with the corresponding system contractor and the 412th EWG Maintenance and Logistic Operations Division.

2.9. Acceptance Testing

2.9.1. The contractor shall submit an acceptance test procedure for government approval for the VDS. (CDRL A006) The acceptance test procedure shall be performed at the completion of the installation of each VDS at the customer site. The acceptance testing shall, as a minimum, verify the following system performance characteristics

2.9.1.1. Field of View: The contractor shall verify image coverage of the required field of view and image geometry position accuracy to +/- 1 degree across the dome image.

2.9.1.2. Luminance Measurements: Acceptance testing shall include light meter measurements (in Foot-Lamberts) verifying the average luminance and contrast of the VDS using an ANSI 50% black and 50% white checkerboard test pattern with all projectors displaying the test pattern.

2.9.1.3. Resolution Measurements: Acceptance testing shall include resolution measurements using a set of ten white and black vertical and horizontal line pairs. Customer viewing of line pairs on the dome, as follows, to determine the point at which the line pairs are discernable as line pairs on the dome surface.

2.9.1.3.1. Perform resolution measurement at the center of each projected image

2.9.1.3.2. Calculate the arc-minute/Optical Line Pair for each projected image

2.9.1.3.3. Calculate the average for all of the arc-minutes/Optical Line Pair measurements

2.9.1.4. Intensity Matching: Acceptance testing shall include customer subjective Pass/Fail white intensity matching evaluation across all projected images using full field 0%, 50% and 100% white level test patterns without distracting visible anomalies.

2.9.1.5. Color Matching: Acceptance testing shall include customer subjective Pass/Fail Color matching evaluation of dawn, day, dusk, and night across all projected images using 5 customer-selected visual database OTW scenes without distracting visible anomalies.

2.9.1.6. Blend Zone: Acceptance testing shall include customer subjective Pass/Fail of non-discernable blend zone evaluation of dawn, day, dusk, and night across all projected images using 5 customer-selected visual database OTW scenes without distracting visible anomalies.

2.10. Training

2.10.1. One time on-site training at each site, Edwards, Nellis AFB, and Wright-Patterson in use of automatic alignment/calibration solution shall be provided by the contractor. Duration of training is anticipated to be 2 days or less and is to be provided to one (1) to ten (10) employees at both JSE-E, JSE-N, and Wright-Patterson. Training shall be provided after the successful completion of the acceptance test for the first VDS.

2.11. Delivery

2.11.1. Four (4) units to be delivered to Edwards AFB, up to eight (8) units to be delivered to Nellis AFB and one (1) unit delivered to Wright-Patterson AFB. Within phase two (2) (letter request for proposal RFP) the Air Force may identify additional units.

2.12. The Air Force is interested in exploring innovative technology domains that may not be covered in the list above, the above described area of interest is intended to also be a call for open ideas and technologies that cover other related areas not currently listed (i.e., the unknown-unknown). This Call is meant for innovative solutions to be adapted in innovative ways to meet DoD stakeholder’s needs in a short timeframe.

2.13. Communication between Prospective Industry Partners and Government Representatives. It is requested that interested industry partners submit questions in writing to the Contracting POC no later than 09 JUN 21, 1400 PST. Submitted questions will be reviewed and consolidated, and the Air Force will post answers to these questions as an amendment to this Call by 11 JUN 21. Please avoid using proprietary or confidential information. If a question requires the potential industry partner to provide information that includes proprietary information, please make sure to mark the information appropriately. Discussion with any point of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the government.

2.14. Address questions to: Contracting Officer, Ryan Coney, e-mail ryan.coney@us.af.mil. Please include the CSO Call number in the subject line of your email.

3.0 Submission Information

3.1. First Step: White Paper Instructions

3.1.1. General. A white paper prepared in accordance with the format stated in para 3.1.3. below shall include discussion of the nature and scope of the solution offered, the offeror’s proposed technical approach, and a rough order of magnitude (ROM) cost. The Government will review the white papers in accordance with the review criteria stated in para 4.1. Based on this review, the Government will determine which have the potential to best meet the Air Force’s needs. Offerors will be notified of the disposition of their white paper. Those offerors submitting white papers assessed as meeting Air Force needs will be asked to submit a technical and price proposal. The cost of preparing white papers in response to this announcement is not considered an allowable direct charge to any resulting or any other contract; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in FAR 31.205-18. White papers may be ineligible for further consideration if all requirements of this solicitation are not met. The White Paper should focus on the solution offered to meet the objectives identified above.

3.1.2. White Page Instructions. White papers shall be detailed enough to allow for a limited technical evaluation and to fully understand the materials used. White papers are limited to 20 pages prepared in .pdf format. Font should be size 10 standard business font, normal character spacing (i.e., not condensed). White papers received that exceed the page limitation will have the excess pages removed before review. White papers submitted that are illegible will not receive further consideration. Include page numbers.

3.1.3. Format. The white paper shall be formatted as follows:

3.1.3.1. Section 1. Title page

3.1.3.1.1. The white paper shall include a title page which identifies the company name, the company’s Commercial and Government Entity (CAGE) number, the company’s Dun & Bradstreet Data Universal Numbering System (DUNS) number, Company POCs (include email and telephone), and the title of the white paper. The title page does not count towards the page limitations identified above.

3.1.3.2. Section 2. Technical summary of proposed solution

3.1.3.2.1. Describe the technical summary of the proposed solution meeting the area of interest/objectives, including how the solution addresses the objectives identified in para. 2 within this Call and how the offeror intends to integrate the identified GFE items.

3.1.3.2.2. A statement of agreement to following any Associated Contractor Agreement that may be included in any resulting contract award. Additionally, a description of any projects that require collaboration with multiple contractors in a similar arrangement to an Associated Contractor Agreement.

3.1.3.3. Section 3. Estimated delivery schedule or period of performance

3.1.3.3.1. Describe the estimated lead time from award of a contract/agreement or the estimated period of performance length.

3.1.3.4. Section 4. ROM

3.1.3.4.1. The ROM is provided as a bottom line estimate used to indicate possible magnitude of proposed solution. This is not a request for a full price proposal. The offeror may segregate pricing to fit the technical summary provided in Section 2 of the white paper (e.g., if the technical summary proposed two approaches, the offeror may provide a ROM for each). The Air Force may use this to assist in making budget related decisions. The Air Force does not intend to award based on this dollar value.

3.1.3.5. Section 5. Open discussion

3.1.3.5.1. This section is optional and can be used to cover any information the potential industry partner wishes to address.

3.1.4. Other Information. Multiple white papers within the purview of this Call may be submitted by each offeror. If the offeror wishes to restrict its white papers, they must be marked with the restrictive language stated in FAR 52.215-1(e). Offerors shall not submit white papers that contain classified information without receiving further instruction by the Contracting POC.

3.1.5. Eligible Offeror. This is an unrestricted request. Small businesses are encouraged to submit white papers. Offerors are encouraged to complete the Annual Representations and Certification in the System for Award Management (SAM) as soon as possible.

3.1.6. There are no limits on the number of White Papers/proposals an offeror may submit.

3.1.7. You may be ineligible for award if all requirements of this solicitation are not met within the White Paper and proposal (if applicable) by the due date as identified above and in subsequent requests for proposals, if selected to provide a proposal.

3.2. Second Step. Full Proposal Requirements

3.3. PROPOSAL DUE DATE AND TIME. To be provided in the Requests for Proposal sent to offerors that submit White Papers considered to be of further interest to the Air Force. Proposals received after specified date and time, will be considered late in accordance with 52.212-1(f).

3.4. Submission POC: Full Proposals must be submitted to the Contracting Points of Contact (POCs):

Contracting Officer Name: Ryan Coney Address: 5 S. Wolfe Ave. Edwards AFB, CA 93524 Phone: 661-277-3234/ Cell phone: 330-261-3626 Email: ryan.coney@us.af.mil

3.4.1. General. The Government will invite select offerors to submit full proposals based on favorable evaluation results of White Papers. Proposals will be requested via a Request for Proposal (RFP) letter by the contracting officer, and will contain separate submission instructions and applicable due dates and timelines. The letter RFP will identify the information required to evaluate the full proposal (e.g., technical and price volumes). At a minimum, the Air Force will evaluate responses to letter RFPs for technical and price. Additional criteria may be required in order to adequately evaluate an offeror’s proposed approach (e.g., past performance). The letter RFP will contain other instructions such as the proposal due date, format, Air Force POCs, and submission method. The cost of preparing proposals in response to a letter RFP is not considered an allowable direct charge to any resulting contract or agreement. Unsuccessful offerors will be notified by the Government, either via email or letter, to inform them that the proposed effort is not of interest to the Government at this time.

3.4.2. Statement of Work. Each response to a letter RFP shall include a non-proprietary version of a Statement of Work (SOW). The SOW shall contain a summary description of the proposed solution, to include detailed task descriptions. This document will be made part of any resulting contract. The following is an outline for a SOW.

3.4.2.1. Background: The background information should identify the requirement in very general terms; describe why the project is being pursued, and how it relates to other projects. Summarize any statutory authority or regulations affecting the overall requirement.

3.4.2.2. Scope: This section should provide a brief statement of what the offeror expects to accomplish under the contract — the breadth and limitations of the contract effort. It should not include specific work tasks or a description of deliverable products since this will be included in the “Tasks” section.

3.4.2.3. Objectives: This section should provide a concise overview of the contract effort goals and objectives; and how the results or end products will be used.

3.4.2.4. Tasks/Technical Requirements: This section defines the tasks that the contractor shall complete during contract performance and would have a task description for each step of the Work Breakdown Schedule (WBS). The description of task requirements will depend on the approach that is selected to describe the required effort.

3.4.2.5. Deliverables: This section should clearly state all deliverables including CDRLs and material.

3.4.2.6. Period of Performance: The period of performance shall be clearly stated using units of months after contract award. Milestones shall be stated as a number of months after contract award. These milestones shall include the end of technical effort and end of contract period of performance.

3.4.2.7. Cost or Pricing Data: This Call is being executed under a CSO, which is authorized under a current Class Deviation (ref. DARS Tracking Number 2018-O0016, Class Deviation – Defense Commercial Solutions Opening Pilot Program). As such, awards made against this CSO will be considered commercial for the award itself. Awards issued outside of a CSO will require a separate determination of meeting the definition of a Commercial Item IAW FAR 2.101. Since awards made against this Call will be considered commercial, certified cost or pricing data will not be required. However, a Contracting Officer may require other than certified cost or pricing data in order to support price reasonableness.

3.4.3. Proposal Validity Period. Unless otherwise specified in the letter RFP, offerors must state the proposal validity period of their proposal. A minimum proposal validity period of 90 days should be provided.

4.0 Evaluations

4.1. White Paper Evaluation. The Air Force will review white papers as follows:

1. Technical approach to meeting the described objectives within this Call, to include how the offeror plans on integrating the identified GFP items

2. Ability to participate in the associated contractor efforts to fully integrate the required capabilities.

3. Funds Availability

4.2. Proposals will be categorized as Recommended, Selectable, or Nonselectable as follows:

1. Recommended: Proposals are recommended for acceptance if sufficient funding is available, and normally are displaced only by other recommended proposals.

2. Selectable: Proposals are recommended for acceptance if sufficient funding is available, but at a lower priority than recommended proposals. A Selectable proposal may require additional development. To ensure a diversity of approaches, a Selectable proposal may be prioritized over a recommended proposal if the Selectable proposal presents a unique approach unlike any of the recommended proposals.

3. Not Selectable: Even if funds were available, the proposal should not be funded

4.3. The Air Force will negotiate directly with those offerors selected for funding based off the white paper evaluations described above. Awards are contingent upon successful negotiations. The Air Force reserves the right to discontinue negotiations with any contractor should parties fail to reach agreement on contract terms, conditions, or price within a reasonable time. The Air Force may award all, some, or none of the proposed effort. Price will be considered to determine that the proposed price is fair and reasonable.

5.0 Other Information

5.1. System for Award Management Registration

5.1.1. FAR 52.204-7, System for Award Management (SAM) and DFARS 252.204-7004, Alternate A, System for Award Management (SAM) are included by reference. SAM is the primary Government repository for prospective federal awardee information and the centralized Government system for certain contracting, grants, and other assistance related processes. By submission of an offer, the offeror acknowledges the requirement that a prospective awardee shall be registered in the SAM database prior to award, during performance, and through final payment of any contract, basic agreement, basic ordering agreement, or blanket purchasing agreement resulting from this solicitation. Contractors may obtain information on registration and annual confirmation requirements via the SAM accessed through https://www.acquisition.gov or by calling 866-606-8220.

5.2. Debriefings

5.2.1. The Government will conduct written, post-award debriefings upon request only in accordance with 52.212-1(l) and will address the evaluation factors contained herein only. It will not include a comparison of submissions against a common statement of work (SOW) as the CSO provides no common statement of work that interested parties must respond to and instead represents opportunity for submission of a variety of innovative commercial items, technologies, and/or services that represent meaningful submissions of diverse scope and price. Associated Contractor Agreements

5.3. Associated Contractor Agreement

5.3.1. An associated contractor agreement will be required between the government, the MFC contractor, the mini-dome contractor, the PCD and SFD contractor, and the HOTAS contractor.

5.4. Non-government advisors

5.4.1. Offerors are advised that data submitted to the Government in response to this solicitation will be released to individuals who work for the following government support contractor(s):

DCS Corporation, MTSI, and JT4

5.4.2. These contractors provide advice and assistance analyzing and reviewing acquisition documentation, and participate as advisors in Government Source Selections. Offerors not wishing to have their submission released to the companies listed above must notify the Contracting POC before submission of their white paper. Please contact the Contracting POC within this Call with questions or concerns regarding their role.

5.5. Covered Defense Information

5.5.1. Offerors should take note that the provision at DFARS 252.212-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting is included in this Call. It is anticipated that contractors will not be provided or generate Covered Defense Information which will be processed, stored, or transmitted on/through an unclassified system that is owned, or operated by or for, a contractor.

5.6. Government Furnished Property (GFP) Availability

5.6.1. GFP is anticipated to be made available under any resulting contract. In accordance with FAR 45.201(b), the contractor is responsible for all costs related to making the property available for use, such as payment of all transportation, installation, or rehabilitation costs.

5.7. Other Applicable Provisions/Clauses

5.7.1. Other applicable provisions/clauses will be provided to potential industry partners within letter RFPs issued.

5.8. Marking Proprietary Proposal Information

5.8.1. Information contained in unsuccessful proposals will remain the property of the Applicant. The Federal Government may, however, retain copies of all proposals. Public release of information in any proposal submitted will be subject to existing statutory and regulatory requirements. If proprietary information is provided by an Applicant in a proposal, which constitutes a trade secret, commercial or financial information, it will be treated in confidence, to the extent permitted by law, provided that the proposal is clearly marked by the Applicant as follows:

Proposal data the firm does not wish to make public, or to be used by the Government except for peer review, shall:

(1) Mark the first page of each proposal volume with the following legend: "This proposal includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed-in whole or in part-for any purpose other than to evaluate this proposal. If, however, a contract 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 provided in the resulting contract. 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 pages [insert numbers or other identification of sheets]"; and

(2) Mark each sheet of data it wishes to restrict with the following legend: “Use or disclosure of data contained on this page is subject to the restriction on the first page of this volume." DoD assumes no liability for unmarked data disclosure or use and may use or disclose such data for any purpose.

5.9. Base Support/Network Access:

5.9.1. Base support will be determined for each award for testing, validation, and demonstration.

Export Control: Information involved in this effort may be subject to Export Control, International Traffic in Arms (ITAR) 22 CFR 120-131, or Export Administration Regulations (EAR) 15 CFR 710-774. If effort may be subject to export control, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal. (See DFARS 225.7901-4, DFARS 252.225-7048, Export-Controlled Item). Foreign Participation: Participation at the prime level is prohibited. Subcontracting arrangements will be handled in accordance with the International Traffic and Arms Regulation. In addition, foreign national participation will be limited to public domain information only.

CONTRACT DATA REQUIREMENTS LIST (CDRL) QUICKLIST

CDRL A001: Computer Software Product (CSP), DI-IPSC-81488. [See CALL Par 2.6.7.1] CSP is required at Base-line of each new software release.

CDRL A002: Engineering Drawings, DI-DRPR-80651. [See CALL Par 2.7.1, 2.7.3] Engineering drawings are required at Base-line of each new drawing release.

CDRL A003: Interface Control Drawing Documentation, DI-CMAN-81248. [See CALL Par 2.6.16, 2.7.3] ICDs for Medium Fidelity Cockpit systems to include structures, power, and their interface points to the facility.

CDRL A004: Design Review Data Package, DI-ILSS-81335 [See CALL Par 2.7.1, 2.7.2] System Requirements Review / Preliminary Design Review (SRR/PDR). Critical Design Review (CDR).

CDRL A005: Technical Reviews and Audits on Defense Programs, IEEE 15288.2. [See CALL Par 2.7.1, 2.7.2] System Requirements Review / Preliminary Design Review (SRR/PDR). Critical Design Review (CDR). Training shall be provided after the successful completion of the acceptance tests for the first Medium Fidelity Cockpit.

CDRL A006: Commercial Support Documentation (CSD), DI-MISC-80557. [See CALL Par 2.7.8, 2.7.9, 2.7.10, 2.9.1] Data product generated by the specific and discrete task requirements as delineated in the contract.