Inactive

Amendment One: The purpose of Amendment One is to provide responses to questions received in accordance with this RFI. Innovation Challenge: How Can the Department of Defense Better Contract with Indu... Amendment One: The purpose of Amendment One is to provide responses to questions received in accordance with this RFI. Innovation Challenge: How Can the Department of Defense Better Contract with Industry for Software Development Solutions? The Department of Defense (DoD) runs on software. Every DoD mission, major system acquisition, and technology modernization effort is software intensive. Effective, timely software is critical to enabling future DoD capabilities to dominate future conflicts. The DoD and military services recognize that to deliver such capabilities, the DoD needs contract structures that enable flexibility. This requires improving how the DoD harnesses commercial software development expertise, capabilities, and platforms. DISA is partnering with the Office of the Undersecretary of Defense Acquisition & Sustainment (OUSD A&S) Acquisition Enablers Software Pathway team and United States Special Operations Command (USSOCOM) to gather innovative industry ideas. To inform future software development acquisitions, the DoD wants industry inputs and ideas to improve contracting for software solutions. These can be informed by industry best practices and examples of successful execution. The DoD seeks your feedback on effective and innovative ways for the DoD to better contract for software development solutions. The Department values your input on contracting techniques that enable the DoD to be a better partner. Background DoD has made a strong pivot over the last few years to transition to modern software development practices of Agile, Lean, and DevSecOps. These are now the default approaches to develop software in the DoD, as driven by software modernization strategies, acquisition and CIO leadership direction, statute, and policy. The Software Acquisition Pathway, governed by DoDI 5000.87, enables the DoD to acquire custom software capabilities under the Adaptive Acquisition Framework. The DoD is also moving to better leverage “software factory” enterprise platforms and services allowing programs to focus on key functionality instead of duplicating the full tech stack. This requires transforming many of the DoD’s processes, policies, and culture to embrace the new paradigm. As industry has led the way, the DoD wants to learn how we can effectively transform our contracting strategies and vehicles to adopt these software practices and grow our National Security Innovation Base. Feedback gained through this Innovation Challenge RFI will be considered by the Department for developing contracting guidance and shaping key future software acquisitions. Requested Feedback The DoD seeks written feedback on potential contracting approaches for Agile software development teams and DevSecOps (DSO)-as-a-Service solutions. Dependent on industry feedback to this RFI, the DoD may follow-up with future engagement opportunities; to include question and answer sessions, one-on-one engagements, roundtables and/or requests for additional written information. The DoD encourages respondents to share their innovative ideas on effective contract structures that could be used by the Department to: Select contract types that are best suited for software development and DSO-as-a-Service activities Enable flexible and responsive Agile software development and DSO-as-a-Service contracts Incentivize high-quality, user-centric, and timely software deliveries Successfully measure contract performance Responses: Responses are due by 1600 CDT on 15 August 2022 to enable the Government to organize findings. Additional Discussions: The Government may choose to reach out to select respondents for additional discussions as a result of this RFI. Such discussions would only be used to obtain additional information as part of market research. Questions: Questions regarding this RFI shall be submitted in writing by email. The Government does not guarantee that questions received after 24 June 2022 will be answered. Please see attached PDF for additional details, submission instructions, and Points of Contact. Disclaimer This RFI is issued solely for information and planning purposes. This RFI is not a solicitation and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Responses will not be considered as proposals, nor will any award be made as a result of this request. Federal Acquisition Regulation (FAR) clause 52.215-3, “Request for Information or Solicitation for Planning Purposes”, is incorporated by reference. The Government does not intend to reimburse respondents for any costs associated with the submissions of their responses to this RFI; respondents to this RFI are solely responsible for all expenses associated with responding. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in response to this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. Responses from this RFI will be used to formatively shape broad DoD guidance for acquiring software solutions. Response content may be aggregated and anonymously published into summary documentation to facilitate such guidance. Any publications resulting from this RFI will be non-attributional, and RFI respondents’ consent for their responses to be used for such purposes.