§4211. Acquisition strategy — Inbound Citations

Citations to 10 U.S.C. § 4211 as a whole

• 10 U.S.C. § 3374(a)(3)(B)

  Go to provision →
  (B) were incurred to meet an anticipated contract delivery schedule or anticipated contract price targets of the Government under an acquisition strategy required under section 4211 of this title; and
• 10 U.S.C. § 4212(a)

  Go to provision →
  (a) The Secretary of Defense shall ensure that the initial acquisition strategy (required under section 4211 of this title) approved by the milestone decision authority and any subsequent revisions include the following:

  (1) A comprehensive approach for managing and mitigating risk (including technical, cost, and schedule risk) during each of the following periods or when determined appropriate by the milestone decision authority:

  (A) The period preceding engineering manufacturing development, or its equivalent.

  (B) The period preceding initial production.

  (C) The period preceding full-rate production.

  (2) An identification of the major sources of risk in each of the periods listed in paragraph (1) to improve programmatic decisionmaking and appropriately minimize and manage program concurrency.
• 10 U.S.C. § 4402(c)

  Go to provision →
  (c) In the case of a major defense acquisition program that uses a modular open system approach, the acquisition strategy required under section 4211 of this title shall—

  (1) clearly describe the modular open system approach to be used for the program;

  (2) differentiate between the major system platform and major system components being developed under the program, as well as major system components developed outside the program that will be integrated into the major defense acquisition program;

  (3) clearly describe the evolution of major system components that are anticipated to be added, removed, or replaced in subsequent increments;

  (4) identify additional major system components that may be added later in the life cycle of the major system platform;

  (5) clearly describe how intellectual property and related issues, such as technical data deliverables, that are necessary to support a modular open system approach, will be addressed; and

  (6) clearly describe the approach to systems integration and systems-level configuration management to ensure mission and information assurance.