SUBSCRIBE HERE
Request for Solutions: System-of-Systems Controlled Environment Test Infrastructure
Petty Officer 3rd Class Tyrel Greenough, a corpsman with Headquarters Company, 3rd Battalion, 3rd Marine Regiment, watches the helicopter that will take him and the rest of the men participating in Operation Big Wave back to base land in Khanagawr, Afghanistan Aug. 20, 2010. The operation was conducted to disrupt the enemy from using supply lines to bring weapons and fighters into Nawa.

Request for Solutions: System-of-Systems Controlled Environment Test Infrastructure

CLICK TO VIEW DIRECTLY ON THE TREX WEBSITE 

1.0 Purpose

 

This Request for Solutions (RFS) is issued to locate capable vendors with the ability to deliver a unique solution for the System-of-Systems Controlled Environment Test Infrastructure (SCETI) requirement presented below. The Government will evaluate the solutions with the intent of awarding an Other Transaction Agreement (OTA) in accordance with 10 U.S. Code § 2371b.

 

2.0 Summary and Background

 

The U.S. Army is interested in improving its test capability for sensors used in degraded visual environments (DVE) conditions, including dust and heavy rain. Current Government test capabilities allow for testing in live-flight (manned rotary winged tests), which provides realistic flight mechanics but comes with significant costs and risks – or in a laboratory setting, which is low cost but does not provide realistic mechanics. Additionally, in live flight test, the environments to which the system under test (SUT) can be exposed to are limited and non-repeatable.

 

In order to improve this test capability, the U.S. Army is interested in prototyping a system that will place sensor assemblies into low cost emulated flight through artificial repeatable rain and dust DVEs characterized by instrumentation in order to directly enhance the readiness and capability of Army aviation platforms. The full SCETI capability will be delivered to Redstone Test Center. A stand-alone copy of the dust measurement suite will be delivered to Yuma Test Center.

 

2.1 The characteristics of this system and the Government concept for its development are included in the attached SCETI Technical Supplement.

 

2.2 Intellectual Property and Rights in Technical Data: Intellectual Property is to be negotiated based on the offeror’s proposed solution.

 

It is the Government’s desire to receive Government purpose rights to all development and deliverables of technical data funded under the transaction agreement to include but not limited to RATH-based software plugins developed for operation of SCETI (source code and executables). Government purpose rights means the right to use, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction; and release or disclose technical data 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 for United States government purposes.

 

The Government desires to have government purpose rights for at least a five-year period, which would commence upon delivery of the SCETI capability. The Vendor would have the exclusive right, including the right to license others, to use technical data in which the Government has obtained government purpose rights under this contract for any commercial purpose during this five-year period. Documentation for software based on the Government-owned RATH architecture will be marked with Distribution Statement D, Distribution authorized to the Department of Defense and U.S. DoD contractors only due to Critical Technology effective 4 January 2018.

 

Commercial software native to any COTS items used require no distribution statement or export controls.

 

The definitions for rights in technical data and computer software under this effort shall be the same as utilized in the Defense Federal Acquisition Regulations clause 252.2277013(a), dated FEB 2014.

 

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

 

2.4 Evaluation Process: After receipt of submissions from TReX members, the Government will complete their initial assessments from a pool of Government subject matter experts*. At this point, the Government may conduct a down select to the pool of vendors with the most technically feasible solutions to hold expanded conversation on the proposed solution and/or potential demonstrations, however responses may be accepted without further discussion.

 

*Support contractors will not be involved in the evaluation of responses.

 

3.0 RFS Responses:

 

3.1 Technical Solution: The Vendor’s proposed technical solution shall describe their approach to providing the system characteristics described in the SCETI Technical Supplement. The solution shall describe how the Vendor plans to provide all of the major capabilities described, with the order of importance to the Government being

 

1.) the emulated flight capability; 2.) the SCETI control software; 3.) the atmospheric measurement capability; and 4.) the rain development capability.

 

This hierarchy of capabilities is based on the criticality of the component capability to the SCETI mission. For example, if SCETI has an emulated flight capability but no rain capability, sensors may still be tested in existing dust generators at Redstone Test Center or during naturally occurring rainstorms.

 

