Practical Operating Guidelines POG Master

1
Practical Operating Guidelines (POG) Master

• March 31, 2009

2
Table of Contents

• Introduction
• POG Taxonomy guidelines
• Process Steps
• Key Documentation / Modules
• POG Position Roles and Responsibilities
  guidelines
• POG JCTD DUSD(ASC) Funding guidelines
• DoD Programs Supporting Transition and Agile
  Acquisition guidelines

3
POG Attributes

• Driven by JCTD process and life cycle
• Formulate, Propose, Candidate Review, Rate and
  Rank, JROC Needs Validation, USD(ATL) Approval,
  Congressional Notification, Implementation
  Direction, Demonstration, Assessment and
  Transition, and Final Report
• Composition
• PowerPoint-based master and modules guidelines
  and examples
• Word-based narrative, illustrations and outlines
• Tailorable
• Compatible with KIMS
• Supports diverse set of users / audiences
• Meets needs of JCTD processes and life cycle
• User Categories
• Category I DoD, interagency, COCOM, Joint Staff
  and Service field JCTD leadership and management
  (POG Narrative Description)
• Category II Managers and teams of approved JCTDs
  and JCTD proposal teams (Complete POG)

Information developed using the POG may be
portrayed in the form of PowerPoint style
briefing charts (for briefings) or as Word style
written documents (for descriptive, detailed
information)
4
JCTDs BridgeST and Acquisition
5
Characteristics of JCTDs

• Address COCOM Needs With Innovative Concept and
  Mature Technology
• Provide Capability Solution With Operational
  Concepts and Tactics, Techniques and Procedures
  (TTP)
• Assess Solutions in Warfighter Operational
  Demonstrations
• Usually Joint, Often Combined / Coalition /
  Interagency / Transformational
• Rapid Results 1 to 3 Years or Less to Final
  Demonstration and a Prototype Interim Capability
• Multiple Funding Sources
• Transition enabled through a Technology /
  Capability Transition Agreement (TCTA)

Emphasis on Demonstration and TransitionTry With
Intent To Buy
6
JCTDMeasures and Metrics
7
JCTD Framework
8
JCTD Guidelines Taxonomy
9
JCTD 10 Step Life-Cycle Process Flow
10
Formulate

• Key Activities
• Define and confirm Operational Problem and
  Desired Capabilities
• Coordinate with other COCOMs for input / feedback
• Determine eligibility / qualification to be a
  JCTD candidate
• Identify and develop JCTD Team (operational,
  technical, transition, acquisition, policy,
  international, interagency, Joint Staff, OSD)
• Develop JCTD candidate proposal (i.e.,
  operational, technical, transition) including
  management, funding and team approach
• Includes use of 10 Key Questions and 7 Factors
  checklist described in JCTD POG narrative
• Produce JCTD Candidate Proposal Package including
  potential animation of CONEMP or CONOP
• Accomplish any time via workshop approach or
  other collaborative media
• Participants
• Lead Operational Manager, COCOM with Partner(s)
• Supporting
• Technical Manager, Service / Agency
• Transition Manager, Service / Agency
• Oversight Executive, ODUSD(ASC)
• Independent Assessor
• Interagency, International, Joint Staff

Key Documentation Proposal Paper, Candidate
Review Briefing, Quad Chart
11
Proposal Paper Outline

• Overview
• The Situation guidelines, example
• Coalition / Joint / Interagency Operational
  Problem guidelines, example
• Desired Capabilities guidelines, example
• Top Level Capabilities and Metrics guidelines,
  example
• Solution Trade-Off Analysis
• Key Assumptions guidelines, example
• Alternatives Identification and Comparison
  guidelines, example
• Conclusions and Recommendations guidelines,
  example
• Capabilities Solution guidelines, example
• Overall Demonstration Strategy guidelines,
  example
• Operational Management
• Operational View-1 (OV-1) Architecture
  guidelines, example
• Top Level CONEMP or CONOP guidelines, example
• Critical Operational Issues guidelines, example
• Coalition / Joint / Interagency Operational
  Utility Assessment Strategy guidelines, example
• Operational Demonstration Approach guidelines,
  example
• Top Level Demonstration Scenarios guidelines,
  example
• Technical Management

CR
RR
F
P
12
Proposal Paper Outline (contd)

• Transition Management
• Overall Transition Strategy guidelines,
  examples
• Description of Products / Deliverables
  guidelines, example
• Certification and Accreditation (Type A)
  guidelines, example
• Follow-on Development, Production, Fielding and
  Sustainment (Type D) guidelines, example
• Industry and / or COI Development (Type I)
  guidelines, example
• Limited Operational Use (LOU) if implemented
  (Type O) guidelines, example
• Non-Materiel Follow-on Development and
  Publication (Type S) guidelines, example
• Networks / Equipment / Facilities / Ranges /
  Sites guidelines, example
• Organizational and Programmatic and Approach
• Organizational Structure, Roles and
  Responsibilities guidelines, example
• Programmatic
• Schedule guidelines, example
• Supporting Programs guidelines, example
• Cost Plan by task and by year guidelines,
  example
• Funding by source and by year guidelines,
  example
• Acquisition and Contracting Strategy guidelines,
  example
• JCTD Risk Management and Mitigation Approach
  guidelines, example
• Summary / Payoffs guidelines, example

CR
F
P
RR
13
Candidate Review BoardBriefing Outline

• The Situation example
• Coalition / Joint / Interagency Operational
  Problem example
• Desired Capabilities example
• Top Level Capabilities and Metrics example
• Solution Trade-Off Analysis and Alternatives
  Identification example
