The Decision Point is a high-fidelity activity model with recommended deliverable products expected in each phase. At the completion of each phase of development, Decision Point produces leads to documentation needed to progress to the next phase. These deliverables are sufficient to proceed to a Technology Project Gate Review

While the bulk of these products are produced by the S&T shop as the technology adapts itself to the capability needs, some of these products (User Requirements for instance) are provided to the S&T by the Acquisition center

It is important to note that the final phase deliverables are developed jointly where the Acquisition customer (and often the User) are actively participating in phase planning and providing guidance and resources needed to steer the demonstration of the technology capability into meeting User needs.

In the images used below to demonstrate the deliverables for each phase, the following legend indicates the responsible party for that deliverable:

CHECKLIST

The deliverables for the Discovery phase are:

Feasibility Study

After a literature search and the Feasibility Study, a Feasibility Study Paper (white paper) is prepared to document the results and to describe the effort. This study will include project objectives, mission requirements, functional requirements, candidate architectures and candidate concepts, basic principles involved, the Systems Engineering approach, the known or perceived need, and potential customers/sponsors.

Concept Formulation Analysis Plan

The Concept Formulation Analysis Plan (CFAP) identifies the process and funding for evaluating candidate technologies in the Formulation phase. It is developed at the conclusion of the Discovery Phase following the completion of the Feasibility Study. The CFAP provides a description of the technology and the potential user needs/benefits as well as a description of the concept formulation process that will be followed. Key areas for the CFAP to describe are how the potential concepts will be defined for the technology and how the associated practical military application will be determined. It includes the plan for; analysis and evaluation of feasible alternatives, for how the analysis will be accomplished, the conceptual formulation studies that will be considered and analyzed, the analytical tools that will be used for the assessment. If they exist currently, the key performance parameters and other criteria that will be used to select the preferred concept are identified. Other factors such as the costs, schedule, and risk for concept formulation and analysis effort will be identified as well as the organizations that should be participating or invited to participate.

CHECKLIST

The deliverables for the Formulation phase are:

Analysis of Technical Alternatives

The Analysis of Technical Alternatives is a JCIDS process and document and the Decision Point does not provide a template for one. And yet, the tools for accommodating supporting an AoA is very important to the ultimate transition of any technology. According to the Office of Aerospace Studies, the AoA is the focus of Concept and Technology Development Phase (CTDP). The AoA is designed to examine a broad spectrum of potential alternatives to the mission need described in the Mission Needs Statement. Logically, the S&T could be asked to support an AoA with technology candidates that address the specific gaps being filled. The objective of the AoA therefore is to: Refine alternatives, Refine criteria, Refine evaluation, Work to gain consensus, Reduce uncertainty, and choose an alternative technical approach.

Concept Formulation Analysis Report

A Concept Formulation Analysis is conducted to identify key technologies, perform alternative concept analysis, perform system and sub-system tradeoff studies, select the Best Feasible solution, determine the Estimated Technology Life Cycle Cost, the Technology Advancement Degree of Difficulty (TADD) index (preliminary risk), and to analyze the potential benefit over current technology. At the conclusion of this phase, the formulated concept is documented in a Concept Formulation Analysis Report (CFAR), which becomes the focus of the Technology Readiness Assessment (TRA).

Proof of Concept Plan

A Proof of Concept Plan is developed Following a successful TRA for TRL 2, which documents expected activities, processes, models and simulations, and other means of analysis needed to conduct a proof of selected concept for the required key technology(ies) as well as a schedule and cost estimate for the next phase.

CHECKLIST

The deliverables for the Proof of Concept phase are:

Proof of Concept Report

A Proof of Concept Report documents the active research and development, including results of analytical and laboratory studies, proof that provides physical validation and documentation that the key technologies work as envisioned and their capabilities support the user’s requirements. Key preliminary (draft) performance and technical parameters and specifications are also identified and documented.

Technology Development Strategy (TDS) Initial

The TDS is the primary planning document for technologies containing all of the important elements necessary to accomplish development of the technologies as applied to the customer(s) requirements. Even though the TDS is described at the Acquisition level, most science and technology enterprises recognize the elements of the TDS as residing in a Program/Project Plan. The important thing is that a Plan is developed, followed, and used to report Technology Project status. For that reason, it should contain basic Program Management Data, such as; Estimated/Budgeted/Actual Cost, Schedule, Performance Goals (Requirements), Risks Management Plan, Program Deliverables, and the Risk Management strategy.

Technology Transition Agreement (TTA) (Interest)

