Title: Technology Capability Transition Agreement Outline
1Technology / Capability Transition Agreement
Outline
- Cover
- Table of Contents
- Introduction and Summary guidelines, example
- Joint Capability Technology Demonstration (JCTD)
- Desired Capabilities Summary guidelines,
example - Benefit to Initial Capabilities Document (ICD),
Capability Development Document (CDD), or
Capability Production Document (CPD) Key
Performance Parameters guidelines, example - Products and Deliverables, TRL or MRL, and
transition date guidelines, example - Transition Entrance Criteria guidelines,
example - Program Demonstration and Assessment Approach and
Status guidelines, example - Technical Manager contact information
guidelines, example - Transition Strategy
- Type A, D, I, O and / or S guidelines, example
- Targeted Programs of Record (POR) or Programs
Type A, D, I - Description guidelines, example
- Acquisition Life Cycle Status guidelines,
example - Projected Initial Operational Capability Date
guidelines, example - Program Manager and Project Officer contact
information guidelines, example - Targeted Operational Organizations Type O
- Organizational Description guidelines, example
2- This Page Left Intentionally Blank
3Section Title I. Introduction and Summary
- Section I. Introduction and Summary
- Guidelines
- Content
- Describe and highlight the purpose and intent of
this Technology / Capability Transition Agreement - Summarize Technology / Capability description and
operational payoff the JCTD provides to
operational community - Format
Contents of the T / CTA is based on the
Management and Transition Plan Section IV
Transition
POG
M
4Example I. Introduction and Summary
- Introduction
- The Program Managers and JCTD Managers mutually
agree to enter into this Technology / Capability
Transition Agreement (T/CTA) for the purpose of
defining products and deliverables from the
appropriate name JCTD to appropriate name
POR/Program. - This T/CTA defines the functional
responsibilities and support relationships
between the parties signing this agreement. It
ensures a clear understanding of the
responsibilities of all parties to ensure a
successful transition of products and
deliverables from the JCTD to the program of
record / program name - Summary
- The to be named products and deliverables provide
the following benefits to the appropriate name
programs It is cheaper to purchase, cheaper to
operate, a better fit to warfighter needs, more
reliable with more capabilities and can be
fielded faster than similar named technologies in
pre-production development. - The named COCOM or Component sponsor has stated a
requirement for this Technology / Capability in
the listed requirements document.
POG
M
5Section Title II. JCTD A. Desired Capabilities
Summary
- Section Sub-Title A. Desired Capabilities
Summary - Guidelines
- Content
- Provide JCTD name
- Identify the key technologies and capabilities
provided by the JCTD - Provide a brief description of each technology
and capability status and additional development
as applicable - Identify current Technical Readiness Levels (TRL)
for each Technology / Capability - Use plain English language for a non-technical
reader of information - Format
POG
M
6Example II. JCTD A. Desired Capabilities
Summary
The JFM JCTD, capability is a data fusion engine
which integrates legacy and emerging sensor
systems into a common operating picture (COP).
JFM JCTD allows for automation and fusion of the
disparate systems through the application of
smart algorithms and tailored business
rules. Operational users will be provided with
actionable information and enabled to focus on
response functions. Primary components and
attributes of the integrated system are listed
below Physical Security, CBRNE Day Night and
Attended and unattended mature sensors and
fusion, sensor integrated into system suite,
robust C2 architecture, standard commercial
communication protocol and standards, automatic
processes to cue intervention, alerts,
assessments, near real time correlation and
geo-location, network Services Infrastructure,
Common Operational Picture, unmanned systems
(unattended UGV, UAV).
POG
M
7Section Title II. JCTDB. Benefit to Initial
Capabilities Document (ICD), Capability
Development Document (CDD), or Capability
Production Document (CPD) Key Performance
Parameters (KPP)
- Section Sub-Title B. Benefit to Initial
Capabilities Document (ICD), Capability
development Document (CDD), or Capability
Production Document (CPD) Key Performance
Parameters (KPP) - Guidelines
- Content
- Review existing approved or developing ICD, CDD
and / or CPD - Identify primary and secondary documents the JCTD
contributes and provides benefits - Define how the JCTD will contribute to the
accomplishment of the ICD, CDD and / or CPDs
KPPs - Cite specific and applicable defined
capabilities, attributes and KPPs of the ICD, CDD
and / or CPD(s) - Provide relevant JCTD information highlighting
technology or capability contributions to the
ICD, CDD and / or CPD capabilities, attributes
and KPPs - Format
POG
M
8Example II. JCTDB. Benefit to Initial
Capabilities Document (ICD)/ Capability
Development Document (CDD)/ or Capability
Production Document (CPD) Key Performance
Parameters (KPP)
- CDD 1 (Primary)
- CDD Capabilities, Attributes, KPPs Networked
Battle Command KPP 2 - The FCS network must
enable Battle Command and provide situational
awareness to the manned platform and dismounted
soldier level. (Threshold) - JFP JCTD Contribution The JFP JCTD will leverage
existing Net-Centric capabilities by providing
more rapid analysis and dissemination of Battle
Space Object (BSO) track information to operating
units - CDD 2 (Secondary)
- CDD Capabilities, Attributes, KPPs Joint
Interoperability KPP 1 - The FCS FoS must be
Joint interoperable. (Threshold) - JFP JCTD Contribution The JFP JCTD promotes
Joint Interoperability by employing multi-INT
sensor data and databases, existing information
sources (SIGINT, IMINT, ACINT, SEAWATCH, JMIE,
Internet), in a near-real-time analytical and
planning environment, to vastly improve shared
situational awareness of joint forces
POG
M
9Section Title II. JCTD C. Products and
Deliverables TRL or MRL and Transition Date
- Section Sub-Title C. Products and Deliverables,
TRL or MRL and transition date - Guidelines
- Content
- Identify all JCTD transition products and
deliverables - Use information from Section IV. C., of the
Management and Transition Plan - Identify quantities
- Identify the TRL, MRL and planned transition date
for each deliverable - Reference Section IV. C., Management and
Transition Plan for narrative descriptions of
each deliverable - Format
POG
M
10Example II. JCTD C. Products and Deliverables
TRL or MRL and Transition Date
Provide narrative description for each Product /
Deliverable
POG
M
11Section Title II. JCTD D. Transition Entrance
Criteria
- Section Sub-Title D. Transition Entrance
Criteria - Guidelines
- Content Define capabilities, tasks and
attributes entrance criteria - Use JCTD Technologies and Capabilities Summary as
the starting point - Add additional information rows on table / matrix
showing transition-specific criteria if
required - Format
POG
M
12Example II. JCTD D. Transition Entrance
Criteria
POG
M
13Section Title II. JCTD E. Program
Demonstration and Assessment Approach and Status
- Section Sub-Title E. Program Demonstration and
Assessment Approach and Status - Guidelines
- Content
- Describe top level framework for demonstrations
- Technical testing
- Technical demonstrations
- Operational demonstrations
- Identify top level time frames (i.e., years /
quarters), milestones and decision points - Provide top level approach for technical and / or
operational demonstrations and assessments - Briefly summarize the current status of the
defined approach - Format
POG
M
14Example II. JCTD E. Program Demonstration and
Assessment Approach and Status
- Two-Phase Spiral Technical and Operational
Demonstrations - Driven by Desired Capabilities and CONOPS TTPs
- Demonstrate Desired Capabilities NLT FY10
- Conduct technical component tests and system
demonstrations - Reduces risk via test-fix-test approach
- Captures ongoing warfighter input
- Conduct repetitive evaluations of CONOP/TTPs,
threats and environment, and scenarios /
vignettes - Performs integration test and demonstration of
Program concept - Tech Demonstrations (TD) serve as dress
rehearsals for Operational Demonstrations (OD) - Two TDs Jul 2009 and May 2010
- Performed at contractor facility TBD
- Conduct ODs
- Conducted by joint, coalition and interagency
warfighters and CONOPs /TTPs - Serves to capture independent warfighter
assessments. Each OD conducted over 2 weeks. - Produces Quick Look and OUA reports
- OD-1 / LJOUA Sep 2009 (Stand-Alone Demonstration
Camp Swampy) - OD-2 / JOUA Jul 2010 (Stand-Alone Demonstration,
Battle Lab Ft. Defiance) - Assessment driven by four-tiered approach as
follows - Operational Problem
POG
M
15Section Title II. JCTD F. Technical Manager
Contact Information
- Section Sub-Title F. Technical Manager Contact
Information - Guidelines
- Content
- Identify the individual designated to be the
technical coordinator and day-to-day manager of
the Technologies / Capabilities to be
transitioned - Format
POG
M
16Example II. JCTD F. Technical Manager Contact
Information
- Technical Manager Contact Information
- The Technical Manager for the New Radio Program
is Mr Sam Smith 703-921-1234 sam.smith_at_lab.com
1234 N. Fairfax Drive, Alexandria, VA 22972
POG
M
17Section Title III. Transition StrategyA. Type A
/ D / I / O and / or S
- Section Sub-Title A. Type A, D, I, O and / or S
- Guidelines
- Content
- Define top level overall transition strategy,
recommendations, and way forward for JCTD - Identify transition path(s) based on ADIOS
framework - Type A Certification and Accreditation
- Type D Follow-on Development, Production,
Fielding and Sustainment - Type I Industry and / or COI Development
- Type O Limited Operational Use
- Type S Non-Materiel Follow-on Development
Publication - Establish preliminary recommended top level time
frames (i.e., Quarter(s) and FYs) - Driven by JCTD Operational Demonstration and
assessment milestones and planned off-ramps - Format
POG
M
18Example III. Transition StrategyA. Type A / D /
I / O and / or S
Transition
Certification Accreditation, 3Qtr, FY11
- Products
- SW system specification and architecture packages
- Assessment Reports, CONOP and TTP
- Training Package, Security Classification Guide
- Transition Plan
- Targeted Program Enterprise Services, DIA
Operational Demonstration
Type A
Follow-on Development, Acquisition, Fielding and
Sustainment, 1Qtr, FY11
GMA JCTD
- Products
- HW and SW system specification and architecture
packages - LJOUA, JOUA, CONOP and TTP
- Training Package, Safety Waivers, Releases
- Transition Plan
- Targeted Programs PM TRSYS (USMC) PM CATT (USA)
Operational Utility Assessment
Type D
Industry or Community of interest (COI) HW / SW
Development, 1Qtr, FY11
Yes
Utility?
- Products
- HW and SW system specification and architecture
packages - Demonstration Results
- Targeted Industry Northrop Grumman, Boeing,
McDonnell Douglas
Type I
Limited Operational Use, 2Qtr, FY10 1Qtr, FY11
No
- Interim Capability
- HW and SW system specification and architecture
packages - LJOUA, JOUA, CONOP and TTP
- Training Package, Safety Waivers, Releases
- Transition Plan
- Targeted Organization MOUT Facility, Ft.
Benning JFP, Camp Pendleton
Type O
Stop Work Back to ST
Non-Materiel Development and Publication, 2Qtr,
FY10 1Qtr, FY11
- Products
- DOTMLPF Change Recommendations
- CONOPS, TTPs, Training Plan Documents
- Targeted Combat Development Orgs TRADOC, MCCDC
Type S
Provide supporting top-level summary narrative
for each transition type
POG
M
19Section Title IV. Targeted Programs of Record
(POR) or Programs Type A, D, IA. Description
- Section Sub-Title A. Description
- Guidelines
- Content
- Identify and provide top level description for
each POR or Program identified for Type A, D or I
transitions - Use information from Sections IV. D.2. E.2.
F.2., POR or Program Detail Sheets of the
Management and Transition Plan - Specify type of transition for each
- Format
POG
M
20Example IV. Targeted Programs of Record (POR)
or Programs Type A, D, I A. Description
POR Description The JFP Program is an enterprise
organization that receives, evaluates and
integrates technologies based on organizational
requirements including the Intelligence
Applications Division of the Intelligence
Community Agency (ICA). POR Description The
principle mission of the Airplane Program is air
refueling. This asset greatly enhances the
Services capability to accomplish its primary
missions of Global Reach and Global Power. It
also provides aerial refueling support to Air
Force, Navy, and Marine Corps aircraft as well as
aircraft of allied nations. There are a total of
417 aircraft in both the active duty and reserve
fleets. Company Description The ABC Engine
Company is a long time leader and innovator in
the aviation propulsion industry. Their area of
expertise is to provide durable, lightweight,
high performance gas turbine engines.
POG
M
21Section Title IV. Targeted Programs of Record
(POR) or Programs Type A, D, I B. Acquisition
Life Cycle Status
- Section Sub-Title B. Acquisition Life Cycle
Status - Guidelines
- Content
- Identify the current acquisition life cycle phase
for each of the targeted transition POR or
Program - Describe status including timelines as
applicable - Milestone B, Engineering and Manufacturing
Development (EMD) - Milestone C, Production
- Fielding, Sustainment
- Certification and Accreditation
- Independent Research and Development industry
only - Format
POG
M
22Example IV. Targeted Programs of Record (POR)
or Programs Type A, D, I B. Acquisition Life
Cycle Status
- POR 1
- The XYZ Program is in the Certification and
Accreditation Phase of the acquisition life
cycle. It is scheduled to enter the Production
Fielding and Sustainment Phase in the 3rd quarter
of FY12 - POR 2
- The Future C4ISR Program is in the Technology
Development Phase of the acquisition life cycle.
It is 6 months from scheduled Milestone B
decision and EMD. The milestone C decision for
fielding and sustainment is scheduled for the 3rd
quarter of FY 12. - IRD
- The ABC engine company turbine upgrade program is
in the Technology Development Phase of the
acquisition life cycle. The program is scheduled
to enter follow-on development in the 3rd quarter
of FY12.
POG
M
23Section Title IV. Targeted Programs of Record
(POR) or Programs Type A, D, I C. Projected
Initial Operational Capability Date
- Section Sub-Title C. Projected Initial
Operational Capability Date - Guidelines
- Content
- Identify the projected Initial Operational
Capability date of the targeted transition POR or
Program - For Industry Type I, identify IRD program
completion date - Format
POG
M
24Example IV. Targeted Programs of Record (POR)
or Programs Type A, D, I C. Projected Initial
Operational Capability Date
- POR 1
- The Future C4ISR Program IOC is 4th quarter, FY
2012 - POR 2
- Transition start in FY11 with platform
integration EMD. The POR will complete
acquisition and fielding of all 42 payloads by
FY14. All 149 active-duty aircraft will be
modified to support an MMP roll-on capability by
FY15. - IRD Program
- Transition start in FY11 (1st Spiral in 3rd QTR
of FY11, 2nd Spiral in 4th QTR of FY12). ABC
Engine will field engines with upgraded blade
coating starting in FY14 and completing 342
upgraded engines by the end of FY17.
POG
M
24
25Section Title IV. Targeted Programs of Record
(POR) or Programs Type A, D, I D. Program
Manager and Project Officer Contact Information
- Section Sub-Title D. Program Manager and Project
Officer Contact Information - Guidelines
- Content
- Identify the program or project manager name and
the individual in the program office responsible
for day-to-day management, with contact
information, concerning the Technologies /
Capabilities to be transitioned - Use information from Sections IV. D.2. E.2.
F.2., POR or Program Detail Sheets of the
Management and Transition Plan - Format
POG
M
26Example IV. Targeted Programs of Record (POR)
or Programs Type A, D, I D. Program Manager
and Project Officer Contact Information
- POR 1
- Program Manager, C4ISR Program COL Joseph L.
Jones 703-921-1234 joe.jones_at_us.army.mil 1234
N. Fairfax Drive, Alexandria, VA 22972 - Program Officer, Future C4ISR Program Samuel
Smith 703-921-4321 sam.smith_at_us.army.mil 1234
N. Fairfax Drive, Alexandria, VA 22972 - POR 2
- Program Manager, The Airplane Program Mr. PM,
DSN XXX-XXXX Email xxxxx_at_xx.com - IRD Program
- Point of Contact, The ABC Engine Company Mr.
CEO, COM XXX-XXX-XXXX Email xxxxx_at_xx.com
POG
M
27Section Title V. Targeted Operational
Organizations Type OA. Organizational
Description
- Section Sub-Title A. Organizational Description
- Guidelines
- Content
- Identify and provide top level description for
each operational organization identified for Type
O transitions - Use information from Section IV. G.2. Detail
Sheets of the Management and Transition Plan - Format
POG
M
28Example V. Targeted Operational Organizations
Type OA. Organizational Description
- 305th Air Refueling Squadron
- The principal mission is air refueling. The
squadron ensures Global Reach and Global Power
are expanded and supported for missions in the
CENTCOM AOR. It provides aerial refueling support
to Air Force, Navy and Marine Corps aircraft, as
well as aircraft of allied nations. There are a
total of 41 aircraft in both the active duty and
reserve fleets.
POG
M
29Section Title V. Targeted Operational
Organizations Type OB. Operational Condition
- Section Sub-Title B. Operational Condition
- Guidelines
- Content
- Identify the current operational condition of the
targeted Operational Organization(s) - Describe operational condition including
timelines as applicable - What is the organization currently doing (i.e.
preparing for operational deployment,
operationally deployed, recently returned from
deployment, conducting routine training, etc.)? - How long has the organization been in this
condition? - Assuming that the organization is large, how much
of it is in various operational conditions (i.e.
or number of subordinate units that may be
currently engaged in active operations)? - Format
POG
M
30Example V. Targeted Operational Organizations
Type OB. Operational Condition
- 305th Air Refueling Squadron
- The squadrons assets is actively engaged in
military operations providing resources in
support of CENTCOM. 20 of air refueling assets,
50 of aerial re-supply assets, 50 of rotary
wing assets and 33 of port control personnel are
actively engaged in combat operations or in
support of ongoing combat operations. Remaining
units are engaged in training and training
preparation.
POG
M
31Section Title V. Targeted Operational
Organizations Type OC. Projected Future
Operational Condition
- Section Sub-Title C. Projected Future
Operational Condition - Guidelines
- Content
- Identify the projected future operational
condition of the targeted Operational
Organization(s) - Describe projected future operational condition
including timelines as applicable - What will the organization be doing next (i.e.
preparing for operational deployment,
operationally deployed, recently returned from
deployment, conducting routine training, etc.)? - When will the organization change into this
projected future operational condition and for
how long? - Assuming that the organization is large, how much
of it is projected to be in various operational
conditions (i.e. or number of subordinate
units that may be currently engaged in active
operations)? - Format
POG
M
32Example V. Targeted Operational Organizations
Type OC. Projected Future Operational Condition
- 305th Air Refueling Squadron
- The squadron is anticipated to remain actively
engaged in military operations providing
resources in support of CENTCOM through the
second quarter of FY12. At the conclusion of
ongoing military operations, it is planned that
the unit will return to a cycle of training and
training preparation to prepare for the next
instance of operational requirements.
POG
M
33Section Title V. Targeted Operational
Organizations Type OD. Commander Contact
Information
- Section Sub-Title D. Commander contact
information - Guidelines
- Content
- Identify the commander and the individual in
command headquarters responsible for day-to-day
management, with contact information, concerning
the Technologies / Capabilities to be
transitioned - Use information from Section IV. G.2. Detail
Sheets of the Management and Transition Plan - Format
POG
M
34Example V. Targeted Operational Organizations
Type OD. Commander Contact Information
- 305th Air Refueling Squadron
- Commander Col Pilot, DSN XXX-XXXX E-Mail
XXXX_at_XX.XX
POG
M
35Section Title VI. Targeted COCOM / Components
or Combat Development Commands Type SA.
Organizational Description
- Section Sub-Title A. Organizational Description
- Guidelines
- Content
- Identify and provide top level description for
each COCOM J Code, Components or Combat
Development Command identified for Type S
transitions - Use information from Sections H.2. Detail Sheets
of the Management and Transition Plan - Format
POG
M
36Example VI. Targeted Combat Development
Commands Type S A. Organizational Description
- J-5, COCOM 1
- Strategic Planning and Policy (J5), U.S. XXX
Command. Assists the Chief of Staff XXX in the
study, preparation, formulation and revision of
long-range plans to meet war contingencies.
Provides staff advice and assistance to the Chief
of Staff XXX in his discharge of responsibilities
pertaining to the Joint XXX-US Co-Secretariat
Mutual Defense Board and other defense
cooperation agreements and international
arrangements. Assists the Chief of Staff in the
conduct of researches on strategic, security and
military matters. Provides over-all direction,
supervision and control of ODCS for Plans, J5
personnel, activities and resources. Performs
such other functions as the CDR XXX may direct - TRADOC
- Recruits, trains and educates the Army's
Soldiers develops leaders supports training in
units develops doctrine establishes standards
and builds the future Army. TRADOC is the
architect of the Army and "thinks for the Army"
to meet the demands of a nation at war while
simultaneously anticipating solutions to the
challenges of tomorrow. The TRADOC headquarters
staff analyzes, assesses, provides
staff-management oversight and recommends for
decision all activities affecting policy, command
guidance, developmental processes and
implementation / execution processes to support
the command in meeting its mission. The staff
facilitates the coordination and dissemination of
strategic operational concepts and plans,
doctrine and training to the Defense Department,
Department of the Army, U.S. Joint Forces
Command, sister services, Congress and external
agencies and organizations. Also, the staff
supports TRADOC subordinate organizations in
executing command initiatives in recruiting,
training, educating, designing, testing and
evaluating the force.
POG
M
37Section Title VI. Targeted Combat Development
Commands Type S B. COCOM or Component
Representative or Capability Manager contact
information
- Section Sub-Title B. COCOM or Component
Representative or Capability Manager contact
information - Guidelines
- Content
- Identify the COCOM or Component Representative or
Capability Manager name and the individual in the
program office responsible for day-to-day
management, with contact information, concerning
the Technologies / Capabilities to be
transitioned - Use information from Sections H.2. Detail Sheets
of the Management and Transition Plan - Format
POG
M
38Example VI. Targeted Combat Development
Commands Type S B. COCOM or Component
Representative or Capability Manager contact
information
- J-5 COCOM 1
- The J-5 CENTCOM COCOM Representative is COL
Joseph L. Jones 813-921-1234 joe.jones_at_us.army.m
il 1234 N. McDill Drive, Tampa, FL - TRADOC
- TRADOC POC COL Hardman, DSN XXX-XXXX Email
xxxxx_at_xx.com
POG
M
39Section Title VII. Schedule
- Section Title VII. Schedule
- Guidelines
- Content Illustrate and lay out during (if
appropriate) and post-JCTD RDTE, production,
sustainment, fielding and / or publication time
frames each targeted POR, Program, COCOM,
Component or Combat Development Command
organization - Uses Gantt chart-like illustration
- Illustrate recommended JCTD transition type(s)
schedules for during and post-JCTD activities
based on JCTD products and deliverables and
perspective starting with completion of interim
and final assessments - Illustrate existing targeted POR and / or Program
RDTE, production, sustainment and fielding
schedules aligned with during and post-JCTD
timeline - Illustrate targeted LOU organization operational
schedules aligned with during and post-JCTD
timeline - Illustrate existing targeted COCOM, Component or
Combat Development Command non-materiel
development and publication organizational
schedules aligned with during and post-JCTD
timeline - Use schedule illustrations to provide comparative
view between recommended post-JCTD activities
versus existing POR and / or Program, COCOM,
Component or Combat Development Command schedules
to highlight schedules compatibilities and
incompatibilities - Format
POG
M
40Example VII. Schedule
POG
M
41Section Title VIII. Funding
- Section Title VIII. Funding
- Guidelines
- Content
- List and organize all additional funding
requirements for implementation of JCTD
Transition Plan - Copy / paste and use funding information as
defined in Management and Transition Plan Section
IV. J. - Show funding by type, source and year
- Provide supporting narrative assessment and
position on the state and feasibility of the
additional required funding to implement
transition of the products and deliverables
according to the Management and Transition Plan
Section IV information. - Provide statements regarding commitment and
intent. - Format
POG
M
42Example VIII. Funding
- The listed additional funding fully resources the
implementation of the JFP Transition. Additional
funding identified for Type A and D transitions
is programmed and committed in the FY12-17 POM.
Company 1 has identified and committed IRD. Type
O funding is committed by the 305th Refueling
Squadron. Type S funding is committed by TRADOC
to develop and institutionalize CONOPs and TTPs.
- Commitment Upon successful demonstration of key
performance requirements, PM JFP will integrate
XXX (product) into JFP commencing in FY11. This
integration effort will be funded under PE
XXXXXXX, Project XXXX. - Intent Upon successful demonstration of key
performance requirements, PM JFP intends to
integrate XXX (product) into JFP commencing in
FY11 under PE XXXXXXX Project XXXX).
POG
M
43Section Title IX. Risk Management
- Section Title IX. Risk Management
- Guidelines
- Content Identify risks associated with
transitioning JCTD, specifically - Define short description of each risk, expected
level of impact (high, medium, low), mitigation
strategy for risk factors, expected result of
mitigation strategy - Operational (e.g., operational use suitability,
etc.) - Technical (e.g., POR and / or Program and / or
system architectures compatibility, technical
maturity, etc) - Funding (e.g., Post JCTD funding adequacy,
funding commitment, funding level etc.) - Cost (e.g., Cost feasibility)
- Schedule (e.g., POR and / or Program and / or
Operation schedule compatibility, etc) - Transition (e.g., Programmatic feasibility, CDD
compatibility, etc) - Policy (e.g. POR and / or Program and / or
Operation policy impacts, etc) - Provide supporting narrative information
explaining the selection of the overall TCL
rating based on and for each transition type, as
applicable - Rate Transition Commitment Level (TCL) based on
strength of transition commitment and years
remaining in JCTD - Format
POG
M
44Example IX. Risk Management
POG
M
45Section Title X. Transition CommitmentA.
Transition Commitment Level and Status
- Section Sub-Title A. Transition Commitment Level
and Status - Guidelines
- Content
- Rate Transition Commitment Level (TCL) based on
strength of transition commitment and years
remaining in JCTD - Provide supporting narrative information
explaining the selection of the overall TCL
rating based on and for each transition type, as
applicable - Select final TCL rating in support of T/CTA
signatures and approval - Format
POG
M
46Example X. Transition CommitmentA. Transition
Commitment Level and Status
The JCTD is currently at Level B (Working) in
Block B2 (Yellow) with 2 years remaining. The
T/CTA is currently in development the MTP
Section IV Transition information is written and
being coordinated and some of the targeted
Programs are committed to funding and have
provided PE numbers.
Transition Commitment Level (TCL)
Years remaining in approved JCTD
1
2
3
Strength of Transition Commitment
A. T/CTA Level A - Committed
- Fully signed and approved T/CTA
- MTP Section IV Transition Information Fully
Coordinated and Completed - All Transition Funding Programmed with PE Numbers
Identified
A1
A2
A3
B. T/CTA Level B - Working
- MTP Section IV Transition Information in
Coordination - T/CTA Developing
- Transition TRL Established
- Some targeted POR / Programs / Operational
Organizations / Combat Development Commands
committed funding with PE Numbers
B1
GMA JCTD
B3
C. T/CTA Level C - Initial
- MTP Section IV Transition Information initiated
- T/CTA Framework Established
- Targeted PE Line(s) Key Stakeholders Identified
- Target POR / Programs / Operational Organizations
/ Combat Development Commands Identified and
Transition Commitment Intent Obtained
C1
C2
C3
D. No MTP Section IV Transition Information or
T/CTA initiated
D1
D2
D3
POG
M
47Section Title X. Transition CommitmentB.
Resource Sponsor and Requirements Manager Contact
Information
- Section Sub-Title B. Resource Sponsor and
Requirements Manager contact information - Guidelines
- Content
- Identify the resource sponsor(s) responsible for
resourcing and committing funding to implement
Transition Plan - Include name, organization, e-mail, telephone
number for every transition type - Format
POG
M
48Example X. Transition CommitmentB. Resource
Sponsor and Requirements Manager Contact
Information
- Type A
- Resource Sponsor Ms S. Smith, G-8, HGDA,
703-921-2134 s.simpson_at_us.army.mil Pentagon
room 3E385, Washington, D.C. - Requirements Manager Mr. O. Taylor, DSN
XXX-XXXX Email xxxxx_at_xx.com - Type D
- Resource Sponsor 1 Mr. D. Vader, DSN XXX-XXXX
Email xxxxx_at_xx.com - Requirements Manager 1 Mr. B. Simpson, DSN
XXX-XXXX Email xxxxx_at_xx.com - Resource Sponsor 2 Mr. E. Scrooge, DSN XXX-XXXX
Email xxxxx_at_xx.com - Requirements Manager 2 Mr. D. Tracy, DSN
XXX-XXXX Email xxxxx_at_xx.com - Type I
- Resource Sponsor Ms. P. Lea, COM XXX-XXX-XXXX
Email xxxxx_at_xx.com - Requirements Manager Mr. C. Eastwood, COM
XXX-XXX-XXXX Email xxxxx_at_xx.com - Type O
- Resource Sponsor Mr. L. Skywalker, COM
XXX-XXX-XXXX Email xxxxx_at_xx.com - Requirements Manager Mr. J. Wales, DSN XXX-XXXX
Email xxxxx_at_xx.com - Type S
- Resource Sponsor Mr. J. Bond, DSN XXX-XXXX
Email xxxxx_at_xx.com - Requirements Manager Mr. H. Solo, DSN XXX-XXXX
Email xxxxx_at_xx.com
POG
M
49Section Title XI. Signatures
- Section Title XI. Signatures
- Guidelines
- Content
- All transition partners programs and
organizations identified in the Management and
Transition Plan (MTP), Section IV Transition, and
Technology / Capability Transition Agreement
(T/CTA) sign T/CTA committing organizations,
funding and transition of technologies /
capabilities according to MTP Section IV
Transition Plan. - Format
POG
M
50Example XI. Signatures
- Technical Manager Date
- Program Manager Date
- Program Manager Date
- Organizational Commander Date
- COCOM Representative Date
POG
M