• Capabilities Solution example
• Operational View-1 (OV-1) example
• Overall Demonstration and Programmatic Strategy
  example
• Core Technologies example
• Interoperability and Integration example
• Security, Information Assurance and Safety
  example
• Overall Transition Strategy example
• Certification and Accreditation (Type A)
  example
• Follow-on Development, Production, Fielding and
  Sustainment (Type D) example
• Industry and / or COI Development (Type I)
  example
• Limited Operational Use (LOU) if implemented
  (Type O) example
• Non-Materiel Follow-on Development and
  Publication (Type S) example
• Organizational Wiring Diagram example
• Schedule example

CR
F
P
RR
14
Candidate Review Board Briefing Outline Back-ups

• Back-ups
• CONEMP or CONOP example
• Critical Operational Issues example
• Coalition / Joint / Interagency Operational
  Utility Assessment Strategy example
• Operational Demonstration Approach example
• Top Level Demonstration Scenarios example
• System View-1 (SV-1) example
• Technical Demonstration and Programmatic Approach
  example
• Transition Affordability example
• Training example
• Description of Products / Deliverables example
• Supporting Programs example
• Networks / Equipment / Facilities / Ranges /
  Sites example
• Acquisition and Contracting Strategy example

CR
F
P
RR
15
Quad Chart(Name JCTD and FYs)guidelines,
example

• Capabilities Solution
• Technologies

• Operational Problem
• OV-1

• Transition
• Funding

• Participants
• User Sponsor
• Lead Agency
• OM
• TM
• XM
• Schedule

JNV
CR
F
P
RR
16
Propose

• Key Activities
• Submit JCTD Candidate to DUSD(ASC) via KIMS and
  supporting e-mail message to Oversight Executive
  if assigned via three on-ramp options
• 2nd Qtr, CRB, 4th Qtr, Mini-CRB Anytime /
  Immediate Rolling Start
• Continue Development and Coordination of
  Candidate Proposal
• Presentations to
• Other related COCOMs, Service / Agency Lead,
  Inter-agency, international partners as
  appropriate
• Applicable JCIDS Functional Capability Working
  Group(s)
• Lunch Bunch meetings
• Confirm organizational and funding commitment
• Obtain initial POR and / or Program and / or
  Organization commitment intent
• Maintain updated Candidate Proposal on KIMS
• Pre-brief candidate to ADUSD(ASC) Joint
  Functional Capability Area Board representative
  and Director, JCTD Program, ADUSD(ASC) to obtain
  approval to present to Candidate Review
• Participants
• Lead Operational Manager, COCOM with Partner(s)
• Supporting
• Technical Manager, Service / Agency
• Transition Manager, Service / Agency
• Oversight Executive, ODUSD(ASC)
• Independent Assessor

Key Documentation Proposal Paper, Candidate
Review Briefing, Quad Chart
17
Candidate Review

• Key Activities
• Present JCTD Candidate Proposal to DUSD(ASC)
  Candidate Review Board
• Obtain DUSD(ASC) and Candidate Review
  concurrence to continue development and
  coordination of candidate proposal
• Continue development and coordination of JCTD
  Candidate Proposal
• Priority on organizational and funding commitment
• Obtain POR and / or Program and / or Organization
  commitment intent
• Maintain updated Candidate Proposal on KIMS
• Participants
• Lead Operational Manager, COCOM with Partner(s)
• Supporting
• Technical Manager, Service / Agency
• Transition Manager, Service / Agency
• Oversight Executive, ODUSD(ASC)
• Interagency, International, Joint Staff

Key Documentation Proposal Paper, Candidate
Review Briefing, Quad Chart
18
Rate and Rank

• Key Activities
• Review JCTD Candidate Proposals for completeness
  and executability
• Coordinate with and obtain Functional Capability
  Board(s), JCB and JROC concurrence
• Continue coordination of JCTD Candidate Proposals
  with COCOMs, Services, Interagency and Lunch
  Bunch
• Conduct Rating and Ranking process with COCOMs
  and Services
• Maintain DUSD(ASC) concurrence to continue
  development and coordination of candidate
  proposal
• Continue development of JCTD Candidate Proposals
• Obtain organizational and funding commitment
• Obtain POR and / or Program and / or Organization
  commitment intent
• Maintain updated Candidate Proposal on KIMS
• Finalize list of JCTD Candidate Proposals to go
  forward for JROC Needs Validation
• Initiate development of Implementation Directive
  (ID) (not reqd for Rate and Rank)
• Participants
• Leads Director, JCTD Program, ADUSD(ASC) and
  Oversight Executive, ODUSD(ASC)
• Supporting
• COCOMs and Services
• Operational Manager, COCOM
• Technical Manager, Service / Agency
• Transition Manager, Service / Agency

Key Documentation Proposal Paper, Candidate
Review Briefing, Quad Chart
19
JROC Needs Validation

• Key Activities
• Obtain JROC needs validation of Operational
  Problem and Desired Capabilities ensuring support
  of COCOM IPLs and Joint Staffs most pressing
  operational needs
• Continue coordination of JCTD candidate Proposal
  with Functional Capability Area Board or Working
  Group, COCOMs, Services, interagency
• Maintain DUSD(ASC) concurrence to continue
  development and coordination of candidate
  proposal
• Continue development of JCTD candidate proposal
• Obtain POR and / or Program and / or Organization
  commitment intent
• Maintain updated candidate proposal on KIMS
• Continue development of ID (not reqd for JROC
  Needs Validation)
