RAH-66 Comanche Comanche Process Comanche Process Improvement Improvement Vision and Initiatives Vision and Initiatives 26 JAN 04 26 JAN 04 Mr. Richard Tyler Dr. Sam Cooke Ms. Kathleen Leonard Mr. Scott Reed
Contents Contents • Purpose – To describe the Comanche Process Improvement (PI) vision, activities and status • Outline – Comanche Program Overview – Process Improvement Approach & Schedule – Process Improvement Status and Path Ahead – Summary 26 JAN 04 2
System Description System Description Main Rotor T802 Engines ~4.5M SLOC Fire Composite Tail Drive Control Shaft Radar Advanced Cockpit Fantail Rotor IR Ribbon Exhaust FLIR External Advanced Target Acquisition Weapons System Provision Internal Armaments Gun Advanced Composite OTTIS Airframe Advanced Digital Avionics 26 JAN 04 3
Comanche Software Source Lines of Code Comanche Software Source Lines of Code (SLOCs SLOCs ) ) ( AIR VEHICLE SLOC COMPARISON 6.2M Category SLOC (K) SLOC/K 2400 Air Vehicle 2739 2000 Training 1182 1600 Support 107 1200 Integration 130 800 400 TOTAL 4158 0 OH58D AH-64 A MH-60K AH-64D RAH-66 C-17 F-22 JSF Armament 138K Airframe (A/F) Flight Control System (FCS) 40K 145K Air Vehicle Training 1,182K Mission Equipment Package (MEP) 4158K 2416K 1,451K SLOC reused Support from LBA, F-22 & 107K Integration Others 130K Data current as JUN 02 Data current as JUN 02 Data from CARD Data from CARD 26 JAN 04 4
Comanche Software Growth Comanche Software Growth Cumulative Software Cumulative Software SLOC Feb 09 4,500,000 +656K SLOC 4,000,000 Apr 08 Jun 07 +87K SLOC +685K SLOC 3,500,000 Jun 06 3,000,000 TOTAL +960K SLOC ISF 2,500,000 ITS GSE Mar 05 FCS 2,000,000 +499K SLOC Jan 05 AF +189K SLOC Aug 04 MEP 1,500,000 Apr 04 +13K SLOC +72K SLOC May 02 1,000,000 500,000 0 DROP 10 DROP 10.20 DROP 10.30 DROP 11 DROP 12 DROP 13 DROP 14 DROP 14.5 DROP 15 1,088,840 1,160,809 1,173,885 1,361,728 1,860,962 2,820,917 3,506,330 3,593,380 4,249,334 TOTAL Data current as JUN 02 Data current as JUN 02 Data from CARD Data from CARD 26 JAN 04 5
Comanche Program Schedule Comanche Program Schedule FY 03 FY 04 FY 05 FY 06 FY 07 FY 08 FY 09 FY 10 FY 11 FY 12 FY 03 FY 04 FY 05 FY 06 FY 07 FY 08 FY 09 FY 10 FY 11 FY 12 IOC Block II LL IPR ITC LRIP DAB FUE IDR MS III MS IIIA Block III IDR Block I Development Developmental Testing Aircraft • Flight Testing A/C 3-6 • Mission Equipment Package Intg • Maintained By Contractor A/C 7 Aircraft 7 Available Aircraft 7 Available LUT for DT or OT for DT or OT Training Aircraft • User Test & Training • Limited User Test A/C 8-11 • IOTE Training • Maintained By Contractor IOTE Block I Aircraft Simulators And Training Devices LRIP 2 (23) LRIP 3 (35) LRIP 1 (15) Block II Development Development Test FRP 1 (48) Blk II OT FRP 2 Block III Development Development Test Blk III OT Level Initial Process Continuous Process Improvement Improvement 3 26 JAN 04 6
Process Improvement History Process Improvement History • 2002: In response to various independent program assessments, Comanche PM launches a process improvement initiative focusing on acquisition processes Independent Assessments – Identified lack of Systems Engineering as a program weakness – Identified acquisition process as a target for improvement – Recommended review of contractor processes by Software Engineering Institute (SEI) • 2003: ASA (ALT) launches the Army Strategic Software Improvement Program • 2003: OSD improvement initiatives mandated by the Bob Stump National Defense Authorization Act for Fiscal Year 2003, Sec. 804. for Improvement of Software Acquisition Processes Our challenge: Find a way to to improve acquisition processes, meet requirements and minimize impact to the Comanche PMs while answering the mail at Army, OSD and Comanche (internal) levels 26 JAN 04 7
How Comanche PI Fits into the How Comanche PI Fits into the Process Improvement Environment Process Improvement Environment Comanche PI Section 804 ASSIP • All Product • All DoD Programs • All Army Programs Software Offices • Focus on Software • Focus on Software • Focus on System • Policy • Benchmark for • Model Based Improvement Improvement • Goal SA-CMM Level 3 ASSIP Complies ASSIP Complies Comanche Comanche with Section 804 Complies with with Section 804 Complies with ASSIP ASSIP 26 JAN 04 8
Why Are We Doing This? Why Are We Doing This? Improving Comanche Acquisition Processes will: • Instill Discipline Into Acquisition Processes • Capture Comanche Best Practice Expertise Before It’s Gone • Enhance Internal And External Communication • Maximize Efficient Use Of Constrained Resources • Expand The Scope Of Risk Management Efforts • Achieve Predictable Project Cost And Schedules • Reduce Project Cost And Schedule Variances • Comply With Section 804 Bottom Line Bottom Line Process Improvement Makes Process Improvement Makes Good Business Sense Good Business Sense 26 JAN 04 9
Comanche Removes Steps from the Comanche Removes Steps from the Traditional Strategy Traditional Strategy Organizational Organizational Level Level Level Level Level Process Assets are Level Process Assets are Level 1 2 & 3 3 1 3 used as a 2 used as a 2 Force Multiplier Gaps Force Multiplier Gaps PI Team Identifies Step 1 Each Project PI Team Organization Step 2 Organization Organization Develops Each Project Analyzes Develops Pilot Projects Assessed Closes Gaps From Scratch Assessed Validate Re-Analyzes Status Existing Existing Assets Assets Project Standard Project Standard Level 2 Acquisition Best Policies Level 2 Acquisition Policies Practices Organization Practices Organization Processes Policies Policies Process Asset Processes Policies Policies Process Asset Each Project Step 3 Procedures Practices Practices Procedures Library Practices Practices Library Deploy Across Tailors Processes Processes Processes Processes Procedures Organization; Procedures Procedures Procedures Project-Unique Project-Unique Each Project Assets are not Assets are not Organization Tailors Developed Developed Maintains Up- Front Up- Front 26 JAN 04 10
Comanche Process Improvement Comanche Process Improvement Strategy Details Strategy Details • The Systems Engineering Division owns process improvement • SEI Capability Maturity Models (CMM) provide framework for Process Improvement – Software Acquisition CMM (SA-CMM) Level 2 & 3 key process areas provide organizational framework – Relevant Systems Engineering CMM (SE-CMM) practices and existing Comanche practices are mapped into SA-CMM framework key process areas • Comanche Process Improvement is a “Do-It-Yourself” Effort – Comanche Personnel are involved in every step – Software Engineering Institute (SEI) and AMRDEC Software Engineering Directorate (SED) provide consulting services – ASSIP benchmark data/recommendations are integrated into the Comanche process improvement effort 26 JAN 04 11
Comanche PI Vision and Authority Comanche PI Vision and Authority The Comanche PMO will base their The Comanche PMO will base their … process improvement effort on the Capability … process improvement effort on the Capability Maturity Model Integration (CMMI -Systems Maturity Model Integration (CMMI -Systems Engineering) and the Software Acquisition (SA- Engineering) and the Software Acquisition (SA- CMM) process improvement frameworks … CMM) process improvement frameworks … … we are going to shoot for a Level III … we are going to shoot for a Level III assessment by December 2004. assessment by December 2004. Strategic Acquisition Process Improvement Plan Strategic Acquisition Process Improvement Plan Signed by COL Michael Cantor PM Comanche Signed by COL Michael Cantor PM Comanche 28 AUG 03 28 AUG 03 26 JAN 04 12
Comanche Operational Approach Comanche Operational Approach to Acquisition Improvement to Acquisition Improvement Establish sponsorship Communicate results Conduct process Establish vision Pilot the new data gathering and scope processes Communicate results Communicate results Communicate results Rollout the new Build a model Develop a plan processes of the process Communicate results Communicate results Communicate results Perform gap Develop the Conduct mini Analysis new processes evaluation Communicate results Communicate results Communicate results Shaded Tasks with a Check Mark are Complete, and without are In-Progress Clear Tasks are not begun 26 JAN 04 13
Recommend
More recommend
