战略与国际研究中心-Seven-Ways-to-Make-the-LRS_6页_303kb

LRS-B Program Success Summary

Core Content

The LRS-B (Long Range Strike-Bomber) program, led by Northrop Grumman, is a critical new defense initiative for the U.S. Air Force. It aims to develop a next-generation bomber that will enable global precision strike capabilities, operating in hostile environments with advanced technology. Despite the program's significance, it faces substantial challenges during its development and procurement phases.

Main Points

1. Clear and Stable Funding Projections

• The Air Force set a cost target of $550 million per aircraft (in 2010 dollars) for 100 units.
• However, the total program cost, including development and inflation, is expected to exceed $100 billion in then-year dollars.
• Key Action: Provide transparent and realistic cost estimates to manage expectations and avoid budget overruns.

2. Avoid Requirements Changes

• Requirements changes are a major cause of cost overruns.
• The Air Force should limit the number of people involved in requirements decisions to reduce the likelihood of changes.
• Key Strategy: Push new or altered requirements to a future version ("LRS-B 2.0") to avoid disrupting the current program.

3. Don't Oversell Technical Maturity

• While some technologies are mature, the integration of these systems presents significant risks.
• The program must manage these risks, especially in areas like apertures, electronic warfare, and software development.
• Key Insight: Technical maturity does not equate to full system readiness; integration challenges remain.

4. Focus on Systems Engineering

• Systems engineering is essential to identify how subsystems interact and generate new risks.
• It helps in designing detailed weight budgets and managing electronic integration.
• Key Practice: Conduct thorough systems engineering to mitigate risks early and reduce the need for costly fixes later.

5. Triage High-Risk Technologies

• Certain technologies, such as radar, electronic warfare, and software, pose significant risks.
• The Air Force has already initiated risk reduction efforts for apertures and is aware of potential issues with these subsystems.
• Key Approach: Proactively identify and manage high-risk technologies to prevent unforeseen problems.

6. Prepare for Testing Failures

• Testing is crucial to uncover performance issues and design flaws.
• Some failures are expected and can be addressed, while others may reveal previously unknown problems.
• Key Principle: Build in sufficient margin in the schedule and budget to handle testing-related issues and ensure flexibility.

7. Avoid Excessive Concurrency

• Excessive overlap between development and production can lead to costly retrofits.
• Production should begin only after development is sufficiently advanced to minimize risks.
• Key Balance: Ensure that the first production lots are used for operational testing to maintain realism and reduce surprises.

Key Information

• Program Status: LRS-B is the only new manned combat aircraft currently in development.
• Cost Estimate: The Air Force estimates $21.4 billion for engineering and manufacturing development, and $51.1 billion for procurement of 100 aircraft (in 2010 dollars), with total costs likely exceeding $100 billion when including inflation and development costs.
• Technological Challenges: Integration of mature technologies into a new airframe presents significant risks.
• Stakeholders: The program's success depends on coordinated efforts from the Air Force, Northrop Grumman, and Congress.
• Testing Importance: Testing is a necessary and valuable process that helps identify and resolve issues before operational deployment.

Conclusion

The LRS-B program has the potential to significantly enhance the U.S. Air Force's global strike capabilities, but it must be managed with care to avoid cost overruns, technical setbacks, and schedule delays. By following these seven strategies—clear funding, stable requirements, realistic technical maturity assessments, robust systems engineering, triaging high-risk technologies, preparing for testing failures, and avoiding excessive concurrency—the program can be more likely to succeed in the long term.