• Participants
• Lead Director, JCTD Program, ADUSD(ASC) and
  JROC
• Supporting
• Operational Manager
• Technical Manager, Service / Agency
• Transition Manager, Service / Agency
• Oversight Executive, ODUSD(ASC)
• Joint Staff

Key Documentation Quad Chart
20
USD(ATL) Approval

• Key Activities
• Develop Congressional Summary Report for ongoing
  and new JCTDs
• Obtain USD(ATL) approval of JCTD selected
  candidates
• Continue development of JCTD
• Obtain POR and / or Program and / or Organization
  commitment intent
• Maintain updated JCTD on KIMS
• Continue development of ID (not reqd for
  USD(ATL) Approval)
• Participants
• Leads Director, JCTD Program, ADUSD(ASC) and
  USD(ATL)
• Supporting
• Oversight Executive, ODUSD(ASC)
• Operational Manager
• Technical Manager, Service / Agency
• Transition Manager, Service / Agency
• Interagency, International, Joint Staff

Key Documentation Congressional Summary Report
21
Congressional Summary Report Outline (for each
JCTD)

• JCTD Title guidelines, example
• Year Started guidelines, example
• COCOM / User Sponsor guidelines, example
• Lead Service / Agency guidelines, example
• Coalition / Joint / Interagency Operational
  Problem guidelines, example
• Capabilities Solution guidelines, example
• Planned Schedule guidelines, example
• Overall Transition Strategy
• Accomplished to date guidelines, example
• Planned guidelines, example
• Operational Use by the Warfighter (if applicable)
  guidelines, example
• Funding FY20XX, OSD(ASC), total planned funding
  all sources guidelines, example

CN
UA
22
Congressional Notification

• Key Activities
• Conduct 30-day (calendar days) Congressional
  Notification process for approved JCTD
• House Armed Services Committee
• House Appropriations Committee
• House Appropriations Committee, Subcommittee on
  Defense
• Senate Armed Services Committee
• Senate Appropriations Committee
• Senate Appropriations Committee, Subcommittee on
  Defense
• Continue development of JCTD
• Obtain POR and / or Program and / or Organization
  commitment intent
• Maintain updated JCTD on KIMS
• Finalize development of ID (not reqd for
  Congressional Notification)
• Participants
• Lead Director, JCTD Program, ADUSD(ASC) and
  Oversight Executive ODUSD(ASC)
• Supporting
• Operational Manager
• Technical Manager, Service / Agency
• Transition Manager, Service / Agency

Key Documentation Congressional Summary Report
23
Implementation Direction

• Key Activities
• Obtain stakeholders approval of JCTD
  Implementation Directive (ID)
• Obtain DUSD(ASC) approval of JCTD ID
• Continue development of JCTD
• Obtain POR and / or Program and / or Organization
  commitment intent
• Maintain updated JCTD on KIMS
• Request and obtain funding
• Participants
• Lead Director, JCTD Program, ADUSD(ASC) and
  Oversight Executive, ODUSD(ASC)
• Supporting
• Operational Manager
• Technical Manager, Service / Agency
• Transition Manager, Service / Agency
• Interagency, International

Key Documentation Implementation Directive,
Funding Request
24
Implementation DirectiveOutline

• Cover
• Signature Page (senior resource providers)
• Introduction guidelines, example
• Coalition / Joint / Interagency Operational
  Problem guidelines, example
• Overall Objective and Approach guidelines,
  example
• Organizational Structure, Roles and
  Responsibilities guidelines, example
• Top Level CONEMP or CONOP guidelines, example
• Overall Transition Strategy guidelines, example
• Schedule guidelines, example
• Funding Tables
• Cost Plan per Task and FY guidelines, example
• Funding per Source and FY guidelines, example
• Points of Contact guidelines, example

JNV
UA
CN
ID
RR
25
Funding Request

• DUSD(ASC) Funding Request Overall Guidelines
  guidelines
• DUSD(ASC) Funding Request Form guidelines,
  example
• DUSD(ASC) Sub-Allocation Memo guidelines,
  example
• Statement of Work for Reimbursable MIPR
  guidelines, example
• Statement of Work for Direct Cite MIPR
  guidelines, example

DAT
ID
26
Demonstration, Operational Utility Assessment
Transition

• Key Activities
• Develop and implement operational, technical and
  transition approach
• Develop, coordinate and obtain Director, JCTD
  Program, approval of MTP
• Develop and coordinate CONOP and TTP
• Identify and establish user functional
  requirements based on CONOP, Desired Capabilities
  and Tasks / Attributes
• Develop and establish Integrated Assessment Plan
  (IAP)
• Develop technical documentation (e.g., approach,
  specifications, security classification guide,
  etc.)
• Develop Training Plan
• Develop / update Business Case Analysis
  supporting MTP Section IV Transition and
  Technology/Capability Transition Agreement
  (T/CTA) strategy
• Initiate development of T/CTA
• Request and obtain JCTD funding
• Conduct vulnerability assessments (via JIOWC)
• Technically and operationally demonstrate JCTD
  according to CONOP, TTP, Top Level Capabilities
  and Metrics, and Functional Requirements
• Employ spiral demo-build-demo approach
• Update, coordinate and establish MTP, T/CTA,
  CONOP and TTP, technical documentation and
  Training Plan obtain applicable stakeholder
  approval
• Perform Interim(s) and Final Operational Utility
  Assessments (I/OUA)
• Develop and obtain COCOM approval of interim(s)
  and OUA Reports
