United States Joint Forces Command Joint Concept Development and Experimentation (JCD&E)

1. United States Joint Forces Command Joint Concept Development and Experimentation (JCD&E) Interagency and Multinational Information Sharing Architecture and Solutions (IMISAS) Project Overview 7 December 2010 Ms. Kathryn Smith IMISAS Project Lead Joint Concept Development & Experimentation USJFCOM, J9

2. Joint Concept Development and Experimentation • U.S. Joint Forces Command’s Joint Concept Development and Experimentation (JCD&E) Directorate (J9) Mission… • Develop innovative joint concepts and capabilities and provide proven solutions to the most pressing problems facing the joint force. • Deliver operationally relevant solutions to support current operations, drive doctrine, organization, training, materiel, leadership, personnel and facilities (DOTMLPF) and policy changes to better enable the future joint force. • Provide leadership and collaborative environments to generate innovative ideas with a range of interagency, multinational, academic and private sector partners.

3. Interagency Multinational Information Sharing Architecture & Solutions (IMISAS) Problem Statement: US COCOMs lack a coherent framework/capability to share information and collaborate across multiple domains with a broad range of mission partners (government/interagency, multinational, multilateral and private sector) due primarily to restrictive policies, conflicting authorities, ad hoc/non-existent procedures, business rules and non-interoperable networks and systems. Warfighter Challenge: USAFRICOM, USEUCOM Partners: OSD-NII/CIO, USEUCOM, USAFRICOM

4. IMISAS Project • Develop operational capabilities for unclassified information sharing across domains which incorporates existing technologies as practical • Identify and develop best practices, policies and procedure recommendations • Conduct a limited objective, “Human in the loop”, scenario-based experiment of an operational information sharing capability, with real-time collaboration across domains with multiple mission partners to verify and validate recommended policies and procedures in a collaborative environment Warfighter Challenge: USAFRICOM, USEUCOM Partners: OSD-NII/CIO, USEUCOM, USAFRICOM

5. IMISAS Experimentation Campaign USAFRICOM/USEUCOMSite Visit #115-19 Nov RESEARCH AND ANALYSIS Stakeholders/ Gaps and Solutions Conference6-9 Dec SOLUTION REFINEMENT Final Report SOLUTION IDENTIFICATION Final Planning Conference 21-23 Jun Initial Planning Conference / Solutions Development Conference 24-28 Jan Mid Planning Conference(T) 12-14 Apr EXPERIMENTATION Tech Trial 18-29 Jul Proof of ConceptDemonstration1-5 Aug HANDBOOK & RECOMMENDATIONS FORDOCTRINE AND POLICY CHANGES IDENTIFICATION OF TRANSITION PARTNERS TRANSITION Transition Conference 7-9 Sep TODAY PLANNED END OF IMISAS PROJECT ENDS EVENT

6. IMISAS Project Timeline IMISAS FPC (T) 21-23 Jun Stakeholders' Conference / Gaps and Solutions Conference 06-09 Dec Contract Award 22 Sep 10 IMISAS MPC (T) 12-14 Apr Research and Discovery SEP 2010 OCT 10 NOV 10 DEC 10 JAN 11 FEB 11 MAR 11 APR 11 MAY 11 JUN 11 JUL 11 AUG 11 SEP 11 OCT 2011 Proof of Concept Demonstration (T) 01-05 Aug USEUCOM/USAFRICOM Site Visit #1 15-19 Nov IMISAS Initial Planning/ Solution Development Conference 24-28 Jan Transition Conference (T) 07-09 Sep

7. IMISAS Focus • Examination via experimentation, potential solutions to improve planning and coordination between the US Department of Defense and non-military partners • Identify additional technical capabilities required to establish sustained and habitual information sharing and collaborative relationships among organizations • Not merely a technical issue: • Human factors • Organizational culture • Policy and procedural barriers

8. IMISAS Refinement Approach • Focus on: • Areas of greatest operational impact to the warfighter challenge sponsors and partners • Areas where results are attainable in the scope of time and resources • Leveraging other related work • Areas in which US DOD can be a catalyst, transition agent and immediate implementer

9. IMISAS – Planned Approach • Experiment on unclassified and classified experimental networks with All Partners Access Network (APAN) portal used for information sharing. • Include sharing with social/alternative networks • Focus on synchronization and movement of data between different networks Benefits: • Robust environment that duplicates COCOM environment • Incorporate new social/alternative networks Challenges: • Management of 2 experimental networks • More difficult problem set to model and manage

10. IMISAS Experimentation Campaign USAFRICOM/USEUCOMSite Visit #115-19 Nov RESEARCH AND ANALYSIS Stakeholders/ Gaps and Solutions Conference6-9 Dec SOLUTION REFINEMENT Final Report SOLUTION IDENTIFICATION Final Planning Conference 21-23 Jun Initial Planning Conference / Solutions Development Conference 24-28 Jan Mid Planning Conference(T) 12-14 Apr EXPERIMENTATION Tech Trial 18-29 Jul Proof of ConceptDemonstration1-5 Aug HANDBOOK & RECOMMENDATIONS FORDOCTRINE AND POLICY CHANGES IDENTIFICATION OF TRANSITION PARTNERS TRANSITION Transition Conference 7-9 Sep TODAY PLANNED END OF IMISAS PROJECT ENDS EVENT

11. What is an Experiment? Experiments: Identify problems through systematic, rigorous research Develop concepts that provide potential solutions Use scenarios to establish an experimental environment Include extensive post-event analysis and reporting cycle Employ some means of manipulating something (a variable) under a controlled condition, and measuring the results Must provide credible, defendable results • Simple definition: • A process to explore the effects of manipulating a variable.

