In fact, the NDS encourages the use of prototyping prior to defining requirements. Unlike formal acquisition programs, however, prototyping is often not bound by traditional Joint or Military Service requirements processes. In addition, for urgent requirements, warfighters can use their Components’ urgent needs processes or work through the Joint Staff’s urgent needs process in which Combatant Commands, the Chairman of the Joint Chiefs of Staff, or the Vice Chairman of the Joint Chiefs of Staff can submit Joint Urgent Operational Needs Statements and Joint Emergent Operational Needs Statements. The Joint Requirements Oversight Council-led Capability Gap Assessment.įormal requirements also include capability gaps that have been validated by Components or the Joint Staff and documented by Joint or Military Services’ requirements processes, such as Integrated Priority Lists (IPL) and Initial Capability Documents.The USD(R&E)’s Road to Dominance modernization priorities.Examples include requirements listed in approved Joint Capabilities Integration and Development System documents and strategic needs recorded in the following documents: Certainly, the most obvious are validated requirements that are documented through formal processes. Military capability gaps can be obtained from numerous sources. However, for projects seeking to directly support an operational mission, the purposes will come in the form of an identified existing or emerging military capability gap. For projects in which the objective is to push the boundaries of technology, the purpose could come in the form of a statement of intent by the researcher or an emerging need not yet formally recognized by the Department. Prototyping should start with a clear understanding of why the prototype is being developed.
Reference Source: DoD Prototyping Handbook, Nov 2019 Identifying Military Capability Gaps for Prototyping Projects CAEs will ensure the approved requirement document is available in the Knowledge Management and Decision Support system. Reference Source: DoDI 5000.80, Paragraph 4.1 Approval authorities for each capability requirement will be delegated to a level that promotes rapid action. Reference Source: DoDI 5000.80, Paragraph 1.2.fĮach DoD Component will develop a streamlined process that results in a succinct requirement document no later than 6 months from the time the operational needs process is initiated.
#Prototype 3 requirements full
This process will result in an approved requirement and a DA signed acquisition decision memorandum (ADM) that validates the rationale for using the MTA pathway and identifies the full funding required. DoD Components will develop a merit-based process for the consideration of innovative technologies and new capabilities to meet needs communicated by the Joint Chiefs of Staff and the Combatant Commanders.
Reference Source: DoDI 5000.80, Paragraph 3.1.a
0 kommentar(er)