• Finalize CONOP and TTP, technical documentation
  and Training Plan
• Initiate transition pending successful IOUAs /
  final OUA

• Operational Organizations
• Combat Development Command (CDC) Capability
  Managers
• Functional Capability Working Group
  Representative(s)
• Targeted POR or Program PM Representative(s)

• Financial Programmer(s)
• COCOM and Component Representative(s)
• Resource Sponsor

Key Documentation Management and Transition Plan
(MTP), Technology / Capability Transition
Agreement (TCTA) CONOP TTP, Funding Request,
Integrated Assessment Plan (IAP), Operational
Utility Assessment (OUA) Report
27
CONOP TTP Outline

• Overview
• Purpose and Scope guidelines, example
• Development Process example
• Coalition / Joint / Interagency Operational
  Problem guidelines, example
• Desired Capabilities guidelines, example
• Capabilities Solution guidelines, example
• Capability Summary
• Joint Functional Capability Area(s) Relevance
  guidelines, example
• Required Capabilities guidelines, example
• Concept of Operations Summary guidelines,
  example
• Threat and Operational Environment guidelines,
  example
• Critical Operational Issues (COI) guidelines,
  example
• Joint / Coalition / Interagency Capabilities and
  Metrics
• Top Level Capabilities and Metrics guidelines,
  example
• Mission Area Analysis (MAA) guidelines, example
• Joint / Coalition / Interagency Concept(s) of
  Operation
• Operational View (OV-1) guidelines, example
• Strategic - Operational - Tactical Level of War
  (as applicable) guidelines, example
• Scenarios (Operational Situation) example

DAT
28
CONOP TTP Outline(contd)

• Joint / Coalition / Interagency Tactics,
  Techniques and Procedures (TTP)
• Purpose and Scope guidelines, example
• Tactics, Techniques and Procedures guidelines,
  example
• DOTMLPF Modification (as needed) guidelines,
  example
• Conclusions and Issues guidelines, example
• Acronyms and Terms guidelines, example
• Glossary guidelines, example
• Related Documents guidelines, example
• Appendices (optional) guidelines, example
• Architecture Framework
• Operational Views (OV-2, 3, 5, 6c)
• System Views (SV-1, 2, 6)
• Technical Views (TV-1)
• Joint Capability Systems / Technologies
• Description - Characteristics - Performance
  Parameters
• Program(s) Strategy - Objectives (if applicable)
• JCIDS / Acquisition Process Required Documents
  (as applicable)
• Initial Capabilities Document (ICD)
• Capabilities Development Document (CDD)

DAT
29
Management and Transition Plan Outline

• Cover
• Signature Page (leaders of execution players)
• Table of Contents
• Overview
• The Situation guidelines, example
• Coalition / Joint / Interagency Operational
  Problem guidelines, example
• Desired Capabilities guidelines, example
• Top Level Capabilities and Metrics guidelines,
  example
• Solutions Trade-off Analysis
• Key Assumptions and Guidelines guidelines,
  example
• Alternatives Identification and Comparison
  guidelines, example
• Conclusions and Recommendations guidelines,
  example
• Capabilities Solution guidelines, example
• Overall Demonstration Strategy guidelines,
  example
• Operational
• Operational View-1 (OV-1) guidelines, example
• Top Level CONEMP or CONOP guidelines, example
• Critical Operational Issues (COI) guidelines,
  example

Action Oriented Facts To the Point
DAT
30
Management and Transition Plan Outline (contd)

• Technical
• System View-1 (SV-1) guidelines, example
• Technical Demonstration and Programmatic Approach
  guidelines, example
• Core Technologies guidelines, example
• Transition Affordability guidelines, example
• Interoperability and Integration guidelines,
  example
• Training guidelines, example
• Security, Information Assurance and Safety
  guidelines, example
• Transition
• Capabilities Summary
• Joint Functional Capability Area(s) Relevance
  guidelines, example
• Required Capabilities guidelines, example
• Threat and Operational Environment guidelines,
  example
• Capabilities and Tasks and Attributes Entrance
  Criteria guidelines, example
• Overall Transition Strategy guidelines, example
• Description of Products and Deliverables
  guidelines, example
• Certification and Accreditation (Type A)
• Overall Strategy guidelines, example
• Targeted POR / Programs (use detail sheets)
  guidelines, example

Action Oriented Facts To the Point
DAT
31
Management and Transition Plan Outline (contd)

• Limited Operational Use (LOU) (if implemented)
  (Type O)
• Overall Strategy guidelines, example
• Targeted LOU Organizations (use detail sheets)
  guidelines, example
• LOU Capability Package guidelines, example
• Non-Materiel Follow-on Development and
  Publication (Type S)
• Overall Strategy guidelines, example
• Targeted COCOMs and / or Components or Combat
  Development Commands (use detail sheets)
  guidelines, example
• Configuration Management guidelines, example
• Schedule guidelines, example
• Funding guidelines, example
• Transition Management guidelines, process
  example, team example
• Programs, Plans, Budgeting, and Execution (PPBE)
  Strategy
• Year of Execution Reprogramming guidelines,
  example
• Budget guidelines, example
• Program Objective Memorandum (POM) Build
  guidelines, example
• Training Strategy / Methods guidelines, example
• Interoperability and Integration guidelines,
  example
• Security and Certification and Accreditation
  (CA) guidelines, example
• Intellectual Property (IP) guidelines, example

Action Oriented Facts To the Point
DAT
32
Management and Transition Plan Outline (contd)

• Networks / Equipment / Facilities / Ranges /
  Sites guidelines, example