12. Experiment vs. Exercise Experiments are NOT exercises An exercise is… …a simulated maneuver or operation, usually utilizing current doctrine and organization Usually for the purpose of training, or evaluation of mastery • An experiment… • …is a means of testing, in a controlled environment, the quality, value, or usefulness of a proposed solution to a problem to help support the practitioners in the field. • Proposed solution is generally a process, organization or enabling technology/tool • Performance of the participants is usually graded • Testing the proposed solution – not the participants • …considered to be very bad if it “fails.” • … considered to be totally acceptable if the proposed solution is not completely successful, or even if it “fails.”

13. IMISAS Gap Validation Conference • Goals and objectives: Gap validation and initial solution development • Gaps examined from three factors: • policy and procedures • organizational culture/human factors • technical • Conference execution: Facilitated break out sessions focused on discussing gaps in each of the three areas • Desired outcomes: Validation and consensus on gaps; prioritized gaps for focus in the experiment

14. IMISAS Definitions (1 of 2) Capability - The ability to achieve a desired effect under specified standards and conditions through combinations of means and ways to perform a set of tasks to execute a specified course of action Capability Gap - The inability to achieve a desired effect under specified standards and conditions through combinations of means and ways to perform a set of tasks CJCSI 3170.01G, 1 March 2009

15. IMISAS Definitions (2 of 2) • JE Partner: organization receiving results and benefits from the conduct of the experiment. • Partners have a role in determining scope, design, resourcing, execution, implementation and transition of solutions. • Stakeholder: The organization or entity that is positively or negatively affected by the results of the experimentation efforts, or who has a key contributing role in the project. • CJCSM 3010.02, page GL-13

16. Experimentation Plan • Create an operational capability for unclassified information sharing across domains which incorporates existing technologies as practical • Conduct a limited objective experiment (LOE) of an operational information sharing capability with real-time collaboration across domains with multiple mission partners to verify and validate recommended polices and procedures • Facilitate an LOE with an operational vignette with Human-in-the-Loop (HITL) monitoring and interaction to validate the ability to share information across domains

17. Products • Experimentally validated: • Recommendations for enhancements to Unclassified Information Sharing (UIS) platform capabilities • Handbook and doctrine recommendations • Recommendations for changes in policy

18. IMISAS Experimentation Campaign USAFRICOM/USEUCOMSite Visit #115-19 Nov RESEARCH AND ANALYSIS Stakeholders/ Gaps and Solutions Conference6-9 Dec SOLUTION REFINEMENT Final Report SOLUTION IDENTIFICATION Final Planning Conference 21-23 Jun Initial Planning Conference / Solutions Development Conference 24-28 Jan Mid Planning Conference(T) 12-14 Apr EXPERIMENTATION Tech Trial 18-29 Jul Proof of ConceptDemonstration1-5 Aug HANDBOOK & RECOMMENDATIONS FORDOCTRINE AND POLICY CHANGES IDENTIFICATION OF TRANSITION PARTNERS TRANSITION Transition Conference 7-9 Sep TODAY PLANNED END OF IMISAS PROJECT ENDS EVENT

19. IMISAS Transition Pathways and Strategy Handbook & Policy Enhancement Enhancement to UIS/APAN UNCLASSIFIED 19

20. Keys to Successful Transitions • Transition must be in the forefront; starting early is critical to successful transition • Identify appropriate change agents early • Organizations should consider managing/steering their respective transition

21. In Summary • Recognize: • Policy and authorities drive procedures • The need to accommodate organizational cultures • The human factors involved in information sharing • Seek to: • Develop simple repeatable procedures • Accommodate users from multiple domains • Integrate existing hardware, software and networks • IMISAS is a step towards to meeting the information sharing and collaboration needs of all potential stakeholders

23. Some Complementary Efforts • Cross Domain Collaborative Information Environment (CDCIE) Joint Concept Technical Demonstration (JCTD) • Transnational Information Sharing Cooperation (TISC) JCTD • All Partner Access Network (APAN) • HARMONIEWeb • CimicWeb, InRelief, and ReliefWeb • Multinational Experiment (MNE) 6 and MNE 7 • Adaptive Logistics Network (ALN / MNE 6 Objective 4.5) • Coalition Warrior Interoperability Demonstration (CWID) • Empire Challenge • Interagency Situational Shared Awareness • Unclassified Information Sharing CONOPS • Unclassified Information Sharing Service (DISA Enterprise service)

24. Long-Term Institutionalization • Materiel: • Equipment • Weapons platforms • Programs of Record • Doctrine: • Joint Doctrine Publications • Service Doctrine Publications • Tactics, Techniques, and Procedures • Allow new application of existing capability • Modification of force posture • Changes requiring interagency cooperation • Leadership & Education: • Change management actions • Implementation support • Policy direction • Funding support • Plans of Action • Organization: • OPLANS • Business Process • Process Charts • Goals and Objectives • Standard Operating Procedures • Support Plans • Organizational Charts, and • Deployment of equipment and troops • Personnel: • Occupational Specialties and Sub-specialties • Recruitment and Staffing • KSAs • Competencies • Aptitude • Training: • Training Content • Delivery Methods Training Support Infrastructure • Training Evaluation • Training Goals and Objectives • Training Personnel • Tasks, Conditions, and Standards • Facilities: • Field fortification support • Force bed down • Main supply routes • Operations and maintenance • Roads/trails • Other physical infrastructure • Engineering support services