Requirements The Acquisition Strategy example essay topic

General Considerations Each PM must develop and document an acquisition strategy to guide program execution from initiation through re procurement of systems, subsystems, components, spares, and services beyond the initial production contract award and during post-production support. The acquisition strategy evolves through an iterative process and becomes increasingly more definitive in describing the relationship of the essential elements of a program. A primary goal of the strategy is to minimize the time and cost it takes, consistent with common sense and sound business practices, to satisfy identified, validated needs, and to maximize affordability throughout a programs useful life cycle. In developing the acquisition strategy, the PM considers all policy guidance contained in the acquisition strategy portion on DoD 5000.2 R. In documenting the acquisition strategy, the PM provides a complete picture of the strategy for the decision makers who will be asked to coordinate on or approve the strategy document. The PM ensures the document satisfies the requirements of DoD 5000.2 R for the acquisition strategy to identify, address, describe, summarize, or otherwise document specific, major aspects or i sues of the program or strategy. The PM develops the acquisition strategy in preparation initiation, prior to the program initiation decision, and updates it prior to all major program decision points or whenever the approved acquisition strategy changes or as the system approach and program elements become better defined.

The PM engages the Working -Level Integrated Product Team (WIT) and Operational Test Agency (OTA) in the development of the acquisition strategy, and obtains concurrence of the Program Executive Officer and Component Acquisition Executive, as appropriate. The Milestone Decision Authority approves the acquisition strategy prior to the release of the formal solicitation. Approval usually precedes each decision point, except at program initiation, when the acquisition strategy usually is approved as part of the milestone decision review. REQUIREMENTS The acquisition strategy provides a summary description of the requirement the acquisition is intended to satisfy. The summary highlights aspects of the requirement (1) driven by family-of-systems or mission area requirements for interoperability, and (2) that reflect dependency on planned capability being achieved by other programs. The summary also states whether the requirement is structured to achieve full capability in time-phased increments or in a single step.

For time-phased requirements, define the block about to be undertaken, as well as subsequent blocks. The acquisition strategy identifies approved source documents constituting the authoritative definition of the requirement such as the Operational Requirements Document (ORD), Capstone Requirements Document (CRD), and Acquisition Program Baseline (APB). The acquisition strategy describes the status of source documents as of a specified date. It identifies any significant aspects of the requirement that are unsettled, and the impact this uncertainty has on the acquisition strategy. The acquisition strategy must be flexible enough to accommodate the requirements decisions ultimately made, either through providing alternative strategies when potential outcomes are limited and known, or through providing for a strategy update.