CLOSED ! ! !
Request for Solutions: OneSAF – Computer Based Training
Posted: 20 September 2018
Submitted Questions Answered: OneSAF_CBT_RFS_Q_A_17Oct2018_v3
Contractor Vetting Guidance: Contractor Security Vetting v3 092518
RFS Proposal Submission Date Extended to October 25, 2018 ! ! !
This Request for Solutions is issued to develop and acquire a Computer Based Training (CBT) tool for the One Semi-Automated Forces (OneSAF) program capable of demonstrating the use of the OneSAF software application in lieu of face-to-face training mechanisms. The Government will evaluate the solutions with the intent of negotiating an Other Transaction Agreement under the Training and Readiness Accelerator (TReX).
2.0 Solutions Summary and Service Background
2.1 The United States Army Modeling and Simulation (M&S) community faces challenges with ensuring that its users are trained to an adequate level to allow them to reasonably support required events – whether large or small entity count or number of users. Additionally, the cost to conduct basic level training and schedule management can become cumbersome and counterproductive. The delivered solution will allow for the distribution of unclassified FOUO CD/DVD media to training locations and for the training audience to conveniently schedule training without additional cost.
2.2 The Program Executive Office for Simulation, Training, and Instrumentation’s (PEO STRI) OneSAF program coordinates with M&S users and community leaders to offer, schedule, and conduct user training multiple times throughout the year. Careful and considerate coordination is required to conduct these classes at a customer site or at the program office site in Orlando, FL. It takes a focused, time-consuming effort to ensure that customer funds are put on contract in a timely manner and that all required paperwork is provided in accordance with local (PEO STRI) policy and guidance.
2.3 The effort will be accomplished in three distinct efforts with two technical milestones. The first effort will be the initial response outlining the initial concept of the vendors’ solution outlining the methodology and technology to be used. The second effort – also called Technical Milestone 1 – will be a usable, working module providing initial capability for a CBT application including a Knowledge Check capability. The third effort – Technical Milestone 2 – will be a fully operational prototype module providing a production-ready capability to be delivered to the Government.
2.4 Attachment 1, OneSAF CBT Tech Supplement, contains the requirements for the user interface walkthrough and the threshold and objective requirements for Technical Milestone 1. Attachment 2, OneSAF Operator Manual, contains full information about the operation of the OneSAF system and will provide more detail into the use of the various menus and tools to be trained as part of the prototype.
2.5 The Government anticipates that follow-on production contracts or transactions may be awarded to the Vendor(s) of this effort without the use of competitive procedures if the participants in this transaction successfully complete the prototype project as outlined within this Request for Solutions and in accordance with the initially proposed individual solutions.
2.6 The desired prototype(s) will be an open, accessible, user-friendly training tool that helps OneSAF M&S community users to provide point-of-need training for basic operator skills to their representatives in support of simulation exercises.
2.7 The Army seeks to focus on reduction of training costs and the enabling of distributed training capabilities while allowing modules to be continuously inserted and updated without disruption to the user training community.
2.8 Vendors interested in responding to this Request for Solutions must be members of the Training and Readiness Accelerator (TReX).
3.0 RFS Responses:
3.1 The Vendor’s proposed solution should describe their approach to delivering a training solution for the OneSAF Management and Control Tool (MCT) as outlined in Section 2 and the Tech Supplement, with emphasis and focus on the following:
a) Ease of interface use, module access
b) Efficacy of instruction
c) Ability to represent current simulation GUI
d) Scalability for multiple versions
3.2 Vendor shall ensure all commercial and/or proprietary software applications are identified as part of the response. These callouts will not count against the page limits established as part of the RFS.
3.3 Intellectual Property (IP) Rights and Rights in Technical Data and Computer Software: All IP and data and software rights remain negotiable based on individual Vendor solutions.
As all information provided by the Government for this effort is restricted in its distribution, it is the intention of the Government to own, maintain, and manage the content that is delivered for this CBT. It is the desire of the Government to contract out for more updates and/or make updates as part of its current contracts in order to evolve and enhance this CBT as the program needs dictate. As well, the Government may award additional contracts or transactions to the Vendor of this effort without the use of competitive procedures if the participants in this successfully complete the prototype project as outlined within this Request for Solutions and in accordance with the initially proposed individual solutions. Vendor shall propose the intellectual property rights and rights in technical data and computer software to be delivered with your solutions, clearly outlining any restrictions. If additional pages are needed to provide restrictions, they may be submitted as an appendix – though your initial approach should be clearly outlined within your technical response.
3.4 Anticipated Delivery Schedule: Vendor shall include the anticipated delivery schedule to reflect their individual solution.
3.5 Proposed Pricing and Milestone Payments: Vendors will submit a fixed amount price for their prototype solution, further divided into severable milestone payments as appropriate. Your pricing submission shall be submitted together with the technical response as an appendix. There is no limit to the page length for the pricing appendix, though it should be noted that cost detail is not being requested.
3.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.
3.7 In addition to your nontraditional business status, the cover page of the response will 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@example.com, with “OneSAF CBT” used in the subject line. Questions must be submitted no later than 12:00 PM EST on October 5th. Questions received after the deadline may not be answered. Questions shall not include proprietary data as the Government reserves the right to post submitted questions and answers, as necessary (and appropriate) to facilitate Vendor solution responses.
3.9 Responses will be submitted no later than 12:00 PM EST on October 25th. Your response should be submitted electronically to firstname.lastname@example.org, with “OneSAF CBT” used in the subject line. Any submissions received after this time on this date may be rejected as late and not considered.
3.10 Technical responses shall not exceed ten 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 or page count. 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. Commercial and/or proprietary software shall be submitted as an appendix and does not count towards page count.
3.11 Your submissions shall be submitted as a PDF document, with your company name listed as the first part of the file submission. (e.g. “Company X – OneSAF CBT”)
4.0 Selection Process
4.1 Individual responses will be evaluated with consideration given to the vendor’s ability to provide a clear description of the proposed solution, technical merit of the response and total project risk. The proposed project price, schedule, and intellectual property 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 considering the identified focus areas in Paragraph 3.1 as well as the ability to fulfill the requirements in Attachment 1, OneSAF CBT Tech Supplement.
4.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.
4.3 If sufficient validation of the claim is not provided, the Government may reject the submission. Assessment of risks is subjective. If the risk is obvious or the schedule seems overly aggressive, the Government will consider that in their total risk assessment.
5.0 Additional Information
5.1 The costs of preparing and submitting a response is not considered an allowable direct charge to any government contract or agreement.
5.2 Export controls: research findings and technology developments arising from the resulting prototype 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).
5.3 Interaction and/or Disclosure with Foreign Country/Foreign National Personnel.
The Vendor should comply with foreign disclosure processes IAW US Army Regulation (AR) 380‐10, Foreign Disclosure and Contacts with Foreign Representatives; 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.
5.4 All submissions will 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 will include the following sentences on the cover page:
“This submission includes data that will not be disclosed outside the Government, except to non-Government personnel for evaluation purposes, and will 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 will 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]”
5.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 or download the request for solutions (RFS), the RFS amendment extending the submission date, the technical supplement, and guidance on contractor security vetting click the following hyperlinked text.
Active TReX Membership will be required to submit a solution for this opportunity. To start your TReX Membership application and registration, please visit TReX Membership.
Any questions regarding the opportunity should be directed to email@example.com.