In addition to describing the approach to delivering these capabilities, the technical solution shall include a full discussion of: a) anticipated development risks; b) a description of the maintenance concept for SCETI; c) estimated lifecycle management costs for a fully delivered system; d) team composition and subvendor involvement.

 

Ensure that you state all assumptions made during development of your responses.

 

3.2 Intellectual Property and Rights in Technical Data: As outlined in paragraph 2.2 above, all IP and data rights remain negotiable based on individual vendor solutions. While the Government has expressed their desire, Vendors are not limited to proposing solutions which adhere only to that desire. Your response should clearly outline the appropriate rights in technical data that will be delivered with your solutions, as well as a list of any third-party software/hardware to be delivered; in addition to any required overhead/recurring costs of the use of that software/hardware.

 

3.3 Anticipated Delivery Schedule: With the technical solution, the Vendor shall include the anticipated delivery dates of all SCETI capabilities and completion dates for all tasks and task stages as described in the SCETI Technical Supplement. The Vendor is permitted to propose a modified staging structure within their solution, with justification for deviation from the Government concept, as appropriate.

 

3.4 Proposed Pricing Milestones: Vendors should submit fixed amount pricing with their solution, with payments occurring at clearly definable, detailed milestones. It should be clear, with sufficient detail, what is being delivered at each milestone. These milestones will serve as more than mere payment points, but also as “gates” to proceed onward with the project.

 

The Government is not dictating a specific price mechanism and Vendors are encouraged to submit a payment plan that fits appropriately with their technical solution. (E.g. you are not required/limited to match milestones specifically to the tasks/stages outlined in the Technical Supplement)

 

3.5 Tailored SCETI Technical Supplement: Vendors will be asked to tailor the SCETI Technical Supplement alongside the solution with tracked changes to reflect the solution and approach proposed. Acceptable tailoring includes modification of characteristics to describe what the proposed solution will deliver, modifications to the staging strategy as described within the technical solution, and reference documents to be provided by the Government as required to provide the solution.

 

3.6 Provide your nontraditional* business status or your ability to meet the eligibility requirements in 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 section 1502 of title 41 and the regulations implementing such section.

 

3.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.

 

3.8 All questions related to this RFS should be submitted in writing to [email protected], with “SCETI” used in the subject line. Note: the Government reserves the right to post submitted questions and answers, as necessary (and appropriate) to facilitate vendor solution responses.

 

3.9 Responses shall be submitted no later than 12:00 PM EST on March 15, 2018. Your response should be submitted electronically to [email protected], with “SCETI” used in the subject line.

 

3.10 Responses shall not exceed 25 pages in length, utilizing standard 12-point font. Any charts or figures are not bound by the 12-point font requirement.

 

4.0 Selection Process

 

4.1 Individual responses will be evaluated with consideration given to the demonstrated expertise and overall technical merit of the response, feasibility of implementation, and total project risk. The proposed project price, delivery schedule, and data rights assertions will be considered as aspects of the entire response when weighing risk and reward. Further, the Government will evaluate the degree to which the proposed concept provides an innovative, unique – yet realistic and sustainable – approach to meeting the SCETI technical capabilities and objectives.

 

4.2 The Government reserves the right to request demonstrations of commercially proposed solution sets as part of the negotiation and risk assessment portion of the evaluation.

 

4.3 The Government will issue an OTA to the respondent(s) whose solution substantiates to be most advantageous to the Government, cost, schedule, technical risks and other factors considered.

 

5.0 Anticipated Nature of the Agreement

 

The nature of the agreement will be heavily influenced by individual solutions proposed. However, it is the Government’s intent for the OTA(s) issued to be of a fixed amount, with clearly definable milestones. The agreement will provide a mutually beneficial plan between Government and vendor to complete each task outlined in the SCETI Technical Supplement within the scope of the vendor’s solution.

 

6.0 Additional Information

 

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

 

6.2 Export controls: research findings and technology developments arising from the resulting White Paper 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).

 

6.3 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]”

 

6.4 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.”

 

6.5 The Agreements Officer for this effort is Mr. Brian Serra. He can be reached at [email protected] or 407-208-3357.