Acquisition Strategies in DoD Procurements :: essays research papers

General ConsiderationsEach PM must develop and document an skill scheme to guide platform execution from initiation through reprocurement of systems, subsystems, components, spares, and services beyond the initial production contract award and during post-production support. The acquisition scheme evolves through an iterative process and becomes increasingly more important in describing the relationship of the essential elements of a program. A primary destination of the dodge is to minimize the time and cost it takes, consistent with common star 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 wholly policy guidance contained in the acquisition strategy portion on DoD 5000.2R. In documenting the acquisition strategy, the PM provides a complete escort of the strategy for the termination makers who will be asked to coordinate on or approve the strategy document. The PM ensures the document satisfies the requisites of DoD 5000.2R for the acquisition strategy to identify, address, describe, summarize, or otherwise document specific, major aspects or isues 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 sanction acquisition strategy changes or as the system set near and program elements become better defined. The PM engages the Working Level integrated Product Team (WIPT) and Operational Test Agency (OTA) in the study of the acquisition strategy, and obtains concurrence of the Program Executive Officer and Component achievement 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 initiati on, when the acquisition strategy usually is approved as part of the milestone decision review.REQUIREMENTSThe acquisition strategy provides a synopsis 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 dependance 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).