Technology Transition Agreement is intended to be a mechanism for a technology project to obtain interest from users/sponsors, where the ultimate goal is for them to identify clear intent to incorporate the technology into a fielded capability and finally to secure commitment from a Program Office to transition the technology. The TTA process of interest-to-intent-to-commitment will ensure stakeholders that technologies are carefully managed and are delivered to the customer not only within time and budget constraints, but also that they provide increased capabilities to meet the needs of the warfighter

User Operational Requirements

Operational Requirements typically belong to the User and define the operational concept and requirements that are to be achieved and is the basis for evaluating the readiness of resultant products and services to become operational. Operational Mission Requirements/Objectives may include information from mission needs statements, existing performance requirements, SOW, TRD, ORD, notional objectives, etc.

Breadboard Lab Validation Plan

The Breadboard Laboratory Validation Plan describes the effort for integration (and possible fabrication) of hardware in a laboratory "breadboard" setting or computer in the loop to validate not only that the technologies work together but also that their performance continues to support the expected concept outcome. During this phase, system requirements will be refined, initial performance metrics established, and the preliminary system engineering Form, Fit, and Function analysis will be better defined to achieve the end product design. Scaling documents and diagrams are undertaken and development of a scalable technology prototype(s) will be initiated. Integration studies are planned for and draft conceptual hardware and software designs are commissioned.

CHECKLIST

The deliverables for the Refinement phase are:

Breadboard Lab Validation Report

The Breadboard Lab Validation Report is a sort of After Action Review of the Breadboard Lab Validation Plan. However, this phase integrates the basic key technology components to determine if they will actually work together. This is accomplished through integration of "ad hoc" hardware in a laboratory "breadboard" setting or computer in the loop to validate not only that the technologies work together but also that their performance continues to support the expected concept outcome. During this phase, system requirements are refined, performance metrics are established, and the preliminary system engineering Form, Fit, and Function analysis is better defined to achieve the end product design.

TDS Update

The TDS is the primary planning document for technologies containing all of the important elements necessary to accomplish development of the technologies as applied to the customer(s) requirements. Even though the TDS is described at the Acquisition level, most science and technology enterprises recognize the elements of the TDS as residing in a Program/Project Plan. The important thing is that a Plan is developed, followed, and used to report Technology Project status. For that reason, it should contain basic Program Management Data, such as; Estimated/Budgeted/Actual Cost, Schedule, Performance Goals (Requirements), Risks Management Plan, Program Deliverables, and the Risk Management strategy.

TTA (Intent)

Technology Transition Agreement is intended to be a mechanism for a technology project to obtain interest from users/sponsors, where the ultimate goal is for them to identify clear intent to incorporate the technology into a fielded capability and finally to secure commitment from a Program Office to transition the technology. The TTA process of interest-to-intent-to-commitment will ensure stakeholders that technologies are carefully managed and are delivered to the customer not only within time and budget constraints, but also that they provide increased capabilities to meet the needs of the warfighter.

User Performance Requirements

The User Performance Requirements include any capability or characteristic requirements developed for the system. A performance requirement specifies the speed or operational effectiveness of a capability that must be delivered by the technology component architecture as seen by the technical layers within that system architecture. Key performance parameters are either provided from published User documentation or extracted from other sources of documented performance requirements or goals.

Brassboard Lab Validation Plan

The Brassboard Lab Validation Plan sets up testing that will continue to increase the fidelity of the technology to demonstrate that the components of the technology work together as a whole as a part of a system. This document will outline the plan for setting up a simulated environment where the basic technological brassboard components are integrated with reasonably realistic supporting elements. A determination of what test data will be collected, what analysis will be performed, what reporting will be generated and how any issues found will be addressed should be included in this plan.

CHECKLIST

The deliverables for the Development phase are:

Brassboard Lab Validation Report

The Brassboard Lab Validation Plan describes the higher fidelity testing of the technology performed to demonstrate that the components of the technology work together as a whole as a part of a system. This document reviews the setup of the simulated environment where the basic technological brassboard components are integrated with reasonably realistic supporting elements.

TDS Update

The TDS is the primary planning document for technologies containing all of the important elements necessary to accomplish development of the technologies as applied to the customer(s) requirements. Even though the TDS is described at the Acquisition level, most science and technology enterprises recognize the elements of the TDS as residing in a Program/Project Plan. The important thing is that a Plan is developed, followed, and used to report Technology Project status. For that reason, it should contain basic Program Management Data, such as; Estimated/Budgeted/Actual Cost, Schedule, Performance Goals (Requirements), Risks Management Plan, Program Deliverables, and the Risk Management strategy.