• Organizational and Programmatic Approach
• Organizational Structure, Roles and
  Responsibilities guidelines, example
• Programmatic
• Schedule guidelines, example
• Supporting Programs guidelines, example
• Cost Plan by task and by FY guidelines,
  example
• Funding by source and by FY guidelines,
  example
• Acquisition and Contracting Strategy guidelines,
  example
• JCTD Risk Management and Mitigation Approach
  guidelines, example
• Summary and Payoffs guidelines, example
• Acronyms and Terms guidelines, example
• Glossary guidelines, example
• Related Documents guidelines, example

Action Oriented Facts To the Point
DAT
33
POR and / or Program or LOU Organization or
COCOM and / or Component or Combat Development
Command Detail Sheet Outline

• POR and / or Program or LOU Organization or COCOM
  and / or Component or Combat Development Command
  Title
• POR and / or Program or LOU Organization or COCOM
  and / or Component or Combat Development Command
  Description
• POC
• Transition Type
• Transition Products and Deliverables
• Key Transition Steps, Actions and Activities
• Transition Timeline
• Required additional funding (i.e., delta for
  certification and accreditation, follow-on
  development, production and fielding, operation,
  maintenance and / or publication)
• Major Issues and Solutions
• Technical, Cost and Schedule Risk

Action Oriented Facts To the Point
MTPO
34
Technology / 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

DAT
35
Integrated Assessment Plan (IAP)Outline

• Overview
• Purpose and Scope guidelines, example
• Coalition / Joint / Interagency Operational
  Problem guidelines, example
• Desired Capabilities guidelines, example
• Capabilities Solution guidelines, example
• Top Level CONEMP or CONOP guidelines, example
• Operational View-1 (OV-1) guidelines, example
• System View-1 (SV-1) guidelines, example
• Operational Assessment Approach
• Schedule guidelines, example
• Demonstration Venues and Participants
  guidelines, example
• Pre-Certification Opportunities and Aspects
  guidelines, example
• Procedures (aligned with TTP) guidelines,
  example
• Data Requirements and Resources guidelines,
  example
• Constraints (as applicable) guidelines, example
• Operational Utility Assessment Framework
• Coalition / Joint / Interagency Operational
  Problem guidelines, example
• Critical Operational Issues (COI) guidelines,
  example
• Top Level Capabilities Metrics guidelines,
  example

Action Oriented Facts To the Point
DAT
36
Integrated Assessment Plan (IAP)Outline (contd)

• Operational Utility Assessment Reporting
  guidelines, example
• Networks / Equipment / Facilities / Ranges /
  Sites guidelines, example
• Assessment Management
• Team guidelines, example
• Approach guidelines, example
• Acronyms and Terms guidelines, example
• Glossary guidelines, example
• Related Documents guidelines, example

Action Oriented Facts To the Point
DAT
37
Operational Utility Assessment(OUA) Report
Outline

• Overview
• Purpose and Scope guidelines, example
• Coalition / Joint / Interagency Operational
  Problem guidelines, example
• Desired Capabilities guidelines, example
• Capabilities Solution guidelines, example
• Top Level CONEMP or CONOP guidelines, example
• Operational View-1 (OV-1) guidelines, example
• Demonstration Venues and Participants
  guidelines, example
• Assessment Management Team guidelines, example
• Constraints guidelines, example
• Operational Utility Assessment Results
• Capabilities Impact on Coalition / Joint /
  Interagency Operational Problem guidelines,
  example
• Resolution of Critical Operational Issues (COI)
  guidelines, example
• Top Level Capabilities and Metrics Results
  guidelines, example
• Measures of Performance (MOP) Results and
  Measures of Effectiveness (MOE) guidelines,
  example
• Operational Deficiencies guidelines, example
• Summary / Conclusions and Recommendations
• Operational Utility Determination guidelines,
  example
• Transition, DOTMLPF, CONOP and TTP
  Recommendations guidelines, example

DAT
38
Final Reporting

• Main Activities
• Complete Limited Operational Use of Interim
  Capability effort if conducted
• Collect, organize and assemble JCTD documentation
  package
• Obtain 4 Star Champion memorandum supporting
  JCTD capability and transition
• Draft COCOM Senior Leadership memorandum to Lead
  Transition Service / Agency Programmer / Senior
  Acquisition Executive requesting POR / Program
  resourcing for transition
• Draft Final Report
• Submit Final Report to DUSD(ASC) and disseminate
  to COCOMs, Joint Staff, Services and Combat
  Development Centers
• Brief FCB, JCB, JROC on Final Report as
  appropriate
• Participants
• Leads Transition Manager with Operational
  Manager
• Supporting
• Technical Manager
• Oversight Executive, ODUSD(ASC)
• Interagency, International

Key Documentation Final Report
39
Final Report (FR) Outline

• Overview
• Purpose and Scope guidelines, example
• Coalition / Joint / Interagency Operational
  Problem guidelines, example
• Desired Capabilities guidelines, example
• Capabilities Solution guidelines, example
• Top Level CONEMP or CONOP guidelines, example
• Operational View-1 (OV-1) guidelines, example
• Organizational Structure, Roles and
  Responsibilities guidelines, example
• Accomplishments and Lessons Learned
• Capabilities Impact on Coalition / Joint /
  Interagency Operational Problem guidelines,
  example
• Demonstration Accomplishments guidelines,
  example
• Limited Operational Use Accomplishments if
  conducted guidelines, example
• Transition Accomplishments / Projection
  guidelines, example
