Developing a Product Line Acquisition Strategy for a DoD Organization


Book Description

Abstract: "Industrial experience clearly demonstrates that a product line approach for software-intensive systems can save money and result in faster time to field higher quality systems. Many within the DoD recognize the benefits of product lines, but also recognize that there are significant challenges to adopting such an approach. One of several challenges that confront a DoD organization is developing and implementing a suitable acquisition strategy. To be effective, the DoD organization must balance its product line aspirations against the ability of potential contractors (having varying levels of product line experience and 'hands-on' knowledge of related legacy systems) to meet its needs. It also must balance them against the requirements of DoD policy and regulatory documents that govern the entire acquisition process. Several key questions are: 'What does developing an acquisition strategy involve?' and 'How does a DoD organization develop an effective strategy for acquiring a software product line?' This case study focuses on a recent effort that shows how one DoD organization answered these questions. This technical note describes the approach a DoD organization used to develop alternative acquisition strategies and analyzes the pros and cons of each. It summarizes the acquisition context. It also presents a number of alternative product line acquisition strategies, a method for comparing the merits of each approach, and some risk reduction measures. Although this case study purposely disguises the actual organization and product line, it reflects the considerations involved in developing a software product line acquisition strategy."




The DoD Acquisition Environment and Software Product Lines


Book Description

Abstract: "Industrial experience clearly demonstrates that a product line approach for software-intensive systems can save money and result in faster time to field higher quality systems. Many within the DoD recognize the benefits of product lines, but also recognize that there are significant challenges to adopting this approach. Many of these challenges stem from the fact that the DoD is in the business of acquiring systems rather than developing them. A key question is how can a software product line approach best be accommodated within the current DoD acquisition environment? In order to answer this question, this technical note examines three key DoD acquisition policies and regulations and their implications for launching a product line approach. This includes examining the DoD acquisition management process and DoD guidance on acquisition strategies that set the context for software product line acquisition planning. Sources of confusing guidance on developing acquisition strategies are examined and terms are defined to clarify what is meant by a product line acquisition strategy. The need for strategic acquisition planning in launching a product line is discussed and insight is provided on how it differs from traditional acquisition planning."




The DoD Acquisition Environment and Software Product Lines


Book Description

Abstract: "Industrial experience clearly demonstrates that a product line approach for software-intensive systems can save money and result in faster time to field higher quality systems. Many within the DoD recognize the benefits of product lines, but also recognize that there are significant challenges to adopting this approach. Many of these challenges stem from the fact that the DoD is in the business of acquiring systems rather than developing them. A key question is how can a software product line approach best be accommodated within the current DoD acquisition environment? In order to answer this question, this technical note examines three key DoD acquisition policies and regulations and their implications for launching a product line approach. This includes examining the DoD acquisition management process and DoD guidance on acquisition strategies that set the context for software product line acquisition planning. Sources of confusing guidance on developing acquisition strategies are examined and terms are defined to clarify what is meant by a product line acquisition strategy. The need for strategic acquisition planning in launching a product line is discussed and insight is provided on how it differs from traditional acquisition planning."




Creating a DoD Strategic Acquisition Platform


Book Description

The U.S. must be prepared to respond to a broad set of national security missions, both at home and abroad. Yet many deficiencies exist in defense capabilities need to support these missions -- systems are aging and technologies are becoming obsolete. Fixing the DoD acquisition process is a critical national security issue -- requiring the attention of the Sec. of Defense. DoD needs a strategic acquisition platform to guide the process of equipping its forces with the right materiel to support mission needs in an expeditious, cost-effective manner. The incoming leadership must address this concern among its top priorities, as the nation¿s military prowess depends on it. This report offers recommendations for rebuilding the defense acquisition process.




Product Line Acquisition in a DoD Organization


Book Description

Abstract: "In the Department of Defense (DoD) acquisition environment, many organizations have not seriously considered adopting a product line approach or are reluctant to because it is not a well-understood acquisition paradigm. Nonetheless, a compelling case can be made for adopting a product line approach because it addresses a problem facing many program managers today -- how to cost-effectively acquire, develop, and maintain a set of related software-intensive systems and how to respond to the needs of greater product agility in the face of the current DoD transformation. This technical note chronicles the decisions a program manager might face in considering the adoption of a product line approach. The report uses a hypothetical acquisition to focus on why an acquisition organization should consider adopting a product line approach -- instead of the traditional stovepipe approach -- when acquiring a number of software-intensive systems that have a lot in common. The technical note provides a program manager with insight into the many benefits of adopting a product line approach and examines alternative acquisition approaches for acquiring a product line capability."




