Breakthroughs in Applying Systems Engineering to Technology DevelopmentforInternational Council on Systems Engineering (INCOSE)Systems Engineering Conference in DC (SEDC) Ms. Melanie Klinner US Army Space and Missile Defense Command/Army Forces Strategic CommandMr. Jeffrey Craver Defense Acquisition UniversityMr. Mike EllisSenior Systems Engineer(Formerly with Intrepid)
Describe the problem space of managing the maturation of technology for transition from the perspective of the Program Manager, User, and the Technologist
Provide an overview of the Technology Program Management Model (TPMM) solution set in terms of Processes, Systems Engineering, and Transition Management
Describe the Breakthrough in terms of the Systems Engineering Module (SEM)that provides online implementation of TPMM
Describe how the SEM exists within an S&T Enterprise and for the Management of Technology Programs/Portfolio’s/Project’s
Describe how the DTRA TPMM Project has applied the model to improve current processes and add-value to the enterprise
Provide the Way Forward and the extension of the TPMM process into the Technology Development Domain from Basic Research to Program Management.
Fact: There are diminishing resources and belt tightening ongoing in DoD
Unfortunate Reality: Warfighter Needs are increasing at a significant rate in an attempt to outpace an Asymmetric Threat
Culture Change:Adopt a Stage-Gate Process in the Development Phase and Incorporate a Systems Engineering-Based Criteria Set for Assessing Technology Maturity
Requirements definition and plans for maturity advancement are not developed consistently or effectively.
No common set of tools and standards to gauge technology maturity.
Improve the rate for Transitioning of Technologies
Transition not always considered as a part of Technology Development
Limited Customer/User identification/involvement
Technology Development Challenges
Establish “a management methodology that balances the portfolio by Incorporating Discipline and Rigor through the use of clear, well-defined and Measurable Metrics!”
J. Heusmann DTRA-J9 (7 May 09)
If you “Push” long enough – they will come!
Your next chance for funding is 5 years down the road – stud!
Hey Buddy - I OWN The Requirements!
You don’t understand - This project is different from everyone else
Gotta be small,
and 99.99% reliable
My prime can do that!!
I NEED a REQUIRMENT (CDD)!
I Want it All!!
I Want it Cheap!
I Want it Now!
I am governed by DoD 5000.02
S&T does not require a process – I have been doing it for years
I’m governed by the JCIDS
You forgot about the “illities”!!!
Customer role is to integrate
The TPMM Collaboration was formed to improve and expand the TPMM methodology and jointly develop a tool-based process intent on reducing the risk to technology development.
DAU has recommended TPMM as a Systems Engineering best practice since 2008.
DTRA Process Improvement effort has been recognized by AT&L Value Engineering Achievement Award.
TPMM-based SharePoint Solution Application:
Systems Engineering Module (SEM)
NTD’s use of TPMM and the tenets of BBP have both potential and direct savings implications. Specifically, over $30 million has been saved both directly (~$8M) and through cost avoidance (~$22M) by the implementation of this best practice systems engineering method to develop and assess a technology’s maturity.
A TRL-Based, Stage Gate Model Designed for Technology Development and Transition
Functions Performed by TPMM
TTA = Technology Transition Agreement TDS = Technology Development Strategy
Systems Engineering principles are embodied in the activities and associated documentation in each stage of maturity development
Use Systems Engineering-Based (TPMM) process to change the culture:
Balance Technology Portfolio’s so that Priorities are aligned to Mission Strategy and Customer Needs are clearly identified and understood
ImproveProject Management Performancein the areas of requirements traceability, system engineering rigor, transition focus, maturity assessment, and in planning/execution/reporting
Exchange “informational” calendar-driven Project Technical Reviews with “decisional” event-driven Reviewswhere technical progress is examined "as-needed" in accordance with a Project’s Lifecycle Plan.
Increase Successful Transition of Technology byengaging Early Systems Engineering and aligning with Acquisition Authorities.
Promote consistency in technical interpretation of TRL Maturity levels throughout the DoD S&T Enterprise and with Program Managers.
Extend SE-Based practices for use in SBIR and IRAD Programsby tailoring the TPMM as applicable to that purpose.
Mr. Jeffrey CraverDefense Acquisition UniversitySouth Region
Huntsville, ALE-mail: Jeffrey.Craver@dau.mil
Ms. Melanie Klinner
TPMM Product Manager
Technical Center/Cyberspace Technology Division
Redstone Arsenal, Huntsville, AL
Mr. Mike EllisSystems Engineering Consultant
(Formerly with Intrepid)E-mail: Michael.Shannon.Ellis@gmail.com
Mr. Alan BarclayTPMM Industry Project Manager
Gaps NOT Covered
Gaps Partially Covered
Gaps Potentially Duplicated