• Lessons Learned guidelines, example
• Summary, Conclusions and Recommendations
  guidelines, example
• Acronyms and Terms guidelines, example
• Glossary guidelines, example
• Documentation guidelines, example
• Detailed Lessons Learned

FR
40
Position Roles and Responsibilities

• Operational Manager guidelines
• Technical Manager guidelines
• Transition Manager guidelines
• ODUSD(ASC) Oversight Executive guidelines
• Oversight Group guidelines
• ODUSD(ASC) Combatant Command Lead guidelines
• ODUSD(ASC) Joint Functional Capability Area
  Portfolio Lead guidelines
• COCOM JCTD Program Lead guidelines
• Independent Assessor guidelines
• Combat Development Command (CDC) Capability
  Manager (from Service or Agency) guidelines
• Resource Sponsor guidelines
• Financial Programmer guidelines
• Joint Functional Capability Representative (from
  Joint Staff FCB) guidelines
• COCOM or Component User Representative
  guidelines
• Service or Agency Representative guidelines
• Program Manager (Government or Industry)
  guidelines

41
Operational Manager

• Partner Community Operational and Acquisition
• Provides day-to-day operational direction
• Serves as member of IMT (OM, TM, XM, OE)
• Codevelops ID, Management and Transition Plan
• Manages and provides input on warfighter
  involvement
• Coordinate components and other COCOMs
  involvement
• Plans, schedules, executes operational
  demonstrations and exercises
• Develops Joint CONOP and TTP and functional
  requirements with user participation
• Develops DOTMLPF recommendations
• Plans and conducts Joint and coalition OUAs with
  support of the independent assessor
• Participates and contributes to transition
  planning
• Continues to support JCTD during LOU of interim
  capability
• Supports closeout and final reporting
• Serves as organizational POC Staff Officer for
  coordination of JCTD documentation
• Organizations COCOM

PRR
42
Technical Manager

• Partner Community Technology
• Provides day-to-day technical direction
• Serves as member of IMT (OM, TM, XM, OE)
• Codevelops ID and Management and Transition Plan
• Integrates and technically demonstrates the
  capability and applicable technologies
• Manages JCTD contract(s) and acquisition
  instruments
• Delivers the Joint capability solution to the OM
  for demonstration, exercises and assessment
• Participates and contributes to the OUA planning
• Participates and contributes to the CONOP and TTP
  development
• Manages Capability Solution
• Participates and contributes to transition
  planning
• Develops training plan and provides training
• Contributes to development of DOTMLPF
  recommendations
• Continues to support JCTD during LOU on interim
  capability, as needed
• Serves as JCTD financial manager
• Serves as organizational POC Staff Officer for
  coordination of JCTD documentation
• Organizations Deputy Assistant Secretary of the
  Army, Research Technology (DAS(RT)), Office of
  Naval Research (ONR), Air Force Research
  Laboratory, applicable Defense technology
  organization

PRR
43
Transition Manager

• Partner Community Operational and Acquisition
• Serves as Lead for Transition Team
• Provides day-to-day transition facilitation,
  collaboration and direction
• Serves as member of IMT (OM, TM, XM, OE)
• Co-develops ID, Management and Transition Plan
• Plans for and supports possible LOU of interim
  capability
• Leads development and configuration management of
  MTP Section IV Transition and Technology /
  Capability Transition Agreement (T/CTA)
• Participates and contributes to the OUA planning
• Participates and contributes to the CONOP and TTP
  development
• Identifies and facilitates funding for transition
  and LOU support
• Leads required document development (ICD, CDD,
  Capabilities Production Document CPD), as
  needed
• Leads budget and POM development for transition
  to acquisition and coordinates with Services and
  agencies
• Connects with OSD agile acquisition opportunities
  and DoD programs supporting transition
• Joint Capabilities Technology Demonstration
  (JCTD) BA4 Transition Defense Acquisition
  Executive (DAE) Pilot Program Defense
  Acquisition Challenge (DAC) Foreign Comparative
  Testing (FCT) Technology Transition Initiative
  (TTI) Quick Reaction Funds (QRF) Rapid Reaction
  / New Solution (RR/NS) Manufacturing Technology
  (ManTech) Mfg. ST
• Serves as organizational POC Staff Officer for
  coordination of JCTD documentation
• Organizations PEO / PMs

PRR
44
ODUSD(ASC) Oversight Executive

• Serves as SME and provides POG assistance for the
  JCTD life cycle to government industry and
  international management, coalition, and / or
  interagency team
• Serves as member of IMT (OM, TM, XM, OE)
• Coordinates and establishes priorities, evaluates
  alternatives, oversees funding requirements, and
  assesses programmatic feasibility
• Assesses program deficiencies and recommends
  remedies
• Oversees development, coordination,
  implementation of IDs, Management and Transition
  Plans, international cooperative project
  agreements, congressional correspondence and
  information documents
• Maintains liaison with executives of COCOMs,
  Services, OGAs, industry, professional
  associations, academia and international MoD s.
• Chairs teams consisting of members from the OSD,
  Joint Staff, COCOMs, Services, defense agencies
  and industry
• Defends JCTD with Congress, DoD Leadership,
  Government Accountability Office (GAO), and other
  stakeholders
• Serves as organizational POC Staff Officer for
  coordination of JCTD documentation
• Organizations OSD

PRR
45
Oversight Group

• Established for each JCTD
• Chaired by the DUSD(ASC) or Director, JCTD
  Program or his / her primary representative and
  primarily includes Senior / FO / GO level
  decision-makers / stakeholders representing the
  operational, technical and transition management
  areas
