unclassified 1 united states joint forces command united states joint forces command joint...
TRANSCRIPT
UNCLASSIFIED
1
United States Joint Forces CommandUnited States Joint Forces CommandJoint Perspectives on Joint Perspectives on
Capability DevelopmentCapability Development
United States Joint Forces CommandUnited States Joint Forces CommandJoint Perspectives on Joint Perspectives on
Capability DevelopmentCapability Development
M. Kim FrisbyUSJFCOM/J89 Joint Architectures andCapability Engineering Division
2UNCLASSIFIED
The United States Joint Forces Command provides mission-ready Joint Capable forces and supports the development and
integration of Military, Government, and Multinational capabilities to meet the present and future operational needs
of the Joint Force.
Joint Forces Command Mission
3UNCLASSIFIED
The Challenge
Deconflicted Coordinated IntegratedINDUSTRY/ACADEMIA
MULTINATIONAL
INTERAGENCY
JOINT
INDUSTRY/ACADEMIA
MULTINATIONAL
INDUSTRY/ACADEMIA
MULTINATIONAL
INDUSTRY/ACADEMIA
MULTINATIONAL
INTERAGENCY
JOINT
Build the right numbers Provide the right equipment Provide the right guidance Be able to operate together with Partners
• US and Multi-national• Military and Civilian
4UNCLASSIFIED
Commander’s Guidance
• Jointness is not a natural state – deserves our best Jointness is not a natural state – deserves our best efforteffort
• Our enemy means every word it saysOur enemy means every word it says
• We will fight future wars with partnersWe will fight future wars with partners
• Our military must improve capability in the irregular Our military must improve capability in the irregular fightfight
• Maintain our conventional dominance Maintain our conventional dominance
Reshape our forces to fight a new way of war
5UNCLASSIFIED
JFCOM Lakeview Tech Park
Training
Experimentation
Laboratory
Federal Government
Army
Army Training & Doctrine and Capabilities Integration Center
Industry
Organizing for Synergy – JFCOM Model
Universities
Military, Industry, Academia, Government, and other Nations Located Together
Partner Nations
Navy
Marines
JFCOM
HeadquartersJFCOM in
Suffolk1” = 5 miles
1” = 8 kilometers
Air Force,and Multi-Service Tactics, Techniques & Procedures
6UNCLASSIFIED
• Developing joint concepts and experimenting Developing joint concepts and experimenting
• Find out what works for the futureFind out what works for the future
• Ensuring military systems “talk” to each other Ensuring military systems “talk” to each other
• Fixing those that don’t, making new systems that doFixing those that don’t, making new systems that do
• Training Joint Forces Training Joint Forces
• From Headquarters Staffs to IndividualsFrom Headquarters Staffs to Individuals
• Providing deployable joint teamsProviding deployable joint teams
• A team available “right now” to meet Commander’s immediate needsA team available “right now” to meet Commander’s immediate needs
• Providing Joint ForcesProviding Joint Forces
• Right mix of forces and equipment to get the job doneRight mix of forces and equipment to get the job done
USJFCOM ApproachSupporting the Joint Commander
7UNCLASSIFIED
39,600 Marines (RC)
51,579 Marines 2,671 Sailors
1 Division1 Wing1 MLG
MARFORCOM
545,000 Soldiers (RC & NG)
195,000 Soldiers
7 Divisions35 BCTs
FORSCOM
19,382 Sailors (RC)
101,000 Sailors
6 CSGs 5 ESGs
USFF
57,357 Airmen (RC & NG)
83,652 Airmen
26 F/B/CompWings
ACC
1.1 Million Soldiers, Sailors, Airmen, and Marines
Over 80% of US-based General Purpose Active and Reserve Forces
Joint Forces Command Components
8
19 Nations with Bilateral MOU/A with USJFCOM - 29 Representatives (Exchange/Foreign Liaison Officers)
7 Nations pursuing Bilateral MOU/A with USJFCOM3 Visitors/Representatives at JFCOM
Brazil1 (USFF)
Mexico1 (USFF)
Jordan1 (J7) (Gapped)
Sweden2 (J9/JPRA)
UK3 (J7/J8/J9)
Singapore1 (J9) (Gapped)
Morocco 1 (J7)
Poland1 (J9)
Romania 1 (J7)
ROK3 (J7/J9)
Sweden1 (ACT)
Australia1 (J8)
Canada2 (J7/J9)
Finland2 (J8/J9)
Germany3 (J9)
Israel 1 (J9)
Denmark1(J9)
Japan2 (J8/J9)
Hungary1(J9)
Italy1(J9)
Pakistan (J7)
Thailand
Spain1 (J9)
Algeria France 2 (J7/J9)
Greece 1 (J9)
Portugal1 (J9)
Czech Republic
Qatar
3 Nations with “Additional-Duty” Relationship with USJFCOM - 3 Representatives
Additional Opportunities for Multi-National Collaboration - NOT attached to USJFCOM23 NATO Nations with Local National Liaison Representatives (NLR) to Allied Command Transformation - 35 Representatives
Belgium1
Bulgaria2
Canada1
Czech Republic2
Denmark1
Estonia1
France2
Germany2
Greece1
Hungary2
Italy2
Latvia1
Lithuania1
Netherlands1
Norway2
Poland2
Portugal1
Romania2
Slovakia2
Slovenia2
Spain2
Turkey1
UK1
10 Partnership for Peace Nations with NLR to ACT - 10 Representatives
Austria1
Albania1
Armenia1
Azerbaijan1
Finland1
FYROM1
Croatia1
Switzerland1
1 Partnership for Peace Nation1 Representative (not NLR)
Sweden1
Ukraine1
7 Latin American Nations at U.S. Fleet Forces Command - 7 Representatives
Argentina1
Brazil1
Chile1
Ecuador1
Mexico1
Peru1
Colombia1 (Gapped)
Georgia1
USJFCOM Multi-National Collaboration
9UNCLASSIFIED
Maintain a Bias for Action
Current Efforts…
• Continue Focused Support to Win the Current WarsContinue Focused Support to Win the Current Wars• Improve Global Force Management ProcessImprove Global Force Management Process
• Maintain our Conventional Superiority and Improve Maintain our Conventional Superiority and Improve Capability in the Irregular FightCapability in the Irregular Fight
• Improve Joint Command and ControlImprove Joint Command and Control• Leader centric, network enabledLeader centric, network enabled
• Support our PartnersSupport our Partners• Multi-national, US, military and civilianMulti-national, US, military and civilian
• Maintain Deployable Operational HeadquartersMaintain Deployable Operational Headquarters
10UNCLASSIFIED
Joint Capability Development Directorate
Joint Capability Developer• Joint Capability Requirements
• Joint ArchitecturesJoint Architectures• Data Strategy
• Joint Integrated Fires
• Rapid Capability Transition
Joint Capability Developer• Joint Capability Requirements
• Joint ArchitecturesJoint Architectures• Data Strategy
• Joint Integrated Fires
• Rapid Capability Transition
C2 Capability Portfolio Management (C2 CPM)
• Collaborative, inclusive partnerships with COCOMs/Services/Agencies/M-Natl• Engage across DOTMLPF-P Spectrum • Increase interoperability & operational effectiveness for C2 stakeholders
Joint Capability Developer• Joint Capability Requirements
• Joint ArchitecturesJoint Architectures• Data Strategy
• Joint Integrated Fires
• Rapid Capability Transition
Operational Sponsor for Global C2 Systems-Joint (GCCS-J) and Net-Enabled Command Capability (NECC)
• Joint Combat Capability Developer (JCCD)
• Direct coupling of capability requirements to DISA & Services as material developers
• DOT_LPF-P (Non-material) Integration Focus
• End-to-End Warfighter Engagement
C2 Capability Portfolio Management (C2 CPM)
• Collaborative, inclusive partnerships with COCOMs/Services/Agencies/M-Natl• Engage across DOTMLPF-P Spectrum • Increase interoperability & operational effectiveness for C2 stakeholders
DOTMLPF-P = Doctrine, Organization, Training, Material, Leadership & education, Personnel, Facilities and Policy
11
UNCLASS\\FOUO
UNCLASS\\FOUO
J8 JCD
J8J8
J88 - JCCDJ88 - JCCD
JFIITJFIIT
J82-Joint Mgt Office
J82-Joint Mgt Office
“J8 JCD Engine”
Maj Gen Kennedy
J8AJ8AMaj Gen Rajczak
J8BJ8BMr. Whitehead
Capt DeMane
Travel & BudgetTravel & Budget
Laurie Redmond
J85-Capability RequirementsJ85-Capability Requirements
Danny Allen
J89-Joint Architectures
J89-Joint Architectures
Kim Frisby
J86-Capability Transition
J86-Capability Transition
CAPT Ruce
J87-Info Integration
J87-Info Integration
Leslie Winters
John Wellman
JSICJSICJ83-Capability Resource MgtJ83-Capability Resource Mgt
Rob Borders
J84-Joint T&EJ84-Joint T&E
Randy Coonts
CAPT DeMane
COSCOS
J8VJ8VJ8SCJ8SCBrig Gen Shook
J8FJ8FMr. Westphal
COL Hambrecht COL Nelson
12
Architecture Integration BranchCapability Architects Data Base Admin
Sys Admin
Help Desk
Standards&
Policy BranchJTF Architecture
ArchitectureSupport
Capability Engineering
JCCD ArchitectureSupport
Joint C2 Architecture and Capability Analysis Enterprise (JACAE)
Warfighter Product Support
C2 CPM
JCIDS JTF Sustainment
& Certification
Executable Architectures
PPB&E Analysis
Tailored Reporting
Architecture Federation
J89 Organization
Unclassified 13
Shaping & Assessing C2 Capability Shaping & Assessing C2 Capability Example: Net-Enabled Close Air SupportExample: Net-Enabled Close Air Support (Digital CAS) (Digital CAS)
Leader - CentricOperational Thread:
CAS
Joint Fires Observer
Joint Terminal Attack Controller
Pilot
DOT_LPF-P Solutions
AssessmentsExercises - Training
M2M “9-Line”
M2M Coordinates
Laser Target Designation
KPP=Key Performance Parameters
Interoperability of Disparate Systems
Integration of Uniformed Services
Net - EnabledNet-Enabling Systems:
Net-Ready KPPs
Material Solutions
Assessment Gap?
Requirement
Gap?
Universal Joint Tasks
ArchitectureArchitectureRoleRole
Operational ActivitiesOperational Activities
Systems FunctionsSystems Functions
Joint StaffJ7 Mapping
Architectures
Analysis
Accreditations
Concepts/Plans
Assessments
Policy
Standards
Policy
Standards
Policy
Standards
Policy
Standards
Policy
Standards
Policy
Standards
Operational
Programmatic
Technical
Documentation
Policy
Standards
Joint Integration& Interoperability
Recommendations via DetailedDetailed
DOTMLPF Analysis
Policy
Standards
Joint Capability Areas (JCAs)Joint Capability Areas (JCAs)
Other CPMs
C2 Portfolio*C2 Portfolio*
- Programs of Record - Systems - Sub-systems - New Capabilities
JCAs- to- PECsJCAs- to- PECs
PA&EMapping
CPM AreasCPM Areas
Capability Mapping BaselineCapability Mapping Baseline““Periodic Table” for Operational DOTMLPF-P AnalysisPeriodic Table” for Operational DOTMLPF-P Analysis
NCES/NECC
USAFUSA
USMC
USN
Joint CommonSystem Functions
List (JCSFL)
JTF OperationalActivities / Tasks / Sub-tasks
Tier I
UJTLSN X.XST X.XXOP X.X.XTA X.X.X.X
Joint Warfighter Billets
Authoritative Sources:
AUTLs, MCTL, NTTL, AFTL
TT(Training)
MM(Materiel)
LL(Leadership)
PP(Personnel)
Platforms/Weapons
Applications/Services
ADS & Data Models
Networks/Comms
PP(Policy)Joint TasksJoint Tasks
Service TasksService Tasks
OpNodesOO(Organization)
Operational Nodes & Billets Operational Nodes & Billets
DD(Doctrine)
FF(Facilities)
Leader-CentricLeader-Centric
Net-EnabledNet-EnabledJCAsJCAs
JCAsJCAs
UNCLASS\\FOUO
UNCLASS\\FOUO
Joint Common System Function List (JCSFL)Joint Common System Function List (JCSFL)Joint Common System Function List (JCSFL)Joint Common System Function List (JCSFL)
POC: John AndreJ89 Standards & Policy [email protected]
POC: John AndreJ89 Standards & Policy [email protected]
- Embedded in Joint Architecture and Capability Enterprise (JACAE) Catalog for reuse in integrated architectures – web service deployed in July 2009
- Prescribed by CJCSI 6212.01E (15 Dec 08) for capability development- Version 2.0 – July FY09 release, normalized with Navy CSFL v4.0
Provides a common lexiconcommon lexicon of system functions, supporting development of enterprise and solution architectures, and capability assessments across the DoD
AKO/DKO Portal: https://www.us.army.mil/suite/page/419489
16
DOTMLPF Analysis
Ideas for Material
Approaches
IntegratedArchitecture
System
Function YYY
System
Function YYY
Systems Systems A, C, FA, C, F
SystemNode
SystemNode
Activity XXXX
Activity XXXX
Capability
System ASystem A System BSystem B System CSystem C
Systems of Record OR Potential New Systems
Measures of Effectiveness and Performance attributes
How well system enables desired capabilities
Common System Common System Function Lists Function Lists required!required!
Candidate systems & specific functions
SystemSystemSystem DSystem D SystemSystemSystem ESystem E SystemSystemSystem FSystem F SystemSystemSystem GSystem G
* *
*
Why Do We Need a JCSFL?Why Do We Need a JCSFL?
It is essential to use a common system function lexicon to develop and integrate joint architectures and to support horizontal & vertical assessment of C2 capabilities
Activity XXXX = Sys Func YYY performed by Systems A, C, & F
17Unclassified
17
Net-Ready Key Performance Parameter (NR-KPP) Net-Ready Key Performance Parameter (NR-KPP) Elements in CJCSI 6212.01EElements in CJCSI 6212.01E
Solution Solution ArchitecturesArchitectures
Solution Solution ArchitecturesArchitectures
Net-Centric Net-Centric Data and ServicesData and Services
Net-Centric Net-Centric Data and ServicesData and Services
InformationInformationAssuranceAssuranceInformationInformationAssuranceAssurance
GIG Standards GIG Standards ComplianceCompliance
GIG Standards GIG Standards ComplianceCompliance
Evaluate compliance with Standards and applicable GIG Enterprise Service Profiles
Verify C&A status, and that IOP testing is conducted using the approved IA configuration
Evaluate visibility, accessibility, understandability and compliance to DoD Information Enterprise Architecture
DoDAF Operational & Systems/Services Views, DoD IEA,Joint Common Systems Function List (JCSFL)Joint Common Systems Function List (JCSFL)
11
SupportabilitySupportability(Spectrum, JTRS, SAASM, TDL Implementations)(Spectrum, JTRS, SAASM, TDL Implementations)
SupportabilitySupportability(Spectrum, JTRS, SAASM, TDL Implementations)(Spectrum, JTRS, SAASM, TDL Implementations)
Verify programs comply with respective policy and guidance
Interoperability Certification is based on NR-KPP Requirements in Capability-Based Acquisition Documents
18
19
20
21
• A collaborative environment and repository for the development of reusable joint integrated architectures
• Employment of a standard framework and repeatable processes to:
Generate reusable operations, systems, technical architecture & capability standards
Integrate and develop enterprise reference architecture data for joint warfighting mission areas
• Support to USJFCOM, COCOM, Services, and Agencies through federated information sharing
The Joint Command and Control (JC2) Architecture and Capability
Assessment Enterprise (JACAE)
22
23
24
25
26Unclassified
Capability Information Sharing Challenges Capability Information Sharing Challenges
• Lack of “master, federated database” for JCIDS documents, including the e-ISP
• Inability to exchange information elements that keep lexicon, taxonomy, and ontology in-tact
• “Atomic Elements” of information exchange are not in-place to allow for dynamic re-composition, according to end-user requirements
Architecture Federation Pilot –Architecture Federation Pilot – Addresses Capability Information Sharing Gap for Addresses Capability Information Sharing Gap for
Joint Warfighting MissionsJoint Warfighting Missions
27
UNCLASS\\FOUO
Unclassified27
Federation BackgroundFederation Background
• Decision makers at all levels of the DoD require access to the information provided by architectures in order to make informed decisions
• Standards and guidance have existed to some extent for architecture development, however:– The tools methods for storing and sharing the data vary greatly
between organizations.
– Enormous amounts of architecture data has been collected in stove-piped, proprietary environments.
• As an example JFCOM’s architecture environment that is rich with information designed to support standing up and certification of a Joint Task Force HQ
Use of proprietary, stove-piped environments has hampered collaborative architecture development
28
UNCLASS\\FOUO
Unclassified28
Architecture Federation PurposeArchitecture Federation Purpose
• Maximize limited resources and eliminate and reduce duplication of effort
• Improve the speed of development, accuracy, and currency of reusable architecture information
• Share Data Between Various Organizations, Tools and Environments – Encourage more effective collaboration– Create more efficient architecture development and
analysis processes in support of DoD initiatives – Improve relevancy to key decision processes (JCIDS,
POM, etc.)
29
UNCLASS\\FOUO
Unclassified29
Federation Sub-WG (SWG) Federation Sub-WG (SWG) MembersMembers
ParticipantsUSJFCOM J89/J87*
Army Architecture Integration & Management Division
(AIMD)*
Marine Corps Systems Command*
ASD(NII)/DoD-CIO DoDAF MetaModel (DM2) Team
Johns Hopkins University Applied Physics Laboratory
Siemens Government Services
Advisory Defense Architecture Registry
System User Group
Federated Joint Architecture Working Group
Department of Defense Architecture Framework Core
Management Group
USJFCOM J3/4 Force Management Improvement Program Architecture Team
• Indicates organizations with data repositories in Proof of Concept Demonstration
Navy RDA-CHENG Mission Architecture IPT representative sits on SWG meetings
Air Force Organizations are interested in upcoming federation efforts
30
UNCLASS\\FOUO
Unclassified30
DoD CIO Standards
Data Storage Locations
USAData
Storage(CADIE)
USMCData
Storage(MCAE)
USJFCOM Data
Storage(JACAE)
JCSFL UJTL’s JCAS Data BCT Data SystemsService Tasks USMC Data USA Data
Web Service InterfaceWeb Service Interface
Publish Publish DiscoverDiscover Use ManipulateUse Manipulate
Use Case – AV1, AV2, OV6
Federation Pilot ConceptFederation Pilot Concept1. User Searches for Data2. Directory Service Returns Search
Results from Registered Services to User
3. User Connects to Service Provider Through Data Translation Services
4. Service Provider Authenticates User and Returns Data to User (Use DKO/JKO)
5. User Displays Required Data
DARSAV1sAV1s
ArchitectData Consumer
DM2*DM2*
* DoDAF Metadata Model
32
33
34
35
36
37
38
UNCLASS\\FOUO
Unclassified38
Federation POCsFederation POCs
• Kim Frisby [email protected]
– Phone: (757) 836-7702
• William Piazza [email protected]
– Phone: (757) 836-2725
• JAIWG JKO Portal– https://www.us.army.mil/suite/page/512915
• JAIWG Federation Working Group JKO Portal – https://www.us.army.mil/suite/page/596533
• JACAE JKO Portal– https://www.us.army.mil/suite/page/474703
39UNCLASSIFIED
Questions and Discussion