Defense acquisition : improved program outcomes are possible


Book Description

We are pleased to be here today to discuss issues facing the Department of Defense (DOD) in its acquisition of weapon systems, related spare parts, and other goods and services. In response to the many changes that have been witnessed in the defense acquisition environment over the last few years, DOD has begun broad-based changes to its acquisition and contracting processes. However, weapon programs continue to have questionable requirements; unrealistic cost, schedule, and performance estimates; and strategies that begin production before adequate testing has been completed. This discussion of acquisition issues is well-timed, as DOD implements plans to increase its procurement budget to $60 billion in fiscal year 2001-a 40-percent increase over last fiscal year's budget. My testimony focuses on a different approach to improving weapon acquisition outcomes based on best commercial practices and an understanding of the acquisition culture. My testimony also includes some observations on (1) DOD'S management of its acquisition workforce and organization, (2) DOD'S experience with commercial pricing of spare parts, (3) the effectiveness of DOD'S mentor-protege pilot program, and (4) federal agencies' use of multiple award task- and delivery-order contracts.




An Acquisition Strategy, Process, and Organization for Innovative Systems


Book Description

There is a widespread belief that in the future some military threats might be quite different from those of the recent past-requiring a response by innovative system and employment concepts. Our present weapon-system acquisition process was designed for a different environment than the one that exists today and seems ill suited to meet demands posed by the apparent expansion of unconventional and asymmetric threats. In response to this new environment, recent calls for reform have placed special emphasis on the need for an acquisition process that is better able to satisfy the need for truly innovative system concepts. We outline a suggested acquisition strategy, process, and organization that would operate in conjunction with the present process, and that is specially designed for effective development of novel and more risky system concepts. We describe this strategy in enough detail to identify its key elements, suggesting how it could work and why we believe it would provide needed capabilities not present in our current acquisition process.




Acquisition Reform


Book Description

Pursuant to a congressional request, GAO reviewed the Department of Defense's (DOD) efforts to establish a new management structure and make changes to its major weapons acquisition systems, focusing on: (1) DOD progress in implementing a presidential advisory commission's recommendations to establish clear accountability over its weapons acquisitions and provide unambiguous authority over its acquisition programs; and (2) related DOD initiatives that address the government's and defense industry's relationship. GAO found that: (1) DOD established clear channels of command by reducing the number of management levels in its acquisition system and creating an Under Secretary of Defense for Acquisition position; (2) the newly established acquisition structure streamlined and centralized acquisition processes and reduced some formal reporting requirements; (3) DOD began a process for projecting its future spending by using more realistic funding assumptions; (4) DOD did not fully implement its acquisition work-force reduction plans; (5) DOD began implementing the Defense Acquisition Workforce Improvement Act, which is intended to improve the quality of the acquisition work force; (6) the change in national security threats reduces the DOD justification for concurrent development and production of major weapons systems and supports the advisory commission's acquisition strategy that favors increased prototype usage; (7) although DOD made significant changes to its acquisition management structure and system, the success of those changes will depend on strong leadership, strengthened internal controls, and the free-flow of information; and (8) DOD implemented such initiatives to improve its relationship with the defense industry as integrating a finance plan, developing a contractor risk assessment guide, establishing defense enterprise programs, using commercial products, and consolidating certain acquisition activities.




Strategies for Acquisition Agility


Book Description

The authors analyze various approaches to speed acquisition of military capabilities and keep pace with evolving threats, assess these approaches' suitability for different conditions and acquisition types, and identify implementation issues.




Critical Code


Book Description

Critical Code contemplates Department of Defense (DoD) needs and priorities for software research and suggests a research agenda and related actions. Building on two prior booksâ€"Summary of a Workshop on Software Intensive Systems and Uncertainty at Scale and Preliminary Observations on DoD Software Research Needs and Prioritiesâ€"the present volume assesses the nature of the national investment in software research and, in particular, considers ways to revitalize the knowledge base needed to design, produce, and employ software-intensive systems for tomorrow's defense needs. Critical Code discusses four sets of questions: To what extent is software capability significant for the DoD? Is it becoming more or less significant and strategic in systems development? Will the advances in software producibility needed by the DoD emerge unaided from industry at a pace sufficient to meet evolving defense requirements? What are the opportunities for the DoD to make more effective use of emerging technology to improve software capability and software producibility? In which technology areas should the DoD invest in research to advance defense software capability and producibility?