• Provides a collaborative decision making forum on
  an annual or as needed basis to
• Review in-process status
• Address and resolve senior level issues presented
  by JCTD Integrated Management Team
• Provide guidance and direction on execution of
  JCTD including such areas as major funding,
  schedule, organizational and / or programmatic
  changes
• Renders decisions that could accelerate,
  maintain, extend or terminate a JCTD

PRR
46
ODUSD(ASC) Combatant Command Lead

• Understands prioritized COCOM operational needs,
  including
• Annual COCOM IPL submissions and Joint needs
  (e.g., JUONS, other)
• Component needs
• Lessons learned based on operations or exercises
• Connects with (DDRE) agile acquisition
  opportunities and programs
• Joint Capability Technology Demonstration (JCTD)
  Joint Experimentation (JE) and Joint Prototyping
  Joint Advance Warfighting Program (JAWP)
  Technology Transition Initiative (TTI) Program
  Defense Acquisition Challenge (DAC) Program
  Foreign Comparative Testing (FCT) Program
  Coalition Warfare Interoperability Demonstration
  (CWID) Program Defense Adaptive Red Team (DART)
  Quick Reaction Special Projects (QRSP) Joint
  Rapid Acquisition Cell (JRAC) Rapid Equipping
  Force (REF) Research and development programs at
  agencies (e.g., DARPA, DTRA, DISA)
• Coordinates between COCOM staff, DDRE and ASC
• ASC participation in annual COCOM conferences
• Other significant visits / meetings (e.g., Joint
  Staff hub trips, DDRE and ASC staff visits to
  COCOMs, COCOM staff visits to DDRE and ASC,
  COCOM attendance at JCTD candidate reviews and
  Functional Capability Board
• Items of Interest (e.g., status of COCOM
  proposals, technology push opportunities)
• Coordinates high-level COCOM, DDRE and ASC
  communications
• PERSONAL FORs, calls for proposals, senior
  oversight reviews, other formal communications)
• Conducts routine, day-to-day interactions with
  COCOM POCs
• As requested by COCOM staff, presents COCOM
  interests in JCIDS

PRR
47
ODUSD(ASC) Joint Functional CapabilityArea
(JFCA) Portfolio Lead

• Coordinates with the Joint Staff and others in
  the JCIDS process for designated JFCA portfolios
  including
• Working closely with the ASC OE assigned to JCTD
  candidate proposal throughout JCTD life cycle to
  ensure appropriate visibility and interface are
  maintained within the parameters of JCIDS
• Continual coordination with the COCOM
  representative to ensure the equities of the
  COCOM(s) are being accurately and energetically
  pursued in the JCTD and in the JCIDS process.

PRR
48
COCOM JCTD Program Lead

• Partner Community Operational and Acquisition
• Serves as the lead for the COCOM JCTD Program
• Oversees coordination of components and other
  COCOMs involvement
• Assists COCOM J-codes in identification and
  submission of new JCTD candidates
• Coordinates COCOM rating and ranking of JCTD
  proposals through COCOM
• Monitors individual JCTD and overall JCTD program
  portfolio performance transition
• Maintains COCOM JCTD records and documentation
• Represents COCOM to DUSD(ASC) and other COCOMS
  on JCTD issues
• Provides direct assistance to JCTD teams
  developing proposal to include submittal and
  partnership development
• Reviews and approves JCTD IDs and MTPs
• Provides necessary assistance to operational
  managers
• Coordinates COCOM staff participation in annual
  JCTD Oversight Group reviews
• Responsible for planning and execution of the
  COCOM annual JCTD review
• Assists DUSD(ASC) staff with understanding COCOM
  needs and capability gaps and reporting of JCTD
  information
• Attends and participates in Candidate Review
  Board, Managers Conference, and other COCOM
  conferences
• Serves as organizational POC Staff Officer for
  coordination of JCTD documentation
• Organization COCOM

PRR
49
Independent Assessor

• Reports directly to OM
• Drafts overall Operational Utility Assessment
  (OUA) strategy and framework
• Develops and coordinate Integrated Assessment
  Plan (IAP)
• Develops and coordinate Demonstration Execution
  Document (DED) / Assessment Execution Document
  (AED), as needed, in support of IAP
• Prepares and execute data collection plan
  (quantitative and qualitative)
• Conducts raw data collection using general or
  specially designed test equipment
• Issues and conduct surveys, questionnaires
• Provides technical analysis of demonstrations /
  assessments results
• Drafts and coordinate I / OUA Quicklook Reports
• Drafts Limited Operational Utility Assessment
  (LOUA) and OUA Reports including DOTMLPF
  recommendations
• Assists in planning and scheduling assessment
  events / exercises
• Trains assessment observers and supplementary
  data collectors
• Participates as appropriate in meetings of the
  OM, TM and XM

PRR
50
Combat Development Command (CDC)Capability
Manager

• Partner Community Requirements Definition and
  Financial Programming
• Provides Joint and Services-based capabilities
  definition and guidance
• Leads and directs required document update or
  development (ICD, CDD, Capabilities Production
  Document CPD), etc., as needed
• Serves as advisor and member of Transition Team
• Co-develops MTP Section IV Transition and T/CTA
• Leads development and provides DOTMLPF baselines
  and changes
• Serves as organizational POC Staff Officer for
  coordination of JCTD documentation
• Organizations TRADOC, ACC, MCCDC, FFC, JFCOM

PRR
51
Resource Sponsor

• Partner Community Requirements Definition and
  Financial Programming
