Competitive Prototyping Overview1 (11 pages)

Previewing pages 1, 2, 3, 4 of 11 page document View the full content.
View Full Document

Competitive Prototyping Overview1



Previewing pages 1, 2, 3, 4 of actual document.

View the full content.
View Full Document
View Full Document

16 views

Unformatted text preview:

Competitive Prototyping Challenges for DoD and Industry Paul Croll AMND Fellow May 28 2008 01 14 19 07 50 AM 6851 06 Teamwork 2006 1 What is it Why should I care Competitive Prototyping CP is an approach to competition where two or more competing teams develop prototypes during the early stages of defense acquisition programs Memo released by the Honorable Mr John Young Under Secretary of Defense for Acquisition Technology and Logistics OUSD AT L on September 19 2007 Directed the military services and agencies to formulate all pending and future programs with acquisition strategies and funding that provide for two or more competing teams producing prototypes through Milestone MS B Focus is on major system acquisitions and key system elements Policy expected to be issued in late summer 2008 Policy will impact how the largest systems are acquired by the Government with an increased occurrence of prototyping higher risk elements of a system before the procurement 01 14 19 07 50 AM 6851 06 Teamwork 2006 2 The Honorable Mr John Young s Memo 01 14 19 07 50 AM 6851 06 Teamwork 2006 3 When will the prototyping be done DoD 5000 Life Cycle Competitive Prototyping performed here Graphic from Defense Acquisition Guidebook 01 14 19 07 50 AM 6851 06 Teamwork 2006 4 Expected Benefits from Mr Young s memo Primary benefits Avoid cost overruns Reduce technical risks Validate system designs Evaluate manufacturing processes Reduce time to fielding Secondary benefits Increasing and strengthening the interaction of government and industry management teams Develop and enhance systems engineering capabilities Retain people with critical engineering skills Attract young talent to the field of science and engineering 01 14 19 07 50 AM 6851 06 Teamwork 2006 5 Industry Feedback Workshop held 4 28 08 to solicit industry feedback on Mr Young s memo Summary of feedback There is great value to both the government and prospective developers in Maturing all relevant technologies Substantially reducing overall risk Refining critical program paths Curtailing dependency on paper proposals It is important to achieve an early lock down of stable and predictable requirements volatility is apt to be a serious impediment to successful competitive prototyping Goals need to be clearly defined the rationale for industry investment e g IRAD should be visible and convincing The logistics of managing a Competitive Prototyping may stretch thin the government team potentially impeding open communications between the government and the contractors Competition may not be necessary during the pre Milestone B prototyping phase if technology levels going in are high enough Several industry topics stirred a great deal of conversation on the part of the DoD audience Innovation Recognition and Intellectual Property Protection Does Competitive Prototyping increase or reduce the product s time to market Presenters provided empirical examples on both sides of this issue 01 14 19 07 50 AM 6851 06 Teamwork 2006 6 Survey on CP Software Impacts Little consideration has been given regarding the impact on and of software Survey to be conducted to collect insights on software impacts with special attention to Requirements Risk Estimation Software quality attributes Survey results will be used by NDIA and OUSD AT L to provide guidance to both government and industry Expected to drive several specific tasks to create appropriate guidance 01 14 19 07 50 AM 6851 06 Teamwork 2006 7 Survey Sampling Criteria Success critical stakeholders SCS involved in such procurements including Acquirers military services and defense agencies with roles including Technical Contractual Oversight Competitors such as prime contractors Acquisition support organizations such as SETA contractors Acquisition process researchers such as academics and industry researchers Acquisition policymakers such as persons currently or formerly in these roles Respondents selected from the above entities should have direct experience with the software aspects of CP or CP like processes on large software intensive system SiS projects It is desirable that the software components of such projects be valued on the order of 50 million or larger The surveyed communities should comprise a diversity of domains for example C4ISR avionics integrated systems of systems etc to capture the broad nature of acquired systems 01 14 19 07 50 AM 6851 06 Teamwork 2006 8 Additional Survey Details Survey timeframe June and early July Survey structure Survey responses via e mail or Internet One hour phone call for follow up Survey being sponsored by NDIA Software Industry Experts Panel OUSD AT L Systems and Software Engineering Directorate Survey will be executed by University of Southern California Center for Systems and Software Engineering led by Dr Barry Boehm 01 14 19 07 50 AM 6851 06 Teamwork 2006 9 References The Honorable Mr John Young s September 19 2007 memo DOD Acquisition Czar Wants Prototyping Competition WashingtonTechnology 10 9 07 Pentagon s New Prototype Plan wired com 1 25 08 The Pentagon s New R D Rules Leave Many Questions Unanswe red The Avascent Group 1 22 08 01 14 19 07 50 AM 6851 06 Teamwork 2006 10 For More Information Paul R Croll Fellow Computer Sciences Corporation 10721 Combs Drive King George VA 22485 5824 Phone Fax e mail 1 540 644 6224 1 540 663 0276 pcroll csc com 01 14 19 07 50 AM 6851 06 Teamwork 2006 11


Access the best Study Guides, Lecture Notes and Practice Exams

Loading Unlocking...
Login

Join to view Competitive Prototyping Overview1 and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Competitive Prototyping Overview1 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?