TTA Update (Intent)

Technology Transition Agreement is intended to be a mechanism for a technology project to obtain interest from users/sponsors, where the ultimate goal is for them to identify clear intent to incorporate the technology into a fielded capability and finally to secure commitment from a Program Office to transition the technology. The TTA process of interest-to-intent-to-commitment will ensure stakeholders that technologies are carefully managed and are delivered to the customer not only within time and budget constraints, but also that they provide increased capabilities to meet the needs of the warfighter.

Manufacturing Plan (Draft)

The Manufacturing Plan (MP) specifies any requirements in regards to facility and system layout or size. This also includes the site location. Manufacturing Plans are intended to communicate the fabrication needs of the technology component or system to the transition partner in order to prepare them to effectively integrate the technology into their Program. MP’s typically include specifications for Facility, location, production methods, staffing (numbers and training), inventory, quality plans, material needs, environmental concerns, and government requirements that may pertain to special handling.

Production/ILS Plan (Draft)

The Production Plan is intended to communicate the replication needs of the technology component or system to the transition partner in order to prepare them to effectively integrate the technology into their Program. Specifies the capacity, methods, and sequence of production, along with production specifications, which include staffing, quality, material, conditions, and government requirements.

Prototype Relevant Environment Lab Validation Plan

The Prototype Relevant Environment Lab Validation Plan is a test plan for a prototype to be integrated and tested in a relevant environment.

CHECKLIST

The deliverables for the Demonstration/Transition phase are:

Prototype Relevant Environment Lab Validation Report

This report contains laboratory test data collection. Includes results, conclusions, hardware specifications, production plan draft, refined life cycle cost, funding estimate, and specifications. Additionally, this reports contains a Continue/Desist Developing this Technology recommendation and rationale.

TDS Final

The TDS is the primary planning document for technologies containing all of the important elements necessary to accomplish development of the technologies as applied to the customer(s) requirements. Even though the TDS is described at the Acquisition level, most science and technology enterprises recognize the elements of the TDS as residing in a Program/Project Plan. The important thing is that a Plan is developed, followed, and used to report Technology Project status. For that reason, it should contain basic Program Management Data, such as; Estimated/Budgeted/Actual Cost, Schedule, Performance Goals (Requirements), Risks Management Plan, Program Deliverables, and the Risk Management strategy.

TTA Update (Commitment)

Technology Transition Agreement is intended to be a mechanism for a technology project to obtain interest from users/sponsors, where the ultimate goal is for them to identify clear intent to incorporate the technology into a fielded capability and finally to secure commitment from a Program Office to transition the technology. The TTA process of interest-to-intent-to-commitment will ensure stakeholders that technologies are carefully managed and are delivered to the customer not only within time and budget constraints, but also that they provide increased capabilities to meet the needs of the warfighter.

Manufacturing Plan (Final)

The Manufacturing Plan (MP) specifies any requirements in regards to facility and system layout or size. This also includes the site location. Manufacturing Plans are intended to communicate the fabrication needs of the technology component or system to the transition partner in order to prepare them to effectively integrate the technology into their Program. MP’s typically include specifications for Facility, location, production methods, staffing (numbers and training), inventory, quality plans, material needs, environmental concerns, and government requirements that may pertain to special handling.

Production/ILS Plan (Final)

The Production Plan is intended to communicate the replication needs of the technology component or system to the transition partner in order to prepare them to effectively integrate the technology into their Program. Specifies the capacity, methods, and sequence of production, along with production specifications, which include staffing, quality, material, conditions, and government requirements.

Program Protection Plan (PPP)

Program Protection is the integrating process for managing risks to advanced technology and mission-critical system functionality from foreign collection, design vulnerability or supply chain exploit/insertion, and battlefield loss throughout the acquisition lifecycle. PPP's are required in in 5000.2 for a Program Office but not necessarily a Technology Project. A Technology may have Critical Program Information (CPI) and needs to produce or use a Security Classification Guide (SCG) in order to disposition classified materials but PPP's are the province and responsibility of Program Offices and not Technology Projects. The purpose of the PPP is to help programs ensure that they adequately protect their technology, components, and information. This includes information that alone might not be damaging and might be unclassified, but that in combination with other information could allow an adversary to clone, counter, or defeat war fighting capability.

Transition Support Plan

The TM in conjunction with the Customer/Sponsor develops the transition plan showing how and when capability enhancement technologies would transition into that system. The Transition Plan is developed at the beginning of the Demonstration Phase and updated throughout the remainder of the technology program until the actual transition takes place.