• Serves as headquarter resource provider
• Serves as co-transition decision-maker with
  applicable acquisition decision authority
• Serves as member of Transition Team
• Co-develops Transition Plan and Technology /
  Capability Transition Agreement (T/CTA)
• Serves as organizational POC Staff Officer for
  coordination of MTP Section IV Transition and
  T/CTA
• Organizations G-8, HQDA N-8, OPNAV A-5/A-8,
  USAF HQUSMC, PR J-8A, SOCOM, Defense agencies

PRR
52
Financial Programmer

• Partner Community Requirements Definition and
  Financial Programming
• Serves as headquarter financial planner and
  programmer of funding based on Resource Sponsor
  prioritization and decisions to support TP and
  T/CTA
• Year of Execution Reprogramming
• Budget Estimate Submits and / or R2 Exhibits
• POM Development and Build to include FYDP
• Serves as member of Transition Team
• Co-develops MTP Section IV Transition and T/CTA
• Leads development of Business Case Analysis

PRR
53
Joint Functional Capability Representative

• Partner Community Requirements Definition and
  Financial Programming
• Serves as Joint Staff JCIDS subject matter expert
  for applicable Joint Functional Capability Area
  (JFCA) information
• Applicability to JFCs, JICs, JOps, JOCs, JCD
• Joint JFCA relevance
• Serves as advisor / member of Transition Team
• Stewards required ICD / CDD / CPD through JCIDS
  process
• Co-develops MTP Section IV Transition and T/CTA
• Serves as organizational POC Staff Officer for
  coordination of JCTD documentation
• Organizations Functional Capability Boards (FCB)

PRR
54
COCOM or Component User Representative

• Transition Partner Community Dual hatted in
  Requirements Definition and Financial
  Programming, and Operational and Acquisition
  partner communities
• Understands prioritized COCOM operational needs,
  including
• Annual COCOM IPL submissions and Joint needs
  (e.g., JUONS, other)
• Component operational needs
• Lessons learned based on operations or exercises
• Serves as member of Transition Team
• Co-develops MTP Section IV Transition and T/CTA
• Coordinates high-level COCOM or Component and OSD
  communications
• PERSONAL FORs, calls for proposals, senior
  oversight reviews, other formal communications
• Presents COCOM or Component interests in JCIDS
  process
• Leads development of Type O Overall Strategy and
  Operational Organization Detail Sheet information
• Serves as organizational POC Staff Officer for
  coordination of MTP Section IV Transition and
  T/CTA
• Organizations COCOM J-Codes and Component HQs

PRR
55
Service or Agency Representative

• Transition Partner Community Dual hatted in
  Requirements Definition and Financial
  Programming, and Operational and Acquisition
  partner communities
• Understands prioritized Service / Agency
  technology and modernization needs
• Annual ST and Modernization Plans
• Coordinates ST priorities, evaluates
  alternatives, oversees funding requirements, and
  assesses programmatic feasibility
• Assesses program deficiencies and recommends
  remedies
• Oversees development, coordination,
  implementation of ST correspondence and
  information documents
• Maintains liaison with executives of COCOMs,
  Services, OGAs, industry, professional
  associations, academia
• Serves as member of Transition Team
• Co-develops Transition Plan and Technology /
  Capability Transition Agreement (T/CTA)
• Coordinates high-level Services and Defense
  Agency communications
• PERSONAL FORs, calls for proposals, senior
  oversight reviews, other formal communications
• Serves as organizational POC Staff Officer for
  coordination of JCTD documentation
• Organizations DAS(RT), ONR, AQR, applicable
  technology or laboratory organization

PRR
56
Program Manager (PM)

• Transition Partner Community Operational and
  Acquisition
• Serves as the POR / Program SME
• Serves as member of Transition Team
• Co-develops Transition Plan and Technology /
  Capability Transition Agreement (T/CTA)
• Leads development of Type A, D or I Overall
  Strategy, POR / Program Detail Sheet and
  Configuration Management information
• Ensures optimum program execution blends with
  best value to warfighter / taxpayer
• Serves as organizational POC Staff Officer for
  coordination of TP and T/CTA
• Organizations Applicable PEO / PMs

PRR
57
JCTD DUSD(ASC) Funding

• Critical component for successful JCTD execution
• More in first two years to allow Services /
  agencies to program for remaining years including
  transition
• Can be greater than 30 of total JCTD funding
• Not more than 8M per year without special
  DUSD(ASC) approval
• Defined by Proposal Package, Implementation
  Directive (ID) and Management and Transition Plan
  (MTP)
• DUSD(ASC) funding release requirements for
• First year funding DUSD(ASC) and all partners
  approve ID
• Up to 50 while ID in coordination to decrease
  start-up time if approved by ODUSD(ASC) OE and
  Director, JCTD Program
• Second year funding Dir. JCTD Program and
  leaders of execution players approve MTP 90 days
  after approved ID
• Up to 50 of second year funding can be released
  if MTP approval is considered imminent
• Budget Activity 4 (BA-4) Program Element (PE) for
  Transition
• Budget Activity 5 (BA-5) PE for Defense
  Acquisition Executive (DAE) Pilot program
• Limited amount of procurement funding to sustain
  successful, very mature (i.e., TRL 7 or greater)
  Joint-peculiar projects until transition
  accomplished

58
DoD Programs Supporting Transition and Agile
Acquisitions
59
Contact Information
ASC www.acq.osd.mil/asc 703-695-5036 JCTD htt
p//www.acq.osd.mil/jctd 703-697-5558