UNCLASSIFIED Joint and Coalition Warfighting Mr. John Vinett March 2012 Technical Baseline Capability
UNCLASSIFIED
Joint and Coalition WarfightingJoint and Coalition Warfighting
Mr. John VinettMarch 2012
Technical Baseline Capability
UNCLASSIFIED
Issue 11-010: Lack of a defined technical baseline to support Joint Force Development has resulted in duplication and inefficiency in the community.
Discussion: The current technical baseline supporting Joint Force Development is not formally documented. As a result, development efforts are initiated without reviewing the baseline to determine if capability already exists, if it is planned, or if it is required. In a resource constrained environment we must describe what Joint capabilities we currently have to determine where we are going based on what we need.
Endstate: A collaborative, disciplined process to establish and control the baseline to enable efficient management and effective use of research and technologies in support of Joint Force Development
POA&M: Clarify intent and guidance, establish collaborative forum to define the baseline, determine baseline requirements, develop initial baseline, identify resource implications, and present to Stakeholder Leadership Team for approval.
OPR: JS J-7 JCW (JOSE); OCRs: CCMDs, Services
SEP 11
Briefer: Mr VinettInitiated 26 Sept 11
Joint Force Development Tech Baseline
UNCLASSIFIED
UNCLASSIFIED
SEP 11
Clarify intent and guidance
Establish collaborative forum
OCT 11 DEC 11
Develop initial draft baseline
JAN 12
Identify resource implications
Present refined baseline to Stakeholders (World Wide)
MAR 12
Identify issue
NOV 11
DJ7 azimuth check
FEB 12
Refine baseline
Updated 23 Feb 12
2
UNCLASSIFIED
Purpose
3
• To develop a Technical Baseline that defines each technical end item, its sub-product and its dependencies. Define resources allocated that include manpower, equipment, and funding. Define strategies for each technical end item through FY13. Used to develop roadmaps and build capability that maintains a relevant product on a periodic basis
• Endstate: A collaborative tool of tools which leverages existing processes that clearly defines the organizations capabilities, its requirements and future strategies.
Unclassified
UNCLASSIFIED
Baseline Definition (RIE)
4
• Technical Baseline - All aspects and activities that comprise a total technical capability. This includes component software, IA, Documentation products, Functionality, Performance and Services (JLVC/JTEN).
• Operational Baseline - Subset of a technical baseline that is in operational use by capability users (JLVC 5.0/JTEN 1.0).
• Developmental Baseline - Subset of a technical baseline that is in development for future use (JLVC 6.0/JTEN 2.0).
Unclassified
UNCLASSIFIED
Why?
5
• Provide Clear definition for start point for JF2020
• Reduce duplicative functionality
• Identify capabilities to migrate to Services
• Implement a Configuration Control Discipline
Unclassified
UNCLASSIFIED
Baseline Products
6
Lower Enclave – Collateral Secret
DRRSReadinessReporting
JTIMSTraining Objectives
JMSEL
JDLM
DESSTRANSCOM
LogisticsFederation
Logistics Models
ABS
TENA InstrumentedRanges
GamingVBS2
JLVCCore Simulations &
Support Tools
JMECS
JECS
LOTS
JAWSJSPA
JMEM
JT
EN
/ DIS
Ne
two
rk
RTI (JLVC/ERF FOM)
JLOD
JLVC Bridge
JTDS
JCATS
JAAR-RLJTLS
LEGENDAir ForcePrimarily Army & Shared
Navy
Marine Corps
NRO
Primarily Joint & Shared
NSA
FY11-13
WIMIntel
Model
Intel Models
BEServer
ACE-IOS
NWARS-NG
IWMDT
DTRA
MDA
ACE-IOS
SIGINT Model
NSANet
JWICS
Upper Enclave - TS / SCI
RadiantMercury
TIUBallistic
Missile Sim
IAMD & Space Models
SSG/GEGGPS
Simulation
TDACSBallistic
COCOM
Virtual Simulators
AFSERS-MUSEVirtual ISR
ImageryWES
VRSG
MUSE-CSS
VIPRS
Virtuals
JLCCTCWARSIMArmy
C2 Network
AWSIMUSAF
NCTE
JSAFUSN
MTWSUSMC
Service Combat ModelsExCIS
Sarty
JLVC 6.0 Enterprise
DE-SimMDST
IAMD Model
OneSAFArmy
Unclassified
UNCLASSIFIED
Way Ahead
Clarify the capabilities required to meet Baseline objectives Add Use-Case to ClearQuest Identify Users and their, roles, requirements and responsibilities Validate Database construct Identify key decision, managing and informing events Design Reports for key information and decision points throughout the
lifecycle• Status update (i.e. Traffic Light depiction)
• COA analysis (i.e. Budget call/constraints)
Report Timing (Synchronous & Adhoc) Other Use-Case Scenario’s
7Unclassified
UNCLASSIFIED
POA&M
WJTSC (Issue Initiated) 26 Sep 2011 Stand-up Baseline WG (Weekly) 29 Sep 2011 Define draft Tech End items 06 Oct 2011 John Vinett TECH BL brief-back 07 Oct 2011 Define draft Criteria (WG) 13 Oct 2011 Toni Cerri TECH BL discussion 14 Oct 2011 Brief back WG (Major End items) 20 Oct 2011 Collaboration with services 27 Oct 2011 Brief S&I Leadership 18 Nov 2011 Initial ED draft complete (what we do) 18 Nov 2011 Collaborate with all JOSE Branches 1 Dec 2011 Begin CONOPS development 1 Dec 2011 Develop Budget Use-Case 12 Jan 2012 Initial JOSE draft baseline complete 10 Feb 2012 Brief S&I Leadership mid Feb 2012 Recommended Way ahead WJTSC
8Unclassified
UNCLASSIFIED
Issue 11-010: Lack of a defined technical baseline to support Joint Force Development has resulted in duplication and inefficiency in the community.
Discussion: The current technical baseline supporting Joint Force Development is not formally documented. As a result, development efforts are initiated without reviewing the baseline to determine if capability already exists, if it is planned, or if it is required. In a resource constrained environment we must describe what Joint capabilities we currently have to determine where we are going based on what we need.
Endstate: A collaborative, disciplined process to establish and control the baseline to enable efficient management and effective use of research and technologies in support of Joint Force Development
POA&M: Clarify intent and guidance, establish collaborative forum to define the baseline, determine baseline requirements, develop initial baseline, identify resource implications, and present to Stakeholder Leadership Team for approval.
OPR: JS J-7 JCW (JOSE); OCRs: CCMDs, Services
MAR 12
Briefer: Mr VinettInitiated 26 Sept 11
Draft Revised Tech Baseline
UNCLASSIFIED
UNCLASSIFIED
APR 12
Clarify intent and guidance
Establish collaborative forum
MAY 12 JUL 12
Develop initial draft baseline
AUG12
Identify resource implications
Present refined baseline to Stakeholders (World Wide)
OCT 12
Brief status to M&S WG
JUN 12
DJ7 azimuth check
SEP 12
Refine baseline
Updated 21 Mar 12
9
UNCLASSIFIED
BINS
12
Strategy and VisionStrategy and vision includes documents, processes, and guidelines that support the future development of the Joint Training Environment. This line of operation receives and manages requirements from the stakeholders and provides insight back to those stakeholders so they can understand how their individual requirements fit into the larger picture of future development. Joint Live Virtual Constructive FederationThe JLVC is the total of the products that are produced or integrated by the JOSE to provide the environment supporting training and concept development. It includes federates (individual simulations), infrastructure (simulation framework), and user tools (C2 integration, exercise control, etc.). ProjectsProjects represent specific efforts directed by and funded under the Strategy and Vision to achieve the goals of the stakeholders with respect to the Joint Training Environment. These lines of operation include the development of new capabilities for the simulations and the integration of Service simulation capabilities into the environment where they can be shared across the Joint Training Enterprise. ServicesServices are specific, ongoing technical services provided by JOSE to support Service and COCOM stakeholders and customers. These lines of operation are conducted under the guidance of the Strategy and Vision to ensure that common requirements are paid for once, and leveraged across the Joint Training Enterprise. InfrastructureInfrastructure represents the backbone upon which the Joint Training Environment rides. It includes the networks and control structures to support Joint, Service, and COCOM exercises and experimentation. This line of operation also includes integration to support Joint acquisition in the Test and Evaluation domain. Standards and TestingStandards and Testing provide the validation that the JLVC, Projects, Services, and Infrastructure meet the requirements of the Strategy and Vision. This line of operation includes integration with the DoD, academic, and industrial bases to identify, implement, and guide the development of standards that support interoperability of the JCW products across the Joint Training Environment.