Technology Program Management Model

 

<Home>

<Transition Paradigm> <What's New?> <FAQs> <Contact Us>  

Frequently Asked Questions (FAQs)

 

What is the TPMM?
Is the TPMM a computer application?
What benefits does the TPMM provide?
How did TPMM get started?
What is a Stage-Gate process?
My program is different. Can the TPMM model be tailored to work for me?

Who can I contact for more information on TPMM?

 

What is the TPMM?

TPMM is a Technology Readiness Level (TRL)-based stage-gate process model that contains engineered criteria, tailorable to any given technology development program. It is a management model that focuses on the full activity set (e.g. programmatics, systems engineering, transition management, verification) that can be used by a technology program manager to manage their technical development program to transition to an Acquisition Customer. Every activity contributes to the technology product. The results of each activity are documented by one or more deliverables in any given phase - no superfluous activities.

The model infrastructure has been built such that it:

  • Defines each TRL as a phase (stage)
  • Establishes Exit criteria (gate) for each TRL
  • Reinforces System Engineering Principles
  • Aligns to Enterprise Development Process (DoD 5000)
  • Focuses on successful transitioning
  • Provides the criteria supporting Technology Transition Agreements 

 <TOP>

 

Is the TPMM a computer application?

Not yet. We are in the development phase of transferring that model criteria data set into a relational database which will then drive the further development of a computer application. These items are being developed and tested in cooperation with various S&T organizations at the enterprise level. With that said, the model itself is still a viable and validated tool that can and is being used to conduct TRAs, develop Technology Transition Agreements, develop Technology Development Strategies (TDS), and TDS to Acq Strategy roadmaps not to mention old fashion technology development and management (TRL roadmap), just to name a few. The database architecture coupled with the model taxonomy has become a very powerful tool and once the application can be realized it will be able to provide portfolio and enterprise level data in support of key technology decisions at all levels.

 <TOP>

 

What benefits does the TPMM provide?

TPMM benefits include:

  • Confidence in the estimation of the maturity (Technology Readiness Assessment results)
  • Establishes a common language set for TRL interpretation
  • Reduces risk of failure to transition by improving customer management:
    • Increases customer involvement early in the development process
    • Increases customer involvement throughout the development process
    • Increases customer support through better communication and standardization
    • Increases customer committment through Transistion Agreements at multiple phases
    • Increases customer credibility through improved documentation process
    • Point solutions for immediate needs :
      • Technology Program Reviews (TPR)
      • Internal Technology Readiness Assessments (TRA)
      • Technology Advancement Assessments (TAA)
      • Technology Transition Agreements (TTA)
      • Technology Development Strategies (TDS)
      • TDS to Acquisition Strategy Roadmaps
      • TRL Roadmaps
      • Audit Trails for compliance needs        
         

 <TOP>

 

How did TPMM get started?

TPMM was initially developed at the SMDC by the Tech Center director to assist Technology Developers in the management of their tech programs.  What he saw happening was that:

  • Transition was an afterthought
  • Technologist still tinkering with their technology when the Acq Program needed it
  • Tech Managers didn’t have clear goals established to know when they were finished
  • Or simply not knowing when technology was needed

TPMM attempted to alleviate these issues by the incorporation of Systems Engineering and Programmatic principles and practices with Transition Management in a stage-gated process for (TRL-based) maturity assessment.  The TPMM resolves to do the following:

  • Transition has to be part of the development process

  • Transition activities occur early in TRL phases

  • Incorporate Best Practice: - Technology Transition Agreement (TTA) :

    • Includes All stakeholders early in development process

    • Facilitates early transition management

    • Provides Accountability and Buy-In

 <TOP>

 

 What is a Stage-Gate process?

A Stage-Gate process is one in which the work is done in distinct phases. Each phase is a "Stage". During a Stage, money is allocated for that phase and work is performed. Each Stage has specific characteristics against which it is measured to determine if that phase has been completed. These characteristics include Deliverables, Funding Allocation, Metrics, and Goals (Exit Criteria). Once a phase is completed (Deliverables delivered, Funding spent, Goals met, Metrics satisfied), then a decision must be made whether to move forward with the program. This is the "Gate". Each Gate is a decision point for the program to move to the next stage and is typified by a program review. The TPMM gate is the Technology Program Review (TPR), which is comprised of two individual assessments. The first is a Technology Readiness Assessment (TRA) which determines whether the program has achieved a specific Readiness Level. The second is a Technology Advancement Assessment (TAA), which validates the planning function for the next phase. The outcome of the TAA is a decision to either a) Go to the next stage; b) Kill the program; c) Hold the program; or d) Recycle the program back into the current stage to satisfy some unsatisfied criteria. Once a decision to go forward to the next Stage has been made, funding must be allocated, deliverables defined, and Goals and Metrics specified for that Stage. Then the work for that Stage commences. The TPMM uses the TRL gates as the basis for each Stage of its Stage-Gate Process.

 <TOP>

 

My program is different. Can the TPMM model be tailored to work for me?

Absolutely. The steps involved in tailoring the TPMM have been drawn from the results of multiple successful pilot programs. These steps are iterated below:

  1. Understand the Program
  2. Capture "As Is" Current Behavior
  3. Map-to and Tailor the TPMM. This eliminates those TPMM functions that clearly do not pertain to the program. (e.g. if the program has no software, the software-specific functions would be eliminated from the criteria set.
  4. Establish the tailored criteria set for the specific Technology Program
  5. Status the criteria set
  6. Conduct a Gap Analysis
  7. Populate Exit Criteria and Deliverables Table
  8. Conduct the Technology Program Review (for each phase)

 <TOP>

 

Who can I contact for more information on TPMM?

For more information, please fill out this short form or contact either:

Mr. Jeff Craver
Defense Acquisition University
Southern Campus

E-mail: Jeffrey.Craver@DAU.mil
Voice: 256-895-3453

           or

U.S. Army Space & Missile Defense Command Public Affairs Office
Huntsville, Ala. 35807-3801

Voice: 256-955-3887

           or

Mr. Michael Ellis
DMD, LLC
360B Quality Circle
Huntsville, AL 35806
E-mail: Mike.Ellis@DMDGroupInc.com

 

 <TOP>