TREX

Air Force Distributed LVC Prototype Project

CLOSED ! ! !

Submission Deadline Extended to June 29, 2018 ! ! !

Request for Solutions:

Distributed Live Virtual Constructive (dLVC) Prototype

Amendment 1 - 18 June 2018 (dLVC RFS - Amd1)

Questions Answered (dLVC RFS Questions-Answers)

1.0 Purpose

This Request for Solutions is seeking a demonstratable system that balances computer processing for modeling and simulation at ground and aircraft processing nodes when connected by a training datalink with limited bandwidth. The Government will evaluate the solutions with the intent of negotiating an Other Transaction Agreement under the Training and Readiness Accelerator (TReX).

2.0 Summary and Background

The US Air Force uses training to acquire skills, develop proficiency, and evaluate performance. The Distributed LVC prototype project will demonstrate an architecture which balances model and simulation processing requirements between ground and aircraft nodes given a limited-bandwidth datalink. These computer models are required to generate virtual and constructive weapons, threats, and targets which enable flying training for initial skills and proficiency in support of air mobility and combat readiness.

The Distributed LVC prototype will consist of a ground-based computational node connected to a mobility rack-mounted or tactical aircraft pod-based node via a simulated radio datalink similar to the fifth-generation advanced training waveform (5G-ATW) developed by the Air Force Research Laboratory’s SLATE Advanced Technology Demonstration. The 5G-ATW datalink passes encrypted messages via compressed distributed interactive simulation (cDIS) data packets. During a training exercise, many (several hundred) simulators and computer generated forces (i.e., synthetic entities) will pass data about their position performance, weapons and status through ground-based communication node(s) to many (~100) live training systems via a training radio datalink. The live training systems will also be sending data about their performance, weapons, and status to the synthetic entities. Through this data exchange, the live operators will be able to train with and against many more entities than can be reasonably fielded in an exercise hosted on a range with limited airspace, real estate, and security.

Entities generate data packets as required to communicate a change in their performance, weapons and system status. In a dynamic training environment, many (~10-20) messages may be rgenerated from a single entity every second. These data are transmitted on the 5G-ATW datalink using up to 64 discrete frequencies within the upper L band. However, the transmission is subject to interference and attenuation requiring repeating messages. Therefore, in order to support a large force employment exercise with up to 1000 live and synthetic entities, a very large number of data packets must be passed between live and synthetic entities.

The Distributed LVC prototype project will demonstrate an architecture that establishes models and simulation at the ground node and aircraft node in order to reduce the data volume on a connecting training datalink.

2.1 Vendors interested in responding to this Request for Solutions must be members of the Training and Readiness Accelerator (TReX).

3.0 Technical Overview and Objectives

Training scenarios generate synthetic entity data packets to support training participants and training objectives. The Distributed LVC system requirements below establish the volume of data generated during training scenarios:

