TPMM
ttaphases.png

The Technology Transition Agreement (TTA) process helps ensure that technologies are carefully managed and delivered with increased capabilities within time and budget constraints.

Decision Point helps facilitate effective communications between the Acquisition center and the technology base by:

  • Developing Alignment Mechanisms such as the Technology Transition Agreement (TTA) and a (tech-level) Technology Development Strategy (TDS).
  • Guiding creation of documents used to exchange Interest, Intent and Commitment at significant event milestones throughout the Acquisition Lifecycle leading to transition at MS-B.

Additionally, Decision Point promotes systems engineering rigor by establishing a TRL based stage-gate process for planning, developing, and assessing technology maturity in the S&T organization. Use of Decision Point provides confidence to the Acquisition center that the User requirements are being met in the technology product.

Depending on TRL level of the project, it may fall under one of three categories:

  • 6.1: Basic research, typically associated with technology readiness level (TRL) 1 and 2, in which new scientific phenomena are sought in an effort to discover and advance fundamental knowledge in fields important to national defense. Such research is generally broad in nature, and because of its low TRL, can be considered inherently “high risk.”
  • 6.2: Applied research (also called exploratory development), typically associated with TRL 3 and 4, in which technology is developed based on a newly discovered scientific phenomena, or by the application of scientific phenomena in a totally different manner than currently applied.
  • 6.3: Advanced technology development, typically associated with TRL 5 and 6, in which multiple technologies (often from cross disciplines) are integrated and demonstrated to enable the development of a new military capability to satisfy a military need.

Each TTA is broken down into three stages: Interest, Intent, and Commitment, which occur in Phase 3, Phase 4, and Phase 6, respectively.

Interest Stage

The Interest Stage of the TTA occurs after the technologist has completed the Proof of Concept Phase. Additionally, the S&T will have completed the Initial Technology Development Strategy (TDS) outlining the plans of the Project.

In the Interest Stage, the primary activities are to:

  1. Provide the S&T Project Name
  2. Determine Requirements Officer and Performance Requirements
  3. Define Interface Control Drawing
  4. Identify Target Acquisition Program
  5. Obtain signed approval of the TTA

Intent Stage

The Intent Stage of the TTA occurs upon completion of the Refinement Phase and upon validation of the concept against high-level user requirements. At this point, an Initial Cost Estimate should be complete based on analysis of the requirements.

In the Intent stage, the PEO/PM indicates their intent to receive the project for commencement of the Acquisition Phase at a later date, as well as to initiate POM funding if required.

Commitment Stage

The Commitment stage of the TTA is the highest level of agreement and includes a firm commitment by all stakeholders to transition the technology.
At this point, the user concludes development of a Capability Development Document (CDD) and successfully demonstrates the technology in a relevant environment. The PEO/PM will complete the needed documentation required for Initial Acquisition, and the POM will reflect the cost estimate of the technology development and transition.

When developing the technology, it is important to identify quantifiable criteria that will be used to measure whether the technology/product development effort is proceeding appropriately. An analysis of the technology or product against these key technical measures of readiness should be performed after each stage of TTA development to determine readiness to transition.

Evaluations against the Project’s Key Technical Measures of Readiness can assume many forms. Here are two examples of evaluations:

Key Indicators Description TTA Version
1 2 3
Performance Requirements Definitive, complete, measurable performance & physical attributes parameters to be tracked Not Likely Yes Yes
Performance Thresholds Minimum acceptable performance threshold has been identified Not Likely Yes Yes
Performance
Demonstrated
Current performance of the technology / product Maybe (Simulated) Yes - Lab Yes - Relevant Environ
Test Planning Conditions under which technology / product will be tested / demonstrated prior to delivery to acquisition Not Likely Yes - Lab Yes - Relevant Environ
Manufacturability/
Producibility
The requirements for manufacturing and / or production have been identified and assessed Not Likely Maybe Yes
Operational
Environment
The environment in which the technology will operate has been defined Maybe Yes Yes
TRL at Transition Estimate of the transition TRL coordinated with the program office Maybe Yes Yes


TTA Stage Key Indicators
Performance
Requirements
Performance
Thresholds
Performance
Demonstrated
Test
Planning
Manufacturability /
Producibility
Relevant / Operational
Environment
TRL at
Transition
1 - Interest ? ? ?
2 - Intent X X X LAB ? RE X
3 - Commitment X X X RE X OE X

LEGEND
UNLIKELY
POSSIBLE
DEFINATE

Of course, as the Project progresses through the stages of TTA development and Technological Maturity, the data used for evaluation will change. Consistent evaluation will provide a clear picture of where the development gaps are, as well as a clear picture of how the project is progressing.

In the process of developing a TTA through the three stages of Interest, Intent, and Commitment various parties will contribute information to the document.

Requirements Organization

The requirements organization will be responsible for identifying the requirements officer and the governing source of the capability requirement. This can be any of the following:

  1. Initial Capabilities Document (ICD)
  2. Capabilities Development Document (CDD)
  3. Capabilities Production Document (CPD)
  4. Other official reference documenting Capability Need.

Should a formal requirements document not exist, the appropriate Future Operational Capability or Force Level Capability should be referenced and the plan to develop a requirements document should be included.

Acquisition Program Office

The Acquisition Program Office will identify personnel responsible for day to day program/project management, along with the following documents/information:

  1. Target Acquisition Program – Brief description of the program to receive the technology/product including objectives and projected operational capability dates.
  2. Acquisition Program Technology Need – Identification of the technology needs/benefits related to the requirements.
  3. Integration Strategy – Description of the process for integrating the technology/product into the acquisition program.
  4. Transition FY
  5. Statement conveying the level of interest, intent, or commitment.

Sustainment Organization

In addition to identifying a Sustainment Officer responsible for identifying resourcing and executing sustainment after transition, the Sustainment Organization will provide Signed and Dated copies of all stages of the Technology Transition Agreement to commit participating organizations to the plan outlined in the agreement.