1. Air mobility and combat scenarios
a. Airdrop (16-ship formation)
b. Offensive counter air (32 friendly v 64 enemy aircraft)
c. Defensive counter air (16 friendly v 64 enemy aircraft)
d. Air Interdiction (8-ship strike package, fighter/bomber/Special Operations Forces mix)
e. Close air support (4-ship combat air patrol, surveillance/reconnaissance full-motion video, with joint terminal attack controller

2. Data generation
a. Live weapon systems
i. Aircraft performance changes 5° roll, pitch, yaw; 5% power; 10 kts airspeed; 50 ft altitude
ii. System operating status, mode
iii. Weapons status, mode, probability of kill, real-time kill assessment
iv. Radar mode, tracks
v. Radar warning receiver mode, tracks
vi. Countermeasure operating status, mode
vii. Cloud ceiling/winds/gusts viii. Identification, Friend, or Foe (IFF) status, tracks ix. Infrared sensor status, tracks
b. Simulator training (virtual) systems
i. Aircraft performance changes 5° roll, pitch, yaw; 5% power; 10 kts airspeed; 50 ft altitude
ii. System operating status, mode
iii. Weapons status, mode, probability of kill, real-time kill assessment
iv. Radar mode, tracks
v. Radar warning receiver mode, tracks
vi. Countermeasure operating status, mode
vii. Cloud ceiling/winds/gusts
viii. Visual system depiction changes with weather/season/time of day/battle damage/electro-optical spectrum ix. Identification, Friend, or Foe (IFF) status, tracks x. Infrared sensor status, tracks
c. Computer generated forces (constructive) entities
i. Allied aircraft type/number/formation/route/signature
ii. Aggressor aircraft type/number/formation/route/damage state/signature
iii. Mobile surface-to-air missile movement/operation/track/launch/damage state/signature
iv. Fixed surface-to-air missile operation/track/launch/damage state/signature
v. Radar range/jamming effectiveness/countermeasures
vi. Weapons track/target/launch
vii. Ground forces type/number/formation/route/signature/damage state
viii. Cloud ceiling/winds/gusts

3. Communications network
a. Open systems architecture
b. Ground node
c. Aircraft node with P5 pod form, power, cooling limits
d. Datalink bandwidth
i. Low (1 Mb/sec)
ii. High (10 Mb/sec)
iii. Dynamic (variable due to interference/attenuation, 0.1-10 Mb/sec)
e. Cross data solution for four multiple, independent levels of security
f. Data latency 50 ms [minimum], 10 ms [goal] ground node-line of sight data link-aircraft node
g. Encryption capability (required in design, but not required for demonstration) SECRET [minimum], TOP SECRET [goal]

Minimum - Level of performance that is required to be useful.
Goal - Level of performance which would best meet the mission needs. Performance beyond the goal is not valuable.

4.0 Program Overview and Phases

4.1 Phase 1 – The first phase will establish the architecture and trade space for live weapon systems, simulators, and constructive models to communicate on an encrypted network with distributed processing and a radio data link between live and synthetic entities. A preliminary design review will be conducted and report delivered to document the proposed architecture design with an outline of expected network performance given low, high, and dynamic radio data link capabilities.

4.2 Phase 2 – The second phase will demonstrate the architecture design. The live systems will be represented by a training pod form factor stimulated by a live aircraft emulation. The 5G-ATW data link (or similar) may be simulated with a network cable connecting the physical layers. Simulators and constructive entities will be represented by a combination of desktop flight simulators and automated, computer-generated forces executing an air mobility and combat simulation. The entities will generate state data according to the requirements above. Network performance will be evaluated on data volume and latency measures.

4.3 The prototype will be evaluated by government users in an operational demonstration and a technical report will be delivered to document the architecture, models, documented source code, simulation interfaces, and network performance. The training pod node and ground node will be delivered to the government at conclusion of the demonstration.

4.4 The combined period of performance of the two phases will be dependent on the selected offeror’s solution, though may not exceed two years.

5.0 RFS Responses:

5.1 The Vendor’s proposed solution shall describe their approach to delivering a demonstrable Distributed LVC prototype, with specific emphasis addressing the focus areas listed below.

Focus Area 1: Vendors should clearly identify their understanding and experience with simulator architecture, to include cDIS.

Focus Area 2: Vendors should clearly detail their approach to presenting a viable network architecture.

Focus Area 3: Vendors should clearly detail their understanding of processing capabilities to handle data volume and latency for the prescribed training scenarios.

Focus Area 4: Vendors should clearly detail their approach to using an open systems architecture.

The focus areas are not listed in any specific order of priority and responses will be considered as a whole.

5.2 Please ensure any assumptions made are clearly stated in your response.

5.3 Intellectual Property and Rights in Technical Data: All IP and data rights are negotiable based on individual vendor solutions.

It is the Government’s desire to receive government purpose rights to all development and deliverables of technical data and software funded under the transaction agreement, for at least a five-year period. The five-year period, or such other period as may be negotiated, would commence upon execution of the Other Transaction Agreement that required development of the items, components, or processes or creation of the data. Upon expiration of the five-year or other negotiated period, the Government would receive unlimited rights in the technical data. Government purpose rights means the right to use, modify, reproduce, release, perform, display, or disclose technical data and software within the Government without restriction; and release or disclose technical data and software outside the Government and authorize persons to whom release or disclosure has been made to use, modify, reproduce, release, perform, display, or disclose technical data and software for United States government purposes.

Your response should clearly outline the appropriate rights in technical data and software that will be delivered with your solutions.

5.4 Anticipated Delivery Schedule: With the technical solution, the Vendor shall include the anticipated delivery dates for each phase. A one-to-two-year timeline is considered an appropriate, realistic delivery timeframe.

5.5 Proposed Pricing and Milestone Payments: Vendors shall submit a fixed price for their solution for Phase 1 and Phase 2. The pricing for each phase should be further divided into milestone payments that are tied to clearly defined performance achievements. Your pricing submission shall be submitted in a separate document with no pricing detail provided in the technical response. There is no limit to the page length for the pricing submission.

5.6 Provide your nontraditional* business status or your ability to meet the eligibility requirements of 10 U.S. Code § 2371b on the cover page of your response. Within your response, please check the following box which applies – with appropriate justification if applicable.

There is at least one nontraditional defense contractor or nonprofit research institution participating to a significant extent in the project. All significant participants in the transaction other than the Federal Government are small businesses or nontraditional defense contractors. At least one third of the total cost of the project is to be provided by sources other than the Federal Government.

*Nontraditional – 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 DoD that is subject to full coverage under the cost accounting standards prescribed pursuant to 41 U.S. Code § 1502 and the regulations implementing such section.

5.7 In addition to your nontraditional business status, the cover page of the response shall also include the company name, Commercial and Government Entity (CAGE) Code (if available), address, and primary point of contact including phone number and email address. The cover page does not count towards page count.

5.8 All questions related to this RFS should be submitted in writing to initiatives@nstxl.org, with “dLVC” used in the subject line. Questions must be submitted no later than 12:00 PM EST on June 6th, 2018. Questions received after the deadline may not be answered. Questions shall not include proprietary data.
Note: the Government reserves the right to post submitted questions and answers, as necessary (and appropriate) to facilitate vendor solution responses.

5.9 Responses shall be submitted no later than 12:00 PM EST on June 29th, 2018. Your response should be submitted electronically to initiatives@nstxl.org, with “dLVC” used in the subject line. Any submissions received after this time on this date may be rejected as late and not considered.

5.10 Technical responses shall not exceed nine pages in length, utilizing standard 12-point font. Charts or figures directly relevant to the solution may be referenced and submitted as appendices and are not bound by the 12-point font requirement. Any pages submitted outside of this page length requirement, outside of standard charts and figures, will not be reviewed. Cover page does not count towards page count.

6.0 Selection Process

6.1 Individual responses will be evaluated with consideration given to the technical merit of the response, feasibility of implementation, and total project risk. The proposed project price, schedule, and data rights assertions will be considered as aspects of the entire response when weighing risk and reward. The Government will evaluate the degree to which the submission provides a thorough, flexible, and sound approach in response to the total submission.

6.2 The Government will award this project, via TReX, to the respondent(s) whose solution substantiates to be most advantageous to the Government, cost, schedule, technical risks and other factors considered. The Government reserves the right to award to a respondent that does not meet all of the requirements, but provides attributes or partial solutions of value, of the Request for Solutions.

7.0 Additional Information

7.1 The costs of preparing and submitting a response is not considered an allowable direct charge to any government contract or agreement.

7.2 Export controls: research findings and technology developments arising from the resulting project may constitute a significant enhancement to the national defense and to the economic vitality of the United States. As such, in the conduct of all work related to this effort, the recipient will comply strictly with the International Traffic in Arms Regulation (22 C.F.R. §§ 120-130), the National Industrial Security Program Operating Manual (DoD 5220.22-M) and the Department of Commerce Export Regulation (15 C.F.R. §§ 730-774).

7.3 Interaction and/or Disclosure with Foreign Country/Foreign National Personnel.

The contractor should comply with foreign disclosure processes IAW Army Regulation 380‐10, Foreign Disclosure and Contacts with Foreign Representatives; Air Force Instruction 16-201 Air Force Foreign Disclosure and Technology Transfer Program; Department of Defense Directive (DoDD) 5230.11, Disclosure of Classified Military Information to Foreign Governments and International Organizations; and DoDD 5230.20, Visits and Assignments of Foreign Nationals.

7.4 All submissions shall be unclassified. Submissions 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 the following sentences on the cover page:

“This submission 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 Company 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]”

7.5 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 submission.”

To view and download the amended dlVC Request for Solutions (RFS) or the questions answered, click the hyperlink below.

dLVC RFS - Amd1

dLVC RFS Questions-Answers

Active TReX Membership is required to submit a solution for any RWP or RFS.  To start your TReX Membership application and registration, please visit TReX Membership.

Any questions regarding the pending RFS should be directed to initiatives@nstxl.org.