jwfc event handbook 2010[1]

i

Headquarters, US Joint Forces Command Norfolk, Virginia

Joint Warfighting Center

Event Handbook

2010

The Joint Warfighting Center (JWFC) is pleased to provide this guide to the JWFC Training Operations desk. This handbook is a comprehensive reference tool which outlines USJFCOM’s support to combatant commands through the Chairman, Joint Chiefs of Staff (CJCS) exercise program and our work in support to Service training programs. Specifically, this document outlines the flow of the various JWFC offices and external groups that actively participate in forming, designing, executing, and assessing joint training.

The purpose of this handbook is to help you navigate the requirements associated with today’s operational environment. It provides a solid framework for how to effectively integrate individual and collective joint training opportunities through a growing global infrastructure linking joint and Service training sites. It encourages the involvement of US government agencies, multinational colleagues, and other partners in the conduct of our future operations.

Areas for improvement or corrections should be directed to Director Joint Warfighting Center/J7 (USJFCOM/Operations Group/Plans Branch), 116 Lake View Parkway, Suffolk, Virginia, 23435-2697.

STEPHEN R. LAYFIELD Major General, U. S. Army Director, Joint Warfighting Center/J7

ii

PREFACE

iii

TABLE OF CONTENTS

Page PREFACE ..................................................................................................................................................... i CHAPTER I INTRODUCTION

• Handbook Purpose .............................................................................................................................. I-1 • Joint Training Management Responsibilities ....................................................................................... I-1 • Joint Warfighting Center Mission and Roles ....................................................................................... I-2 • Scope ................................................................................................................................................... I-3 • Joint Warfighting Center Support ........................................................................................................ I-4 • Summary ............................................................................................................................................. I-5

CHAPTER II JOINT WARFIGHTING CENTER ORGANIZATION

• General ............................................................................................................................................... II-1 • JWFC Organization ............................................................................................................................ II-2 • JWFC Joint Management Offices (JMO) ............................................................................................ II-7 • JWFC Supporting Organizations ........................................................................................................ II-8

CHAPTER III JOINT TRAINING SYSTEM

• Overview ............................................................................................................................................ III-1 • Phase I (Requirements) - Determine Mission Essential Tasks ......................................................... III-3 • Phase II (Plans) - Develop Joint Training Plans (JTP) ...................................................................... III-4 • Phase III (Execution) - Execute Joint and Agency Training Plans .................................................... III-5 • Phase IV (Assessment) - Assess Training Performance .................................................................. III-7 • Summary ........................................................................................................................................... III-8

CHAPTER IV JWFC JOINT TRAINING TIERS AND CAPABILITIES

• General ..............................................................................................................................................IV-1 • Tiers of Training and Events ..............................................................................................................IV-1 • Multinational Training ........................................................................................................................IV-2 • Interagency Training ..........................................................................................................................IV-2 • Joint Personnel Recovery Agency (JPRA) ........................................................................................IV-2 • Joint Deployment Training Center (JDTC) ........................................................................................IV-2 • Knowledge and Information Fusion Exchange (KnIFE) ....................................................................IV-2 • Joint Public Affairs Support Element (JPASE) ..................................................................................IV-3 • Integration of Capability Testing ........................................................................................................IV-3 • Joint National Training Capability ......................................................................................................IV-3 • Summary ...........................................................................................................................................IV-4

CHAPTER V JOINT EVENT LIFE CYCLE

• General ...............................................................................................................................................V-1 • Training Requirements Analysis .........................................................................................................V-2 • Joint Event Life Cycle Events .............................................................................................................V-2 • Summary ..........................................................................................................................................V-11

iv

CHAPTER VI JOINT WARFIGHTING CENTER EVENT SUPPORT • Introduction – JWFC Support to Combatant Commands ..................................................................VI-1 • Scenario −− MSEL Support ...............................................................................................................VI-1 • Opposing Force/Situational Forces ...................................................................................................VI-2 • Joint Exercise Control Group .............................................................................................................VI-2 • Doctrine and Education Support to Joint Training .............................................................................VI-2 • Intelligence Support to Joint Training ................................................................................................VI-3 • Exercise Sustainment Planning Support ...........................................................................................VI-4 • Communication Systems ...................................................................................................................VI-5 • Modeling and Simulation ...................................................................................................................VI-5 • Observation, Training, and Analysis Support ....................................................................................VI-5 • Synthetic Media Support ...................................................................................................................VI-7 • Joint Knowledge Development and Distribution Capability (JKDDC) ...............................................VI-8 • Joint Experimentation, Test and Evaluation, and Advanced Concept Technology

Demonstration (JETA) Integration into Joint Training ....................................................................VI-8 • Information Operations (IO) Joint Management Office ......................................................................VI-9 • Joint Training Service Support ..........................................................................................................VI-9 • Desk Officer Checklists ...................................................................................................................VI-10 • JWFC Training Effectiveness Survey Program ...............................................................................VI-10

ENCLOSURES

• (1) JWFC Organization Chart ..............................................................................................ENC (1)-1 • (2) Joint Training Plan TAB Descriptions ............................................................................ENC (2)-1 • (3) Joint Training Information Management System (JTIMS) .............................................ENC (3)-1 • (4) JELC POA&M and Deliverable Checklist ......................................................................ENC (4)-1 • (5) Pre-Exercise Executive Brief Format .............................................................................ENC (5)-1 • (6) Exercise Directive Example ...........................................................................................ENC (6)-1 • (7) Initiating Directive MSG (Example) ................................................................................ENC (7)-1 • (8) Initiating Directive (Example) (Text Format) ..................................................................ENC (8)-1 • (9) Remote Site Survey Checklist .......................................................................................ENC (9)-1 • (10) Scenario Development ................................................................................................ENC (10)-1 • (11) Master Scenario Event List Development ...................................................................ENC (11)-1 • (12) Opposing Force/Response Cell ...................................................................................ENC (12)-1 • (13) Joint Exercise Control Group (JECG) Operating Procedures .....................................ENC (13)-1 • (14) Exercise Intelligence Planning Guide ..........................................................................ENC (14)-1 • (15) Sustainment .................................................................................................................ENC (15)-1 • (16) Joint Exercise Support Branch Support .......................................................................ENC (16)-1 • (17) The Joint Training Tool Kit ...........................................................................................ENC (17)-1 • (18) JWFC Event Testing ....................................................................................................ENC (18)-1 • (19) JKDDC Support to Joint Training .................................................................................ENC (19)-1 • (20) IO Support to Joint Training .........................................................................................ENC (20)-1 • (21) Service Support ...........................................................................................................ENC (21)-1 • (22) Security ........................................................................................................................ENC (22)-1 • (23) Visitors Bureau .............................................................................................................ENC (23)-1 • (24) JWFC Floor Plans ........................................................................................................ENC (24)-1 • (25) Public Affairs ................................................................................................................ENC (25)-1 • (26) Manning Requirements ................................................................................................ENC (26)-1 • (27) Desk Officers (JELC) Checklists ................................................................................. ENC (27)-1

APPENDICES

• Appendix A, Encl 3, Introduction and Administration Information ....................................... ENC (3)-A-1

v

• Appendix B, Encl 3, Rolls and Responsibilities ................................................................... ENC (3)-B-1 • Appendix C, Encl 3, Training ............................................................................................... ENC (3)-C-1

GLOSSARY

• Part I − Abbreviations and Acronyms .............................................................................................. GL-1 • Part II − Terms and Definitions ...................................................................................................... GL-10

FIGURES

• I-1 2008 Unified Command Plan USJFCOM Joint Force Trainer Responsibilities ............................. I-2 • I-2 The JWFC Training Tiers ............................................................................................................... I-4 • II-1 Operations Group ......................................................................................................................... II-2 • II-2 Joint Training Division .................................................................................................................. II-3 • II-3 Joint Exercise Division ................................................................................................................. II-3 • II-4 The Joint Support Division ........................................................................................................... II-4 • II-5 Training Development Group ....................................................................................................... II-5 • II-6 Doctrine & Education Group ......................................................................................................... II-6 • III-1 The Joint Training System .......................................................................................................... III-1 • III-2 JTS: Inputs, Processes, and Outputs ......................................................................................... III-2 • III-3 J/ATP Flow Chart ....................................................................................................................... III-5 • III-4 Execution and Assessment ........................................................................................................ III-8 • V-1 Joint Event Life Cycle ..................................................................................................................V-1 • V-2 Joint Event Life Cycle - Stage 1 ...................................................................................................V-3 • V-3 Joint Event Life Cycle - Stage 2 ...................................................................................................V-5 • V-4 Joint Event Life Cycle - Stage 3 ...................................................................................................V-7 • V-5 Joint Event Life Cycle - Stage 4 ...................................................................................................V-9 • V-6 Joint Event Life Cycle - Stage 5 .................................................................................................V-10 • Encl 12: 12-1 OPFOR Information Flow ...............................................................................ENC (12)-4 • Encl 13: 13-1 Example of a JECG Battle Rhythm ................................................................ENC (13)-1 • Encl 13: 13-2 Typical JECG Structure ..................................................................................ENC (13)-3 • Encl 13: 13-3 Example of an ESMD .....................................................................................ENC (13)-5 • Encl 19: 19-1 JKO Network Illustration ..................................................................................ENC (19)-3 • Encl 19: 19-2 JKO Access Illustration ...................................................................................ENC (19)-4 • Encl 20: 20-1 Information Operations Range .......................................................................ENC (20)-3 • Appendix B: B-1 Desk Officer Team .................................................................................... ENC (3)-B-2 • Appendix B: B-2 Deployable Training Team ....................................................................... ENC (3)-B-4

REFERENCES

• CJCSI 1800.01.C, Officer Professional Military Education Policy, 7 Aug 2007 • CJCSI 3151.01A, GCCS COP Reporting Requirements, 19 Jan 2003 • CJCSI 3500.01E, Joint Training Policy and Guidance for the Armed Forces of the United States, 31

May 2008 • CJCSM 3500.03B, Joint Training Manual for the Armed Forces of the United States, 31 Aug 2007 • CJCSM 3500.04E, Universal Joint Task Manual, 25 Aug 2008 • Unified Command Plan (UCP) 2008, 23 Dec 2008 (Classified) • Joint Mission Essential Task List (JMETL) Development Handbook, Sep 2002 • USJFCOM 1025.1-M, Joint Experimentation, Test and Evaluation, and Advanced Concept

Technology Demonstration (JETA) Integration into Joint Training Manual, 3 Jun 2005 • DOD Regulation 5200.1-R, Information Security Program • DOD Regulation 5400-7R, Department of Defense Freedom of Information Act (FOIA) Program

vi

Intentionally Blank

I-1

CHAPTER I: INTRODUCTION

1. Handbook Purpose a. The Joint Warfighting Center Event Handbook provides information to be used as a guide and ready reference for individuals participating in the Chairman, Joint Chiefs of Staff (CJCS) Exercise Program, the CJCS Joint Training Program, and the Joint Training System (JTS) conducted by the Joint Warfighting Center (JWFC). Most importantly, the Handbook is intended to provide Desk Officers, trainers and planners a user friendly document in planning, constructing, conducting, and evaluating events. Additionally this Handbook provides the mechanics, offices, and internal JWFC organizations where forming, designing, executing, and assessing joint events take place. b. The handbook lists the multiple capabilities of the Joint Warfighting Center available to support events planned and executed within and external to the facility and the capability to distribute live-virtual-constructive capabilities within events to worldwide locations. 2. Joint Training Management Responsibilities a. The following have specific joint training management responsibilities: Office of the Secretary of Defense, Chairman of the Joint Chiefs of Staff, Joint Staff, US Joint Forces Command (USJFCOM), US Special Operations Command, combatant commanders, Services, Service components, and combat support agencies. The responsibilities of the Chairman of the Joint Chiefs of Staff and USJFCOM are highlighted in the following paragraphs. For detailed information on joint training management, see CJCS Instruction 3500.01E, Joint Training Policy and Guidance for the Armed Forces of the United States, Training Responsibilities (CJCS Instruction 3500.01E). b. The Chairman of the Joint Chiefs of Staff is responsible for ensuring the joint training of the Armed Forces of the United States to accomplish strategic and contingency planning and preparedness in accordance with policy guidance from the President and the Secretary of Defense. As such, the Chairman has delegated much of the responsibility to USJFCOM for the execution of the CJCS Exercise Program. c. USJFCOM, as the Joint Force Trainer and lead agent for the Joint Staff’s joint force training program is responsible for deploying trained and ready joint forces and providing operational and intelligence support from assigned forces in response to the requirements of supported combatant commands. The JWFC, as executive agent for joint training, is tasked with providing sufficient training events for USJFCOM components, JTF, and combatant command headquarters. USJFCOM is responsible to the Chairman of the Joint Chiefs of Staff for managing the combatant commander's portion of the CJCS Exercise Program. USJFCOM is a centralized organization capable of structuring, executing, and/or facilitating joint training events across the full spectrum of joint training. See CJCS Instruction 3500.01E, Joint Training Policy and Guidance for the Armed Forces of the United States, for more detail on USJFCOM's support to the JTS.

I-2

3. Joint Warfighting Center Mission and Roles:

Mission: The Joint Warfighting Center trains forces, develops doctrine, and provides an interoperable training environment to improve joint warfighter readiness.

a. CJCS Instruction 3500.01E, Joint Training Policy and Guidance for the Armed Forces of the United States defines the Joint Training System and directs the CJCS joint training program. CJCS Manual 3500.03B, Joint Training Manual for the Armed Forces of the United States provides the implementation guidance for conducting CJCSI 3500.01E. USJFCOM J-7, Joint Training Directorate and JWFC, as the Chairman’s executive agent for joint training, is responsible for delivering trained, capable, interoperable joint forces, and leading the transformation of individuals and collective joint training. The JWFC role is to support the CJCS Exercise Program by preparing, conducting, and assessing events that provide collective joint training for combatant commanders and the Services. To meet the realistic expectations experienced within today’s dynamic operational environment, the JWFC is functionally organized to provide training support by routinely tailoring and combining capabilities to ensure that customers receive what they need. Event supporting capabilities are provided by both subordinate organizations of the JWFC and subordinate USJFCOM commands. b. The JWFC, with its supporting military, DOD civil service, and civilian contractor personnel, train joint force commanders, component commanders, designated forces, and staffs in the application of joint doctrine and joint tactics, techniques, and procedures. Figure I-1 depicts the responsibilities for the Joint Force Trainer for USJFCOM derived from the Unified Command Plan 2008.

Joint Warfighting Center Responsibilities as the Joint Force Trainer

1. Assisting the chairman, combatant commanders, and Service Chiefs in their preparation for joint and multinational operations.

2. Supporting the Services’ and combatant commanders’ participation in the Combatant Commander Exercise Engagement and Training Transformation program.

3. Conducting and assessing joint and multinational training for assigned Forces.

4. Leading the development and operation of joint training systems and architectures that directly support the combatant commanders, Services, and defense agencies.

Figure I-1. 2008 Unified Command Plan USJFCOM Joint Force Trainer Responsibilities.

c. JWFC supports the worldwide combatant commander's training and exercise programs through the JTS. JWFC also provides the foundation for joint operations by supporting joint doctrine development for current needs and future concepts for joint organizations and is evolving to expanded roles in support of joint readiness. Emerging JWFC focus areas are to: (1) Emphasize the human dimension of warfare; enhance cognitive development across the spectrum from information to knowledge to understanding to intuition. (2) Support the development of immersive training technologies that enhance the development of agile, high-performance leaders and units – train as you fight, and fight as you train. (3) Increase tactical unit access to live, virtual, and constructive capabilities (ISR, joint fires).

I-3

(4) Increase mutual training value for DOD and non-DOD partners in joint and Service training programs. (5) Increase frequency and fidelity of training that is focused on the integration of special operations forces with general purpose forces. d. JWFC conducts joint and multinational training focused on commanders staffs, and component forces operating as part of a joint or multinational task force in accordance with joint mission-essential tasks specified by the supported combatant commander. JWFC supports joint tactical-level training centered on Service component-sponsored advanced field training exercises with staff and tactical training programs being supported by distance learning and advanced distributed simulation technologies at the JWFC. JWFC's emerging technologies and program applications provide the capability to rehearse, train, and exercise USJFCOM's assigned continental United States-based forces and geographic combatant commander’s forces worldwide. e. The Deputy Under Secretary of Defense for Readiness (DUSD(R)) has outlined a program for the Joint National Training Capability (JNTC) supporting the mission of the JWFC that creates an environment for realistic joint exercises against aggressive, free-playing, opposing forces, with high quality feedback. The JNTC enhances the enabling capability that promotes persistent integrated live, virtual, and constructive simulation environment, available globally on a 24-hour basis, and linked to real-world command and control systems where practical. The JNTC provides the where-with-all to train forces against a general threat, to conduct mission rehearsal against a specific threat, or to experiment with new doctrine, tactics, techniques, procedures, Joint Operational Concepts, and equipment. JNTC, as the integrating environment, enables joint training to the full complement of defense training audiences. Active and Reserve forces, from a single Service, are able to train in a realistic joint operational environment with other Service forces and joint battle staffs represented with extensive simulation support. Battle staffs from joint headquarters, component headquarters, and Service tactical headquarters can train and rehearse using real-world command and control systems where practical, with tactical forces represented with extensive simulation support. The JNTC programs continue to evolve in order to encompass larger training audiences, to more effectively and more often include coalition partners, US agency partners, and non-governmental partners. 4. Scope a. JWFC supports the Joint Staff, combatant commands, Services and subordinate joint force commanders in all four phases of the JTS (i.e., Requirements, Plans, Execution, and Assessment), which is the backbone of the CJCS Exercise Program and the CJCS joint training program. The Handbook's primary focus is on Phase III -- Execution of joint training events. This support is coordinated through assigned JWFC Desk Officers who serve as representatives of USJFCOM to the Joint Staff, combatant commands, and subordinate joint force commands. b. The organizational structure of JWFC is designed to execute missions described in the Unified Command Plan 2008. See Chapter II, of this Handbook, "Joint Warfighting Center Organization." c. CJCS Manual 3500.03B, Joint Training Manual for the Armed Forces of the United States, provides information on the JTS and the procedures for developing training requirements, creating joint training plans, executing those plans and assessing training proficiency. (1) For a detailed discussion of the JTS, see CJCS Manual 3500.03B, Joint Training Manual for the Armed Forces of the United States, Enclosures B-F. (2) For a JWFC Desk Officer and action officer perspective of the JTS, see Chapter III, of this Handbook, "Joint Training System."

I-4

d. Joint training events are the most visible tools of the JTS and are categorized based upon their intended training audience. These events are primarily captured within four JWFC identified tiers, and range from US Service core competency training to interagency and intergovernmental joint training. Figure I-2 lists the JWFC training tiers. Chapter IV, of this Handbook, “JWFC Joint Training Tiers and Capabilities” provides “Tier” definition.

JWFC TIERS OF TRAININGJWFC TIERS OF TRAINING

Tier 1 Combatant Command and Higher Authority Training

Tier 2 Joint Task Force Training

Tier 3 Functional Component Training

Tier 4 Individual Organizational Training

Figure I-2. The JWFC Training Tiers. e. Joint training events are developed using the process described in the Joint Event Life Cycle (JELC). The JELC, within the JTS Phase III -- Execution, consists of five stages to successfully execute a discrete training event -- Design; Planning; Preparation; Execution and Analysis; and Evaluation and Reporting. (1) For a detailed description of the JELC process, see CJCS Manual 3500.03B, Enclosure E, Phase III (Execution). (2) For the JWFC Desk Officer perspective for implementing the JELC, see Chapter V, of this Handbook, "Joint Event Life Cycle." f. The JWFC provides products and services in support of training events that are conducted within JWFC facilities and at deployed, worldwide locations. Procedures have been developed with an explanation that describe the extent and nature of products and services that supported and supporting commands can expect from JWFC. See Chapter VI, of this Handbook, "Joint Warfighting Center Event Support," for the availability of JWFC resources and the methodology for how those resources are prioritized and allocated between the Joint Staff and combatant commands. g. In an effort to assess the effectiveness of JWFC products and services, the JWFC collects data from beneficiaries (stakeholders) before, during and after training events. The purpose of this collection effort is to gain the stakeholder’s perspective and to influence internal and external process improvements. h. The Handbook enclosures offer the user, JWFC Desk Officers, combatant command, and subordinate joint force representative’s access to sample messages and briefing templates, checklists, and reports. The Handbook also includes JWFC facility plans, modeling and simulations capabilities, and standard procedures for developing the joint master scenario event list (MSEL) in support of an event. 5. Joint Warfighting Center Support The JWFC provides means to “train as we operate” by strengthening “jointness” in Service training programs, facilitating a “whole of government” approach for military and civilian partners,

I-5

leveraging technologies to bring training to the user, establishing linkages with global partners, and facilitating the development of new joint competencies. a. JWFC employs capabilities to support multiple and concurrent training events. These capabilities include and are not limited to: modeling and simulation support; subject matter experts to cover numerous disciplines; e.g., Observer Trainers (O/Ts); joint mission-essential task list and training objectives development; academics; media role playing; scenario development; senior mentorship; a live-virtual-constructive reactive opposing force; after-action review and analysis; command, control, communications, computers, intelligence, surveillance, and reconnaissance; and existing and emerging technologies. JWFC personnel and their efforts culminate in a flexible, experienced, intelligent, responsive, and imperceptible control group that drives the training event or exercise. JWFC provides the framework for the assessment of training and the collection of near-term, training-based, warfighting capability improvements. These and other capabilities are resident within the JWFC and at deployed locations subject to the availability of assets, funding, and allocation priorities established by the Joint Staff. See CJCS Manual 3500.03B, The Joint Training Manual for the Armed Forces of the United States, Enclosure Q, USJFCOM Training Support Capabilities, for a description of USJFCOM's joint training support capabilities. b. To determine event requirements, the Joint Staff J7, with JWFC support, annually hosts and facilitates meetings with combatant command and Service representatives at the Worldwide Joint Training and Scheduling Conferences. The purpose of the meetings is to: 1) Resolve combatant command/Combat Service Agencies (CSA)/Service and joint training issues; 2) establish a plan of action and milestones to resolve outstanding joint training issues; and 3) fully integrate interagency partners into the joint training community of interest. c. Working closely with combatant command representatives, JWFC Desk Officers, acting as JWFC primary points of contact, have oversight and coordinating responsibilities with all JWFC subject matter experts. JWFC Desk Officers determine early in the JELC process the exact level, type, and priority of specific support required for the training event. d. The JWFC also may be tasked to support other requirements such as USJFCOM J-9, Joint Experimentations, and the Joint Enabling Capability Command’s (JECC) operational initiatives provided to combatant commands. Many of these events require the same level of support as other JWFC internal events. 6. Summary a. This Handbook provides the means for all personnel associated with the JWFC training event program to better understand the many facets and capabilities available through the Warfighting Center. The Handbook also provides quick ready reference checklists, templates, and message formats for the JWFC Desk Officer and planners that are supporting an event.

I-6

Intentionally Blank

II-1

CHAPTER II: JOINT WARFIGHTING CENTER ORGANIZATION 1. General a. The Joint Warfighting Center (JWFC) conducts, supports, and assesses joint training and develops and assesses joint and multinational doctrine to prepare leaders to use emerging concepts and capabilities for multi-national and interagency operations world-wide. The JWFC supports the Joint Staff, combatant commanders, and Service Chiefs in preparing for and conducting joint, interagency, non-governmental, and multinational operations. The JWFC is a committed and reliable team of military personnel, DOD civil service personnel, and civilian contractors dedicated to training forces for the purpose of delivering trained, capable, and interoperable joint forces. The JWFC consists of the Director’s Group which is directly supported by the Operations, Training Development, and Doctrine & Education Groups. Additionally, the Director’s Group directs three Joint Management Offices and six supporting organizations. Responsibilities of these directorate functions are described in the following paragraphs and their organizational hierarchy within JWFC is delineated at Enclosure (1), “JWFC Organization Chart.” 2. JWFC Organization a. Director’s Group. This group is responsible for integrating both the internal organizational structure in order to accomplish JWFC’s mission for training warfighters in combatant commands, in Services, and in joint task forces. The Organizational Group is dedicated to the successful integration of all USJFCOM’s joint training related responsibilities — doctrine, capabilities, training, and models and simulations. It ensures that the JWFC collective efforts remain aligned with the efforts of the rest of the USJFCOM, the Joint Staff, and the Office of the Secretary of Defense (OSD). (1) Director, J7/Joint Warfighting Center (JWFC). The Director J7/JWFC is responsible for joint force exercise and training development, training resources allocation, management, and assessment. The Director, J7 assists the Chairman of the Joint Chiefs of Staff (CJCS), the combatant commanders, and the Service Chiefs in their preparation for joint and multinational operations through the conceptualization, analysis, development, dissemination, assessment, and revision of current joint and, where appropriate, multinational doctrine, and tactics, techniques, and procedures. (2) Deputy Director, J7/Joint Warfighting Center (JWFC). The Deputy Director, J7/JWFC assists the Director, J-7, in the conduct of joint force event and training development. In the absence of the Director, J7, he fulfills the Director’s operational responsibilities within USJFCOM. (3) Vice Director, J7/Joint Warfighting Center (JWFC). The Vice Director J7/JWFC assists the Director, J7 in managing day-to-day administrative issues for the “Center.” His responsibilities span personnel hires and acquisition initiatives to resource allocations.

(4) Chief of Staff (COS). The COS office has oversight for the following JWFC supporting branches: Strategy, Plans & Assessment; Mission Assurance & Support; Workforce Management; and Reserve Affairs.

(a) Strategy, Plans and Assessment Division. Support JWFC leadership engagement with internal and external audiences; support leadership in executing planning and programming phases of Planning and Programming, Budgeting and Execution (PPBES); manage JWFC strategic planning process; and manages internal and external performance-based assessment.

(b) Mission Assurance & Support Division. Provides common services and support in

staff areas. Specific tasks include: staff actions and operations, Operational Security (OPSEC), Knowledge and Information Management, Foreign Disclosure, and Facilities and Logistics.

II-2

(c) Workforce Management Division. Provides coordination and work force analysis for

military/civilian personnel management, exercise manning, Reserve integration, organizational support, as well as programming and policy development that fully enable Joint functions and priorities.

(5) Executive Director. Responsible for four major programs: Navy working capital, funded

government personnel, supporting the command, and as a technical contracted workforce. The Executive Director plays a crucial training enterprise level role in coordination at the OSD and JS level in establishing principles, agreements, reviews, and procedures that affect all combatant commands, Services and Agencies. J7 Executive Director has responsibilities for managing all Training Technology Capabilities which span all Services, Joint Experimentation and Joint Testing Communities.

(6) Technical Director. The J7 Technical Director/ Acquisition Advisor is directly responsible to

the Director, J7 for the technical development and technical operations of the JWFC.

(7) Business Management. Responsible for program management; including planning, oversight, execution, and analysis of all J7 fiscal matters, as well as the execution of all funding related to the J7 portion of all USJFCOM-supported activities.

b. Operations Group. In support of the USJFCOM’s joint training program, the Operations Group accomplishes the following: supports combatant commands in the development and execution of their training exercises; trains rotating Joint Task Forces (JTF); conducts Mission Rehearsal Program; executes senior leader education; integrates lessons learned, concepts, and prototypes into exercises; and supports multinational training and engagement. The Operations Group encompasses three Divisions: Joint Training Division, Joint Exercise Division, and Joint Support Division. Figure II-1 depicts the Operations Group.

Chief, Operations

Group

Deputy Operations

Joint Support TeamTrainer Operations

Joint Training Division

Joint Exercise Division

Joint SupportDivision

Plans & Policy

Figure II-1. Operations Group

The Operations Group implements the joint training system (JTS) (per Chapter III, "Joint Training System," to this Handbook) and supports and conducts joint and multinational training and events focused on commanders, staffs, and component forces. Subparagraph 2.d. describes details concerning the Operations Group.

(1) Joint Training Division (JTD). The JTD prepares joint force commanders and their staffs for joint and combined operations. Training is based upon current US joint doctrine and joint tactics, techniques, and procedures. The Joint Training Division consists of teams (Deployable Training Teams (DTTs)) who observe, train and educate designated joint force commanders and staffs through training. Additionally, the DTTs educate senior leaders and support joint war fighter and trainer capability improvement. This activity occurs at the JWFC and at other remote sites worldwide, in association with

II-3

joint and/or multinational exercises and real-world operations. The team members include observer/trainers from all Services providing analysis of collected observations reported in the form of event facilitated after-action reviews (FAARs) and commander’s summary reports (CSARs). Deployable Training Teams (DTTs) design academic training programs tailored to support combatant commanders' training objectives by developing and conducting academic seminars, planning workshops, focused functional training sessions, and senior leader seminars. Additionally, the DTT provides "just-in-time" joint and/or multinational training in support of real-world crises. Figure II-2 portrays the JTD.

Operations

O/Ts

Intel

O/Ts

Plans

O/Ts

Sustainment

O/Ts

CommStrategy

O/Ts

Interagency

O/Ts

Legal

O/Ts

Chief, Joint Training Division

Deputy, Joint Training Division

Plans / Training

Future Ops

PINNACLECAPSTONEKEYSTONE

InformationSharing

O/Ts Figure II-2. Joint Training Division

(2) Joint Exercise Division (JED). The JED supports joint, multinational, and interagency training of combatant commanders, JTF Headquarters, functional component headquarters, Service capabilities and multinational partners for joint and combined operations. This includes all stages involved in mission rehearsal exercise that train rotational forces for deployment into wartime theaters of operation. The Division designs, plans, prepares, executes, and analyzes joint and multinational training events to support the warfighter. JWFC events train combatant commander staffs and JTF staffs using the combined efforts of the command tailored to specific training requirements. The Joint Exercise Division is divided into Functional Planners, Desk Officers and a Multinational Affairs Branch in order to provide event support on a worldwide basis in accordance with CJCS Manual 3500.03B. All training conforms to the JTS, and is conducted within the Joint Event Life Cycle (JELC). The JED’s exercise support priorities are based on USJFCOM Commander’s guidance, and the combatant commander’s exercise engagement (CE2) programming process. Figure II-3 depicts JED.

Functional Planners Desk Officers Multinational Affairs Branch

Chief, Joint Exercise Division

Deputy, Joint Exercise Division

Training ExerciseSpecialist

Figure II-3. Joint Exercise Division

II-4

(a) Functional Planners. This Branch provides the functional support; e.g., intelligence, interagency, information operations, combat service support, threat operations, Joint Personnel Recovery, training analysis, and Defense Threat Reduction Agency/Chemical, Biological, Radiological, Nuclear, and high-yield Explosives (DTRA/CBRNE) support in order to create a realistic exercise environment that allows the training audience the ability to accomplish its mission objectives. Members of the Functional Branch interact and partner with Service and combatant command training audience subject matter experts (SMEs) and Centers of Excellence to plan for the conduct of and execution of events. (b) Desk Officers. Supporting the joint training system, Desk Officers are the Operations Group’s direct link to combatant commands and USJFCOM components planners and trainers. The Desk Officer, assisted by Event Planners, ensures that the Joint Event Life Cycle (JELC) is implemented in accordance with the JTS, and represents the interest of combatant commands within the JWFC; e.g., support JNTC Accreditation and Mitigation enabling Service and combatant command training programs. (c) Multinational Affairs. Supporting the multinational response within the joint training system, this Branch conducts and supports In the Spirit of (ISO) Partnership for Peace (PfP) multinational events in AFRICOM, EUCOM and CENTCOM Areas of Responsibility (AORs). They assist Allied Command Transformation in transforming the NATO training and exercise program. (3)Joint Support Division (JSD). The mission of the Joint Support Division (JSD) is to provide technical planning (M&S & C2 systems), engineering, and execution support to all combatant command, service, and specific coalition exercises and Joint Professional Military Education events; support the Joint National Training Capability accreditation, certification, and mitigation program; operate and maintain the Joint Training and Experimentation Network (JTEN) in order to provide highly realistic training within a joint context. The JWFC Information Assurance Manager and team support the JSD and the JWFC Designated Approval Authority by ensuring events are executed in compliance with appropriate DOD policies, directives and letter of instruction. Figure II-4 displays the Joint Support Division organization.

Chief, Joint Support Division

Deputy Chief, Joint Support Division

Joint Support DivisionOperations Officer

Joint Exercise Support Joint Systems Engineering C 4 I

JWFC Information AssuranceManager

C 4 I

Figure II-4. The Joint Support Division

(a) Joint Exercise Support Branch. The Joint Exercise Support Branch (JESB) provides direct support to JFCOM, combatant commands, and Service training events. The JESB supports the JWFC by providing Modeling & Simulations (M&S) and Command, Control, Communication, and Computers (C4) subject matter experts (SMEs) in support of joint training events. The JESB plans, implements, and executes C4 architectures, simulation to C4 interfaces, M&S architectures and associated support for all

II-5

JFCOM events by analyzing joint and Service exercise objectives, exercise scenarios, force structures, and go-to-war command and control systems and processes. (b)Joint System Engineering Branch. The Joint System Engineering Branch (JSEB) provides technical infrastructure engineering support for the Suffolk complex day-to-day activities, real-world operations, and Joint training and experimentation. The JSEB provides technical expertise to design, specify, procure, install and upgrade specific electronic systems at JWFC: - LAN/WAN, C4, M&S, VTC, A/V, Broadcast Production, SW development, Joint Digital Library, JKDDC LMS, JESS, & Logbook - Manages Life Cycle Management for JWFC / JNTC training and exercise systems The JSEB provides engineering implementation for technology insertion into existing systems and supports the J7 M&S engagement strategy. (c) C4I Branch. The C4I branch provides the JTEN Network Operations Security Center (NOSC) to provide direct support to JFCOM, combatant command and Service training events. The NOSC is located within the JWFC. The C4I Branch interfaces with other branches in the JSD to identify and solve technical issues in support of training events.

c. Training & Development Group (TDG). This group supports the JWFC with a centralized process by which joint training environment shortfalls are identified, training environment requirements are identified, prioritized and vetted to stakeholders, and then solutions are identified, funded and integrated into the joint training environment. The Training Development Group spans the spectrum of joint training environment requirements to Joint Requirements Oversight Council endorsement and procurement. A complementary and parallel function is the Capability Improvement Process that facilitates the development of newly required warfighting capabilities, integrating them appropriately into the JFT's joint training support program, and managing them through the "Capability Change Recommendation" (doctrine, organization, training, materiel, leadership and education, personnel, and facilities format) for submission to the Joint Staff. The Training Development Group is responsible for development of future joint training environment requirements for the Joint Training Enterprise. The TDG consolidates guidance from sources internal and external to JFCOM, analyzes needs and formulates training environment requirements for enhancements to current Service, combatant commands and component training programs to support current and future joint operational needs, and incorporates priorities from the various training transformation (T2) oversight bodies (Senior Advisory Group, Executive Steering Group, Joint Integrated Process Team, and Corporate Board) in order to prioritize training environment requirements and develop solutions for the Joint Training Enterprise. Figure II-5 below portrays the TDG organizational structure.

Figure II-5. Training Development Group

d. Doctrine & Education Group (DEG). The DEG develops, assesses and assists in the development of joint and multinational doctrine and shapes joint leader development and education to assist the Chairman of the Joint Chiefs of Staff, Combatant Commands, and the Services in preparing US Military

II-6

Forces for joint and multinational operations. The Doctrine & Education Group (DEG) supports the Desk Officer by providing Joint doctrine subject matter experts to joint training audiences at USJFCOM-supported joint training exercises and to real-world joint operations as requested. The following subparagraphs highlight the specific functions and capabilities of the DEG’s organization and structure as shown in Figure II-6.

Figure II-6. Doctrine & Education Group (1) Development Division. This division oversees and facilitates the assessment, revision, and creation of joint doctrine via the joint publication development process outlined in CJCSI 5120.02A. The DEG’s development division is also the assessment process holder for the Chairman’s doctrine program. Assessments of joint doctrine are conducted in support of the Chairman through the Joint Staff J7. The assessment process is continuous and involves all the Services and Combatant Commands. All assessments include observations taken from doctrine analysts and observer/trainers at joint exercises and real-world operations, to include analysis of potential doctrinal implications from joint lessons learned. (2) Integration Division. The Integration Division provides the necessary linkage between concept maturation and doctrine development to capture, assess, compare, and integrate key conceptual ideas and validated experimentation results that could improve joint doctrine. Through a process of reviewing USJFCOM Joint Experimentation Program concept products (Baseline Collective Assessments; concept papers such as white papers, concept of operations, and tactics, techniques, and procedures; and Doctrine, Organization, Training, Materiel, Leadership, Personnel, and Facilities (DOTMLPF) Change Packages) and participation in J-9 events (Experiments, Working Groups, seminars, and DOTMLPF Change Package development), Integration Division enhances the identification of doctrinal recommendations and accelerates good ideas and potential doctrinal resolutions into joint doctrine and joint tactics, techniques, and procedures. Integration Division also reviews Joint Staff concepts developed under the auspices of the Joint Operations Concepts document for the same purposes described above. (3) Education and Training Support Division. The Education and Training Support Division (ETSD) shapes joint leader development, education and learning. To accomplish this, the ETSD conducts the Process for Accreditation of Joint Education Support (PAJE) (CJCSI 1800.01C), provides enhanced institutional learning (non-JPME) courseware analysis, review and certification (CJCSM 3500.03B), manages the Joint Individual Learning Database (CJCSM 3500.03B), integrates education and distance learning modules into joint military exercises, facilitates a relationship with the Joint Forces Staff College, assists in the education and training of Flag and General Officers (FO/GOs) (CJCSI 1800.01C), supports Military Education Coordination Council (MECC) (CJCSI 1800.01C), and collaborates with stakeholders and other organizations across the DOD enterprise. (4) Doctrine Support Team (DST). This JWFC Support Team element is comprised of civilian contractors who are joint doctrine subject matter experts that provide research and analysis of pertinent joint doctrine issues as they surface before, during, and after joint exercises and real-world operations. DST members work in conjunction with USJFCOM Deployable Training Teams (DTTs) during pre-exercise/deployment training, while deployed to provide on-scene support during exercises and real-world

II-7

operations; and in assisting in the preparation of the Commander’s Summary report upon redeployment to identify best practices, lessons learned and other processes and procedures that have potential joint implications. 3. JWFC Joint Management Offices (JMO):

a. Information Operations (IO) JMO: (1) IO Support. A JWFC IO (Psychological Operations, Computer Network Attack & Computer Network Defense, Electronic Warfare, Operations Security, and Military Deception) planner is assigned to each geographic combatant command JWFC supported exercise to assist the training audience in the design and development of IO training objectives. The planner routinely coordinates additional support externally from the IO community (e.g. Joint Information Operations Warfare Command, Service Information Warfare Centers, JFCC-NW, etc.) and other external agencies (e.g. JITC, NSA, JSC, etc.) and coordinates “live activities” (e.g. Red Team participation, cyber and close access, IO range use, and communications security monitoring) as necessary to support and accomplish training objectives.

(2) Information Operations Range (IOR). The IO Range provides a secure, persistent,

flexible, seamless, and realistic experimentation, test, training and exercise environment enabling the Services and combatant commands to visualize non-kinetic weapons effects, understand the intricate and interactive effects generated by kinetic and non-kinetic weapons, and achieve the same level of confidence and expertise employing IO weapons that they have with kinetic weapons. The functional structure of the IO Range is based on the integration of existing ranges, laboratories, information warfare centers, and other Government facilities currently supporting IO test, training, exercise, and experimentation events.

(3) IO Range Support. The IO Range supports exercises (to include mission rehearsals,

training, developmental test and evaluation (OT&E) to meet Combatant Commander and Service IO requirements. Additionally, it provides an environment for IO experimentation, Advanced Concept Technology Demonstrations (ACTDs), Joint Capability Technology Demonstrations (JCTDs), Advanced Technology Demonstration (ATDs), modeling and simulation Studies and Analyses, and TTP development. The IO Range is coordinating with USSTRATCOM’s IO Joint Munitions Effects Manual (JMEM) effort and other IO development activities.

b. Joint Knowledge Development and Distribution Capability (JKDDC) JMO. JKDDC focuses on

web-enabled joint individual training. It provides our military forces with distance learning by creating, storing, imparting, and applying knowledge to enhance an individual’s ability to think joint intuitively. It develops and distributes joint knowledge via a dynamic, global-knowledge network that provides immediate access to joint training resources. JKO is the operational arm of JKDDC. JKO is USJFCOM’s cornerstone for implementing DOD’s advanced distributed learning strategy. It is a comprehensive web-based source of joint task force and combatant command battle staff training information. It provides initial training opportunities prior to participating in joint training events, or in preparation for real-world operations. JKDDC Multinational, formerly the RCSN, provides education and training capabilities through JKO to combatant commanders and multinational partners in an effort to strengthen security cooperation strategies in their areas of operations.

c. Joint National Training Capability (JNTC) JMO. The JNTC JMO oversees budget planning and

execution and conducts configuration management for the entire program. The JMO leads the effort to collect, merge, and validate JNTC joint training budgetary requirements by facilitating, monitoring, and overseeing JNTC processes. The JMO, in conjunction with stakeholder working groups, develops JNTC investment and acquisition strategies, planning year and execution year budgets, and execution plans.

d. Joint Advanced Concepts (JAC). The JAC program finds, demonstrates, transitions, and

transfers the most promising operational concepts and technology solutions for transformational, joint, and coalition educations and training. The JAC identifies JWFC candidate events for insertion of

II-8

advanced concepts and technologies. These technologies/concepts can be but are not limited to Joint Capability Technology Demonstrations (JCTDs), limited objective experiments, pilot demonstrations, functional training concepts, etc.

4. JWFC Supporting Organizations: a. Joint Enabling Capabilities Command (JECC), Suffolk, VA. Mission statement is under revision pending formal approval.

b. Joint Personnel Recovery Agency (JPRA), Washington, D.C. The Joint Personnel Recovery Agency (JPRA) supports DOD’s preparation, planning, execution, and adaptation of Personnel Recovery (PR). PR includes military, diplomatic, and civil efforts to affect the recovery and reintegration of personnel who become isolated while participating in a US sponsored military activity or mission and are, or may be, in a situation where they must survive, evade, resist, or escape. Personnel Recovery Support Teams (PRST) are one method by which JPRA accomplishes its training and support tasks. A PRST is a task organized, rapidly deployable, and when appropriate, regionally oriented teams, providing subject matter experts who advise, assist, guide or train commanders, forces and organizations and potential isolated personnel responsible for conducting or supporting personnel recovery operations. c. Joint Deployment Training Center (JDTC), Ft. Eustis, VA. The Joint Deployment Training Center provides a consistent training program for the joint community through its standardized instructional material, instructor proficiency, and centralized management and control. The JDTC provides training to the joint community through resident instruction, Mobile Training Teams (MTTs) and distributed learning products via the SIPRNET. The JDTC training program is evolving to ensure that the program meets the needs of the joint community and grows as the processes, procedures, and applications continue to change and mature. d. The Joint Targeting School (JTS), Dam Neck, VA. The JTS instructs mid career personnel the Joint Targeting process, based on the six step joint targeting cycle. Four core periods of instruction are given: Staff course (joint doctrine and the joint targeting cycle), applications course (computer simulation methods to predict weapons capabilities against targets), Joint BDA course (focusing on phase 1 and 2 battle damage assessment), and collateral damage methodology. e. NATO School, Oberammergau, Germany. The NATO School is an international organization founded on a bilateral arrangement between the U.S. and Germany. Pursuant to the 12 JUL 2005 CJCS MEMO, USJFCOM has assumed lead agent responsibilities for the NATO School (NS), and the U.S. Element, NS, has been transferred COCOM to USJFCOM. Since transfer of responsibility for the U.S. involvement in the NS, the USJFCOM Directorates have been working collaboratively with ACT to further develop and support the NS mission. The NS mission parallels the Joint Trainer mission of USJFCOM, and association with the NS supports JFCOM interests in multinational training transformation. For example, the NATO School’s robust activities and collaboration with NATO’s various Centers of Excellence provides training transformation synergies with the JNTC efforts to network U.S. Military Services and multinational partners into a distributive environment with a global reach. The alignment of the NATO School with USJFCOM has helped cultivate the USJFCOM - ACT relationship which is supportive of the training transformation efforts of the United States, other Alliance members, and Partnership for Peace nations. USJFCOM will continue to develop its U.S. lead agent role with the NS and the collaborative relationship with ACT to ensure the NS education and training mission is effectively met. f. Joint Warfighting Center Support Team (JST): (1) The JST is a civilian contractor team that provides non-personal general and technical support to the JWFC organization to ensure the successful execution of the USJFCOM joint training

II-9

administered program. The JST provides general support contractor tasks to include, among others, major exercise support to the combatant commanders and battle staffs and JWFC facilities support. (2) Throughout the handbook, JST positions and functions will be specifically noted. For all aspects of event support, the JWFC Desk Officer will interact directly with a Joint Event Support Team (JEST) Lead Planner and one of nine Event Support Teams in the JST Joint Operations Support Group. The JST is structured and resourced in a manner to support all JWFC sponsored events.

II-10

Intentionally Blank

III-1

CHAPTER III: JOINT TRAINING SYSTEM

"The JTS [Joint Training System] is a 4-phased Methodology that aligns training strategy with assigned missions to produce trained and ready individuals, units, and staffs."

CJCSM 3500.03B, Joint Training Manual for the Armed Forces of the United States 1. Overview a. Joint Training System (JTS). The JTS meets a critical training need by providing the joint community and joint force commanders with a process that ensures the US military is trained based on joint doctrine and capable of performing its mission across the range of military operations. Guidelines for the system are established in CJCS Instruction 3500.01E, Joint Training Policy and Guidance for the Armed Forces of the United States, while detailed information is contained in CJCS Manual 3500.03B, The Joint Training Manual for the Armed Forces of the United States. The JTS is a four-phased methodology that aligns training strategy with assigned missions to produce trained and ready individuals, units, and staffs. JTS phases are depicted in Figure III-1. The JTS requires commanders to develop training plans, keyed to the training requirements that detail the training events to be conducted. It defines the framework for training event design that allows commanders to execute the training, based on the command training plan. The JTS encompasses data related to doctrine, organization, training, materiel, leadership and education, personnel, and facilities (DOTMLPF). Lastly, the JTS provides commanders the ability to assess the training conducted, evaluate its effectiveness, and determine where to direct training in the future.

The Joint Training System

Requirements Planso Derived from National Military

Strategy and Assigned Missionso Driven by Mission Requirements,

Training Audience, and Tools

Based on Commander’s Intent& Joint Doctrine

Stated in Terms of Joint Mission-Essential Tasks,Conditions, and Joint Standards

ExecutionAssessments

ImproveImproveJointJoint

ReadinessReadiness

It is a Commander’s Responsibilityto Ensure that All Joint Training Events are Evaluated

o Commander Assesses:

Identify Ability to Meet Joint Standards:Strengths/Deficiencies in Doctrine, Organization, Training, Materiel,Leadership & Education, Personnel,and Facilities

Training EffectivenessJoint Readiness

Creates Joint Training Plan andEstablishes Objectives to MeetTraining Requirements

Guidance Provided and SchedulesDeconflicted by CJCS and USJFCOMusing JTIMS

o Joint Training Conducted by CJCS & Combatant Commands

JMETL

JTP

TPE

MTA

Requirements Planso Derived from National Military

Strategy and Assigned Missionso Driven by Mission Requirements,

Training Audience, and Tools

Based on Commander’s Intent& Joint Doctrine

Stated in Terms of Joint Mission-Essential Tasks,Conditions, and Joint Standards

ExecutionAssessments


ReadinessReadiness


ReadinessReadiness

It is a Commander’s Responsibilityto Ensure that All Joint Training Events are Evaluated

o Commander Assesses:

Identify Ability to Meet Joint Standards:Strengths/Deficiencies in Doctrine, Organization, Training, Materiel,Leadership & Education, Personnel,and Facilities

Training EffectivenessJoint Readiness

Creates Joint Training Plan andEstablishes Objectives to MeetTraining Requirements

Guidance Provided and SchedulesDeconflicted by CJCS and USJFCOMusing JTIMS

o Joint Training Conducted by CJCS & Combatant Commands

JMETL

JTP

TPE

MTA

Figure III-1. The Joint Training System

b. JTS: Inputs, Processes, and Outputs. The JTS phases are structured such that the output or product of one phase provides input for the next phase in the system. Figure III-2 depicts the inputs, processes, and outputs associated with each JTS phase.

III-2

JTS: Inputs, Processes, and Outputs

Requirements Plans Execution Assessment

I N P U T S

• Current National Military Strategy (NMS)

• Joint Strategic Capabilities Plans (JSCP)

• Presidential and SecDef Directives

• Treaty Obligations • Unified Command Plan

(UCP) • Security Cooperation

Plans • DOD Directives • Command Plans

(OPLANs/CONPLANs) • Higher HQs JMETL* • Joint Doctrine • Commander’s

Guidance* • UJTL/Service Task

Lists*

• J/AMETL(T/C/S/Org)* • SecDef / CJCS High

Interest Training Issues • Combatant Command High

Interest Training Requirements

• Joint Doctrine • Standard Operating

Procedures (SOPs) • Master Training Guides

(MTGs) • Relevant Lessons Learned

(LL) • Commander’/Agency

Director’s Training Guidance* (C/ATG)

• Training Proficiency Assessment/Mission Training Assessment (TPA/MTA)*

• Command, Component, Agency Training Plans*

• Joint Training Schedule*

• Relevant LL

• JTP* • TPOs/TPEs* • Informal

Results • Actual

Operations • Relevant

Lessons Learned • External Inputs • Other Feedback

P R O C E S S E S

• Conduct Mission Analysis to Identify Tasks

• Select Tasks from UJTL* • Select/Apply

essentiality Criteria • Select J/AMETs* • Select Responsible

Organizations* • Determine and select*

relevant Conditions and Standards

• Supporting, &, Command-Linked Tasks*

• Commander/Director Approves J/AMETL

• Revise C/ATG* • Analyze J/AMETs • Review TPA of JMET -

Organizations* • Refine Training Audience

based on TPA* • Develop Training

Objectives* (TO) • Determine Training

Methods* • Design Training Event

/Schedule Resources* • Publish J/ATP *

• Execute Joint Event Life Cycle (JELC)

• Develop*/Conduct/ Evaluate Academic Training Events

• Develop*/Conduct*/ Evaluate* Exercises

• Develop/Capture* Task Performance Observations (TPOs)*

• Review TPOs* • Determine/Document*

Training Proficiency Evaluation level (TPE) o T-Trained o P-Partially Trained o U-Untrained o N-Not Observed

• Develop/forward AAR*

At each echelon within the command, and within each subordinate organization, commanders /directors: • Analyze TPEs* from

Phase III • Review relevant LL

in other military operations

• Prepare Staff/Unit Assessment

• Develop TPAs* • Develop MTAs* • Obtain

Commander’s Approval of Proposed TPAs and MTAs

• Document audience TPAs, and Mission MTAs, in JTIMS

• Determine/forward Lessons

• Identify/Forward Issues

O U T P U T S

• J/AMETL* • Tasks, Conditions,

Standards, Organizations (T/C/S/Org)*

• Command JTP • Component Training Plans* • CSA ATP*

• TPOs*/TPEs*

• C/ATG* • TPAs*, MTAs* • Validated LL • Defined Issues

* Supported by JTIMS Note: Acronyms and definitions are listed in Glossary.

Figure III-2. JTS: Inputs, Processes, and Outputs c. Joint Training Information Management System (JTIMS). (1) Overview. The JTIMS supports with automated tools the requirements-based Joint Training System (JTS). The JTIMS is a multi-user, Web-based suite of tools that links critical DOD and joint automation programs. The JTIMS integrated information management tools assist the joint trainer by

III-3

identifying, collecting, storing, and disseminating the data required to execute the command joint training plan. (2) JTS/JTIMS Interface. The JTS and the JTIMS interfaces will be discussed below in each JTS Phase discussion. Detailed information concerning the JTIMS operating system can be found in the JTIMS Quick Reference Guide (QRG) on the JTIMS web site at https://jtims.js.smil.mil/jtims. (3) JTIMS Implementation. . See Appendix A, “Introduction and Administration Information,” Appendix B, “Rolls and Responsibilities,” and Appendix C, “Training,” to Enclosure (3), “Joint Training Information Management System (JTIMS) for basic business rules regarding JTIMS implementation at USJFCOM/JWFC. 2. Phase I (Requirements) -- Determine Mission Essential Tasks a. Purpose. The purpose of JTS Phase I (Requirements) is for combatant commands and agencies to capture the tasks or functions required to accomplish assigned missions. The inputs, processes, and outputs of Phase I are listed in Figure III-2 and discussed in the following paragraphs. b. Inputs. The requirements phase defines mission requirements in terms of tasks that must be performed by the command and the responsible organizations at all levels throughout the force. Sources from which missions are identified include the National Military Strategy, Joint Strategic Capabilities Plan, Unified Command Plan, Presidential and Secretary of Defense directives, theater security cooperation plans, commander's guidance, and joint doctrine. c. Processes. A mission analysis is conducted that results in the production of the command joint mission-essential task list (JMETL). Use of the Joint Mission Essential Task List (JMETL) Development Handbook (September 2002), will assist in this command wide process. The JMETL details those tasks that are essential to a command's or agency's ability to perform assigned missions and include supporting tasks and command linked tasks. Supporting tasks are those that contribute to the accomplishment of a joint mission-essential task (JMET) and are performed by subordinate elements of a joint force, such as joint staff or functional components. Command-linked tasks are those that must be performed by another major command in order for a combatant command to perform its own mission. The mission essential task (MET) build process is physically accomplished in the Defense Readiness Reporting System (DRRS). d. Outputs. The command approved JMETL becomes the output for Phase I (Requirements). The JMETL represents the link between the National Military Strategy and the combatant commander's strategy and assigned tasks. The JMETL provides the basis for Phase II (Plans). e. JTIMS Interface. The approved JMETLs once inputted in DRRS are dynamically pushed to the JTIMS to support the development, management and execution of other JTS products. f. JWFC Support. (1) JMETL Development Workshop. JWFC can facilitate for subordinate commands a workshop to support JMETL identification and development. (2) DRRS training. JWFC can arrange subordinate command DRRS training if required. g. Reference Material. Resources available to assist commands and agencies in developing their specific tasks in the proper format and language include CJCS Manual 3500.03B, The Joint Training Manual for the Armed Forces of the United States, Enclosure C - Phase I (Requirements), CJCS Manual 3500.04 (series), the Universal Joint Task List, and the CJCS JMETL Development Handbook, Sep 2002.

III-4

3. Phase II (Plans) -- Develop Joint Training Plans (JTP) a. Purpose. The purpose of Phase II (Plans) is to produce a Joint Training Plan (JTP). The JTP provides the commander’s guidance and a comprehensive plan of action to link assessment derived training requirements with training events to accomplish training audience objectives. The JTP identifies those individuals and organizations that need training, the Training Objectives (TOs) of the required training, the training events needed to satisfy these Training Objectives, and the estimated resources required to conduct the training events. The inputs, processes, and outputs of Phase II are listed in Figure III-2 and discussed in the following paragraphs. b. Inputs. JTPs developed in Phase II are based on capability requirements identified in the JMETL in Phase I (Requirements). This phase begins once the command METL is developed and approved by the commander. Such things as the CJCS High Interest Training Issues; joint doctrine; joint tactics, techniques, and procedures; lessons learned; and output from the assessment phase from past training events and exercises are considered when developing joint training plans. c. Processes. (1) The flowchart in Figure III-3 provides a disciplined approach to JTP development. As depicted the JTP is built incrementally, one tab at a time. JTP Tab descriptions can be found at Enclosure (2), “Joint Training Plan TAB Description,” to this Handbook. (2) An initial training assessment is conducted to determine the status of training proficiency for each mission essential task (MET), within each assigned mission. Training requirements are then determined from training deficiencies found. TOs are derived from the MET’s conditions, and standards. TOs describe for the training audience the desired outcome of a training activity, the impetus for initiating a training activity, and the measures for evaluating the performance. The TO relates to the successful accomplishment of the JMET and consists of performance objectives, training conditions, and level of performance. TOs are based on joint doctrine, Commander’s/Directors guidance, and organizational standing operating procedures. (3) The assessed level of performance also determines the training methods (academic/exercise), training modes (CPX/FTX/computer based/distance learning/workshop/etc), and training media (VTC/DVD/computer software/etc) required. (4) As resources are identified, joint training events, either academic or exercise, are developed. (5) The events are then scheduled, resourced, and deconflicted. d. Outputs. The commander's training guidance and the command's MET assessment drive the development of the output of Phase II (Plans), which is the command Training Plan. The Training Plan states command missions in general terms, restates JMETL, presents commander's training guidance and identifies the commander’s high interest training requirements (HITR). It identifies audiences requiring training and the events, with resources and TOs, needed to train them to accomplish the required tasks, under relevant conditions, to meet required standards. e. JTIMS Interface. JTIMS is designed to assist the commands in developing, managing and approving their JTPs. The JTIMS provides the ability to post the Commander’s training guidance and HITR. The JTIMS supports the collaborative development of global and local joint training schedules to include an online scheduling and deconfliction capability. As resources are identified, the JELC methodology is used to developed in JTIMS joint training events, either academic or exercise. f. JWFC Support. JWFC can for USJFCOM subordinates assist with TO development by facilitating a Training Objective Workshop (TOW). The goal of the two or three day workshops is to develop training objectives, which includes identifying the training audience, performance, training situation, level of

III-5

performance, and the methods, mode, and media at the board, center, cell, and bureau level. Training objectives are developed specific to the event or exercise. h. Reference Material. See CJCS Manual 3500.03B, The Joint Training Manual for the Armed Forces of the United States, Enclosure D - Phase II (Plans), and Enclosure K - Joint Training Plan Format for more detailed information.

J/ATP Flow Chart

Figure III-3. J/ATP Flow Chart

4. Phase III (Execution) -- Execute Joint and Agency Training Plans a. Purpose. The purpose of Phase III (Execution) is to conduct the events and exercises as planned in the joint and agency training plans and to evaluate performance relative to specified training objectives. The inputs, processes, and outputs of Phase III are depicted in Figure III-2 and discussed in the following paragraphs. b. Inputs. The focus of the execution phase is preparing, executing, and evaluating command joint training events. The input for this phase is an approved joint training plan coupled with a training schedule.

III-6

c. Processes. Joint training events, either academic or exercise, are designed using the Joint Event Life Cycle (JELC) methodology. The JELC, a cycle within Phase III (Execution), consists of five stages -- Design; Planning; Preparation; Execution and Evaluation; Analysis and Reports. The JELC provides an orderly sequence of processes, products, activities, and decision points that, if followed, will assist the command in achieving the training goals and objectives in the training event. All joint training events, academic or exercise, are evaluated to determine whether or not the training audience accomplished the training objectives. Evaluation of each training event is done using event by event observations which are called Training Proficiency Observations (TPOs). The collective appraisal of the TPOs determines the training audience ability to achieve the event’s TOs. These aggregated results are used in Phase IV (Assessment) to assist in determining readiness and guide development of the next training cycle. See Figure III-4. d. Outputs. The output of Phase III includes execution of joint training events, either academic or exercise, collection of TPOs and determination of the Training Proficiency Evaluation (TPE) of the training audience. Potential DOTMLPF issues and lessons learned (LL) are also identified during this phase of the JTS. The final outputs of Phase III are the after action reports (AARs), the Commander Summary Reports (CSRs) and the TPEs. The TPEs directly support Phase IV Assessment. e. JTIMS Interface. The JTIMS supports training event planning, coordination, execution, review and analysis. It will automate the Joint Event Life Cycle (JELC) down to the JTF component and unit level. It provides for the development of the Collection Management Plan (CMP), collection of TPOs, determination of TPE and production of the Commander’s Summary Report (CSR). See Enclosure (3) to this Handbook for JTIM access, use and procedures. f. JWFC Support. The JWFC supports actual events or exercises in the following ways: (1) Event Development Conferences. Within the JELC and prior to the training audience (TA) executing an exercise, a series of conferences are conducted in order to appropriately prepare the TA for the conduct of the event. These conferences use a series of meetings and workshops to assist the command or agency in refining their training requirements for the event. Conference activities ensure "refining" the event as identified in their training plan, or in lieu of a functional joint training plan, development of JMETL, exercise objectives, and training objectives. Products from conferences include JMETL and exercise objective identification, exercise "mission refinement," and training objective refinement. For detailed information about each conference, see Chapter V, "Joint Event Life Cycle." (2) Joint Master Scenario Events List (JMSEL) Development. During the course of training event development, a JMSEL may be required. This list of events should be developed from the training objectives that previously were developed. JWFC personnel are available to assist commands in developing the JMSEL events that accomplish the designated training objectives. JWFC assistance may or may not be part of a JWFC supported exercise. JMSEL workshop dates and duration normally are scheduled in advance (at the CDC). For more information on JMSEL development, see Chapter V, "Joint Event Life Cycle," and Chapter VI, paragraph 2. “Scenario and MSEL support." (3) Collection Management Plan (CMP) Development. The purpose of the CMP is to delineate the procedures and responsibilities of a JWFC team from Joint Training Division for the collection and analysis of joint training exercises. The CMP provides guidance for pre-exercise analysis, a framework for organizing observer data, and a basis for training objective observations. The CMP serves to focus the collection process to ensure that all operational exercise training objectives are observed. The plan will be of sufficient detail to accurately describe the “who, what, when, where, and how.” Based on this data, JWFC analysts will develop the feedback products, which include the facilitated after action reviews (FAARs) and the commander's summary report (CSR). A CMP is developed for each exercise and delivered to the Chief of the JWFC Deployable Training Team (DTT), five days prior to execution. The task performance evaluations (TPEs) developed from the Training Proficiency Observation (TPO) collected as a result of the CMP will assist in evaluating the training event and are used later by the

III-7

commander to develop the command's training proficiency assessment (TPA) in Phase IV. The JWFC can assist in the development of the training event CMP, observe and collect observations related to the training objectives during the training event, and the development of TPEs. This assistance is provided through the normal course of a JWFC supported exercise, or may be requested separately. (4) Facilitated After Action Review (FAAR) Development. The FAAR will occur at the conclusion of the exercise. It will include a JWFC led discussion of key operational take a ways, significant lessons learned or accomplishments by the participants, and recommendations or ways ahead. As part of the FAAR, the training audience usually identifies those functional areas they want to sustain or improve based on their experience in the exercise. In addition to the formal FAAR, the DTT normally conducts functional AARs designed to provide additional training feedback at the staff action officer level. These informal reviews should take place whenever there is a logical reason to conduct one. In this way, events or actions are fresh in the minds of all participants and maximum training benefit is obtained. Functional AARs are centered on staff section functional area training objectives as they relate to the exercise. For more information on AARs, see Chapter V, "Joint Event Life Cycle." (5) Commander's Summary Report (CSR). The CSR provides the commander a written record of the significant strengths and weaknesses of the staff's performance relative to the selected JMETs and operational training objectives. The DTT normally will prepare the CSR on site at the conclusion of the exercise and deliver it to the supported command two days after the FAAR. Usually JWFC will provide only one CSR for a two-tiered exercise and the combatant commander will determine which command will receive the written report. (See Chapter V, "Joint Event Life Cycle," and Chapter VI, “Joint Warfighting Center Event Support,” paragraph 10, “Observation, Training, and Analysis Support” for CSR information.) g. Reference Material. See CJCS Manual 3500.03B, The Joint Training Manual for the Armed Forces of the United States, Enclosure E - Phase III (Execution) for more detailed information. 5. Phase IV (Assessment) -- Assess Training Performance a. Purpose. In this final phase of the JTS, the commander is looking for a determination of the command or agency mission capability from a training viewpoint. The purpose of Phase IV (Assessment) is to determine which organizations within the command or agency are able to perform at the level required to meet the task standard(s) of the MET, and which missions the command and agency is trained to accomplish. The inputs, processes, and outputs of Phase IV are depicted in Figure III-2 and discussed in the following paragraphs. b. Inputs. The products from the Phase III (Execution) become inputs for the assessment phase. Training Proficiency Evaluations (TPEs) from Phase III, Lessons Learned relevant to the organization, AARs, CSRs and performance personally observed should all be considered by the commander. c. Processes. The assessment is a command responsibility. The commander, taking into account results gathered using the CMPs for the events, performs the actual assessment. The commander assesses the command’s individual task assessments to determine a Training Proficiency Assessment (TPA). The TPAs and JMETs associated with specific missions are then analyzed to produce Mission Training Assessments (MTAs). Commander’s judgment, supported by objective data input, forms the MTA for each mission. The Commander/Director should determine whether the command is trained to accomplish the mission. The assessments seek to answer the questions, “Is the organization trained to accomplish specific tasks?” and, “Is the command trained to accomplish its assigned missions?” While assessment completes the training cycle it also begins the next cycle, because assessments drive future training plans. See Figure III-4. d. Outputs. The products of Phase IV are the TPAs and MTAs, the Commander’s determination of whether the command is trained to accomplish the mission. Assessments of less than fully trained on

III-8

existing JMETs, combined with any new JMETs developed and the drafting of an updated Commander’s guidance form the primary training requirements for the next training cycle. e. JTIMS Interface. JTIMS supports assessment of joint training events by automating the command’s ability to produce Training Proficiency Assessments (TPAs), derived from the Training Proficiency Evaluations (TPEs) made during the Execution Phase. Once the TPAs for each task are completed, DRRS will pull approved TPAs, with associated issues and resolutions, from JTIMS as part of the DRRS training assessment tab which supports the command’s overall readiness assessment in DRRS. Once the MTAs are completed they are also pulled and displayed in DRRS. f. JWFC Support. JWFC assistance in developing the supported command’s training assessment is provided through workshops, academics, and seminars. JWFC also provides assistance to the command training assessment through development of AARs, a FAAR, and a CSR which the commander used to make his mission readiness evaluations. g. Reference Material. See CJCS Manual 3500.03B, The Joint Training Manual for the Armed Forces of the United States, Enclosure F - Phase IV (Assessment) for more detailed information.

Execution and Assessment

ExecutionPhase

AssessmentPhase

Use of JELC & CMP - Event Observations

IN JTIMSTask

PerformanceObservations

(TPOs)Collected,based on Training

Objectives (TOs), by Internal or External

Observers

Training& Exercise

Events

ActualOperations

ExternalFeedback

InformalInput

TrainingProficiencyAssessment

MissionTraining

Assessment

Directoratesdetermine if JMETs

are trained tothe standards

T (Trained)P (Partially Trained)

orU (Untrained)based on TPEs

Commander determines whether

the Commandis trained to accomplish

its Missions, based on TPAs(T- P- U)

TRAINING

PROFICIENCY

EVALUATION

Done by Training Audience Leaders in JTIMS

LessonsLearned

Figure III-4. Execution and Assessment 6. Summary a. The Joint Training System provides commanders with a systemic approach to assist in ensuring readiness levels required in their command are met through effective joint training. b. The JTS approach assists in identifying the functional responsibilities of assigned individuals and organizations in the form of tasks, conditions, and standards; identifying events and resources to

III-9

accomplish required training; conducting and evaluating training; and assessing the resulting performance of assigned individuals and organizations relative to their functional responsibilities. c. The JTIMS supports the facilitation and execution of processes within all four JTS Phases. JTIMS is the primary information support tool used to support combatant command joint training programs.

III-10

Intentionally Blank

IV-1

CHAPTER IV: JWFC JOINT TRAINING TIERS AND CAPABILITIES 1. General. The purpose of this chapter is to define the various JWFC joint training tiers, JWFC training capabilities, USJFCOM’s training capability support to the JWFC, and introduce capabilities supported by the Joint Warfighting Center and enabled through the Joint National Training Capability (JNTC). The categorization of “tiers of training” for exercise programs is not intended to imply an isolated approach to the conduct of joint training. Rather identifying tiers with associated training efforts provides a means of providing clarification to the various events executed within US Joint Forces Command’s (USJFCOM) joint training program. The JNTC functions to enhance the joint training program through designated Joint Management Offices (JMO) that manage day-to-day activities providing enabling capabilities for combatant command and Service training. While the JNTC JMOs oversee different programs, their collective efforts complement the joint training process by managing programs that provide dynamic, capabilities based training that emphasizes the mission requirements of the Combatant Commands while preserving the ability of the Services to train on their core competencies. The Joint Force Trainer’s primary focus is emphasis on joint interoperability across all levels of war: strategic, operational, and tactical. The JWFC goal – deliver trained, capable, interoperable joint forces. 2. Tiers of Training and Events. a. Tier 1: (National Level and Combatant Command training) – Joint training is designed to prepare national level organizations and combatant commander and staffs at the strategic and operational levels of war to function integrating interagency, non-governmental partners, and allies in highly complex environments. The components of the Department of Defense rarely will respond to a crisis independently, because global challenges require the Secretary of Defense to be an integral part of political, economic, and humanitarian initiatives requiring U S military resources providing responses alongside partners. The desired end state in integrating a diverse audience in a joint training environment is to identify core competencies, procedural disconnects, and common ground to achieve US unity of effort. b. Tier 2: (Joint Task Force Training) - Upon establishment by an designated authority, the Joint Task Force (JTF) incorporates joint training designed to assist the Commander, JTF in the preparation for conducting complex military operations at the operational level of conflict. The JTF is normally a part of a larger national or international effort assigned a specified mission or limited objective working in an environment that requires close coordination among a host of diverse agencies and organizations. c. Tier 3: (Functional Component Training) – Interoperability training designed for US military Service components ensuring the ability of systems, units, or forces to function within a joint, interagency, non-governmental, and multinational environment. This training is designed to prepare individuals, staffs, and Service units in response to the operational requirements and assigned missions of the combatant commands. d. Tier 4: (Individual Organizational Training) – Organizational training is based on unit policy and joint and Service doctrine linked to unit mission-essential tasks. This training focuses on basic, technical, and unit operational training to support joint force commanders. Service tactical training programs are focused at improving full spectrum proficiency of general purpose forces. Joint unit training follows the joint training system and ensure the readiness of specialized joint units. Joint unit training includes basic combat skills training, as well as individual, staff and collective training and specialized courses like the Joint Enabling Capabilities Planners and Systems Perspective of the Operational Environment courses.

IV-2

3. Multinational Training a. General. USJFCOM conducts a multinational training program in cooperation with the North Atlantic Treaty Organization's (NATO) Strategic Allied Command Transformation (SACT). The program focuses on three key areas: (1) the Partnership for Peace (PfP) Exercise Program, (2) the Regional Security Cooperation Network, and (3) Advanced Distributed Learning. The concept for the program is to create a triad of capability amongst Partnership for Peace (PfP) nations: modeling and simulation (M&S, advanced distributed learning, and distributed computer assisted exercises. Advanced distributed learning provides on-line learning tools for individual training. Distributed computer assisted exercises reinforces individual training and promotes the development of national simulation centers. b. PfP Program. The PfP program is a significant policy initiative that directly supports NATO goals and US National Security objectives. Those objectives ensure regional stability and security, encourage awareness and respect for the democratic process, promote the pursuit of economic prosperity among PfP nations, and organize partner nations under a cooperative security umbrella. The PfP Exercise Program is executed in cooperation with NATO. The program uses distributed computer assisted exercises as the backbone for training. 4. Interagency Training. USJFCOM works with a broad range of partners within the joint training enterprise to support joint warfighter development in response to the demands experienced in today’s operational environment. While the interagency community has always been a necessary focal point of joint training criteria, it has certainly emerged as a requisite partner for successful military operations. Interagency Training is an integral part of the JWFC joint training program. The intent of the JWFC interagency training is to plan, develop, coordinate, execute, and evaluate all components of interagency interaction/replication in all assigned USJFCOM JWFC exercises throughout the Joint Event Life Cycle. JWFC’s Interagency Joint Military Program Manager provides advice to the Commander, USJFCOM JWFC, the Operations Group Chief; Joint Exercise Division Chief and the individual desk officers on the conduct of training and exercises that involve aspects of the interagency process. 5. Joint Personnel Recovery Agency (JPRA). The Joint Personnel Recovery Agency shapes Personnel Recovery (PR) for the Department of Defense, interagency, and partner nations enabling commanders, forces, and individuals, to effectively accomplish their Personnel Recovery responsibilities. The JPRA develops, delivers, and assesses personnel recovery command and control (C2) specialized Survival, Evasion, Resistance, and Escape (SERE) training providing task organized, rapidly deployable, and regionally oriented teams who advise, assist, guide or train commanders, forces and organizations and potential isolated personnel responsible for conducting or supporting personnel recovery operations. 6. Joint Deployment Training Center (JDTC). The JDTC provides a consistent training program for the joint community through its standardized instructional material, instructor proficiency, and centralized management and control. The JDTC provides training to the joint community via Mobile Training Teams (MTTs) and resident instruction. The JDTC training program is evolutionary to ensure that the program meets the needs of the joint community and grows as the processes, procedures, and application continue to change and matures. 7. Knowledge and Information Fusion Exchange (KnIFE). KnIFE provides a “One-Stop-Shop” for customers to access Improvised Explosive Devices (IED) related information. KnIFE provides units training for deployment with current, relevant, in-theater information pertinent to their operations. KnIFE can rapidly inject actual combat scenarios for deploying units entering their training cycle. KnIFE participates in the Mission Rehearsal Exercise (MRX) Program, preparing command and staff personnel for missions to Iraq, Afghanistan, and the Horn of Africa (HOA). KnIFE participates in the design, preparation, and execution of storylines and MSEL injects for each exercise.

IV-3

8. Joint Public Affairs Support Element (JPASE). JPASE deploys joint media operations, communications and computer support to joint task forces and joint special operations task forces worldwide. JPASE enhances joint public affairs capability through training, doctrine development, and the establishment of joint standards and requirements to ensure the joint force commander has an organization of equipped, trained and ready public affairs professionals providing counsel, operational planning and tactical execution of communication strategies as a function of joint military operations in support of national objectives. 9. Integration of Capability Testing. The joint training enterprise provides the integrating environment to validate new capabilities and to lead the transformation of collective and individual joint training. The integration of emerging, mid-term and long term joint warfighting capability initiatives into joint exercises for test and validation consistent with accomplishing required training in support of JFCOM’s joint training and transformational responsibilities, seeks to examine potential solutions to identified warfighter deficiencies and shortfalls. This approach supports the philosophy of the Joint Training System (JTS) with the aim to improve readiness. Joint Training can thus serve not only as a useful means to inform the development process, but also as a means to transition capabilities from the hands of the developers into the hands of the warfighter. 10. Joint National Training Capability a. Background. The JNTC was established as the centerpiece of training transformation and is built upon the foundation of four pillars to deliver effective joint context to combatant command and Service training. The four pillars of joint context are: (1) realistic combat training; (2) adaptive opposing force (OPFOR); (3) common ground truth; and (4) high quality feedback. The four pillars allow the JNTC to establish and operate an affordable joint training capability that enables integration of combatant command, service, and government agency training components to “train like we operate” to support national security goals. b. Intent. The JNTC provides, across all levels of warfighting, a dynamic, capabilities-based training environment through accredited programs and certified sites and systems focused on joint mission essential tasks articulated by Combatant Commands and Service requirements. The long term strategic goal of reaching Full Operational Capability (FOC) will be achieved when all major Service training programs have been accredited to a baseline set of joint tasks and all supporting sites and systems are interoperable to a specific set of standards. JNTC’s ultimate goal is to maintain programs that keep pace with the emerging dynamics experienced in a global operational environment impacting both friendly and enemy capabilities. New requirements are emerging, necessitating modification to existing joint tasks and identification of new ones that, in turn, produce training capability gaps and seams within combatant command and Service training programs. The JNTC intends to be ready to meet those challenges and fulfill its role as the centerpiece of DOD’s efforts towards training transformation. c. Implementation. As new requirements emerge, the JNTC will place a priority on training, education and experimentation capabilities that are forward looking and address joint, “whole government” and multi-national operations. Focus on key learning capabilities which improve skills in adaptability, agility, anticipation of the adversary, foreign language, and foreign cultural insights; particularly interpersonal relations and negotiation. Training activities will strike a balance between engagement against a global, irregular adversary and a traditional adversary and Joint Operations Concepts must be developed, experimented upon, trained to and evaluated. The JNTC Management Office (JMO) is the focal point for JNTC planning, program preparation, and execution of JNTC resources and programs in collaboration with the Services, Special Operations Command, and the Joint Staff representing the other combatant commands. The JNTC JMO collects, merges, and validates JNTC training requirements.

IV-4

11. Summary. The joint training enterprise is comprised of the combatant commands, Services, OSD(P&R) and the Joint Staff J7. USJFCOM, as the lead agent for joint training, is the operational arm of DOD’s joint training program, providing joint training events and JTF/functional component certification support to the Joint Staff, combatant commanders and Services. The joint training enterprise provides the integrating environment to validate new capabilities and to lead transformation of collective and individual joint training. The primary objective of the JWFC is to deliver trained, capable, interoperable joint forces to the warfighter.

V-1

CHAPTER V: JOINT EVENT LIFE CYCLE 1. General a. Joint Event Life Cycle (JELC). All joint training events supported by the Joint Warfighting Center (JWFC) are to be designed, planned, and executed in accordance with the JELC. The JELC is a flexible planning tool that can be tailored to accommodate joint training and/or technology insertion events of varying levels of activity and complexity. Although, nominally, a 12-18 month process, the JELC can be modified to fit any timeframe required by and agreed upon by the parties involved. The JELC is resident in and applies to Phase III (Execution) of the Joint Training System (JTS)(see Chapter III) and is sometimes defined as a “cycle within a cycle.” The JELC (see Figure V-1) consists of the following five “stages” (as differentiated from the four “phases” of the JTS): Design; Planning; Preparation; Execution; and Analysis, Evaluation, and Reports. Furthermore, each stage of the JELC is defined by a series of planning conferences designed to provide ongoing guidance, monitor progress, identify challenges, establish tasking and provide a breakpoint between each stage. The JELC is intended to guide and assist event planners in a methodical process that ensures that specific joint training and event milestones are captured prior to event execution. For more detailed information on the JELC, see CJCS Manual 3500.03B, Joint Training Manual for the Armed Forces of the United States.

Figure V-1. Joint Event Life Cycle

b. The sophistication of collaboration tools (VTC and Defense Connect Online) is seen by JWFC as a force multiplier when viewed in respect to the increase in support requirements and decrease in available resources. The electronic distribution of JELC collaboration will provide USJFCOM JWFC more flexibility

V-2

and additional resources to support the combatant commands' requirements. JWFC Desk Officers will, when possible, use online collaboration for product requirements versus face to face interaction. JWFC acknowledges the need to maintain the flexibility of the JELC while working to get exercise planners to work more collaboratively. 2. Training Requirements Analysis a. Identification of Training Parameters. The success achieved in the development and conduct of a JTS Phase III training event is dependent upon the successful completion of the processes required in the preceding two phases of the JTS. This is where requirements are established and precursor planning is accomplished (Phase I - identification of requirements and Phase II - development of the command's Joint Training Plans [JTPs]). The command's joint training plans should provide the following required exercise design parameters: (1) Event type and purpose (2) Event training audience (3) Event objectives to include identification of joint mission- essential tasks (JMETs) and the supporting event training objectives (TOs). b. Training Objective Development. Training objectives (TO) provide a solid foundation for the design, planning, preparation and execution of any joint exercise. The supported command will develop training objectives for each training event. The most common method of developing training objectives is via the Training Objective Workshop (TOW). However, commands with “mature” Joint Training Plans (JTP) and a stable mission set may only require a review and validation of existing TO’s prior to commencement of the JELC for a given exercise. If required, however, the Training Objective Workshop (TOW) is a JTS Phase II function that provides the supported command an opportunity to review and validate their JTP training objectives (TOs), as well as develop new ones if required, for the specific mission being exercised. Ideally, the TOW will always be conducted prior to the Concept Development Conference (CDC) which marks the commencement of the Design Stage (Stage I) of the JELC. The format of this 3 to 5 day workshop allows representatives from the various command staff offices as well as boards, bureaus, centers, and cells to closely examine their standing JTP list of training objectives for currency and applicability. Revisions to existing TOs, the creation of new TOs, and changes in mission taskings form the basis for updating the command JTP. 3. Joint Event Life Cycle a. JELC Stage 1 - Design. The Design stage commences with the preparations for and completion of the Concept Development Conference (CDC) and ends with the Initial Planning Conference (IPC). Actions during the design stage include such things as:

• Review and refinement of the training requirements including the JMETs and TOs from the command's JTP

• Identification of the training audience and the academic training concept. • Development of a Plan of Action and Milestones (POA&M). (See Enclosure 4, “JELC POA&M.” • Drafting of the scenario outline. • Identification of the desired After Action Review (AAR) process and products.

V-3

Figure V-2. Joint Event Life Cycle - Stage 1

Concept Development Conference (CDC). The CDC is a precursor to the Initial Planning Conference (IPC). Its purpose is to ensure that all prerequisite elements and key parameters have been identified and initial decisions made concerning the assignment of offices of primary responsibility (OPRs) for various tasks , as well as the establishment of tasking and decision due dates in the form of a Plan of Action and Milestones (POA&M). The CDC is typically conducted 12 to 18 months prior to event execution based on a “notional” JELC duration. If the command's JTP is a mature viable document, a CDC may not be required and event coordination may be accomplished via collaborative means (such as video teleconferencing (VTC)) among key players. Briefs provided by the supported command should include: commander's mission statement, exercise objectives, planning guidance, training audience, approved JMETs, updated TOs, exercise classification, and other pertinent event information. Much of this may also (or alternatively) be promulgated via the Combatant Commander’s Exercise Initiating Directive for each event. Concept Development Conference Outcomes. Among the products and processes that should be completed and/or validated at the CDC are the following:

• The exercise purpose defined (commander's guidance). • Exercise Objectives and Training Objectives (TOs). • Identification of the primary training audience. • Development of a draft exercise control plan. • C4I and intelligence concepts.

V-4

• Draft (supported command) joint Exercise Initiating Directive. (See Enclosures 7 and 8. “Initiating Directive Example (message format),” and “Initiating Directive Example (text format).”

• Exercise locations • Draft milestones • Outline of the road-to-crisis (RTC). • Role (if required) of an opposing force (OPFOR) and/or situational force (SITFOR). See

Enclosure (12), “OPFOR/Response Cell. • Identification of Deployable Training Team (DTT) and AAR requirements. • Proposed simulation requirements.

Note: CDC briefings, wrap-up message, and taskings should be posted on the supported command and JWFC web sites for reference. Initial Planning Conference (IPC). The IPC is routinely conducted 10 to 12 months prior to event execution and lasts three to four days. Prior to the IPC the supported command should have completed a draft joint exercise directive, CDC outcomes should be approved (event type, event objectives, JMETs, exercise classification, and training audience), and TOs should be finalized and approved. Conference briefs, at a minimum, should include: approved exercise design, approved TOs, potential doctrine issues and implications, and the initial road-to-crisis. Typical working groups include: operations, intelligence, and scenario; M&S; communications, Exercise Support Manning Document (ESMD); deployment logistics; DTT; and exercise management. Exercise locations and force protection issues for deployed exercises also need to be addressed. Completion of the IPC marks the end of the JELC Design Stage. Initial Planning Conference Outcomes. Among the products and processes that should be completed and/or validated at the IPC are the following:

• Deployed logistic requirements. • Refined C4I requirements. • Validation of the exercise milestones. • Review potential exercise inserts (JETA, FTE) • Review JS guidance • Draft JECG structure. • Draft Event Control Plan. • Draft database requirements. • Outlined MSEL conference requirements. • Development of the FAAR concept of operations.

Note: IPC briefings, wrap-up message, and taskings should be posted on the supported command and JWFC web site for reference. b. JELC Stage 2 - Planning. This stage normally begins following the conclusion of the IPC and ends with the completion of the Middle Planning Conference (MPC). Key events conducted during this stage include: MSEL Development Conference (MDC); a site survey; initial simulation database build (See Enclosure 9, “Remote Site Survey Checklist” for further details. Key objectives of this stage are to develop products approved during the CDC and IPC as well as finalize concepts and supporting plans. Furthermore the training audience, and training requirements are identified and MSEL development is initiated See Figure V-3, which further details the flow of activities during the planning stage.

V-5

* OPFOR CAMPAIGN PLAN DEVELOPMENT* OPFOR CAMPAIGN PLAN DEVELOPMENTMSEL DEVELOPMENTMSEL DEVELOPMENTEVENT CONTROL PLAN DEVELOPMENTEVENT CONTROL PLAN DEVELOPMENT

2. PLANNING STAGE2. PLANNING STAGE

MSEL ManagerIDENTIFIED

Draft BLUFOROPLAN PlanDeveloped

ConferenceAttendees

IDENTIFIED

Event DirectiveWritten

Event Control Plan

BRIEFED

MPC MilestoneReview

FINALIZEEvent Directive

Database 2Requirements

BRIEFED

MSELBRIEFED

ScenarioBRIEFED

ScenarioDELIVERED

DATABASE TEST/BUILDDATABASE TEST/BUILDDBDB

BuildBuildTestTest

Draft OPFORCampaign Plan

Developed

MPC AgendaPUBLISHED

FINALIZE C4I& M&S

Concept

DTTDTTAcademic PlanAcademic Plan

BRIEFEDBRIEFED

MPCMPCMPCMSEL DevelopmentConference

MSEL MSEL DevelopmentDevelopmentConferenceConference

Draft MSELDeveloped

Event SupportEvent SupportSITE SITE SURVEYSURVEY

DTTDTTAcademicAcademic

PlanPlan

FINALIZEScenario

FINALIZEForce List

FINALIZELogistics Concept

FINALIZEExercise Support

FINALIZEJoint Manning

Documents

FINALIZETraining SPT

Rqmts



2. PLANNING STAGE2. PLANNING STAGE

MSEL ManagerIDENTIFIED

Draft BLUFOROPLAN PlanDeveloped

ConferenceAttendees

IDENTIFIED

Event DirectiveWritten

Event Control Plan

BRIEFED

MPC MilestoneReview

FINALIZEEvent Directive

Database 2Requirements

BRIEFED

MSELBRIEFED

ScenarioBRIEFED

ScenarioDELIVERED


BuildBuildTestTest

Draft OPFORCampaign Plan

Developed

MPC AgendaPUBLISHED

FINALIZE C4I& M&S

Concept

DTTDTTAcademic PlanAcademic Plan

BRIEFEDBRIEFED

MPCMPCMPCMSEL DevelopmentConference

MSEL MSEL DevelopmentDevelopmentConferenceConference

Draft MSELDeveloped

Event SupportEvent SupportSITE SITE SURVEYSURVEY

DTTDTTAcademicAcademic

PlanPlan

FINALIZEScenario

FINALIZEForce List

FINALIZELogistics Concept

FINALIZEExercise Support

FINALIZEJoint Manning

Documents

FINALIZETraining SPT

Rqmts


Middle (Mid) Planning Conference (MPC). The MPC is usually conducted 7 to 8 months prior to event execution and lasts approximately three days. Typical working groups include: operations, intelligence, scenario, M&S (including database); Comms; exercise manning; deployment logistics; and exercise management. Conference briefings may include: key features of the joint Exercise Directive; an overview of the draft Exercise Control Plan; the draft OPFOR/SITFOR CONOPS plan briefed to a selected audience; and the draft scenario/road-to-crisis reviewed. (See Enclosure 6, “Exercise Directive Example”) Mid-Planning Conference Outcomes. Among the products and processes that should be completed and/or validated at the MPC are the following:

• Exercise Directive ready for publication. • Development of a draft event control plan. • Draft Scenario RTC. • An FAAR concept of operations. • Final Planning Conference (FPC) agenda.

Master Scenario Event List (MSEL) Development Conference (MDC). The MDC is usually conducted either just prior to or immediately following the MPC. A draft MSEL is the deliverable product from this conference. Since the MSEL implementation process is highly dynamic during event execution the MSEL is not considered finalized until exercise termination (ENDEX). Conference briefs include: exercise objectives; TOs; scenario and road-to-crisis; OPFOR CONOPS plan overview highlighting major “muscle moves”; operation of the web-based Joint MSEL (JMSEL) tool; and the MSEL development

V-6

protocol. See Enclosure (10), Scenario Development,” and Enclosure (11), “MSEL Development" for more information on developing and refining the MSEL. MDC briefings, wrap-up messages, and taskings should be posted on the supported command and JWFC web site for reference. The draft MSEL is resident in the JMSEL data base and accessible to designated personnel. Model and Simulation Selection Process. Most JWFC supported exercises are conducted at the 3-star joint task force (JTF) or 4-star geographic combatant commander staff level. Model selection criteria involve considerations of: exercise objectives, type exercise, training audience, TOs, exercise budget, and manpower availability. This combination of considerations generally drives the selection of the simulation to be utilized in support of a given exercise. The JWFC provides various simulations from its M&S “tool kit.” The simulations include JCATS (Joint Conflict and Tactical Simulation), JTLS Joint Theater Level Simulation), and the JLVC (Joint Live Virtual and Constructive) federation consisting of JCATS, AWSIM (Air Warfare Simulation), JLOD (JCATS Low Overhead Driver), JSAF and various other simulation systems depending on the event to be supported. See Chapter VI, paragraph 8, “Communication Systems" and paragraph 9, "Modeling and Simulation” for more detailed information on the model and simulation selection process. Event Testing Process. Event testing plays a key and integral part in all computer-assisted exercises and the planning and database building process. It ensures that the selected simulation model(s) can accurately execute realistic battles, reflect realistic results, and create the "illusions of war" that support the customer's campaign plans and exercise objectives. Part of this process includes not only the validation of database game characteristics, but also the identification of shortfalls requiring programming corrections or work-around procedures if the shortfall cannot be resolved through simulation. Normally, at least three event tests are conducted. JWFC will develop the event test plans, which will ensure that every critical piece is tested, verified, and approved by the supported command. In addition, these event tests provide a foundation upon which controller procedures can be developed to ensure that the simulation functions and interoperability are executed in a manner that is transparent to the training audience. See Enclosure (18), “JWFC Event Testing” for more explicit detail on event testing. JWFC Training Effectiveness Survey Program. In order to better support the Warfighter, the JWFC implemented a survey program to obtain the training customer’s feedback following selected USJFCOM supported training events. The Survey Program is intended for the combatant commands to provide JWFC with feedback that will allow us to take correct action as necessary, improve on those things we could be doing better, and reinforce those things we are doing well. If the JWFC has recommended a particular event for survey participation, this proposal will be addressed during the conferences supporting the JELC and prior to event/exercise execution. c. JELC Stage 3 - Preparation. Completion of the MPC ends the planning stage (Stage 2) and initiates the preparation stage. During Stage 3, the exercise concepts, supporting plans, draft MSEL, and academic training plans are finalized, approved, and published. The exercise milestones are also reviewed and the schedule for any remaining Event Tests is presented and approved. The FPC is convened to confirm completion of all required milestones prior to exercise start (STARTEX) and to distribute the required plans, orders, and relevant doctrine material. Prior to the FPC, the Exercise Control Plan is published, Exercise Functional Test is conducted, development of the MSEL continues (implementers completed), OPFOR CONOPS plan is finalized, joint Exercise Directive is published, and the AAR concept of operations is finalized. Figure V-4 depicts actions during the preparation stage, which results in database decisions and M&S testing.

V-7

*OPFOR CAMPAIGN PLAN*OPFOR CAMPAIGN PLAN FPCFPCFPC


Test #3Test #3& Lock& Lock

DBDBBuildBuild

Test #2Test #2

OPFORCampaign plan

Briefed

Plans DISTRIBUTED

Final Event Review

Event DirectivePUBLISHED

OPFOR CampaignPlan FINALIZED

FPC AgendaPUBLISHED

EventEventControl planControl planDELIVEREDDELIVERED

EventEventControl PlanControl PlanPUBLISHEDPUBLISHED

AARAARObserverObserver

Training BRIEFEDTraining BRIEFED

MSELMSELSyncSync

WorkshopWorkshop

3. PREPARATION STAGE3. PREPARATION STAGE

MSEL DEVELOPMENTMSEL DEVELOPMENT

COLLECTION MANAGEMENT PLAN DEVELOPMENT INITIATEDCOLLECTION MANAGEMENT PLAN DEVELOPMENT INITIATED

MSEL FinalPublished

DocumentsDISTRIBUTED

Tasking MessageReleased

Exercise Synchronization

Drill Draft

*OPFOR CAMPAIGN PLAN*OPFOR CAMPAIGN PLAN FPCFPCFPC


Test #3Test #3& Lock& Lock

DBDBBuildBuild

Test #2Test #2

OPFORCampaign plan

Briefed

Plans DISTRIBUTED

Final Event Review

Event DirectivePUBLISHED

OPFOR CampaignPlan FINALIZED

FPC AgendaPUBLISHED

EventEventControl planControl planDELIVEREDDELIVERED

EventEventControl PlanControl PlanPUBLISHEDPUBLISHED

AARAARObserverObserver

Training BRIEFEDTraining BRIEFED

MSELMSELSyncSync

WorkshopWorkshop

3. PREPARATION STAGE3. PREPARATION STAGE

MSEL DEVELOPMENTMSEL DEVELOPMENT

COLLECTION MANAGEMENT PLAN DEVELOPMENT INITIATEDCOLLECTION MANAGEMENT PLAN DEVELOPMENT INITIATED

MSEL FinalPublished

DocumentsDISTRIBUTED

Tasking MessageReleased

Exercise Synchronization

Drill Draft


Final Planning Conference (FPC). The FPC is conducted approximately three months prior to event STARTEX and lasts about three days. The purpose of the FPC is to provide a last check of the status of planning and preparation for event execution and to finalize, publish, and distribute all key exercise plans and documents. These will include constructs for Joint Exercise Control Group (JECG) training as well as both the communications exercise (COMMEX), and “mini”-exercise (MINIEX). Both the “commex” and “miniex” are conducted prior to startex and are an integral part of the JECG training regimen. In addition a final MSEL synchronization drill will be conducted and preparations for Exercise Operational Test finalized. As the name implies, the FPC is the final opportunity for all concerned to resolve remaining issues and endorse the final planning product. Final Planning Conference Outcomes. Among the products and processes that should be completed and/or validated at the FPC are the following:

• Identification of any post-conference taskers and/or issues to be resolved by higher authority.

• Finalization of FPC wrapup message. • Posting of all exercise documents on appropriate websites. • Completion of MSEL synchronization drill, • Completion of a Force Protection Plan briefing (if required).

i. Approximately sixty days prior to exercise execution, the JWFC Desk Officer will present an update briefing to the Director, J7 on the status of exercise planning and preparation. (See Enclosure (5), “Pre-exercise Executive Briefing Example)

V-8

Academics. The DTT provides command and staff training support to the training audience before, during, and after the exercise. Academic training is based on the requirements of the training audience. A facilitated crisis action planning and time-phased force and deployment data development and deployment exercise can be conducted, if desired by the training audience. During exercise execution, academic training support also may be provided. In addition, the observer/trainers and Doctrine and Education Group analyst(s) working with the training audience may conduct academic seminars and "on-the-spot" training throughout the exercise. Further, assigned Doctrine and Education Group analyst(s) may conduct research and provide joint doctrine updates/briefings to the observer/trainers and other exercise participants as required throughout the exercise. The training audience is provided a list of subject matter experts at the conclusion of the event in case post-event questions arise. d. JELC Stage 4 - Execution. During Stage 4, set up and final preparations are made at the exercise site(s), including Comms and simulation systems setup and checks, JECG training, COMMEX -- where communications are tested within the JECG and with the training audience, and MINI-EX -- the pre-exercise battle rhythm execution to help the JECG and training audience understand game play. The execution stage begins with the deployment of support equipment and personnel to the exercise or event site and ends with the completion of the Formal After Action Review (FAAR) and re-deployment. Following ENDEX, the FAAR is conducted for key members of the training audience. Figure V-5 represents the primary actions that occur in the execution stage, culminating in the execution of the AAR. Pre-Deployment Briefing. This briefing is provided to all JWFC participants and is intended to provide important information concerning their deployment. Topics covered include: overview of event or exercise; event timeline; information about the location where participants will deploy; billeting; rates for per diem and miscellaneous incidentals and expenses; emergency phone numbers; classified material/equipment packup, shipping, storage and redeployment; force protection procedures to follow during deployment; and a threat briefing for the operational area.

V-9

AAR EXECUTED

JECGJECGTrainingTraining

EXECUTEDEXECUTED

AARAARObserver Observer TngTngEXECUTEDEXECUTED

COMEX COMEX EXECUTEDEXECUTED

DTTDTTTrainingTraining

EXECUTEDEXECUTED

Exercise Synch Drill

CMPCMPDeliveredDelivered

JAARJAARProcessProcess

CAMPAIGN EXECUTIONCAMPAIGN EXECUTION

MSEL EXECUTIONMSEL EXECUTION

COLLECTION MANAGEMENT EXECUTIONCOLLECTION MANAGEMENT EXECUTION

EventEX

EventEventEXEX

4. EXECUTION STAGE4. EXECUTION STAGE

SynchWargame

COP Conference

Phase IIOPORD

Development

Phase IIOPORD

Development

Phase IAcademic

AAR EXECUTED

JECGJECGTrainingTraining

EXECUTEDEXECUTED

AARAARObserver Observer TngTngEXECUTEDEXECUTED

COMEX COMEX EXECUTEDEXECUTED

DTTDTTTrainingTraining

EXECUTEDEXECUTED

Exercise Synch Drill

CMPCMPDeliveredDelivered

JAARJAARProcessProcess

CAMPAIGN EXECUTIONCAMPAIGN EXECUTION

MSEL EXECUTIONMSEL EXECUTION

COLLECTION MANAGEMENT EXECUTIONCOLLECTION MANAGEMENT EXECUTION

EventEX

EventEventEXEX

4. EXECUTION STAGE4. EXECUTION STAGE

SynchWargame

COP Conference

Phase IIOPORD

Development

Phase IIOPORD

Development

Phase IAcademic


Joint Exercise Control Group. The JECG is the "central nervous system" for control of the exercise. It regulates the flow of information among the training audience, observers and controllers, senior mentors, models and simulations, C4I systems, response cells, support cells, AAR observers, and the OPFOR/SITFOR. JWFC provides contractor personnel to operate the simulation, to assist the military and serve as role players in response cells, to assist the military MSEL manager, to be the OPFOR/SITFOR, to assist in control of overall exercise coordination, and to provide pre-exercise training for JECG response cell participants. Exercise specific information about JECG structure, methods, and responsibilities are detailed in the Exercise Control Plan. The draft Exercise Control Plan is a JWFC deliverable to the supported command at the MPC. See Enclosure (13), “JECG Operating Procedures” for more details. Facilitated After Action Review (FAAR) Process. The JWFC DTT provides the event FAAR. The FAAR is an extension of the training environment and is linked to the JMETs, TOs, the commander's major focus areas, and the operational phase of the exercise. It includes a discussion of key operational or strategic issues, significant lessons learned, and/or accomplishments. JWFC senior mentors, retired flag officers, can provide consultation for the combatant and JTF commanders during an exercise. The

V-10

decision concerning the employment of a senior mentor(s) in support of an exercise should be made during the planning process. e. JELC Stage 5 - Analysis, Evaluation, and Reports. This stage begins after the DTT has conducted the FAAR. DTT produces a commander's summary report (CSR) for the commander of the training audience.

5. ANALYSIS, EVALUATION & REPORTS5. ANALYSIS, EVALUATION & REPORTS

InternalInternalReviewReview

CDCCDCCDC

TO JTS PHASE IV

Joint AfterAction Report EXERCISE

REPORT(S) and/orEVALUATIONS

PRODUCED

Internal ProcessImprovement

Data, Information, Knowledge

EXERCISEREPORT(S) and/ or

EVALUATIONSDELIVERED

Observations,Issues, Lessons

Learned

5. ANALYSIS, EVALUATION & REPORTS5. ANALYSIS, EVALUATION & REPORTS

InternalInternalReviewReview

CDCCDCCDC

TO JTS PHASE IV

Joint AfterAction Report EXERCISE

REPORT(S) and/orEVALUATIONS

PRODUCED

Internal ProcessImprovement

Data, Information, Knowledge

EXERCISEREPORT(S) and/ or

EVALUATIONSDELIVERED

Observations,Issues, Lessons

Learned


Commander's Summary Report. The CSR is delivered to the supported command by the

JWFC Desk Officer, normally ten working days after event completion. Delivery can be accelerated to two days if required by the training audience. A CSR usually contains the following sections:

1. Table of Contents 2. Introduction 3. Exercise Intent and JMET 4. Commander’s Issues (summary of key issues discussed at the FAAR, plus copies of the

briefing slides) 5. Observations and Analysis of Exercise JMET and TO. (observations and analysis of the

JMET(s) and TO(s) 6. Points of Contact Collection Management Plan. The CMP delineates the responsibilities and procedures for the collection and analysis of information for the training exercise. The CMP is provided to the DTT ten working days before event execution. Abbreviations and Acronyms. In addition to the CMP, abbreviations and acronyms used in any of the JWFC products are defined and placed in one document and provided to the supported commander when the CSR is delivered.

V-11

Joint Doctrine Issues and Voids. Doctrine and Education Group analysts will initiate appropriate action to resolve joint doctrine issues and voids identified during this stage.

Internal After Action Report (IAAR). Within 30 days of completion (ENDEX) of each exercise (or other training event) the JEST Lead, in concert with the Desk Officer, will conduct an Internal After Action Review (IAAR). The intent of the IAAR is to provide a forum for conducting a thorough, candid examination (involving both government and contractor personnel) of the subject training event from a design, planning, preparation and execution (DPP&E) perspective. The ultimate goals are to capture efforts that went well (“sustains”) as well as to identify areas that require remedial action. The primary product of the IAAR is a list of significant concerns or “issues” (complete with description, action office assignment and due date) for follow-up action and eventual resolution. 4. Summary The JELC is a process consisting of discrete conferences, products, and milestones that, when implemented, allows the JWFC to plan, coordinate, and execute multiple joint training events or exercises. It also enables the JWFC Desk Officers to schedule, deconflict, and establish tentative dates to execute the multitude of tasks required to execute complex events and exercises. The JELC consists of five stages: design, planning, preparation, execution, and evaluation. The outputs of each stage are the inputs for the following stage. Although described as a series of discrete events, in reality, the JELC is a continuous process and the boundaries between stages may become indistinguishable. Lastly, the JELC is unique because it also provides sufficient flexibility for JWFC Desk Officers and other planners to modify the process as needed to meet specific training event or exercise requirements, to include adapting the process to support the demanding challenges of a complex joint experiment.

V-12

Intentionally Blank

VI-1

Chapter VI: JOINT WARFIGHTING CENTER EVENT SUPPORT 1. Introduction a. The purpose of this chapter is to describe the various types of capabilities that are available to use in support of event programs. Specific levels of support are determined on priorities established by the combatant commands and the Joint Staff, actual requirements for these events, the availability of JWFC resources and funding, and real world commitments. Support is identified and schedules are de-conflicted at the annual Office of the Secretary of Defense (OSD) and Joint Staff sponsored, USJFCOM hosted Worldwide Joint Training and Scheduling Conference (WJTSC) held twice a year (normally September and February). b. The Combatant Commanders’ Exercise Engagement (CE2) program, managed by the Joint Staff J7, provides the necessary funding to support the Chairman’s, Joint Chiefs of Staffs (CJCS) sponsored joint training program. The JWFC is typically funded and resourced to support two combatant command events and one Joint Staff event annually. Depending on the size, location, and complexity of the event, support beyond this level must be negotiated through the supported combatant command and joint staff. c. When support is requested and resources are available, the JWFC support may include: joint mission-essential task; event planning; scenario development; opposing force (OPFOR) planning and role playing; intelligence planning support; exercise sustainment planning and role playing support; interagency planning and role playing support; multi-national planning and role playing; information operations planning and role playing support; academic training; observation, training, and analysis; modeling and simulation (M&S) support; communications systems (CS) architecture design and setup; and exercise manning requirements assistance. With limited exceptions JWFC is responsible for deployment, sustainment and redeployment of its personnel. d. The supported training audience participates in all exercise planning and design efforts in order to determine what resident combatant command support will be necessary for event execution. The level of support in each particular area will depend on the requirements, construct, and objectives of the event. The following paragraphs described in detail JWFC support options and resources. 2. Scenario-MSEL Support a. Scenario Development

(1) The exercise scenario describes strategic and operational environment in sufficient scope and detail to allow accomplishment of the exercise and training objectives.

(2) The JWFC Scenario-MSEL Section is the focal point for coordinating all environmental inputs to ensure a single, realistic, plausible, and coherent environment. Scenario-MSEL is responsible for creating or managing the creation of a Road to Crisis (RTC), an Operational Environment Overview, Ground Truth Documents, start of exercise (STARTEX) situation, the storylines (or threads), and Master Scenario Event List (MSEL) injects. Environmental inputs may also include an Intelligence Summary (INTSUM), a Threat Campaign Plan, one or more simulations, an Information Operations Study, situation reports (SITREPs) from U.S. Embassies and international or non-governmental organizations (IO/NGO), United Nations Security Council Resolutions (UNSCRs), etc.

(3) See Enclosure (10), “Scenario Development,” for a step-by-step discussion of scenario building.

b. Master Scenario Event List (MSEL) Development

VI-2

(1) Overview. A MSEL is a chronological list of occurrences that are injected into an exercise via the command and control systems, such as e-mail, telephone, and the Global Command and Control System, used by a training audience. The intent is to create a series of realistic situations requiring the training audience to practice tasks drawn from their Joint Mission Essential Task List (JMETL). The Joint Master Scenario Event List (JMSEL) is an automated system for MSEL management.

(2) JMSEL provides a Web-based interface for exercise design and planning, document development, management, and tasking. JMSEL is designed to support geographically dispersed organizations and a wide variety of functional areas in a collaborative, data-sharing environment. JMSEL supports both subject matter expert (SME) users and MSEL Managers. See Enclosure (11), “Master Scenario Event List (MSEL) Development,” for a step-by-step discussion of MSEL building. 3. Opposing Force / Situational Forces a. This section covers the manning, duties and responsibilities, processes and procedures, and information flow for use during joint events to include interaction with other joint or combined Exercise Control Group (ECG) cells. Enclosure (12), “OPFOR/Response Cell” provides details regarding the opposing and situational forces application and integration. b. Mission Statement. The Joint Warfighting Center (JWFC) Forces Branch provides a robust and realistic opponent that supports joint event training objectives. Specifically, the OPFOR/SITFOR cell portrays the traditional military, paramilitary, irregular military, insurgents, terrorists, or any other type of organizations representing opposing forces (OPFOR) or situational forces (SITFOR) as required by the scenario in the simulation. Secondary Missions: OPFOR/SITFOR cell portrays the simulation of commercial shipping and air assets normally operating in the AOI in support of the scenario. To this stage, the OPFOR/SITFOR cell will:

(1) Prepare and implement “the threat” for the training audience following the OPFOR Campaign Plan (approved by the Event Director or his designated representative).

(2) Ensure all OPFOR Campaign Plan activities support the master scenario events list (MSEL) as well as provide dynamic events as coordinated and approved by Senior Control. 4. Joint Exercise Control Group (JECG). The JECG is responsible for managing and directing the execution phase of all exercises. It consists of subject matter experts from all functional areas. The JECG manages MSEL injects, provides role playing actions, and controls the flow of the exercise to ensure exercise and training objectives are met. The JECG is responsible for all dynamic scripting. See Enclosure (13),”JECG Operating Procedure.” 5. Doctrine and Education Support to Joint Training a. Introduction. The Doctrine and Education Group (DEG) fulfills CJCS guidance with regard to training as stated in CJCSI 3500.01E and CJCSM 3500.03B. The DEG provides a unique capability for training support to joint, Service and multinational training events. The DEG routinely supports the Chairman’s joint training program, mission rehearsals, regional security cooperation training. The DEG also leverages joint training events to collect observations that inform joint doctrine development, assessment, and revision; the DOTMLPF change process; and ensures that joint doctrine is relevant and supports the joint warfighter in the current operational environment. b. The JWFC Training Event Support. The DEG joint doctrine subject matter experts (SMEs) are available to support Desk Officers, Event Planners, and analysts throughout the joint events life cycle (JELC). The DEG’s joint doctrine SMEs are routinely assigned to support DTT O/Ts, AAR analysts, and the training audience. They participate in all pre-event training and deploy with the DTT for event

VI-3

execution worldwide. During pre-event preparation, DEG’s SMEs provide doctrine research and analysis capability to ensure that doctrine topics and terminology are addressed appropriately. During event execution, DEG’s joint doctrine SMEs work with O/Ts and AAR analysts by providing doctrine research that supports the coaching/mentoring effort. Also, joint doctrine support is provided to the training audience as needed; for example, through identification of doctrine resources for internal staff training. DEG’s SMEs assist in the production of the Commander’s Summary Report (CSR) by reviewing the text for doctrinal accuracy and providing editing support. Additionally, DEG’s SMEs gain valuable insights by collecting observations and identifying gaps and seams that can be applied to the JFCOM doctrine development and revision effort. 6. Intelligence Support to Joint Training a. JWFC Intelligence Branch provides varying levels of planning and execution support throughout the Joint Event Life Cycle (JELC) process. To do this, USJFCOM establishes an intelligence planning team, to include military, civilian and contractor planners and supporting functional representatives. The Military Intelligence Lead Planner acts as the conduit between the training audience(s) intelligence planners and the JWFC. The major areas of support in the planning process includes: lead planning, intelligence production, manning, training, intelligence models and simulations, intelligence CS, targeting, and collections. The general sequence of these events is contained in Enclosure (14), “Exercise Intelligence Planning Guide” to this Handbook. The necessity for individual products varies with each exercise, and is determined under the guidance of the Lead Intelligence Planner. b. The Mission Rehearsal Exercises (MRX), in addition to the Unified Endeavor (UE) program has increased the intelligence support demands upon the JWFC Intelligence Team. In supporting joint training events, the use of time separated phases for differing units have added three to six full exercise planning evolutions, in differing areas, under a single exercise name. The additional evolutions increases demands for systems knowledge and intelligence discipline practices beyond those encountered in previously conducted JWFC exercises. MRX events differ from UE exercise in that JWFC intelligence is in direct support to the US Army’s Battlefield Combat Training Program (BCTP) vise JFCOM. MRX are focused on a lower echelon command (i.e. BCT) than UE program. c. Lead Intelligence Planner. JWFC intelligence support includes a government Lead Intelligence Planner, a lead planner from the JST (contractor) who coordinates between the Desk Officers and members of the exercise planning team (operations, CS, M&S, OPFOR, Sustainment), and the training audience's intelligence planners. Lead Planners facilitate the Intelligence Working Groups during the different planning conferences, as well as other intelligence-specific planning activities during the JELC. The Lead Planner is responsible for promulgating the Intelligence Plan of Action and Milestones (PAO&M). d. Intelligence Production. Intelligence products are developed for each exercise simulating the output of national agencies, subordinate, peer, and higher echelon of commands. These products are focused on replicating the intelligence environment encountered at the operational and strategic levels of war. e. Manning. The Intelligence Planner works closely with all functional event support members, and is responsible for the drafting and coordination of the Consolidated Exercise Support Request (CESR), and for populating the Joint Exercise Control Group (JECG)intelligence billets in the Joint Event Management Information System (JEMIS). f. Training. The Intelligence Planner is responsible for identifying training shortfalls within the Intelligence Support Cell. For MRX and UE events, the lead planner is also responsible for coordinating with the JFCOM Joint Forces Intelligence School (JFIS) for development of a unit specific tailored training plan for the designated training audience. This plan incorporates both computer based training and onsite instruction.

VI-4

g. Intelligence Model and Simulations. JWFC Intelligence will assign a lead intelligence M&S planner to support the Lead Planner in selecting, designing, and implementing a simulated environment for event execution. h. Intelligence CS. To exercise the way we fight, JWFC maximizes the use of existing intelligence architecture and CS systems. JWFC replicates baseline joint intelligence systems and maximizes use of real-world sensors, databases, techniques, and procedures. The JWFC adapts its intelligence architecture to the training audience's documented baseline systems and communications paths.

(1) Exercise Planning (a) Due to the complexity and classification of Intelligence training operations, 1 to 2 intelligence working groups (IWG) are scheduled for each event. IWGs are normally held in conjunction with MSEL scripting conferences and have similar goals. Additionally, and Intelligence cut off date is established. This is the last date that real-world information may be considered for use by the training audience. (b) Model selection is based on training objectives and scenario. M&S systems requirements must be determined early in the planning cycle to allow for database development. (c) Training Objectives (TO) are developed in conjunction with training audience intelligence leadership.

(2) CS Architecture. Modeling and Simulations personnel define and integrate real world and simulation communications architectures to communicate among multiple models at various locations to ensure that reports flow during execution. To the extent possible, the training audience should bring its real world CS systems to Event Test 2 and 3 for integration and identification of possible problem areas. Incompatible message handling instructions and internal message routing problems should be identified for correction at these tests, or for development of work around processes which will be invisible to the Training Audience.

(3) Exercise Preparation Stage

(4) Event Execution Stage. At the beginning of event execution, a mini-exercise will be

conducted to insure full CS connectivity with the training audience.

(5) After Action Reporting (AAR inputs are provided by all Intel sections immediately following exercise execution. AAR input consists of both problems needing further refinement and/or practices which have been found to be particularly good. JWFC may provide AAR comments concerning the training audience to the JWFC Deployable Training Team but not directly to the training audience. The Lead Intelligence Planner will develop an internal AAR focused on exercise planning and execution, to be briefed to the JWFC Senior Intelligence Officer. The intelligence lead planner, in cooperation with their JST counterpart, will archive all planning, execution, and AAR data for future reference. 7. Exercise Sustainment Planning Support a. Sustainment training encompasses logistics and personnel services necessary to maintain and prolong operations until mission accomplishment. JWFC Sustainment Planners facilitate training in the following functional areas: supply support, maintenance, transportation, human resources support, religious ministry support, financial management, legal support, health service support (HHS), explosive ordnance disposal (non IED), field services and general engineering. The level and fidelity of sustainment play is dependent upon exercise objectives, training objectives and availability of required resources. b. External Sustainment Agencies. Sustainment exercise play can be enhanced with the participation of external agencies and commands such as the U. S. Transportation Command, Defense Logistics

VI-5

Agency, and Army Sustainment Command. As mentioned above, the JWFC can help identify requirements and coordinate this participation. For additional details, see Enclosure (15), “Sustainment.” 8. Communication Systems a. Exercise CS Planners are responsible for integration of the control network into the overall exercise architecture. They analyze joint and service exercise objectives, operational command and control systems and processes, and integrate exercise simulation architectures into exercise CS architectures. CS Planners assist joint service or coalition training audience J-6 planners with planning and accessing the CS requirements to support the execution of joint training exercises. CS Planners analyze C2 Systems architectures, bandwidth requirements, and power requirements. During exercises, they provide management oversight of the military, contractor, and government matrixed team that establishes and provides reliable C2 Systems to the JWFC/J7 training staff and joint service or coalition organization in training, both in-garrison and deployed to austere environments. b. Services and Capabilities. The Joint Exercise Support Branch (JESB) has developed a Standing Operating Procedures (SOP) document to establish key duties and responsibilities for the CS Planner. The SOP is available through the JES Branch Chief and provides guidance for CS planners to design and execute tailored M&S and CS architectures and support plans for joint and coalition training exercises. Absent the SOP, Enclosure (16), “Joint Exercise Support Branch Support” provides an abbreviated familiarization of the services and capabilities the CS planner coordinates in support of training events. Formats for the specific documents identified will be provided by the CS planner. Desk Officers and other members of the planning team can request additional information from the CS planner. 9. Modeling and Simulation a. JWFC supported events are supported with modeling & simulation (M&S) tools and technical oversight. The use of modeling & simulation is planned and executed by a designated JWFC event M&S planning team. The M&S event planning team is comprised of a lead government M&S Planner from the Joint Support Division, intelligence M&S planner, and the following contractor specialists: Technical Coordinator, CS Integrator, federation manager, model operators, database developers and instructor /controllers. Event requirements will come from the desk officer, lead event planner and functional planners. b. Joint Training Tool Kit. The Joint Training Tool Kit is the suite of tools JWFC uses to conduct joint training for combatant commands and Service JNTC programs. This suite of tools is part of the Training Transformation (T2) effort. JWFC develops two M&S federations within the Joint Tool Kit. These federations are the Joint Live, Virtual, Constructive (JLVC) and Joint Multi-Resolution Model (JMRM). More information on both federations is available in Enclosure (17), “Joint Training Tool Kit.” c. In preparation for JWFC exercises, the technical aspects supporting the exercise require verification to ensure that the systems will provide the training audience with the stimulation required to meet training objectives. While every exercise is different, most will fall into the following model of; data development, functionality testing, and operational testing, this model is not a requirement for execution of the exercise. Differences in exercise size and scope, as well as simulation selection will dictate exactly what is required. The lead Modeling and Simulation Planner will make the final determination of what pre-exercise testing is required to ensure a successful exercise. In support of this effort, the Modeling and Simulation Planner provides technical oversight and conducts associated event tests (see Enclosure (18), “JWFC Event Testing.”) 10. Observation, Training, and Analysis Support a. Academic Training Phase

VI-6

(1) The Operations Group's Joint Training Division (JTD) is responsible for the development of the academic training plan. The purpose of this plan is to identify and describe the overall content of the scheduled academic portions of a particular combatant commander or JTF joint event or exercise. It will be developed for each exercise/event containing a JTD supported academic training component. The plan initially starts as an academic training "concept." The "concept" is presented and approved at the initial planning conference. It then evolves into an academic training "plan," which is presented for review and approval at the mid-planning conference. Considerations in developing the content of the plan include:

(a) Joint mission-essential tasks (b) Exercise/training objectives (c) Exercise mission and scenario (d) Major focus areas (e) Commander's guidance and commander's critical information requirements (f) Observations from previous exercises

(2) JTD will provide senior mentor, O/Ts, and after-action review (AAR) analyst support

required to complete academic training. (3) The term "academic" refers to all knowledge-based instructional opportunities and events

preceding the practical application (operation order planning and/or execution) portions of an exercise. There also may be an event that is strictly "academic," with no follow-on application/execution. The current categories of training available are:

(a) Seminars: doctrinal centric presentations/discussions conducted or facilitated by

observer/ trainers for the commander and primary staff in plenary sessions tailored to meet the training objectives of a particular exercise.

(b) Functional Training: more focused learning by individual J-codes, staff sections, and

various boards/centers/cells in both formal and informal settings. (c) Senior Leader Seminars: seminars aimed at providing the commander’s flag and

general officers and other designated personnel the opportunity to study and discuss what the commander considers to be key issues, as they relate to a particular exercise or command issue.

(d) Crisis Action Planning Workshop: a series of functional-level sessions during which

the training audience works through the crisis action planning/operational planning process, developing appropriate staff section estimates. b. Planning, Operational Rehearsal, and Execution Phases

(1) During a supported exercise or event a task organized Deployable Training Team (DTT) composed of a senior mentor, O/Ts, AAR analysts, doctrine representatives, and technical support specialists support the particular activity. The goal of this tailored team is to enable the training audience to achieve their exercise and training objectives. This is accomplished by providing feedback through daily contact and functional AARs, facilitated after-action reviews (FAARs), and a single commander's summary report (CSR) given to the combatant commander or designated subordinate commander. As a rule, the JWFC will fund for one senior mentor per exercise. Combatant commanders and/or JTF commanders requesting senior mentor support beyond this must request the additional support in writing and be prepared to fully fund their request.

VI-7

(2) The following products may be provided:

(a) Functional After-Action Review. Conducted by O/Ts assigned to cover specific staff areas, the functional AARs provide the individual staff sections a forum for self-discovery and a means to capture areas for sustainment and improvement.

(b) Facilitated After-Action Review. The DTT provides a qualified JWFC facilitator to

conduct the FAAR. This is conducted at the conclusion of the exercise at a time and place determined by the supported commander.

(c) Commander's Summary Report. As previously determined during the planning cycle, the DTT provides one CSR to the primary training audience's commander. The CSR will be completed and provided to the commander generally within 10 working days of event completion. An accelerated 48 Hour CSR is available upon request if it is needed to support the commander’s post-exercise assessment program. 11. Synthetic Media Support a. WNN provides Joint Force Commanders, staffs, component staffs, and other event participants with relevant information pertaining to the operational environment and scenario in the form of real-time synthetic television, print, and radio media. WNN products facilitate training in public communications, perception management, information management, open source intelligence collection, and strategic communication. These products include:

(1) Road-to-Crisis (RTC) Videos. The RTC Video is a scene-setter newscast that sets the stage for an exercise, STAFFEX, vignette, or experiment. Typically presented at the start of an event, the RTC Video explains the history of a conflict or crisis and provides information relating to the military, political, and humanitarian challenges of a military mission.

(2) World News Network (WNN) Broadcasts. The WNN newscast provides current scenario-

related information and a reflection of public support for a military operation. WNN broadcasts are also a tool for exercise controllers to stimulate a reaction or change in training audience performance.

(3) WNN Special Reports. The WNN special report is a short newscast that provides pertinent

scenario information that must be injected quickly or at a specific time during an exercise. (4) Adversarial and Regional News. Adversarial and regional (atypical) newscasts provide

information from the perspective of an adversary, geographic region, ethnic group, or other social influence on military operations. Atypical newscasts are most commonly created through the fictitious news organization Arab News Network (ANN) in support of training events and mission rehearsals for operations in Iraq. ANN and atypical newscasts can only be provided when production does not interfere with other exercise requirements.

(5) Print News Stories. Print news stories provide exercise controllers with an alternative to

WNN video products for injecting MSEL events and scenario information. Print news may also provide commentary on mission activities to replicate the presence and impact of the media during military operations. Reservists assigned to the Joint Public Affairs Support Element (JPASE) or other Reserve Component organizations create print news under the supervision of the Public Affairs Lead and Media Coordinator.

(6) World News Radio. World News Radio provides an additional medium for simulated news,

editorials, and interviews. Radio broadcasts are not a standard WNN product and are created on a non-interference basis at the discretion of the exercise Media Coordinator.

VI-8

(7) Press Role Players. Media role players may be provided for simulated press events and interviews. JPASE Reservists and other JECG members typically perform that role as secondary duties. Media role players write print news stories and broadcast scripts in addition to other responsibilities as defined by the Public Affairs Lead and Media Coordinator.

(8) Media Training. The Media Branch may assist JPASE and supported commands in

providing tailored media training to commanders, public affairs officers, and other joint staff members. A combination of academics and in-studio practical exercises, tailored for mission requirements, challenge individuals and groups to prepare messages and practice interview skills in a variety of settings and under varying degrees of pressure. Because of the increased preparation time required for media training, requirements should be discussed and agreed on at initial planning conferences. b. The tone and content of simulated media are driven by training and exercise requirements. The level of media support and selection of products are based on several factors including: type of event, training objectives, simulations, communications architecture, workspace, availability of Reserve augmentees, and public affairs training requirements. 12. Joint Knowledge Development and Distribution Capability (JKDDC). JKDDC is the Department of Defense program to transform individual joint training in order to improve warfighter performance and readiness for integrated operations. Joint Knowledge Online (JKO), an enterprise portal system, is the tool JKDDC uses to provide convenient access to online joint training and information resources. Integrated with other DoD systems, JKO employs the latest advanced distributed learning technologies to provide training courses and resources that better prepare warfighters for joint exercises and integrated operations. Enclosure (19), “JKDDC Support to Joint Training” provides the details for using these online services for joint training. 13. Joint Experimentation, Test and Evaluation, and Advanced Concept Technology Demonstration (JETA) Integration into Joint Training. a. The United States Joint Forces Command (USJFCOM) Joint Experimentation, Test and Evaluation, and Advanced Concept Technology Demonstration (JETA) Integration into Joint Training Manual, USJFCOM 1025.1-M, outlines the procedures for integrating emerging joint warfighting capabilities into joint training events. b. The primary purpose of JETA integration is to examine potential solutions to warfighting deficiencies and assist with presenting validated solutions to the Joint Staff. The JETA Integration Process facilitates the integration of capability initiatives into joint exercises for test and validation consistent with accomplishing required training in support of USJFCOM’s joint training and transformation responsibilities. c. It is USJFCOM policy to closely liaison and coordinate with leadership of agencies and entities involved in development of new or improved warfighting initiatives, including Joint Tests and Evaluation, Joint Capabilities Technical Demonstrations (JCTDs), and joint and Service experimentation and prototyping. d. The JETA Integration Process is designed to integrate initiatives into joint training events which USJFCOM sponsors or supports. The intent is to have a JETA participate in a training event and be able to maximize exercise opportunities in order to collect data requirements from testing, evaluating, and validating initiatives with minimum disruption to the training audience. Early planning by entering the Joint Event Life Cycle ideally at the Initial Planning Conference (IPC) provides for a greater likelihood of success experienced by all parties. e. Capabilities Improvement Sponsors begin the process with the completion and presentation of a JETA questionnaire and CONOPS to the Joint Training Development Group (JTDG) representatives as a

VI-9

nomination for integration of their JETA into a joint Training event. Document formats are at Appendixes 2 and 3, JETA Integration Process Manual, USJFCOM 1025.1-M. The JTDG representative will coordinate through the Joint Training Operations Group desk officer/exercise planner for the best fit training event which USJFCOM either sponsors or supports. The intent is to secure an invitation for the JETA to participate in the planning process through both attendance at the planning conferences and the conduct of detailed coordination with the exercise - sponsor command’s planning staff for eventual approval to participate in exercise execution. The specific responsibilities for the various representatives at each planning conference are reflected in the checklists in Appendix 1, JETA Integration Process Manual, USJFCOM 1025.1-M. During planning conferences, the possible impact of JETA/s on the training audience will be discussed. Each JETA must explain how it will execute its test requirements (emphasis on minimal disruption to the training audience), and how it will train specific participants within the training audience to execute actions/procedures so that the JETA can obtain requisite data. Formal approval of integration into exercise execution is normally announced by the end of the Mid Planning Conference (MPC). IMPORTANT NOTE: JETAs are NOT funded under programmed/budgeted joint exercise resources. The JETA sponsor is expected to plan for and resource all aspects of their participation/integration into the joint training program. All requirements beyond those agreed to by the exercise director -- equipment, personnel, and other special requirements -- will be the responsibility of the JETA sponsor. The participating JETA sponsor can expect a “fair share” exercise expense requirement to integrate the JETA into the exercise (connectivity, special facilities, additional cost that the JETA brings to the conduct of the exercise, etc.). The JETA’s financial consideration is covered in the JETA questionnaire and will be addressed in detail during initial meetings with the JTDB. 14. Information Operations (IO) Joint Management Office. As the lead agent for joint force training, USJFCOM is responsible for supporting the combatant commanders, Services, Combat Service Agencies and National Guard Bureau in their implementation of the Chairman’s joint training policy and guidance and execution of their training programs. Additionally, USJFCOM provides joint training for and/or assistance with the joint training of combatant commander battle staffs, JTF HQ staffs and JTF functional component commanders and their staffs and headquarters designated as potential joint headquarters. Enclosure (20), “IO Support to Joint Training” provides specific supporting details. 15. Joint Training Service Support a. The JWFC Event Service Support function provides central logistical support to JWFC sponsored participants at JWFC or combatant command exercise locations. b. Perform site surveys to determine the following essential logistical requirements. c. Provide JWFC Equipment Support by packing and shipping necessary exercise equipment. d. Provide JWFC Personnel Support by arranging travel and lodging for personnel supporting exercises at a deployed location.

e. Schedule in-processing day, time and location. Including all life support items necessary for the exercise. f. Additional JWFC services information is contained at the following Enclosures:

(1) Enclosure (21) “Service Support” (2) Enclosure (22) “Security”

VI-10

(3) Enclosure (23) “Visitors Bureau” (4) Enclosure (24) “JWFC Floor Plan” (5) Enclosure (25) “Public Affairs” (6) Enclosure (26) “Manning Requirements”

16. Desk Officer Event Checklists. As the primary government representative assigned in support of a geographical combatant commands event program, the JWFC Desk Officer represents the JWFC Commander in all matters related to the JWFC Event Program. The Desk Officer ensures that the Joint Event Life Cycle (JELC) is implemented in accordance with the JTS, and represents the interest of combatant commands within the JWFC; e.g., support JNTC Accreditation and Mitigation enabling Service and combatant command training programs. Each Desk Officer is authorized to coordinate independently with his/her assigned combatant command in order to allow full integration into that commands exercise program. To assist the Desk Officer, Enclosure (27), “Desk Officer (JELC) Checklist” provides a guide for ensuring that key elements are accomplished within the JELC. 17. JWFC Training Effectiveness Survey Program. The Joint Warfighting Center (JWFC) wants to ensure that the “Center’s” exercise support is meeting the requirements and expectations of the combatant Commander. To help the JWFC determine and assess the conduct of an exercise, event sponsoring commands are asked to complete a survey that evaluates the level of effort and provide the JWFC immediate post-exercise feedback. The JWFC is committed to providing individual and collective joint training that is current, tailored, and responsive to mission needs. In order for the JWFC to continue to meet customer training requirements as their operational environment evolves, we depend on an assessment of our support after each event/exercise. Operations Group, JWFC directs the JWFC Desk Officer/Event Planner to provide an event’s sponsoring organization with a survey during the exercise JELC. The survey is provided well ahead of an event’s execution in order for participating command personnel to digest its content well in advance to completing and returning to the JFCOM Desk Officer/Event Planner at the conclusion of the exercise. The JWFC exercise leads are directed to conduct a personal interview with the individual completing the survey in order to fully comprehend survey inputs. The JWFC Desk Officer/Event Planner will provide the survey results to the Chief, Operations Group. The intent of the JWFC survey program is to provide an opportunity to assess the way we conduct our exercise program. Combatant command survey participation provides the JWFC with an “outside” perspective that better helps improve services ensuring that the warfighter receives the best training available.

ENC (1)-1 Enclosure (1)

Enclosure (1): JWFC Organization Chart


Intentionally Blank


Enclosure (2): Joint Training Plan Tab Descriptions

Tab A: This Tab consists of the commander’s training guidance. It is a concise narrative describing the focus and objectives of the command’s training plan. It outlines the plan for training the individuals, staffs and components to execute assigned missions and assessing the results in order to attain and maintain a high state of joint readiness. Tab B: To provide a correlation between each command mission and their associated tasks that will lead to mission success and to identify relationships with subordinate commands and other commands and/or agencies through the identification of supporting and command-linked tasks. Tab C: To identify the list of mission essential tasks that the commander considers essential to accomplish assigned missions. These tasks are reported on in the Defense Readiness Reporting System (DRRS) via the Joint Combat Capabilities Assessment (JCCA). The JMETL includes the essential tasks, responsible organization, conditions, and standards. All supporting and command-linked tasks are listed under the appropriate JMET. Tab D: This Tab depicts the commander’s Training Assessment of each Task based on completion of Phase IV (Assessment) during the last training cycle. The results of this assessment, in conjunction with the commander’s training guidance, are used to determine training requirements for the upcoming training cycle. Tab E: This tab associates training objectives with JMETs and the training methods. This is a tool for command personnel and organizations that support the command training efforts. Specific training objectives, derived from the JMET, are identified for each training audience. A training objective is a statement that describes the desired outcome of a training activity. It consists of a training audience, performance statement (tied to a specific JMET), training situation, and level of performance required. The complete list of training objectives, training audience, and method defines the combatant command’s training requirements. Tab F: This tab provides event data that becomes the input to the CJCS JTMS. The command joint training event schedule is refined and updated each year during the command’s Exercise and Training Scheduling Conference. The commanders’ refined, updated schedules are published in JTIMS and become the foundation for deconfliction at the Worldwide Joint Training and Scheduling conference (WJTSC) normally held each February and September. Tab G: This tab presents the time line to be used as a deconfliction tool within the command and at the annual WJTSC. The event time is the final tie-in that will show who is involved in training events and show OPTEMPO and/or PERSTEMPO conflicts with training. It can also be used to show the chronological building of training events that culminate in a major or high visibility training event. Tab H: This tab provides guidance to subordinate commanders on mission support required to ensure component and unit training programs are developed to support combatant command mission capability requirements. This tab provides a listing of the commander’s high interest training requirements that require joint resources and training focus from joint force providers to achieve desired readiness to support combatant command mission capability requirements.


Intentionally Blank

Enclosure (3)

ENC (3)-1

Enclosure (3): Joint Training Information Management System (JTIMS)

This enclosure has been developed to assist JWFC personnel with the use of the Joint Training Information Management System (JTIMS). The enclosure will address the management aspects of using JTIMS to support the application of the Joint Training System (JTS) (Figure III-1). It has been designed to assist the users of JTIMS, in obtaining information about how to get on-line and begin utilizing the system. It identifies and defines the rolls and responsibilities for use of the JTIMS by JWFC personnel so they will be able to meet the Joint Staff’s and Combatant Commander’s requirements as the lead agent for joint training.

Appendix A - Introduction and Administrative Information

Appendix B - Rolls and Responsibilities

Appendix C – Training

Enclosure (3)

ENC (3)-2

Intentionally Blank

Enclosure (3)

Appendix A

ENC (3)-A-1

Appendix A: Introduction and Administrative Information

Introduction JTIMS is a secure web-based [SIPRNET] suite of applications with a central database designed to support all phases of the JTS (Chapter III, Figure III-1). The use of JTIMS will provide a clearly definable thread linking mission requirements to unit training, and training resources needed to prepare the training audience for military operations. Design The system is designed to assist the joint training community in identifying requirements, creating joint training plans, executing those plans and assessing training proficiency. The JTS design is “data rich”, meaning simply that there is a large amount of data required to fully execute the system. JTIMS provides an integrated database made available to multiple users and applicable to the systematic administration and management of each phase of the JTS. While developed primarily for use by the joint training community, JTIMS will provide valuable training data to a growing number of “other” users (JWFC Training Development Group, JWCA, etc.). The JTIMS consists of “Published” and “Unpublished” event/exercise data. Published data can be viewed by all personnel that have access to the SIPRNET by going to the JTIMS Login page at http://jtims.js.smil.mil/jtims/welcome.do and clicking on “Select Organization Type” in the Public View section. Unpublished Data is “Restricted Data”. Restricted access provides authorized users with access to information and capabilities based upon user role permissions and assigned user group(s). To access the restricted areas of the system through the “Restricted Login” section of the JTIMS Login page, you must have an approved JTIMS ID. JTIMS Access To attain a JTIMS Login Identification: Go to the JTIMS Login Page at http://jtims.js.mil/jtims/welcome.do. From the JTIMS Login page, select the Request JTIMS ID link, located in the Restricted Login box on the left side of the page. The system will display the Request JTIMS ID page. Note: At a minimum, complete the required fields. Required fields are indicated with a red asterisk (*). In the Select User Group link for the USJFCOM User Group type in “DJ2000”. Enter your Personal Information in the available fields and menus. (* indicates a required field and cannot be left blank) Note the following additional information. JTIMS ID: JTIMS ID cannot contain spaces and must be at least five characters in length. The recommended format is "lastname.firstname". *Password: Passwords must contain at least 9 characters and include at least one number, one uppercase letter, one lowercase letter, and one special character (for example, myJTIMS#pwd1). Passwords cannot contain spaces. Confirm Password: Re-enter the same password as above. Town in which you were born: The user will be asked to answer this question if to request a forgotten password. Requested Role Type: Select the corresponding checkbox to identify the requested role(s). Note: Stratlift roles are not available for selection when requesting a JTIMS User ID. The user group lead assigns the Stratlift role after the user requests a JTIMS User ID. The requesting user should indicate in the “Justification” block that Stratlift roles are required.

Enclosure (3)

Appendix A

ENC (3)-A-2

Note: Roles are to be requested in accordance with the guidance in Appendix B to this enclosure. Multiple User Roles can be assigned to each JTIMS ID. User Group Lead (All permissions, including admin, for assigned User Group. This role is limited to select individuals in J7.) Training Plan Analyst (Manage Joint Training Plans, create events, adds training objectives and manage assessments) Force Provider (Acknowledges requests and assigns or de-assigns forces for an event.) Event Team Lead (Manage all aspects of the assigned event, to include assigning event Execution Analysts and Training Objective Analysts. Event Team Leads are assigned to a specific event by the UGL.) Event Manager (Manage Events) Training Objective Analyst (Manage training objectives for each assigned event.) Execution Analyst (Manage Collection Management Plan (CMP), TPOs and TPEs for assigned events.) Assessment Analyst (Conducts training assessments for assigned JMET(s) as Trained, Partially Trained, or Untrained (T, P, or U). JMSEL Analyst (Access to Event Scenarios) JTIMS Guest (Access JTIMS as guest). Justification: Explanation of why the user is requesting the role(s). Organization Affiliation: Additional information about the user. This information is associated with the user throughout the system and can be modified on the Update Profile page. Click the Continue button to submit the request. A Request JTIMS ID Verification page will appear. Verify the information entered is correct: Click the Request JTIMS ID button to submit the request. (Click the Edit button to change any information or click Cancel to return to the JTIMS Login page without requesting a JTIMS ID.) The Request JTIMS ID Confirmation page appears indicating that the request was submitted. Select the OK button to continue. The system returns to the JTIMS Login page. The request will be reviewed by the User Group Lead. Once approved, the requester will receive an email notification that the requested JTIMS ID has been approved. JTIMS Functionality: Detailed instructions for application use can be accessed from the JTIMS Home Page upper right hand corner in the Information Center. Here you will find a Quick Reference Guide and other useful reference material. Additionally, Clicking the “?” at right hand side of a page will take the user to an on-line help menu. JTIM Help: For USJFCOM JTIMS related issues contact the UGL at (757) 203-6168 (DSN 668-6168). Contact the appropriate Event Lead for exercise related questions.

ENC (3)-B-1 Enclosure (3)

Appendix B

Appendix B: Rolls and Responsibilities The Requested Role Type for USJFCOM JWFC personnel when requesting a JTIMS ID should be in accordance with the following guidelines. The role descriptions below are color coded to Figures B-1 and B-2 for easy reference. USJFCOM Desk Officers will request role type Training Plan Analyst. This will allow them to:

Manage Scenarios. Manage/View Change List Create New Events. View Collection Management Plans (CMP). Manage Training Proficiency Assessment (TPA).

Joint Event Support Team (JEST) Lead will request role type Event Team Lead. This will allow them to:

Import/Export JTIMS Lite. Manage/View Change Lists. Manage event scenarios. Manage event description and details. Assign Training Objective Analysts. Manage Event Training Objectives. Manage transportation Requirements. Manage Event Milestones. Manage Force Requirements. Publish/Unpublish/Cancel events. Manage Collection Management Plan. Assign Observers to TOs in CMP. View in Staffing TPO/TPE data. Manage TPOs. Manage TPE. Publish/Unpublish TPO/TPE data.

JEST Event Planners will request role types Event Manager, Training Objective Analyst and Execution Analyst. This will allow them to:

Manage/View Change lists. Manage scenarios. Manage Transportation Requirements. Manage Event Training Objectives. Manage Collection Management Plan. Assign Observers to TOs in CMP. View in Staffing TPO/TPE data. Manage TPOs and TFOs. Manage Training Proficiency Evaluations.

Scenario/JMSEL Managers will request role type JMSEL Analyst and JTIMS Guest. This will allow them to:

Manage Scenarios. Manage Event Training Objectives. Create and Export reports. Read only all event data.

Event Technical Coordinators will request role type JTIMS Guest. This will allow them to:


Appendix B

Create and Export reports. Read only all events data.

JEST Event Planner

Desk Officer TeamCOCOM Desk Officer

JEST Lead

Scenario/JMSEL Manager

Tech Coordinator

Training Plan Analyst

Execution Analyst

JMSEL AnalystJTIMS Guest

Event Manager

Event Team Lead

Training Objective AnalystJTIMS Guest

FIGURE B-1. Desk Officer Team

Deployable Training Team (DTT) Chief will request role types Training Plan Analyst, Event Team Lead and Senior O/C Analyst. This will allow them to:

Manage Scenarios. Manage/View Change List Create new events. View Collection Management Plans (CMP). Manage Training Proficiency Assessment (TPA). Import/Export JTIMS Lite. Manage/View Change Lists. Manage event scenarios. Manage event description and details. Assign Training Objective Analysts. Manage event training. Manage transportation Requirements. Manage Event Milestones. Manage Force Requirements. Publish/Unpublish/Cancel events. Manage Collection Management Plan. Assign Observers to TOs in CMP. View in Staffing TPO/TPE data. Manage TPOs. Manage TPE. Publish/Unpublish TPO/TPE data. Manage Task Performance Observations (TPOs). Manage Task Field Observations (TFOs). Post/Update the CSR.


Appendix B

Approve/Decline TPOs. Generate JMET Observations Report. View Posted CSRs. Manage CSR Section.

DTT Lead Observer Trainer (OT) will request role type Event Team Lead, Senior O/C Analyst and Training Objective Analyst. This will allow them to:

Import/Export JTIMS Lite. Manage/View Change Lists. Manage event scenarios. Manage event description and details. Assign Training Objective Analysts. Manage event training. Manage transportation Requirements. Manage Event Milestones. Manage Force Requirements. Publish/Unpublish/Cancel events. Manage Collection Management Plan. Assign Observers to TOs in CMP. View in Staffing TPO/TPE data. Manage TPOs. Manage TPE. Publish/Unpublish TPO/TPE data. Manage Task Performance Observations (TPOs). Manage Task Field Observations (TFOs). Post/Update CSR. Approve/Decline TPOs. Generate JMET Observations Report. View Posted CSRs. Manage CSR Section. Manage/View Change List. Manage Event Training Objectives.

DTT Analyst Team Chief/Lead Analyst will request role type Senior O/C Analyst, Training Objective Analyst and Execution Analyst. This will allow them to:

Manage Task Performance Observations (TPOs). Manage Task Field Observations (TFOs). Post/Update CSR. Approve/Decline TPOs. Generate JMET Observations Report. View Posted CSRs. Manage CSR Section. Manage/View Change List. Manage Event Training Objectives. Manage Collection Management Plan. Assign Observers to TOs in CMP. View in Staffing TPO/TPE data. Manage TPOs and TFOs. Manage Training Proficiency Evaluations.

DTT Team Members will request role type Training Objective Analyst and Execution Analyst. This will allow them to:


Appendix B

Manage/View Change List. Manage Event Training Objectives (TOs). Manage Collection Management Plan. Assign Observers to TOs in CMP. View in Staffing TPO/TPE data. Manage TPOs and TFOs. Manage Training Proficiency Evaluations.

DTT Analyst Team Members will request role type Training Objective Analyst and Execution Analyst. This will allow them to:

Manage/View Change List. Manage Event Training Objectives (TOs). Manage Collection Management Plan. Assign Observers to TOs in CMP. View in Staffing TPO/TPE data. Manage TPOs and TFOs. Manage Training Proficiency Evaluations.

Deployable Training Team (DTT)Chief DTT

DTT Lead Observer Trainer (OT)

Training Plan Analyst

Execution Analyst

Event Team Lead

Training Objective Analyst

Senior Mentor

Analyst Team (AT) Chief

Lead Analyst

AT Member

DTT OT Team Member

Event Team LeadSenior O/C Analyst

Senior O/C AnalystTraining Objective Analyst

Training Objective AnalystExecution Analyst

Training Objective AnalystExecution Analyst

Execution AnalystTraining Objective Analyst

Senior O/C Analyst

Commander

FIGURE B-2. Deployable Training Team (DTT)

ENC (3)-C-1 Enclosure (3)

Appendix C

Appendix C: Training

Purpose The JTIMS requires data input mandating all users receive the proper training in the JTS and JTIMS in order to use the JTIMS effectively. On a periodic basis USJFCOM JTIMS “users” will be made aware of the latest JTIMS information and capabilities changes. Formal JTIMS training will be conducted by the command Joint Training System Specialist (JTSS) on an as needed/requested basis. Course availability Familiarization Course. (1 half Day) Limited, hands-on (queries, reports). This course will familiarize personnel with the JTS, how it relates to JTIMS, and concludes with a demonstration of the relationship. It is tailored mainly to senior leadership positions (and other similar positions), which require an overall knowledge of the system. User Course. (1 half Day) – Limited, hands-on, as required. This course will demonstrate the value of JTIMS as a database. Instruction is concentrated and tailored to the users’ needs (i.e. Desk Officers and TD Group analysts). This course also contains a familiarization block to tie all four phases of the JTS into JTIMS. Event Planner Course. (1-2 Day) – Intensive, hands-on instruction for all phases. This course contains in-depth instruction on not only usage of JTIMS, but actual data entry/edit. This course will give in-depth instruction on all four phases of the JTS, and how to enter, edit, and retrieve data throughout the system. JTIMS training shall be requested by the USJFCOM user by contacting the Plans Branch of the Operations Group at the Joint Warfighting Center. Training is available at the USJFCOM –JWFC facility in Suffolk, VA and must be coordinated in advance. Through prior coordination, supported/hosting commands (i.e. components and subordinates) can be trained at their facilities provided appropriate workstations (SIPRNET capable) are available.

ENC (3)-C-2 Enclosure (3)

Appendix C

Intentionally Blank


Enclosure (4): JELC POA&M and Deliverable Checklist

TASK/PRODUCT DUE OPR

Counter IED System Defeat Support IAW JELC POAM IED JETA Planning and Integration IAW JELC POAM TECH SUPT Training Objective Development Support 30 Days Prior to CDC JEST/JTSA Assist Supported Command with JMETs (App by Tng Aud CDR) 30 Days Prior to CDC JEST/JTSA Plan of Action and Milestones (POA&M) 30 Days Prior to CDC JEST/JTSA CDC VTC Schedule (if applicable) 1 Week Prior to CDC TECH SUPT CONCEPT DEVELOPMENT CONFERENCE (CDC) CDC Conference/Meeting Minutes 1 Week After CDC TECH SUPT IPC VTC Schedule (if applicable) 1 Week Prior to IPC TECH SUPT INITIAL PLANNING CONFERENCE (IPC) Simulation Selection IAW JELC POA&M TECH SUPT Intel Plan of Action and Milestones (POA&M) (Tab 9) at IPC JEST Exercise Directive IPC JEST Exercise Manning assistance request IPC JEST IPC Conference/Meeting Minutes 1 Week After IPC TECH SUPT Site Survey MOA (as required) from JELC POA&M TECH SUPT SITE SURVEY Site Survey Report (as required) 30 Days After Survey TECH SUPT Master Scenario Events List (MSEL data structure) 10 Days Prior to MDC SCE/MSEL MDC VTC Schedule (if applicable) 1 Week Prior to MDC TECH SUPT MSEL DEVELOPMENT CONFERENCE (MDC) MDC Conference/Meeting Minutes 1 Week After MDC TECH SUPT Focus Area Analysis Continuous SCE/MSEL Scenario (includes RTC document) 10 days prior to MPC SCE/MSEL MPC VTC Schedule (if applicable) 1 Week Prior to MPC TECH SUPT MIDDLE PLANNING CONFERENCE (MPC) OCONUS Telecommunications service request for execution (or pegged to another date)

execution (or other pegged dates) minus 180 days TECH SUPT

CONUS Telecommunications service request for execution (or pegged to another date)

execution (or other pegged date) minus 120 days TECH SUPT

Event Floor Plans draft Draft NLT MPC TECH SUPT Intel MOA (Tab 4) at MPC INTEL Consolidated exercise support request (Tab 5) at MPC JEST Intel training objectives (Tab 6) at MPC INTEL Intel Exercise Support Manning Document (ESMD) (Tab 7) at MPC INTEL Proposed J2 mission vision statement (Tab 8) at MPC INTEL Road to Crisis (Tab 10) at MPC SCE/MSEL Brief Academic Training Plan Prior To End of MPC DTAT Systems Architecture Diagrams Draft Draft NLT MPC TECH SUPT M&S/C4 Architecture Plan Draft Draft NLT MPC TECH SUPT Technical Resources Requirements Draft NLT MPC + 7 days TECH SUPT Technical Event Planning Conference/Meeting Minutes 1 Week After MPC TECH SUPT OPTASKCOP and OPTASKLINK - draft 2 weeks after MPC TECH SUPT


Operational Environment (PMESII) Overview MPC plus 30 days SCE/MSEL M&S database 2 weeks before ET1 TECH SUPT Event Test #1 Test Plan ET1 minus 7 days TECH SUPT

Event Test #1 Control Brief (Forces) NLT 1 week prior to event test #1 TECH SUPT

EVENT TEST 1 Event Test #1 Test Results Report ET1 plus 7 days TECH SUPT Publish Intelligence Annex B 30 Days Prior to FPC INTEL Provide Threat Operations Rules of Engagement 30 Days Prior to FPC INTEL CAX Information Management (IM) Plan 30 Days Prior to FPC JEST/IMO Master Scenario Events List to Support MSEL Synch 10 Days Prior to FPC SCE/MSEL FPC VTC Schedule (if applicable) 1 Week Prior to FPC TECH SUPT FINAL PLANNING CONFERENCE (FPC) Contractor training program schedule IAW JELC POA&M TECH SUPT Systems Architecture Diagrams Final Draft NLT FPC + 7 days TECH SUPT Force Protection Plan FPC JEST Event Floor Plans final Final NLT FPC TECH SUPT Technical Event Planning Conference/Meeting Minutes 1 Week After FPC TECH SUPT M&S/C4 Architecture Plan Final Final NLT FPC plus 7 days TECH SUPT

OPTASKCOP and OPTASKLINK - final 2 weeks after FPC OR OR OR 7 days before ET3 TECH SUPT

JECG Architecture Control Document 30 Days after FPC JEST Draft Event M&S Control Plan and Crash Recovery Procedures Plan

Draft NLT 3 weeks prior to event test #2 TECH SUPT

Interim authority to operate authorization 2 weeks before net activation (eg ET2 here) TECH SUPT

Event Test #2 Test Plan Final NLT 1 week prior to event test #2 TECH SUPT


EVENT TEST 2 Event Test #2 Test Results Report NLT 1 week after ET2 TECH SUPT MSEL Synch VTC Schedule (if applicable) 1 Week Prior to MSC TECH SUPT MSEL SYNCHRONIZATION CONFERENCE Technical Event Planning Conference/Meeting Minutes 1 Week After MSC TECH SUPT EXECUTION DEPLOYMENT

Draft Rules and Workarounds Book Initial NLT 2 weeks prior to event test #3 TECH SUPT

Event Test #3 Test Plan Final NLT 1 week prior to event test #3 TECH SUPT


EVENT TEST 3 Final Event M&S Control Plan and Crash Recovery Procedures Plan Final NLT end of event test #3 TECH SUPT Final Rules and Workarounds Book Initial NLT end of event test #3 TECH SUPT Publish Event Test #3 Test Results Report NLT 1 week after ET3 TECH SUPT ACADEMICS Academic Seminar Class/phase start date DTAT


Functional roles / Event Support Manning Document (ESMD) 75 days prior to execution JEST

Event Manning 75 days prior to execution / deployment TECH SUPT

Event Control Plan 30 Days Prior to execution JEST Joint Exercise Control Group (JECG) Training Plan 30 days prior EXEC JEST Mini-Exercise Plan 30 days prior EXEC JEST Collection Management Plan (CMP) 15 days prior to execution DTAT JECG Pre-Ramp-up Intel summary (Tab 11) 10 working days prior to execution INTEL Information Operations (IO) Documents 10 days prior EXEC IO JECG Pre-MRX Up INTSUM (Tab 12) 10 working days prior to execution INTEL Intel script road map (Tab 14) 10 working days prior to execution INTEL Event Documentation 1 Week Prior to Event JEST Threat Concept of Ops 10 days before execution (if req'd) FORCES Provide WNN/Studio Support Road to Crisis (RTC) Video due 7

days before execution of events requiring same. During Execution (as required) 12 hrs of request.

WNN

Sustainment/Deployment 7 days before execution of each conf or event (if req'd by exercise) SUST

Interagency (IA) Documents/Role Playing Prior to execution for events requiring IA scenario IA

EXECUTION Intel Exercise Design Plan 1st day execution (UE event) INTEL Joint Master Scenario Events list output (Tab 13) 1st day of Execution SCE/MSEL Intel JMSEL input ROE (Tab 3) 1st day of Execution SCE/MSEL

Hotwash Reports and Daily Event Summary Reports Daily During Execution / last day of EXEC shown TECH SUPT

Conduct Facilitated After Action Review (FAAR) At Completion of Exercise employing a DTT DTAT

FACILIATED AFTER ACTION REVIEW (FAAR) Produce Commander's Summary Report (CSR) 10 days After FAAR DTAT Produce Technical After Action Review (TARR) Report 30 days after event TECH SUPT Lessons Learned 30 days after event TECH SUPT Internal After Action Review Report (IAAR) NLT 30 days after execution JEST Collect, reduce, and archive exercise data (JTER data) 30 days after execution JEST Input to COCOM/Training Program Accreditation Report IAW COCOM accred. POA&M JEST


Intentionally Blank

Enclosure (5)

ENC (5)-1

Enclosure (5): Pre-Exercise Executive Brief Format

1. Purpose This annex links to a template for structuring an update briefing to the Director, J7/Joint Warfighting Center on the status of planning and preparation for a specific exercise. This briefing should be provided 30 days prior to exercise execution. 2. Briefing Format a. Black and white slides (only use color when it will increase understanding) b. Number all slides c. No abbreviations d. Agenda: (1) Exercise Overview (2) Exercise Objectives (3) Training Audience, Command Organization, and Location (4) Exercise Construct (a) Scenario Overview (b) Exercise Flow (c) Joint Exercise Control Group Architecture (5) Joint Warfighting Center Support (a) Personnel (b) Force Protection (c) Budget 3. Joint Warfighting Center Point of Contact Questions concerning the pre-exercise executive brief should be directed to:

Enclosure (5)

ENC (5)-2

Intentionally Blank


Enclosure (6): Exercise Directive Example FM HQ USPACOM HONOLULU HI/J7// TO SECSTATE WASHINGTON DC OSDASDSOLIC AMEMBASSY TOKYO AMEMBASSY JAKARTA AMEMBASSY SINGAPORE AMEMBASSY BANGKOK USDAO TOKYO USDAO JAKARTA USDAO SINGAPORE USDAO BANGKOK CHJUSMAGTHAI BANGKOK TH ODC JAKARTA CDRUSARPAC FT SHAFTER HI//G3/APOP/APOP-EX/APOP-TREX// COMSOCPAC HONOLULU HI//SOJ3// 13AF HICKAM AFB HI//A3// COMMARFORPAC//G3/G5// COMPACFLT PEARL HARBOR HI//N3// CDR USJFCOM NORFOLK VA//J7// INFO CDRMTMC FALLS CHURCH VA CDR USJFCOM NORFOLK VA CDRUSASOC FT BRAGG NC COMSC WASHINGTON DC CG III MEF COMSEVENTHFLT//N3// CDR4THPSYOPGP FT BRAGG NC DIA WASHINGTON DC//DHO-3// COMNAVFORJAPAN YOKOSUKA JA CTF 76 BLOUNT ISLAND COMMAND COMNAVSURFPAC COMTHIRDFLT//N3// COMFFC COMEXSTRIKGRU THREE COMNAVBEACHGRU ONE PHIBCB ONE NAVCARGOBN ONE CG MARCORLOGCOM ALBANY GA COMSEALOGFE SINGAPORE COMPSRON THREE COMPSRON TWO COMNECCLITTLE CREEK VA JICPAC HONOLULU HI HQ AMC SCOTT AFB IL FIRST NCD FORWARD PEARL HARBOR HI CDR USSOCOM MACDILL AFB FL USACAPOC 96 CA BN CDR FT BRAGG NC CDR USTRANSCOM SCOTT AFB IL SJFHQ PACIFIC CDR USPACOM HONOLULU HI//J1/J2/J3/J4/J5/J6/J7/J8/J01PA/J06/J07// CLASSIFICATION (U N C L A S S I F I E D)// EXER/COBRA GOLD 2008 (CG 08) MSGID/GENADMIN/USPACOM/J7//


SUBJ/EXERCISE COBRA GOLD 2008 (CG 08) EXERCISE DIRECTIVE REF/A/ DOC/USPACOM/31 JUL 07// REF/B/DOC/USPACOM/24 JUL 07// REF/C/DOC/USPACOM/22 JUN 07// REF/D/DOC/USPACOM/MAY 07// REF/E/DOC/CJCSI 3121.01B/13 JUN 05// REF/F/DOC/CJCS/15 FEB 05// REF/G/DOC/USCINCPACINST S3710.2J/13 NOV 00// REF/H/DOC/JP 3-16/5 APR 00// REF/I/DCO/MNF SOP/31 JAN 07// NARR/REF A IS USPACOM PACIFIC JOINT TRAINING STRATEGY. REF B IS USPACOMINST 0505.2A THAT ESTABLISHES USPACOM JOINT EXERCISE PROGRAM. REF C IS USPACOM EXERCISE COBRA GOLD 2008 INITIATING DIRECTIVE. REF D IS USPACOM THEATER SPECIFIC TPFDD LOI THAT ESTABLISHES GUIDANCE ON TPFDD PROCEDURES. REF E IS CJCS STANDING RULES OF ENGAGEMENT / STANDING RULES FOR THE USE OF FORCE FOR U.S. FORCES. REF F IS CJCSINST 3150.25B THAT ESTABLISHES POLICY GUIDANCE, AND RESPONSIBILITIES FOR THE CJCS JOINT LESSONS LEARNED PROGRAM (JLLP). REF G IS USPACOM THEATER-SPECIFIC ROE. REF H IS JOINT PUBLICATION 3-16, JOINT DOCTRINE FOR MULTINATIONAL OPERATIONS. REF I IS MULTINATIONAL FORCE STANDING OPERATING PROCEDURES (MNF SOP), REV 2.// JUSMAGTHAI: PLEASE PASS TO ROYAL THAI SUPREME COMMAND (RTSC) J7, ATTN: MAJGEN TARNCHAIYAN, CG 08 JOINT AND COALITION EXERCISE PLANNING OFFICE// 1. REMARKS. THIS DIRECTIVE PROVIDES UPDATED USPACOM PLANNING AND TASKING GUIDANCE FOR EXERCISE COBRA GOLD 2008 (CG 08) U.S. EXECUTIVE AGENT (EA), U.S. JOINT TASK FORCE (JTF), AND USPACOM COMPONENTS. EXERCISE COBRA GOLD IS AN ANNUAL CJCS, PART 1, USPACOM SPONSORED, US JOINT AND MULTINATIONAL THEATER SECURITY COOPERATION PLAN (TSCP) EXERCISE. MAJOR EXERCISE EVENTS IN USPACOM PRIORITY ORDER ARE: COALITION TASK FORCE (CTF) AND UNITED NATIONS FORCE HEADQUARTERS (UNFHQ) COMMAND POST EXERCISE (CPX); HUMANITARIAN / CIVIC ASSISTANCE (H/CA) PROJECTS; AND A FIELD TRAINING EXERCISE (FTX) THAT INCLUDES LIVE FIRE EVENTS. CG EXERCISE TAKES PLACE IN THE KINGDOM OF THAILAND. ALL EVENTS THAT TAKE PLACE IN THAILAND ARE IDENTIFIED AS THAILAND STANDARD (G) DATES / TIMES. ALL EVENTS THAT TAKE PLACE IN THE UNITED STATES ARE IDENTIFIED AS HAWAII STANDARD (W) DATES / TIMES. 2. EXERCISE DATES. 2.1. INCLUSIVE DATES: 15 APR - 28 MAY 08. 2.2. EMPLOYMENT DATES: 5 - 21 MAY 08. 2.3. CRITICAL CANCELLATION DATE: 2 APR 08. 3. EXERCISE, GOALS, OBJECTIVES, STRATEGIC COMMUNICATION MESSAGE, COALITION MISSION ESSENTIAL TASK LIST (CMETL) / UNITED NATIONS TASK LIST (UNTL). 3.1. EXERCISE GOALS. EXERCISE COBRA GOLD IS DESIGNED TO IMPROVE US JOINT AND MULTINATIONAL INTEROPERABILITY AND CAPABILITY TO EFFECTIVELY RESPOND AND EXECUTE COMPLEX MULTINATIONAL OPERATIONS. SPECIFIC GOALS FOR THE US JOINT TASK FORCE (JTF) ARE: 3.1.1. TRAIN U.S. JOINT / MULTINATIONAL BATTLE STAFFS AND FORCES. 3.1.2. EVALUATE PLANS FOR SMALL SCALE CONTINGENCIES (SSC). 3.1.3. EXECUTE ENGAGEMENT STRATEGIES. 3.1.4. STRESS AND EVALUATE STRATEGIC TRANSPORTATION AND C4I. 3.1.5. ADVANCE AND EVALUATE JOINT AND MULTINATIONAL INTEROPERABILITY AND CAPABILITY TO PLAN AND EXECUTE THE MOST LIKELY CONTINGENCY OPERATIONS IN THE SOUTHEAST ASIA REGION. 3.1.8. EXERCISE SERVICE UNIQUE DEPLOYMENT AND REDEPLOYMENT SKILLS. 3.1. 9. ADVANCE PARTNER NATIONS ABILITY AND CONFIDENCE TO LEAD THE PLANNING AND EXECUTION OF COMPLEX MULTINATIONAL OPERATIONS. 3.2. OBJECTIVES. CONDUCT A JOINT AND MULTINATIONAL CTF AND UNFHQ PEACE SUPPORT OPERATION; CONDUCT H/CA PROJECTS THAT MAXIMIZES POTENTIAL SECURITY BENEFITS


AND FOSTERS GOOD WILL OF LOCAL RESIDENTS LIVING NEAR EXERCISE LOCATIONS; AND CONDUCT A FTX THAT INCLUDES: LIVE FIRE; US JOINT; AND MULTINATIONAL EVENTS. 3.3. STRATEGIC COMMUNICATION MESSAGE. THE EXERCISE SCENARIO IS FOCUSED ON THE MOST LIKELY CONTINGENCY OPERATIONS EXPECTED IN THE SOUTHEAST ASIA REGION, REINFORCES USPACOM COMMITMENT TO THE SOUTHEAST ASIA REGION, MAXIMIZES POTENTIAL SECURITY BENEFIT, IMPROVES PARTICIPATING NATIONS’ MILITARY-TO-MILITARY RELATIONSHIPS, AND ADVANCES USPACOM THEATER SECURITY COOPERATION (TSC) OBJECTIVES. 3.4. CMETL. THE FOLLOWING IS THE CTF CMETL FOR CG 08: 3.4.1. ST 8.1.2 PROMOTE REGIONAL SECURITY AND INTEROPERABILITY (C5). 3.4.2. OP 4.7.4 TRANSITION TO CIVIL ADMINISTRATIVE / UNITED NATIONS FORCES (C3). 3.4.3. OP 4.7.5 COORDINATE POLITICO-MILITARY SUPPORT (C5). 3.4.4. OP 4.7.6 COORDINATE CIVIL AFFAIRS (C7). 3.4.5. OP 4.8 ACQUIRE, MANAGE, AND DISTRIBUTE FUNDING (C8). 3.4.6. OP 5 PROVIDE OPERATIONAL COMMAND AND CONTROL (C3). 3.4.7. OP 5.1 ACQUIRE AND COMMUNICATE OPERATIONAL LEVEL INFORMATION AND MAINTAIN STATUS (C6). 3.4.8. OP 5.3 PREPARE PLANS AND ORDERS (C5). 3.4.9. OP 5.3.3 DETERMINE OPERATIONAL END STATE (C3). 3.4.10. OP 5.5 ESTABLISH, ORGANIZE, AND OPERATE A JOINT AND COALITION TASK FORCE (JTF / CTF) HEADQUARTERS (C3). 3.4.11. OP 5.5.5 ESTABLISH COMMAND TRANSITION CRITERIA AND PROCEDURES (C5). 3.4.12. OP 6.2 PROVIDE PROTECTION FOR OPERATIONAL FORCES (C3). 3.4.13. OP 5.7.4 COORDINATE PLANS WITH UNITED NATIONS FORCE HEADQUARTERS (UNFHQ), HUMANITARIAN, AND NON-MILITARY ORGANIZATIONS (C5). 3.4.13. OP 7.4 COORDINATE CONSEQUENCE MANAGEMENT (CM) (C3). 3.5. UNTL. THE FOLLOWING IS THE UNFHQ UNTL FOR CG 08: 3.5.1. OPERATIONAL LEVEL MONITORING, SUPERVISING, OBSERVING, REPORTING (U3). 3.5.2. OPERATIONAL LEVEL MANAGEMENT OF PATROLS, PATROLLING & REPORTING (U3). 3.5.3. COMBAT INDICATORS AND EARLY WARNING MILITARY INTELLIGENCE (U2). 3.5.4. NEGOTIATION AND LIAISON (U5). 3.5.5. COMMAND, CONTROL AND COMMUNICATIONS (U3). 3.5.6. OPERATIONAL LEVEL SECURITY (U7). 3.5.7. PUBLIC INFORMATION (U7). 3.5.8. MILITARY SUPPORT TO OTHER AGENCIES (U7). 3.5.9. OPERATIONAL LEVEL LOGISTICS (U4). 3.5.10. MEDICAL (U4). 3.5.11. OPERATIONAL LEVEL AIR OPERATIONS SUPPORT (U3). 3.5.12. MISSION TRAINING (U3). 4. EXERCISE PARTICIPANTS. 4.1. THE PRIMARY TRAINING AUDIENCES ARE THE CTF STAFF, WHICH INCLUDES; U.S. JTF STAFF; ROYAL THAI ARMED FORCES (RTARF) JTF STAFF; SINGAPORE ARMED FORCES (SAF) STAFF, AND THE UNITED NATIONS FORCES HEADQUARTERS (UNFHQ) STAFF WHICH INCLUDES; RTARF, JAPANESE SELF DEFENSE FORCES (JSDF); SINGAPORE ARMED FORCES (SAF); AND INDONESIAN NATIONAL DEFENSE FORCES (TNI). 4.2. THE SECONDARY TRAINING AUDIENCE IS THE CTF COMPONENTS. 4.3. PARTICIPATING U.S. MAJOR COMMANDS INCLUDE: USPACOM; USTRANSCOM; MARFORPAC; USARPAC; PACFLT; PACAF; AND SOCPAC. PARTICIPATING THAILAND MAJOR COMMANDS INCLUDE; ROYAL THAI SUPREME COMMAND (RTSC); THAI ARMY; THAI MARINE CORPS; THAI NAVY; THAI AIR FORCE; AND THAI SPECIAL OPERATIONS FORCES (SOF). 4.4. PLANNED INTERNATIONAL, NON-GOVERNMENTAL, HUMANITARIAN, AND U.S. ACTIVITIES / DEPARTMENTS / AGENCIES INCLUDE: CENTER FOR DISEASE CONTROL (CDC); WORLD HEALTH ORGANIZATION (WHO); USPACOM CENTER OF EXCELLENCE (COE); UN WORLD FOOD PROGRAM (WFP); INTERNATIONAL MEDICAL CORPS (IMC); UN OFFICE FOR THE COORDINATION OF HUMANITARIAN AFFAIRS (OCHA); INTERNATIONAL COMMITTEE OF THE RED CROSS (ICRC); AND US DEPARTMENT OF STATE (DOS).


4.5. TENTATIVE MULTINATIONAL PLANNING AUGMENTATION TEAM (MPAT) NATIONS INCLUDE: AUSTRALIA; BRUNEI; FRANCE; ITALY; UNITED KINGDOM; BANGLADESH; INDIA; MALAYSIA; MONGOLIA; AND PHILIPPINES. 4.6. TENTATIVE COALITION OBSERVER LIAISON TEAM (COLT) NATIONS INCLUDE: CHINA; SOUTH KOREA; SRI LANKA; PAKISTAN; NEPAL; VIETNAM; CAMBODIA; AND LAOS. 5. EXERCISE PLANNING GROUP. 5.1. USPACOM EXERCISE REVIEWER AND CO-EXERCISE DIRECTOR, IS COL DUVALL, USPACOM J7. 5.2. THAILAND CO-EXERCISE DIRECTOR IS LTGEN WORAPONG, RTSC J3. 5.3. COMMANDER, COALITION TASK FORCE, IS LTGEN WIBOONSAK (CDR RTA 2ND CORPS). 5.4. DEPUTY COMMANDER, COALITION TASK FORCE, AND COMMANDER, UNITED STATES JOINT TASK FORCE, IS LTGEN GOODMAN (COMMARFORPAC). 5.5. COMMANDER, UNITED NATIONS (UN) FORCES IS TBD. 5.6. USPACOM EXECUTIVE AGENT IS MARFORPAC. 5.7. SINGAPOREAN CONTINGENT COMMANDER IS TBD. 5.8. JAPANESE CONTINGENT COMMANDER IS TBD. 5.9. INDONESIAN CONTINGENT COMMANDER IS TBD. 6. U.S. COMMAND RELATIONSHIPS. 6.1. MARFORPAC IS THE SUPPORTED USPACOM COMPONENT FOR ALL EXERCISE RELATED EVENTS. ALL OTHER USPACOM COMPONENTS AND EXTERNAL USPACOM COMMANDS ARE IN A SUPPORTING ROLE TO MARFORPAC. 6.2. COMMARFORPAC IS THE SUPPORTED CDR, U.S. JTF. 6.3. EACH SERVICE AND PARENT COMMAND WILL MAINTAIN OPERATIONAL CONTROL (OPCON) AND ADMINISTRATIVE CONTROL (ADCON) OF THEIR SERVICE MEMBERS. 6.4. CDR, MARFORPAC, HAS FORCE PROTECTION AUTHORITY FOR ALL U.S. FORCES WHILE IN THAILAND FOR ANY CG 08 EXERCISE RELATED EVENTS (CONFERENCES, SITE SURVEYS, WORKSHOPS, MEETINGS, COORDINATION, VISITS, EXERCISE EXECUTION, ETC.). COMMANDERS AT ALL LEVELS ARE AUTHORIZED MORE RESTRICTIVE FORCE PROTECTION MEASURES IAW PARENT UNIT POLICIES / TTP’S / SOP’S. 6.5. THE COMMANDER, U.S. JTF WILL REPORT DIRECTLY TO THE COMMANDER, UNITED STATES PACIFIC COMMAND, WITH COURTESY INFORMATION TO THE U.S. EXERCISE REVIEWER AND EXERCISE DIRECTOR (USPACOM J7). 7. COALITION EXERCISE CONTROL GROUP (CECG). 7.1. CECG DIRECTOR IS MAJGEN TARNCHAIYAN (RTSC J7). 7.2. CECG DEPUTY DIRECTOR IS MG WILSON (USARPAC). 8. U.S. FORCES. 8.1. USPACOM GUIDANCE AND INTENT FOR THE JOINT EXERCISE PROGRAM IS THAT ALL USPACOM COMPONENTS WILL PARTICIPATE / PROVIDE FORCES FOR EACH OF THE EXERCISE MAJOR EVENTS. USPACOM COMPONENTS WILL PROVIDE THE FOLLOWING FORCES FOR CG 08: 8.2. MARFORPAC. 8.2.1. APPROPRIATE PERSONNEL TO FULFILL EXECUTIVE AGENT RESPONSIBILITIES. 8.2.2. U.S. JTF HEADQUARTERS NUCLEUS. 8.2.3. U.S. MARFOR CECG RESPONSE CELL. 8.2.4. U.S. MARFOR H/CA (ENCAP) FORCES. 8.2.5. U.S. MARFOR FTX FORCES. 8.2.6. EXERCISE FREEDOM BANNER BANNER MARITIME PRE-POSITIONING FORCE (MPF) FORCES. 8.3. USARPAC. 8.3.1. APPROPRIATE PERSONNEL AND EQUIPMENT TO FULFILL CECG C2 AND SUPPORT REQUIREMENTS. 8.3.2. U.S. JTF AUGMENTATION AS IDENTIFIED BY THE U.S. JTF CDR WITHIN THE JOINT MANNING DOCUMENT (JMD). 8.3.3. U.S. ARFOR CECG RESPONSE CELL. 8.3.4. U.S. ARFOR H/CA (MEDCAP / ENCAP) FORCES. 8.3.5. U.S. ARFOR FTX FORCES.


8.4. PACFLT. 8.4.1. U.S. JTF AUGMENTATION AS IDENTIFIED BY THE U.S. JTF CDR WITHIN THE JOINT MANNING DOCUMENT (JMD). 8.4.2. U.S. NAVFOR CECG RESPONSE CELL. 8.4.3. U.S. NAVFOR H/CA (MEDCAP / ENCAP) FORCES. 8.4.4. U.S. NAVFOR FTX FORCES. 8.4.5. EXERCISE FREEDOM BANNER MARITIME PRE-POSITIONING FORCE (MPF) NAVAL SUPPORT ELEMENTS (NSE) TO INCLUDE: COMMANDER MARITIME PRE-POSITIONING FORCE (CMPF); C2 OF NAVAL SUPPORT ELEMENT (NSE) / MARITIME PRE-POSITIONING FORCE (MPF); LIGHTERAGE OPERATIONS; LIFT-ON / LIFT -OFF (LO/LO), ROLL-ON / ROLL-OFF (RO/RO); INTERNAL SECURITY OF MARITIME PRE-POSITIONING SHIP (MPS), BEACH AND PORT SECURITY FOR MPF OPERATIONS, AND WATERBORNE SECURITY OF MPS. 8.5. PACAF. 8.5.1. U.S. JTF AUGMENTATION AS IDENTIFIED BY U.S. THE U.S. JTF CDR WITHIN THE JOINT MANNING DOCUMENT (JMD). 8.5.2. U.S. AFFOR CECG RESPONSE CELL. 8.5.3. U.S. AFFOR FTX FORCES. 8.6. SOCPAC. 8.6.1. U.S. JTF AUGMENTATION AS IDENTIFIED BY THE U.S. JTF CDR WITHIN THE JOINT MANNING DOCUMENT (JMD). 8.6.2. U.S. SOF CECG RESPONSE CELL. 8.6.3. U.S. SOF FTX FORCES. 9. EXERCISE CONCEPT. 9.1. CG 08 EXERCISE CONCEPT BY MAJOR EVENT ARE: 9.1.1. U.S. JOINT AND MULTINATIONAL COMMAND POST EXERCISE (CPX) THAT INCLUDES A ROYAL THAI ARMED FORCES (RTARF) LED UNITED NATIONS SECURITY COUNCIL RESOLUTION-AUTHORIZED (UNSCR-AUTH) MULTINATIONAL COALITION TASK FORCE (CTF) HEADQUARTERS, AND A SEPARATE UNITED NATIONS MANDATED (UN-MAN) UNITED NATIONS FORCES HEADQUARTERS (UNFHQ). THE CTF WILL UTILIZE REF I (MNF SOP) FOR CTF PROCEDURES. THE MNF SOP IS LOCATED AT THE FOLLOWING URL: HTTP://WWW.MNFSOP.COM. 9.1.2. MULTINATIONAL HUMANITARIAN / CIVIC ASSISTANCE (H/CA) PROJECTS THAT MAXIMIZE POTENTIAL SECURITY BENEFITS, AND GOOD WILL OF LOCAL POPULACE LIVING NEAR EXERCISE LOCATIONS. 9.1.3. FIELD TRAINING EXERCISE (FTX) DESIGNED TO ADVANCE U.S. JOINT INTEROPERABILITY AND TACTICAL OPERATIONAL READINESS: IMPROVE MULTINATIONAL COMBINED-ARMS INTEROPERABILITY AND OPERATIONAL TACTICAL READINESS; AND MIL-TO-MIL RELATIONS. SEEK OPPORTUNITIES TO LINK APPROPRIATE FTX EVENTS TO THE CPX SCENARIO TO ADVANCE EXERCISE REALISM AND CAPACITY BUILDING. 10. JTF CERTIFICATION. 10.1. CG 08 IS NOT A U.S. JTF CERTIFICATION EXERCISE. 11. EVALUATION CONCEPT. 11.1. EA WILL IDENTIFY THE CG 08 PRIMARY TRAINING AUDIENCE AFTER ACTION REVIEW (AAR) REQUIREMENTS, AND IN COORDINATION WITH THE CTF AND UNFHQ PARTICIPATING NATIONS, ESTABLISH AND CONDUCT AN APPROPRIATE MULTINATIONAL AAR TEAM FOR THE EXERCISE. 11.2. IAW REF F, ALL USPACOM COMPONENTS WILL FORWARD CG 08 OBSERVATIONS, LESSONS LEARNED, AND ISSUES FOR RESOLUTION TO THE U.S. JTF COMMANDER NLT 31 MAY 08. COMMANDER, U.S. JTF, WILL BE THE POINT OF SYNCHRONIZATION FOR ALL JOINT LESSONS LEARNED AND ISSUES FOR RESOLUTION. NLT 22 JUNE 08, THE COMMANDER, U.S. JTF, WILL ENTER APPROPRIATE OBSERVATIONS, LESSONS LEARNED, AND ISSUES FOR RESOLUTION ON THE USPACOM JOINT LESSON LEARNED PROGRAM SIPRNET WEB SITE LOCATED AT: HTTP://II.GSF.PACOM.SMIL.MIL (ALL LOWER CASE). 12. REPORTING. 12.1. IN-PROGRESS SITUATION REPORTS (SITREP). EA IS RESPONSIBLE FOR SUBMITTING DAILY SITREPS TO HQ USPACOM JOINT OPERATIONS CENTER (JOC) AND J7 ON EXERCISE


ISSUES, DEVELOPMENTS, AND ACCOMPLISHMENTS DURING CG 08 EXERCISE EXECUTION (8-21 MAY 08). 12.2. COMMANDER’S QUICK LOOK REPORT. COMMARFORPAC (U.S. JTF) IS RESPONSIBLE FOR SUBMITTING THE COMMANDER’S QUICK LOOK REPORT TO THE CDR USPACOM, NLT 29 MAY. THE COMMANDER’S QUICK LOOK REPORT FORMAT AND SUBMISSION GUIDANCE IS FOUND IN USPACOMINST 0505.2A, USPACOM JOINT EXERCISE PROGRAM (JEP). 12.3. EXERCISE SUMMARY REPORT. MARFORPAC (EA) IS RESPONSIBLE FOR SUBMITTING AN EXERCISE SUMMARY REPORT TO THE USPACOM J7 NLT 13 JUN 08. THE EXERCISE SUMMARY REPORT FORMAT IS FOUND IN THE USPACOMINST 0505.2A, USPACOM JOINT EXERCISE PROGRAM (JEP). 13. EXPERIMENTATION / TRANSFORMATION INTEGRATION. 13.1. EXPERIMENTATION INTEGRATION: IAW REF B, AND THE USPACOM THEATER PLAN FOR TRANSFORMATION, JOINT EXPERIMENTATION INITIATIVES MAY BE INTEGRATED INTO CG 08. ALL JOINT EXPERIMENTATION AND TRANSFORMATION INITIATIVES FOR CG 08 MUST HAVE RECEIVED FINAL APPROVAL FOR INTEGRATION DURING THE INITIAL PLANNING CONFERENCE (IPC) BY THE USPACOM J7, RTSC J3, EA, AND U.S. AND THAI JTF. 13.2. USPACOM J8 (TRANSFORMATION, EXPERIMENTATION, AND ACQUISITION BRANCH) WILL SUBMIT A DETAILED EXPERIMENTATION PLAN FOR APPROVAL TO USPACOM J7, VIA U.S. EA AND U.S. JTF, NO LATER THAN 7 DEC 2007. THE EXPERIMENTATION PLAN WILL INCLUDE: THE PROJECT NAME; PROJECT SPONSOR; DETAILED EXPERIMENTATION OBJECTIVES; LINKAGE TO EXERCISE OBJECTIVES AND EXERCISE CMETL; EXPERIMENTATION TRAINING PLAN; RESOURCE REQUIREMENTS; AND DELIVERABLES. 14. BUDGET GUIDANCE. 14.1. GENERAL. PROGRAMMED FUNDING LEVELS ARE DETERMINED AND APPROVED BY USPACOM. PROGRAMMED FUNDING INCLUDES: STRATEGIC LIFT; EXERCISE RELATED CONSTRUCTION (ERC); TITLE 10 DEVELOPING COUNTRIES COMBINED EXERCISE PROGRAM (DCCEP); HUMANITARIAN / CIVIC ASSISTANCE (H/CA); PERSONAL EXPENSE (PE) REQUIREMENTS; AND POSSIBLY ASIA PACIFIC REGIONAL INITIATIVE (APRI) FUNDS. USPACOM ALLOCATED FUNDING LEVELS ARE SUBJECT TO REVISION DURING THE EXERCISE JOINT EVENT LIFE CYCLE (JELC) DUE TO POTENTIAL SHIFTING REQUIREMENTS / PRIORITIES WITHIN THE USPACOM JOINT EXERCISE PROGRAM AND AVAILABLE FUNDING. 14.1.1. CONTROLLING AUTHORITIES OF ALL FUNDS WILL ENSURE EXERCISE FUNDS ARE PRUDENTLY DISBURSED AND DO NOT EXCEED ALLOCATED LIMITS. 14.1.2. ALL INDIVIDUAL O&M FUNDED TRAVEL AND PER DIEM COSTS IS THE RESPONSIBILITY OF THE PARENT ORGANIZATION. 14.1.3. U.S. JTF FWD / REAR PECULIAR SUPPORT REQUIREMENTS (OTHER THAN TRAVEL / PER DIEM) WILL BE DETERMINED AND COORDINATED BY THE EA AND APPORTIONED ON A FAIR SHARE BASIS AMONG PARTICIPATING COMPONENTS. 14.2. STRATEGIC LIFT. THE CONTROLLING AUTHORITY FOR STRATEGIC LIFT FUNDS IS USPACOM J7. CG 08 PLANNERS WILL USE $19.725M AS THE TENTATIVE APPROVED STRATEGIC LIFT ALLOCATION. ALLOCATED STRATEGIC LIFT FUNDING FOR CG 08 ARE INCLUSIVE OF ALL FREEDOM BANNER AND PORT HANDLING / INLAND TRANSPORTATION (PH/IT) COSTS ASSOCIATED WITH CG 08. 14.2.1. STRATEGIC LIFT FUNDING FOR MOVEMENT OF PAX AND CARGO WILL ONLY BE PROVIDED TO USPACOM VALIDATED REQUIREMENTS. 14.3. HUMANITARIAN / CIVIC ASSISTANCE (H/CA). THE CONTROLLING AUTHORITY FOR H/CA FUNDS IS THE EA (MARFORPAC). H/CA EXPENSES PAID FROM TITLE 10 H/CA FUNDS ARE THOSE INCURRED AS A DIRECT RESULT OF PROVIDING H/CA. THIS INCLUDES THE COST OF MATERIALS AND SERVICES, IF ANY, WHICH NEED TO BE HIRED FOR H/CA PROJECTS. IT DOES NOT INCLUDE COSTS ASSOCIATED WITH THE MILITARY OPERATION (E.G., TRANSPORTATION, PERSONNEL EXPENSES, PETROLEUM, OIL AND LUBRICANTS, REPAIR OF EQUIPMENT, ETC.). TITLE 10 H/CA MAY NOT BE PROVIDED TO ANY FOREIGN COUNTRY UNLESS THE U.S. SECRETARY OF STATE SPECIFICALLY APPROVES THE PROVISION OF SUCH ASSISTANCE.


14.3.1. ANY OTHER H/CA OR COMMUNITY RELATIONS (COMREL) EVENTS COORDINATED BY OTHER COMMANDS WILL ONLY BE CONDUCTED IF THEY DO NOT INTERFERE WITH THE USPACOM APPROVED H/CA PROJECTS, ARE APPROVED BY THE EA, AND ARE SELF FUNDED. 14.3.2. H/CA FUNDING ALLOCATION WILL BE IDENTIFIED VIA SEPARATE CORRESPONDENCE TO APPROPRIATE COMMANDS. 14.4. DEVELOPING COUNTRIES COMBINED EXERCISE PROGRAM (DCCEP). THE CONTROLLING AUTHORITY FOR DCCEP FUNDS IS THE USPACOM J45. DCCEP COVERS INCREMENTAL EXPENSES INCURRED BY THE HOST NATION. INCREMENTAL EXPENSES ARE THE ADDITIONAL, RESPONSIBLE, AND PROPER COSTS OF GOODS AND SERVICES INCLUDING RATIONS, FUEL, TRAINING AMMUNITION AND TRANSPORTATION THAT ARE CONSUMED BY THE HOST NATION AS A DIRECT RESULT OF THAT COUNTRY'S PARTICIPATION IN CG 08. REQUESTS AND NOMINATIONS FOR DCCEP FUNDING ALLOCATION WILL BE SUBMITTED TO JUSMAGTHAI. FINAL DCCEP DISBURSEMENT WILL BE COORDINATED BY JUSMAGTHAI WITH THE OFFICE OF PRIMARY RESPONSIBILITY FOR DCCEP MANAGEMENT, HQ USPACOM J45. 14.4.1. DCCEP FUNDING ALLOCATION WILL BE IDENTIFIED VIA SEPARATE CORRESPONDENCE TO APPROPRIATE COMMANDS. 14.5. PERSONAL EXPENSE (PE). THE CONTROLLING AUTHORITY FOR PE FUNDS IS USPACOM J45. PE COVERS COSTS ASSOCIATED WITH PARTICIPATION BY DEVELOPING NATIONS IN PLANNING CONFERENCES. PE FUNDING WILL BE COORDINATED BY USPACOM J7 WITH USPACOM J45. 14.5.1. PE FUNDING ALLOCATION WILL BE IDENTIFIED VIA SEPARATE CORRESPONDENCE TO APPROPRIATE COMMANDS. 14.6. EXERCISE RELATED CONSTRUCTION (ERC). THE CONTROLLING AUTHORITY FOR ERC FUNDS IS USPACOM J44. THE FOLLOWING ARE THE APPROVED EXERCISE COBRA GOLD FY 08 ERC PROJECTS: 14.6.1. PC08-03: RENOVATE CLOSE QUARTER BATTLE (CQB) FACILITY, LOP BURI, THAILAND. 14.6.2. PC08-13: UPGRADE FACILITIES, UDORN AIR BASE, THAILAND. 15. FORCE PROTECTION GUIDANCE. 15.1. EA WILL DEVELOP AND PUBLICIZE FP POLICY, PLANS, AND MEASURES TO COVER THE SPECTRUM OF POTENTIAL DANGERS TO U.S. FORCES, WITH A PRIMARY EMPHASIS ON CRIMINAL AND TERRORIST THREATS. 15.2. REF E AND REF F IDENTIFY THE RULES OF ENGAGEMENT (ROE) FOR U.S. FORCES WHILE IN THAILAND. COMMANDERS AT ALL LEVELS WILL ENSURE ALL U.S. FORCES ARE COMPLETELY FAMILIAR WITH BOTH REFERENCES PRIOR TO ANY TRAVEL TO THAILAND. 16. PUBLIC AFFAIRS GUIDANCE. 16.1. THE EA PAO IN COORDINATION WITH THE CTF, UNFHQ, AND ALL PARTICIPATING NATIONS PAO WILL DEVELOP PROPOSED PUBLIC AFFAIRS GUIDANCE (PAG), AND SUBMIT TO USPACOM J01PA NLT 10 MAR 08 FOR APPROVAL. THE PROPOSED PAG WILL BE IAW DODINST 5405.3. USPACOM JO1PA WILL SUBMIT RECOMMENDED CG 08 TO THE JOINT STAFF PAO NLT 17 MAR 08. 17. TIME PHASED FORCE AND DEPLOYMENT DATA (TPFDD) GUIDANCE. 17.1. THE FOLLOWING PROVIDES CG 08 TPFDD GUIDANCE; TPFDD DEVELOPMENT; VALIDATION PROCEDURES; CHANGE PROCEDURES, REDEPLOYMENT PLANNING; AND CLASSIFICATION GUIDANCE. THE DETAILED USPACOM TPFDD LETTER OF INSTRUCTION (LOI) CAN BE FOUND ON THE USPACOM J35 HOMEPAGE LOCATED AT URL: HTTP://WWW2.HQ.PACOM.SMIL.MIL/J3/J35/J354/TOPICS/20040401101450/FINAL_TPFDD_LOI050711.DOC. 17.2. HQ USPACOM IS FULLY COMMITTED TO IMPROVING THE PERSONNEL AUGMENTATION AND MOVEMENT PROCESS IN SUPPORT OF EXERCISES. HISTORICALLY, INACCURATE AND UNTIMELY INFORMATION HAS DIRECTLY IMPACTED EXERCISE SEALIFT AND, MORE CRITICALLY, AIRLIFT PLANNING AND SCHEDULING. 17.3. AREAS REQUIRING IMPROVEMENT INCLUDE: TIMELY INPUT OF DATA INTO JOPES; ACCURACY OF INFORMATION; ADHERENCE TO TIMELINES AND MILESTONES;


CHANGES AFTER VALIDATION; THE UNACCEPTABLE NUMBER OF NO SHOWS; AND ACCOUNTABILITY OF PERSONNEL. THE IMPACT IS PERSONNEL TURBULENCE AND MISUTILIZATION OF SCARCE AIRLIFT RESOURCES TO INCLUDE DEGRADED SUPPORT OF DEPLOYING PERSONNEL AND WASTED USE OF STRATEGIC LIFT FUNDS. 17.4. ALL COMMANDS WILL APPLY AND ENFORCE DISCIPLINE IN IDENTIFYING AND SOURCING ALL REQUIREMENTS AND VALIDATING EXERCISE MOVEMENT DATA IN THE TPFDD BY DIRECTED SUSPENSE DATES. VALIDATION IS DEFINED AS TPFDD RECORDS THAT ACCURATELY REFLECT UNIT READINESS, MOVEMENT DATES, AERIAL AND SEA PORTS OF EMBARKATION / DEBARKATION (APOE / APOD, SPOE / SPOD) AND LEVEL IV PASSENGER AND CARGO DETAILS WITHOUT ERROR. 17.5. TO FACILITATE CG 08 TPFDD COORDINATION, THE FOLLOWING EXERCISE NEWSGROUP, EXERCISE.CG 08.PACOM.PLANS, HAS BEEN ESTABLISHED ON THE USPACOM SERVER LOCATED AT: NEWS.GCCS.PACOM.SMIL.MIL AND IS THE SERVER OF RECORD. THE CG 08 EXERCISE NEWSGROUP IS THE ONLY OFFICIAL COMMUNICATION METHOD OF RECORD. ALL TPFDD ISSUES WILL BE POSTED VIA NEWSGROUPS. 17.6. TPFDD DEVELOPMENT AND SCHEDULING GUIDANCE. 17.6.1. THE JTF COMMANDER IS RESPONSIBLE FOR DEFINING AND PRIORITIZING FORCE REQUIREMENTS SUBJECT TO AVAILABLE LIFT AND FUNDING CONSTRAINTS. SERVICE COMPONENT COMMANDS AND SUPPORTING COMMANDS WILL IDENTIFY ALL TPFDD REQUIREMENTS IN PLAN IDENTIFICATION DATA (PID) 58CGD AND 58CGR IAW PUBLISHED GUIDANCE TO MAXIMIZE EFFICIENCY. 17.6.2. THE FOLLOWING ULN CODE STRUCTURE WILL BE UTILIZED FOR DEVELOPING ULNS: FIRST/SECOND CHARACTER OF ULN ORGANIZATION H (A-H) USPACOM H (J-Z) JTF / SUBUNIFIED K USARPAC L ` PACAF M MARFORPAC N PACFLT J SOCPAC G USTRANSCOM 17.7. ALL EAD / LAD WINDOWS WILL BE A MINIMUM OF THREE (3) DAYS FOR AIRLIFT AND SIX (6) DAYS FOR SEALIFT. 17.8. ALL HAWAII BASED ULNS WILL USE HICKAM AFB AS THEIR APOE AND PEARL HARBOR AS THE SPOE. 17.9. APOE / APOD RESTRICTIONS: CRITERIA FOR CONSIDERATION OF OPENING AN ADDITIONAL APOE ARE 100 PAX / 15 STONS OF PERSONNEL/EQUIPMENT FOR STRATEGIC LIFT AND 30 PAX / 5 STONS FOR INTRATHEATER LIFT. ADDITIONAL APOES WILL ONLY BE ESTABLISHED BY USPACOM. FOR INITIAL PLANNING PURPOSES, THE FOLLOWING APOES / APODS ARE AUTHORIZED FOR CG 08: MCCHORD AFB, MARCH ARB, HICKAM AFB, ANDERSEN AFB, KADENA AB, YOKOTA, IWAKUNI MCAS, ELMENDORF AFB, SCOTT AFB, UTAPHAO THAILAND, KORAT THAILAND. APOES / APODS WILL BE FURTHER REFINED AS THE PLANNING CYCLE PROGRESSES. 17.10. SEALIFT MOVEMENT CONSIDERATIONS. 17.10.1. APPROVED SPOE / SPOD FOR DEPLOYMENT: TACOMA, PEARL HARBOR, TENGAN PIER (AMMO ONLY), NAHA, SASEBO, CHUK SAMET (ALL CARGO EXCEPT AMMO), THUNG PRONG (AMMO ONLY) AND APRA GUAM FOR NAVFOR ONLY. SPOE / SPOD WILL BE FURTHER REFINED AS THE PLANNING CYCLE PROGRESSES. 17.10.2. UNITS WILL VALIDATE SEALIFT DEPLOYMENT MOVEMENT WINDOWS BASED ON LAD AND IAW WITH THE USPACOM TPFDD LOI. AFTER VALIDATION, MSC / SDDC WILL RECOMMEND CHANGES BASED ON AVAILABILITY OF SEALIFT. 17.11. TENTATIVE AIRLIFT WINDOWS. 17.11.1. TENTATIVE DEPLOYMENT MOVEMENT WINDOWS ARE AS FOLLOWS:


C100 (EAD) - C103 (LAD): ADVON 1 C111 (EAD) - C113 (LAD): ADVON 2 C120 (EAD) - C122 (LAD): MAIN BODY 1 C125 (EAD) - C127 (LAD): MAIN BODY 2 (RESERVES HAVE PRIORITY) 17.11.2. TENTATIVE REDEPLOYMENT MOVEMENT WINDOWS ARE AS FOLLOWS: C143 (RLD) - C143 (ALD) – C143 (EAD) – 145 (LAD): AIR MAIN BODY 1 (RESERVES HAVE PRIORITY) (FOR AIR REDEPLOYMENT MAIN BODY 1 ONLY, THE RLD AND ALD WILL BE THE SAME C-DAY: C143) C146 (ALD) - C147 (EAD) - C149 (LAD): MAIN BODY 2 C1552 (ALD) - C153 (EAD) - C155 (LAD): REAR PARTY 1 C157 (ALD) - C158 (EAD) - C160 (LAD): REAR PARTY 2 17.12. THE INITIAL SEALIFT DEPLOYMENT EAD / LAD WINDOW WILL BE C110 - C115 AND MAY BE REFINED AS PLANNING PROGRESSES. THE INITIAL SEALIFT REDEPLOYMENT ALD WILL BE 149 AND MAY BE REFINED AS PLANNING PROGRESSES. 17.13. VALIDATION CHECKLIST. AT A MINIMUM, THE VALIDATING COMMAND WILL ENSURE THE FOLLOWING ITEMS ARE ACCURATE PRIOR TO VALIDATION: AIR EAD = ALD + 1. SEA EAD = ALD + 2 LOAD + TRANSIT TIME. AIR LAD = EAD + 2. SEA (INTERTHEATER) LAD = EAD + 6. SEA (INTRATHERATER) LAD = EAD + 4. MOVEMENT WINDOW IS APPROVED. POE IS APPROVED. POD IS APPROVED. ALL INFORMATION REQUEST WITHIN POC PULL DOWN MENU FILLED IN. BASELINE POC MUST HAVE IN-DEPTH KNOWLEDGE OF ULN INFORMATION. INDIVIDUAL AUGMENT ULN’S MUST BE SOURCED PRIOR TO JTF VALIDATION TO USPACOM (INDIVIDUAL AUGMENT NAME FILLING BILLET MUST BE FILLED IN). UIC IS NOT A MISCELLANEOUS CODE. LEVEL 4 DETAIL EXISTS FOR ALL CARGO ULNS. LEVEL 4 DETAIL AGREES WITH LEVEL 2 DETAIL FOR ALL CARGO ULNS. THE CEI FIELD IS COMPLETED WITH THE LETTER A, G OR R TO INDICATE ACTIVE, GUARD OR RESERVE COMPONENT. EACH ULN CONTAINED IN REDEPLOYMENT PID EXISTS IN DEPLOYMENT PID. 17.13.1. RESOLVE DISCREPANCIES REVEALED BY COMPARISON CHECK BETWEEN DEPLOYMENT AND REDEPLOYMENT PIDS (APPLIES TO REDEPLOYMENT VALIDATIONS ONLY). 17.14. TPFDD CHANGE PROCEDURES. CHANGES DESCRIBED IN THIS PARA REFER TO TPFDD CHANGES AFTER USPACOM HAS VALIDATED THE TPFDD TO USTRANSCOM. CHANGES TO VALIDATED REQUIREMENTS WILL BE MINIMIZED TO AVOID OPERATIONAL DISRUPTIONS. CHANGE PARAMETERS AND PROCEDURES ARE OUTLINED IN THE USPACOM TPFDD LOI. 17.15. TPFDD CLASSIFICATION GUIDANCE: INFORMATION RELATED TO THE CG 08 TPFDD IS CONFIDENTIAL//RELEASABLE COBRA GOLD 08 (C//REL CG 08) AND MAY NOT BE DISCLOSED OR DISSEMINATED TO NON-EXERCISE PARTICIPANTS WITHOUT APPROVAL OF USPACOM J7. 17.16. COBRA GOLD 08 TPFDD POC’S: 17.16.1. USPACOM J712 TPFDD NCO: MSGT ROSALDO, J712, DSN: 477-8249. 17.16.2. USPACOM J35 OPT / DMT TPFDD COORDINATOR: MSGT LASKER, J35, DSN: 477-9151. 18. CLASSIFICATION GUIDANCE. 18.1. TERM DEFINITIONS. 18.1.1. CLASSIFIED MILITARY INFORMATION (CMI). CLASSIFIED MILITARY INFORMATION REQUIRING PROTECTION IN THE INTERESTS OF NATIONAL SECURITY ARE LIMITED TO THREE CLASSIFICATIONS: TOP SECRET, SECRET, AND CONFIDENTIAL, AS DESCRIBED IN EXECUTIVE ORDER 12958. SEE ALSO DOD 5200.1 AND 5230.11 AT WWW.DTIC.MIL WEBSITE FOR


ADDITIONAL INFORMATION ON CLASSIFICATION GUIDANCE AND DISCLOSURE POLICY. 18.1.2. DISCLOSURE. ORAL DISCUSSION OR VISUAL DISPLAY OF CMI. 18.1.3. DISCLOSURE AUTHORITY. AN OFFICIAL, SPECIFICALLY DESIGNATED IN WRITING, WHO MAY DISCLOSE OR DENY CMI. 18.1.4. RELEASE. THE GIVING UP, RELINQUISHMENT, DISSEMINATION, OR PHYSICAL TRANSFER OF CMI TO AN AUTHORIZED REPRESENTATIVE OF A FOREIGN GOVERNMENT FOR RETENTION. 18.2. DISCLOSURE CRITERIA. DISCLOSURES MAY BE AUTHORIZED ONLY BY U.S. OFFICIALS WHO HAVE BEEN DELEGATED AUTHORITY TO DISCLOSE CMI AND THEN ONLY FOR THAT INFORMATION FOR WHICH THEY HAVE BEEN GIVEN AUTHORITY. 18.3. BLANKET RELEASE OF CMI OR FOREIGN ACCESS TO U.S. ONLY SYSTEMS IN CONJUNCTION WITH EXERCISE CG 08 IS NOT AUTHORIZED. CMI MATERIALS DISCLOSED OR PHYSICALLY TRANSFERRED (I.E., RELEASED TO FOREIGN NATIONALS) MUST BE REVIEWED AND APPROVED BY A FOREIGN DISCLOSURE OFFICER BEFORE TRANSFER TO THE FOREIGN RECIPIENT THROUGH APPROVED FOREIGN DISCLOSURE CHANNELS. 18.4. FOREIGN NATIONALS WILL NOT BE GIVEN ACCESS TO SYSTEMS WHICH ARE U.S. ONLY OR WHICH REQUIRE INTERFACE WITH U.S. ONLY SYSTEMS AND NETWORKS (SUCH AS TBMCS, JDISS, SIPRNET, ETC). PROPOSALS TO OBTAIN SPECIAL AUTHORIZATION MUST BE REQUESTED VIA APPROPRIATE CHANNELS WITH A FULL EXPLANATION OF THE REQUIREMENT AND SECURITY SAFEGUARDS THAT WOULD PREVENT INADVERTENT DISCLOSURE OF CMI. SHOULD COMBINED OPERATIONS WITH OR NEARBY THESE U.S. ONLY SYSTEMS AND NETWORKS BE GRANTED, ONLY THAT CMI PREVIOUSLY APPROVED FOR DISCLOSURE AND/OR RELEASE IS AUTHORIZED. REQUESTS FOR FOREIGN ACCESS TO U.S. ONLY SYSTEMS MUST BE SUBMITTED AS EARLY AS POSSIBLE, BUT NLT THAN NINETY DAYS PRIOR TO STARTEX, THROUGH COMMAND FDO OFFICE. SUBMISSION OF A REQUEST DOES NOT GUARANTEE APPROVAL. 19. COORDINATING INSTRUCTIONS. 19.1. THE FOLLOWING ARE THE REMAINING KEY EXERCISE MILESTONES, EVENT LOCATIONS, AND OFFICE OF PRIMARY RESPONSIBILITY (OPR) FOR CG 08: 19.1.1. 14 NOV 07: SUBMIT CG 08 AUGMENTEE REQUIREMENTS AND REPORTING INSTRUCTION TO USPACOM J132, (U.S. EXECUTIVE AGENT). 19.1.2. 19 -21 NOV 07: EVENT TEST #1 (BY INVITATION ONLY), CAMP SMITH, HAWAII, (USPACOM J73). 19.1.3. 26 NOV 07: USPACOM J132 TASKS USPACOM COMPONENTS TO FILL CG 08 INDIVIDUAL AUGMENTEE REQUIREMENTS, ISSUES RECLAMA GUIDANCE, AND ISSUES INDIVIDUAL AUGMENTEE REPORTING INSTRUCTIONS, (USPACOM J132). 19.1.4. 5 DEC 07: BASIC CONCEPT BRIEF TO USPACOM J7, CAMP SMITH, HAWAII, (U.S. EXECUTIVE AGENT). 19.1.5. 8 - 10 JAN 08: TPFDD (FORCE FLOW) WORKSHOP, (BY INVITATION ONLY), CAMP SMITH, HAWAII (U.S. JTF). 19.1.6. 22 JAN 08: U.S. JTF PRE-VALIDATES ENTIRE TPFDD (DEPLOYMENT / REDEPLOYMENT) TO USPACOM J7, (U.S. JTF). 19.1.7. 1 FEB 08: USPACOM VALIDATES ENTIRE TPFDD (DEPLOYMENT / REDEPLOYMENT) TO USTRANSCOM, (USPACOM J35). 19.1.8. 4 - 8 FEB 08: FINAL SITE SURVEY (BY INVITATION ONLY), VARIOUS LOCATIONS, THAILAND, (U.S. EXECUTIVE AGENT). 19.1.9. 11 - 15 FEB 08: FINAL PLANNING CONFERENCE (FPC), (BY INVITATION ONLY), BANGKOK, THAILAND, (U.S. EXECUTIVE AGENT). 19.1.10. 16 - 17 FEB 08: MSEL SYNCHRONIZATION WORKSHOP, (BY INVITATION ONLY), BANGKOK, THAILAND, (JWFC). 19.1.11. 25 FEB 08: DETAILED CONCEPT BRIEF TO USPACOM J7, CAMP SMITH, HAWAII, (U.S. EXECUTIVE AGENT). 19.1.12. 10 MAR 08: SUBMIT PROPOSED PUBLIC AFFAIRS GUIDANCE (PAG) TO USPACOM J01PA, (U.S. EXECUTIVE AGENT). 19.1.13. 17 MAR 08: SUBMIT PAG TO JOINT STAFF,(USPACOM J01PA).


19.1.14. 2 APR 08: CRITICAL CANCELLATION DATE (JOINT STAFF). 19.1.15. 7 APR 08: EXERCISE CG 08 VISITOR POLICY MESSAGE PUBLISHED, (U.S. EXECUTIVE AGENT). 19.1.16. 14 - 18 APR 08: EVENT TEST #2 (BY INVITATION ONLY), CAMP SMITH, HAWAII, (USPACOM J73). 19.1.17. 21 APR - 21 MAY 08: CG 08 HUMANITARIAN / CIVIC ACTION (H/CA) PROJECTS CONDUCTED, (BY INVITATION ONLY), VARIOUS LOCATIONS, THAILAND, (U.S. JTF). 19.1.18. 6 - 8 MAY 08: EVENT TEST #3, (BY INVITATION ONLY), SATTAHIP, THAILAND, (USPACOM J731). 19.1.19. 8 MAY 08: CG 08 OPENING CEREMONY, (BY INVITATION ONLY), KORAT, THAILAND, (RTSC J7). 19.1.20. 8 - 10 MAY 08: CG 08 ACADEMICS / COMMEX / MINIEX, (BY INVITATION ONLY), VARIOUS LOCATIONS, THAILAND, (CTF / UNFHQ). 19.1.21. 8 - 21 MAY 08: CG 08 FTX, (BY INVITATION ONLY), VARIOUS LOCATIONS, THAILAND, (CTF / UNFHQ). 19.1.22. 11 - 21 MAY 08: CG 08 CPX, (BY INVITATION ONLY), KORAT, THAILAND, (CTF / UNFHQ). 19.1.23. 21 MAY 08: CG 08 HUMANITARIAN / CIVIC ACTION (H/CA) PROJECTS DEDICATION, (BY INVITATION ONLY), VARIOUS LOCATIONS, THAILAND, (RTSC J7). 19.1.24. 21 MAY 08: CG 08 CTF AFTER ACTION REVIEW (AAR), KORAT, THAILAND, (CTF / UNFHQ). 19.1.25. 21 MAY 08: CG 08 CLOSING CEREMONY, (BY INVITATION ONLY), KORAT, THAILAND, (RTSC J7). 19.1.26. 16 JUN 08: U.S. JTF COMMANDER JOINT QUICK LOOK REPORT DUE TO CDR, USPACOM, CAMP SMITH, HAWAII (U.S. JTF). 19.1.27. 23 JUN 08: USPACOM COMPONENTS SUBMIT JOINT LESSONS LEARNED AND ISSUES TO EA, (U.S. EXECUTIVE AGENT). 19.1.28. 30 JUN 08: COMPILED USPACOM COMPONENTS JOINT LESSONS LEARNED AND ISSUES SUBMITTED TO USPACOM, (U.S. EXECUTIVE AGENT). 19.2. MODIFICATIONS TO THE CG 08 PLANNING MILESTONES MAY BECOME NECESSARY DURING THE JELC. ANY MODIFICATIONS TO MILESTONES WILL BE PROMULGATED VIA THE EXERCISE APAN WEBSITE. 19.3. TRAINING AUDIENCES WILL USE THE JOINT TRAINING INFORMATION MANAGEMENT SYSTEM (JTIMS) TO FACILITATE TRAINING OBJECTIVE AND MASTER SCENARIO EVENT LIST (MSEL) MANAGEMENT. 19.4. U.S. PERSONNEL ATTENDANCE CONTROL MEASURES INCLUDE USING A SINGLE POC COUNTRY CLEARANCE AUTHORIZATION MESSAGE BY THE U.S. EA FOR ALL COBRA GOLD RELATED CONFERENCES, SURVEYS, WORKSHOPS, MEETINGS, AND EXERCISE ATTENDEES. CHJUSMAGTHAI WILL NOT APPROVE ANY COBRA GOLD RELATED COUNTRY / AREA CLEARANCE REQUESTS SUBMITTED BY ANY OTHER COMPONENT, AGENCY, OR INDIVIDUAL. 20. POINTS OF CONTACT. COMMAND NAME DSN COM USPACOM (J712) STEVE MELLINGER 477-8238 808-477-8238 (USPACOM PRIMARY COBRA GOLD EXERCISE PLANNER) USPACOM (J712) MAJ JAMES FALEAFINE 477-8232 808-477-8232 (USPACOM ALTERNATE COBRA GOLD EXERCISE PLANNER) MARFORPAC GS 13 CHRIS MOHR 477-8540 808-477-8540

(U.S. EXECUTIVE AGENT PRIMARY COBRA GOLD EXERCISE PLANNER) MARFORPAC GS 14 WADE YOFFEE 477-8539 808-477-8539

(U.S. EXECUTIVE AGENT ALTERNATE COBRA GOLD EXERCISE PLANNER)


Intentionally Blank

Enclosure (7) ENC (7)-1

Enclosure (7): Initiating Directive MSG (Example)

142025Z NOV 07 HQ USPACOM J7(SC) TO COMMARFORPAC(sc) AIG 8705 ADFWC HQJOC CC COMPACFLT PEARL HARBOR HI CDR USPACOM HONOLULU HI(SC) PACAF CV(SC) COMSOCPAC HONOLULU HI(SC) JOINT STAFF WASHINGTON DC HQ USAF WASHINGTON DC CNO WASHINGTON DC(SC) CDR USSOCOM(MC) HQ USSTRATCOM(SC) CDR USJFCOM NORFOLK VA(MC) DA WASHINGTON DC AMC CC(SC) CG III MEF(sc) COMSEVENTHFLT ICORPS G3(SC) CTF 70 CTF 72 CTF 73 USDAO CANBERRA ACT AS CMC WASHINGTON DC(sc) HQ USPACOM J1(SC) HQ USPACOM J2(SC) HQ USPACOM J3(SC) HQ USPACOM J4(SC) HQ USPACOM J5(SC) HQ USPACOM J6(SC) HQ USPACOM J8(SC) HQ USPACOM(SC) HQ USPACOM SJFHQ(SC) USARPAC ACC(SC) CDR USTRANSCOM(SC) CDRFORSCOM CMD CTR FT MCPHERSON GA CG 3RD MARDIV(sc) HICKAM AFB HI BDP(SC) EWTGPAC SAN DIEGO CA(SC) JIOC J8(SC) CTF 74 CTF 76 MARITIME ADMIN WASHINGTON DC ISSO FALLS CHURCH VA UNCLASSIFIED// FM HQ USPACOM HONOLULU HI TO AIG 8705 COMMARFORPAC ADFWC HQJOC


INFO CDR USPACOM HONOLULU HI COMPACFLT PEARL HARBOR HI USARPAC ACC DCDR PACAF HICKAM AFB HI COMSOCPAC HONOLULU HI JOINT STAFF WASHINGTON DC HQ USAF WASHINGTON DC CNO WASHINGTON DC CDR USSOCOM HQ USSTRATCOM CDR USJFCOM NORFOLK VA DA WASHINGTON DC CDR USTRANSCOM CDRFORSCOM CMD CTR FT MCPHERSON GA AMC CC CG III MEF CG 3RD MARDIV COMSEVENTHFLT HICKAM AFB HI BDP ICORPS G3 EWTGPAC SAN DIEGO CA JIOC CTF 70 CTF 72 CTF 73 CTF 74 CTF 76 USDAO CANBERRA ACT AS MARITIME ADMIN WASHINGTON DC ISSO FALLS CHURCH VA CMC WASHINGTON DC HQ USPACOM HONOLULU HI/J1/J2/J3/J4/J5/J6/J8/J01PA/J06/J07 SJFHQ HONOLULU HI BT UNCLASSIFIED// MSGID/GENADMIN/USPACOM J7// SUBJ/EXERCISE TALISMAN SABER 2009 (TS 09) INITIATING DIRECTIVE// REF/A/DOC/USPACOM/310707// REF/B/DOC/USPACOM/240707// REF/C/DOC/USPACOM/010206// REF/D/DOC/USPACOM/010206// NARR/REF A IS HQ US PACIFIC COMMAND (HQ USPACOM) PACIFIC JOINT TRAINING STRATEGY. REF B IS USPACOM INSTRUCTION 0508.2A, USPACOM JOINT EXERCISE PROGRAM. REF C IS USPACOM INSTRUCTION 0029.1, JOINT TASK FORCE CERTIFICATION PROGRAM. REF D IS USPACOM INSTRUCTION 0509.1, JOINT LESSONS LEARNED AND ISSUE RESOLUTION PROGRAM// RMKS/1. PURPOSE: TO PROVIDE GUIDANCE AND ASSIGN RESPONSIBILITIES FOR INITIAL PLANNING FOR TS 09. 2. EXERCISE DATES: ALL DATES IN THIS MESSAGE REFERENCE HAWAII TIME UNLESS OTHERWISE INDICATED. EXERCISE DATES 6 JUL 2009 - 26 JUL 2009 A. INCLUSIVE DATES: 1 JUN 2009 - 31 AUG 2009 B. EMPLOYMENT DATES: 6 JUL 2009 - 26 JUL 2009 C. CRITICAL CANCELLATION DATE: 21 APR 2009 3. EXERCISE GOALS, OBJECTIVES AND STRATEGIC COMMUNICATION MESSAGE: A. OVERALL EXERCISE GOAL: TO IMPROVE U.S./AUSTRALIAN COMBAT TRAINING, READINESS AND INTEROPERABILITY.


(1) TALISMAN SABER 09 IS A USPACOM TIER II EXERCISE THAT EXERCISES COMMANDER III MARINE EXPEDITIONARY FORCE (III MEF) AND STAFF AS A COMBINED TASK FORCE (CTF) IN A SHORT WARNING, POWER PROJECTION, FORCIBLE ENTRY SCENARIO, IN ORDER TO CERTIFY III MEF AS A USPACOM JTF CAPABLE HQ. IT IS CDR USPACOM NUMBER 1 PRIORITY EXERCISE IN FY 09. (2) TS 09 WILL OCCUR IN THE MARITIME AREAS OF THE CORAL SEA AND ARAFURA SEA (TBC), AND AT AUSTRALIAN GAZETTED RANGES: SHOALWATER BAY TRAINING AREA (SWBTA), BRADSHAW FIELD TRAINING AREA (BFTA), TOWNSVILLE FIELD TRAINING AREA (TFTA), AND DELAMARE RANGE FACILITY (DRF). TS 09 WILL BE A SINGLE EXERCISE (6-26 JUL 09) WHICH INCORPORATES A COMBINED COMMAND POST EXERCISE (CPX) AND A COMBINED FIELD TRAINING EXERCISE (FTX) WITH FORCE-ON-FORCE EXERCISE AND INTEGRATED COMBINED ARMS LIVE-FIRE EXERCISES (LFX). SERIALIZED LFX WILL OCCUR DURING FORCE INTEGRATION TRAINING (FIT) AND WORK UP TRAINING. TACTICAL LXF WILL BE INTEGRATED INTO THE FTX (16-25 JUL 09). TS 09 WILL MAKE MAXIMUM USE OF LIVE, VIRTUAL, AND CONSTRUCTIVE SIMULATION SUPPORT VIA JTEN/DTEN. CURRENT TS 09 DRAFT CONCEPT INCORPORATES A PROPOSED BUT NOT RESOURCED U.S. ARMY AIRBORNE BATTALION STRATEGIC AIR DROP (SAD). B. KEY EXERCISE OBJECTIVES: (1) CONDUCT CTF TRAINING AND A CULMINATING CAPSTONE EVENT FOR CERTIFICATION OF III MEF HEADQUARTERS (JTF 505) AS A USPACOM JTF IAW REF C. (2) ADVANCE U.S./AS MILITARY-TO-MILITARY RELATIONSHIP AND INTEROPERABILITY. (3) PLAN AND EXECUTE STRATEGIC AIR AND SEA MOVEMENT OF U.S. AUGMENTING FORCES USING THE JOINT OPERATION PLANNING AND EXECUTION SYSTEM (JOPES). (4) EXERCISE U.S./AS C4I INTEROPERABILITY AND CONNECTIVITY UTILIZING THE CENTRIX-4 EYES (CFE) AND COMMON SIPRNET DOMAIN (CSD) NETWORKS. (5) EXERCISE COMBINED PLANNING AND OPERATIONS BY UTILIZING THE JOINT TASK FORCE SOP (JTF SOP) AND MULTINATIONAL FORCE SOP (MNF SOP). (6) EXERCISE A COMBINED FORCE AIR COMPONENT COMMANDER (CFACC) AND COMBINED AIR OPERATIONS CENTER (CAOC). (7) INCORPORATE INTELLIGENCE, SURVEILLANCE, AND RECONNAISSANCE (ISR) TECHNOLOGIES WITH EMPHASIS ON 'SENSOR TO COMMANDER/SHOOTER'. (8) INCORPORATE STRATEGIC, OPERATIONAL, AND TACTICAL LEVEL INTELLIGENCE ANALYSIS AND DISTRIBUTION AT THE TS AND SECRET LEVELS. (9) INCORPORATE MATURE EXPERIMENTATION / TRANSFORMATION INITIATIVES IN ACCORDANCE WITH ENCLOSURE 4 (JOINT EXPERIMENTATION) TO TAB A TO ANNEX B OF REF A. (8) INCORPORATE MATURE TECHNOLOGY EXPERIMENTATION AND DEMONSTRATION INITIATIVES. (9) INCORPORATE KEY AS-U.S. JOINT COMBINED TRAINING CENTRE (JCTC) CAPABILITY PROOF OF CONCEPT / INITIAL OPERATIONAL CAPABILITY. (10) INCORPORATE INTELLIGENCE, SURVEILLANCE, AND RECONNAISSANCE (ISR) TECHNOLOGIES WITH EMPHASIS ON 'SENSOR TO COMMANDER/SHOOTER'. (10) INCORPORATE STRATEGIC, OPERATIONAL, AND TACTICAL LEVEL INTELLIGENCE ANALYSIS AND DISTRIBUTION AT THE TS AND SECRET LEVELS. (11) CONDUCT A SAFE, ACCIDENT FREE EXERCISE. C. STRATEGIC COMMUNICATION: (1) DRAFT STRATEGIC END STATE OBJECTIVE: TO ASSURE ALLIES AND PARTNERS OF U.S. -AS CAPABILITY. (2) DRAFT STRATEGIC COMMUNICATION THEMES: (A) THE U.S. IS COMMITTED TO REGIONAL SECURITY, PEACE AND STABILITY (C) THE AS - U.S. MILITARIES ARE FLEXIBLE AND READY (D) THE AS - U.S. MILITARIES ARE INTEROPERABLE (E) AS - U.S. CONTINUE TO SUPPORT THE WAR AGAINST TERRORISM (3) DRAFT STRATEGIC COMMUNICATION MESSAGES: (A) AS - U.S. ALLIANCE REMAINS A MODEL IN THE ASIA PACIFIC REGION (B) THE U.S. APPRECIATES ACCESS TO AS PORTS, AIRFIELDS AND TRAINING AREAS


(C) THE U.S. IS COMMITTED TO ITS PARTNER NATIONS, THE REGION, REGIONAL PEACE AND STABILITY (D) AS - U.S. MILITARY INCREASED INTEROPERABILITY, FLEXIBILITY AND READINESS IS A FORCE MULTIPLIER TO WIN THE WAR ON TERROR (E) AS - U.S. MILITARY TECHNOLOGY SHARING IS A COMBINED EFFORT TO COUNTER ADVERSARY TACTICS, TECHNIQUES, AND PROCEDURES (F) THE AS - U.S. RELATIONSHIP IS CORNERSTONE OF REGIONAL STABILITY 4. EXERCISE PARTICIPANTS: A. PRIMARY TRAINING AUDIENCE: III MEF AS AN OPERATIONAL LEVEL COMBINED TASK FORCE AUGMENTED BY AUSTRALIAN DEFENCE FORCE (ADF) PERSONNEL. B. SECONDARY TRAINING AUDIENCE: CTF FUNCTIONAL COMPONENTS. C. PARTICIPATING COMMANDS: (1) U.S. COMMANDS: (A) USPACOM (B) JFCOM (C) USTRANSCOM (B) COMMARFORPAC (C) COMPACFLT (D) COMPACAF (E) COMUSARPAC (F) COMSOCPAC (2) AUSTRALIA COMMANDS: (A) HQ JOC (B) ADFWC (C) LAND COMMAND (D) FLEET COMMAND (E) AIR COMMAND (F) SOHQ D. OBSERVERS: TO BE DETERMINED E. PER REF D, HQ USPACOM WILL PARTICIPATE WITH AN APPROPRIATE SIZED ELEMENT TO PROVIDE THE TIER 1 OVERSIGHT AND REPLICATION. 5. TALISMAN SABER 09 COMBINED EXERCISE PLANNING GROUP: A. USPACOM EXERCISE DIRECTOR REVIEWER: USPACOM DEPUTY COMMANDER. B. AUSTRALIAN OFFICER SCHEDULING THE EXERCISE (OSE): AS CHIEF OF DEFENCE FORCE (CDF). C. AUSTRALIAN OFFICER CONDUCTING THE EXERCISE (OCE): CHIEF JOINT OPERATIONS (CJOPS) D. TALISMAN SABER 09 EXECUTIVE AGENTS RESPONSIBLE FOR THE PLANNING, PREPARATION, AND EXECUTION OF THE EXERCISE. (1) U.S. EXECUTIVE AGENT (EA): COMMARFORPAC (2) AS EXECUTIVE AGENT: COMMANDANT AUSTRALIAN DEFENCE FORCE WARFARE CENTER E. OTHER PLANNING GROUP MEMBERS: (1) PRIMARY AND SECONDARY TRAINING AUDIENCE. (2) SUPPORTED COMMANDER (FOR EXECUTION): COMMARFORPAC. (3) SUPPORTING COMMANDS PER PARA 6.C. (4) PARTICIPATING COMMANDS PER PARA 4.C. (5) USPACOM J1/J2/J3/J4/J5/J6/J7/J8/J01PA/J06/J07. F. THE EA WILL ESTABLISH A COMBINED EXECUTIVE STEERING GROUP (CESG) FOR PLANNING CONSISTING OF: MARFORPAC, ADFWC, III MEF, USPACOM J712, AND HQ JOC J70. G. SPECIFIC EXECUTIVE AGENT RESPONSIBILITIES: (A) ENSURE ALL REQUIRED EXERCISE MEETINGS, WORKSHOPS, AND CONFERENCES ARE CONDUCTED AT LOCATIONS APPROPRIATE TO THE PARTICIPATING AUDIENCE. PREPARE DETAILED AGENDAS AND COORDINATE ADMINISTRATIVE REQUIREMENTS. (B) WITH APPROPRIATE PARTICIPANTS, DEVELOP, COORDINATE, PREPARE AND DISTRIBUTE EXERCISE DOCUMENTS, TO INCLUDE: THE U.S. EXERCISE


DIRECTIVE, EXERCISE PLAN (EXPLAN), EXERCISE CONTROL PLAN, SIGNIFICANT MILITARY EXERCISE BRIEF (SMEB), PROPOSED PUBLIC AFFAIRS GUIDANCE (PPAG), FORCE FLOW (TPFDD) AND ANY OTHER SUPPORTING DOCUMENTS AS REQUIRED. (C) ASSIST THE CTF (III MEF), WHEN APPLICABLE, IN THE DEVELOPMENT OF THE CTF COMBINED MANNING DOCUMENT (CMD) AND BATTLE ROSTER (PER REF C) AND EXERCISE SUPPORT REQUIREMENTS FOR SUBMISSION TO THE SERVICE COMPONENTS. (D) ASSIST THE JTF COMMANDER IN PREPARING AND PROVIDING THE JTF CERTIFICATION PROPOSAL TO USPACOM DEPUTY CDR AND COMMANDER PER REF C. (E) PRESENT THE BASIC AND DETAILED CONCEPT BRIEFS TO HQ USPACOM EXERCISE DIRECTOR IAW REF B. (F) CONSOLIDATE COUNTRY CLEARANCE REQUESTS AND FORWARD TO APPROPRIATE AGENCIES IN ACCORDANCE WITH INSTRUCTIONS INCLUDED IN DOD INSTRUCTION 4500.54, FOREIGN AREA CLEARANCE GUIDE. (G) ESTABLISH A COMBINED EXERCISE PLANNING GROUP. MEMBERS WILL INCLUDE REPRESENTATIVES FROM ALL USPACOM SERVICE COMPONENTS AND APPROPRIATE GOVERNMENT AGENCIES AND SPECIALTIES. THE PRIMARY FUNCTIONS OF THIS GROUP WILL BE TO COORDINATE EXERCISE PLANNING, PROVIDE QUALITY CONTROL, MONITOR SCENARIO DEVELOPMENT, AND PERFORM OTHER PLANNING TASKS AS NECESSARY. (H) DEVELOP AND IMPLEMENT FORCE PROTECTION POLICIES, PLANS AND MEASURES FOR THE EXERCISE. (I) PROVIDE EXERCISE FUNDING GUIDANCE. OBTAIN, CONTROL AND DISBURSE SERVICE INCREMENTAL FUNDS (SIF) AS NECESSARY. ENSURE EXERCISE REMAINS WITHIN FISCAL GUIDANCE. (J) PROVIDE OVERSIGHT FOR JFCOM/JOINT WARFIGHTING CENTER (JWFC) INTEGRATION (SIM/TECH SUPPORT, SENIOR CONTROL, MSEL MANAGEMENT, AAR/MEDIA SUPPORT) INTO THE COMBINED EXERCISE CONTROL GROUP. (K) COLLECT, REVIEW AND FORWARD TO USPACOM J7 APPROPRIATE JOINT LESSONS LEARNED AND THOSE ISSUES REQUIRING RESOLUTION AT USPACOM LEVEL PER REF D. SUBMISSIONS WILL BE MADE VIA THE USPACOM JOINT LESSONS LEARNED COLLECTION TOOL NLT 26 SEP 09. (M) PERFORM OTHER TASKS AS DIRECTED BY THE EXERCISE DIRECTOR. 6. TALISMAN A. EXERCISE DIRECTORS: (1) USPACOM EXERCISE SABER 09 EXECUTION COMMAND RELATIONSHIPS: DIRECTOR: USPACOM DEPUTY COMMANDER (2) AUSTRALIAN EXERCISE DIRECTOR: COMMANDANT ADF WARFARE CENTRE (ADFWC) B. SUPPORTED COMMANDER: COMMARFORPAC C. SUPPORTING COMMANDER: SEE PARAGRAPH 4C(1). COMPLETE FORCE LIST WILL BE PROMULGATED IN THE EXERCISE DIRECTIVE. D. SCENARIO ORDER OF BATTLE (OOB) AND C2 WILL BE SPECIFIED IN CONCEPT BRIEFS. 7. JTF CERTIFICATION: EXERCISE TALISMAN SABER 09 WILL SERVE AS THE CAPSTONE EVENT FOR CERTIFICATION OF HQ III MEF AS A JTF CAPABLE HQ 8. STRATEGIC LIFT BUDGET: (TBD) A. AIRLIFT: (PROJECTED) $18M (1) TALISMAN SABER: TBD (2) STRATEGIC AIR DROP: TBD B. SEALIFT: (PROJECTED) TALISMAN SABER: (PROJECTED) 77 RO/RO DAYS/$4.428M C. PORT HANDLING/INLAND TRANSPORTATION (PH/IT): TBD D. FUNDING LEVELS IN PARAS 8A - 8C ARE ESTIMATES. FINAL PRELIMINARY STRATLIFT FUNDING FOR FY 09 IS EXPECTED IN NOVEMBER 2008, SUBJECT TO CHANGE. 9. COORDINATING INSTRUCTIONS: A. EXERCISE MILESTONES: (1) USPACOM PUBLISHES THE INITIATING DIRECTIVE: 9 NOV 08. (2) TRAINING OBJECTIVE WORKSHOP: 3-4 DEC 07, CAMP SMITH, HAWAII. (3) CONCEPT DEVELOPMENT CONFERENCE: 5-7 DEC 07, CAMP SMITH, HAWAII. (4) MASTER SCENARIO EXERCISE LIST (MSEL) DEVELOPMENT CONFERENCE: 10-11 DEC 07, CAMP SMITH, HAWAII.


(5) SCENARIO DESIGN WORKSHOP (SDW): 10-11 DEC 07, CAMP SMITH, HAWAII. (6) EA BRIEFS BASIC CONCEPT TO USPACOM J7 AND USPACOM J01: 10 MAR 08. (7) BRADSHAW FIELD TRAINING AREA (BFTA) AMPHIBIOUS SURVEY: 26 MAY - 6 JUN 08. (8) INITIAL SITE SURVEY (ISS): 7-11 JUL 08 IN AUSTRALIA. (9) INITIAL PLANNING CONFERENCE (IPC): 14-18 JUL 08 AT NEWCASTLE, AUSTRALIA. (10) THE PUBLIC ENVIRONMENT REPORT (PER) TO THE AS DEPARTMENT OF ENVIRONMENTAL STEWARDSHIP: 18 JUL 08. (11) COMBINED JOINT MANNING DOCUMENT CONFERENCE: 21-22 JUL 08 AT ADFWC, NEWCASTLE AS. (12) MSEL SYNCHRONIZATION CONFERENCE: 21-22 JUL 08 AT ADFWC, NEWCASTLE AS. (13) EA SUBMITS EXERCISE DIRECTIVE TO USPACOM J7: 30 JUL 08. (14) AUGMENTATION REQUIREMENTS DUE TO EA: 30 JUL 08. (15) COMBINED STRATEGIC PLANNING GROUP CONFERENCE: 11-15 AUG 08, CAMP SMITH HAWAII. (16) USPACOM J7 PUBLISHES EXERCISE DIRECTIVE: 22 AUG 08. (17) EA SUBMITS CTF CMD/BATTLE ROSTER REQUIREMENTS TO USPACOM J13: 15 SEP 08. (18) EVENT (DATA BASE) TEST # 1: 22-26 SEP 08 AT JWFC, SUFFOLK, VA. (19) COMBINED U.S.-AUS JOINT EXPERIMENTATION TECHNOLOGY AND CONCEPT PRESENTATIONS AND COORDINATION AT USPACOM GAMING SUPPORT FACILITY (GSF), CAMP SMITH, HAWAII: 13-14 NOV 08. (20) DECISION TO DEFER TO THE AS DEPARTMENT OF THE ENVIRONMENT AND WATER RESOURCES: 15 NOV 08. (21) MID-PLANNING CONFERENCE (MPC): 17-21 NOV 08 AT CAMP SMITH, HAWAII. (22) MASTER SCENARIO EVENT LIST CONFERENCE: 22-24 NOV 08 AT CAMP SMITH, HAWAII. (23) EA PUBLISHES EXERCISE PLAN: 8 DEC 08. (24) EA SUBMITS REMAINING EXERCISE INDIVIDUAL AUGMENTEE REQUIREMENTS TO USPACOM J13: 12 DEC 08. (25) USPACOM J13 PUBLISHES INDIVIDUAL AUGMENTATION MESSAGE: 19 DEC 08. (26) COMPONENTS SUBMIT AUGMENTEE SHORTFALLS RECLAMA TO USPACOM J13: 14 JAN 09. (27) USPACOM J13 RETASKS COMPONENT AUGMENTEE SHORTFALLS THROUGH CROSS-SERVICE FILLS: 21 JAN 09. (28) EA SUBMITS SIGNIFICANT MILITARY EXERCISE BRIEF TO USPACOM J7: 15 FEB 09. (29) STAFFEX: 23-27 FEB 09 AT CAMP COURTNEY, OKINAWA. (30) USPACOM J7 PUBLISHES SMEB TO JCS: 1 MAR 09. (31) COMPONENTS VALIDATE SEALIFT AND AIRLIFT TPFDDS TO EA: 10 MAR 09. (32) COMPONENTS SUBMIT BY-NAME INDIVIDUAL AUGMENTEE LIST TO USPACOM J13: 10 MAR 09. (33) EVENT (DATA BASE) TEST # 2: 16-20 MAR 09, JWFC SUFFOLK, VA, CAMP SMITH, HAWAII (34) EA VALIDATES DEPLOYMENT/REDEPLOYMENT TPFDD TO USPACOM J35: 23 MAR 09. (35) SENIOR LEADER SEMINAR (SLS): 23-27 MAR 09, CAMP COURTNEY, OKINAWA. (36) EA FORCE FLOW (TPFDD) WORKSHOP: 23-27 MAR 09, CAMP H. M. SMITH, HAWAII. (37) USPACOM VALIDATES SEALIFT DEP/REDEPLOY TPFDD TO USTRANSCOM: 1 APR 09. (38) EA SUBMITS PUBLIC AFFAIRS GUIDANCE (PAG) TO USPACOM J7: 2 APR 09. (39) EA BRIEFS DETAILED CONCEPT TO USPACOM J7 AND USPACOM J01: 9 APR 09. (40) EA PUBLISHES EXERCISE CONTROL PLAN: 13 APR 09. (41) USPACOM PROVIDES PROPOSED PAG TO JCS: 13 APR 09. (42) FINAL SITE SURVEY (FSS): 14-17 APR 09, AUSTRALIA. (43) FINAL PLANNING CONFERENCE (FPC): 20-24 APR 09 AT NEWCASTLE, AS. (44) CRITICAL CANCELLATION DATE: 1 MAY 09. (45) T-DAY: 1 JUN 09. (46) EVENT (DATA BASE) TEST # 3: 06-10 JUL 09 (DISTRIBUTED LOCATIONS). (47) EXERCISE EXECUTION DATES: 06-26 JUL 09 (MAIN BODY DEPLOYMENT 06 - 10 JUL 09, RSOI/WORKUPS/ADVANCE OPS 08 - 15 JUL 09, CTF OPERATIONAL 13 - 25 JUL 09). (48) FACILITATED AFTER ACTION REVIEW (FAAR): 26 JUL 09.


(49) JTF COMMANDERS QUICK LOOK TO USPACOM: NO LATER THAN 1 AUG 09. (50) PARTICIPANTS SUBMIT JOINT LESSONS LEARNED AND ISSUES TO EA: 26 AUG 09. (51) EA WILL BE PREPARED TO CONDUCT AN EXECUTIVE AGENT HANDOVER BRIEF IN SEP 09 IF TS 11 SHIFTS TO AN NEW EA. (52) EA SUBMITS JOINT LESSONS LEARNED AND ISSUES TO USPACOM: 26 SEP 09. B. MODIFICATION TO THE TS 09 PLANNING MILESTONES MAY BECOME NECESSARY AS A RESULT OF EXERCISE REVIEW, TPFDD REFINEMENT AND/OR OTHER FACTORS. ANY REQUIRED MODIFICATIONS WILL BE APPROVED BY USPACOM J7 AND PROMULGATED BY MESSAGE TRAFFIC AND EXERCISE WEBSITE. C. SUCCESSFUL ACHIEVEMENT OF TS 09 WILL BE DIRECTLY RELATED TO THE CONTINUITY OF EXERCISE POCS DURING PLANNING AND EXECUTION. IT IS IMPERATIVE THAT POCS BE AVAILABLE FROM THE BEGINNING OF THE PLANNING PROCESS, THROUGH EXECUTION, AND THE FINAL IDENTIFICATION AND SUBMISSION OF CRITICAL LESSONS LEARNED AND UNRESOLVED ISSUES. CEPG DESIGNATED COMMANDS PER PARA 5 ARE REQUIRED TO PROVIDE THE NAMES OF THEIR PRIMARY AND ALTERNATE POCS FOR PLANNING TO THE EA NLT 15 NOV 07. D. EXERCISE PLANNING DOCUMENTS WILL BE COORDINATED BY EMAIL, TRANSMITTED BY DMS/AUTODIN WHEN APPROVED, AND/OR POSTED ON THE TS 09 WEBPAGE FOR USE BY ALL PARTICIPANTS. A WEBSITE HAS BEEN ESTABLISHED FOR TS 09 ON THE HQ USPACOM SIPRNET HOME PAGE LOCATED AT HTTP://WWW3.GSF.HQ.PACOM.SMIL.MIL/TS/TS09/ (LOWER CASE). THE EA WILL ESTABLISH, POPULATE AND MAINTAIN CENTRIX FOUR EYE'S (CFE), COMMON SIPRNET DOMAIN (CSD), AND ASIA PACIFIC AREA NETWORK (APAN) WEB SITES TO SUPPORT COMBINED INFORMATION FLOW NLT THE TS 09 IPC. E. TRAINING AUDIENCES ARE TO USE JTIMS TO FACILITATE TRAINING OBJECTIVES AND MASTER SCENARIO EVENT MANAGEMENT. 10. EXPERIMENTATION/DEMONSTRATION INTEGRATION: PRIORITY IS TO CONDUCT THE EXERCISE WITH THOSE ACTUAL SYSTEMS AND PROCESSES THAT ARE CURRENTLY IN USE BY OPERATING FORCES. HOWEVER, THE OPPORTUNITY EXISTS FOR INTEGRATING INTO TS 09 PROCESSES, SYSTEMS, OR TECHNOLOGIES NOT CURRENTLY PART OF THE STATUS QUO. A. THE TS 09 COMBINED EXECUTIVE STEERING GROUP (CESG) WILL ADJUDICATE SPECIFIC EXPERIMENTATION /DEMONSTRATION PROPOSALS TO ENSURE THEIR MATURITY AND CONSISTENCY WITH EXERCISE GOALS AND OBJECTIVES. B. JOINT US-AUS EXPERIMENTATION AND DEMONSTRATION PLANNING POA&M WILL BE PRESENTED AT THE CDC. EXPERIMENTATION WILL FOCUS ON EXERCISE TRAINING OBJECTIVES, COMMAND CAPABILITY GAPS, JMETS, AND LESSONS LEARNED FROM TS07 AND PREVIOUS EXERCISES AND CONTINGENCIES. 11. PLANNING CONFERENCE ATTENDANCE CONTROL MEASURES: A. FOR ALL U.S. PERSONNEL ATTENDANCE CONTROL MEASURES WILL INCLUDE SINGLE POC COUNTRY CLEARANCE AUTHORIZATION, QUOTAS AND ONLINE REGISTRATION/JUSTIFICATION FOR CONFERENCE ATTENDEES. THESE CONTROL MEASURES WILL BE INSTITUTED BY THE EA AND ARE INTENDED TO ACCOMMODATE REQUIRED PERSONNEL ATTENDANCE WHILE CREATING PERSONNEL AND COST EFFICIENCIES AND CONFORM TO LIMITED SPACE AVAILABILITY. THE EA IS RESPONSIBLE FOR MAXIMIZING THE USE OF COLLABORATIVE TOOLS SUCH AS VTC, INFO WORK STATION (IWS), PRE-COORDINATION MEETINGS, ETC.TO MINIMIZE THE IMPACT OF REDUCED CONFERENCE ATTENDANCE. B. COUNTRY/AREA CLEARANCE REQUESTS: CONSOLIDATED COUNTRY CLEARANCE REQUESTS ARE THE RESPONSIBILITY OF THE EXECUTIVE AGENT. ALL COMPONENTS/AGENCIES MUST SUBMIT PERSONNEL CLEARANCE DATA TO COMMARFORPAC FOR CONSOLIDATION AND SUBMISSION TO USDAO, AUSTRALIA. USDAO WILL NOT APPROVE TS 09 RELATED COUNTRY/AREA CLEARANCE REQUESTS SUBMITTED BY ANY OTHER COMPONENT/AGENCY. C. ea WILL COORDINATE FOR AND CONDUCT ADDITIONAL CONFERENCES/WORKSHOPS AS REQUIRED. 12. ENVIRONMENTAL: A. COMMANDANT ADFWC, IN COORDINATION WITH MARFORPAC AND COMPACFLT N01E1, FLEET ENVIRONMENTAL (SONAR USE); WILL HAVE THE LEAD FOR ENVIRONMENTAL ISSUES.


B. TO MEET THE TIMETABLE FOR AS ENVIRONMENTAL APPROVAL PROCESS, THE TS 09 EXERCISE ENVIRONMENTAL REFERRAL HAS TO BE SUBMITTED TO AS NLT 31 MAY 08. THIS IS PRIOR TO THE IPC. EXERCISE PARTICIPANTS WHOSE ACTIVITIES MAY HAVE AN ENVIRONMENTAL IMPACT MUST SUBMIT A LIST OF THESE ACTIVITIES TO THE EA ENVIRONMENTAL LEAD NLT 01 MAY 08. AFTER THIS DATE NO NEW ACTIVITIES WITH A POSSIBLE ENVIRONMENTAL IMPACT WILL BE ALLOWED. C. PROVIDE ACTIVITIES WITH ENVIRONMENTAL IMPACT INFORMATION AND DETAILS TO MR. TRAVIS COLLINS PHONE +61-2-4964-6076, EMAIL [email protected]. FAX +61-417-457-781, AND MR. LARRY FOSTER PHONE 808-471-4235 EMAIL [email protected]. 13. FORCE FLOW (TPFDD): A. TS 09 EXERCISE SUPPORT FORCE FLOW PLAN IDENTIFICATION (PID) IS 59TSD FOR DEPLOYMENT AND 59TSR FOR REDEPLOYMENT (THESE PIDS WILL INCLUDE EXERCISE AND SAD PAX AND CARGO REQUIRING STRATEGIC LIFT). NOTE: THE INCLUSION OF FREEDOM BANNER AND SAD IN THE EXERCISE CONSTRUCT TBD. B. NEWSGROUP: EXERCISE.TS09.PACOM.PLANS HAS BEEN ESTABLISHED ON NEWS SERVER NEWS.GCCS.PACOM.SMIL.MIL TO ASSIST COMMANDS IN THE PLANNING, COORDINATION, AND VALIDATION FOR MOVEMENT OF EXERCISE PERSONNEL AND EQUIPMENT TO AND FROM AUSTRALIA IN SUPPORT OF TS 09 AND SUPPORTING EXERCISES. THE EXERCISE NEWSGROUP IS THE ONLY OFFICIAL SOURCE FOR EXERCISE-RELATED FORCE FLOW INFORMATION. TELEPHONE CONVERSATIONS, EMAILS OR PLANNING CONFERENCE DISCUSSIONS ARE NOT BINDING. FOR ASSISTANCE GAINING ACCESS TO NEWSGROUPS, CONTACT MS. LINDA JETHROE, HQ USPACOM/J35, DSN 477-8136, OR VIA NEWSGROUP OR EMAIL ADDRESS: [email protected]. C. FORCE FLOW DISCIPLINE IS THE KEY TO SUCCESS. TO REDUCE CONFUSION AND COSTLY LAST-MINUTE SCHEDULE CHANGES, EVERY LEVEL OF COMMAND MUST APPLY AND ENFORCE DISCIPLINE WHEN IDENTIFYING AND SOURCING EXERCISE REQUIREMENTS AND VALIDATING EXERCISE MOVEMENT DATA. SERVICE COMPONENT COMMANDS MUST CONDUCT AND VERIFY DETAILED PLANNING FOR EACH ULN PRIOR TO VALIDATION, AND PROVIDE TIMELY NOTIFICATION OF PID CHANGES THROUGH EXERCISE NEWSGROUPS. SERVICE COMPONENTS ARE RESPONSIBLE FOR CONFIRMING THAT PID CHANGES ARE PASSED TO THE LOWEST POSSIBLE LEVEL - THE INDIVIDUAL ACTIVE DUTY OR RESERVIST AUGMENTEE. D. COMMERCIAL TICKET PROGRAM (CTP). CTP IS BY EXCEPTION AND WILL NOT BE USED SOLELY FOR CONVENIENCE OF EXERCISE PARTICIPANTS. COMPONENTS DO NOT NEED TO IDENTIFY CTP CANDIDATES. UPON ENTRY OF MOVEMENT REQUIREMENTS INTO THE TPFDD, USPACOM J7/J35 WILL WORK WITH USTRANSCOM TO IDENTIFY ULNS THAT WILL MOVE BY CTP AND ALCON WILL BE NOTIFIED VIA MESSAGE. COMPONENTS WILL HAVE TO JUSTIFY OUT-OF-WINDOW AND NON-APPROVED APOE/APOD REQUIREMENTS TO EA VIA NEWSGROUPS PRIOR TO VALIDATION. E. VALIDATION: VALIDATION IS THE PROCESS BY WHICH USPACOM SUBORDINATE COMMANDS CONFIRM TO USPACOM THAT ALL PID ENTRIES REPRESENT VALID EXERCISE REQUIREMENTS, REFLECT THE CURRENT UNIT STATUS ATTRIBUTES AND AVAILABILITY, CONFIRM UNITS TASKED IN VALIDATED ULN'S ACKNOWLEDGE AND WILL HAVE PASSENGERS/CARGO AT DESIGNATED PORTS BY ALD, ARE FREE OF AUTOMATION ERRORS, CONFORM TO VALID APOE/APOD/MOVEMENT WINDOW COMBINATIONS, AND HAVE ACCURATE LEVEL IV DETAIL FOR PASSENGERS AND CARGO. ALL FIELDS MUST BE VERIFIED BEFORE VALIDATING TO USPACOM, J71/J35. SEE PARA 9.A. FOR VALIDATION MILESTONES. 14. CLASSIFICATION GUIDANCE: A. PRODUCTS (MESSAGES, BRIEFINGS, ETC) CREATED SPECIFICALLY FOR EXERCISE TS 09 WILL BE CAVEATED REL AS/CAN/UK/US TO THE MAXIMUM EXTENT POSSIBLE. THIS WILL NOT ONLY ALLOW FULL AS-U.S. INTERCHANGE, BUT WILL FACILITATE THE FLOW OF INFORMATION THROUGH THE CENTRIX FOUR EYES (CFE) AND COMMON SIPRNET DOMAIN (CSD) SYSTEMS. B. EXERCISE RELATED MOVEMENTS AND LOCATIONS OF FORCES IN CONJUNCTION WITH EXERCISE TS 09 ARE AUTHORIZED FOR RELEASE.


C. REFERENCES TO C-DAY WITH RESPECT TO STRATLIFT MOVEMENT IS CLASSIFIED SECRET IAW USPACOM TPFDD LOI. D. FOREIGN DISCLOSURE OFFICES MUST REVIEW CLASSIFIED MILITARY INFORMATION (CMI) TO DETERMINE WHAT IS RELEASABLE. MINIMIZING THE AMOUNT OF CMI FACILITATES COMBINED TRAINING. E. UNLESS SPECIFICALLY AUTHORIZED, AUSTRALIAN NATIONALS WILL NOT BE GIVEN ACCESS TO SYSTEMS WHICH ARE U.S.-ONLY OR WHICH REQUIRE INTERFACE WITH U.S.-ONLY SYSTEMS AND NETWORKS (SUCH AS CTAPS, JDISS, SIPRNET, ETC). PROPOSALS TO PERMIT FOREIGN NATIONAL ACCESS TO THESE U.S. ONLY SYSTEMS MUST BE REQUESTED VIA APPROPRIATE CHANNELS WITH FULL JUSTIFICATION EXPLAINING REQUIREMENT AND THE SECURITY SAFEGUARDS THAT PREVENT INADVERTENT DISCLOSURE OF CMI. SHOULD COMBINED OPERATIONS WITH OR NEARBY THESE U.S.-ONLY SYSTEMS AND NETWORKS BE GRANTED; ONLY CMI APPROVED FOR DISCLOSURE AND/OR RELEASE IS AUTHORIZED. ANY REQUESTS FOR FOREIGN ACCESS TO U.S.-ONLY SYSTEMS MUST BE SUBMITTED AS EARLY AS POSSIBLE, NLT THE TS 09 FPC, TO USPACOM J223. 15. POINTS OF CONTACT: A. MARFORPAC (U.S. EA) (1) PRIMARY POC:LTCOL CARL REYNOSO, COMMARFORPAC G3 DSN 477-8640 /(808) 477-8640, EMAIL: [email protected] (SIPR), [email protected] (UNCLAS) (2) MARFORPAC (EA) SECONDARY POC: MR STEVEN MERRILL, COMMARFORPAC G3 DSN 477-8796/(808) 477-8796, EMAIL: [email protected] (SIPR), [email protected] (UNCLAS) B USPACOM PRIMARY POC: LTC KEN HARVEY, J712, DSN 315 477-8246, UNCLAS FAX 477-8280, EMAIL: KENNETH.J.HARVEY1 @PACOM.SMIL.MIL (SIPR), [email protected] (UNCLAS). C. ADDITIONAL POINTS OF CONTACT (DSN PREFIX 315): (1) USPACOM J72 (JTF CERTIFICATION) LTC STEPHEN MYERS 477-8272 (2) USPACOM J723 (LESSONS LEARNED) MR JIM LONG 477-7767 (3) USPACOM J7A (JTIMS) MR. TIM SCHROTH DSN 477-8220/(808) 477-8220 (4) USPACOM J462 (LOGISTICS) MAJ PHILLIP BENEFIELD DSN 477-7490/(808) 477-7490 (5) USPACOM J061 (LEGAL) CDR GREG SMITH DSN 477-1191/(808) 477-1191 (6) USPACOM J81 (EXPERIMENTATION) MIKE SOLOMON DSN 477-7666/(808) 477-7666 (7) PACFLT N37 (LEAD PLANNER) CDR JAMES DAVIS 808-471-4832 DSN 315-471-4832 (8) 13 AF EXERCISES MAJ KEN CLINE 449-8943/(808) 449-8943 (9) USARPAC G35 EXERCISES/TREX MR SEAN LEE 438-5809/(808) 438-5809 D. AUSTRALIAN DEFENCE FORCE (ADF) (1) PRIMARY POC: CMDR DICK SINGLETON, HQJOC J70 INTERNATIONAL ENGAGEMENT AND EXERCISES PHONE: 011 61 2 6127 1231, UNCLAS EMAIL: [email protected] ADFWC POC: LCMDR VIC MACINTOSH 011 61 2 4964 6021 UNCLASS EMAIL: [email protected] BT


Intentionally Blank

Enclosure (8): Initiating Directive (Example)

(Text Format)

Enclosure (8)

ENC (8)-1

18 Apr 08 MEMORANDUM FOR SEE DISTRIBUTION FROM: Chief of Staff, NORAD AND USNORTHCOM SUBJECT: Vigilant Shield 09 (VS 09) Initiating Directive 1. Attached is the Initiating Directive for VS 09. The Initiating Directive is intended to announce the exercise planning process and provide exercise planning guidance. This directive provides key planning information and includes exercise objectives, dates, training audiences, scenario concept, planning workgroups, points of contact, and milestones. 2. This directive also outlines specific tasking and responsibilities for NORAD and USNORTHCOM staff and supporting elements to ensure the successful execution of the exercise. //ORIGINAL SIGNED BY//

PAUL J. SULLIVAN Major General, USAF

Attachments: (1) Distribution List (2) Vigilant Shield 09 Initiating Directive

Enclosure (8)

ENC (8)-2

Distribution List This memo is available on the VS 09 exercise planning site on the NIPR at: https://operations.noradnorthcom.mil/sites/Exercises/Planning/PriorityExercises/VS09/default.aspx under Shared Documents. This memo may be reproduced for use in planning and development of supporting exercise plans and materials. Electronic copies of this memo will be forwarded to the following NORAD-USNORTHCOM directorates, components and subordinate commands, and the Joint Warfighting Center.

N-NC/J1 N-NC/J2 N/J3 NC/J3 N-NC/J4 N-NC/J5 N-NC/J6 N-NC/J8 N-NC/IC N-NC/SG N-NC/JA N-NC/PA N-NC/CP N-NC/HC SJFHQ-N ARNORTH AFNORTH FFC MARFORNORTH ANR CANR CONR CMD JFHQ-NCR JTF-AK JTF-CS JTF-N JWFC

Enclosure (8)

ENC (8)-3

Vigilant Shield 09 Initiating Directive References:

a. NORAD and USNORTHCOM FY 08-09 Commander’s Training Guidance (U) b. CJCSM 3500.03B Joint Training Manual 31 Aug 07

1. PURPOSE. This directive provides tasking, control and guidelines, in accordance with the NORAD and USNORTHCOM Commander’s Training Guidance, necessary to plan, design and execute exercise VS 09 within the commands and in concert with NORAD-USNORTHCOM (N-NC) component and subordinate commands. It enables exercise planners at all levels to develop supporting objectives, identify requirements, and plan events for a successful exercise execution. The scope and dynamics of exercise development necessitate that all exercise-related documents may be modified on short notice. The latest copies will be posted on exercise web sites with a summary of the changes identified. 2. EXERCISE DATES.

a. Exercise execution: 12-18 Nov 08 b. Facilitated After Action Review (FAAR) Secure Video-Teleconference

(SVTC): 19 Nov 08 c. Critical Cancellation Date (CCD): 10 Oct 08

3. CONCEPT. Vigilant Shield 09 is a Chairman, Joint Chiefs of Staff (CJCS)-designated, N-NC-conducted, US Joint Forces Command (USJFCOM)-supported Command Post Exercise (CPX) focusing on Homeland Defense (HD) with some Defense Support of Civil Authorities (DSCA) processes included. VS 09 will be conducted as a scheduled Tier III exercise within the National Exercise Program (NEP). NORAD-USNORTHCOM Headquarters is the primary training audience and the exercise is linked to USSTRATCOM’s Global Lightning 09 and Bulwark Defender 09, the Joint Staff’s Positive Response 09, the National Guard’s Vigilant Guard series, the State of California’s Golden Guardian exercise and Canada Command’s Determined Dragon 09. 4. OVERVIEW. N-NC/J7 has been designated as the lead planning agent for VS 09. All the exercises linked/combined with VS 09 will use a common Joint Event Life Cycle (JELC) whenever possible. Specifically, exercise planners from all linked exercises will participate in a common set of planning conferences [Initial Planning Conference (IPC), Scenario Development Conference (SDC), Mid Planning Conference (MPC), Final Planning Conference (FPC) and Master Scenario Events List (MSEL) Synchronization Conference (MSC)] to plan and coordinate exercise development. USSTRATCOM’s IPC was conducted earlier in December 2007 and was therefore not incorporated. Direct coordination is authorized for all other JELC steps. As needed, individual exercise planning work groups will schedule teleconferences or VTCs to meet planning milestones, but will also participate in these common planning conferences. In addition, a single control structure managed by the Joint Warfighting Center (JWFC) will be used

Enclosure (8)

ENC (8)-4

to conduct the exercise. As part of the control structure, the Joint Master Scenario Events List (JMSEL) application will be used as the single event database to facilitate exercise control. When finalized, the RELCAN and NIPRNet JMSEL databases will be merged with SIPRNet JMSEL to provide a single exercise execution control database.

a. Commander’s Intent. For VS 09, N-NC Commander’s intent is to conduct a narrowly-focused, in-depth exercise with air defense operations as the primary venue. The scenario will be focused on air defense (NORAD-centric), DSCA, and terrorism threats and/or incidents. VS 09 will focus on symmetric and asymmetric air threats with limited DSCA responses provided by N-NC components. VS 09 combines multi-level Command Post Exercise (CPX) elements. Specifically, VS 09 will:

(1)Validate appropriate Commander’s Interest Items/Lessons Learned from National Level Exercise 2-08 and Vigilant Shield 08

(2)Exercise elements of CONPLANs 3310 (Aerospace Defense), 3400 (Homeland Defense), 3500 [Chemical, Biological, Radiological, Nuclear and High-Yield Explosive Consequence Management (CBRNE CM)], and 3501 [Defense Support of Civil Authorities (DSCA)]

(3)Exercise counterterrorism plans and tactics, techniques and procedures (TTPs) identified in the Counterterrorism Combined Defense Plan (CT CDP) and other CONPLANs. The VS 09 counterterrorism focus was previously exercised through the USNORTHCOM VITAL ARCHER exercise series

(4)Coordinate with U.S. Army North (ARNORTH) Headquarters to deploy and employ a subordinate Joint Task Force (JTF) using an Operational Command Post (OCP) as its core element

(5)Deploy and employ limited elements of a CBRNE CM Response Force (CCMRF)

b. Method. VS 09 will employ integrated academics, simulations, Table Top Exercises (TTXs), Staff Exercises (STAFFEXs), and other linked events culminating in a focused, November timeframe CPX. The DOD will deploy and employ ARNORTH OCP 2 to California State Golden Guardian exercise venue locations as the scenario dictates. DSCA will be provided during CPX and limited Field Training Exercise (FTX) play in support of a Federal response through a Joint Field Office (JFO) Federal Coordinating Officer (FCO) (may be simulated) as requested by the State of California (CA).

c. End State. N-NC HQs are evaluated and/or assessed in HD and DSCA missions, and staff implementation of solutions and/or fixes to NLE 2-08 and VS 08 Commander’s Interest Items and Lessons Learned are validated. Command is capable of executing exercised CONPLANs and gaps are identified for resolution.

5. N-NC EXERCISE OBJECTIVES.

a. Employ a Joint Forces Air Component Commander (JFACC) and exercise NORAD HQ, Regions and Sectors against symmetric and asymmetric air threats

b. Employ a Joint Forces Maritime Component Commander (JFMCC) and exercise NORAD Maritime Warning and N-NC responses to maritime threat(s)

c. Exercise N-NC HQ Continuity of Operations (COOP)

d. Employ Joint Forces Land Component Commander (JFLCC) and have them deploy a JTF to conduct CBRNE CM operations in a CPX

e. Deploy and employ selected elements of a CCMRF in a CPX environment for assessment and collective training (may be limited FTX opportunities)

Enclosure (8)

ENC (8)-5

f. Exercise IAW designated NORAD and USNORTHCOM CONPLANs

g. Exercise the CT CDP with Canadian military and civilian counterparts

h. Explore possible seams in CONPLANs 3310, 3400, 3500 and 3501 with:

(1)DHS and DHS/FEMA (2)Office of the Assistant Secretary of Defense – Homeland Defense

(OASD-HD) (3)Joint Staff (4)US Strategic Command (5)US Transportation Command (6)US Joint Forces Command (7)US Pacific Command (8)US Southern Command (9)US Special Operations Command (10) National Guard (11) DOD supporting agencies and non-DOD departments and agencies (12) Non-Governmental Organizations (NGOs) and Private Industry

i. Validate transportation and logistics support constructs and

sustainability

j. Employ “Dynamic Enemy” (Red Team) concepts

k. Employ “Dynamic Media” concept to create a “CNN Effect” 6. JOINT MISSION ESSENTIAL TASKS (JMETs). The following JMETs will be exercised:

a. NORAD.

(1) SN 3.4.1 Provide Aerospace Control (2) SN 3.4.12 Provide Maritime Warning (3) SN 3.4.2 Provide Aerospace Warning (4) SN 3.4.2.1 Provide Integrated Tactical Warning and Attack

Assessment (5) ST 6.1.4 Organize and Coordinate Theater Air Defense (6) ST 7.1.5 Determine Theater Warfighting and Other Needs,

Solutions and Concepts (7) ST 8.4 Provide Theater Support to Other DOD and Government

Agencies b. USNORTHCOM.

(1) ST 1.6 Control or Dominate Strategically Significant Areas (2) ST 6.1.7 Conduct Ballistic Missile Defense Operations (3) ST 8.4.2 Conduct Counterterrorism (4) ST 8.4.5 Coordinate Civil Support in the United States (5) ST 8.5 Integrate Military Operations with Regional

Interagency Activities (6) ST 9.5 Coordinate Consequence Management in Theater

c. NORAD and USNORTHCOM.

(1) ST 2.4 Analyze and Produce Theater Strategic Intelligence and

Prepare Intelligence Products (2) ST 4.2 Coordinate Support to Forces in Theater (3) ST 5.1 Operate and Manage Theater C4I Environment

Enclosure (8)

ENC (8)-6

(4) ST 5.3 Determine Strategic Direction (5) ST 5.5 Conduct Theater-Wide Information Operations (IO) (6) ST 5.6.1 Plan and Provide for External Media Support and

Operations

c. NORAD and USNORTHCOM JMETs, the JMET staff supporting tasks, supporting JMETs of Subordinate JTFs and Service Component Commands, and the command linked JMETs of other commands shall include identified Training Objectives (TOs) that require observations and evaluations during VS 09. TOs are developed by staff directorates, divisions, branches, and special staff sections, and then validated by the Functional Battle Staff cells and units (i.e., training audiences) prior to inclusion in the Joint Training Information Management System (JTIMS). Most TOs can and should be trained to during lower level staff and individual training programs prior to VS 09. TOs identified for observation and evaluation during VS 09 are those that stress the training audiences (the HQ battle staff, operational JTF, or tactical unit) collective capabilities. All TOs submitted are derived from ability of training audiences to meet the standards of the JMETs, staff supporting tasks, supporting JMETs of Subordinate JTFs and Service Component Commands, and the command linked JMETs. In addition, TOs must have the necessary training situations and levels of performance (conditions and standards) to provide observation and evaluation criteria for the observation team. All TOs must be documented against the appropriate JMET, staff supporting task, etc. in JTIMS, where they are observed and evaluated by the observation team during VS 09. 7. TRAINING AUDIENCES/PARTICIPANTS.

a. Focused training audiences in VS 09 are N-NC Headquarters, NORAD Regions (CONR, CANR, ANR), ARNORTH, and AFNORTH. N-NC HQ will be the operational focus. JWFC Senior Mentor and Deployable Training Team (DTT) will be allocated to HQ N-NC.

b. Other expected participants as determined by scenario and exercise construct will include N-NC Subordinate JTFs and Components, selected elements of the CCMRF (to include, at a minimum, a Task Force Headquarters), simulated representation for OASD(HD), DHS, FEMA, State of California, Joint Staff, USJFCOM, USTRANSCOM, and the Government of Canada (Public Safety Canada, Strategic Joint Staff, and Canada Command). 8. KEY EXERCISE EVENTS TIMELINE. The dates for the primary planning conferences and exercise execution are listed in the Table below and also in JTIMS.)

DATE EVENT LOCATION 10-14 Dec 07

GL 09 IPC/Scenario Development Conference

Omaha, NE

8-11 Jan 08 VS 09 IPC Colorado Springs,

CO 12-14 Feb 08

VS-GL 09 Scenario Development Conference

Colorado Springs, CO

27-28 Feb 08

VS 08 Phase II TTX Colorado Springs,

CO

TBD Apr 08 Bridge TTX for VS 08/NLE 2-08 (PR/VI) Colorado Springs,

CO 9-13 Jun 08 VS-GL 09 Mid Planning Conference Omaha, NE

TBD Aug 08 Bridge TTX for NLE 2-08/VS-GL 09 Colorado Springs,

CO

9-12 Sep 08 VS-GL 09 Final Planning Conference Colorado Springs,

CO 6-10 Oct 08 Future Plans Cell PLANEX Colorado Springs,

Enclosure (8)

ENC (8)-7

CO 21-23 Oct 08

VS-GL 09 MSEL Synchronization Conference

Suffolk, VA

12-18 Nov 08

VS-GL 09 Execution Various

20 Nov 08 N-NC FAAR Colorado Springs,

CO 9. INTELLIGENCE OVERVIEW. VS 09 will not include an intel warm start; however, as the VS 09 scenario includes terrorist activity, an intelligence background NOT involving the Universal Adversary List will be developed to support the scenario and facilitate use of the “dynamic enemy” concept. The Future Plans Cell will use “exercise STARTEX-similar” Intel to run a PLANEX 6-10 Oct 08. Exercise relevant Intel will be added to the weekly CSAM briefings in the weeks leading up to the 12 Nov STARTEX. 10.COORDINATING INSTRUCTIONS.

a. As a Tier III exercise under the National Exercise Program, the National Interagency Simulation Cell (comprised of representatives from appropriate departments and agencies based on the scenario) will be requested to support exercise play. This cell will simulate Federal Interagency activities and address headquarters-level strategic and policy issues. In the event there is insufficient Interagency support for the stand-up of the National Interagency Simulation Cell, JWFC will establish an Interagency Simulation Cell as part of the main Joint Exercise Control Group (JECG) in Suffolk, VA.

b. The Joint Staff will be conducting a Staff Assessment Visit (SAV) in conjunction with and after the completion of VS 09. The SAV will not interfere with VS 09 exercise and will be transparent to the general VS 09 audience. This information is provided for situational awareness only.

c. An Executive Steering Committee (ESC) will be established for VS 09 and chaired by N-NC/J7 Exercise Division Chief.

d. The National Guard Bureau and the N-NC/J71 Vigilant Guard Team #3 are responsible for the Vigilant Guard exercise which will run in conjunction with California’s Golden Guardian (GG) exercise. California National Guard (CAANG) and CA State Emergency Management Division (CA EMD) are the sponsors and lead planners for the GG exercise.

e. Joint Staff’s Positive Response 09-1 could include FTX and CPX play in response to the DSCA scenario in CA and would involve local, county, State and Federal participants.

f. USSTRATCOM’s GLOBAL LIGHTNING (GL) 09 is a CJCS-designated USSTRATCOM-conducted Tier I exercise designed to train USSTRATCOM HQ, USSTRATCOM’s Joint Functional Component Commands (JFCCs), Task Forces (TFs), service components, and other USSTRATCOM units on all mission areas via supporting plans to the linked COCOM's set of plans. BULWARK DEFENDER (BD) 09 is a Joint Staff-designated capability assessment designed to train, evaluate, and improve baseline readiness of computer network defenses, including integrated network operations command and control capabilities as well as tactics, techniques, and procedures across networks, services, and operations and security centers. As a major multi-COCOM and multi-agency effort, future documentation and planning calendars will refer to this combined exercise as VS-GL 09.

g. Canada’s Determined Dragon 09 will be a national-level exercise co-directed by Canada Command and Public Safety Canada. The main effort will be

Enclosure (8)

ENC (8)-8

the development of Interagency cooperation to enhance national capability and display focused intent. The exercise will be set in a bilateral asymmetric threat environment. Canada Command’s goal is to train toward an effective operational-level Headquarters capable of collaborating with other government departments and agencies to provide the necessary national direction and guidance to Regional Joint Task Force (RJTF) HQs, and demonstrate the ability as a full Joint Interagency Multinational Public (JIMP) partner by connecting and cooperating with N-NC in the defense of North America. Canada and the US will coordinate on vignettes to exercise the US and Canada Counterterrorism Combined Defense Plan (CT CDP).

h. US Joint Forces Command (USJFCOM), through the JWFC, provides support to N-NC for exercise design, planning, scenario development, MSEL development and exercise control for the exercises listed in paragraph 3. Specific details of JWFC support are listed in paragraph 11.c. below. In addition, USJFCOM/J3 Trusted Agent(s) (TA) is/are requested to participate in exercise planning and execution. Specifically, request USJFCOM/J3 TA participation in the planning conferences (IPC, MPC, FPC, MSEL Synchronization, In-Progress Reviews, and workgroup meetings (as required)), and, during the exercises, participating in White Cell VTCs and executing their role as the force provider in the Request for Assistance (RFA) process, including the alert, notification and deployment of identified, sourced CCMRF units. 11.TASKINGS. N-NC Directors, NORAD and USNORTHCOM subordinates and components, and the JWFC are tasked as follows:

a. N-NC.

(1)Director N-NC/J1 shall designate a VS 09 lead exercise planner for the directorate who will:

(a)coordinate with the N-NC/J1 Divisions to obtain appropriate subject matter expert (SME) representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(b)represent the Director, N-NC/J1 in scenario and scripting conferences, IPC, MPC, FPC, MSEL Synchronization, In-Progress Reviews (IPRs), and workgroup meetings (as required) for the exercise;

(c)coordinate and compile data from participating units to develop the real-world exercise participant/components (Blue Force) Joint Manning Document (JMD);

(d)draft and coordinate Exercise Individual Augmentation Request messages/electronic Staff Routing Sheet (eSRS) for all NORAD-USNORTHCOM Directorates and subordinate staffs;

(e)obtain participating units’ draft reporting instructions; prepare and release the exercise reporting instructions message;

(f)provide Annex E – Personnel of the Exercise Plan (EXPLAN) and appropriate appendices (as required) by 9 Jun 08 for review at the MPC;

(g)coordinate with venue workgroups to address J1 requirements; and

(h)supervise the development of exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the directorate’s training objectives.

(2)Director N-NC/J2 shall designate a VS 09 lead exercise planner for the directorate who will represent the N-NC/J2 at all work group and planning conferences and:

(a)represent the Director N-NC/J2 in scenario and scripting workgroups and conferences, IPC, MPC, FPC, MSEL Sync and IPRs and workgroup

Enclosure (8)

ENC (8)-9

meetings (as required) for the exercise and, in addition, serve as the VS 09 Intelligence Work Group Chairman;

(b)coordinate with the Intel Divisions and Branches as well as the Intelligence Community to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(c)provide exercise theater threat assessment prior to and during the exercise as required utilizing the National Exercise Program Universal Adversary database;

(d)develop Defense Intelligence Infrastructure (DII) and component intelligence reporting requirements in accordance with the N-NC Intelligence battle rhythm;

(e)develop the Ground Truth Document in coordination with JWFC (i.e., J2 will script event stream leading up to terrorist events, and JWFC will script results of the events);

(f)provide Annex B – Intelligence of EXPLAN and appropriate appendices (as required) by 9 Jun 08 for review at the MPC;

(g)identify Intelligence processes and procedures unique to the exercise (Information Management (IM) plan supplement) to enable intelligence information flow and support to components;

(h)coordinate with venue work groups to satisfy J2 requirements; and

(i)supervise the development exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the directorate’s training objectives.

(3)Director N/J3 shall designate a VS 09 lead exercise planner for the directorate who will:

(a)coordinate with the N/J3 Divisions and Branches to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(b)represent the Director N/J3 in scenario and scripting conferences (IPC, MPC, FPC, MSEL Sync and IPRs) and work group meetings (as required) for the exercise;

(c)provide and coordinate input to Annex C – Operations of EXPLAN for all venues and appropriate appendices (as required) by 9 Jun 08 for review at the MPC;

(d)participate in venue workgroups to coordinate N/J3 requirements;

(e)provide SMEs as Trusted Agents as required for realistic scenario development;

(f)fully develop NORAD Maritime Warning objectives for incorporation into VS 09 framework; and

(g)supervise the development of exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the directorate’s training objectives.

(4)Director NC/J3 shall designate a VS 09 lead exercise planner for the directorate who will:

(a)coordinate with the NC/J3 Divisions and Branches to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(b)represent the Director, NC/J3 in scenario and scripting conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(c)validate and approve Individual Augmentee requirements to be compiled by the N-NC/J1 and released to Force Providers by 30 Apr 08;

Enclosure (8)

ENC (8)-10

(d)compile, validate and transmit component Request For Exercise Support after review at the MPC/MDC;

(e)coordinate with N-NC/J7 to ensure Exercise Support units are entered into JTIMS, as required;

(f)coordinate with Canada Command and Canadian Special Forces Command for scenario development;

(g)direct USNORTHCOM IM, including its incorporation into the command crisis action and operating procedures;

(h)coordinate the design and maintenance of exercise Blue Players portal site with the N-NC Information Manager;

(i)coordinate with the USNORTHCOM Information Manager and publish the consolidated N-NC IM plan as Annex K to the EXPLAN not later than 19 Oct 08 for review at the MSC;

(j)provide and coordinate Annex C – Operations of EXPLAN and appropriate appendices (as required) by 9 Jun 08 for review at the MPC;

(k)participate in venue workgroups to coordinate NC/J3 requirements;

(l)provide SMEs as Trusted Agents as required for realistic scenario development; and

(m)coordinate with other NC/J3 SMEs to develop exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the directorate’s training objectives.

(5)The Director N-NC/J4 shall designate a VS 09 lead exercise planner for the directorate who will:

(a)coordinate with the N-NC/J4 Divisions and Branches to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(b)represent the Director N-NC/J4 in scenario and scripting conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(c)provide oversight for and monitor all logistical support requirements associated with the planning and coordination of the exercise;

(d)ensure that Environmental Protection Surveys and products required for compliance with the National Environmental Policy Act for the deployment of forces within the U.S. are completed and requirements documented within the EXPLAN ANNEX L (Drafts to be submitted by 9 Jun 08 for review at the MPC).

(e)provide Annex D – Logistics of EXPLAN and appropriate appendices (as required) by 9 Jun 08 for review at the MPC;

(f)lead the Deployment and Force Flow Work Group as well as the Logistics Work Group at all planning conferences and meetings;

(g)coordinate with venue workgroups to address J4 requirements; (h)coordinate with the Joint Staff and services for the

selection and use of a Base Support Installation to participate in exercise VS 09 and host/support deploying forces;

(i)provide SMEs as Trusted Agents as required for realistic scenario development; and

(j)supervise the development of exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix.



Enclosure (8)

ENC (8)-11

(b)represent the Director N-NC/J5 in scenario and scripting conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(c)provide exercise requirements and coordinate participation in support of Theater Security Cooperation (TSC) plans and policies, to include the arrangement of special visits and escorts for foreign visitors during exercise execution in support of TSC goals;

(d)provide SMEs as Trusted Agents as required for realistic scenario development;

(e)supervise the development of exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix; and

(f)provide Annex G – Strategic Communications of EXPLAN and appropriate appendices (as required) by 9 Jun 08 for review at the MPC.



(b)represent the Director N-NC/J6 in exercise planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(c)provide leadership for the Communications Work Group during exercise planning meetings, conferences, etc. to include the development of exercise milestones, assignment of responsibilities, work group agenda preparation and the preparation and presentation of work group out-briefs at all planning conferences;

(d)schedule, plan, and conduct exercise-specific communications testing and rehearsals to include internal and external communications exercises (COMMEXs) to ensure all stakeholders have access to the portals, collaborative tool suites, and secure conferencing capabilities as required during exercise execution;

(e)coordinate integration of communications and information sharing technology initiatives into exercise design to ensure initiative assessment without negative impact to training audience objectives or command and control;

(f)coordinate all exercise locations’ frequency requirements, prepare and issue an exercise Frequency Management Plan if required;

(g)promulgate the Communications Security (COMSEC) Call-Out message, as required;

(h)ensure directions in the standing Common Operational Picture (COP) message are followed;

(i)coordinate the development and finalization of Annex K – Command, Control, Communication and Computer (C4) Systems of EXPLAN and appropriate appendices (as required) by 9 Jun 08 for review at the MPC;

(j)publish Exercise Phone Book on both unclassified and classified portals for both exercise control and exercise participants not later than one week prior to exercise execution;

(k) coordinate Mobile Training Team (MTT) visits for IM training for exercise participants, as requested;

(l) coordinate with the JWFC exercise planning team to ensure the exercise control networks and communications requirements are fulfilled;

(m) coordinate with venue workgroups to address J6 requirements; and

(n) develop exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario.

(8)The Exercise Division Chief, N-NC/J71 shall designate the Branch Chief of N-NC/J712 as the VS 09 lead exercise planner for the directorate who will:

Enclosure (8)

ENC (8)-12

(a)coordinate all exercise planning and scenario development to

achieve approved exercise objectives; (b)coordinate with the N-NC/J75 Joint Readiness Division to

provide a current command assessment of the command’s and subordinate commands’ and components’ JMETL status to guide development of exercise focus areas and N-NC objectives for VS 09;

(c)coordinate with JWFC and subordinate commands and components to ensure the completion of a JMSEL that will meet exercise objectives;

(d)coordinate with J74 for a primary point of contact for all modeling and simulation development, testing, and execution;

(e)ensure the entry of force requirements (or the NC/J3 developed supplemental RFF) into JTIMS, as required.

(f)develop, schedule, and administer all facets of the Joint Exercise Life Cycle (JELC) and ensure the timely completion of exercise milestones;

(g)develop exercise planning progress presentations and schedule update briefings for the N-NC/J7 with the N/J3, NC/J3, CS, DC, ND and CDR after each major planning conference;

(h)coordinate with NC/J32 for counterterrorism scenario planning, objectives, and milestones relating to bi-national special operations activities,

(i)coordinate with J72 to ensure development of the supporting staff training plan;

(j)coordinate with J75 to develop a VS 09 Collection Management Plan for HQ N-NC to include the development of a Data Collection Team;

(k)coordinate with J75 to provide and present Facilitated After Action Review (FAAR) instructions to participants during the Final Planning Conference;

(l)coordinate with J75 to collect FAAR inputs and development of the FAAR presentation to be conducted upon conclusion of the exercise;

(m)publish and monitor exercise milestones, tracking the exercise through completion;

(n) coordinate with J75 to develop the Training Objectives Worksheet (TOW);

(o)coordinate with J74 to get approval of exercise funding including airlift and selected personnel travel related to planning conferences and execution;

(p)coordinate with J72 to develop a supporting staff training plan based on guidance from J7 and input gathered at the IPC and MPC, and provide brief of training plan at FPC;

(q)based on the J72 training plan, conduct appropriate Battle Staff Academics prior to the exercise, using the N-NC Learning Management System to the maximum extent possible;

(r)maintain a ready reference of all exercise messages, briefings, and conference results leading to the exercise;

(s)coordinate facilities and equipment required by the JWFC in or near N-NC headquarters to support N-NC Battle Staff training, exercise control and evaluation;

(t)assist in coordination of facilities and equipment required by JWFC at ARNORTH and deployed locations to support ARNORTH and N-NC Battle Staff training, exercise control and evaluation;

(u)develop, coordinate and promulgate the EXPLAN; and (v)coordinate with J75 to collect all participants’ After-Action

Reviews (AARs) and lessons learned, and publish a Quick Look Report (QLR) 30 days after the exercise and an Exercise Summary Report (ESR) NLT 90 days after the exercise.


Enclosure (8)

ENC (8)-13

(a)represent the Director, N-NC/J8 providing funding guidance and technical assistance as required;

(b)coordinate with the N-NC/J8 Divisions and Branches to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(c)represent the Director N-NC/J8 in exercise planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise.

(10) Director, NORAD-USNORTHCOM Interagency Coordination shall designate a VS 09 lead exercise planner for their staff who will:

(a)coordinate with the N-NC/IC Staff and Interagency representatives to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(b)represent the Director N-NC/IC in exercise planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(c)assist in the coordination of agency participation, level of play, location, and periods of VS 09 availability;

(d)assist in exercise planning and scenario development; (e)develop exercise events and supporting implementers within

the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the Staff’s training objectives;

(f)assist in leading the Interagency Work Group; (g)coordinate with venue workgroups to address Interagency

requirements; and (h)aid in drafting Annex V – Interagency Coordination of EXPLAN

and appropriate appendices (as required) by 9 Jun 08 for review at the MPC.

(11) The Command Surgeon shall designate a VS 09 lead exercise planner for their staff who will:

(a)coordinate with the N-NC/SG Staff and Interagency representatives to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(b)represent the Command Surgeon General in exercise planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(c)coordinate the development and scripting of realistic medical effects in the designated exercise scenarios;

(d)establish SG training objectives specific to this exercise; (e)participate in and support the venue work groups as required; (f)provide Annex Q – Medical Support of EXPLAN and appropriate

appendices (as required) by 9 Jun 08 for review at the MPC; and (g)develop exercise events and supporting implementers within

the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the Staff’s training objectives.

(12) The Staff Judge Advocate shall designate a VS 09 lead exercise planner for their staff who will:

(a)coordinate with the N-NC/JA Staff representatives to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(b)represent the Staff Judge Advocate in exercise planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(c)evaluate and analyze the N-NC exercise in view of current legal and related policy issues, and applicable domestic and international law;

Enclosure (8)

ENC (8)-14

(d)coordinate the development of exercise Rules Of Engagement (ROE);

(e)coordinate the development of exercise Rules on the Use of Force (RUF); and

(f)develop exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the Staff’s training objectives.

(13) The Command Public Affairs Officer shall designate a VS 09 lead exercise planner for their staff who will:

(a)coordinate with the N-NC/PA Staff representatives to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(b)represent the Public Affairs Officer in exercise planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(c)assist in exercise planning and scenario development of synthetic media to include the development of a dynamic “CNN Effect” exercise media cell;

(d)develop Proposed Public Affairs Guidance (PPAG) for submission to OASD/PA for approval and dissemination by 15 Oct 08;

(e)provide Annex F – Public Affairs of EXPLAN by 9 Jun 08 for review at the MPC;

(f)participate in scenario and scripting conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(g)lead the Public Affairs and Synthetic Media Work Group; (h)develop exercise events and supporting implementers within

the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the Staff’s training objectives;

(i)provide coordination for the establishment and execution of an exercise Joint Visitors Bureau (JVB) at the primary exercise location, in conjunction with other Federal, State, local, and tribal public affairs representatives; and

(j)coordinate with the NORAD-USNORTHCOM Protocol Office and Command Secretariat for the development of a VIP exercise invitation list.

(14) The Command Protocol Officer will:

(a)provide guidance for N-NC Distinguished Visitor (DV) visits related to the exercise, at both local and remote locations, to include coordination with subordinate commands and other Federal, State, and local Protocol officials; and

(b)support the planning and execution of the Bridge TTX (April 2008).

(15) The command Chaplain shall designate a VS 09 lead exercise planner for their staff who will:

(a)coordinate with the N-NC/HC Staff and Interagency representative to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(b)represent the Command Chaplain in exercise planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(c)coordinate the development and scripting of realistic religious support issues in the designated exercise scenarios;

(d)establish HC training objectives specific to this exercise; and

Enclosure (8)

ENC (8)-15

(e)develop exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the Staff’s training objectives.

(16) Director, Standing Joint Force Headquarters NORTH (SJFHQ-N) will designate a VS 09 lead exercise planner for their staff who will:

(a)coordinate with SJFHQ-N Staff representatives to obtain appropriate SME representatives to support scenario development and the achievement of specific training objectives supporting JMETL assessment and evaluation;

(b)represent the Director, SJFHQ-N in exercise planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise; and

(c)deploy individual augmentation in support of JTFs and/or components as directed.

(17) Director, Cheyenne Mountain Directorate (CMD) will designate CMD/J7 as the VS 09 lead exercise planner for CMD who will:

(a)ensure crew personnel in all operational centers are prepared to participate in the exercise and have read and understand all exercise documentation (available in Crew Notes, on the Exercise Web page, and through CMD/J7 briefings);

(b)coordinate with CMD/SC regarding system configurations and with 721st regarding their participation;

(c)coordinate the Training Objectives Worksheet (TOW); and (d)evaluate simulation (SIM) media tapes prior to STARTEX, if

required.

(18) The Foreign Disclosure Officer (FDO) will develop and implement procedures for the management of foreign releasable information material as required;

b. Components, Regions and JTFs.

(1)The Commander, US Army North (ARNORTH) will provide appropriate VS 09 exercise planning staff who will:

(a)represent the ARNORTH Commander in all exercise primary and venue planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(b)prepare and submit a request for staff personnel augmentation per current Manning Documents to the N-NC/J1;

(c)co-lead (with the State of California and N-NC/J71) the Land venue Work Group;

(d)as the Army Service Component Command (ASCC), coordinate all US Army exercise funding and deployed logistical support to include Army CBRNE Consequence Management Response Force (CCMRF) forces;

(e)prepare and submit Time-Phased Force Deployment Data (TPFDD) information to NC/J35 for validation not later than 15 Jul 08;

(f)provide the assistance of the Civil Support Response Division (CSRD) to develop of the CCMRF tactical training venues and execution management plan/observation plan;

(g)provide 10 Observer/Controllers (O/Cs) support to assist in the execution and assessment of the CCMRF FTX training plan. Specifics will be promulgated by separate correspondence;

(h)provide input to the EXPLAN; and (i)develop exercise events and supporting implementers within

the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and ARNORTH training objectives.

Enclosure (8)

ENC (8)-16

(2)The Commander, US Air Forces North (AFNORTH) will provide appropriate VS 09 exercise planning staff who will:

(a)represent the AFNORTH Commander in all exercise primary and venue planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise;

(b)prepare and submit a request for staff personnel augmentation per current Manning Documents to the N-NC/J1;

(c)prepare and submit TPFDD information to NC/J35 for validation;

(d)provide input to the EXPLAN; and (e)develop exercise events and supporting implementers within

the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and AFNORTH training objectives.

(3)NORAD Regions (ANR, CANR, CONR) will provide appropriate planning staff who will:

(a)provide representation in all exercise primary and venue planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) as required for the exercise;

(b)provide input to the EXPLAN; (c)participate in the exercise: provide a Command Center or a

Response Cell (24-hour operations) to replicate operations as determined during exercise coordination;

(d)develop exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and your Region’s training objectives;

(e)prepare and submit TPFDD information to NC/J35 for validation; and

(f)prepare and submit a request for staff personnel augmentation per current Manning Documents to the N-NC/J1, if required.

(4)US Marine Forces North (MARFORNORTH) will provide appropriate planning staff who will:

(a)provide representation in all exercise primary and venue planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise as appropriate;

(b)prepare and submit a request for staff personnel augmentation per current Manning Documents to the N-NC/J1 as required to support exercise play;


(d)coordinate all service exercise funding and deployed logistical support to include CCMRF forces;

(e)develop exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the Component training objectives.

(5) US Fleet Forces Command (FFC) will provide appropriate planning staff who will:




Enclosure (8)

ENC (8)-17

(d)develop exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and the Component training objectives.

(6)Commander, Joint Force Headquarters National Capital Region (JFHQ-NCR) will provide appropriate planning staff who will:



(c)provide an appropriate level operations center or a response cell (24-hour operations) to replicate operations as determined during VS 09 exercise coordination;

(d)develop exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario and JFHQ’s training objectives; and

(e)prepare and submit TPFDD information to NC/J35 for validation as required.

(7)Joint Task Forces (JTF-AK, JTF-N*, JTF-CS*) will provide appropriate exercise planning representation who will:

(a)represent the JTF in all exercise primary and venue planning and scenario conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise as appropriate;


(c)provide an appropriate level operations center or a response cell (24 hour operations) to replicate operations as determined during activities and exercises prior to VS 09;

(d)develop exercise events and supporting implementers within VS 09 and the MSEL synchronization matrix in support of the exercise scenario and the JTF’s training objectives; and

(e)prepare and submit TPFDD information to NC/J35 for validation as required. * Note: Now OPCON to JFLCC.

c. JWFC. Staff will:

(1)support N-NC/J7 in exercise development; (2)support development and participate in scenario and scripting

conferences (IPC, MPC, FPC, MSEL Sync and IPRs) for the exercise; (3)develop the Ground Truth Document in coordination with N-NC/J2 (J2

will script event stream leading up to terrorist events and JWFC will script results of the events);

(4)role-play the functions of supporting Unified Commands and/or higher and/or lateral activities, other DOD and non-DOD agencies if not directly participating;

(5)if needed, provide an Interagency Simulation Cell to replicate Interagency actions and capabilities required to support the exercise;

(6)assist in preparation of the CJCS Crisis Action Planning products (such as Warning Orders, Alert Orders and Planning Orders) as required;

(7)assist in the building of the exercise scenario and MSEL database in coordination with N-NC;

(8)provide media and public affairs support, as coordinated;

Enclosure (8)

ENC (8)-18

(9)identify personnel to supplement the Joint Exercise Control Group (JECG), observers, and other joint functions above the service component level, as required;

(10) coordinate design, installation, operation and maintenance, in conjunction with N-NC, of White Cell exercise communications systems needed to ensure MSEL execution and control of the exercise. Coordinate commercial communications requirements with appropriate contracting agencies;

(11) provide Annex X – Exercise Control Plan of EXPLAN and appropriate appendices (as required) by 9 Jun 08 for review at the MPC;

(12) provide Senior Mentor and associated Observer/Trainers (O/Ts) to N-NC. Provide O/Ts and Senior Mentor, analysts and DTT to ARNORTH as coordinated;

(13) facilitate AAR briefing and prepare written Commander’s Summary Report for N-NC; and

(14) manage development of exercise events and supporting implementers within the VS 09 MSEL and the MSEL synchronization matrix in support of the exercise scenario. 12. VS 09 JOINT EXERCISE PLANNING GROUP POCs.

a. Exercise Director: Gen Renuart, CDR N-NC

b. Deputy Exercise Director: Mr. Gene Pino (SES), N-NC/J7

c. Exercise Coordinator: COL Mike DeMarco, N-NC/J71 d. N-NC/J1: Ms. Kathy Bannick, (719) 554-5936 N-NC/J25E: Mr. Chuck Telotte, (719) 554-0260 N/J33: Mr. Jon Smidt, (719) 556-9654 N/J35: Lt Col Murray, (719) 554-4953 and Capt (CF) Marika Hagen, (719) 554-9045 N/J33N: LTC Kalb, (719) 554-5840 NC/J32: Mr. Tom Leithead, (719) 554-6379 NC/J37: (Pri) Mr. Michael Odornez, (719) 554-7145 NC/J37: (Alt) Mr. Tim Mishkofski, (719) 554-4906 N-NC/J39: Mr. Stu Habermehl, (719) 554-1501 NC/J35 JOPES: TBD N-NC/J4: Mr. Kevin Ross, (719) 554-2270 N-NC/J5: Ms. Darah Hyland, (719) 554-4412 and Mr. Scott Mason, (719) 554-1642 N-NC/J6: Mr. Mark Jensen, (719) 554-9515 N-NC/J71 POCs: - Vigilant Shield Team Lead: Mr. Steve Zakaluk, (719) 554-5453

- N-NC/J71 Planning Team: Aerospace: Capt Bob Harvie, (719) 554-3686 - Support: Mr. Mark Cravens, (719) 556-3647 - Maritime: Mr. Bob Hibbert, (719) 554-3686

- Land: Mr. Dave Funk, (719) 556-3647 - Counterterrorism: Mr. Chuck Thinger, (719) 554-9761

N-NC/J8: TBD N-NC/IC: Gordon Crom, (719) 554-4681 N-NC/WO: Mr. Kris Morrill, (703) 601-5090 POLAD: TBD N-NC/PA: Mr. Don Miles, (719) 554-4652 N-NC/SG: Mr. Adam Michels, (719) 554-3579 N-NC/JA: TBD N-NC/HC: Ms. Cathy Uetrecht, (719) 554-7234

N-NC/CP: TBD N2C2: (Pri) Mr. Mark Fitzgerald, (719) 556-1598 N2C2: (Alt) Mr. Tim Haddan, (719) 554-2373 SJFHQ-N: Mr. Ron Cilek, (719) 556-3114

Enclosure (8)

ENC (8)-19

CMD/J7: Mr. Tom Lavallee, (719) 474-2419 JTF-AK: Mr. Rick Everson, (907) 552-4873 JTF-CS: Mr. Frank Mettille, (757) 788-6559 JTF-N: MAJ Dave Youngblood, (915) 313-7602 JFHQ-NCR: LTC Robert Cornejo, (202) 685-2681 ANR: Maj (CF) Rob Murphy, (907) 552-4384 CANR: LCol (CF) Spike Tremblay, (204) 833-2500, ext 5160 CONR: Maj (CF) Trent Morrisey, (850) 283-8698 FFC: Mr. Eric Shaffer, (757) 836-5591 ARNORTH: LTC Paul Condon, (210) 221-0737 MARFORNORTH: Mr. Russ Forshag, (504) 678-8061 AFNORTH: Mr. Paul Daniel, AFNORTH A9 (DSN 523-4926) CANSOFCOM: Maj Tim Baker, (613) 719-1866 ACC: Ms. Shirley Auzenne ACC/A3H (757) 764-9328, or Mr. Larry Marks (757) 764-6148

e. Committees and Work Groups. The detailed planning and preparation

for this exercise will be conducted by planners as part of integrated, multi-agency committees and work groups. In an exercise of this magnitude and complexity, integrated work groups provide a means to develop a consistent and comprehensive scenario and control structure. The Executive Steering Committee provides oversight and direction to the work groups. Work groups design the main exercise venues. Below is a list of work groups (subject to change, based on needs of the exercise).

(1) Executive Steering Committee:

• Exercise Design and Development • Scenario Oversight

(2) Work Groups:

• Exercise Management and Control • Air (includes all NORAD planners) • Land (FEMA, ARNORTH and California State planners) • Maritime (including FFC planners) • Counterterrorism (includes CANSOFCOM planners) • IMD/BMD (includes Space) • Communications • Deployment • Logistics • Cyber (includes Information Assurance, Computer Network

Defense, Information Operations, Strategic Communications, Public Affairs and Media sub-groups)

• Intelligence • Interagency • Modeling and Simulation • Personnel Augmentation

13.EXERCISE DOCUMENTS. Documents designed specifically to support VS 09 are as follows:

a. Initiating Directive (ID). Provides an overview of the exercise, including basic concepts, dates, planning milestones and exercise objectives. Furthermore, this document provides tasking for exercise design and conduct, and assists exercise designers and planners at all command levels in developing supporting objectives and scenarios. Lead: N-NC/J71.

Enclosure (8)

ENC (8)-20

b. Exercise Plan (EXPLAN). The EXPLAN provides information for exercise participants (to be published NLT 30 Sep 08). Lead: N-NC/J71.

c. Exercise Control Plan. Supplement to EXPLAN. Provides information for “white cell” players on exercise control aspects. Lead: JWFC 14.VS 09 Collection Management Plan (CMP). Identifies collection methods to provide data for NORAD and USNORTHCOM Exercise Summary Reports, Task Performance Observer (TPO) Evaluations, Training Proficiency Evaluations (TPEs) and Lessons Learned (to be published NLT 29 Oct 08). Lead: N-NC/J75.

a. Exercise planning documents will be posted at the JWFC sites when they are established. Until then, they can be found at the following locations:

(1) RELCAN: TBD (2) SIPRNet: https://operations.noradnorthcom.smil.mil/sites/Exercises/ planning/priorityexercises/vs09/default.aspx under Shared Documents (3) NIPRNet: https://operations.noradnorthcom.mil/sites/Exercises/Planning/ PriorityExercises/VS09 under Shared Documents

b. Blue Player Actions and data will be posted using real-world systems and dedicated exercise play pages. 15. EXERCISE PLANNERS/TRUSTED AGENTS INSTRUCTIONS.

a. Purpose. These instructions provide additional information for Exercise Planners/Trusted Agents to develop exercise events and implementers. Planners will provide support as necessary to support the exercise objectives and their specific training audiences.

b. Responsibilities. Exercise Planners/Trusted Agents are responsible for the validity and quality of their Joint MSEL (JMSEL) inputs. As SMEs, Exercise Planners/Trusted Agents are to ensure their injects will remain within the exercise objectives. As part of the planning process, the MSEL will be synchronized to ensure that a particular MSEL will not inadvertently impede other agencies’ training objectives.

c. Supporting Documents. To help SME Exercise Planners/Trusted Agents develop coherent, integrated MSEL events, the JWFC has developed a set of exercise planning tools. The exercise Planning Matrix is a spreadsheet that lays out the major events in the exercise by time and by actor. Vignette Ground Truth documents provide the detailed background for each event. The purpose of the Ground Truth document is to provide a basis for MSEL scripting. It contains all releasable facts and is the governing document from which MSEL events and implementers will be built. These two tools will be available on the exercise web sites.

d. MSEL Instructions.

(1)JMSEL link is located at the following links:

(a)NIPRNet: https://jmsel1.jwfc.jfcom.mil/jmsel (b)SIPRNet: http://jmsel1.exer.jntc.smil.mil/jmsel (c)NXMSEL: https://hseep.dhs.gov/nxmsel/main.asp (d)RELCAN: http://157.219.176.12/jmsel

Enclosure (8)

ENC (8)-21

(2)Access to the NIPRNet JMSEL requires an additional approval which must be granted by the JWFC/J6 Webmaster. To request access to the NIPRNet Webgate, sign on using the JMSEL NIPRNet URL. When the JWFC webpage appears, request “access an account.” The top portion of the form is your information, while the bottom portion is the JWFC POC information. The comment portion must have the following statement, “Request access to the JMSEL server.”

e. Exercise Plan (EXPLAN) Development. Organizations listed as Office of Primary Responsibility (OPR) are assigned the following sections of the VS 09 EXPLAN for preparation. The EXPLAN will be built concurrent with exercise development through the use of conference work groups. Deadline for submitting appropriate sections is 9 Jun 08 for review at the MPC. A draft of the EXPLAN will be available at the FPC for review. The final EXPLAN will be published no later than 30 Sep 08.

losure 9: SECTION OPR

• Security Instructions N-NC/J7

• Classification Guidance (Para 15.f.)

• Table of Contents N-NC/J7

• Basic Plan o Purpose o Background/Executive Summary o Exercise Concept and Scope o JMETs o Major Exercise Objectives o Exercise Scenario o Training Audiences o STARTEX Conditions

N-NC/J7

• Annex A – Task Organization N-NC/J7

• Annex B – Intelligence N-NC/J23

• Annex C – Operations o Appendix 1 – NORAD

Tab A – ANR* Tab B – CANR* Tab C – CONR*

o Appendix 2 – USNORTHCOM Tab A – ARNORTH* Tab B – JFHQ-NCR* Tab C – JTF-CS* Tab D – JTF-N* Tab E – JTF-AK* Tab F – Fleet Forces Command* Tab G – Air Forces North* Tab H – Marine Forces North* Tab I – CCMRF*

o Appendix 3 – Information Operations o Appendix 4 – Operations Security

Tab A – OPSEC Estimate/Critical Information Listings (CIL)

Tab B – Operations Indicators and Threats to Operations

N/J33 and N/J35 ANR CANR CONR NC/J37 ARNORTH JFHQ-NCR JTF-CS JTF-N JTF-AK FFC AFNORTH MARFORNORTH N-NC/J71 N-NC/J39 N-NC/J39

• Annex D – Logistics N-NC/J4

Enclosure (8)

ENC (8)-22

• Annex E – Personnel o Appendix 1 – Component Personnel Portion of the CDR

SITREP o Appendix 2 – NORAD Regional Personnel Portion of

SITREP o Appendix 3 – Personnel Definitions

N-NC/J1

• Annex F – Public Affairs o Appendix 1 – Public Affairs Guidance o Appendix 2 – Visitors

• Annex G – Strategic Communications

N-NC/PA N-NC/PA N-NC/Protocol N-NC/J5

• Annex H – Environmental Services N/J33O

• Annex K – Command, Control, Communications, and Computer (C4) Systems o Appendix 1 – Communications Planning/Defense Red Switch

Network Secure Voice Conferencing (DRSN) o Appendix 2 – Message Handling Procedures o Appendix 3 – Communications Security (COMSEC) o Appendix 4 – Exercise Phone Book

• Annex Q – Medical Services • Annex V – Interagency Coordination

b. N-NC/J6 N-NC/SG N-NC/IC

• Annex X – Exercise Control Plan JWFC

• Annex Z – Distribution List N-NC/J7

*Notes: 1. At their discretion, OPRs can add or delete an Appendix or Tab to fit their need. 2. Tabs should include exercise objectives, JMETs, participating forces, milestones, points of contact and exercise control. If individual commands develop an EXPLAN, then that EXPLAN can be substituted for the required Tab.

f. Classification Guidance. The following classification guidance will be used for VS 09: (1) Exercise Nickname Unclassified (U) (2) Exercise Execution Dates Unclassified (U) (3) Exercise Concept (Scenario) Unclassified (some portions classified) (4) Exercise Objectives Unclassified (U) (5) Participants (collective list) Unclassified (U)

g. Operational Security (OPSEC). Commanders at all echelons will stress OPSEC. Use of secure voice communications systems and encryption devices will be used to preclude disclosure of sensitive information to unauthorized sources.

h. Exercise Project Officers. Respective exercise planners:

(1) NORAD-USNORTHCOM:

(a)Mr. Steve Zakaluk, N-NC/J712 VS Team Lead, (719) 554-5453, DSN 692-5453, FAX (719) 554-9688, DSN FAX 692-9688, NIPRNet – [email protected], SIPRNet – [email protected]

(b)Capt (CF) Bob Harvie, N-NC/J712 Exercise Planner, (719) 554-3686, DSN 692-3686, FAX (719) 554-9688, DSN FAX 692-9688, NIPRNet – [email protected], RELCAN – [email protected]

Enclosure (8)

ENC (8)-23

(c)Mr. Mark Cravens, N-NC/J712 Exercise Support (719) 556-3647, DSN 834-3647, FAX (719) 554-9688, DSN FAX 692-9688, NIPRNet – [email protected], SIPRNet – [email protected]

(d)Mr. Bob Hibbert, N-NC/J712 Exercise Support, (719) 554-3686, DSN 692-3686, FAX (719) 554-9688, DSN FAX 692-9688, NIPRNet – [email protected], SIPRNet – [email protected]

(e)Mr. Dave Funk, N-NC/J712 Exercise Support, (719) 556-3647, DSN 834-3637, FAX (719) 554-9688, DSN FAX 692-9688, NIPRNet – [email protected], SIPRNet – [email protected]

(f)CDR Bob Heath, N-NC/J712 Exercise Support, (719) 556-3647, DSN 834-3637, FAX (719) 554-9688, DSN FAX 692-9688, NIPRNet – [email protected], SIPRNet – [email protected]

(2) Joint Warfighting Center:

(a)Mr. Bill Johnson, USJFCOM VS 09 Exercise Planner, (757) 203-7862, DSN 668-7862, FAX (757) 203-7086, DSN FAX 668-7086, NIPRNet - [email protected], SIPRNet – [email protected]

(b)Mr. Steve Winters, JWFC Joint Support Team (JST) Lead, (757) 203-6438, DSN 668-6438, FAX (757) 203-7031, DSN FAX 668-7031, NIPRNet - [email protected], SIPRNet – stephen.winters@jfcom/smil.mil

(c)Mr. Drew Trousdell, JWFC JST, Vigilant Shield Team Lead, (757) 203-6731, DSN 668-6731, FAX (757) 203-7031, DSN FAX 668-7031, NIPRNet – [email protected], SIPRNet – [email protected]

Enclosure (8)

ENC (8)-24

Intentionally Blank

Enclosure (9)

ENC (9)-1

Enclosure (9): Remote Site Survey Checklist

The purpose of this checklist is to collect information and determine remote site survey requirements for the installation, operation, and maintenance of communications nodes and modeling & simulation (M&S) systems in support of distributed and deployed events and exercises. Remote site requirements are a four-phased process: (1) provide the remote site read-ahead checklist; (2) conduct the on-site survey; (3) Submit an IATO to JWFC; and, (4) sign a technical Memorandum of Agreement (MOA) with the supported command. An example of an MOA is provided at the end of this guide. The Remote Site Read-Ahead Checklist is sent to the supported command three to four weeks prior to the site survey and is intended to provide a general understanding of the types of facilities and equipment needed to support joint force exercises. The package identifies the nature of the information the survey team intends to gather at the remote site. The data collected during the site survey is used to compile a Remote Site Survey Summary Report, used by exercise planners, the supported command, and remote site representatives to customize support requirements for a specific event or exercise. If multiple sites are visited a separate report should be prepared for each site. The site survey checklist is used as the primary reference in formulating the technical MOA between the supported command and JWFC, finalizing the site planning process. The MOA addresses the specific services and equipment that JWFC will provide and the services and equipment the supported command will provide. This document is produced following the completion of the site survey and initial site planning procedures. It will be signed by JWFC and the supported command.

Remote Site Survey Checklist

Enclosure (9)

ENC (9)-2

Table of Contents Section A. Trip Report/Executive Summary Section B. Site Management Logistical and Site Physical Security Administrative Equipment and Supply Command and Control Systems Video Teleconferencing Voice and Data Telecommunications Power and Environmental Control Maps, Charts, Building Diagrams and Floor plans Section C. Models and Simulations Checklist Section D. Intelligence Systems and SCIFs Section E. Interim Authority to Operate Requirements Section F. Memorandum of Agreement


Enclosure (9)

ENC (9)-3

SECTION A. TRIP REPORT/EXECUTIVE SUMMARY

This section should be a summary of survey results and outstanding issues not exceeding two pages in length. Suggested Format: Dates of Trip Sites Visited Members of Survey Team Points of Contact at Sites Summary of Results Critical Issues to be resolved


Enclosure (9)

ENC (9)-4

SECTION B. SITE MANAGMENT LOGISTICAL AND SITE PHYSICAL SECURITY Site Manager: Site manager or a point of contact that can make decisions about facilities in relation to the supported exercise at your location. Name: Commercial phone: After duty hours: DSN Phone: Fax: Email address: Home page address:

Mailing address:

Comments: Site Shipping Manager Inbound and Outbound: Name: Commercial phone: After duty hours: DSN Phone: Fax: Email address: Home page address:

Mailing address:

Comments:


Enclosure (9)

ENC (9)-5

Site Physical Security Manager: Name: Commercial phone: After duty hours: DSN Phone: Fax: Email address: Home page address:

Mailing address:

Comments: Site COMSEC Custodian: Name: Commercial phone: After duty hours: DSN Phone: Fax: Email address: Home page address:

Mailing address:

Comments: Site ADPE Custodian: Name: Commercial phone: After duty hours: DSN Phone: Fax: Email address: Home page address:

Mailing address:


Enclosure (9)

ENC (9)-6

Comments: LOGISTICAL AND SITE PHYSICAL SECURITY CHECKLIST: 1. This checklist is a guide to ensure the right questions are asked pertaining to shipping, storage and receipt of equipment into and out of the exercise location. Detailed addresses and POC information is key for follow up action and correspondence. a. Required shipment arrival date at site: b. Loading/unloading facilities availability and include building # and address. Include special instructions if required (on-site): c. Is loading/unloading facility protected from inclement weather? d. Forklift and/or pallet jack availability: e. Transportation (coordination procedures/additional points of contact): f. United Parcel Service/FedEx/DHL points of contact and specific addresses/phone numbers, if different from above shipping information


Enclosure (9)

ENC (9)-7

g. Location and procedures for temporary storage of shipping containers: h. Customs requirements (if international): i. What are site access policies j. What are normal hours of operation for site during the week and on weekends? k. Are there special requirements for military or contractor personnel access to post or base? What are the site normal working hours? Is the facility accessible for work after normal working hours? The survey team can get forms that need to be filled out if necessary and hours for vehicle registration, etc.

l. Addresses and Telephone/Fax numbers for Security Clearances and Visit Requests

m. Recommended arrival airport

n. Recommended lodging for survey team

o. Passport/Visa requirements

p. International Drivers license requirements


Enclosure (9)

ENC (9)-8

q. Country Clearance requirements

r. Special immunization/medical requirements

s. Customs procedures ADMINISTRATIVE EQUIPMENT AND SUPPLY Supply Point of Contact: Name: Commercial phone: After duty hours: DSN Phone: Fax: Email address: Home page address:

Mailing address:

Alternate: Commercial phone: DSN phone: Email address: Comments: ADMINISTRATIVE EQUIPMENT AND SUPPLY CHECKLIST JWFC will ship a footlocker of administrative supplies, but in the event demand exceeds shipped quantity or new requirements arise, cooperation and assistance at the site is needed to fulfill these requirements. Availability of the following should be assessed during the site survey:

ITEM Y/N Number ITEM Y/N Number ITEM Y/N NumberPens Floppy

disks Pencils

Projector Note paper Power


Enclosure (9)

ENC (9)-9

Screens strips Binders Tape Paper White boards

Staplers Shredders

UPS: Building Portable

Copiers Printer cartridges

Toner Other Other COMMAND, CONTROL, COMMUNICATIONS, COMPUTERS, AND INTELLIGENCE SYSTEMS Site C4I Technician Point of Contact: Lead Tech: Commercial phone: After duty hours: DSN phone: Fax: Email address: Home page address:

Mailing address:

Alternate: Commercial phone: DSN phone: Email address: Alternate: Commercial phone: DSN phone: Email address: Comments: COMMAND, CONTROL, COMMUNICATIONS, COMPUTERS, AND INTELLIGENCE SYSTEMS CHECKLIST 1. What is the existing method for C4I systems connectivity to the SIPRNET?


Enclosure (9)

ENC (9)-10

2. What types of C4I systems assets does your site currently possess (Global Command and Control System, All Source Analysis System, TCO, Joint Maritime Command Information System, etc.)? 3. C4I Systems Table

C41 SYSTEMS HARDWARE REQ’TS

PRINTER REQ’TS

CONNECTIVITY DETAILS

QUANTITY SOFTWARE VERSION

LOCATION

GCCS-J/M/A TBMCS ADSI C2PC MCS ASAS AFATDS AMDWS ADOCS TAIS CSSCS/BCS3 C2PC IOS JDISS OTHER

VIDEO TELECONFERENCING Site VTC Technician Point of Contact: Lead Tech: Commercial phone: After duty hours: DSN phone: Fax: Email address: Home page address:

Mailing address:

Alternate: Commercial phone: DSN phone: Email address: Alternate:


Enclosure (9)

ENC (9)-11

Commercial phone: DSN phone: Email address: Comments: VIDEO TELECONFERENCING CHECKLIST 1. Video teleconferencing requirements (VTC). JWFC personnel require an area located near the senior controllers’ white cell (if site is a JECG response cell) and large enough to comfortably accommodate 15-20 people that can be set aside as a temporary video teleconferencing studio. JWFC typically runs (standards) H.323, 384, FCIF, 30 fps. a. What existing VTC capabilities are already in place and available for time-share or committed JECG use? b. Type of crypto: c. Type of connectivity (leased T-1, ISDN, FTS2000, DVGS): d. Brand and protocol of in-house VTC equipment: e. If the JNTC Polycom VTC suite is to be installed in this facility, in what bldg/room? Who will cable? 2. There is or is not a requirement for a separate JECG/White Cell video teleconferencing center to be deployed to this site. It will be located in building ________, room number ___________.


Enclosure (9)

ENC (9)-12

VOICE AND DATA TELECOMMUNICATIONS Site Senior Communications Point of Contact: Lead Tech: Commercial phone: After duty hours: DSN phone: Fax: Email address: Home page address:

Mailing address:

DISA Representative:

Commercial phone: DSN phone: Email address: Alternate: Commercial phone: DSN phone: Email address: Comments: Site Network Engineer Point of Contact: Lead Tech: Commercial phone: After duty hours: DSN phone: Fax: Email address: Home page address:

Mailing address:

Site IS Engineer Point of Contact: Lead Tech: Commercial phone: After duty hours: DSN phone:


Enclosure (9)

ENC (9)-13

Fax: Email address: Home page address:

Mailing address:

VOICE AND DATA TELECOMMUNICATIONS CHECKLIST 1. DEMARC point. Where will the exercise circuit terminate? Building and room number: _________________ a. Can the DMARC point handle multiple circuits?___________.

b. What is the distance from the DMARC to the POD? c. What is the connection type from the DMARC to the POD? (copper, fiber, media type) d. Are copper or fiber modems required to extend T-1 lines from the DMARC to the POD and if so who will provide? e. What is the power breaker rating where the POD will be located? f. If more than one building is involved, what is the building-to-building connectivity? (copper, fiber) g. What is the room to room connectivity? (copper, fiber) h. If room or building connectivity is fiber, what is the media type? (ST, SC, MTRJ) i. What type patch panels are present at the location? (copper, fiber, media type) j. Can existing LAN infrastructure be isolated for JWFC use? 2. Voice grade communications lines. Determine the number and location of all currently installed voice grade telephone lines (DSN and commercial access). a. How many existing telephones phones in the area are available for JECG exercise purposes and what are their capabilities (DSN, commercial long distance, commercial local)?


Enclosure (9)

ENC (9)-14

b. What is the upper limit on the number of commercial phone lines at the proposed exercise location? What is the procedure for billing long distance non DSN calls? 3. List the amount and types of available commercial communication equipment. (Example: STU-III phones, POTS, secure fax devices, etc.) 4. Create a LAN Capability Map. This map will depict the network architecture / physical routing and key equipment locations depicting modified capabilities needed to support the envisioned network configuration. This map will depict proposed LAN connectivity between the POP for WAN network services and the individual systems and facilities that participate in the training event a. What edge device (router or switch) will this facility use to connect to the backside of the site Red Premise Router? b. How will the path between this facility and the site Red Premise Router be secured? Who is responsible for security? c. What equipment at this facility will connect to the JTEN? d. If VoIP phones will be installed in the facility, which bldg/room? Does the facility have its own VoIPs (make/model)? Does the facility wish to integrate its VoIPs with JWFC VoIPS? e. Does this facility have any video requirements (UAV video, range video, etc)? f. Does this facility use a network management system (HPOV, NeuralStar/JNMS, Foundary, Compaq insight, Spectrum, What’s Up Gold, CISCO Works, etc)?

g. Does this facility intend to use a DMZ between the site’s networks and the JTEN? If so, what? Who will control?


Enclosure (9)

ENC (9)-15

h. Does this facility use Network Address Translation (NAT) on its networks? i. Does this facility use multicast, unicast, or broadcast protocols on its networks? If so, what protocol and how are the routers/switches configured? j. Will this facility require access to SIPRNET through the JTEN-SIPRNET Gateway? Include applications, ports and protocols. k. Will this facility use any collaborative tools (IWS, DCTS, etc) that they intend to interface with JTEN? Do they have CIE servers? l. If a DIS/HLA Gateway is required will it be allowed into the facility (LINUX) POWER/ENVIRONMENTAL CONTROL Site Power Technician Point of Contact: Lead Tech: Commercial phone: After duty hours: DSN phone: Fax: Email address: Home page address:

Mailing address:

Alternate: Commercial phone: DSN phone: Email address: Alternate: Commercial phone: DSN phone: Email address:


Enclosure (9)

ENC (9)-16

Comments: POWER/ENVIRONMENTAL CONTROL CHECKLIST 1. Power availability/environmental factors: a. Network stability/known power outage problems: b. Outlet quantity/location requirements by location will be determined after the survey team returns. Any shortfalls will be sent to the host so arrangements can be made for additional power in time for exercise execution. c. Breaker ratings by room, floor, and building. d. Heat/air conditioning details: e. Uninterrupted Power Supply availability (building and portable): MAPS, CHARTS, BUILDING DIAGRAMS AND FLOORPLANS (attach)

SECTION C. MODELS AND SIMULATIONS CONFIGURATION CHECKLIST


Enclosure (9)

ENC (9)-17

Site Modeling and Simulation Point of Contact: Lead Tech: Commercial phone: After duty hours: DSN phone: Fax: Email address: Home page address:

Mailing address:

Alternate: Commercial phone: DSN phone: Email address: Alternate: Commercial phone: DSN phone: Email address: Comments: WORKSTATION WORKSHEET EQUIPMENT

SOURCE W/S Required JWFC REMOTE

ALSP AIR MODEL GIAC GROUND MODEL INTEL MODEL AMPHIBIOUS MARITIME TACSIM ? JECG LAN PCs PRINTERS LOGISTICS? JSWS SIMPLE ANALYSIM


Enclosure (9)

ENC (9)-18

JDLM SELS REMOTE SITE HARDWARE ASSETS WORKSHEET EQUIPMENT MODEL QUANTITY Servers PCs SUN Workstations Laptops HP Workstations Cabling/drops required:

SECTION D. INTELLIGENCE SYSTEMS AND SCIFS Site Intelligence Point of Contact: Lead Intel Planner: Commercial phone: After duty hours: DSN phone: Fax: Email address: Home page address:

Mailing address:

Alternate: Commercial phone: DSN phone: Email address: Alternate: Commercial phone: DSN phone: Email address: Comments:


Enclosure (9)

ENC (9)-19

INTELLIGENCE SYSTEMS CHECKLIST 1. What is the separation distance between the response cell and the training audience? 2. What will be the security classification of the intelligence spaces? 3. Will classified storage be available during the exercise? If so, where? 4. Will a DOD safe be provided to the response cell? Who will sign for the safe? 5. What is the storage of classified material policy regarding intelligence spaces? 6. Will a shredder be provided to the response cell? 7. What is classified destruction policy during the exercise? 8. Will a sensitive compartmented information facility be required for exercise control? If so, who will lead the accreditation process? 9. What simulations will be at the response cell? Where will the Tactical Simulation be located in reference to the Air Warfare Simulation Model? 10. Will the site provide National Imagery and Mapping Agency (NIMA) products to the response cell?


Enclosure (9)

ENC (9)-20

SECTION E. INTERIM AUTHORITY TO OPERATE REQUIREMENTS

1. IATO Contacts at JWFC COMM: 757.203.7788

DSN: 668.7788 FAX: 757.686.7967 JNTC Network Security Manger COMM: 757.203.7879 DSN: 668.7879 JWFC IAM COMM: 757.203.7477 DSN: 686.7477

2. To extend the JTEN to a site we will need to following documents: •Interim Authority To Operate (IATO) – if site-owned equipment is connecting to the

JTEN or an Intent to Protect letter – if no site-owned equipment is connecting • Network diagrams – a high level drawing of how the JTEN is extended through the site

YOUR LETTER HEAD Date:

From: YOUR COMAND To: USJFCOM, Joint Warfighting Center JTTG Subj: CERTIFICATION OF AUTOMATED INFORMATION SYSTEMS/NETWORK TO PROCESS AND TRANSMIT DATA DURING EVENT 1. This site fully meets the Automated Information Systems (AIS) security requirements of established federal, DOD, and (BRANCH if required) policies for administrative, cryptological, physical, personnel, information, and special intelligence security. 2. Having reviewed the AIS topology for the (name of location, building ###, Base name, State), it is determined that all participants Automated Data Processing (ADP) systems/networks (and VTC systems) are at an acceptable level of risk to process up to and including yyyyyy data. Based on that determination, Interim Authority To Operate (IATO) and interconnect these systems/networks during (EXERCISE NAME) system testing through ENDEX is granted. 3. All Classified magnetic media associated with this exercise will be removed and stored in approved containers when workspaces are not manned unless the area is cleared for open storage of Secret Classified material. 4. We acknowledge and consent to JWFC conducting an initial vulnerability assessment and periodic unannounced vulnerability assessments on systems connected to the JWFC network infrastructure to determine the security features in place to protect against unauthorized access or attack. 5. This IATO will expire upon removal of equipment at the end of (EVENT) or sooner if there are modifications which change the security posture or status. These modifications must be reviewed by the equipment owner or host site and agreed to in writing prior to implementation.


Enclosure (9)

ENC (9)-21

6. Point of contact is name DSN ###-#### or commercial (###) ###-####.

SIGNATURE BLOCK OF YOUR COMMAND’S DAA (DESIGNATED APPROVING AUTHORITY)

Date:

YOUR LETTER HEAD

From: YOUR COMAND To: USJFCOM, Joint WarFighting Center, JT-60 Subj: Intent to Protect equipment provided for (EVENT). 1. This letter is a declaration of our Intent to Protect the LAN and equipment provided by Joint WarFighting Center during (EVENT). 2. This site or space fully meets the security requirements of established federal, DOD, and (your Command) policies for processing and storing data at the highest classification of the LAN or equipment. Access to these spaces will be limited to those personal who are cleared to the highest level of the LAN or equipment and who posses the required need to know. This Command will not allow anyone to make modifications to the equipment configuration without the equipment owner or host site’s knowledge and approval. 3. All classified magnetic media and crypto will be removed and stored in approved containers when workspaces are not manned, unless the area is cleared for open storage of this level classified data.

4. This letter will expire upon removal of equipment at the end of (EVENT) or sooner if there are modifications which change the security posture or status. These modifications must be reviewed by the equipment owner or host site and agreed to in writing prior to implementation. 5. Point of contact is name DSN ###-#### or commercial (###) ###-####. SIGNATURE BLOCK OF YOUR COMMAND’S FACILITY OR ADP

5. Request to Connect Template

YOUR LETTER HEAD Date:

From: Command To: USJFCOM, Joint Warfighting Center, JT-60 Subj: Request to Connect for (Event) 1. To participate in (EVENT) the (Command) will provide (Systems). The technical information on these systems is listed below. For (EVENT), the equipment will be located at the Joint Warfighting Center, Suffolk, VA.


Enclosure (9)

ENC (9)-22

Qty Equipment S/N or

Plant Accnt # OS Software

2. Having reviewed the security measures currently implemented in the areas of security management, software, hardware to include all required security patches, IAVA’s and mandated DoD lockdowns it is determined that these systems are at an acceptable level of risk to process up to and including XXXXXXXXXX level data. 3. Accordingly, I grant interim approval to operate these systems in support of EVENT. This IATO applies when these systems are operated within the bounds established by their normal CONOPS or other security documentation. 4. We acknowledge and consent to JWFC conducting an initial vulnerability assessment and periodic unannounced vulnerability assessments on systems connected to the JWFC network infrastructure to determine the security features in place to protect against unauthorized access or attack. 5. This IATO will expire at the conclusion of EVENT, or sooner if there are significant modifications which change the security posture or accreditation status. Any system changes must be reviewed by the DAA and approved in writing prior to implementation. 6. Point of contact is name DSN ###-#### or commercial (###) ###-####.

SIGNATURE BLOCK OF YOUR COMMAND’S DAA (DESIGNATED APPROVING AUTHORITY)


Enclosure (9)

ENC (9)-23

SECTION F. SAMPLE TECHNICAL

MEMORANDUM OF AGREEMENT BETWEEN

UNITED STATES JOINT FORCES COMMAND AND

PARTICIPATING REMOTE SITE 1. Purpose This Technical Memorandum of Agreement (MOA) sets forth a set of predefined terms and conditions. It will outline the equipment and/or services that will be provided by the United States Joint Forces Command (USJFCOM), Joint Warfighting Center (JWFC) during any training event or exercise as well as the equipment and/or services that will not be provided by JWFC. Any equipment and/or services not provided by JWFC then become the sole responsibility of the participating host remote site. In addition, this MOA initiates and formalizes agreement of terms between JWFC and the participating remote site for the safe storage of cryptographic equipment; while on-line and off-line, and key material, during all testing and training events. 2. Policy a. JWFC Responsibilities. Assist the remote site with identification of site requirements. Provide the workstations and telecommunications equipment necessary to support distributed models and simulations, and USJFCOM exercise and control group video teleconferencing suite equipment. b. Remote Sites’ Responsibilities (1) Designate a remote site officer in charge (OIC) to coordinate the connectivity for all secure and non-secure voice grade telephone lines, fax lines, and communications pod dial-in line and associated equipment (telephones, secure telephone unit IIIs, FAX machines,) required for efficient facilitation of all testing and training evaluations; with the exception of the equipment that the communications pod dial-in line will terminate into which will be provided by JWFC. (2) Provide all necessary tactical and exercise control radio frequency communications equipment for the training exercise. (3) Provide all necessary command, control, communications, computers and intelligence (C4I) systems for the training audience to command and control their forces. (4) Provide storage equipment and keying material required for secure communications over T-1 trunk lines between the remote site and JWFC.


Enclosure (9)

ENC (9)-24

(5) Establish a policy and/or facility in accordance with DOD communications security guidelines for the safe keeping of the cryptographic equipment and key material during off-line and on-line operations. (6) Coordinate shortfalls through the supporting component. 3. Coordinating Instructions a. Communications pod dial-in Line. Provide a dedicated 4-wire voice-grade telephone line for connection to the communication equipment pod. This is to allow for dial-up capability for troubleshooting and reconfiguration in the event of trunk failure. b. Trouble Line. Provide a dedicated 4-wire voice-grade telephone line and telephone physically near the communications equipment for use by the communications technician as a troubleshooting aid. This line is to be long-distance and DSN capable. c. Ensure that correct cryptographic keying material is on hand for testing and operation of trunk encryption devices on a 30-minute recall basis. d. Support maintenance and testing of communication equipment by allowing maintenance and operations personnel to access equipment on a 24-hour basis. e. Response cells will leave equipment in place from the systems test through the conclusion of the joint training system Phase III – Execution of the event or exercise. Exceptions will be managed on a case-by-case basis through the USJFCOM JW500. ______________________ ________________________ JWFC, JWFC Representative Site Command Representative


Enclosure (10): Scenario Development

1. Exercise and Training Objectives. Analyze the exercise and training objectives and other senior leader guidance and create the main features of the intellectual (as opposed to physical) environment in which the training audience will operate. 2. Documents. Create the Road-to-Crisis (RTC), Operational Environment Overview, or Ground Truth Documents that describe the genesis of the start of exercise (STARTEX) situation. Ground Truth documents may also describe events and situations after STARTEX. Other functional areas or agencies may supplement the Scenario-MSEL retains primary responsibility unless relieved by the government Event Planner. a. Create and coordinate the major details of the STARTEX situation, to include: (1) The overall strategic setting, including an overview of relations with the U.S. and its coalition partners, U.S. civilian agencies, international and non-governmental organizations (IO/NGO), and other states in the region as applicable. (2) The major problems faced by the local authorities, such as insurgencies, terrorists, internal political opposition, economic challenges, social frictions, need for humanitarian assistance/disaster relief (HA/DR), and displaced persons, refugees, and evacuees (DPRE). (3) The training audience mission. b. Create country studies, military capability studies, and threat descriptions for imaginary scenarios. c. Manage and facilitate the creation of the storylines (or threads), and the Master Scenario Event List (MSEL) injects. See Scenario-MSEL Standard Operating Procedure 1, Master Scenario Event List Development, for details. 3. Coordination a. Coordinate Interagency on the details of relations with the U.S. and its coalition partners (if any), U.S. civilian agencies, IO/NGO, and other states in the region. b. Coordinate with Forces and Intelligence for threat details, to include force levels, structures, and capabilities (conventional, unconventional, and asymmetric) as required. c. Coordinate with Forces on the Threat/OPFOR/SITFOR Campaign Plan, to include campaign objectives, levels of violence, etc., on DPRE movement, and on commercial maritime and air (CMA) activity. d. Coordinate with Sustainment on transportation, supply, deployment, and economic infrastructure details. e. Coordinate with information Operations on the information environment and infrastructure. f. Coordinate with the Joint Event Support Team (JEST) and the government Event Planner on the Program Objectives, Activities, and Milestones (POA&M) and Exercise Support Manning Document (ESMD). 4. Creating the Exercise Framework a. Determine and coordinate the sequence of major incidents that will occur during execution.


b. Facilitate and manage storylines based upon the sequence of major incidents. c. Support the storylines in the RTC or Operational Environment Overview. d. Create of facilitate creation of Ground Truth Documents if required. e. Coordinate with the government Event Planner on Blue Force levels. f. Coordinate with government planners on updates and revisions to environmental inputs. 5. Planning and Execution a. During exercise planning: (1) Create, maintain, and deliver the Scenario Overview Briefing to include the RTC, the STARTEX Situation, and the mission. (2) Create, maintain, and deliver the Storyline Briefing. b. During exercise execution: (1) Facilitate the Scenario Synchronization Meeting. (2) Manage dynamic scripting. (3) Coordinate with Threat/OPFOR/SITFOR on activities and levels of violence, on DPRE movement, and on white maritime and air (WMA) activity. (4) Coordinate and assist Response Cells in dealing with scenario issues and role-playing. (5) Coordinate on responses to training audience Requests for Information (RFIs). c. Provide Scenario-MSEL expertise and progress reports to the JEST, government Event Planners and Desk Officers, and the Exercise Control Group as required. 6. Training. The Community of Practice program includes Scenario Manager training.


Enclosure (11): Master Scenario Event List Development 1. Roles and Responsibilities

a. Joint Chiefs of Staff (JCS). The Joint Staff maintains overall responsibility for JMSEL tool deployment, support, and adoption across the Services and commands.

b. JCS Sponsored Joint Exercises. The JWFC has operational responsibility for use of JMSEL in JCS-sponsored joint exercises (normally two exercises per supported command per year).

c. Geographical Combatant Commands. JWFC MSEL support for these exercises includes the JMSEL server, MSEL Manager, database administrator, and system administrator. JWFC does not normally provide JMSEL support to other exercises. JWFC-supported exercises are normally executed using the JMSEL servers located at the JWFC in Suffolk, Virginia. If a JWFC-supported exercise requires the use of a different JMSEL server, special arrangements must be made through the Joint Exercise Support Team (JEST).

d. Training Audience. Each headquarters involved in a JWFC-supported exercise provides SMEs to act as trusted agents during the exercise design process. The SMEs, with the coordination and guidance of the MSEL Managers, create the individual events and write the implementers that in large part drive the exercise. Supported commands and joint task forces (JTFs) may provide their own MSEL Managers to work with the JWFC MSEL Manager. 2. Administration

a. JTIMS. JMSEL is subject to configuration management under JTIMS. The JTIMS Program Manager designates configured items. Changes to configured items are authorized by the CCB and controlled by the JTIMS Program Manager. Changes approved by the CCB will be applied to all JMSEL servers. Generally, only changes required to set default values to those appropriate to the local installation may be made without CCB approval.

b. Software Updates. JMSEL has been stabilized at Version 2.5 Release 2007-04-06. No further changes are anticipated.

c. Hardware Changes. The system administrator coordinates hardware changes with the database administrator to minimize disruption to exercise planning and execution.

d. Troubleshooting. The database administrator, the MSEL Manager, and the system administrator coordinate as required to troubleshoot any problems.

e. Connectivity. The NIPRNET JMSEL server must be available to all approved users including Department of Defense, non-DOD Federal government, and state and local agencies. The SIPRNET JMSEL server must be available to all personnel with SIPRNET access. Coalition access to classified exercises is worked on a case-by-case basis.

f. Backups. The system administrator coordinates backups of the JMSEL databases. MSEL Managers will export copies of their exercise databases frequently enough so that recovery is possible after a hard drive crash or other server failure. 3. Database Administration

a. MSEL Manager and User Privileges. Every exercise in JMSEL will have a JWFC MSEL Manager assigned. JWFC MSEL Managers may have access to any exercise that is not subject to originator control (ORCON). JWFC personnel may have user access to any exercise that is not ORCON. Non-


JWFC MSEL Managers may have MSEL Manager access only to their own exercises, but may have user access to other exercises at the discretion of the JWFC MSEL Managers for those exercises. MSEL Manager and user privileges for non-JWFC personnel may be revoked at the discretion of the JWFC Event Planner, supported command project officer, or the exercise Chief (or Senior) Controller.

b. Creating the Exercise Database. A JMSEL Administrator copies or creates new exercises at the request of the JWFC MSEL Manager. The JMSEL Administrator ensures the Manager Settings are correct and adds the MSEL Manager to the exercise points of contact (POC) list and the MSEL MGR Cell.

1) The MSEL Manager sets up the framework within which the exercise will be constructed, such as training audiences, joint mission essential tasks (JMETs), training objectives, and Inject Cells. The MSEL Manager also grants database access to the SMEs, who in turn develop the events and implementers. Implementers are telephone scripts, e-mails, record message traffic and other inputs that will drive the exercise and achieve the training objectives.

2) During exercise execution, JMSEL provides tools for tracking progress and for reviewing, modifying, and releasing implementers and routing them to the training audience. The system also offers limited support for lessons learned development and data gathering during post exercise operations.

3) The US Joint Forces Command (JFCOM) Joint Warfighting Center (JWFC) maintains classified JMSEL servers at https://jmsel.exer.jntc.smil.mil and unclassified servers at https://jmsel.jwfc.jfcom.mil.

4) Click on the appropriate server for the desired Geographical Combatant Command.

5) Click on “JMSEL Welcome” for access to the Users Guide, Frequently Asked Questions, and Points of Contact.

6) Click on “JMSEL Application” for the login page. On the login page, click on "Start Tour" for an overview of JMSEL functions.

c. Importing Exercises. Only a JMSEL Administrator may import exercises. MSEL Managers coordinate with a JMSEL Administrator for the importation of any needed exercise.

d. Archiving Exercises. Exercises will be archived within ten working days after end of exercise.

e. Database Maintenance. The database administrator reviews the databases periodically to check for errors and remove unneeded POC entries. Non-JWFC POCs who are not assigned to an active exercise will be routinely deleted. The database administrator will coordinate with the MSEL Managers to delete unneeded exercise archives and preserve server capacity.

f. Classification. MSEL Managers brief users on the proper use of classification markings and review exercise databases to ensure legal and correctly formatted classifications are applied to events and implementers. Users are responsible for the correct classification of events and implementers.

1) For Official Use Only (FOUO). FOUO will only be used in accordance with paragraph C4.1.1 in DOD Regulation 5400-7R, "Department of Defense Freedom of Information Act (FOIA) Program."

2) Security Violations. If classified information is inadvertently placed on an unclassified JMSEL server or if information classified above SECRET is placed on a SIPRNET JMSEL server, the Security Officer will be advised and will take the appropriate steps. 4. MSEL Manager

a. Dropdown Lists. The JWFC MSEL Manager creates the exercise framework by entering appropriate information for all the dropdown lists pertinent to the exercise as follows.


1) Derive the Inject Cells from the structure of the Joint or Combined Exercise Control Group

(JECG or CECG) and assign POCs to them.

2) Obtain exercise training audiences, JMETLs, and training objectives from the supported command Event Planner and do not change them without the approval of that officer.

3) The Send From list is scenario-dependent. Much of it can be derived from the warning order or planning order. It represents: (a) the top echelon below the training audience from the Blue Force list, such as Air Force forces (AFFOR) or a carrier strike group; (b) echelons above the training audience, such as the Chairman of the Joint Chiefs of Staff or Secretary of Defense; (c) DOD and non-DOD Federal agencies, such as the Defense Logistics Agency or Department of State; and (d) international and nongovernmental organizations (IO/NGO) such as the United Nations or International Committee of the Red Cross.

4) The Send To list is derived from the organizations within the training audience.

5) Primary Themes are derived in a manner appropriate to the exercise. They may be directed by the supported commander or developed from the training objectives by the MSEL Manager and refined by the Inject Cells at the MSEL Development Conference (MDC).

6) Storylines (or Threads) are derived from the training objectives at the MSEL Development Conference (MDC).

7) Classifications are created in accordance with subparagraph 5f above. Only "UNCLASSIFIED" may be applied to events on a JWFC NIPRNET JMSEL server.

8) Greenwich Mean (Zulu) Time will always be entered with an offset of zero (0).

9) Injection Days, Phases, Inject Levels, and Plain Language Addresses (PLAs) are entered as required.

b. Event Numbering

1) Use of a standard numbering convention makes it easier to navigate the MSELs for various exercises and reduces confusion when events are imported from one exercise to another.

2) The numbering convention uses six digits. The first two digits represent the event drafter’s command, the next two digits the Inject Cell that created the event, and the last two digits are managed by the Inject Cell. Please note that the leading “0” is required to make the numbers sort correctly in the database. The six digits may be followed by an extension consisting of a hyphen and two digits (e.g., -01). The use of any other extension format will cause errors in JMSEL.

a) Digits one and two. Command identifiers are in accordance with Joint Staff procedures. Use the identifier for the command that is sponsoring the exercise.

00xxxx Federal Emergency Management Agency (FEMA) 01xxxx US Army 02xxxx US Navy 03xxxx US Air Force 04xxxx US Marine Corps 05xxxx US Coast Guard 06xxxx National Guard Bureau 07xxxx US European Command (USEUCOM) 08xxxx US Joint Forces Command (USJFCOM) 09xxxx US Pacific Command (USPACOM)


10xxxx US Central Command (USCENTCOM) 11xxxx US Southern Command (USSOUTHCOM) 12xxxx US Transportation Command (USTRANSCOM) 13xxxx US Africa Command (USAFRICOM) 14xxxx North American Aerospace Defense Command (NORAD) 15xxxx US Special Operations Command (USSOCOM) 16xxxx US Northern Command (USNORTHCOM) 17xxxx US Strategic Command (USSTRATCOM) 18xxxx Defense Communications System 19xxxx Defense Finance & Accounting Service (DFAS) 20xxxx Defense Information Systems Agency (DISA) 21xxxx Defense Logistics Agency (DLA) 22xxxx National Geospatial-Intelligence Agency (NGA) 23xxxx Defense Threat Reduction Agency (DTRA) 24xxxx National Communications System 25xxxx National Security Agency (NSA) 26xxxx National Security Council (NSC) 27xxxx Department of State (DOS) 28xxxx Office of the Secretary of Defense (OSD) 29xxxx Joint Staff 30xxxx Armed Forces Medical Information Command 31xxxx Armed Services Blood Program Office 32xxxx Global Patient Requirements Movement Center 33xxxx Military Postal Services Agency 34xxxx Military Entrance Processing Command 35xxxx Selective Service System (SSS) 36xxxx Defense Contract Management Agency b) Digits three and four. Inject Cell that created the event. xx00xx J0, Combatant Commander xx01xx J1, Personnel xx02xx J2, Intelligence xx03xx J3, Operations, Information Operations (IO), JPOTF xx04xx J4, Sustainment, Combat Service Support (CSS), USTRANSCOM, AMC xx05xx J5, Plans xx06xx J6, Communications, USSTRATCOM xx07xx J7 xx08xx J8 xx09xx J9 xx10xx JFLCC/ARFOR xx11xx JFMCC/NAVFOR xx12xx JFACC/AFFOR xx13xx MARFOR xx14xx JSOTF/SOF xx15xx Personnel Recovery xx16xx As Required xx17xx Threat/OPFOR/SITFOR xx18xx Public Affairs Office(PAO), Media xx19xx Interagency, Pol-Mil, Civil Affairs, JCMOTF xx20xx and above used as required

c) Digits five and six. Managed by the Inject Cell. The numbers represent storylines as

determined during the MSEL build. Each storyline can have 101 associated events (no extension plus extensions -00 through -99).

d) Examples.


080212 USJFCOM exercise, Intelligence event, Intelligence Storyline 12. 080212-01 Follow-on event to 080212 further developing Intelligence Storyline 12. 171203 STRATCOM exercise, AFFOR event, AFFOR Storyline 03. 171203-03 Follow-on event to 171203 further developing AFFOR Storyline 03.

c. MSEL Development. The purpose of the MSEL build is to translate the approved training

audience JMETLs, exercise objectives, and training objectives into the events and implementers. JWFC Event Planners and MSEL Managers lead this process. Supported command and JTF MSEL Managers, if appointed, coordinate the events and implementers created by their respective headquarters, but do not change the structure of the exercise.

1) Approval of User Access. All MSEL information is sensitive and much of it is classified. Access is not automatic. It requires the same justification and careful consideration as access to any other sensitive and/or classified information and access will be kept to a minimum consistent with operational requirements. Users will normally only be granted access to exercises in which they are directly involved and such other exercises as the MSEL Manager deems useful to the MSEL build. MSEL Managers regularly check applications for access to exercises and ensure applicants have a need to know. Supported command and JTF MSEL Managers may approve user level access and assign users to Inject Cells. Users can expect that their access to each exercise will be terminated upon conclusion of the exercise.

2) MSEL Development Conference (MDC). The purpose of the MDC is to coordinate the inputs of the SMEs to ensure the MSEL accomplishes the exercise and training objectives established by the supported commander. This opportunity is also normally used to introduce the JMSEL tool to the SMEs and give them sufficient skill in its use to create the MSEL. The MDC is hosted by the JWFC Event Planner and/or the supported command project officer and facilitated by the JWFC MSEL Manager. The conferees will require a minimum of three days of focused effort to complete the necessary training on the MSEL process and the JMSEL tool and to coordinate and structure the MSEL and supporting implementers.

a) Scheduling. While the MDC can be held anytime after the exercise and training objectives are determined, it may be best to schedule it after the Middle or Main Planning Conference (MPC), since by that time most of the other key planning factors for the MSEL (forces and JECG structure) should be finalized. The MDC is often scheduled as a discrete event immediately following the MPC, which reduces the costs of conducting the conference and minimizes the SMEs' travel and time away from their duty stations. It is not practical to conduct the MDC concurrently with a planning conference or event test because the same representatives are required at both.

b) Calling Message. The JWFC Event Planner and the project officer at the supported command, advised by the MSEL Manager, determine the invitees to the conference. A calling message addressed to each of the participating commands, agencies, and offices requests them to send trusted agents who are SMEs in their areas of responsibility. Given the dynamics of group interaction and the finite capability of facilities to host these events, the invitation is normally limited to a few personnel from each functional area, the total desired attendance being about 50 personnel. Much more than 50 attendees become difficult to accommodate. The message announces the location, time, and date of the conference and contains information on how to pre-register, where to stay, how to travel to and from the site, and other administrative details. The message should advise attendees to register in the JMSEL tool and provide instructions for doing so. The JWFC Support Team (JST) Scenario-MSEL Section has sample calling messages.

c) Trusted Agents. A trusted agent is a unit SME who will not be assigned to a training audience staff during exercise execution. The trusted agents who develop the MSEL should be assigned to Inject Cells during exercise execution. At this conference, trusted agents use their detailed functional area knowledge to create the specific events that will occur during the exercise. Units determine which functional areas (operations, plans, and logistics) need to be represented based on the training the unit


plans to receive during the exercise. Unit-specific questions on representation should be referred to the project officer or MSEL Manager.

d) Site Setup. The facility hosting the conference will require a room large enough to accommodate the expected attendance and have sufficient break-out space for sidebar meetings, a computer local area network of 25 to 50 desktop or laptop computers that can access JMSEL using Internet Explorer, and the normal conference audio-visual aids, such as white boards, wall displays of large charts, video projection for computer-based briefings, and so forth. Breakout rooms for information operations and intelligence are very desirable because of the classification and releasability of some of their discussions. At the JWFC, the preferred site is the Management Information Center (MIC) Overflow room, although Test Bays 14 or 15 can be used. Suitable breakout rooms include conference rooms 2100, 2200, and 2026, Conference Rooms in Test Bays 11, 13, and 14, the VTC Theater, and room 2067. The MSEL Manager prepares a MSEL development protocol briefing that contains the exercise objectives, training objectives, themes, and MSEL numbering convention. These files are usually enlarged into wall-size charts for display in the main conference room. Finally, the MSEL Manager prepares the agenda for the conference, subject to government Event Planner approval.

e) Conference Support. The MSEL Manager coordinates with the JEST for the conference room, breakout rooms, computer support, and audio-visual support. For conferences hosted at the JWFC, coordinate with the JEST. For conferences hosted elsewhere, the supported commander provides facilities, audio-visual equipment and computer workstations and networking as required.

f) Briefings and Training. The conference begins with the welcome and administrative briefings, followed by a scenario overview (including start of exercise [STARTEX] conditions, major events, and the desired end state), functional and Service component briefings, operation plan or concept plan briefings as necessary, briefings on Red, Blue, and situation forces, a briefing on the MSEL development protocol, and JMSEL training. This part of the conference normally takes up the first half day, but can take longer, particularly if coalition services provide briefings on their capabilities and plans. Translating the briefings into another language will approximately double the time required.

g) Working Group Meetings and Crosstalk. The key to a successful MDC is the storyboarding process. This process enables the SMEs to create a logical, coherent, and plausible environment for the training audience. Working groups are organized based on the anticipated Inject Cell structure and meet to strategize their MSEL input. Assigning specific training objectives to each of the working groups may help to focus their efforts. The working groups analyze the training objectives to determine the implied tasks, then put the tasks in a logical order for the training audience to work through. For each major task, a storyline, or sequence of events, is built around one or more key events. Key events are those which directly cause the training audience to perform the task implied by a training objective. The key event should be preceded by “enabling” events that set the stage for the key event and followed by “supporting” events that carry the sequence to a logical conclusion.

h) Storyboard briefings. After the working groups have developed their storyboards (half a day to a day of work), the conferees meet in plenary session for the working group leads to brief their storyboards. This meeting enables the working groups to coordinate their efforts, eliminate conflicts, and leverage each others’ work.

i) MSEL Input. The group makes inputs via the JMSEL tool, beginning with the key events. Throughout the conference, the working groups continue to coordinate to eliminate conflicts and ensure there are not multiple similar events when a single event would accomplish the same goals.

j) MSEL Synchronization. The MDC ends by spending half a day synchronizing the inputs made so far. The MSEL is reviewed line by line in date-time-group order. The working group leads briefly discuss the timing and intent of each event, with emphasis on the training audience's expected action. The expected action is the primary tool for detecting conflicts as well as the main indicator of whether the training objectives are being met.


3) Post-MDC. Following the MDC, SMEs return to their duty stations and complete the drafting of the MSEL events and implementers in the JMSEL tool. Coordination between SMEs of the various Inject Cells is essential to building a coherent and plausible exercise. The MSEL Managers will continuously review the developing MSEL and provide coordination and advice as needed, but this part of the process is ultimately dependent on the commitment of the participating commands to the success of the exercise. The SMEs must complete the events and implementers from home station prior to the MSEL Synchronization Conference.

4) MSEL Synchronization Conference (MSC). The purpose of this conference is to review a MSEL that is close to its final form to ensure that it supports the JMETS and the exercise and training objectives, that coordination between Inject Cells has been accomplished, and that the inject dates and times of each event are reasonable. Attendance does not need to be as complete as for the MDC, but all the Inject Cells must be represented. At least the first 72 hours of the MSEL are reviewed line by line in date-time-group order. The Inject Cell leads briefly discuss the timing and intent of each event, with emphasis on the training audience's expected action. The expected action is the primary tool for detecting conflicts as well as the main indicator of whether the training objectives are being met. The MSC is often held immediately after and in conjunction with the Final Planning Conference to reduce travel cost, but more than about two months before execution the MSEL may not be mature enough to make the review worthwhile. At least four hours should be reserved for a thorough review.

d. Execution. During execution, the MSEL (or Event) Cell coordinates with the Chief (or Senior) Controller and the Inject Cells to ensure that the exercise and training objectives are met. The MSEL Cell as a rule consists of two or three people per shift. The JST Scenario-MSEL Section provides up to two people per shift and the remainder come from other sources. The position names vary among the commands, but the duties to be performed are fairly constant and should be formally divided among the members of the team, although the team members back each other up at all times. MSEL Cell duties include: (1) coordinate with the Chief (or Senior) Controller and the Inject Cells on the overall conduct of the exercise as it relates to the JMETs and training objectives; (2) review request for information (RFI) responses; (3) conduct a MSEL Synchronization Meeting for each shift; (4) review each implementer prior to sending it to the releaser or the training audience; (5) update the status of each event as it is executed; and (6) assist the Inject Cells in keeping up with their responsibilities and use of JMSEL. Sometimes the RFI Tracker is nominally a member of the MSEL Cell, but the duties of that position do not relate directly to the MSEL.

1) JECG Training. The MSEL Cell provides training on MSEL execution procedures and use of the JMSEL tool. The Scenario-MSEL Section has sample briefing slides. Each of these training sessions requires a minimum of one hour.

2) Mini-Exercise and Communications Exercise (MINIEX/COMMEX). JECG training will include a MINIEX and a COMMEX, which may be conducted simultaneously. The MSEL Manager develops the events for the MINIEX. The MINIEX/COMMEX serves three purposes for the MSEL process: (a) to practice with the JMSEL tool; (b) to test the functions of the JMSEL tool; and (c) to check communications, including e-mail addresses and telephone numbers, with the Inject Cells and the training audience. To prevent confusion the MINIEX should normally use events specially created for the purpose. It is important that all the Inject Cells communicate with their primary training audiences.

3) White Cell Meeting. Each shift usually will have both a White Cell Meeting and a MSEL Synchronization Meeting. If possible, the White Cell Meeting should come first, so that the decisions and guidance from it can be translated into action at the MSEL Synchronization Meeting. The Scenario Manager or MSEL Manager attends the White Cell Meeting.

4) Scenario Synchronization Meeting. There may be a short (15 to 20 minute) Scenario Synchronization Meeting prior to the MSEL Synchronization Meeting to discuss White Cell guidance and any needed storyline changes or additions, task appropriate personnel, and establish a timeline for completion.


5) MSEL Synchronization Meeting. The MSEL Synchronization Meeting serves to deconflict MSEL events and provide a vital frame of reference for the Inject Cells. The MSEL Cell lead conducts the MSEL Synchronization Meeting. Representatives of all the Inject Cells attend the MSEL Synchronization Meeting and brief the timing and intent of their events. Prior to STARTEX, there is usually a MSEL Synchronization Meeting that covers the first 48 to 72 hours of the exercise to identify any problem areas early. This initial meeting will take three to four hours. After STARTEX, the MSEL Synchronization Meeting normally covers the next 24 hours. This meeting should take no more than one hour. 5. JMSEL Server Support for Training Events

a. Types of Support

1) Planning Conferences. JMSEL server support for planning conferences is normally very limited. The MSEL resides on a server at the JWFC and is available for reference if needed. System and database administrator support is available only during normal JWFC duty hours unless special arrangements are made.

2) MSEL Development Conference. If reliable connectivity with the appropriate (NIPRNET or SIPRNET) JMSEL server at the JWFC can be established from the conference site, only laptop or desktop clients are needed. The number of clients required is determined by the MSEL Manager. If connectivity from the site is unavailable or unreliable, the JWFC will provide a laptop JMSEL server that can be used as the primary or backup server. Experience suggests that a laptop server works best with 12 or fewer clients. System and database administrator support is available only during normal JWFC duty hours unless special arrangements are made.

3) MSEL Synchronization Conference. The MSEL Synchronization itself can be run from a single computer and does not require multiple clients. If MSEL development is planned, requirements will be similar to the MDC. System and database administrator support is available only during normal JWFC duty hours unless special arrangements are made.

4) Event Execution. A great deal of planning and coordination goes into event execution and there are a wide variety of options. Normally, the MSEL will be hosted on a JWFC JMSEL server and system administrator support will be available 24 hours a day. If there is another JMSEL server, such as on a coalition wide-area network (COWAN), test its ability to send email at least three days prior to STARTEX. Database administrator services are rarely needed and are available only during JWFC normal duty hours unless special arrangements are made.

5) Help Desk. At present, there is no JMSEL Help Desk.

b. Scheduling Support. JMSEL support is scheduled by the JST Scenario-MSEL Section for conferences and by the appropriate JEST for exercises. 6. Training

a. MSEL Manager. The Community of Practice program includes MSEL Manager training.

b. User. MSEL Managers provide user training at conferences and exercises.

c. Manual. There is a users manual on the JMSEL Web site and there is a JMSEL Tour available from the login page.

d. Frequently Asked Questions (FAQ). There is a JMSEL FAQ on the JMSEL Web site.


Enclosure (12): Opposing Force/Response Cell 1. Opposing Force

a. The JWFC Forces Branch, a subordinate branch under the Operational Environment Team Lead in the JST, provides the opposing forces (sometimes referred to as the OPFOR/SITFOR Cell). This section will cover the manning, duties and responsibilities, processes and procedures, and information flow for use during joint events to include interaction with other joint or combined Exercise Control Group (ECG) cells.

b. Mission Statement. The Joint Warfighting Center (JWFC) Forces Branch provides a robust and realistic opponent that supports joint event training objectives. Specifically, the OPFOR/SITFOR cell portrays the traditional military, paramilitary, irregular military, insurgents, terrorists, or any other type of organizations representing opposing forces (OPFOR) or situational forces (SITFOR) as required by the scenario in the simulation. Secondary Missions: OPFOR/SITFOR cell portray the simulation commercial shipping and air assets normally operating in the AOI in support of the scenario. To this stage, the OPFOR/SITFOR cell will:

(1) Prepare and implement “the threat” for the training audience following the OPFOR Campaign Plan (approved by the Event Director or his designated representative).

(2) Ensure all OPFOR Campaign Plan activities support the master scenario events list (MSEL) as well as provide dynamic events as coordinated and approved by Senior Control.

c. Manning, Experience, Organization, and Responsibilities. (1) Manning.

OPFOR/SITFOR CELL ECG-197 COMOPFOR CELL LEAD(D) CIV JWFC JST ECG-198 DEPUTY COMOPFOR CELL LEAD(N) CIV JWFC JST ECG-199 OPFOR MARITIME CELL LEAD (D) CIV JWFC JST ECG-200 OPFOR MARITIME (D) CIV JWFC JST ECG-201 OPFOR MARITIME (N) CIV JWFC JST ECG-202 OPFOR AIR CELL LEAD (D) CIV JWFC JST ECG-238 OPFOR AIR (D) CIV JWFC JST ECG-239 OPFOR AIR (N) CIV JWFC JST ECG-240 OPFOR GROUND LEAD (D) CIV JWFC JST ECG-241 OPFOR GROUND (D) CIV JWFC JST ECG-242 OPFOR GROUND (N) CIV JWFC JST

The OPFOR/SITFOR cell is staffed 24/7 for the duration of the CPX: Sample Manning

(2) Experience. All members of the Threat team must be proficient with the simulation model being used. They must also be familiar with OPFOR campaign plan, MSEL, event training objectives, the JTF commander’s intent, and scenario and road to crisis documents. Each member of the team must also be familiar with the tactics, techniques, and procedures, military capabilities, and weapon systems employment of the OPFOR. As members of the JECG, the OPFOR/SITFOR team requires no special training during the JECG train-up period. Each member of the team will also be knowledgeable with the Command and Control Personal Computer (C2PC) system that replicates the Common Operations Picture (COP) and the joint master scenario events list (JMSEL) tool.

(3) Organization. The OPFOR Higher Headquarters (OPFOR HHQ) is normally located with the JECG to facilitate the close coordination required between Senior Event Control and BLUE response


cells with the OPFOR Commander. The OPFOR HHQ Cell is led by COMOPFOR. He serves as leader of the OPFOR. He may or may not have a Chief of Staff (COS)/ battle captain.

(4) Responsibilities.

(a) COMOPFOR/COS.

• Serves as the JECG single point of contact for OPFOR/SITFOR control and scripting issues.

• Supervises the efforts of the OPFOR/SITFOR Cell. • Monitors future operations (next 72 hours) of the OPFOR Campaign Plan. • Briefs Senior Event Control on possible OPFOR Military Courses of Action

(COAs) for the next 24 hours. • Recommends OPFOR military COAs for implementation to Senior Event

Control based on current BLUE activity. Executes OPFOR Military COAs selected by senior event control.

• Ensures OPFOR/SITFOR event activities are designed and controlled to facilitate achievement of all event training objectives through coordination with AAR, O/Ts, response cells and M&S personnel.

• Coordinates closely with other JECG representatives to guarantee the smooth integration of scripted events and model supported events into the event.

• Devises and implements solutions to OPFOR/ SITFOR related scripting or control problems that emerge which could adversely affect the event.

• Conducts daily White Cell brief on significant opposing or situational force activities.

• Represents the OPFOR/SITFOR cell at all required meetings (daily MSEL Synch, Commanders VTC, etc) to facilitate close coordination of OPFOR/SITFOR activities.

• Coordinates with AAR and O/Ts to assess impact of MSELs and achievement of training objectives.

• Determines, in coordination with O/Ts and AAR, when OPFOR/SITFOR activities should be closed out, modified or canceled.

• Provides inputs to the OPFOR Significant Events Log. • Briefs the ECG Event Director on current force ratios and the ability of OPFOR

forces to sustain the necessary operations to meet event and training related objectives.

(b) OPFOR Ground Commander:

• Develops the OPFOR Ground Campaign Plans in support of the event. • Conduct movements of operationally significant units in accordance with the

published OPFOR campaign plan and execution matrices. • Executes dynamic OPFOR injects as approved by COMOPFOR and senior

control. • Coordinates JMSEL events (response cell initiates) requiring model support

with appropriate response cell. • Coordinates (OPFOR initiates) with the Intelligence Cell in order to provide the

training audience with the appropriate intelligence indicators and warnings of significant force activities.


• Provides Ground significant force activities for daily White Cell briefing to COMOPFOR.

• Makes inputs to the OPFOR Ground, Significant Events Log. • Maintains current status of assigned units. • Develops BDA (ground truth reports) for COMOPFOR when requested. • Conducts shift change over briefings.

(c) OPFOR Air/Naval Commander: • Develops the OPFOR Air/Naval Execution Plan/Matrix in support of the event. • Conduct movements of operationally significant units in accordance with the

published and execution matrices. • Executes dynamic injects as approved by COMOPFOR and senior control. • Coordinates JMSEL events (response cell initiates) requiring model support

with appropriate response cell. • Coordinates with the Intelligence Cell in order to provide the training audience

with the appropriate intelligence indicators and warnings of significant force activities.

• Provides air and naval significant activities for daily White Cell briefing to COMOPFOR.

• Makes inputs to the OPFOR Air/Naval Significant Events Log. • Maintains current status of assigned units. • Conducts shift change over briefings.

The following processes apply to the simulation portion of the event:

(1) The OPFOR Campaign Plan provides the guidance and direction for all team members in the constructive (simulation) portion of the event execution. Team members have the authority to conduct operations IAW the approved plans. Actions not contained in the plans are not authorized and must be approved by COMOPFOR after consulting with the Chief Controller.

(2) Process 1: Ground Operations are per OPFOR Campaign Plan that has been approved by the event director. Ground operations will also be directed by model support per the event MSEL. Changes to the ground operations must be approved by COMOPFOR. All ROE changes will be approved by COMOPFOR.

(3) Process 2: Air Operations are per the OPFOR Air execution matrix that has been approved by the event director. Air operations will also be directed by model support per the event MSEL. Changes to air operations must be approved by COMOPFOR. All ROE changes will be approved by COMOPFOR.

(4) Process 3: Naval Operations are per the OPFOR Naval execution matrix that has been approved by the event director. Naval operations will also be directed by model support per the event MSEL. Changes to naval operations must be approved by COMOPFOR. All ROE changes will be approved by COMOPFOR.

(5) Process 4: Information Operations per the OPFOR Campaign Plan that has been approved by the event director. Information operations will also be directed by model support per the event MSEL. Changes to information operations must be approved by COMOPFOR. All ROE changes will be approved by COMOPFOR.


2. Information Flow. The OPFOR Campaign Plan and supporting orders will be provided to the JECG via the shared event drive NLT the FPC. Information flow during the event will normally be as depicted in the figure below.

Figure 12-1. OPFOR Information Flow

(1) Information Generated and Destination. The OPFOR Campaign Plan and supporting orders will be provided to the JECG via the shared exercise drive NLT the FPC.

(2) Information Management Systems Required:

Location (OPFOR HHQ):

• OPFOR Support: − Simulation workstations as required − One (1) NIPR computer equipped with Microsoft Office (Word, Excel,

Power Point, and Outlook). Computers must have Web and printer access. C2PC must also be installed on all machines

− 1 x VOIP phone with 2 numbers − 1 x POTS phone − OPFOR Cell JECG e-mail address and mailbox to receive exercise-

related material

• OPFOR Information Flow. Primary means of communication will be via VOIP. OPFOR cell will interact with other CECG cells to coordinate the following types of information:

• Component Response Cell MSE’s. OPFOR component (Air/Land/Sea)

Instructor/Controllers coordinates each MSE requiring model support with

OPFOR Information Flow

COMOPFOR

CHIEF OF STAFF

GROUND AIR NAVAL TBM

COMOPFOR

GROUND AIR NAVAL

SR Model Control

Senior Control

MaritimeResponse

Cell

IntelResponse

Cell

IOResponse

Cell

POL-MIL Cell

IOSenior Mentor

Exercise DirectorMedia

COMOPFORWhite Cell UpdatesMSEL SychBDA ReportsReview of - Intel Summary’s- IO Injects- Media Injects

AirResponse

Cell

GroundResponse

Cell

DEPUTYCOMOPFOR

Inter Agency

Component I/CsWhite Cell InputCoord/Execute MSELsBDA Input

OPFOR Information Flow

COMOPFOR

CHIEF OF STAFF

GROUND AIR NAVAL TBM

COMOPFOR

GROUND AIR NAVAL

SR Model Control

Senior Control

MaritimeResponse

Cell

IntelResponse

Cell

IOResponse

Cell

POL-MIL Cell

IOSenior Mentor

Exercise DirectorMedia

COMOPFORWhite Cell UpdatesMSEL SychBDA ReportsReview of - Intel Summary’s- IO Injects- Media Injects

AirResponse

Cell

GroundResponse

Cell

DEPUTYCOMOPFOR

Inter Agency




their respective JECG response cell counterpart. Initial coordination is the responsibility of the BLUE response cell representative. This initial coordination should occur at least 48 hours prior to the event. The specific details of how the event will be role-played will be discussed by the BLUE response cell MSEL manager. If uncertain how to precede, the OPFOR I/C will provide suggestions on how the event “could” be played out. Any changes to the event will be reflected in the MSEL. Changes will be done by the BLUE response cell MSEL manager.

• OPFOR BDA. OPFOR will provide daily BDA reports to the intelligence cell

and senior control as requested. This information is ground truth and should be treated as “close hold” information.

• OPFOR IO Injects. The JWFC IO representative is responsible for injecting

OPFOR IO events during execution (via media clips, media reports, etc). The JWFC IO representative will coordinate injects with COMOPFOR prior to release. COMOPFOR should have a chop on the daily WNN script prior to submission for taping.

• BLUE Intelligence Reports. Daily Intelligence Summary’s (DISUMs) are

forwarded to COMOPFOR for review prior to release. Any report that contains estimated OPFOR strength levels, current activity, and capabilities are reviewed by COMOPFOR prior to release to the training audience.

3. Response Cell Support

a. The JWFC Forces Branch, a subordinate branch under the Operational Environment Team Lead in

the JST, provides Response Cell support, teaching supported technology, operating the simulation system to portray forces in the environment and mentoring the response cell in role playing to stimulate the training audience. On occasions the response cell is a secondary training audience while providing role playing. The normal support for a response cell will normally be one person per shift; however, this may increase due to level of support required for a particular event.

b. Duties and Responsibilities. Response cell operators, provided by the JWFC, serve as Instructor

Controllers (I/C) providing the primary capability for the conceptualization, development, and execution of computer-assisted joint exercises and rehearsals. The I/Cs maintain proficiency in joint and service doctrine, maintain certification in specified models and simulations, and maintain qualification in specified Joint Warfighting Center (JWFC) event life-cycle products and services. The response cell operators provide development and skill maintenance of qualified/certified personnel; maintain the program of instruction used to qualify/certify team members; and maintain resource capability development requirements, data reporting, and performance evaluation inputs. The I/Cs perform as Capability Development Team members for joint event products and services by providing database design and test, master scenario, exercise directive, exercise control plan, exercise simulation plan, and Joint Event Life Cycle (JELC) development management. Response Cell operators provide event analysis collection management liaison; provide Opposing Forces (OPFOR) Campaign plan development liaison; and provide intelligence control architecture development. I/Cs are functional area subject matter experts for Advanced Distributed Simulation, the Defense Simulation Internet, and specified service-sponsored models. Response cell operators act as Task Team Leaders during the event development providing on-time quality products and services to JWFC customers ensuring customer satisfaction. Response Cell operators serve as a Task Team Member for event design assisting with the Scenario/Road-to-War, Master Scenario Events List Development Protocol, and database design development. During events conducts workstation controller tasks; e.g., instructs gamer augmentees, facilitates exercise response cell supervisor capability, assists JECG Director, Exercise Controllers, Scenario managers, cell chiefs, and other various event cells.


4. Event Testing. The number of event tests for each event will be determined by the JEST lead and the Desk Officer. Tests will vary based on the simulation system chosen and the size of the executing federation. Normally there will be two to three event tests leading to execution. A lead I/C will be chosen for each event and will be assigned the responsibility to serve as the Deputy Test director under the M&S Action officer. The Deputy Test Director will coordinate with the Senior Model Control and the Test Manager to produce a test plan for each event test.


Enclosure (13): Joint Exercise Control Group (JECG) Operating Procedure 1. The JECG Battle Rhythm. The JECG uses a series of daily activities to collaboratively evaluate how the exercise is progressing and whether there is a need for change. This series of meetings and related events is collectively called the daily JECG “Battle Rhythm.” The TA also has its own Battle Rhythm and the JECG’s Battle Rhythm must be de-conflicted with that of the TA so important TA briefings can be monitored by the JECG leadership. The JECG’s Battle Rhythm provides its members with a predictable schedule of events that facilitates the evaluation of the course of the exercise. The principle event in the daily JECG battle rhythm is the “White Cell Briefing.” Sometimes called the Battle Update Briefing or Exercise Status Brief, the White Cell Brief provides an opportunity for each Cell Leader to give their assessment of how the last 24 hours of the exercise has gone and to review the events the cell will be monitoring over the next 24 hours. The MSEL Synchronization Meeting is the other major event in the JECG Battle Rhythm. The MSEL “Synch” Meeting allows the JECG leadership to review the upcoming MSELs to ensure that: 1) they are fully ready (synchronized) for injection; and 2) they are still needed in the flow of the exercise. For example, if the DTT announces that a particular training objective has been achieved by the TA, future MSELs that support that objective may be postponed (deferred) or cancelled. Both the White Cell Briefing and MSEL Synch Meeting are typically conducted via Video Teleconference (VTC) so that remote JECG locations can participate and provide their input. The final major element of the JECG’s Battle Rhythm is the Shift Changeover Brief. This is a critical event in the daily cycle of the JECG. It allows the oncoming shift to be quickly appraised of the status of events that were completed during the last shift, the status of events that are still being monitored by the cell and to remind the on-coming shift of impending events. A typically JECG Battle Rhythm might look like the following figure:

Figure 13-1. Example of a JECG Battle Rhythm

(a) White Cell Brief. The White Cell Brief is conducted once each shift, normally early in the

shift, and is normally chaired by the JECG Director or (in the Director’s absence) by a Senior Controller. Each Response Cell lead will give their assessment of the last 24 hours of the exercise and review important events that the cell will be monitoring over the next 24 hours. The JECG Director/Senior Controllers will then provide guidance as appropriate. Normally, “Last 24” and “Next 24” slides with simple “bullet statements” are all that are necessary to capture the important event and status information. Certain cells (for example METOC, Tech Control, CS) may require more customized status slides. In some combatant commands, sophisticated computer software programs are used to notify the cells of an upcoming White Cell event collect and collate their inputs into a comprehensive briefing and export the briefing into a portable document format.

(b) MSEL Synchronization Meeting. The MSEL database is naturally the focus of the MSEL

“Synch” meeting. The MSEL Manager normally conducts the meeting and, using the JMSEL Tool, displays the list of upcoming scenario events. As each event is addressed, the Lead of the Cell responsible for injecting that event will announce whether the necessary coordination with other cells has been accomplished and whether the “implementor” used to initiate the event is complete. Senior Control


will then approve the event, changing the event to “synchronized” status, meaning that, at the scheduled time, the cell is free to inject the event. Otherwise the decision might be made to postpone, restructure or even cancel the event. The White Cell Brief and MSEL Synch Meeting both provide forums for making decisions to change the course of the exercise. For instance, if the TA misinterprets an MSE associated with a critical Training Objective, the JECG leadership can discuss the situation and decide how best to respond. The conclusion might be to develop a new, ad-hoc MSE. These “dynamic events” are used to “steer” the exercise back onto the desired track or to provide additional stimulus to the TA to support certain training objectives.

2. Structuring the JECG. Each JECG is organized to meet the specific needs of each training audience and exercise scenario. The JECG is typically organized into Senior Control, Technical Control, and Response Cell elements. Senior Control provides the overall leadership of the JECG, Technical Control provides the simulation and CS environment needed by the training audience and the Response Cells either replicate organizational elements that fall outside the training audience, provide certain types of information needed by the training audience, or both.

(a) Senior Control. The Senior Control Group normally comprises Chief Controllers, Senior Controllers working under the Chief Controllers, sometimes an analysis cell and sometimes other directors needed to manage certain critical parts of the exercise, such as virtual (manned simulators) or live play. The MSEL Manager and IM/KM Manager functions are often made a part of the Senior Control Cell or Group. Senior Controllers are also normally positioned with forward or rear elements of the JECG to provide high-level oversight and coordination.

(b) Technical Control. In most exercises, the TA uses a Common Tactical Picture (CTP) to

display the disposition and status of friendly and opposing forces. Technical Control is responsible for generating the bulk of the information that comprises the CTP although the TA may also generate and manage certain tracks. The track information that makes up the CTP is normally provided by one or more computer simulations. One simulation may provide all the air tracks, one all the maritime tracks and another one all the ground tracks. Other simulations my originate mission reporting and other intelligence or logistics information. Multiple simulations are “federated” to allow them to exchange information. They feed their information to a “Top Cop” system that distributes the CTP to organizations in the TA.

(c) Response Cells. Response Cells create a “real-world” environment for the TA by replicating

organizational elements that otherwise cannot participate in the exercise. These organizations may be subordinate to, parallel to, or even senior to the TA. For example, Response Cells may replicate such organizations as the Secretary of Defense and Joint Staffs, the Department of State and other government agencies, lateral Headquarters, as well as subordinate air, maritime and ground elements of the Order of Battle (OB). Even public organizations such as newspapers and TV networks can be represented. Subject Matter Experts assigned to the cells “role-play” personnel in these organizations, providing an exchange of information that enhances the realism of the exercise by creating the illusion of an actual operational environment. Functionally, response cells can be organized into two groups. Forces Response Cells are responsible for representing friendly and enemy forces and ensuring their combat systems are moved about the “battlespace” in a realistic manner. Functional Response Cells are those that do not represent operational forces but instead provide certain types of information (ex: logistic information, diplomatic information, intelligence information) needed by the Training Audience. To determine what Forces Response Cells are needed for a particular exercise a determination is first made of what order of battle (OOB) would be appropriate to support the scenario. An Air Cell would represent all the subordinate Air Force units and operate simulations to portray the movement of friendly aircraft and related platforms. A Maritime Cell would represent all subordinate naval units and operate other simulations to portray the movement of naval platforms. A Land Cell would provide the same services regarding Army and Marine units. Sometimes a separate cell is used to portray extensive Special Operational Forces (SOF) activity. The OPFOR Cell would represent the operation of all hostile or opposing forces and, sometimes, also neutral forces (operating as SITFOR or “situational” forces, the combined cell then being called “OPFOR/SITFOR”). After a determination is made of what kinds of functional information the TA needs and then organizing a cell for each type, the overall structure of the JECG can be portrayed graphically and lines of command, control and coordination established. A typical JECG structure is shown at Figure 13-2.


Figure 13-2. Typical JECG Structure

3. Manning. Once the complete organization of the JECG is known, each individual position in each cell is documented in an Exercise Support Manning Document or ESMD. Sometimes the manning of the Training Audience and the JECG are both set out in a Joint Manning Document (JMD). The ESMD or JMD will be used to document the qualifications (rank, sex, branch of service, etc.) and experience level desired in each member of the TA / JECG and will form the basis for the exercise “roster.” Once the ESMD/JMD is complete, except for individual names, it will be distributed to units that will support the exercise and they will be tasked to provide the names of their “augmentees.” An example of an ESMD is shown at Figure 13-3 below. (See Enclosure (26), “Manning Requirements” for additional information).

(a) The supported command will generally fill the following types of positions within the

JECG:

(1) JECG director and senior control personnel. (2) Role players for operational and tactical units at echelons above and below the level of the training audience. (3) Cell Leads for functional cells such as intelligence, logistics, deployment, information operations, civil-military operations, media, and interagency operations. (4) Special staff representatives such as legal, public affairs, political adviser, and liaison officers whose presence may be required on the control staff.


(5) Administrative support for exercise control. (6) Technical and communications support personnel. The combatant command is also usually responsible for providing an IM/KM Manager, help desk function, telephone book, email addresses, a request for information (RFI) tracking system, and any Automatic Digital Network message traffic process.

(b) JWFC will generally provide the following types of personnel to the JECG (may be military, contractors, or both):

(1) JWFC senior ranking officer (normally the JWFC Desk Officer). (2) JWFC senior controllers. (3) Technical model and simulation operators and control. (4) CS personnel. (5) Instructor controllers to assist the response cell leaders interface with and run the simulation systems. (6) Interagency response cell augmentees (lead, if required). (7) Information operations response cell augmentees (lead, if required). (8) Logistic and medical response cell augmentees. (9) Deployment cell augmentees. (10) Operations/information management support. (11) Technical and communications support personnel. (l2) Media response cell lead and augmentees.


Figure 13-3. Example of an ESMD


Intentionally Blank


Enclosure (14): Exercise Intelligence Planning Guide

This Exercise Intelligence Planning Guide is a framework for planning. It addresses the most common events and lead times encountered in the development cycle of an intelligence support package for a given exercise. Of necessity, it is not absolute.

Changes in lead times for the development of exercises have varied widely over the last several years,

most often resulting in a greatly compressed development cycles which render overly time specific planning unwieldy or unworkable.

The following pages will address this cycle in terms of sequenced events with checklists of typical

actions to be accomplished before the next cycle event or milestone. These may be modified or even eliminated in any given exercise by changes in the scope, manning or equipment available as directed by the sponsor of the exercise or outside events affecting the exercise.

Accordingly, it should be remembered that this guide is a template based on experience. New

requirements will require a re-look. It may be copied, in whole or in part, as a framework for working a new exercise, and updated in electronic form. It may be wise to print out the template as a backup or desktop reference, and as a hard copy of information and contacts in the event of a computer malfunction.

As portions may not be applicable in all cases, provision is made for indicating that a particular point

was considered but is not applicable. Back fill color may be used to provide a quick visual representation of the completion of particular sections.


1. “Starting out”

a. If you have just been assigned a new exercise, then collection of the information indicated below will enhance your ability to provide a comprehensive planning product within the Joint Exercise Life Cycle (JELC).

b. If you are taking over an existing exercise from another planner, you will probably start somewhere in the middle of the JELC. To bring yourself “up to speed” it would be good to review the following and check for completeness of the information or applicability of the points indicated up to the point where you have entered the cycle. Reference Question or Action Required N/A? POC Contact or Information

Reference 1. Who is the Exercise Desk Officer? 2. Who is the Joint Warfighting Center Support

Team (JST) counterpart?

3. What is the JELC for this exercise? 4. What are the dates for the Intelligence

Coordinating Conferences?

5. Where are the files for the previous exercises in this series? Do they include:

5.a - Intelligence Exercise Support Manning Document (ESMD)

5.b - Intelligence Joint Manning Document (JMD) 5.c - Intelligence Training Objectives (TOs) 5.d - J2 Vision 5.e - Intelligence Memorandum of Agreement

(IMOA)

5.f - JWFC/JST functional and National/Theater Intelligence POC list

5.g - Plan of Actions and Milestones (POA&M) 5.h - Intelligence story lines 5.i - Consolidated Exercise Support Requests

(CESRs)

5.j - Intelligence After Action Report (AAR) 5.k Lessons Learned (LL) ( Training Audience [TA]

version) [INTSUMs], etc)

5.l Lessons Learned Joint Exercise Control Group [JECG] version)

5.m - Collection Asset Matrix (CAM) 5.n Exercise Intelligence Summaries - Sample Intel

products from theater


c. A similar set of questions needs to be answered with regard to Intelligence POC’s.

Reference Question or Action Required N/A? POC Contact or Information Reference

6. Who are your Points of Contact for: 6.a - Scripting Lead 6.b - In-Theater Intelligence POCs from the previous

exercise.

6.c - Intelligence Rep Combatant Command (COCOM) (may be more than one)

(Trusted agent)

6.d - Intelligence Rep Functional Command (FUNCOM) (may be more than 1)

(Trusted agent)

6.e Intelligence rep, when applicable. from Battle Command Training Program (BCTP) or Marine Staff Training Program (MSTP)

(Trusted agent)

6.f - Intelligence C4I 6.g - Intelligence M&S 6.h - Human Intelligence (HUMINT) 6.i - Signal Intelligence (SIGINT and subs) 6.j - Imagery Intelligence (IMINT) 6.k - TENCAP/ MUSE (UAV simulator) 6.l - Modernized Integrated Data Base (MIDB) 6.m - All-Source Intelligence 6.n - IEDS-D (Improvised Explosive Device System

Defeat)

6.o - Intelligence Opposing Force (Op For) 6.p - Targeting 6.q - Collection Management 6.r - Manning 6.s - METOC/Weather 6.t - Special Operations Forces (SOF) Intelligence 6.u - DSG-A/JIOC 6.v - Intelligence Observer/Trainer (O/T) 6.w - Joint Forces Intelligence School

(JFIS)/Regional Joint Intelligence Training Facility (RJITF)

6.x - Request for Information (RFIs) Manager 6.y -Service/Doctrinal POC 6.z - Necessary to have national reps? Which

ones? (e.g. CIA, NSA, DIA, NGIC, NRO, ONI, DTRA, JPRA etc).

6.aa Measures and Signatures (MASINT)

d. Pre Concept Development Conference

(1) Contact the G/A/N-2 for the prospective primary training audience. Also ask them who their lead exercise Intelligence planner will be. That person is your trusted agent for that unit. You can have more than one trusted agent.

(2) Establish contact with the trusted agent and send them the following items from the previous exercise:

− Intelligence JMD − Intelligence TOs − J2 Vision − IMOA − JWFC functional and National/Theater Intelligence POC list


− POA&M − Intelligence story lines − Intelligence AAR and LLs (TA version) − JFIS/RJITF POC and course information materials. − Intelligence functional POCs in theater − Consolidated Exercise Report Request (CESR)

(3) Ask the trusted agent for a current Intelligence functional POC list from their unit.

(4) Ask the trusted agent to come to the CDC with the questions/information about the following items if possible:

− Intelligence JMD − Intelligence TOs − J2 Vision − IMOA − JWFC functional and National/Theater Intelligence POC list − POA&M − Intelligence story lines − JFIS/ RJITF training − Subordinate unit Intelligence POCs and Intelligence TOs. − CESR

(5) Training Objectives (TO) Workshop (TOW) (Usually held at JTF garrison site. There may not be a TOW, and Intelligence typically does not attend these)

(6) Determine Intelligence TOs (To start, propose Intelligence TOs from previous exercise)

− TOs for Combines Joint Task Force (CJTF) (Primary Intelligence TA) − TOs for Components/Subordinate Units (Secondary Intelligence TA)

(7) TOs derived from Uniform Joint Task List (UJTL) (CJCSM 3500.04B) (usually OP 2 family of tasks)

(8) CJCS/COMJFCOM and COCOM/CJTF commander will usually have recommended training items and “focus areas”. (Obtain Intelligence-specific items of interest from these organizations)

e. Common Considerations

Every exercise planning group goes through a series of false starts and discoveries as it develops its plan and then encounters reality in the form of lead times for delivery. The following is often overlooked:


1. What are the proposed dates of the exercise events per the JELC?

2. What are the dates, times, and weather played in the exercise? (ZULU ONLY!!)

3. What is the Real world Intelligence/info cutoff date?

4. What is the cutoff date , and what organization is



responsible for providing the “real world” MIDB. (should match Intelligence/info cutoff date)

4.a When is the MIDB due to Models and Simulations (M&S)?

4.b When is the MIDB due to the TA? 5 Coordinate a request for METOC support from

Joint Forces Command (JFCOM) METOC right away. Inform them of the JELC and which events you will need METOC support for.

6 Determine how they are actually conducting Intelligence operations in theater. (Needed so exercise play will not cross up what training audience is to experience)

7. Which Higher headquarters Control (HICON) roles will the ICC in the JECG “play”. (e.g.. CENTCOM/ National Intelligence)?

7.a Which BBCCs JWFC will Intelligence chair or support based on theater battle rhythm?.

7.b Is there a need for Intelligence support for Coalition response cells (i.e. ISAF or MNFI, NATO)?

8 How many Intelligence In-Progress Reviews (IIPRs) will the Senior Intelligence Officer (SIO) want? (Recommend one before a Ramp Up and one before the exercise or MRX at a minimum.) What dates will these fall on?

8.a Which personnel will need to be notified to provide input prior to the IIPR?

9 What are the specific Pre-exercise production requirements (i.e. INTSUMs, Road to Crisis [RTCs], Joint Effects Tasking Orders [JETOs})? When they are due to the TA. (Recommend one INTSUM before a ramp up and one INTSUM before an exercise)

9.a What are the Exercise execution period production requirements from “Higher Headquarters” (i.e. INTSUMs, briefs, etc)? When the TA will want them?

10 What are the dates for the Master Scenario Event List (MSEL) Development Conferences (MDCs), and MSEL Synchronization Conferences (MSCs)?

10.a Can the ICC be conducted in one day following that date?

11. Has a space been reserved for the Intelligence Working Group to break out into during the CDC? (If at JWFC, recommend TB1) If not, request one in secure spaces to the CDC location.

11.a Have logins and passwords for computers in Test Bay 1 for the Intelligence Syndicate been obtained?

11.b Has clearance data for the Intelligence Syndicate been sent to the correct Special Security Officers (SSOs) wherever the CDC will be held? (Been received if CDC held at JWFC?).

12 If traveling, get approval from the desk officer as to who can travel with you, cut military orders in the Defense Travel System (DTS), propose a rental car/ privately owned vehicle (POV) plan, get airline tickets, and reserve hotel rooms.



Notify other JWFC travelers as needed.

f. Concept Development Conference (CDC) The Concept Development Conference (CDC) is conducted by the sponsor of the exercise some

six to nine months prior to the anticipated exercise execution date. It is usually held at JWFC, but may be held at a Training Audience location. A review of previous exercises in a series, and collection of the information and documents referred to in the previous section, will provide a robust base and framework for the information to be discussed at the CDC. Exchanging information prior to the CDC will suggest possible “strawmen” and begin the control of the expectations of the participants

(1) Attendees normally include the following:

− Lead Planner − JST counterpart − JFIS/RJITF POC − TA Intelligence trusted agent − National Intelligence Reps (DIA, NSA, NGIC, NGA, NRO, JWAC, CIA, DTRA, JPRA,

ONI, JOC, etc) − Theater Intelligence Reps (COCOM/FUNCOM) − Service Academic/Doctrinal Intelligence rep when applicable. (e.g., BCTP or MSTP)

(2) Goals for the Intelligence Syndicate at a CDC typically include the following:

Ref. Goal N/A or

Done Due Out POC

1. Propose Intelligence Exercise and Training Objectives

2. Identify Primary and Secondary Intelligence Training Audiences

3. Identify Area of responsibility (AOR)/Joint operations Area (JOA)

4. Propose Intelligence Story Lines 5. Draft IMOA 6. Introduce J-2’s Vision 7. Present JFIS/RJITF training capabilities and

get approval for DIRLAUTH (direct liaison authorized).

8. Determine Intelligence POCs for TA, JECG, theater and national entities.

9. Propose/recommend Intelligence role in the Scenario Concept.

10. Propose/recommend Intelligence model and simulation decisions and selections

11 Propose/recommend Classification Guidance

12. Propose/recommend Releasability Guidance 13. Plan the Initial Planning Conference (IPC).

g. If the CDC is held at JWFC, the lead planner should invite intelligence functional leads based on

need and availability.

h. Participants need to register in JEMIS and ensure clearance data is passed to the correct SSOs before traveling.


i. Intelligence representatives to these meetings and conferences should anticipate coming to all

scheduled events. The time lost in bringing new personnel “up to speed” for each meeting is excessive and should be avoided in order to maintain continuity and a consistent product. 2. The Initial Planning Conference (IPC)

a. Pre-Event Test (ET)-1: Pre-event testing and coordination will be needed with the Modeling and Simulations Lead and the Intelligence Modeling & Simulations Lead. As a matter of convenience, it is better to let them use data from the last exercise when possible. The training audience rarely develops sufficient information to support the new exercise by this point. Find out from the M&S Lead what they need from Intelligence and task your Intelligence M&S Lead to accomplish.

Typical support items include the following:

Reference Items which may be needed N/A? Reference location 1. MIDB 2. Joint Target List (JTL) 3. Restricted Target List (RTL) 4. No-Strike Target List (NSTL) 5. Air Tasking Order (ATO) 6. Collection “deck” 7. Reconnaissance, Surveillance, and Target

Acquisition (RSTA) annex

b. ET-1: (Usually held at JWFC). Keep in contact with the JWFC M&S Lead to see what Intelligence

support they need. Your Intelligence M&S lead should participate in the Event Test (ET) looking out for intelligence’s interests and problems associated with the interface of the baseline models and the intelligence models. Corrections may be possible during the course of the ET or after.

c. Pre IPC: Continuing the coordination begun before, during and after the CDC. Have the trusted agent work on, bring, and or send copies of working papers on the following:

− First draft of Intelligence JMD − Proposed Intelligence TOs − Proposed J2 Vision − TA input to IMOA − Unit functional and Intelligence POC lists − TA input to POA&M − Proposed Intelligence story lines − JFIS/ RJITF training requirements/desires − Subordinate unit Intelligence POCs − Proposed subordinate unit Intelligence TOs. − CESR inputs for TA national level support. (1st due 180 days prior to execution) − How much reporting and what type of reporting they want to receive. − Organic ISR assets list by type and quantity they expect to deploy with. − Organic Intelligence C4I list of systems which they expect to employ in theater.

d. Items to consider (Functional Lead responsible in parenthesis under POC):


Reference Action or Question N/A? POC or Ref Answer 1. - Have all “pre CDC and IPC items to

consider” been considered and/or answered?

2. - Are there any changes to which theater and national Intelligence, Surveillance, and Reconnaissance (ISR) assets by type and quantity will be played?

(CM)

3. - Are there any changes to the theater and national level Intelligence C4I employed in AOR/theater/CONUS that will be played or simulated?

(Intel C4I)

4. - Have the approved JTL, RTL or NSTL been obtained, and if obtained, any changes made?

(Targeting)

5. - Have the HVI list and target folders been obtained, and if obtained, any changes made?

(Targeting)

6. - Confirm which Networks the MSEL server will be on. (SIPR,COWAN or both)

(JMSEL Manager)

7. - Confirm which Intelligence C4I networks will be used. (i.e. SIPR, JWICs, COWAN, etc)

(Intel C4I)

8. - Confirm that COLISEUM accounts and hierarchy for RFIs have been set up?

(Intel C4I)

9. Confirm that PRISM accounts and hierarchy for CM been set up? Confirm which version? Confirm which network?

(CM/Intel C4I)

10. - Have the collection decks and RSTA annexes for the exercise been prepared?

(CM)

11. - Have JADOCs used for targeting been provided to JWFC Targeting?

(Targeting)

12. - Confirm which networks will be used by DSG-A/JIOC

(JIOC/Intel C4I)

13. - Confirm which networks will be used for the JTC-I Imagery Product Library (IPL).

(IMINT/Intel C4I)

14. - Confirm which networks SIG will use . (IMINT/IntelC4I) 15. - Determine changes to the Intelligence

footprint and floor plan for the forward element

. (Intel Planner/Intel C4I)

16. - Determine changes to the Intelligence footprint and floor plan at JWFC.

(Intel Planner/Intel C4I)

17. - Obtain logins and passwords for computers in Test Bay 1 for the Intelligence Syndicate use

(Intel Systems)

18. -Did you reserve a space for the Intelligence Syndicate to break out to for the MPC. (If at JWFC recommend Test Bay 1, if not, request an appropriate cleared area at the IPC site)

(Intel Planner/ Exercise Planner)

19. Did the JWFC Intelligence functional leads receive sample Intelligence Exercise Directive Annexes/Appendices for this exercise? If not, send.

(Intel Planner)

20. Did the JWFC Intelligence functional leads receive a sample IMOA? If not, send and give them a due date for inputs.

(Intel Planner)

21. Did the JWFC Intelligence functional leads receive a sample POA&M? If not, send, and give them a due date for inputs

(Intel Planner)

22. Did the JWFC Intelligence functional leads receive sample Intelligence products (INTSUMs, etc)? If not, provide.

(Intel planner/ All- Source)


Reference Action or Question N/A? POC or Ref Answer 23. - Ensure clearance data for the Intelligence

Syndicate attendees is sent to the correct SSOs’ wherever the IPC will be held. (Check the calling message to see if the SSO address is correct)

(SSO/Intel Planner)

24. If traveling, get approval from the desk officer as to who can travel with you, cut orders in DTS, propose a rental car/POV plan, get airline tickets, and reserve hotel rooms.

(Intel Planner)

. e. Initial Planning Conference (IPC) (Usually held at the exercise location to conduct a site survey).

Who should attend the IPC:

Lead Planner JST counterpart JFIS/RJITF POC Intelligence C4I Planner Intelligence M&S Planner Scripting Lead Threat Analyst/ Intel-OPFOR LNO METOC TA Intelligence trusted agent National Intelligence Reps (DIA, NSA, NGIC, NGA, NRO, JWAC, CIA, DTRA, JPRA, ONI, JOC, etc) Theater Intelligence Reps (COCOM/FUNCOM) TENCAP/MUSE Service Academic/Doctrinal Intelligence rep, when applicable. (i.e. BCTP or MSTP)

f. Intelligence Syndicate IPC Goals: Ref. Goal N/A

or Done

Due Out POC

1. Finalize Intelligence Training Objectives 2. Finalize primary and secondary Intelligence

Training Audience

3. Discuss Intelligence Model and Simulation plan

4. Discuss the Collection Asset Matrix 5. Review Intelligence part of Scenario Concept 6. Review Enemy Capabilities 7. Determine Intelligence Product List and

Delivery Dates

8. Discuss Intelligence Training Requirements 9. Outline Intelligence Manning

Requirements/Issues for JMD

10. Outline Intelligence Manning Requirements/Issues for ESMD

11. Discuss Intelligence Architecture Concept/Issues

12. Review and edit IMOA 13. Discuss Intelligence Exercise Directive 14. Plan MDC 1/ICC 1 15. Plan Main Planning Conference (MPC)


16. Visit and survey the ICC Forward spaces. g. If the IPC is held at JWFC, the lead planner should invite Intelligence functional leads based on

need and availability. Participants need to register in JEMIS and ensure clearance data is passed to the correct SSOs before traveling. Make sure clearances are “perm-certed” at JWFC for Intelligence Syndicate participants. Requirement is TS/SCI/G/HSE. (Check the “Calling Message” to insure SSO address data is correct.) 3. The MSEL Development Conference (1) Pre-MSEL Development Conference (MDC)-1/Intelligence Coordination Conference (ICC)-1 actions needed include the following:

a. Choose one day of the MDC to host your ICC, based on TA availability. Confirm ICC date with the Exercise Desk Officer. Ensure JWFC Intelligence functional POCs are available that day.

b. Invite TA Intelligence functional leads to the ICC. (IMINT, SIGINT, MASINT, HUMINT, CM, C4I,

All Source, Targets, trusted agent, etc).

c. Propose the quantity and type of Intelligence–owned story lines with TA and Scripting Lead. These will address Training Objectives. They should reflect what is occurring in theater.

d. Propose the quantity and type of Intelligence steady state MSELs with TA and Scripting Lead.

Steady state MSELs assist in replicating the real world environment in the exercise, but do not specifically address Training Objectives. They should reflect what is occurring in theater.

e. Task the Scripting Lead to break up the Intelligence MSEL number block into subsets based on

story lines and steady state MSELs.

f. Determine Intelligence-owned story line and steady state MSEL authors. If model support is needed for a story line, coordination must occur between the story line owner, the scripting lead, M&S Intelligence, and TENCAP/MUSE and AFSERS so imagery, Virtual Reality Scene Generator (VRSG) data, real world target folder data and JCATS/CBS/JTLS data will match up.

g. Reserve a space for the Intelligence Syndicate participants to break out to for the MDC/ICC. (If

the MDC/ICC is at JWFC, TB 1 is recommended. Make sure clearances are “perm-certed” at JWFC for Intelligence Syndicate participants. Requirement is TS/SCI/G/HSE).

h. The trusted agent should bring the following items with updates: − Intelligence JMD − Intelligence TOs − J2 Vision − IMOA − Unit functional and Intelligence POC lists − POA&M − Intelligence story line ideas − JFIS/ RJITF training requirements/desires − Subordinate unit Intelligence POCs − Subordinate unit Intelligence TOs. − CESR inputs for TA national level support.


− How much reporting and what type of reporting they want to receive. − Organic Intelligence, Surveillance, and Reconnaissance (ISR) assets list by type and quantity

they expect to deploy with. − Organic Intelligence C4I list which they expect to employ in theater. − Where will the TA want their UAV feeds to go to?

i. Ensure clearance data for the Intelligence Syndicate participants is sent to the correct SSOs wherever the MDC/ICC will be held. Make sure clearances are “perm-certed” at JWFC for Intelligence Syndicate participants. Requirement is TS/SCI/G/HSE. Check the “Calling Message” to insure SSO address data is correct.)

j. Obtain logins and passwords for computers in Test Bay 1 for the MDC/ICC if at JWFC.

k. If traveling, get approval from the desk officer as to who can travel with you, cut orders in DTS. Propose a rental car/POV plan, get airline tickets, and reserve hotel rooms.

l. MDC-1/ICC-1: (Usually held at JWFC)

(a) Who should attend the MDC:

− Lead Planner − JST counterpart − Scripting Lead − Threat Analyst/ Intel OPFOR LNO − TA Intelligence trusted agent − METOC − National Intelligence Reps (DIA, NSA, NGIC, NGA, NRO, JWAC, CIA, DTRA, JPRA,

ONI, JOC, etc) − Theater Intelligence Reps (COCOM/FUNCOM) − Service Academic/Doctrinal Intelligence when applicable. (i.e. BCTP or MSTP)

(b) Intelligence Syndicate MDC Goals:

Ref. Goal N/A

or Done

Due Out POC

1. Propose, develop and seek approval for Intelligence-owned story lines and steady state MSELs.

2. Coordination between the Intelligence story line owner, the scripting lead, the M&S Intelligence, and TENCAP/MUSE and AFSERS so imagery, VRSG data, real world target folder data and JCATS/CBS data will match up.

3. Support other syndicate story lines with Intelligence as needed

4. Start scripting. 5. Start coordination and deconfliction 6. Plan MPC – Who is coming & briefing.

(c) Intelligence Syndicate ICC Goals:


Ref. Goal N/A or Done

Due Out POC

1. Review IPC Action items and MPC deliverables

2. HICON, CJTF and Components brief Intelligence organization, roles, manning, and locations

3. Review Intelligence Training Requirements

4. Refine Collection Asset Matrix 5. Refine Intelligence C4I 6. Refine Intelligence M&S 7. Refine IMOA 8. Refine CESR (Due 180 days prior) 9. Refine ESMD and JMD 10. Conduct coordination between TA and

JWFC Intelligence functional areas. (IMINT, SIGINT, HUMINT, CM, Targets, All Source, Training, national agencies, etc)

11. Review Exercise Directive Annex B 12. Plan MPC - who is coming and who is

briefing

(d) Who should attend the ICC:

− Lead Planner − JST counterpart − Scripting Lead − Intelligence C4I Planner − Intelligence M&S Planner − Intelligence CM Lead − Intelligence Targets Lead − Intelligence SIGINT Lead − Intelligence HUMINT Lead − Intelligence IMINT Lead − Threat Analyst/ Intel OPFOR LNO − JFIS/RJITF POC − METOC − TA Intelligence trusted agent − TA Intelligence C4I Planner − TA Intelligence M&S Planner − TA Intelligence CM Lead − TA Intelligence Targets Lead − TA Intelligence SIGINT Lead − TA Intelligence HUMINT Lead − TA Intelligence IMINT Lead


− National Intelligence Reps (DIA, NSA, NGIC, NGA, NRO, JWAC, CIA, DTRA, JPRA, ONI, JOC, etc)

− Theater Intelligence Reps (COCOM/FUNCOM) − TENCAP/MUSE/AFSERS − Service Academic/Doctrinal Intelligence when applicable. (e.g., BCTP or MSTP)

m. If the MDC/ICC is held at JWFC, the lead planner should invite Intelligence functional leads

based on need and availability.

n. Confirm that Participants registered in JEMIS and ensure clearance data was received by the correct SSOs. Make sure clearances are “perm-certed” at JWFC for Intelligence Syndicate participants. Requirement is TS/SCI/G/HSE. (Check the “Calling Message” to insure SSO address data is correct.) 4. SECTION V: Main Planning Conference (MPC): (Usually held at JWFC)

a. The Main Planning Conference confirms the major expectations of the training audience and the supporting work of the Joint Exercise Control Group (JECG). Various working groups address their functional areas and identify any areas where additional coordination may be required.

b. Prior to the Main Planning Conference (MPC), Have the trusted agent/s work on and bring or email the following items with updates:

− Intelligence JMD − Intelligence TOs − J2 Vision − TA input to IMOA − Unit functional and Intelligence POC lists − TA input to POA&M − Intelligence story lines − JFIS/ RJITF training requirements/desires − Subordinate unit Intelligence POCs − Subordinate unit Intelligence TOs. − CESR inputs for TA national level support. (Due 120 days prior) − How much reporting and what type of reporting they want to receive. − Organic ISR assets list by type and quantity they expect to deploy with. − Organic Intelligence C4I systems list which they expect to employ in theater.

c. Items to consider:

Reference Action or Question N/A? POC or Ref

Answer 1. - Have all “pre CDC and IPC items to consider” been

considered and/or answered? (Intel Planner)

2. - Are there any changes as to which theater and national Intelligence, Surveillance, and Reconnaissance (ISR) assets by type and quantity will be played?

(CM)

3. - Are there any changes as to the theater and national level Intelligence C4I employed in theater/CONUS that will be played or simulated?

(Intel C4I)


(Targeting)


Reference Action or Question N/A? POC or Ref Answer


(Targeting)

6. - Confirm which networks the MSEL server will be on. (SIPR,COWAN or both)

(JMSEL manager)

7. - Confirm which Intelligence C4I networks will be used. (i.e. SIPR, NIPR, JWICs, COWAN, FOUR I’s, etc)

(Intel C4I)

8. - Confirm that COLISEUM accounts and hierarchy for RFIs have been set up

(Intel C4I)

9. Confirm that PRISM accounts and hierarchy for CM been set up Confirm which version Confirm which network

(CM/ Intel C4I)

10. - Have the collection decks and RSTA annexes for the exercise been prepared and provided to JWFC CM?

(CM)

11. - Have JADOCs used for targeting been provided (Targeting) 12. - Confirm which networks will be used by DSG-A/JIOC (JIOC/Intel C4I) 13. - Confirm which networks will be used for the JTC-I

Imagery Product Library (IPL). (IMINT/Intel C4I)

14. - Confirm which networks SIG and ASSET will use. (IMINT/Intel C4I) 15. - Determine changes to the Intelligence footprint and floor

plan for the forward element. (Intel Planner/ Intel

C4I) 16. - Determine changes to the Intelligence footprint and floor

plan at JWFC. (Intel Planner/ Intel

C4I/Intel Systems) 17. - Obtain logins and passwords for computers in Test Bay

1 (Intel Systems)




(Intel Planner)


(Intel Planner)


(Intel Planner)


(Intel Planner/ All-Source)

23. - Ensure clearance data for the Intelligence Syndicate participants is sent to the correct SSOs’ wherever the IPC will be held.

(SSO/Intel Planner)


(Intel Planner)

. d. Who should attend the MPC Intelligence Syndicate:

− Lead Planner − JST counterpart − JFIS/RJITF POC − Intelligence C4I Planner − Intelligence M&S Planner − Scripting Lead − Threat Analyst/ Intel OPFOR LNO


− METOC − TA Intelligence trusted agent − National Intelligence Reps (DIA, NSA, NGIC, NGA, NRO, JWAC, CIA, DTRA, JPRA,

ONI, JOC, etc) − Theater Intelligence Reps (COCOM/FUNCOM) − TENCAP/MUSE/AFSERS − Service Academic/Doctrinal Intelligence rep, when applicable. (i.e. BCTP or MSTP)

e. The Intelligence Syndicate Goals at the MPC include the following actions:

Ref. Goal N/A or

Done Due Out POC

1. Complete Intelligence JMD by billet and source.

2. Complete Intelligence Training Plan Coordination

3. Complete Intelligence C4I Architecture Plan 4. Complete Intelligence M&S Plan 5. Finalize draft Exercise Directive Annex B

portions

6. Brief detailed JTF J2/JISE, CINC J2/JIC and Component Concept of Operations

7. Continue Intelligence Team Building 8. Complete Intelligence ESMD by billet and

source.

9. Finalize Intelligence Training Objectives and J2 Vision

10. Finalize Intelligence story lines 11. Refine IMOA, POA&M, and Collection Asset

Matrix

12. Plan MDC-2/ICC-2 13. Determine Theater Intelligence SME

requirements

14. Coordinate METOC Support. 15. Submit ICC Floor Plans to JWFC C4I Lead.

f. If the MPC is held at JWFC, the lead planner should invite Intelligence functional leads based on

need and availability.

g. Participants need to register in JEMIS and ensure clearance data is passed to the correct SSOs before traveling. Make sure clearances are “perm-certed” at JWFC for Intelligence Syndicate participants. Requirement is TS/SCI/G/HSE. (Check the “Calling Message” to insure SSO address data is correct.) 5. SECTION VI: The MSEL Development Conference (2)

Pre-MSEL Development Conference (MDC)-2/Intelligence Coordination Conference (ICC)-2 actions needed include the following:

a. Choose one day of the MDC to host your ICC, based on TA availability. Confirm ICC date with the Exercise Desk Officer. Ensure JWFC Intelligence functional POCs are available that day too.

b. Invite TA Intelligence functional leads to the ICC. (IMINT, SIGINT, HUMINT, CM, C4I, All Source, Targets, trusted agent, etc).


c. Propose the quantity and type of Intelligence–owned story lines with TA and Scripting Lead. It should reflect what is occurring in theater.

d. Propose the quantity and type of Intelligence steady state MSELs with TA and Scripting Lead. It should reflect what is occurring in theater.

e. Continue scripting efforts.

f. Continue coordination and deconfliction efforts.

g. Reserve a space for the Intelligence Syndicate to break out to for the MDC/ICC. (TB 1 is recommended).

h. The trusted agent should email or bring the following items with updates:

− Intelligence JMD − Intelligence TOs − J2 Vision − IMOA − Unit functional and Intelligence POC lists − POA&M − Intelligence story line ideas − JFIS/ RJITF training requirements/desires − Subordinate unit Intelligence POCs − Subordinate unit Intelligence TOs. − CESR inputs for TA national level support. − How much reporting and what type of reporting they want to receive. − Organic Intelligence, Surveillance, and Reconnaissance (ISR) assets list by type and

quantity they expect to deploy with. − Organic Intelligence C4I list which they expect to employ in theater. − Where will the TA want their UAV feeds to go to?

i. Ensure clearance data for the Intelligence Syndicate is sent to the correct SSOs wherever the

MDC/ICC will be held. Make sure clearances are “perm-certed” at JWFC for Intelligence Syndicate participants. Requirement is TS/SCI/G/HSE. (Check the “Calling Message” to insure SSO address data is correct.)

j. Obtain logins and passwords for computers in Test Bay 1.

k. If traveling, get approval from the desk officer as to who can travel with you, cut orders in DTS. Propose a rental car/POV plan, get airline tickets, and reserve hotel rooms.

l. MDC-2/ICC-2: (Usually held at JWFC)

(1) Who should attend the MDC:

− Lead Planner − JST counterpart − Scripting Lead − Threat Analyst/ Intel OPFOR LNO


− TA Intelligence trusted agent − METOC − National Intelligence Reps (DIA, NSA, NGIC, NGA, NRO, JWAC, CIA, DTRA, JPRA,

ONI, JOC, etc) − Theater Intelligence Reps (COCOM/FUNCOM) − Service Academic/Doctrinal Intelligence when applicable. (i.e. BCTP or MSTP)

m. Intelligence Syndicate MDC Goals:

Ref. Goal N/A or

Done Due Out POC

1. Refine Intelligence-owned story lines and steady state MSELs

2. Coordination between the Intelligence story line owner, the scripting lead, M&S Intelligence, and TENCAP/MUSE and AFSERS so imagery, VRSG data, real world target folder data and JCATS/CBS data will match up.

3. Support other syndicate story lines with Intelligence as needed.

4. Continue scripting 5. Continue coordination and deconfliction 6. Plan for the Final Planning Conference. –

Who will brief ?

n. Intelligence Syndicate Goals:

Ref. Goal N/A or

Done Due Out POC

1. Review MPC Action items and FPC deliverables

2. HICON, CJTF and Components brief Intelligence organization, roles, manning, and locations

3. Review Intelligence Training Requirements 4. Refine Collection Asset Matrix 5. Refine Intelligence C4I 6. Refine Intelligence M&S 7. Refine IMOA 8. Refine CESR 2 (Due 90 days prior) 9. Refine ESMD and JMD 10. Continue coordination between TA and

JWFC Intelligence functional areas. (IMINT, SIGINT, HUMINT, CM, Targets, All Source, Training, national agencies, etc)

11. Finalize Exercise Directive Annex B 12. Plan FPC - who is coming and who is

briefing

o. Who should attend the ICC:

− Lead Planner − JST counterpart − Scripting Lead − Intelligence C4I Planner


− Intelligence M&S Planner − Intelligence CM Lead − Intelligence Targets Lead − Intelligence SIGINT Lead − Intelligence HUMINT Lead − Intelligence IMINT Lead − Threat Analyst/ Intel OPFOR LNO − JFIS/RJITF POC − METOC − TA Intelligence trusted agent − TA Intelligence C4I Planner − TA Intelligence M&S Planner − TA Intelligence CM Lead − TA Intelligence Targets Lead − TA Intelligence SIGINT Lead − TA Intelligence HUMINT Lead − TA Intelligence IMINT Lead − National Intelligence Reps (DIA, NSA, NGIC, NGA, NRO, JWAC, CIA, DTRA, JPRA,

ONI, JOC, etc) − Theater Intelligence Reps (COCOM/FUNCOM) − TENCAP/MUSE/AFSERS − Service Academic/Doctrinal Intelligence when applicable. (e.g., BCTP or MSTP)

p. If the MDC/ICC is held at JWFC, the lead planner should invite Intelligence functional leads

based on need and availability.

q. Confirm that Participants registered in JEMIS and ensure clearance data was received by the correct SSOs. Make sure clearances are “perm-certed” at JWFC for Intelligence Syndicate participants. Requirement is TS/SCI/G/HSE. Check the “Calling Message” to insure SSO address data is correct.) 6. Final Planning Conference (FPC)

Pre-ET-2: Find out from the JWFC M&S Lead what they need from Intelligence and task your Intelligence M&S Lead to accomplish this. Solve any problems noted from ET-1. By this point, data coming from the TA should be arriving and integrated into the exercise database.

Reference Items needed N/A? On Hand? Location? 1. MIDB 2. Joint Target List (JTL) 3. Restricted Target List (RTL) 4. No-Strike Target List (NSTL) 5. Air Tasking Order (ATO) 6. Collection “deck” 7. Reconnaissance, Surveillance, and Target


a. ET-2: (Usually held at JWFC)


Keep in contact with the JWFC M&S Lead to see what Intelligence support they need, if any. Your Intelligence M&S lead should participate in the ET looking out for Intelligence’s interests.

b. Pre-Final Planning Conference (FPC):

(1) Have the trusted agent work on and bring or email the following items in their final form:

− Intelligence JMD − Intelligence TOs − J2 Vision − TA input to IMOA − Unit functional and Intelligence POC lists − TA input to POA&M − Intelligence story lines − JFIS/ RJITF training requirements/desires − Subordinate unit Intelligence POCs − Subordinate unit Intelligence TOs. − CESR inputs for TA national level support. − How much reporting and what type of reporting they want to receive. − Organic ISR assets list by type and quantity they expect to deploy with. − Organic Intelligence C4I systems list which they expect to employ in theater.

(2) Items to consider:

Reference Action or Question N/A? POC or Ref Answer 1. - Have all “pre CDC, IPC and MPC items to

consider” been considered and/or answered?

(Intel Planner)

2. - Are there any changes to which theater and national Intelligence, Surveillance, and Reconnaissance (ISR) assets by type and quantity will be played?

(CM)

3. - Are there any changes to the theater and national level Intelligence C4I employed in theater/CONUS that will be played or simulated?

(Intel C4I)


(Targeting)


(Targeting)

6. - Confirm which Networks the MSEL server will be on. (SIPR,COWAN or both)

(JMSEL Manager)

7. - Confirm which Intelligence C4I networks will be used. (i.e. SIPR, JWICs, COWAN, etc)

(Intel C4I)

8. - Confirm that COLISEUM accounts and hierarchy for RFIs have been set up

(Intel C4I)

9. Confirm that PRISM accounts and hierarchy for CM been set up Confirm which version Confirm which network

(CM/Intel C4I)

10. - Have the collection decks and RSTA (CM)


annexes for the exercise been prepared 11. - Have JADOCs used for targeting been

provided (Targeting)

12. - Confirm which networks will be used by DSG-A/JIOC

(JIOC?Intel C4I)

13. Confirm which networks will be used by the JTC-I IPL

(IMINT/Intel C4I)

14. - Confirm which networks SIG and ASSET will use.

(IMINT?Intel C4I)

15. - Determine changes to the Intelligence footprint and floor plan for the forward element.

(Intel Planner/ Intel C4I)

16. - Determine changes to the Intelligence footprint and floor plan at JWFC.

(Intel C4I/Intel C4I/ Intel Systems)

17. - Obtain logins and passwords for computers in Test Bay 1

(Intel Systems)




(Intel Planner)


(Intel Planner)


(Intel Planner)


(Intel Planner/ All-Source)

23. - Ensure clearance data for the Intelligence Syndicate is sent to the correct SSOs’ wherever the IPC will be held.

(SSO/Intel Planner)


(Intel Planner)

c. Final Planning Conference (FPC)

(1) Who should attend the FPC and Intelligence Syndicate:

− Lead Planner − JST counterpart − JFIS/RJITF POC − Intelligence C4I Planner − Intelligence M&S Planner − Scripting Lead − Threat Analyst/ Intel OPFOR LNO − METOC − TA Intelligence trusted agent


− National Intelligence Reps (DIA, NSA, NGIC, NGA, NRO, JWAC, CIA, DTRA, JPRA, ONI, JOC, etc)

− Theater Intelligence Reps (COCOM/FUNCOM) − TENCAP/MUSE/AFSERS − Service Academic/Doctrinal Intelligence rep, when applicable. (i.e. BCTP or MSTP)

2. The Intelligence Syndicate Goals at the FPC include the following actions:

Ref. Goal N/A

or Done

Due Out POC

1. Sign IMOA 2. Review Intelligence POA&M 3. Finalize Intelligence C4I, M&S, and

Collection Asset Matrix

4. Finalize Intelligence ESMD and JMD with names

5. Finalize training audience CONOPS, procedures, and BBCCs for Ramp Up/MRX

6. Issue Intelligence products. 7. Finalize Intelligence Subject Matter

Expert (SME) requirements.

8. Finalize Intelligence Story Lines. 9. Obtain Intelligence Exercise Directive

Annex B Appendices

10. Plan Ramp Up and MDC-3.

3. If the FPC is held at JWFC, the lead planner should invite Intelligence functional leads based on need and availability. 4. Participants need to register in JEMIS and ensure clearance data is passed to the correct SSOs before traveling. Make sure clearances are “perm-certed” at JWFC for Intelligence Syndicate participants. Requirement is TS/SCI/G/HSE. (Check the “Calling Message” to insure SSO address data is correct.)

7. SECTION VIII. – EXECUTION VIII.a. Pre-Ramp Up Responsibilities: The Training Audience may request a preliminary “practice round” before an actual exercise. These activities may be different than the actual exercise, or may be extracts from the exercise they will face later.

Ref. Action to be Taken N/A or Done

Reference or Product location

1. Ensure all travel has been approved and coordinated (names, hotels, rental cars, air line tickets, etc) for ICC personnel traveling. Coordinate with the Desk Officer and JWFC Travel POCs. Compile a recall roster and issue to ICC leads for all distributed sites.

2. Ensure all clearance data for all ICC personnel has been sent to the proper SSOs. Pick up badges in advance, if possible.

3. Issue pre-Ramp Up Intelligence products, if required,


in accordance with (IAW) agreed upon due dates. (i.e. INTSUMS, MIDB, Target Folders, detainee packs, etc)

4. Ensure all Intelligence scripting items are ready to be issued for the Ramp Up.

5. Conduct an Intelligence IPR, if the SIO wants one 6. Conduct the Intelligence portion of IPRs if the Desk

Officer calls for them

7. Establish the ICC Battle Rhythm, IAW the JECG and TA’s Battle Rhythms. Be prepared to (BPT) host, chair, or support any Intelligence-specific Battle Rhythm events, if required. (i.e. Joint Collection Management Boards [JCMBs], Enemy Combatant Review Boards [ECRBs], etc)

8. Scrub the ICC portion of the ESMD. Update names and billets as needed. Ensure the SSO and exercise leadership is aware of changes ASAP. If shortfalls arise, inform the SIO immediately, but have a solution in mind.

9. Conduct Intelligence C4I communications checks on all networks and systems, if possible. Obtain logins, passwords and server information too. (Like a COMMEX)

10. Set up the ICC Watch Bills with the ICC Leads. Determine Turnover brief procedures.

11. Build White Cell slide shells 12. Double check to see if other syndicates need

Intelligence support. Provide as required.

13. Issue AAR formats to ICC Leads. 14. Ensure ICC personnel register in JEMIS for the

Ramp Up, if needed

15. Rehearse all ICC Procedures. (deliberate and dynamic scripting, messages, etc) (Like a MINIEX).

16. Coordinate MSEL and Foreign Disclosure (FD) training for ICC members, if needed.

VIII.b. Ramp Up Execution and Reporting Responsibilities Checklist: (Usually a distributed event)

Ref. Action to be Taken N/A or Done

Reference or Product location

1. Conduct the Ramp Up exercise IAW battle rhythm and what the scenario Intelligence script calls for. Do not release products early.

2. Produce and release products, answer RFIs, and serve as HICON for the TA. Fix problems as they arise.

3. Be prepared to adjust or create new Intelligence story lines based on guidance from the JWFC and BCTP Intelligence OTs, Senior Mentors, and exercise leadership. Use the dynamic scripting method.

4. All ICC section leads should keep an electronic or hard copy log book to track the exercise, keep notes and, use that for JECG and TA AAR items.


5. Ask for 3 Up (Sustain)/3 Down (Improve) from all Functional Intelligence Cell Heads in the ICC Main and Forward. This serves as your JECG Hot Wash item input.

6. Ask for TA lessons learned from all Functional Intelligence Cell Heads in the ICC Main and Forward. You can pass this to the TA Intelligence trusted agent.

7. . Keep the SIO and Exercise leadership informed of any ICC issues, and propose solutions.

8. Attend the JECG Hot Wash and FAAR and take notes

9. Put together a TA AAR and ICC AAR and send them to the JWFC Intelligence POCs, TA Intelligence trusted agent, DT1 leadership, JST Intelligence leadership, and the J7 SIO.

10. Recommend awards or commendations for your ICC staff to Intelligence and exercise leadership

11 Post-Ramp Up: Keep in touch with the TA. Time permitting, they can still schedule JFIS/RJITF training after the Ramp Up is completed

12. Remain in contact with TA Intelligence POCs to find out what trained them well, what did not train them well, and what we should add to the MRX to better train them.

13. Archive all final versions of products for the next exercise. Save the Intelligence AARs and LLs for the next exercise

14. Prepare an ICC AAR for the J7 SIO and JTCI DT 1 leadership.

15. Prepare an Intelligence AAR for the TA. You will not get any feedback from JWFC Intelligence OTs. They do not share AAR/LL items. BCTP Intelligence OT will share Intelligence AAR/LL items with you. You must ask for them and keep them “close hold”.

VIII.c. Pre-Exercise Execution Responsibilities Checklist (As Required) 1. Pre-MDC-3(As required): Ref. Goal N/A or

Done Due Out POC

1. Refine and finalize the quantity and type of Intelligence–owned story lines with TA and Scripting Lead based on what happened during the Ramp Up.

2. Refine and finalize the quantity and type of Intelligence steady state MSELs with TA and Scripting Lead based on what happened during the Ramp up.

Ref. Goal N/A or Done

Due Out POC

3. Support other syndicate story lines with


Intelligence as needed. 4. Continue scripting 5. Continue coordination and deconfliction 6. Reserve a space for the Intelligence Syndicate

participants to break out to for the MDC. (Test Bay 1 if at JWFC).

7. Ensure clearance data for the Intelligence Syndicate participants is sent to the correct SSOs wherever the MDC will be held

8. Obtain logins and passwords for computers in Test Bay 1 for the IWG.

9. If traveling, get approval from the desk officer as to who can travel with you, cut orders in DTS. Propose a rental car/POV plan, get airline tickets, and reserve hotel rooms.

10. The trusted agent should bring or email the following items with updates as before:

- Intelligence JMD - Intelligence TOs - J2 Vision - Unit functional and Intelligence POC lists - POA&M - Intelligence story line ideas - JFIS/ RJITF training requirements/desires - Subordinate unit Intelligence POCs - Subordinate unit Intelligence TOs. - CESR inputs for TA national level support. (60 or 30 days prior) - How much reporting and what type of reporting they want to receive. - Organic ISR assets list by type and quantity they expect to deploy with. - Organic Intelligence C4I systems list which they expect to employ in theater. - UAV feed locations for TA

2. MDC-3 (Usually at JWFC): 1. MDC-3: Find out from the JWFC M&S Lead what they need from Intelligence and task your Intelligence M&S Lead to accomplish this. Solve any problems noted from ET-2. By this point, data coming from the TA should be arriving and integrated into the exercise database. 2. Intelligence Syndicate MDC Goals:

Ref. Action or Process to Accomplish N/A or Done

Due Out

POC

Refine Intelligence-owned story lines and steady state MSELs.

Coordination between the Intelligence story line owner, the scripting lead, the M&S Intelligence, and TENCAP/MUSE and AFSERS so imagery, VRSG data, real world target folder data and JCATS/CBS data will match up.


Support other syndicate story lines with Intelligence as needed

Continue scripting Continue coordination and deconfliction Final planning prior to MRX

3. Who should attend the MDC:

− - Lead Planner − - JST counterpart − - Scripting Lead − - Threat Analyst/ Intel OPFOR LNO − - TA Intelligence trusted agent − - METOC − - National Intelligence Reps (DIA, NSA, NGIC, NGA, NRO, JWAC, CIA, DTRA, JPRA,

ONI, JOC, etc) − - Theater Intelligence Reps (COCOM/FUNCOM) − - Service Academic/Doctrinal Intelligence when applicable. (i.e. BCTP or MSTP)

3. If the MDC is held at JWFC, the lead planner should invite Intelligence functional leads based on need and availability. 4. Participants need to register in JEMIS and ensure clearance data is passed to the correct SSOs before traveling. Check the calling message for the correct address and clearances required. 3. Pre-ET-3:

Reference Items needed N/A? On Hand? Location? 1. MIDB 2. Joint Target List (JTL) 3. Restricted Target List (RTL) 4. No-Strike Target List (NSTL) 5. Air Tasking Order (ATO) 6. Collection “deck” 7. Reconnaissance, Surveillance, and Target


1. JWFC M&S. These should be based on the TA collection plan and ISR assets that were agreed upon by the completion of ICC 2/FPC. Find out from the JWFC M&S Lead what they need from Intelligence and task your Intelligence M&S Lead to accomplish this. 2. This is a true end to end C4I-M&S-ISR-Intelligence message output communications check. You also need to ensure you have good POCs for the TA’s Intelligence C4I, CM, IMINT, All Source and Targets sections. Ensure you also have good POCs for TENCAP/MUSE, DSG-A/JIOC, and the CAOC. They will be involved with ET-3 too. Our Intelligence functional POCs will have to coordinate with all of these POCs to ensure testing is complete and works. Solve any problems from ET-2. 4. ET-3 (Usually held at JWFC and the distributed sites): Keep in contact with the JWFC M&S Lead to see what Intelligence support they need, if any. Your Intelligence M&S lead should participate in the ET looking out for Intelligence’s interests. There is time built into the JELC between ET-3 completion and the start of JECG Training for final corrections, but it may be as little as one day.


5. Pre-JECG Training:

Ref. Action to Confirm N/A or Done

Notes

1. Ensure all travel has been approved and coordinated (names, hotels, rental cars, air line tickets, etc) for ICC personnel traveling. Coordinate with the Desk Officer and JWFC Travel POCs. Compile a recall roster and issue to ICC leads for all distributed sites

2. Ensure all clearance data for all ICC personnel has been sent to the proper SSOs. Pick up badges in advance, if possible

3. Issue MRX Intelligence products, if required, IAW agreed upon due dates. (i.e. INTSUMS, MIDB, Target Folders, detainee packs, etc)

4. Ensure all Intelligence scripting items are ready to be issued for the MRX

5. Conduct an Intelligence IPR, if the SIO wants one. 6. Conduct the Intelligence portion of the final IPR if the

Desk Officer calls for them.

7. Establish the ICC Battle Rhythm, IAW the JECG and TA’s Battle Rhythms. BPT host or support any Intelligence-specific Battle Rhythm events, if required. (i.e. JCMBs, ECRBs, etc)

8. Scrub the ICC portion of the ESMD again. Update names and billets as needed. Ensure the SSO and exercise leadership is aware of changes ASAP. If shortfalls arise, inform the SIO immediately, but have a solution in mind.

9. Set up the ICC Watch Bills with the ICC Leads. Determine Turnover brief procedures.

10. Build White Cell slide shells. 11. Double check to see if other syndicates need

Intelligence support. Provide as required.

12. Issue AAR formats to ICC Leads 13. Ensure ICC personnel register in JEMIS for the MRX, if

needed

6. JECG Training/Pre-MRX:

Ref. Action or Process to be checked N/a or Done

Notes

1. Follow the published JECG schedules for the Main and Forward

2. Ensure ICC Main and Forward Members get MSEL Tool and FD training if they need it. Set up Intelligence only training sessions if needed

3. Conduct and complete the COMMEX 4. Conduct and complete the MINIEX. 5. Ensure all ICC Main and Forward elements conduct

comm checks with the TA Intelligence and JECG Intelligence POCs on telephones, VOIPs, e mails, IWS,


MIRC, websites, VTC channels, and shared drives on NIPR, SIPR, JWICs and COWAN. They should send messages and verify they got to their destination and vice versa. They should build distribution lists, signature blocks, phone rosters, turnover briefs, briefing slides, log books, shared drive folders, and watch bills.

6. Rehearse the Deliberate Scripting process in all INTs 7. Rehearse the Dynamic Scripting process in all INTs 8. Rehearse posting products to web sites on all nets 9. Rehearse the FD process. 10. MSEL Synchronization rehearsals will occur during this

time frame

11. White Cell meetings rehearsals will occur during this time frame

12. Rehearse RFI procedures. 13. Rehearse CM procedures 14. The ICC elements should all conduct internal INT-

specific training

15. Rehearse Targeting procedures. SECTION X _ Classified Annex

– PUBLISHED SEPARATELY


Intentionally Blank


Enclosure (15): Sustainment 1. Sustainment Automation Support Tools and Model Requirements. If the training audience requires replication of real world sustainment Command, CS systems to accomplish their training objectives, then model simulations are required to stimulate the systems. (Example: An army training audience component that requires the Battle Command Sustainment Support System (BCS3) to ensure a robust level of exercise play to meet specific training objectives, requires a model with a detailed, accurate database to accurately feed this CS system.) Building a logistics database is time-consuming work and the training audience must be prepared to participate fully in the JWFC JELC, to include database event tests. (Refer to Chapter V, “JELC,” for a more detailed discussion of the event test process.) 2. Control of Sustainment Play. During exercise execution, a sustainment functional response cell is formed to control exercise play. The JWFC military sustainment planner, JST planner, training audience sustainment planner, and select representatives from participating external sustainment agencies normally staff the JECG sustainment cell. If the battle rhythm calls for 24 hour per day operations, manning for a second shift is required. Under the direction of the Sustainment Cell lead, this team injects scripted events, monitors and controls the sustainment play, replicates all sustainment entities at command levels above and below the training audience, and responds to training audience requests for information to provide as much realism as possible for the training audience.


Intentionally Blank


Enclosure (16): Joint Exercise Support Branch Support 1. Data Services: JWFC provides a multitude of data services both internally and external. The services extend across a range of classifications and are developed based upon the classification for each event. Specifically:

a. Joint Training Experiment Network (JTEN): The JTEN is a persistent US Secret wide area network over a DISA backbone consisting of 6 hubs and over 46 persistent training sites. The rapidly re-configurable network supports joint training exercises, experimentation, and the evaluation of new warfighting concepts. The JTEN is paired with several other networks such as the USAF Distributed Mission Operations Network (DMON) and the USN Continuous Training Environment (NCTE) which expands the JTEN reach to many more live, virtual, and constructive training locations. The CS planner will gather the requirements for the event and submit a JTEN request to the NOSC. If there is a site that requires connection that is not a persistent node, the CS planner will work with DISA LNOs to order the circuits. 120 Days is the order time frame for CONUS circuits and 180 days is the order time frame for OCONUS circuits. The Joint Training Network waiver process is used to control all non-standard requests to modify the security posture of the administrative training networks. There are two primary groups within JFCOM who control and approve the waivers; JFCOM J6 and JFCOM J7 (Joint Force Trainer). As a result, a waiver may be J6 action only, J7 action only or J6 – J7 action. JFCOM J6 controls all of the administrative networks and access to SIPRnet and SIPRnet. JFCOM J7 controls all of the Joint Training Networks including JTEN-S, JTEN-U, Cox, Coalition and some others. During the majority of Joint Trainer exercises, the training networks require access through J6 networks to the SIPRnet to communicate, collaborate or stimulate real world systems. J6 serves an “honest broker” for training connections to real world.

b. Unclassified but Sensitive Internet Protocol Router Network (NIPRNet): NIPRNet is, by design, a parallel air gapped analogue to the SIPRNET, providing seamless interoperability for unclassified combat support applications, as well as providing a gateway to the public Internet. While the NIPRNet is operated and controlled by the USJFCOM J6, the JESB uses it to coordinate unclassified correspondence on a daily basis.

c. Secret Internet Protocol Router Network (SIPRNet): SIPRNet is a system of interconnected computer networks used by the U.S. Department of Defense and the U.S. Department of State to transmit classified information (up to and including information classified SECRET) by packet switching over the TCP/IP protocols in a "completely secure" environment. It also provides services such as hypertext documents and electronic mail. While USJFCOM J6 controls the primary border to the SIPRNet, the JESB uses it on a daily basis to coordinate classified correspondence. The CS Planner is required, on a routine basis, to submit Firewall Waiver Requests to open ports and protocols from the JTEN to the SIPRNet. This is done to allow M&S systems residing on the JTEN to stimulate real world Command and Control (C2) Systems residing on the SIPRNet. In addition, and on a case-by-case basis, Firewall Waiver Requests may be used to allow services to be shared between the SIPRNet and the JTEN (i.e. Web Services). Other – The JWFC is capable of installing and operating numerous other networks to including Coalition Wide Area Networks (COWANs), Combined Enterprise Regional Information Exchange System (CENTRIXS) and US BICES (Battlefield Information Collection and Exploitation System). The JWFC is also a remote site off the NORAD RELCAN network to support NORAD/NORTHCOM training. 2. Voice:

a. The CS planner will coordinate for telephone support as the requirements are identified. For secure voice capabilities, the CS planner will coordinate with the COMSEC vault for appropriate


instruments. Any special keymat required for an event should be identified no later than the MPC to give time for obtaining the keymat if it is not part of the current JWFC COMSEC inventory.

b. The CS planner will obtain a long distance code from Comms System Engineering Section for each exercise to assist with budget tracking.

c. If additional standard telephones are required or existing handsets must be moved, a telephone service request is submitted to engineering for support.

d. JWFC facilities have the capability to establish teleconference bridges. 3. VoIP. This section outlines the current Voice Over Internet Protocol (VoIP) capabilities.

a. The JWFC can set up conferences in the NORTEL Switch in addition to point to point. Conference capability supports up to 32 users currently divided into 3 conferences of 10, 10, and 12. That could be 32, 0, 0 or 16, 16, etc.

b. Most other commands use CISCO systems. JWFC can support both CISCO and NORTEL systems and the two call managers are bridged via a router which means if you are calling on a CISCO phone you can talk to a NORTEL phone through our bridge if proper programming of the call managers is completed.

c. The Cisco Call manager (CCM) can support up to 1000 users or instruments. As of today there are only about seventy local and/or remote users registered with the CCM but the important thing is the bridge between systems.

d. We also have a Nortel mini switch which has the least capability of the three platforms. It can only support forty (40) users in its current state.

e. The NORTEL CS1000 is always on the JTEN so it runs at US SECRET. The mini can be used on other networks operating at different classification levels. At present JTEN VoIPs cannot talk to VoIPs on SIPRNET even if firewalls are open.

f. Voice over SIPR: The VoSIP capabilities implemented at the JWFC are delivered over a Defense Red Switch Network (DRSN)-compatible, IP-based system. The capabilities enable secure, joint-interoperable voice communications from JWFC users to our training audiences. The initial implementation (1 October 08) of VoSIP at the JWFC will include the ability to deploy a total of 50 Cisco Phones. These can all be located in the JWFC or deployed depending on the exercise requirements. The three year plan for VoSIP implementation calls for expansion to 150 phones. Additionally, the initial VoSIP enclave will not interoperate with the current secure VOIP phones deployed on the JTEN network. This connection will be made at a later date and at that time this portion of the handbook will be updated to reflect the change in capabilities. 4. VTC. The JWFC currently maintains 6 Polycom MGC100 multipoint control units (MCU’s) for exercise multi-site video teleconferencing support and 13 multi-purpose conference rooms for exercise planning and day-to-day operations. The MCU’s and room systems are certified for use on the DISN Video Services – Global (DVS-g) network and the Video Information Exchange System (VIXS) network. JWFC also maintains two conference rooms certified for use on the Joint Worldwide Intelligence Communications System (JWICS). a. All conference rooms and MCU’s are scheduled in accordance with the JWFC support team (JST) standard operating procedure for conference room scheduling and support.


b. The capability of each MCU is listed below for planning purposes only. The JST video operations department, in conjunction with the JWFC Video Systems Engineering department, makes the decision, based on the exercise requirement and event schedule, which MCU will be used to support a specific event. 5. Email. This section provides a broad overview of JFCOM’s & JWFC’s E-Mail capabilities and outline any factors that should be considered during exercise planning.

a. Enterprise Networks: JFCOM networks are used for administration and day to day operations.

(1) NIPR: (JANET) • NIPR Accounts are normally only created for JFCOM assigned personnel • Log-in Process: CAC required • Maximum E-Mail Box Size: 100 Megabytes • OWA Access: https://webmail.jfcom.mil (CAC log-in required)

(2) SIPR: (LIMS)

• SIPR Accounts are normally only created for JFCOM assigned personnel • Capable of sending/receiving email from both SIPR/JTEN accounts • USA, AUS, CAN, GBR, NZL communications available via GRIFFIN. Contact

Security Manager for GRIFFIN training and obtaining access. • Log-in Process: Username/Password • Maximum E-Mail Box Size: 100 Megabytes • OWA Access: https://webmail.jfcom.smil.mil (username/password} Note: Users can access JTEN accounts via SIPR OWA

(3) Exercise Networks:

(a) JTEN: The Joint Training & Experimentation Network is used for exercises and events. It currently is at the US Secret level and in the near future will be at the unclassified level.

• JTEN Accounts are normally created for Exercise Participants – deleted after

event/exercise • When created for event/exercise – created by position; not by name i.e.,

AC08_Exercise_Director instead of Colonel John Doe • Assigned JFCOM personnel with valid requirements may be assigned JTEN

Accounts—created by name • Capable of sending/receiving email from both SIPR/JTEN accounts • Log-in Process: Username/Password • Maximum E-Mail Box Size: Unlimited • OWA Access: https://webmail.jntc.smil.mil/exchange

(username/password) Note: Users can access SIPR accounts via JTEN OWA (4) COWAN – used to replicate other operational domains.

• Cowan Accounts are normally created for Exercise Participants – deleted after event/exercise

• When created for event/exercise – created by position; not by name - i.e., AC08_Exercise_Director instead of Colonel John Doe

• Assigned JFCOM personnel with valid requirements may be assigned JTEN Accounts—created by name

• Capable of sending/receiving email from both SIPR/JTEN accounts


• Log-in Process: Username/Password • Maximum E-Mail Box Size: Unlimited

(5) Commercial Access (Cox Network):

• With special request, JFCOM can provide commercial network access • Only a medium for network access – web mail access (hotmail, yahoo, etc) • No special accounts or storage area provided/created

(6) GAL (Global Access Listing) Replication: • JWFC does not own any licenses for GAL Sync Replication tools (Jun 08) • Current Process: Each site must extract their GAL to either CSV or LDIF file

format and then exchange files with all participating sites. • In order to avoid conflict – sites should avoid listing their exercise and real- world

entries with the same name, i.e., Real-world: Barksdale; Exercise listing should be: Barksdale-Exercise

6. Message Traffic. The Automated Message Handling System (AMHS) provides a user-friendly means to send and receive messages via the Automated Digital Network (AUTODIN). It provides connectivity to and interoperability with other Government agencies, allies, tactical users, defense contractors and other approved activities external to the Defense Message System (DMS) community. It also provides guaranteed delivery to the intended recipients and maintains writer to reader accountability. Automated Message Handling System is the designated Department of Defense Intelligence Information System (DoDIIS) migration system utilizing COTS products delivered via an internet browser. It includes incoming message and text processing, profiling, retrospective search and retrieval, on-line archive, outgoing message processing, and message composition and coordination. Message Traffic capabilities are integrated into exercises. 7. WEB services. Provides webmaster support using the SharePoint-based exercise Portal, which includes the design, development, encode, and management of SharePoint-based sites for various JFCOM hosted/supported exercises, WNN.com, and IO supported adversarial websites. The following URL will assist in coordinating with the web team: https://us.jfcom.mil/sites/J7/cos/missionassurance/kmim/web_administration/default.aspx

a. Additional web team support to the planner includes:

• Graphic design to enhance/supplement web pages providing the JWFC with a rapid method of knowledge distribution.

• Recommends, analyzes, and implements security aspects for the World Wide Web (WWW).

• Acts as a liaison with JWFC division POCs and planners to ensure that information on JWFC Exercise websites/portal is current and updated in a timely manner.

• Monitors JWFC web pages for required information updates and broken links. • Provides web-related technical and administrative support for both in-house and

deployed joint training events.

b. The SharePoint portal provides the following capabilities for training exercise support:

• Global collaboration for planners, exercise participants, and training • Increased functionality in the hands of the user • Planner and exercise participants control information available to the training audience


• Adversarial sites provide simulated capabilities to enhance real-world atmosphere, (terrorist recruiting site, etc.)

• Video and transcript interjects via WNN exercise sites • Multi-level access permissions to allow for controlled access (full permissions or

contribute) to specific areas of the website or global access to all • MOSS 2007 sites functional on multiple servers – NIPR, SIPR, COWAN, JTEN, etc.

c. Collaborative Information Environment (CIE)

• Button 1 Same time • Button 2 Defense Connect Online (DCO)

8. WNN. World News Network or WNN is a synthetic media capability to enhance the training events sponsored and/or supported by the USJFCOM J7. It is critical that the CS Planner work with the assigned WNN representative during the JELC cycle, and specifically at planning conferences to ensure effective coordination of compilation of coordinating information and distribution of final products.

• Internal Distribution is the process of transmitting coordination information or raw products between exercise locations and Test Bay 19. This information includes interviews, sound bites, stand up reports, still pictures and video scripts. The practices currently used are email, posting to Joint Digital Library or a specific Portal page controlled by permissions.

• External Distribution is the process of transmitting the finished products to the training audience. For a JFCOM sponsored exercise or event, the products are posted to a JWFC portal on an exercise network (NIPR or JTEN). When JWFC supports a Combatant Command exercise, the finished products are either posted to JWFC portals or on the supported Command portal /web pages. Distribution processes need to meet Information Assurance policies. The assigned IA rep will work with the CS planner on technical compliance and the WNN planner on the content. The Foreign Disclosure Officer can assist to ensure the data is releasable during multinational events.

9. Common Operational Picture (COP). The COP is the primary C2 display capability for the Training Audience. It is the ultimate repository of all simulated or live data feeds for the exercise CS architecture. Proper design and management of the COP requires the collective efforts of the JWFC technical support team and the Training Audience. This team effort is guided by joint doctrine (CJCSI 3151.01A, GCCS COP Reporting Requirements, 19 January 2003), Training Audience SOPs, and specific training objective requirements. The outcomes of the COP conference include (1) a COP architecture diagram detailing top-level parent/child relationships and messages flows used to build the COP, (2) an M&S-to-CS diagram detailing the specific message flows from models to C2 Systems, and (3) a draft OPTASK COP message. The JWFC has a Radiant Mercury to allow US Secret COP data to move to non-US Secret Domains. 10. Information Assurance

a. Information Assurance Manager - Security (IS). The following procedures will be followed for IS brought into the JWFC. The IS shall:

• Be in processed during check in at JWFC. • Be used for official business only. • Be in direct support of a specific event. • Be government owned.


• Be properly marked with the appropriate classification. • Have a virus scanner install, running and have up-to-date DAT files. • Have a temporary JWFC bar code on the equipment. • Will have a JWFC property pass completed. The original will be given to the responsible

courier and a copy will be placed on file and forwarded to the JWFC Material Manager.

b. Information System’s Courier. The following procedures will be followed for couriering classified information:

• Have written documentation signed by specific written authorization by the responsible exercise point of contact. The documentation will identify the equipment and certify mission requirements.

• Have a courier card and/or courier letter for the classified IS. • Not connect the IS to any JWFC network without specific authorization for the JWFC

IAM. • Do not remove a phone line from any secure unit or other telephone for the purpose of

connecting a laptop modem. Laptop modem lines are installed in every JTF test bay and additional lines may be requested as needed via the exercise requirements process.

• Scan all information downloaded to JWFC IS prior to migrating the data. • Return their copy of the property pass to the in-processing area, or other designated

area, before removing the IS from the JWFC building. • Ensure the property pass used to verify the laptop and the courier is annotated with the

persons name verifying the information and date/time group the equipment left the building. The verified property pass will be collected by the JWFC Logistics Manager or representative, and used to update the Material Management System.

11. Engineering. The JWFC Chief System Engineer is responsible for providing engineering services in support of the Suffolk Campus Complex infrastructure and for near term (JELC) engineering for event support. The Systems Engineering Team provides the following services:

a. Design, Specify, Procure, Install and Upgrade All Exercise Electronic Systems at JWFC.

b. Communications / Networks (garrison & deployed), C4I, M&S, VTC, Audio/Visual, Broadcast Production, Office Automation, Exercise Support Systems, Oracle Database, SW development, JDLS.

c. Life Cycle Management for JWFC Training & Exercise System (JTEX)Provide Engineering Support for Exercise Planning & Execution and other USJFCOM events (experimentation, real world operations)Provide Engineering Implementation for Technology Insertion into Existing Systems.

d. JWFC Facilities Technical Infrastructure Engineering.

e. Serve as Procurement Agent for JWFC.

f. Serve as JNTC Systems Engineer (Implement JTEN).


g. Reach back to SPAWAR, DARPA, Service SYSCOMs, others.

h. Provide System Engineering design expertise in support of the USJFCOM mission areas.

i. Systems Engineering resides in Operations as part of JSD and consists of about 20 SPAWAR

personnel and 60 contractors. They are divided into six groups.

• Information Transfer (IT) • Information Systems (IS),

• Video System (VS)

• Command, and Control, Communications, and Computers (C4)

• Event Support (ES)

• Communications (Com)

j. The IT Group engineers and maintains a broadband network communication subsystem

connected to and using operational networks globally. The system is capable of carrying voice, video, imagery and data throughout the local area, DoD and the global-wide area and provides multiple gateways for real-time access to worldwide networks such as DREN, DISN (including GIG BE), NMCI, etc. The IT subsystem is sub-divided into the following major functional areas:

• Exercise Communications focuses on providing external communication connectivity to support the JFCOM/J7 training mission, independent of physical location of the training event.

• Power focuses on providing conditioned, redundant, continuous power to support the

JFCOM/J7 training mission, independent of physical location of the training event. • Training & Exercise Network Distribution focuses on providing intra-facility and

transportable communications components to support the JFCOM/J7 training mission. The primary training network is the Joint Training and Experimentation Network, (JTEN) both classified and unclassified, that provides a persistent, secure, global communications infrastructure. The JTEN also provides direct communications links to coalition partner training networks such as the Australian Defense Training and Experimentation Network (DTEN) and the United Kingdom Joint Multinational Interoperability Assurance Network (JMNIAN). IT also stands up various coalition and unclassified networks as required to support the JFCOM/J7 training mission.

• Information Assurance (IA) provides for a defense in depth architecture to protect critical

services and data. The defense in depth strategy protects the systems at the boundaries, network, and host levels. As such, IA systems and components cross the boundaries of all IT, IS, AV, and C4 subsystems.

k. Information Systems (IS). The IS Group engineers and maintains server components designed

to provide office automation, exercise planning, exercise execution, facility management, security management, process refinement and data management. IS systems include hardware technology and software technologies (COTS/GOTS) needed for the JFCOM/J7 to perform the exercise mission. The IS subsystem is sub-divided into the following major functional areas:


• JWFC Exercise Support Network – Unclassified (JESNET-U) – the JESNET-U functional areas is composed of client/server hardware, software and services needed to execute exercise planning, execution and after action review at the unclassified security level. It includes both home station and deployable equipment with reach-back capability. The JESNET-U functional area is in transition to JTEN-U that will provide unclassified services with global reach.

• Joint Training and Experimentation Network -Secret, (JTEN –S) The JTEN Services

functional area is composed of client/server hardware, software and services needed to execute exercise planning, execution and after action review at up to the US Secret level. This set of services is global in nature and includes both garrison and deployable equipment with reach-back capability.

• Coalition Exercise Support Network: The JWFC Exercise networks include several

instances of Coalition Services that can be configured to serve any of our combinations of coalition training events. This capability can support multiple collateral classification levels and includes both garrison and deployable equipment with reach-back capability as the situation requires.

• Applications/Database – this functional area includes GOTS/COTS applications,

databases, database models and structures, both home station and deployed, needed to plan, execute and review the exercise events in support of the JFCOM/J7 joint training mission.

• The Joint Digital Library provides an enterprise, globally accessible, real-time data

repository capable of using data mining, storage, retrieval techniques to support real-time data acquisition and processing in support of exercise post-action review and knowledge management.

° Command, Control, Communications, and Computers (C4). The C2 Group

engineers interfaces for the Model and Simulation (M&S) system to real-world Command and Control (C2) systems. Real-world systems were not originally designed to interoperate with the simulation system, thus interfaces must be developed to provide data transfer from each simulation to stimulate each command/control system. The C4 system is sub-divided into the following major functional areas:

° Intel supports intelligence gathering, analysis and distribution such as: JDISS,

NACCIS, GCCS-I3, JDISS-NT, ASAS and other various components to provide interoperability (OII, OIW, C2Guard, Radiant Mercury, etc.) as required to support in-garrison and deployed exercise events.

° Command and Control (C2) allows the warfighter to manage the battlefield.

These systems are real-world C2 systems, such as: GCCS, LOCE, TBMCS, MCS and other C2 components as required to support in-garrison and deployed exercise events.

l. Video Systems(VS). The Video Systems Group provides digital and analog subsystems that

support local and remote distribution of video materials (VTC, TV production, etc.) in support of the JFCOM/J7 training mission. This system is used to facilitate exercise planning, execution and after-action review of exercise events. The VS is sub-divided into the following functional areas:

(1) Video Distribution (VD provides secure and non-secure video transmission, distribution and replay in support of the entire event cycle (from planning through to post event review)


(2) Info OPS/Television Production provides for simulated video injects which assist in the event scenario development. The primary tool for this function is the World News Network (WNN) studio that provides customized broadcast quality media to be introduced to the training audience.

(3) Distance Learning provides distribution, via digital or analog methods, of training content and material. This system is used to provide pre-event training to improve the quality of both in-garrison and distributed training.

m. Event Support(ES). The Event Support Group made up of technical experts from IT, IS, IA, and C4. Event Support closely coordinates between Planners, NOSC, JST, and Systems Engineering. Their main function is to work directly with Event planners to apply direct Systems Engineering effort and coordination needed for the JFCOM/J7 to perform the exercise mission.

n. Communications(COM). The Communications Group is responsible for providing communications in support of the JFCOM/J7 exercise mission. There are three functional areas within this group.

(1) Communications Provides for telephone, and commercial and DOD communications services for the JFCOM Suffolk Campus.

(2) The Communications Security (COMSEC) provides all required COMSEC Services and controls of all (training and real world) JWFC COMSEC material.

(3) Infrastructure physical plant provides for the physical infrastructure that carries electrical and communications signals throughout the facility. 12. Waiver Process: The Joint Training Network waiver process is used to control all non-standard requests to modify the security posture of the administrative training networks. There are two primary groups within JFCOM who control and approve the waivers; JFCOM J6 (Joint Force Communications) and JFCOM J7 (Joint Force Trainer). As a result, a waiver may be J6 action only, J7 action only or J6/ J7 action. JFCOM J6 controls all of the administrative networks and access to SIPRnet and SIPRnet. JFCOM J7 controls all of the Joint Training Networks including JTEN-S, JTEN-U, Cox, Coalition and some others. During the majority of Joint Trainer exercises, the training networks require access through J6 networks to the SIPRnet to communicate, collaborate or stimulate real world systems. J6 serves an “honest broker” for training connections to real world. While some waivers begin with system administrators for altering the baseline of the training networks, most of the waivers will begin with the Communications Planner.

a. When the Communications Planner, or designated representative, determines a waiver is needed in support of a persistent requirement, an ongoing or future event; the planner or designated representative will fill out the appropriate waiver request form. They will then send the form to the JTEN NOSC via the JTEN IA inbox at [email protected] Once an email is received with the attached waiver, the JTEN NOSC will review for correctness then create and assign a trouble ticket tracking number to the waiver request. At this point the JTEN NOSC will forward the waiver trouble ticket to both IA/CND and the originator of the waiver. The IA/CND branch of the Joint Support Division (JSD) begins the approval process after it is reviewed by forwarding the waiver to the appropriate agency. IA/CND will review the waiver request for technical accuracy, form version, and security considerations as per the Ports Protocols Services (PPS) Assurance Category Assignment List. IA/CND will forward the waiver to the IA/CND Approval Authority. Waivers failing the IA/CND review (technical, security, other), will be routed back to the originator with the explanation and courses of action available to correct the waiver. This will all be done through the IA/CND cell here at JWFC. After approving the waiver, IA/CND review IA/CND will forward the waiver to the designated approval authority based on the nature of the waiver: J6 approval for requests outside of the JWFC enclave and J7 for requests within the JWFC enclave. Both will return the waiver to the JTEN NOSC.


b. J6 Approval: Unless urgent, all waivers will take a nominal timeframe of 5-7 days for approval. JTEN IA/CND can mark a waiver request with urgent to ensure a timely approval is granted, usually 1-3 days. IA/CND will send the request via the JTEN IA mailbox to ensure all communication with J6 use the same email address. When a waiver comes back from J6 approved, IA/CND will forward the approval to the NOSC who will update the waiver trouble ticket and continue to track throughout the waiver’s lifecycle.

c. J7 Internal Waivers: Upon approval of J7 internal waivers, the approval authority will send the waiver back to the NOSC via JTEN IA mailbox. The NOSC will then determine if the waiver is a firewall waiver or an Access Control List (ACL) waiver. For ACL waivers, the NOSC will implement the waiver and document the implementation on the trouble ticket. ACL waivers will also have a 24 hour implementation window. The NOSC will perform testing on the ACL waiver to ensure the waiver is working as designed after implementation. For firewall waivers, the NOSC will annotate approval in the trouble ticket and forward the waiver to systems engineering branch for implementation. Implementation for firewall waivers will occur within 24 hours. Once the systems engineering branch notifies the NOSC the firewall waiver is implemented, the NOSC will contact the originator. The originator then is responsible for testing the waiver implementation and notifying the JTEN NOSC with any issues or concerns. Once a waiver is approved and implemented, an open trouble ticket will remain in the Waiver Tracking Tool until conclusion of the dates specified on the Waiver. Upon conclusion of the event, the Firewall and ACL waivers expire and the trouble ticket is closed. The trouble ticket is then archived and the process starts again as the next waiver request is received. When an existing waiver requires modification, use the following process to ensure seamless modifications without loss of information: Resubmit original waiver with obsolete information lined out and new modified information highlighted. Place a brief summary of the modification at the top of the request, of what the modification is and what it is for. A waiver modification will get a new tracking number to distinguish from the original but allow correlation between the two waivers, and will follow the same process as a regular non-modified waiver. 13. COMSEC: Communications Security (COMSEC). Inter-theater COMSEC Package (ICP) materials or modern key will be used on all joint circuits. The CJTF will identify joint circuit requirements and ICP and modern keying material for each circuit and each type of cryptographic hardware to be used. COMSEC personnel will receive and coordinate key material and secure voice requirements from the exercise planners. The ICP intent to use message identifying required keying material for the exercise will be originated by the CJTF and promulgated to all participants and to the Joint COMSEC Management Office no later than 60 days prior to the exercise. Components who do not currently hold the specified ICP material or modern key short titles required for the exercise must initiate validation/ordering procedures. Components must request authority to receive and utilize ICP material from JCMO via their respective service component headquarters. The COMSEC callout message identifying ICP material short titles and editions will be promulgated by the CJTF no later than 30 days prior to the start of the exercise. Cryptographic key change times will be determined by the component commander and the CJTF and will be included in the COMSEC callout message. The COMSEC manager must be apprised of any keying material being brought into the compound. 14. Network Operations and Security Center (NOSC). In FY04, JFCOM initiated a phased build of the Joint Training and Experimentation Network (JTEN), a high-bandwidth network currently linking 39 Continental United States (CONUS) and 4 Outside the Continental United States (OCONUS) training sites along with the capability for linking 7 non-persistent sites to meet temporary requirements. The JTEN also connects to networks of like classification to expand the number of sites that can participate in Joint training. 15. The JTEN Network Operations and Security Center (NOSC), located at the Joint Warfighting Center (JWFC), in Suffolk Virginia is the heart of the entire network. The NOSC is responsible for the logical configuration, status monitoring (both active and passive), trouble identification, tracking and correction, and Information Assurance monitoring and reporting for the entire JTEN. Although mainly responsible for


the overall health of the operational JTEN, the NOSC will also coordinate with and provide next level network troubleshooting support to the designated Service or Component Network Control Centers participating in an ongoing event. The JTEN NOSC is also responsible for scheduling all events to ensure bandwidth and key resources are readily available to support multiple simultaneous exercises at one time. The CS planner will coordinate NOSC support during the JELC, or in processing a JTEN Request.


Intentionally Blank


Enclosure (17): The Joint Training Tool Kit

The Joint Training Tool Kit is comprised of two federations and associated federation tools. These federations are the Joint Multi-Resolution Model (JMRM) and Joint Live, Virtual, Constructive (JLVC) Federation. These federations are designed to support all types of joint training. JMRM: The JMRM federation is comprised of the Joint Theater Level Simulation (JTLS) and the Joint Conflict and Tactical Simulation (JCATS). JTLS is an aggregate level simulation that replicates ground, air and maritime at a high level. At an aggregated level JTLS also has logistics, deployment and intelligence capabilities. It has the ability to process a TBMCS ATO with a limited ability to fly the ATO out. JCATS is an entity level simulation that also replicates ground, air and maritime. JCATS can use detailed terrain that allows modeling of individual rooms in individual building, complex road networks, elevation and vegetation. This federation has a C4I interface, called the JTLS Operational Interface (JOI). This interface stimulates the GCCS COP. JLVC: The JLVC federation is an entity based federation that federates live, virtual and constructive forces into one synthetic environment. This federation makes use of service entity level simulations. The main federates are:

• Joint Conflict and Tactical Simulation (JCATS) • Air Warfare Simulation (AWSIM) • Joint Simulation of Automated Forces (JSAF) • JCATS Low Overhead Driver (JLOD)

It has intelligence and logistic support from:

• National Wargaming System (NWARS) Next Generation (NG) • Tactical Simulation (TACSIM) • Air Force Constructive Environment – Intelligence Operations Simulation (ACE-IOS) • Joint Deployment and Logistics Model (JDLM) • Logistics Simulation (LOGSIM) for logistics and deployment

The federation has a host of federation and C4I tools, and may use one or a combination of the federations that follow;

• Air Force Constructive Environment – C2 Simulation Interface (ACE-CSI) • SIM-C4I Interchange Module for Plans Logistics, & Exercises (SIMPLE) • Air Force Synthetic Environment for Reconnaissance and surveillance (AFSERS) • Joint Exercise Control Station (JECS) • Joint Exercise Control Station – No SIM (JECS-No Sim) • Joint Simulation Control Analyzer (JSPA) • Joint Deployable After Action review System (JDAARS) • High Level Architecture – Distributed Interactive Simulation (HLA-DIS) Converter (HDC)

The JLVC Federation stimulates the following C4I systems:


• TBMCS – Theater Battle Management Core Systems • AFATADS – Advanced Field Artillery Targeting and Direction System • AMDWS – Air & Missile Defense Work Station • DCSG-A – Distributed Command Ground Station - Army • BCS3 – Battle Command Sustainment and Support System • CPOF – Command Post of the Future • FBCB2 – Force XXI Battle Command, Brigade-and-Below • MCS – Maneuver Control System • GCCS – Global Command & Control System • JADOCS – Joint Automated Deep Operations Coordination System • JOPES – Joint Operation Planning and Execution System • ADSI – Air Defense Systems Integrator • GES – Global Transportation Network (GTN) Exercise Server


Enclosure (18): JWFC Event Testing 1. Exercise Data Validation (EDV): Prior to any valuable testing of the exercise federation, the data that will initialize the models needs to be identified and validated by the training audience. Event planning needs to be mature enough to have a solidified storyline and all of the unit types participating identified. The focus of this event is development of the exercise database with a focus on getting the training audience inputs on force structure and their STARTEX positions. The second goal of this event is the verification that the terrain, force list and platform databases will be accepted by the federation models that will be used in the exercise. The model support required in this event would be limited to the use of the primary ground, air and sea models to verify that the vehicles that will be used in the exercise are able to traverse the terrain from the database, and that the platforms can use the weapon loads planned. If the MSEL development conference or the Initial Planning Conference is held at the JWFC, conducting these events concurrently would provide the database developers with access to the training audience Subject Matter Experts (SME) to clarify any issues that are discovered during the test.

A list of potential desired outcomes of the EDV are:

• Identify command hierarchy and Table of Organization and Equipment (TOE) • Identify database discrepancies, corrections, model workarounds, controller procedures • Assess terrain file

– Validate urban terrain and enhanced buildings features – Validate a system’s ability to move, acquisition and engage in various types of terrain – Validate terrain traffic ability data to include maximum vertical step (meters) that a system

can maneuver over – Validate workstation raster map sets – Identify 1 meter raster imagery requirements for areas of interest

• Check accuracy of unit symbols and naming conventions • Identify Unmanned Aerial Vehicles (UAV) requirements • Identify initial baseline Global Parameters

– Weather Conditions – Weather Effects – Lighting – Level of Fidelity – Dart Weather

• Identify Level of Fidelity Options: – Food and Water Play – Casualty Play – Craters – Enhanced Building Damage – FBCB2, BCS3

• Verify / Define Casualty/Damage Classes: – Casualty/Damage Codes; kill type, treatment/repair times, etc – Casualty/Damage Probabilities – Munitions Effects Classes against Casualty/Damage Classes with appropriate

probabilities effects – Assign Munitions Effects Class to all munitions as needed – Assign Casualty and Damage Classes to all systems as needed – Assign repair/medical capabilities to all systems as needed – Add parts/medical items to supply list – Add required supplies to systems that will be doing the repairs/medical treatment

• Verify exercise response cell manning / configuration requirement


2. Exercise Functionality Test (EFT): This event takes the database that was validated during the EDV and begins testing it within the exercise federation. The focus of this event would be the cross model interactions of the forces and equipment in the database. The entire federation of models planned for the exercise would be tested during this event, in the architecture that is planned for the exercise, using the federation version (whether JMRM or JLVC) that will be used for the exercise. Any virtuals planned for the exercise should participate in this test. If Live instrumented equipment/personnel are planned, a means to validate their performance and interactions should be tested also. This event would be primarily held at the JWFC, but if other models are being operated from other locations, then those remote sites shall be included. At the completion of the Functionality Test, the models federation and database would be closed to any other changes. After this point any major changes to the database would require concurrence from the main training Exercise steering group after they have been briefed on the risks involved with making these changes. This event should be conducted in between the Main and Final Planning Conferences.

• Data Review Objectives:

– Validate input of previously identified data change requests. – Assess accuracy of all change requests. – Review unit table of organization and equipment (TOE) and Start-ex locations. – Assess accuracy of air weapons loads, assignments to target types, and lethality against

the target types. – Verify target database. – Identify/assign naming conventions for optimum unit/target identification and compatibility

among federated systems. – Identify database discrepancies. – Review combat system assignments to units, assigned equipment categories, sub-

categories, ranges, and system capabilities. – Assess aircraft squadron, base/carrier assignments, number and type of aircraft,

standard conventional loads, and target mission compatibility. – Validate command and support unit hierarchy. – Review and execute logistics functional testing. – Confirm intel sensor parameters.

• Federation Functionality objectives

– Review and assess unit engagement, movement and attrition factors. – Assess explicit ground fires capabilities. – Assess air-air, air-surface, surface-air engagements, surface-surface, BDA and attrition. – Review and assess logistics factors, stocks and consumption. – Assess naval functional capabilities with an emphasis on prior exercise lessons learned. – Validate model message output. – Validate submarine detection parameters. – Verify terrain and trafficability data. – Verify that specific advanced ballistic missile defense systems of interest to the training

audience can be adequately modeled. – Assess OPFOR air defense lethality. – Assess USQ sensor capabilities and lethalities. – Test submarine functionality.

• Federation Interoperability objectives

– Assess message generation by Intel Models (i.e. ACE-IOS, TACSIM and NWARS NG). – Verify that target databases match between models. – Verify enumeration data (the mapping of entities from one model to another). Due to time

constraints during the test, it is intended that the majority of this verification will occur prior to test start during federation testing.

– Verify that damage to targets that occurs in ACE-IOS is being correspondingly updated within each model and is also reflected in TACSIM and NWARS NG.

– Assess simulation federation functionality and stability.


• Sim C4I Objectives

– Simulation and C4I objectives--assess federates and the ability of C4I interfaces to produce message feeds. Also refine technical control procedures and work arounds:

• Transmission of OTH gold/USMTF messages to GCCS. • Transmission of TADIL J air and maritime surface tracks to the air defense

system integrator (ADSI). • Validate simulation to C4I system communications. • Fly out the ATO produced by TBMCS. • Check completeness and accuracy of unit symbols and names to be displayed in

the COP. • Fly out the intel collection plan to the extent possible and validate simulation

product output. • Conduct JTEN connectivity tests with all remote exercise locations.

• Intel Objectives

– Review and validate simulation intelligence products produced by the simulations. These

products include messaging products such as TACELINT, TACREP, IPIR, RECCEXREP, and MISREP reports.

– Review/revise procedures for creating the Start-ex intelligence paint. – Verify that where applicable, simulation intelligence products can successfully be parsed

by training audience intelligence C4I systems. – Work with training audience representatives to ensure that the flow of simulation

produced intelligence data planned for the exercise will provide the required level of stimulation.

• Non-technical objectives

• Response cell familiarization / training • Further, it is intended that both Exercise Functionality Test (EFT) and Exercise Operational

Test (EOT) will serve as critical training events for personnel who will man response cells during exercise execution. Accordingly, continuity of FT attendee and JECG manning assignments is highly recommended. During FT, attendees will establish initial familiarity with model interactions and with the response cell leadership responsibilities that will be expected of them during execution.

– What units & commands is my response cell role playing? – What training audience units & commands is my response cell stimulating? – What means (email, phone, chat, message traffic, etc) will I use to interact with my

portion of the training audience?

3. Exercise Operational Test (EOT): This event will be scheduled just prior to the exercise execution and would involve vignette testing of the entire distributed federation. These vignettes would be based on the MSELs that are scheduled for the exercise in an effort to uncover any issues that may arise during execution. These vignettes should be conducted in the same geographic area as the actual MSELs in order to reduce the number of unknowns during execution. By using this method, for each MSEL, the weapon system, unit, and terrain would be verified prior to executions. This event would include the entire model architecture as well as the Command and Control (C2) systems being used by the training audience. By scheduling this event just prior to execution, all simulation and C2 stimulation connections would be maintained through execution. This will reduce the manpower required to establish these networks multiple times throughout testing. 4. While most JWFC events will lend themselves to this system, some will not. It is imperative that we never lose sight of the fact that we are supporting the Combatant Commanders training programs during these exercises. If additional testing is required for a particular exercise then we must be flexible enough to modify this paradigm to deliver an exercise support plan that supports their needs.


Intentionally Blank


Enclosure (19): JKDDC Support to Joint Training 1. Joint Knowledge Development and Distribution Capability (JKDDC) develops joint training products and services in response to JKDDC stakeholder (Combatant Commands, Services, and Combat Support Agencies (CSA)) identified requirements and delivers global access to its Joint Knowledge Online (JKO) Portal system providing access to Web-based courses and learning tools to provide training necessary to prepare in advance for joint training exercises and integrated operations. JKDDC is a service organization providing content development and online hosting in response to validated, prioritized training requirements. In addition to the development of new courseware, JKDDC validates and maintains currency of existing courses. Further, the intent is for all Joint courses and Service modules to be Joint certified. JKDDC certifies all newly developed courses as Joint certified and works with Service modules to achieve Joint certification. JKDDC continuously explores content expansion and sharing opportunities to enhance joint training.

2. Joint Knowledge Online (JKO). JKO training resources are available via three networks: military unclassified NIPR net (http://jko.jfcom.mil), military classified SIPR net (http://jko.jwfc.jfcom.smil.mil) and public access via Internet (http://jko.cmil.org). All three portal channels provide access to the JKDDC tailored learning management system (LMS) that tracks, documents and reports student progress. Course status and completions are recorded in the LMS so that students and training managers can track progress. The LMS also integrates with the Army Training Requirements and Resources System for Service-wide joint training recording and reporting. 3. Each instantiation of the LMS is customized to the particular network: The LMS on NIPR net provides access to all JKDDC courseware with the exception of classified material. The LMS on SIPR net provides all courseware found on NIPR net with the addition of classified courses and material. The LMS via Internet Public provides access to unclassified, non-FOUO courses that are relevant to joint, integrated operations.

(a) Training Products and Services. JKO hosts over 275 operationally relevant joint courses (~1,300 hours of instruction) including multinational and interagency courseware and is continuously developing and adding content in response to stakeholder submitted requirements. Training requirements can be submitted to JKDDC for review and qualification by contacting the JKDDC JMO Knowledge Services Division. 4. JKDDC also continuously explores content sharing opportunities and establishes Communities of Interest for joint communities in response to stakeholder requests. A Community of Interest provides a forum for practitioners of a discipline to interact and share knowledge and experiences pertinent to their tasks at hand, akin to a tailored Web-based individual toolkit. Communities provide a method for individuals to keep each other current in the developments of a shared discipline and assist with better top-down communication by providing multiple direct methods of sharing information and ideas. 5. The Joint Task Force Headquarters (JTF HQ) Training Community is a prominent community on JKO. With the JKO portal launch the Joint Individual Augmentee Training (JIAT) Program designed to prepare Individual Augmentees (IAs) for Joint Task Force Headquarters assignment, transitioned from residential to online training. The JTF HQ communities on JKO provide tailored individual JTF headquarters online training, access to peers, expert help, best practices and lessons learned for all personnel who will be, are, or have been associated with combined, coalition or joint task force headquarters staffs. JKDDC tailored the originally “generic” IA training to Areas of Operation specific training – most recently, specifically for Horn of Africa, Afghanistan and Iraq pre-deployment training. 6. In addition, JKO provides training resources such as a Universal Joint Task List (UJTL) based search tool that associates all available training courses to specific UJTLs, resource links to joint training related sites, and JKDDC products such as the JKO Courseware and Capabilities Catalog, Stakeholder Newsletter, and the Civil Partnership and Training Opportunities Catalog.


7. To request a JKO Community of Interest: Interested users can go to the JKO Manager COI site, download and fill out the Service Request Form and e-mail it to [email protected]. For assistance, phoning the JKO Help Desk at (757) 203-5654 is another way to get a copy of this initiating form.

(a) JKO Exercise Support. JKDDC integrates with Training Operations Group Observer/Trainers, COCOM Desk Officers and event planners to provide online advanced training for exercises. For example, for the recent TERMINAL FURY 08 training event, the TF08 JECG training was expanded to include a Web-based ’Introduction to Computer Assisted Exercises’ course that was developed with assistance from JKDDC and hosted on the JKO Web site. JKDDC works to collaborate with exercise planners in the development of exercise related training and in making such training available via the JKO portal network for advance training and preparation opportunity. 8. JKDDC also works with exercise planners to establish exercise related Communities of Interest to facilitate collaborative exercise related information sharing via JKO. A particular benefit that JKO offers is the Internet access to JKO non-FOUO content for those organizations that are non-DOD / non-military and do not have access to the military networks. The JKO Internet Public site hosts communities for recent exercise events such as Regional Cooperation 2008 and National Level Exercise 2-08. Planners interested in developing exercise related training or communities should contact the JKDDC JMO Knowledge Services Division. (a) Accessing JKO. To access JKO via NIPR net and SIPR net all new users need to first register for a Defense Knowledge Online / Army Knowledge Online (DKO/AKO) account because JKO is hosted on the DKO/AKO platform. Network login and registration instructions are provided for all three JKO network channels: Network Login/Registration Instructions – JKO-N and JKO-S 1. To login to JKO go to http://jko.jfcom.mil and click “New User“ 2. All new users must first register for an account via DKO/AKO. Click “Joint Account" and follow

instructions for establishing an account. (NOTE: DoD/Services contractors must select “Sponsored Account” and use "joint.training" as your Army sponsor.)

3. Complete the account registration form being sure to provide your correct email address and social security number to expedite account approval.

4. You will receive two email notifications: 1) confirming sponsor approval and 2) confirming account setup. Once account is established go to http://jko.jfcom.mil, and click “Enter JKO.” See figure below:


1. Go to http://jko.jfcom.mil and click “New User” 2. Click “Joint Account”

3. Complete Form

4. Receive email notifications that account is ready.

Return to http://jko.jfcom.miland click on “Enter

JKO”5. Follow CAC login instructions

Figure 19-1. JKO Network Illustration.

You will be redirected to DKO/AKO. Follow login instructions and you will be redirected to JKO Home page. JKO-SIPR is accessible by military Service personnel and individuals with DKO/AKO SIPR accounts. If you already have a DKO/AKO SIPR account, go to http://jko.jwfc.jfcom.smil.mil and login using your Common Access Card (CAC) or user name and password. If you do not have a DKO/AKO SIPR account, follow these steps to set up your account. NOTE: See JKO-SIPR LMS account procedures on page vii.

1. to http://jko.jwfc.jfcom.smil.mil and select "Click here to enter JKO". You will be directed to DKO/AKO SIPR login page. 2. Under “New User” click on "Register for DKO-S". 3. Select "Create Joint Account" and complete form to obtain an account. Be sure to provide an external email address and social security number to expedite account approval. 4. You will receive 2 email notifications; 1) first indicating sponsor approval of the account and 2) second indicating DKO/AKO SIPR approval. Accounts become active with notification of DKO/AKO SIPR approval. Once your account is setup, follow instructions for login through DKO/AKO or go to http://jko.jwfc.jfcom.smil.mil and select "Click here to enter JKO".

Network Login/Registration Instructions – JKO-IP

JKO for public access is launched by entering http://jko.cmil.org from your Internet browser. Links to military, NATO, Partnership for Peace, interagency and intergovernmental information resources are immediately available on the home page. To access online training courses from the homepage or Members Portal via the “Take Courses” tab you need to set up an LMS account (described on page vii). To access Communities of Interest (COI’s) and other editing features you need to register for a members account.


The following steps describe the process for obtaining a members account to the areas of the portal that require a profile:

1. Go to http://jko.cmil.org. 2. From the JKO-IP home page click on “Become a Member” located under "Members Portal" in the

upper left corner of the page. Fill out the form that appears and ensure that your email address is correct. NOTE: Recommend checking the box “I would also like a JKO LMS account” if you would like the portal staff to create an IP LMS student account for you. You will receive an email notification once your IP LMS student account is ready. 3. You will receive an email confirmation with an attached link when your members account is

established. Click on the link, which will bring you back to our portal. You will be asked to change your password for security reasons. Once this is accomplished, you will launch into the Members Portal. 4. Inside the Members Portal, you will see that the tabbed menu selections on the top right have

expanded to include a "Communities" tab (our COI's). See figure below.

1. Go to http://jko.cmil.org and click on “Become a Member”

2. Complete the form, checking the box “I would also like a JKO LMS account” if you intend to take courses.

3. Receive email notifications when your LMS and/or Member

accounts are ready. Click on the link provided to

return to the portal.

4. Change your password for security reasons, and you will launch into the “Members” portal.

Figure 19-2. JKO Access Illustration.

To return to JKO-IP, go to http://jko.cmil.org and simply click “login” to enter the Members Portal. Use your login and password to launch into the Members site.


Enclosure (20): IO Support to Joint Training 1. Core, Supporting and Related Information Operations Capabilities.

(a) Core Capabilities: Information operations (IO) consists of five core capabilities which are:

electronic warfare (EW), computer network operations (CNO), psychological operations (PSYOP), military deception (MILDEC), and operations security (OPSEC).

(b) Supporting Capabilities: Capabilities supporting IO include information assurance (IA),

physical security, physical attack, counterintelligence, and combat camera. These are either directly or indirectly involved in the information environment and contribute to effective IO.

(c) Related Capabilities: There are three military functions, public affairs (PA), civil military operations (CMO), and defense support to public diplomacy, specified as related capabilities for IO. These capabilities make significant contributions to IO and must always be coordinated and integrated with the core and supporting IO capabilities. 2. IO Planners. A JWFC government IO planner, supported by a JST IO planner (when required), is assigned to each geographic combatant commander's JWFC supported exercise. The planner often coordinates additional support from other USJFCOM offices and external agencies. The government IO planner attends all remote planning conferences and JELC events for the purpose of assisting the training audience in design and development of the PSYOP, MILDEC, OPSEC, EW, and CNO portions of the exercise with the ultimate objective of achieving the corresponding training objectives identified by the training audience. 3. IO Training Objectives: IO training objectives are identified and affirmed during the design stage of each exercise by the training audience independently or during a formal training objective workshop. 4. Level of IO Play. The level and fidelity of IO play is developed and scoped at the IPC based on affirmed training objectives. IO play is dependent on overall exercise objectives, the spectrum of warfare (Phase 0 – Phase 5 operation), and upon the IO training audience's desires and availability of required resources. During the Master Scenario Event List (MSEL) development conference through the FPC, appropriate MSELs are identified and developed to meet the training audience’s training needs. 5. IO Support Tools. A number of tools and capabilities may be incorporated into exercises to enhance the training environment and support accomplishment of training objectives. Foremost of these is the Information Operations Range (IOR) which enables the training audience to experience real-world non-kinetic IO capabilities in a secure and safe environment. IOR also provides an event planner to develop the range architecture, and assist in recommending tools and supporting organizations. Additionally, when appropriate, JWFC can replicate adversary media capabilities, i.e. website or news agency to enhance the IO training experience. See paragraph 2 for more IOR information. Another new capability to support exercises is the Virtual Integrated Support for the Information Operations eNvironment (VisIOn). VisIOn synchronizes IO analysis, planning and assessment processes and capabilities through a web-based, collaborative environment to improve planning, and enhance mission execution and assessment. 6. External IO Agencies/Activities. IO exercise play can be enhanced with the participation of external agencies and commands such as the Joint Information Operations Warfare Command (JIOWC), 1st IO Command, and the Joint COMSEC Monitoring Activity (JCMA) within NSA. JWFC can help coordinate this participation if the training audience desires. External Support:

(a) OPSEC may include the use of Joint COMSEC Monitoring and Analysis Teams (JCMATs) from the Joint COMSEC Monitoring Activity (JCMA) to monitor all training audience computer and telephone networks for possible OPSEC disclosures.


(b) CNO may include the use of Service and NSA Cyber Red Teams to exercise the training audience against computer network threats. Most often this activity is done in partnership with the DOT&E sponsored Information Assurance and Interoperability (IA&I) assessment. Cyber Red Teams always operate under strict ground rules contained in a memorandum of agreement (MOA) with the training audience.

(c) EW may include experts in EW and spectrum management to exercise the training audience in the full range of challenges involved in coordinating the management of the electromagnetic spectrum in the Joint Operating Area (JOA).

7. Exercise Model Requirements. A robust level of exercise play is highly dependent upon construction of a thorough and accurate model database. Building the database is time-consuming detailed work. It is imperative that training audience personnel, including those representing the components, participate fully in the process. The command structure must be accurately entered and accounted for well in advance of the exercise to ensure the model accurately reflects IO impact during execution. See Chapter V, "Joint Event Life Cycle," for a more detailed discussion of the event test process. 8. Control of IO Play. During exercise execution, an IO functional response cell is formed to control exercise play. The JWFC government IO planner, JST planner, training audience IO planner, and representatives from external IO agencies normally staff the JECG IO cell. If the battle rhythm calls for 24 hour per day operations, manning for a second shift is required. Additionally, knowledgeable IO representatives generally are required within each Service response cell. Together, this IO team injects previously scripted events, controls the IO play, and replicates all IO bodies, at command levels above and below the training audience, to provide as much realism as possible for the training audience. 9. Additional Support. The JWFC Deployable Training Team supports most COCOM and JTF exercise programs across all functional areas, including IO. Observer/Trainers with IO, strategic communication, and public affairs expertise support the training audience’s IO and communication strategy training objectives. The team supports Combatant Commands via functional academics, exercise observation and out-briefs. Staff Assistance Visits are provided to deployed units. The team also conducts the Communication Strategy and IO portion of the Capstone/Keystone/Pinnacle senior leader education courses. Academic briefings are found at https://us.jfcom.mil/sites/Exercises/SLE/default.aspx 10. IO Range (IOR). The IOR is a confederation of IO environments linked to form a holistic, virtual range network. Interconnecting more than 40 member sites, the IO Range simulates realistic IO conditions in live, virtual, and constructive environments. The integrated environment includes traditional military Service and government ranges, laboratories, operations centers, training facilities, and tool and weapon development sites. The IO Range interconnects this infrastructure in a closed-loop environment to provide a realistic test, training, and exercise environment for developing and operationalizing IO weapon systems and their associated Tactics, Techniques and Procedures (TTPs). The IO Range currently supports computer network operations, electronic warfare, and to a lesser extent psychological operations, security and military deception. The IO Range is also exploring options for support of degraded networks and support to irregular warfare. The IOR will reach full operational capability (FOC) in 2011 once all five disciplines are supported. See figure below for Information Ops Range.


Figure 20-1. Information Operations Range

11. Security Levels. The IO Range can operate at any security level or at multiple security levels simultaneously. This ability provides users an opportunity to conduct operations through the IO Range in both cooperative and segmented environments. Specifically, the Range is accredited by Defense Intelligence Agency Designated Approving Authority (DAA) to operate at Protection Level-3 (PL-3) as a special category set by the Director of Central Intelligence Directive (DCID) 6/3, Para 9.G. The Authority to Operate allows the use of cryptologically separated Virtual Private Networks (VPNs) to enable operations at Multiple Independent Levels of Security (MILS) from Secret to TS SCI/SAR. 12. Utilization and Contact Information. The IO Range accommodates a variety of user’s requirements and usage is determined based on event priority. The JWFC government IO planner or JST IO planner responsible for supporting each exercise will coordinate with the IOR for support. Further information can be obtained by emailing the IOR Requirements section on NIPR: [email protected], SIPR: [email protected]; JWIC: [email protected] or by calling (757) 203-6852 or Toll Free at 1-866-630-6892.

Virtual Integration Support for the Information eNvironment (VisIOn).

(a) Background. VisIOn’s overall objective is to build an environment that brings together the

people, processes and technology to improve warfighter IO analysis, planning and assessment capabilities. VisIon in a spiral development process, and in early FY09, VisIOn will provide an initial IO analysis, planning and assessment capability. VisIOn’s initial operational capability is scheduled for FY10, with full operational capability in early FY12.


(b) Contact Information. If the exercise training objectives include the utilization of the VisIOn environment for analysis, planning and assessment, the JWFC government IO planner or JST IO planner responsible for supporting each exercise will coordinate with the VisION team for support. If required and approved, the VisIOn Mobile Support Team from the JIOWC supports exercise training audiences.


Enclosure (21): Service Support 1. Purpose The Joint Warfighting Center (JWFC) Headquarters Commandant (HQCOMDT) in conjunction with the Joint Support Team's (JST) Services Support Coordinator are solely responsible for coordinating all service support for non-local exercise participants. The JWFC HQCOMDT is responsible for developing the exercise service support plan, which provides guidance for lodging, transporting, and feeding exercise participants. Indirectly, service support includes such activities as coordination for in processing, transporting sick call members, scheduling religious services, and providing information through plasma screen displays. The JWFC HQCOMDT, with coordination and input from the JST's Services Support Coordinator, and JWFC Contract Specialists are also responsible for providing budget estimates on food, billeting, and transportation to the JWFC Desk Officer. Questions concerning service support should be directed to:

JWFC HQCOMDT Commercial: (757) 203-7113, DSN: 668

JST Services Support Coordinator

Commercial: (757) 203-7619/5978/7540, DSN: 668 2. General Information The JWFC HQCOMDT and the joint task force (JTF) HQCOMDT represent two distinct organizations. The JWFC HQCOMDT/Service Support Coordinator is responsible for pre-planning most of the functions within the service support area at the JWFC. The JWFC HQCOMDT is the advisor to the JTF HQCOMDT, but there are other key service support areas that the JWFC HQCOMDT interfaces with, to include Protocol, Security, Mailroom, and Warehousing. The JWFC HQCOMDT's checklist includes the following: a. Ensuring all visiting flag officers receive the personal services in a manner suited to their rank. Coordinate JWFC office space facilities for flag officers during the course of the exercise. b. Maximizing cost avoidance for service support provided. c. Coordinate with the JWFC scheduling branch for the use of the facilities to support the exercise. d. Monitoring the in-processing of exercise participants. e. Coordinating, assisting, advising, and monitoring the activities of the JTF HQCOMDT. f. Coordinating government transportation to medical facilities at regional military bases (sick call during the exercise). g. Assisting with the publishing of information materials for exercise participants. h. Coordinating reserve support for headquarters operations. 3. Billeting a. The JWFC HQCOMDT requests reservations from US Government lodging. Only after reservations at bachelor officer quarters (BOQ) and bachelor enlisted quarters (BEQ) rooms are exhausted will shortfalls be identified for commercial contract billeting. The remaining requirement not filled by the BOQ and BEQ will be contracted from outside approved sources by open bids from hotels


b. JWFC HQCOMDT will coordinate billeting reservations to house all exercise participants for JFCOM funded events that reside outside of a 50-mile radius of JWFC. Reservations should be made as early as allowable, but not later than four months in advance. The JTF HQCOMDT executes the billeting plan. When civilian contract rooms become necessary, two persons of comparable rank and same gender will occupy the rooms. Single room reservations will be made for officers in the rank of O-6 and above. In government quarters, rooms normally are single occupancy for staff noncommissioned officers in the grade of E-6 and above. JWFC HQCOMDT will request contracting support for billeting from the JWFC Contracts Supervisor and provide data, such as marketing surveys and the numbers of rooms required to support an exercise over a specified time frame. c. The JWFC HQCOMDT assigns rooms utilizing the JWFC HQCOMDT tool in the Joint Event Management Information System and strives for unit integrity based upon JTF structure. The JWFC HQCOMDT will publish room assignments on the USJFCOM Intranet (i.e., httpwww.jwf://c.jfcom.mil web site under the respective exercise) and maintain liaison with the JTF HQCOMDT throughout the process. d. JTF HQCOMDT issues rooms to participants upon arrival at JWFC. e. Accommodations usually are available at Langley AFB, Norfolk Naval Base, and the Norfolk Naval Shipyard, Portsmouth. All bases have adequate accommodations for all ranks. For specifics on billeting at each location, click on the following hyperlinks: (1) Langley AFB Billeting (2) Norfolk Naval Base Billeting (3) Norfolk Naval Shipyard, Portsmouth Billeting f. The JWFC uses civilian hotels with government contracts to support exercises. Hotels can change with each fiscal year according to the requirements. Civilian accommodations are used in the event that no government quarters are available. All visiting personnel in the rank or grade of O-5 and below will be assigned to a two-person room. 4. Dining a. The JWFC Dining Facility supports events and exercises as part of the USJFCOM joint training program. The JWFC Food Service Officer, commercial telephone (757) 203-7189 will coordinate and ensure high quality meals for events and exercises when the feeding of large numbers of personnel is required, at US Government expense. Per diem is not authorized for exercise participants. b. To request food service support, the following data must be received by the HQCOMDT at telephone (757) 686-7113, DSN: 668-7113, a minimum of 90 days prior to commencement of the exercise. (Note: this is the minimum information to ensure all requests have ample time to be addressed. JWFC HQCOMDT generally will initiate the dining plan six to twelve months prior to an exercise. (1) Date and time frame of exercise (2) Number of personnel per day (3) Number of meals per day (4) Point of contact coordinator of exercise (5) Special requirements. This can include box lunches, coffee service, extended meal times, midnight rations, or any special menu items.


c. Facility sanitation and safety inspections will be conducted during each meal to ensure meals are suitable and temperatures are maintained at the appropriate level. All food service areas, food vendors, barbers, and exchange spaces will be included in facility inspections. d. The Sunny Side Café seats 54 people and is located on the second floor (see Enclosure (14)). It has a grill and serves a variety of fast foods, cold sandwiches, pastries, and salads and operates from 0700 to 1400 hours on weekdays. Payment by individuals is required. 5. Transportation a. JWFC HQCOMDT will publish the transportation plan as part of the service support plan for a major exercise. The JTF HQCOMDT will provide a transportation chief, dispatch noncommissioned officer and drivers and establish necessary contracts for vehicles and drivers. The transportation chief will execute the transportation plan. JWFC HQCOMDT will monitor vehicle usage, bus occupancy, and all other factors to minimize expense. b. Exercise participants on temporary additional duty (TAD) and/or temporary duty (TDY) to this command will be provided group transportation between quarters and duty stations. The Public Works Commission of the Norfolk Naval Base provides buses as requested by HQCOMDT. Prior to exercise execution, buses depart the BOQs and hotels at approximately 0600 and depart JWFC at 1900 hours. During execution, which may include day and night shifts, buses depart quarters at about 0515 and 1700 hours and return at 0700 and 1900 hours. c. Sedans. Personnel in the rank of O-6 and above are assigned sedans. These officers must travel two to a vehicle. 6. Medical and Dental a. The JWFC HQCOMDT is responsible for coordinating medical support for all members participating in exercises. b. Exercise participants at the JWFC are responsible for ensuring they have adequate stocks of prescription medications. c. Medical and dental sick call will be conducted at the US Coast Guard Clinic at Craney Island. The capabilities of the Craney Island Clinic include routine, aviation, and diving physicals; optometry; gynecology; orthopedics; pharmacy; and limited after hours care. For specific information on medical and dental sick call, click US Coast Guard Clinic, Craney Island. d. For acute dental problems, Naval Medical Center, Portsmouth provides 24-hour emergency service. e. Military emergency room commercial telephone numbers (24 hours): (1) Naval Medical Center, Portsmouth -- (757) 953-1365 (2) First Medical Group Hospital, Langley AFB -- (757) 764-6801 (3) Naval Air Station, Oceana Branch Medical Clinic -- (757) 314-7181 (4) Sewells Point Branch Medical Clinic -- (757) 314-6301 (5) US Coast Guard, Craney Island Clinic -- (757) 483-8596 (0730-1600) (6) American Red Cross Armed Forces Emergency -- (757) 440-111


7. Funding a. TAD/TDY Funding (General Information) (1) USJFCOM authorized exercise participants, which includes the training audience and augmentees, will be issued funded TAD/TDY orders by their respective services. TAD/TDY funds may, or may not, include meals, transportation, local transportation and billeting. USJFCOM may provide contracted meals, government billets and government transportation. Specifics will be posted in the event or exercise reporting instructions. When rations, billeting and/or transportation are provided, TAD/TDY per diem will be reduced accordingly. If rations, billeting, and/or transportation are not provided, participants may contract with local hotels, local rental car firms and must purchase meals from local establishments. (2) USJFCOM will fund action addressees for augmentee travel and TAD/TDY expenses conducted in coordination with the exercise project officer, the joint exercise directive and the J-7, if not otherwise funded for joint exercise support. (3) Only those USJFCOM augmentees assigned a USJFCOM joint manning document (JMD) line number will be reimbursed for exercise participation. JMD line numbers must appear on all TAD/TDY orders. Reimbursements for exercise participation are accounted for by the exercise manning document (EX MAN DOC) line number. Orders missing the EX MAN DOC line number may not be reimbursed for costs. To ensure reimbursement, follow the prescribed procedures. (4) Funding will be forwarded by military interdepartmental purchase request (MIPR) based on the Commander, USJFCOM estimate of expenses. Action addressees will be reimbursed by issuing commands, and upon completion of travel, reconcile actual expenses with the JWFC Facilities and USJFCOM Comptroller. (5) The JST Travel Office will handle all JST contractor travel reservations. b. TAD/TDY Funding (Specific Information) (1) Commander, USJFCOM sends MIPRs out to components and agencies approximately 30 days prior to the exercise phase in which the funds will be used. (2) MIPR computations are based on the current EX MAN DOC. Funding amounts are computed for per diem, travel, billeting, and transportation for JTF participants and for USJFCOM augmentees. A list of EX MAN DOC line numbers that are funded for each component are forwarded with the MIPR to the appropriate finance offices. (3) Exercise reporting instructions indicate specific statements that must be included on TAD/TDY orders pertaining to billeting, messing, and transportation. (4) JWFC contractor travel arrangements will be made through the JST Travel Office. If “block” arrangements are made to ensure that a specified number of hotel rooms are reserved in support of an exercise, JST Travel will coordinate all supporting contractor arrangements. The JST Travel Office is the only authorized source for contractor use. c. Other Funding Requests. Requests for exercise funds other than TAD/TDY funds must be submitted in writing to the exercise project officer who will determine the type and amount of funding, if any, for exercise related expenses. Only funding approved and issued may be obligated for expenses. d. Reserve Component Funding. All of the above criteria apply to Reserve component units, elements and/or personnel in support, or as a trainee, in the exercise.


8. Service Support Plan a. The service support plan generally follows the design of a standard five-paragraph plan except only four paragraphs are required: Situation, Mission, Execution, and Coordinating Instructions. If a service support plan is used, the plan becomes a vital tool for organizing operations. Additionally, the document becomes an enclosure/annex to the joint exercise directive. b. Planning for service support should begin at least one year prior to the training phases of an exercise by using notional data from past experience. Room reservations should be secured six to nine months in advance, thus providing hard data for the billeting plan as a subset of the plan. Once billeting locations are determined, the transportation plan follows and other portions of the document, such as the dining plan, can be devised concurrently with development of the billeting plan. 9. Community Facilities a. Fort Eustis. Fort Eustis is located off exit number 250 of Interstate 64 in Newport News, Virginia. Click on Fort Eustis for specifics on community facilities. b. Langley Air Force Base. Click on Langley Air Force Base for specifics on community facilities. c. Naval Air Station Oceana. Click on Naval Air Station Oceana for specifics on community facilities. d. Naval Amphibious Base Little Creek. Click on Naval Amphibious Base Little Creek for specifics on community facilities. e. Naval Medical Center, Portsmouth. Click on Naval Medical Center, Portsmouth for specifics on community facilities. f. Norfolk Naval Shipyard, Portsmouth. Click on Norfolk Naval Shipyard, Portsmouth for specifics on community facilities. g. Naval Station Norfolk. The main installation telephone number is (757) 444-0000. Click on Naval Station Norfolk for specifics on community facilities. h. Norfolk International Airport. The military information booth can be reached at (757) 444-3040. There is a military representative on duty at the military information booth located in the lower level of the arrival terminal and is staffed from 0730 to 0100. 10. Telephone Information and Key Telephone Numbers a. A local telephone directory and a telephone listing of JWFC personnel is available in the main lobby at the Security Desk. Assigned personnel, and those with JWFC computer accounts, can consult Microsoft Outlook's address book. b. Customer Service Center has phones, message center, Cox lines, SIPR/NIPR, and CAC reset. c. For exercise telephone numbers and location of secure phones and faxes, consult the JTF, joint exercise control group support observer trainer, or immediate supervisor. d. Do not discuss classified information on non-secure telephones.


e. Key telephone numbers in area code 757.

Concession Telephone # Joint Training, Analysis and Simulation Center Help Desk

(757) 203-7777

Computer Help Desk (757) 203-2666 Joint Task Force (JTF) Help Desk

(757) 203-7777

Security Desk (757) 203-7900/7067 Security Office (757) 203-7174/7144 In-Processing/Test Bay 34 (757) 203-6196/6197 Joint Warfighting Center Headquarters Commandant (HQCOMDT)

(757) 203-7113

Joint Visitors Bureau (757) 203-7582 Library and Info Center (757) 203-7163 Mailroom (757) 203-7206 Graphics (757) 203-7287


Enclosure (22): Security 1. Security Responsibilities a. Joint Warfighting Center (JWFC) Desk Officer/Project Officer. The JWFC Desk Officer or project officer is responsible for initial coordination with JWFC Security (JT-02K), JWFC Support Team (JST) In-processing Coordinator, and the JWFC Information System Security Manager (ISSM) for: (1) Event classification (2) Event announcement messages (3) Participants and clearance requirements and process (4) Suffolk compound access (5) Badge requirements for planning conferences, event test, execution phases, and other meetings associated with the event. (6) Badge issue and control (7) Physical security and security force requirements (8) Automated information system (AIS) authorizations, scanning, and processing b. JST In-processing Coordinator. The JST In-processing Coordinator is responsible for coordinating with the ISSM for: (1) Access badges (2) Security support for clearances during in processing c. JWFC Security Director. The JWFC Security Director is responsible for the JWFC Security Program, to include information security, personnel security, foreign disclosure, foreign visits, physical security, industrial security, operations security (OPSEC), antiterrorism, and force protection. Event coordinators, JWFC Desk Officers, and/or the Joint Task Force (JTF) Headquarters Commandant (HQCOMDT) will coordinate all security issues with the JWFC Security Director. Questions concerning security can be directed to:

JWFC Security Manager (JT-02K) Commercial: (757) 686-7077, DSN: 668-7077

d. Special Security Officer (SSO). The JWFC SSO is responsible for the appropriate operation of the sensitive compartmented information facility (SCIF) and the security, control, and utilization of all sensitive compartmented information (SCI) at the JWFC facility. All matters relating to SCI or SSO requirements shall be referred to the JWFC SSO. The JTF SSO shall coordinate all SCI issues with the JWFC SSO. e. Communications Security (COMSEC) Manager. The JWFC COMSEC Manager is responsible for the appropriate management of all COMSEC material at JWFC, i.e., receipt, control, accounting, and destruction of all COMSEC material. All matters related to COMSEC material shall be referred to the JWFC COMSEC Manager. The JWFC COMSEC Manager shall also serve as the Top Secret Control Officer for Top Secret COMSEC material.


f. Information Systems Security Manager. The JWFC ISSM is responsible for the development of JWFC's AIS security policies and plans to protect classified information processed in the automated system. The JWFC ISSM and the JWFC Security Director shall coordinate the responsibility for appropriate protection of JWFC personnel, equipment, and related resources concerning AIS. All matters relating to the JWFC AIS Security Program shall be referred to the JWFC ISSM. g. Suffolk Compound Security Force. The Suffolk compound consists of four buildings: The J-9, Joint Experimentation Directorate; the J-7, Joint Force Training Directorate and JWFC; the Joint Technical Exploration Center, and the Security Office. The compound has a full time contract armed security force responsible for physical security, force protection, and law enforcement. The security force duties include, but are not limited to controlling access to the Suffolk compound, conducting vehicle searches, controlling access to buildings, inspecting personnel entering and exiting the compound and buildings, verifying visit requests, checking badges, escorting deliveries, and conducting security checks. h. Participant and Visitors Requirements. Participants and visitors to the Suffolk compound will register for all exercises, conferences, and other events. Participants and visitors will ensure a visit request with security clearance information is forwarded to the JWFC Security Office. All participants and visitors shall comply with the JWFC Security Policies and Regulations. To view these policies and regulations, go to the JWFC web page; click on security, and then to the JWFC Security Handbook and JWFC Security Plan. 2. Event Classification Classification Methods. There are two methods of classification of information: original classification and derivative classification. The Original Classification Authority in the JWFC is the Director, J7. The Director, J7 must make original classification determination and sign the Security Classification Guide developed for the JWFC. Derivative classification is the classification of information from a source document or classification guide. It is the supported organization's responsibility to provide and publicize the final classification guidance. Information or material in the classified annexes and/or appendices of the joint exercise directive is by the authority of the director whose functional material is in the appendix (e.g., classification authority for the classified intelligence appendix is the USJFCOM J-2). For exercise documents or sections without a functional identity, the classification authority will be the Director, J7 until final guidance has been publicized. 3. Participants The event coordinator should determine if the participants will be US only, North Atlantic Treaty Organization (NATO) only, NATO and Partnership for Peace, or multinational. All requests for Non-US participation must be US sponsored and must be submitted in writing to the exercise project officer, the JWFC Foreign Disclosure Representative, and the USJFCOM Foreign Disclosure Officer. The sponsor of Non-US participation is responsible for all coordination. US commands that have Non-US personnel on their staffs need to identify disclosure requirements, as soon as possible. Non-US participants will initiate a visit request in accordance with the Foreign National Access Requirements described below. Pre-planning and coordination for foreign participation is key to receiving the necessary approval. Action officers are responsible for coordinating with the security office any potential foreign visitors attending conferences, meetings, exercises, or other events. Visit requests and/or clearance verification cannot be accepted directly from the foreign visitor's organization. The visit request must be processed through the Defense Intelligence Agency. 4. Event Announcement Messages a. Event coordinators must ensure event announcement messages are reviewed by the JWFC Security Manager prior to release to exercise participants. b. Event announcement messages must contain at a minimum the following information:


(1) USFCOM Suffolk Compound Access. The USJFCOM Suffolk compound is a controlled site and the Suffolk Security Force will verify authorized access to the compound. Personnel not assigned to USJFCOM must have a CAC with a visit request on file. Vehicle access and/or parking will be restricted to DOD vehicle decals, temporary USJFCOM Suffolk compound parking passes, and/or DOD vehicle decals, depending on the force protection condition. (2) Clearance Requirements. The workspaces within the JWFC are restricted to individuals with US Secret clearances or higher. Most exercises are classified and the areas cannot be sanitized to accommodate un-cleared visitors. US exercise participants, observers and visitors must ensure their security managers send visit requests five days prior to their arrival at the USJFCOM Suffolk compound. (3) US Personnel. US personnel should have their security managers send a visit request with clearance information by message, fax, or e-mail to:

USJFCOM JWFC Security Office 116 Lake View Parkway Suffolk VA 23435-2697

voice: fax: secure fax: e-mail:

(757) 686-7174 (757) 686-7512 (757) 686-7012 [email protected]

To verify receipt of visit requests please call (757) 686-7900 or (757) 686-7174.

(4) SCI Access Requirements. US exercise participants, observers, and visitors requiring SCI access should have their SSOs send a visit certification message to SSO JWFC // JW0041//. The JWFC SSO's telephone number is (757) 686-7772/7776. (5) Foreign National Access Requirements. Foreign National participants, observers, and visitors must send their visit request through the Foreign Visit System (FVS) to the Defense Intelligence Agency. The FVS is the automated system, operated by the Office of the Under Secretary of Defense (Policy), that provides staffing and database support for processing requests for visits by foreign nationals to DOD activities and defense contractors. The FVS consists of an unclassified segment that allows the on-line submission of visit requests from foreign governments. Please note this is a lengthy process and all requests should be sent between 30 and 45 days from the date of the visit. To ensure the visit can be tracked by the JWFC Security Office when the visitor arrives, the visitor should know the assigned case number. 5. Badge Control and Issue a. Responsibilities. The HQCOMDT is responsible coordinating badge issue and control with the JST In-processing Coordinator. The HQCOMDT is responsible for issuing and controlling non-SCIF access badges to exercise participants. The JTF is responsible for coordinating with the JST In-processing Coordinator and the JWFC SSO for issuing and controlling SCIF badges. The JTF is responsible for issuing and controlling SCIF access badges for exercise participants. The JST In-processing Coordinator is responsible for retrieving all issued badges prior to departure. JST In-processing Coordinator will audit all badges and provide a report identifying badges missing or lost. Badges will be returned to the appropriate security office in numerical order. b. Badges. Upon arrival participants and visitors clearances will be verified and then issued a security badge. The badge must be worn at all times on the upper front half of the body, in common view. All badges shall be returned to JWFC before departure. A security report will be forwarded to the individual's commander and personnel security clearance adjudication office for all badges not returned after the exercise. Lost badges must be reported immediately to the JWFC Security Office. c. Visitors. Exercise and event personnel are not authorized to approve visitors to the JWFC. At no time will exercise or event personnel sign in and/or escort a visitor into the JWFC. Official observers will


be authorized access after the JWFC exercise/event project officer has approved and added them to the joint manning document. Official observers will then in process and badged. 6. Helicopter Operations The JTF will coordinate with the JWFC Security Director and the Joint Visitor Bureau concerning the arrival of very important persons (VIPs) via helicopter. Additional coordination may be required with other security agencies depending on the VIP. The JWFC Security Office will coordinate with the JWFC Security Force and the Suffolk Fire Department. See Enclosure 18, "Joint Visitors Bureau," for more information on the handling of VIPs. 7. Public Release All public release of information must be processed through the USJFCOM Public Affairs Officer (PAO) and the supported combatant command's PAO. The fact that information is unclassified does not authorize public release. See Enclosure (20), "Public Affairs," for more information on the release of information to the general public. 8. Sensitive Compartmented Information Facility Security The JTF SSO is responsible for all facets of security in the JTF SCIF and any JTF temporary SCIFs. The JTF SSO is responsible for coordinating all SCIF requirements through the JWFC SSO. 9. Physical Security The HQCOMDT will sign for all test bay and safe combinations from the JWFC Security Office and will issue the combinations to the JTF divisions as appropriate. Safe combinations are classified and must be stored as classified. Safe custodians will not carry the combinations on their person (i.e., in wallets, notebooks, purses) or record the combinations in any manner. The JWFC Security Director maintains a Standard Form (SF) 700 combination envelope for all security containers except containers containing SCI and the JWFC SSO maintains the SF 700 for all SCI containers. The JTF will not change combinations. Request for combination change will be made directly to the JWFC Security Office by calling the Help Desk. 10. Information Security Requirements a. Responsibility. All personnel are responsible for strict adherence to the security procedures in DOD Regulation 5200.1-R, Information Security Program. It is the personal responsibility of each individual to protect all classified material from unauthorized disclosure. Personnel shall ensure that classified material they prepare, process, transmit, transport, or store is not made available to persons without appropriate security clearance and a valid need-to-know. The appropriate control and safeguarding of all classified and sensitive material is an important key to the successful of any military operation. b. Restricted Areas. Although the JWFC building is a controlled facility and the test bays are designated as restricted areas, all classified material will be stored in the approved General Services Administration (GSA) security containers provided. The restricted areas are authorized for limited storage of classified material during exercises and other events, and large bulky items, maps hung on the walls, and the classified AIS internal storage media do not have to be stored in GSA containers, but must clearly be marked with the appropriate level of classification. The doors to all test bays must remain closed to ensure un-cleared or personnel without the need-to-know do not gain unescorted access. During exercise or other events, un-cleared personnel may not be escorted into restricted areas. The combination lock must be activated along with the magnetic card lock on classified workspaces when not occupied by cleared US personnel. c. Classified Materials. Personnel having custody of classified material are responsible for securing the material in appropriate GSA approved security containers whenever it is not in use or under direct


supervision of authorized persons. When securing classified material, personnel will use "Open" and "Closed" signs on containers to indicate status of the container. Personnel securing classified material will also use a SF 702, Security Container Check Sheet, for recording all openings, closings, and security checks on each container. When using or processing classified material, personnel will use a SF 705 (Blue Border) for CONFIDENTIAL, a SF 704 (Red Border) for SECRET, or a SF 703 (Orange Border) for TOP SECRET to cover the material to prevent unauthorized disclosure. 11. Classified Meetings Event or exercise classified meetings shall be strictly limited only to those with the required level of security clearance and a need-to-know. The speaker presiding over the meeting shall ensure that attendees are advised when classified information is being disclosed. All doors will be closed and audio-amplifying systems will remain at the lowest volume possible. 12. Marking of Classified Material a. Paper Media. Classified material generated on paper shall be marked with the appropriate classification markings. On the first page of the document, the overall classification level, originator, and declassification information must be displayed. All pages will be marked with the highest classification level of information and markings will be placed on the top and bottom centers of the page. b. Electronic Media. Classified material generated on diskettes, videotape and similar media will be marked externally with the overall classification level, originator, and declassification information. This information must be displayed on the external shell or attached casing. Personnel shall maintain classified material on the least number of disks as possible. Where possible, classified data should be segregated from the unclassified data on a disk. If this is not possible, the entire disk shall be marked with the highest classification of data contained on the disk and appropriately safeguarded. c. Access. All classified material must be safe guarded from unauthorized access, and destroyed by authorized means when no longer required or needed. All classified presentations, transparencies, and recordings will be marked in the same manner. 13. Procedures for the Reproduction of Classified Materials by Authorized Personnel a. Authority. Reproduction of classified portions of the joint exercise directive, in whole or in part, without permission of USJFCOM/JWFC is prohibited, except as required for the preparation of supporting plans. b. TOP SECRET Material. TOP SECRET material shall not be reproduce without approval of the JWFC Security Director and the consent of the originating agency or higher authority. c. NATO Material. NATO SECRET, COSMIC TOP SECRET, and ATOMAL material will not be reproduced without the approval of the JWFC Security Director. d. Safeguard. The material shall be safeguarded in the manner prescribed for its classification. The material will not, under any circumstances, be left unattended. e. Copies. Unwanted copies of the material shall be protected to prevent unauthorized disclosure until destroyed by authorized means. f. Markings. Reproduced copies shall bear appropriate classification, declassification markings and other special markings as required by the originator. g. Photocopying. After reproducing classified material, the photocopying machine will be checked to ensure the original and all copies have been removed.


14. Preparation of Classified Information for Transmission The JWFC mailroom will prepare and transmit classified. Classified material will not be routinely couriered. Personnel must request the JWFC Security Director approve couriering information. The JWFC mailroom will prepare classified material to be couriered. 15. Hand Carrying Classified Material The JTF HQCOMDT must approve in writing all request for event personnel to hand carry classified information off the USJFCOM Suffolk compound. Personnel authorized to hand carry classified information will receive a courier briefing from the JWFC Security Office. The JWFC Security Office is responsible for issuing Courier Authorization Cards, DD Form 2501, and/or Courier Authorization Letters to individuals authorized to hand carry classified material. A list of all classified material being hand carried shall be documented and retained by the JWFC Mail Room. 16. Destruction of Classified Material Classified waste material may be temporarily stored in burn bags. All classified waste material will be destroyed the end of each watch by using the provided shredders located in the space or the disintegrator located in the high bay. Do not assume the next watch will destroy your classified materials. 17. End of Day Security Checks a. Responsibility. JTF Divisions shall assign an individual(s) to conduct security checks of their respective divisions at the close of each working day to ensure that the area is secure. The SF 701, Activity Security Checklist, shall be used to record the security checks and the SF 702 will be used to record securing the test bay. After annotating the SF 701 and the Test Bay SF 702, the individual will notify the JWFC Security Desk that the area has been secured and the JWFC Desk Security Officer will record the test bay as secured. If personnel are working after hours, notify the senior individual present that he or she shall conduct the checks in the area and sign off on security sheet(s) prior to leaving the office. b. Security Checks. Security checks shall include the following items: (1) All classified materials are stored in approved container(s). (2) Burn bags containing classified material are properly stored or destroyed by authorized means. (3) Classified notes, typewriter ribbons, rough drafts, and similar papers have been properly stored or destroyed. (4) Security containers have been locked and signed off on the SF 702 by responsible custodians. (5) All local Internet management system packs, disks, cryptographic ignition keys, and other classified devices have been secured and/or accounted for. (6) All lights, coffee pots, and other electrical equipment has been turned off. 18. Equipment a. Government-Owned and Personal Equipment. Government owned or mission critical equipment entering the JWFC must be pre-approved by the property manager. Personal equipment, to include, but not limited to, cameras, recording devices, radios, cell phones, and laptops is prohibited Government Blackberries/PDA’s may be authorized. The property manager will inventory the equipment and issue a property pass, bar code the item, or otherwise document approval.


b. Photographic Equipment. Anyone with photographic equipment or other recording devices, transmitters, and receivers must obtain approval from the JWFC Security Office or the JWFC ISSM through a JWFC sponsor and be issued a Property pass/Camera pass. c. Undocumented Equipment. Equipment and AIS found in the JWFC without proper documentation may be confiscated pending an investigation. 19. Information Systems Security a. AIS. The following procedures will be followed for AIS brought into the JWFC shall: (1) Be in-processed during check-in at JWFC. (2) Be used for official business only. (3) Be in direct support of a specific event. (4) Have the approval of JWFC Information System Security Officer. (5) Be government owned. (6) Be properly marked with the appropriate classification. (7) Be virus scanned each time they enter the JWFC facility (8) Have a temporary JWFC bar code on the equipment. (9) Will have a JWFC property pass completed. The original will be given to the responsible courier and a copy will be placed on file and forwarded to the JWFC Material Manager. b. Automated Information System Courier. The following procedures will be followed for couriering classified information: (1) Have written documentation signed by specific written authorization by the responsible exercise point of contact. The documentation will identify the equipment and certify mission requirements. (2) Have a courier card and/or courier letter for classified AIS. (3) Not connect the AIS to any JWFC network without specific authorization from the JWFC ISSM. (4) Not removed a phone line from any secure telephone unit III or other telephone for the purpose of connecting a laptop modem. Laptop modem lines are installed in every JTF test bay and additional lines may be requested as needed via the exercise requirements process. (5) Scan all information downloaded to JWFC AIS prior migrating the data. (6) Return their copy of the property pass to the in-processing area, or other designated area, before removing the AIS from the JWFC building. (7) Ensure the property pass used to verify the laptop and the courier is annotated with the persons name verifying the information and date/time group the equipment left the building. The verified property pass will be collected by the JWFC Logistics Manager or representative, and used to update the Material Management System. 20. Operations Security


a. Process. Operations security (OPSEC) is the process of denying adversaries critical information about friendly capabilities and intentions by identifying, controlling, and protecting indicators associated with planning and conducting operations and other activities b. Indicators. Indicators are friendly detectable actions and open source information that can be interpreted or pieced together by an adversary to derive critical information. The goal of OPSEC is increased operational effectiveness achieved through the application of secrecy, surprise, and security. Critical information comprises specific facts about friendly intentions, capabilities, operations, and other activities vitally needed by adversaries to effectively plan and act against friendly mission accomplishment. c. Feedback. All levels of command will stress OPSEC during the planning, execution, and post-execution phases of the exercise/event. Authorized agencies will monitor exercise traffic and provide commanders with an overall evaluation of each organization's OPSEC posture. The use of secure voice communication systems and encryption devices, to preclude unwarranted disclosure of classified and or unclassified sensitive government information, will be emphasized at all times. d. OPSEC Officer. The supported command or organization will appoint an OPSEC Officer to: (1) Identify critical information early in the planning stages. Critical information consists of determining what are the five or six "core secrets" about an operation or plan needed by adversaries to disrupt or prevent mission accomplishment. (2) Analyze the threat, which involves knowing the adversaries, their capabilities and intentions, and the information they require to meet their objectives. (3) Analyze vulnerabilities, which requires a system analysis of operations, programs, activities, and facilities from the adversaries' perspective to identify weaknesses or vulnerabilities susceptible to exploitation. (4) Analyze the risk, which necessitates comprehension of the adversary threat to existing vulnerabilities and deciding whether adversary exploitation of each particular vulnerability warrants the application of one or more countermeasures. (5) Apply countermeasures, which include the development and implementation of methods to eliminate existing vulnerabilities and/or disrupt adversary multi-discipline information gathering and processing capabilities. (6) Ensure command personnel are aware of their critical information and the countermeasures to protect it. (7) Conduct periodic internal surveys to obtain feedback regarding the effectiveness of the OPSEC process within the command. 21. Planning Topics a. The project officer and HQCOMDT must cover a number of critical topics during the planning and execution of a joint training event or exercise. b. As a minimum, the following areas should be covered: (1) Event location (2) Clearance requirements to include visit request/clearance verification procedures for event participants


(3) Event classification guidance and procedures (4) Foreign disclosure requirements and foreign visit procedures (5) Force protection requirements and supplemental security force (6) Information security requirements such as storage and transmission of classified material (7) Compound access and parking (8) Building access, restricted area access, escort procedures, and badge requirements (9) OPSEC (ensure critical information is identified early in the planning stages) (10) Adverse weather procedures


Intentionally Blank

Enclosure (23)

ENC (23)-1

Enclosure (23): Visitors Bureau 1. Purpose This Enclosure provides policy and guidance for coordination, planning, and execution of support to joint training event and exercise visitors. The Joint Visitors Bureau (JVB), in support of the United States Joint Forces Command (USJFCOM) Joint Warfighting Center (JWFC) executes all visits and is responsible for directing all distinguished visitor (DV) evolutions with the joint task force (JTF) exercise directors, component commanders, and/or other training audience protocol offices. The JVB is located at USJFCOM's JWFC in Suffolk, Virginia. All DVs are considered guests of the Commander, USJFCOM (CDR USJFCOM) and will be scheduled per USJFCOM protocol guidance. Questions concerning the JVB should be directed to:

JWFC/Protocol Officer (JT-02P) Commercial: (757) 686-7582, DSN: 668-7582

Fax: Commercial (757) 686-7583, DSN: 668-7583 2. Mission The JVB provides support for DVs observing joint training events and exercises and/or routine or special operations at JWFC during exercise periods. DVs are defined as individuals of flag rank or civilian equivalent or those designated as such by USJFCOM. The Suffolk Complex Protocol Officer is the single point of contact for DVs requesting visits to JWFC. 3. Organization a. The JVB is the central location for coordination of visits to the JWFC. During exercise periods, the size and composition of the JVB is tailored to the scope of the exercise, significant planned events, and the number and level of DVs anticipated. JVB staffing will be included in exercise staffing documents. b. The Protocol Officer has overall control of the JVB and is tasked with ensuring DV visits are executed efficiently and without negative impact to the visitor or JWFC personnel and the training audience. Primary functions are: itineraries and all associated requirements, operations/logistics, liaison with USJFCOM and DV staffs, and coordinating briefings. The Protocol Officer will be kept informed of all visits for the purpose of briefing the USJFCOM J-7. During exercise periods, the JVB usually consists of the Protocol Officer, Assistant Protocol Officer/Administrative Personnel, the Visitor Coordination Officer and two enlisted coordinators, JTF Protocol Representative (liaison function only), and JVB drivers (an E-3 or above provided from the training audience's staff). c. The JVB, staffed by the Protocol Officer during non-exercise periods, is supported by resources within the JWFC, when required. d. During exercise periods the Protocol Officer's responsibilities are: (1) Prepare a detailed guest list to USJFCOM on potential invitees to the exercise. (2) Draft an invitation letter for CDR USJFCOM's signature. (3) Maintain a list of accepted and declined invitations to the exercise. (4) Schedule all DVs for visits to the exercise. (5) Act as central point of contact for DV movements and monitor itinerary progress.

Enclosure (23)

ENC (23)-2

(6) Provide all information pertaining to ongoing DV missions to Director, J7/JWFC. (7) Review draft itineraries submitted by administrative personnel. (8) Distribute, via e-mail, approved itineraries throughout JWFC and USJFCOM. (9) Act as liaison between JWFC and the USJFCOM Protocol Office. (10) Brief the Director, J-7/JWFC on future visits and itineraries. (11) Coordinate helicopter operations with JWFC HQCOMDT. (12) Coordinate all media inquiries with USJFCOM JWFC Public Affairs Officer. (13) Provide food service requirements to JWFC Food Service Liaison and monitor execution. (14) Ensure facility support is scheduled for each visit. (15) Coordinate graphic requirements for each visit. (16) Notify each briefer and tour participant of scheduled visits. (17) Prepare a long-range visit schedule weekly and distribute. (18) Establish and supervise the Visitor Coordination Office. See paragraph 9 below. e. The JTF Protocol Representative's responsibilities are: (1) Maintain liaison function between Commander, JTF/Staff and JWFC Protocol Officer. (2) Prepare a daily brief to the CJTF on scheduled visits. (3) Coordinate meetings and briefs between the CJTF and visitors. (4) Oversee any JTF personnel assigned to the JVB. (5) Act as escort officer on visits involving the CJTF. f. Assistant Protocol Officer/Administrative Personnel's responsibilities are: (1) Prepare/type draft itineraries for the Protocol Officer for review and approval. (2) Tour the proposed visit route for cleanliness prior to the start of the scheduled visit. (3) Greet and escort DVs during their visit. (4) Notify briefers of visitors in their areas. g. JVB Drivers' responsibilities are: (1) Provide local transportation to and from area commands, airports and hotels for DVs. (2) Maintain vehicles assigned to the JVB. (3) Park privately owned vehicles driven by DVs.

Enclosure (23)

ENC (23)-3

4. Visit Requests a. Requests for visits should be received not later than five working days prior to the date of the requested visit. b. The request for visit should contain the following information: (1) Name of DV (2) Security clearance information (3) Social security account number (4) Rank, position, and title (5) Proposed dates of visit (6) Mode of transportation to JWFC (7) Command or company: address, telephone, fax, proposed itinerary, goal of visit, host/sponsor, members of the official party. 5. Concept of Operations When information is received concerning a DV, the Protocol Officer will brief the Director, J-7/JWFC for approval or disapproval. Once approved, the DV is scheduled and his/her office notified. A draft itinerary is prepared and approved by the Director, J7. Upon final approval of the itinerary, the itinerary is published and distributed within JWFC and USJFCOM. All briefers and tour participants are notified. Any specific briefing subjects or issues are forwarded to the appropriate individual for staffing. The Director, J7, will approve all briefs. Visits are staffed on a case-by-case basis. Based on need, members of the JVB may be posted along the tour route with radios to alert each briefer and tour participant of the DV's whereabouts and pending arrival in their spaces. The Protocol Officer will notify the appropriate briefers and tour participants of any changes to established itineraries immediately via radio or in person. 6. Helicopter Operations a. Helicopter operations at JWFC are considered special evolutions and are generally limited to approval by the JWFC Deputy Joint Force Trainer, Operations on a case-by-case basis. Five to seven days' notification is required to support helicopter operations. Only daylight visual flight rules helicopter operations will be conducted. Only H-1, H-3, H-60, Bell Ranger, or comparable size aircraft (less than 21,000 lbs) will be allowed. Information for aircrew unfamiliar with the local area is available from Helicopter Combat Support Squadron 2, Operations, Naval Air Station (NAS) Norfolk, Virginia, by calling DSN 565-4818 or commercial (757) 445-4818, between 0700-1600 hours, Monday through Friday. Refueling and ground maintenance facilities are not available at JWFC. Inbound helicopters are requested to contact NAS Norfolk control tower or local flight service station via radio five minutes out. b. Notification of helicopter operations will be sent to the Protocol Officer by calling telephone number, (757) 686-7582, e-mail to [email protected], or via fax to (757) 686-7583. Notification will include the following information: (1) Name and rank of passengers (2) Date and time of arrival (3) Date and time of departure

Enclosure (23)

ENC (23)-4

(4) Type of aircraft (5) Tail number (6) Name of pilot and co-pilot (7) Point of departure and Defense Switched Network (DSN), commercial, and fax telephone numbers (8) Follow-on destination (9) JWFC approach briefing required (10) Special requirements (11) Ground point of contact and DSN, commercial, fax telephone numbers, and e-mail address. 7. Food Service Food service requirements such as exercise participant mass feedings, official lunches, receptions, coffee setups, and socials are the responsibility of the Food Service Contractor with oversight/review by the Protocol Officer. 8. Graphics Support Graphics support is not required for each visit. Requests for name tents for each member of the visiting party and a welcome sign for the senior member of the party are required on a case-by-case basis. All requests are forwarded to the JWFC Graphics Shop at least one day prior to the visit. The Graphics Shop, when required also provides photographic support. 9. Visitor Coordination Officer a. The Visitor Coordination Officer (VCO) tracks and controls visitors in the facility during JWFC exercises. The VCO controls access to the facility of visitors with a "need to know" while minimizing congestion and ensuring security. Telephone numbers for the VCO are commercial (757) 686-7030, DSN 668-7016, and fax (757) 686-7583. b. The processing procedures for visit requests are: (1) Receive request from sponsor or escort at the visitor's command. (2) Verify clearance at JWFC Security Office. (3) If clearance is on file, notify sponsor and schedule visitor for 2-hour block. (4) If clearance is not on file, notify the sponsor. Advise the sponsor or escort to send security information to JWFC Security Office (Fax - 686-7512). The sponsor or escort should contact the JWFC Security Office (686-7174/7144) for all foreign visitors. (5) Direct the sponsor or escort and visitor to the Visitor Coordination Office upon arrival at JWFC. (6) Have the escort and visitor sign in. (7) Issue an escort and escort required badge. (8) Brief the escort and visitor on visitor rules and provide a copy.

Enclosure (23)

ENC (23)-5

(9) Keep a daily log of visits and provide copies as required. 10. Visitor Control Policy a. Visitors are defined as those personnel in the grades O-6 and below, who are not exercise participants (e.g., not on the exercise manning document) and not JWFC or JWFC employees. Visitors will be limited to one visit period per day (approximately two hours). No more than 25 visitors will be allowed into the exercise area at any one time, therefore visitors should reserve a time through the Visitor Coordination Office. b. All visitors must have an escort officer from a sponsoring USJFCOM Directorate or JTF. Sponsors are responsible for determining potential visitors' need to know and ensuring visitors have current security clearances on file with the JWFC Security Manager prior to the date of their visit. Visitors will be issued "Visitor" badges. The following paragraph contains clearance request information. (1) Visitor security clearance verification must be sent by fax to the JWFC Security Manager at commercial (757) 686-7512, Attention: JWFC Security Manager. Visit request forms are available from the VCO/Protocol Office, at commercial (757) 686-7016. Questions about passing security clearances may be directed to the JWFC Security Manager at commercial telephone number (757) 686-7174/7144. (2) Security clearance verification must contain the following information: (a) Name of the visitor (b) Purpose and duration of clearance (c) Rank and Service (d) Social security account number (e) Date and place of birth (f) Citizenship (g) Unit /command/corporation (h) Duty telephone numbers (commercial and DSN) (i) Unclassified e-mail address, if any (j) Collateral level clearance (k) Security manager signature. c. Visitors requiring access to sensitive compartmented information facilities should have their supporting Special Security Officer (SSO) send a visit certification to SSO JWFC //JT-02S//. The JWFC SSO may be contacted at (757) 686-7776 / 7772. d. Visitors are required to have an escort officer at all times during a visit. This is accomplished by contacting a USJFCOM member to serve as a sponsor. Sponsors will provide the VCO with the name of the visitor(s) and the escort officer(s). A maximum of five visitors can be assigned to one escort officer. Sponsors must ensure that escort officers have access into JWFC and are knowledgeable about the exercise. Escort officers must also have the appropriate access to exercise areas that visitors are requesting to see. The minimum classification of all exercise workspaces is US SECRET. Escorts who are not exercise participants will be issued an "Escort" badge at the Visitor Coordination Office.

Enclosure (23)

ENC (23)-6

e. Visiting hours for Phases I and II will be 0730 to 1730. During Phase III, visiting hours will begin at 0730 and end at 1930. All inquiries at the JWFC Guard Desk regarding visits or visitor badges will be referred to the VCO. (1) When parking limitations have been exceeded or are expected to be exceeded, O-5 and below visitors may have to park outside the JWFC gate. O-6 visitors may park inside the gate in undesignated parking on a space available basis. JWFC gate guards will allow visiting personnel to pass through the JWFC gate with a valid military or government civilian identification card, or an exercise parking pass. Note that stricter access requirements, limitations, and checks may apply when the JWFC is subject to a higher threat condition other than Normal. (2) Visitors will pick up their exercise "Visitor" badges at the VCO when they sign-in on the day of their visit. Badges will be displayed clearly during the entire visit. The JWFC Guard Desk will not issue badges to exercise visitors. (3) Visitor badges will allow access to exercise player (blue) areas. Visitors desiring access to the joint exercise control group or opposing force cell should coordinate with their assigned escort officer. (4) Formal tours will be scheduled for visitors prior to the start of major exercises. Formal tours will be limited to a maximum of 15 personnel each. Visitor formal tours must be requested through the VCO. All other formal tours are reserved for DVs (O-7 and above). f. Visitors to the JWFC will adhere to the following rules: (1) Visitors will not enter areas where a DV tour is present. (2) Visitors will be mindful of noise and overcrowding. Appropriate exercise participants have the authority to ask visitors to leave if an area becomes congested. (3) Visitors will keep clear of the entrance to the joint operations center (JOC). This area is where DVs stand when they are shown the JOC. Visits to the JOC will be limited to 15 minutes. (4) Visitors are only allowed into the reception area of the Joint Information Operations Production Studio (where they can observe operations through the glass windows). Visitors may only stay at the Joint Information Operations Production Studio for 15 minutes. (5) Visitors will occupy only the last row of the Management Information Center (MIC) during presentations. Additional seating is available in the MIC Overflow Room. (6) The VTC Theater and Distinguished Visitor's Briefing Center are off limits to visitors. g. All visitors must sign out and turn in their serialized badges upon completion of the visit at the VCO. If visitors leave after normal visiting hours, badges must be turned in to the Guard Desk in the JWFC lobby. h. Personnel who need to observe an exercise for more than the normal visiting period should request observer status by e-mail to the exercise project officer (shown in our web site at http:\\www.jwfc.jfcom.mil) via a sponsoring USJFCOM officer. Sponsors are responsible for determining the observer's need to know. Sponsors must follow the security verification procedures outlined in subparagraph 10b. Observer line numbers are available on the joint manning document. These line numbers will be issued on a first come, first served basis. Observers will be issued "Observer" badges. Observers will in-process through the Joint Personnel Reception Center using the JWFC southeast entrance across from the helicopter pad.

Enclosure (23)

ENC (23)-7

i. Events at the JWFC are hosted in restricted areas. To enter the restricted areas unescorted individuals are required to have, at minimum, a US Secret clearance. Most exercises are classified and the areas cannot be sanitized to accommodate un-cleared visitors. Sponsors are required to determine if the person requesting to visit the exercise has a "need to know." Visitors and escort officers must ensure their clearances are on file with the JWFC Security Office by calling telephone phone number (757) 686-7174/7144. j. The exercise dining facility and the Sunny Side Up Café are available to visitors and non-participating escort officers at their own expense.

Enclosure (23)

ENC (23)-8

Intentionally Blank

Enclosure (24)

ENC (24)-1

Enclosure (24): JWFC Floor Plans First Deck:

Enclosure (24)

ENC (24)-2

Second Deck:


Enclosure (25): Public Affairs 1. Purpose This Enclosure provides guidance, for United States Joint Forces Command (USJFCOM) public affairs (PA) activities in support of joint training events and exercises conducted by the Joint Warfighting Center (JWFC). Questions concerning PA should be directed to:

USJFCOM Public Affairs Office Commercial: (757) 836-6555

2. General PA is essential to every military operation. DOD policy requires expediting the flow of accurate and timely information to the public and internal audiences. Quality joint PA training is key to preparing joint task force (JTF) commanders and their staffs to operate in challenging and diverse operational environments. 3. Mission for Real-World Public Affairs a. USJFCOM public affairs officer (PAO) and the supported combatant command's PAO have traditional responsibility for PA. b. Initial public announcement of events, if appropriate, is made by the USJFCOM PAO in conjunction with the supported combatant command's PAO via the USJFCOM publicly accessible web site. This release will be made no earlier than the exercise critical cancellation date. The release will contain general exercise information such as locations, dates, participating units, and major events to be conducted. Upon initial release, further release authority is delegated to supporting and participating commands with regard to their participation in the exercise. c. During events, participants must recognize the differences between day-to-day, or "real-world" PA responsibilities and activities and the "simulated" or artificial PA activities that are part of the training experience. d. Due to security restrictions that apply to the Joint Warfighting Center (JWFC) facility as well as to other training venues around the world, as well as the security classification/sensitivity of the exercise scenario and materials, "real-world" media coverage of the events probably will be limited. e. Internal military coverage of the event is important to recognize the Services, units, and individual soldiers, sailors, Marines, and airmen participation in the exercise. Care must be given to insure that the classification guidance provided in the joint exercise directive be closely followed. f. In all cases, "real-world" PA must be coordinated with USJFCOM PA. 4. Mission for Exercise Support a. The USJFCOM PA and the JWFC share responsibility to support JWFC events with professional PA services and products. b. PA training for supported combatant command's, JTF commanders and staffs, and the joint information bureau (JIB), will be provided through media role players covering training and exercise events, and training audience responses to simulated news events or master scenario events list items. Simulated news events may be provided to the training audience in the form of television news programs,


breaking news stories, and special reports. All members of the training audience may provide print news on a web site accessible. c. Staffing augmentation to support PA is essential to the fidelity of the products and services provided to the training audience. Specific requirements for a typical JTF exercise include two knowledgeable PAOs (O-4/5) to support the joint exercise control group, and six PAOs/journalists (two officer, four enlisted) to support the media simulation cell. Contractors assigned to the JWFC are staffed to provide the video production, web services, and oversight of the exercise. 5. Tasks a. USJFCOM PA (J00P) will: (1) Coordinate with the JTF Staff PAO and JIB Director to identify appropriate PA mission-essential tasks for selected key events to emphasize during training. (2) Publicize the exercise as appropriate, through the USJFCOM publicly accessible web site. (3) Coordinate with the combatant command and/or JTF Staff PAO and JIB Director to provide proposed "real-world" PA guidance, in accordance with joint PA doctrine. (4) Provide necessary observer/trainers for selected key events to train and observe PA exercise activities and personnel. (5) In cooperation with JWFC and JWFC planners, ensure that required equipment is available to conduct required exercise PA activities. (6) As may be required, escort, and arrange interviews for media who wish to cover events hosted at the JWFC or in the Norfolk, Virginia, area. b. Combatant command, JTF, and component commands will: (1) Provide qualified PA personnel as tasked in the joint exercise directive. (2) Keep USJFCOM PA informed of non-exercise media interest and queries regarding the exercise. (3) Forward all published news clips to USJFCOM PA. (4) Be prepared for non-exercise media representatives to visit units during all phases of the exercise. As appropriate, provide subordinate commanders with authorization to permit journalists to ride military vehicles and embark aircraft/ships when such visits are properly coordinated through USJFCOM PA via the USJFCOM Commander's Advisory Group and will not interfere with the mission. (5) Publicize individual unit participation in command information programs. 6. Arrangements for "Real-World" News Media Representatives a. For events conducted at the JWFC, USJFCOM PA will coordinate news media visits with the JWFC Deputy Joint Force Trainer, Operations, JWFC Media Branch (a subordinate branch to the civilian contractor JWFC Support Team's), the training audience, and JWFC security as appropriate. For deployed exercises, USJFCOM PA will coordinate news media visits with host installation and appropriate combatant command PA. b. Open and independent reporting is the principal means of coverage of US military operations. Support for accredited media will include access to unclassified operational information consistent with operations security guidance, communications facilities as available and emergency medical treatment on


a reimbursable basis. In return for this support, media representatives must agree to abide by media ground rules established by USJFCOM PA. c. All visiting non-exercise "real-world" media representatives will contact USJFCOM PA. A USJFCOM PA staff member or a unit representative acting under authority provided by USJFCOM PA will escort all correspondents covering exercise events. Prior to arrival at JWFC and JWFC, the home unit PA office will credential hometown news media traveling with participating units. For deployed exercises, the supported combatant command PA has responsibility and final authority for media visits. 7. Security a. Personnel assigned to brief media will not disclose classified information, and media representatives are not permitted unescorted entry into controlled areas such as operations and intelligence centers. All statements made to media representatives are on the record. b. Media stories are not subject to review. Security is at the source, which means responsibility for protection of classified non-releasable information rests with all personnel involved in the exercise. 8. Internal Information Service internal coverage of an exercise will be coordinated with USJFCOM PAO. Itineraries for internal media teams must be coordinated with USJFCOM PA and the supported combatant command PA prior to deployment. The sponsoring Service or command will arrange travel to and from the exercise area. 9. Command Relationships Before an exercise, participating PA offices, at all levels, are authorized, and encouraged to exercise direct liaison. Such coordination should not interfere with the normal chain of command. During the exercise, participants will use the command relationship provided in the exercise scenario. 10. Release of "Real-World" Adverse Incident/Accident Information a. Purpose. This paragraph provides basic procedures for the release of information concerning adverse incidents/accidents involving aircraft, vehicles, ammunition, ships, or facilities and casualties to personnel. b. Applicability. This paragraph applies to personnel of the US Army, US Air Force, US Navy, US Marine Corps, US Coast Guard, and to civilians serving with or accompanying these forces when participating in joint operations. It applies to USJFCOM within the geographic and air space limits of the exercise area. c. Definitions. For the purpose of this paragraph, four categories of adverse incidents are established. (1) Emergency: Any incident that results in the death of one or more exercise participants or that, in all probability, will result in the death of one or more exercise participants. (2) Accident: Any incident that involves serious injury to one or more exercise participants not causing death but requiring the individual's withdrawal from the exercise. Also, incidents that cause a short delay in exercise events or, if emergency procedures were not successful, would result in an emergency. (3) Civil Disturbance: Any incident that involves the local population disrupting the peace and order of the exercise range, from a nonviolent demonstration to actual interference with the conduct of the exercise.


(4) Routine: All injuries, equipment failures, and property damage that are not classified as emergencies, accidents, or civil disturbances. Incidents in this category will not involve adverse incident procedures. d. Basic Procedures. During joint exercises and operations, initial release of information concerning all types of accidents or serious incidents, except civil disturbances, will be made by USJFCOM PA and/or in conjunction with the appropriate combatant command PA. All initial inquiries from the public concerning these accidents or incidents will be referred to the appropriate combatant command PA regardless of the Service involved (1) Participating commands and units will notify USJFCOM PA and the appropriate combatant command PA as soon as possible when an adverse incident occurs. The JTF PAO will immediately make notification of an incident involving loss of life, serious injury to personnel, major damage to facilities, or other potentially newsworthy incidents. USJFCOM PA and the appropriate combatant command PA will pass this information to Office of the Assistant Secretary of Defense (Public Affairs). The Service(s) involved will immediately report the adverse incident through its public affairs channels in accordance with applicable regulations. This reporting is in addition to any required reporting in operational channels. (2) An incident occurring on or near a military installation hosting a joint exercise will usually fall under the jurisdiction of the host installation. Any requests from media representatives covering the exercise to visit the scene will be coordinated by the host public affairs office with the appropriate combatant command PA and USJFCOM PA. While media representatives are on scene, they will have access to the accident on a non-interference basis within the limits of established security policy and ensuring the integrity of the scene of the accident/incident. (3) An official spokesman will be designated by USJFCOM PA and the supported combatant command PA. All initial on-scene media queries will be referred to this official.


Enclosure (26): Manning Requirements 1. Purpose. The policies and procedures of this section apply to all US Joint Forces Command (USJFCOM)-sponsored exercises and those exercises of other combatant commands where USJFCOM has agreed to accept responsibility for control of the Joint Manning Document (JMD) or Exercise Support Manning Document (ESMD). In deployed exercises where the supported combatant commander controls the JMD, the Joint Warfighting Center (JWFC) Desk Officer will provide input and validate the line numbers in coordination with USJFCOM. Questions concerning manning should be directed to:

JWFC Exercise Project Leads

Or

JWFC Exercise Manning

Commercial: (757) 203-7425, DSN: 668-7425 2. Exercise Manning Document and Organization. In USJFCOM-sponsored exercises, the Exercise Manning Document encompasses an entire exercise and consists of two documents: the JMD and the ESMD. The JMD is the joint task force (JTF) commander's document and contains information on the JTF staff and all functional components that will deploy in a real-world scenario. The ESMD contains information on the joint exercise control group (JECG) and response cells billets involved in the control or support of an exercise. The ESMD is filled by personnel internal to USJFCOM and augmented by the Services and agencies as required to support the exercise. 3. Exercise Reporting Instructions:

(a) Reporting instructions will be issued for each location where exercise personnel are assigned. The JTF J-1 will coordinate these reporting instructions for USJFCOM-sponsored exercises (Exercise UNIFIED ENDEAVOR-type exercises), and by the exercise executive agent for other exercises.

(b) The JWFC Headquarters Commandant (HQCOMDT) will provide input on reporting instructions to the JTF J-1 for those individuals reporting to the JWFC. The following topics should be addressed in the reporting instruction message. This list is not all encompassing. Data pertinent to each specific exercise should be added as appropriate.

(1) Billeting. Ensure each line number has a billet and is identified in the message (e.g., JTF4-001 through JTF4-017 billeted at the Visiting Officers Quarters, Langley Air Force Base, Virginia). State which participants require contract quarters. Include a statement to those being billeted aboard a ship that storage space is limited. (2) Reporting Date, Time, and Location. Indicate the date and time each line number is to report, the location, and the projected completion date. Some people may report at a processing center prior to billeting, while others may report to billeting where a processing center has already been set up. Include any special reporting instructions (e.g., they may need to contact a particular individual upon arrival). Remember, early reporting may be requested, so special attention to their arrival may have to be considered. (3) Directions. Include directions from each of the local airports to billeting locations and from each billeting location to duty location.


(4) Transportation. Indicate that exercise participants are directed to use government transportation where available. Also, include if transportation will be provided to and from airports and billeting. (5) Uniforms and equipment. Indicate which duty uniform is to be worn (e.g., battle dress uniforms or Service equivalent) and if any special equipment is required. (6) Messing. Include the type of messing that will be provided. This affects how much, if any, per diem exercise participants receive. (7) Point of Contacts. Include a complete, or as complete as possible, list of points of contact (POCs) (e.g., JECG, HQCOMDT, Help Desk). (8) Security. Events at the Joint Warfighting Center (JWFC) are hosted in restricted areas. To enter the restricted areas unescorted, individuals are required to have, at minimum, a US Secret clearance. Most exercises are classified and the areas cannot be sanitized to accommodate uncleared visitors. Clearance information for all exercise participants and observers must be received by the security office no later than five days prior to the participant's arrival.

(9) Orders. For joint training exercises, list Norfolk, Virginia, as the duty location. Do NOT list Suffolk, Virginia. Orders must include, at a minimum, the following:

• Government billeting provided or not provided. • Government messing provided or not provided. • Government transportation provided or not provided. • State the name of the exercise the individual is attending. • Security clearance of individual. • Line number individual is filling on the JMD (i.e., JTF1-001, ECG2-003). This

is extremely important to properly assign and billet individuals. • Include where the funding is coming from. • Reception center(s) information, location, and hours of operations.

4. Exercise Timelines

(a) The following timeline is in effect for JWFC Exercise Manning Support:

(1) JWFC Exercise Manning Support for all events must be requested by the IPC. Support is guaranteed only for USJFCOM sponsored exercises, but may be requested for all others. (2) The Exercise Manning team will attend the MPC/FPC upon request by the project lead(s). At least two (2) exercise manning personnel will be assigned to participate at the MPC/FPC. They will attend for information purposes and data entry for the ESMD/JMD. (3) ESMD entered into JEMIS- 10 days after MPC. (4) Tasking Message- 150 days prior to COMEX. Note: Sending Tasking Messages, Chief of Staff (COS) Tasker, and Reporting

Instructions received from exercise project officer by set suspense date. 5. All templates are located on the MOSS Portal at: https://us.jfcom.mil/sites/J7/cos/JT02C/Exercise_Manning/Shared%20Documents/Forms/DispForm.aspx?


ID=15. Project officers will fill in the highlighted areas and send to Exercise Manning for further coordination and approval. It will then be sent out using the Automated Message Handling System (AMHS) on the SIPRNet.

• COS Tasker- 60 days prior to COMEX • Alibis and Reclamas are due to Exercise Manning NLT 60 days prior to

Startex • Reporting Instructions- 40 days prior to COMEX • Personnel names/SSN are due to Exercise Manning NLT 30 days prior to

Startex • Assisting the JWFC Support Team with in-processing for all events which are

scheduled at JWFC and all JFCOM-sponsored exercises no matter the location. At least two exercise manning personnel will be assigned for all in-processing events regardless of location.

Joint Event Management Information System

(a) The Joint Event Management Information System (JEMIS) is an internet-based manpower management tool designed to support any event (conference, exercise, classroom training, real-world operations). This system will be utilized throughout the life cycle of any event scheduled to be conducted or supported by USJFCOM/JWFC. There are several aspects of the system which need to be addressed to ensure that efficient event support is achieved. Any and all problems relating to JEMIS or its use will be directed to the JEMIS officer for resolution. It is prohibited to liaison with any other member of the development or management team. (b) When events are conducted in the JWFC facility, there are a myriad of things that must be done prior to the start of the exercise and during its execution. These responsibilities belong to several divergent organizations within the JWFC infrastructure. These responsibilities must be delineated so that the event can be managed and its execution conducted in the most professional manner. To this end, the following are those individuals and components within JWFC and their responsibilities.

6. Exercise Manning will use Joint Event Management Information System (JEMIS) to manage the EMD (except support staff), to include augmentees and taskings. They will ensure all received clear data is entered into the JEMIS database. They will also provide a copy of updated manning documents to project officers using the JEMIS reports function.


Intentionally Blank

Enclosure (27): Desk Officer (JELC) Checklists


OPR[office of primary responsibility]

□ Review command's Joint Training Plan (prior to conference) Supported Command

□Update key parameters: exercise purpose; exercise and training objectives; target audience; designated Joint Mission-Essential Tasks, and planning guidance (approved prior to Concept Development Conference)

Supported Command

□Coordinate with Doctrine Group to obtain CJCS doctrine assessment objectives and identify potential doctrine issues and joint publications/CJCS Instructions/CJCS Manuals, which may relate to the exercise purpose, scenario, and objectives

JWFC

□ Post and coordinate Joint Training Plan and update results on appropriate web page Supported Command

□ Conduct pre-Concept Development Conference coordination with designated Joint Warfighting Center (JWFC) team

Supported Command

□Brief exercise purpose: commander's intent and planning guidance; exercise objectives; training audience; approved Joint Mission-Essential Tasks; updated training objectives; other pertinent information

Supported Command

□Draft exercise design: produce event flow, such as academic, planning, execution, logistics planning factors; milestones for all facets of the Joint Event Life Cycle that pertain to the exercise

Supported Command & JWFC

□ Select simulation model and draft architecture (if appropriate) Supported Command & JWFC□ Draft Road-to-Crisis outline (bullet outline - part of scenario) Supported Command & JWFC

□ Determine potential joint publication/CJCS Instructions/CJCS Manuals and doctrine assessment implication opportunities

JWFC

□Coordinate with other USJFCOM directorates (and other appropriate commands, organizations, and agencies) to determine potential interests, issues, or focus areas related to the exercise

JWFC

□ Determine After Action Review requirements Supported Command & JWFC□ Develop a proposed Joint Exercise Control Group JWFC□ Design communications architecture JWFC□ Design intelligence architecture Supported Command & JWFC□ Draft Joint Exercise Directive outline (or Exercise Plan) Supported Command□ Produce draft Memorandum of Agreement (include milestones) Supported Command & JWFC□ Draft Initial Planning Conference agenda (recommended workshops and outcomes) Supported Command & JWFC

□ Identify Concept Development Conference taskers, offices of primary responsibility, and post conference minutes on appropriate web page


□ Approve Concept Development Conference outcomes Supported Command□ Complete Joint Exercise Directive outline Supported Command

□ Complete and approve training objectives (if revisions required beyond the Concept Development Conference)

Supported Command

□ Complete draft exercise design and event flow Supported Command & JWFC□ Develop academic training concept (if required) JWFC□ Complete the draft Memorandum of Agreement (includes exercise milestones) Supported Command & JWFC□ Finalize and distribute Initial Planning Conference agenda Supported Command□ Produce Draft After Action Review Concept of Operations (internal JWFC document) JWFC

Event

(12-18 months prior to start of exercise [STARTEX])

(following the Concept Development Conference)

JOINT EVENT LIFE CYCLEEVENTS, MILESTONES, PRODUCTS, AND SERVICES

STAGE 1 - DESIGN

Conduct Concept Development Conference

Prior to Initial Planning Conference



□ Brief approved exercise design Supported Command□ Brief approved training objectives (if revisions beyond Concept Development Conference Supported Command□ Brief Road-to-Crisis (outlines sufficient to go into Master Scenario Event List Conference JWFC□ Brief academic training concept (if required) JWFC□ Conduct workshops per Initial Planning Conference agenda Supported Command & JWFC□ Finalize and gain approval of Memorandum of Agreement Supported Command□ Determine exercise analysis team composition to include observers, analysts, and JWFC□ Determine logistic requirements Supported Command & JWFC□ Define command, control, communications, computers, and intelligence requirements Supported Command & JWFC□ Validate exercise milestones (part of Memorandum of Agreement) Supported Command & JWFC□ Deliver draft Exercise Control Plan JWFC□ Determine database requirements for Event Test 1 Supported Command & JWFC□ Finalize exercise control structure Supported Command & JWFC□ Outline Master Scenario Event List conference requirements JWFC□ Verify After Action Review requirements and mutual support requirements (identify Supported Command & JWFC□ Identify Initial Planning Conference taskers, offices of primary responsibility, and post Supported Command & JWFC

□ Develop major situational forces events (related events in the scenario) JWFC□ Complete scenario products necessary for Master Scenario Event List development JWFC□ Identify Blue Forces campaign/operations order significant events/timelines identified Supported Command□ Identify trusted agents from training audience Supported Command□ Identify Master Scenario Event List manager (Joint Exercise Control Group position) Supported Command□ Coordinate with Doctrine Group to identify potential doctrine implications that may JWFC□ Coordinate with other USJFCOM directorates to determine MSEL development JWFC□ Identify potential master scenario events (for Master Scenario Event List) Supported Command□ Identify all conference attendees Supported Command□ Conduct Master Scenario Event List Development Conference. JWFC provides facilitator, Supported Command & JWFC

□ Build draft Situational Forces Campaign Plan (if required) JWFC□ Conduct Event Test 1 (approximately 8 months prior to STARTEX) JWFC□ Conduct Master Scenario Event List Development Conference (if not done with Mid- JWFC□ Finalize site survey (After Action Review, technical, and facility requirements) JWFC□ Write Joint Exercise Directive Supported Command□ Refine command, control, communications, computers, and intelligence requirements Supported Command & JWFC□ Refine Exercise Control Plan JWFC□ Refine Joint Exercise Control Group training plan JWFC□ Design Mini-Exercise JWFC□ Design Communications Exercise JWFC□ Refine After Action Review Concept of Operations JWFC□ Develop academic training modules (if required) JWFC□ Refine Scenario JWFC□ Publish operation order (if applicable) Supported Command□ Identify movement requirements Supported Command & JWFC

JOINT EVENT LIFE CYCLEEVENTS, MILESTONES, PRODUCTS, AND SERVICES (CONTINUED)

Prior to MSEL Development Conference(after Initial Planning Conference)2

Prior to Mid-Planning Conference

STAGE 2 - PLANNINGConduct Initial Planning Conference

(10-12 Months prior to STARTEX)2



□ Brief draft Joint Exercise Directive (as appropriate) Supported Command□ Deliver and brief Exercise Control Plan JWFC□ Brief draft Situational Forces Campaign Plan (selected audience) JWFC□ Brief draft Scenario (Road-to-Crisis and Area Study) JWFC

□ Brief or provide input related to ongoing joint publication assessments and focus areas JWFC

□ Update milestones Supported Command□ Brief Event Test 2 requirements JWFC□ Brief academic training concept (if required) JWFC□ Brief Master Scenario Event List (selected audience) Supported Command□ Identify After Action Review observer source (if required) Supported Command

□Coordinate with Doctrine Group to ensure all available doctrine source and CJCS Instruction/CJCS Manual material is available to the training audience and other participants

JWFC

□ Identify the After Action Review doctrine analyst(s) JWFC□ Provide appropriate supported command standing operating procedures and plans Supported Command

□ Identify Mid-Planning Conference taskers, offices of primary responsibility, and post conference minutes on appropriate web site


□ Publish Exercise Control Plan Supported Command□ Conduct Event Test 2 JWFC□ Publish updated draft Master Scenario Event List Supported Command

□ Provide Joint Warfighting Center time-phased force and deployment data input to supported command

JWFC

□ Finish Situational Forces Campaign Plan JWFC□ Publish Joint Exercise Directive Supported Command□ Finalize Scenario JWFC□ Publish Final Planning Conference agenda Supported Command□ Finalize After Action Review Concept of Operations (internal JWFC document) JWFC

□ Distribute all necessary documents Supported Command & JWFC□ Deliver and or brief applicable plans Supported Command & JWFC□ Re brief applicable portions of Exercise Control Plan JWFC□ Brief Observer Training Plan (if required augmentation) JWFC□ Brief Joint Exercise Control Group Training Plan (part of Exercise Control Plan) JWFC□ Brief Mini-Exercise Plan (part of Exercise Control Plan) JWFC□ Deliver and brief Situational Forces Campaign Plan (limited audience) JWFC□ Deliver Scenario JWFC

□ Brief joint doctrine issues and implications, as required (to include issues in publications under development or revision)

JWFC

□ Other plans as applicable Supported Command□ Conduct Master Scenario Event List synchronization workshop Supported Command□ Brief Event Test 3 requirements JWFC

□ Identify Final Planning Conference taskers, offices of primary responsibility, and post conference minutes on appropriate web page



Final Exercise Review

Conduct Mid-Planning Conference(7-8 months prior to STARTEX)

Prior to Final Planning Conference

Conduct Final Planning Conference

STAGE 3 - PREPARATION

(3 months prior to STARTEX)



□ Conduct academic training (if required) JWFC□ Conduct Event Test 3 JWFC□ Provide doctrine related training to After Action Review team (as required) JWFC

□ Build After Action Review Collection Management Plan and coordinate with Doctrine Group to ensure joint doctrinal consistency and accuracy

JWFC

□ Deploy Supported Command & JWFC

□ Conduct Joint Exercise Control Group training JWFC

□ Conduct After Action Review and doctrine updates/briefings to observer/trainers and other exercise participants, (if required)

JWFC

□ Conduct Communications Exercise Supported Command & JWFC□ Conduct Mini-Exercise JWFC□ Conduct the exercise Supported Command & JWFC

□ Conduct research and provide joint doctrine issue papers to the training audience, analysis team and senior mentor, as required

JWFC

□ Review Facilitated After Action Review brief for doctrine consistency JWFC□ Conduct the Facilitated After Action Review JWFC

□ Ensure inputs to the Commander's Summary Report are supported by and are consistent with joint doctrine

JWFC

□ Produce and deliver the Commander's Summary Report JWFC□ Conduct issue definition Supported Command & JWFC

□ Identify potential joint doctrine voids and issues based on analysis and take appropriate action

JWFC

□ Produce the Joint After Action Report Supported Command□ Conduct the Mission Capability Reassessment Supported Command□ Update the Joint Mission-Essential Task List Supported Command□ Update the command's Joint Training Plan Supported Command□ Conduct Joint Requirements Reporting Supported Command□ Conduct Event Process Improvement Supported Command

STAGE 5 - ANALYSIS, EVALUATION, AND REPORTS


After Final Planning Conference

STAGE 4 - EXECUTIONPrior to STARTEX (on location)



Lead

□ USJFCOM

□□ Form the JTF□ Construct a requirements-based JMD

□ USJFCOM

□ USJFCOM & JTF

□ USJFCOM

□ USJFCOM & all concerned□ USJFCOM & all concerned□ USJFCOM & JTF

□ What USJFCOM will fund□ How to access funding provided by USJFCOM□ Military Interdepartmental Purchase Requests

□ USJFCOM, JTF, & all concerned.□ USJFCOM & all concerned□ USJFCOM & JTF

□ USJFCOM & JTF

□□ Purpose of each exercise phase and who should attend□ Reporting dates and early reporting dates□ Exercise locations by exercise phase

□ USJFCOM, JTF, & all concerned□

□ Funding ceilings□ Liaison officers to the JTF□ Component-to-component liaison officers (JTF J-1/J-3 responsibility)

□□ Obtain plain language addresses with office codes□ Identify JMD section leads with telephone numbers and e-mail addresses□ Identify unit identification codes

□ USJFCOM J-1 & JTF□

□ USJFCOM□ JTF staff□ Service components□ Functional components□ JMD section leads

□ USJFCOM□ USJFCOM

Define responsibilities for the exercise JMD

Identify the exercise tasking window (phases and dates)Provide input to the IPC minutes message

Review JTF J-1 training expectations and objectives (category 3 only)

Review participants by exercise phase

Determine billet prioritiesDevelop liaison officer support

Develop point of contact list with telephone numbers and e-mail addresses

Discuss distribution of information: mail, message traffic, telephone numbers, e-mailReview any Memorandums of AgreementsDiscuss major participating units and their role in the exerciseReview augmentation manning ceilings and limitations placed on the exercise by USJFCOM

Review USJFCOM Joint Exercise Directive (Personnel Annex)Establish exercise timeline for personnel augmentationDiscuss exercise funding:

Review Exercise Tasking DirectiveUS Joint Forces Command (USJFCOM) subject matter experts meet with JTF counterparts to develop the JMD DocumentChair the Initial Planning Conference (IPC) Personnel Planning Group

ActionProvide joint task force (JTF) J-1 copy of "strawman" Joint Manning Document (JMD) table of organizationInstruct the JTF staff on:

IPC Personnel Planning Group Discussion Items

CHECKLIST FOR THE JOINT MANNING DOCUMENTINITIAL PLANNING CONFERENCE

USJFCOM

USJFCOM & JTF

USJFCOM

USJFCOM & JTF

USJFCOM & JTF



Lead□ USJFCOM, JTF, & all concerned

□ JTF J-1

□ JTF functional components

□ USJFCOM, JTF, & all concerned

□ USJFCOM□ USJFCOM

□ JTF J-1

□ USJFCOM, Service components, JTF, JTF functional components, & all concerned

□ Review billets against training objectives□ Finalize critical billet list□ Identify emerging requirements□ Functional Section Leaders present section requirements□ Component representatives review for accurate Service skills, Service

skill codes, and ability to support□ JTF section representatives and USJFCOM subject matter experts

approve sections□ Review priority billets

□ USJFCOM, JTF, & all concerned□ USJFCOM & all concerned

□ What will USJFCOM fund□ How to access funding provided by USJFCOM□ Military Interdepartmental Purchase Requests

□ USJFCOM & all concerned□ USJFCOM & all concerned

□ USJFCOM & all concerned

□ USJFCOM & JTF□ Determine the purpose of each phase and who should attend□ Identify normal and early reporting dates□ Identify exercise locations by phase

□ USJFCOM & JTF□ Determine funding caps□ Identify liaisons to the JTF□ Identify component-to-component liaisons (JTF J-1/J-3 responsible)


□ USJFCOM & JTF□ Combatant commander

□ USJFCOM

□ USJFCOM

□ USJFCOMProvide input from the Personnel Planning Group to the MPC minutes message

Action

Assign responsibility for reporting instructionsValidate exercise JMDFreeze JMD upon conclusion of the MPC. Changes now require USJFCOM approvalRelease change message to initial tasking message, as required

Review augmentation manning caps and limitations placed on the exercise by USJFCOMReview participants by exercise phase

Determine liaison requirements

Update the points of contact list with telephone numbers, e-mail addresses, plain language addresses, and unit identification codes

Review USJFCOM Joint Exercise Directive (Personnel Annex)Review exercise funding status

Review Memorandums of AgreementUpdate exercise timeline for personnel augmentation

Send draft JMD to Service component counterparts prior to MPCChair the MPC Personnel Planning Group

Develop JMD functional section review schedule for MPC Personnel Planning GroupPerform a comprehensive line-by-line scrub of the draft JMD

CHECKLIST FOR THE JOINT MANNING DOCUMENTMID-PLANNING CONFERENCE

MPC Personnel Planning Group Discussion Items

Review exercise tasking proceduresCollect Joint Manning Document (JMD) proposals from joint task force (JTF) staff and component commandersSubmit draft JMD to US Joint Forces Command (USJFCOM) not later than 2 weeks prior to mid-planning conference (MPC)USJFCOM assumes direct supervision of the JMD prior to MPC and for the remainder of the exercise



Lead□ USJFCOM

□ JTF J-1□ USJFCOM & all concerned


□ USJFCOM, Service components, JTF, JTF functional components, & all concerned

□ Review cap numbers with participants□ Review billet fill priorities□ Review participants by phase and report dates□ Identify any additional changes, additions, or deletions□ Review liaison officer support□ Joint task force (JTF) staff□ Functional components□ Critical billets

□ USJFCOM & JTF□ Refine reporting dates and locations□ Refine early reporting dates and locations

□ USJFCOM & JTF□ all concerned□ all concerned□ USJFCOM□ USJFCOM

Draft post-FPC messageProvide input to the FPC minutes message

Review reporting instructions

Update points of contact list with telephone numbers, plain language Validate and submit remote site reporting instructionsRelease Exercise Report Instructions Message

Develop Joint Manning Document (JMD) functional section review schedule Review and update exercise timeline for personnel augmentationReview US Joint Forces Command (USJFCOM) Joint Exercise Directive (Personnel Annex)Review the JMD by functional section:

CHECKLIST FOR THE JOINT MANNING DOCUMENTFINAL PLANNING CONFERENCE

Action

FPC Personnel Planning Group Discussion Items Chair the Final Planning Conference (FPC) Personnel Planning Group



Intentionally Blank

GL-1

GLOSSARY

PART I − ABBREVIATIONS AND ACRONYMS

AAR ADSI ADL ADOCS ADP ADSW AFB AFFOR AFSERS AGR AIG AIS AMETL AMP ANN AOR ARFOR ASAP ATM ATO AWSIM BBCC BCTP BCS3 BEQ BOQ C2PC CAM CAP CAT CAX CBS CCB CCIR CCR CDC CDE CDR CDS

After Action Review Air Defense Systems Integrator Advanced Distributed Learning Automated Deep Operations Coordination System Automated Data Processing Active Duty for Special Work Air Force Base Air Force forces Air Force Synthetic Environment for Reconnaissance and Surveillance Active Guard and Reserve Addressee indicator group Automated information system Agency Mission-Essential Task List Analysis of Mobility Platform Arab News Network Area of Responsibility Army forces As soon as possible Automated Teller Machine Air Tasking Order Air Warfare Simulation Boards, Bureaus, Centers, and Cells Battle Command Training Program Battle Command Sustainment Support System Bachelor Enlisted Quarters Bachelor Officer Quarters Command and Control Personal Computer Collect Asset Matrix Crisis Action Planning Crisis Action Team Computer-Assisted Exercise Core Battlefield System Configuration Control Board Commander's Critical Information Requirements Command Conference Room Concept Development Conference Collateral Damage Estimate Commander Compact Digital Switch

GL-2

CENTRIX CESR CEXC CIB CIE-D CJCS C/JECG CJTF CM CMP CMO CNA CNO COA COLISEUM COMINT COMMEX COMNAVEUR COMSEC CONOPS CONUS CONPLAN COP COS COWAN CPX CSR CTP DAA DCJTF DCSG-A DEG DIA DIRLAUTH DISA DISN DISUM DLA DMS DOD DREN DSN DSOMS DTB DTRA

Combined Enterprise Regional Information Exchange Consolidated Exercise Support Request Combined Explosive Device System-Defeat Concept Integration Branch Counter-Improvised Explosive Device System-Defeat Chairman of the Joint Chiefs of Staff Combined/Joint Exercise Control Group Commander, Joint Task Force Collection Management/Manager Collection Management Plan Civil Military Operations Computer Network Attack Computer Network Operations Course of Action Community On-Line Intelligence System Communications Intelligence Communications Exercise Commander, US Naval Forces, Europe Communications Security Concept of Operations Continental United States Contingency Plan common operational picture Chief of Staff Coalition Wide Area Network Command Post Exercise Commander’s Summary Report Common Tactical Picture Designated Approving Authority Deputy Commander, Joint Task Force Defense Communications Support Group - Army Doctrine and Education Group Defense Intelligence Agency Direct Liaison Authorized Defense Information Systems Agency Defense Information Systems Network Daily Intelligence Summary Defense Logistics Agency Defense Message System Department of Defense Defense research Engineering Network Defense Switched Network Defense Source Operations Management System Deployable Training Branch Defense Threat Reduction Agency

GL-3

DTS DTT DV DVBC DVSG ELINT ENDEX ESD ESMD ETC EW EX MAN DOC FAAR FAQ FAST FDO FOUO FPC FUNCOM FVS GCCC GCCS GENSER GSA HICON HLA HQ HQCOMDT HSS HUMINT HVI HVT I3 IA IA IATO IAVA I/C ICC ICC

Defense Travel Service Deployable Training Team Distinguished Visitor Distinguished Visitor’s Briefing Center Digital Video Service Group Electronic Intelligence Exercise termination Exercise synchronization drill Exercise Support Manning Document Exercise Technical Control Electronic Warfare Exercise Manning Document Facilitated After-Action Review Frequently Asked Questions Forward Area Support Team Foreign Disclosure Officer For Official Use Only Final Planning Conference Functional Command Foreign Visit System Global C4 Control Center Global Command and Control System (variants A, J, & M) General Service (message) General Services Administration Higher Headquarters Control High Level Architecture Headquarters Headquarters Commandant Health Service Support Human Intelligence High-Value Individual High-Value Target GCCS [Global Command and Control System] integrated imagery and intelligence Interagency Information Assurance Interim authority to operate Information assurance vulnerability alert Instructor/controllers Intelligence Coordination Conference – Intelligence Control Cell Integrated Command and Control System

GL-4

ICP IIPR IMINT IMOA INTSUM IO IOR IP IPB IPC IPIR IPL IPTL ISAF ISC ISDN ISP ISR ISSM IWG JAARS JADOC JAWS JCAS JCATS JCLL JCMA JCMT JCOA JCS JDEN JDISS JDL JECC JECEWSI JECG JED JELC JEMIS JEPG JEST JESNET JExLC JETC

Inter-theater Communications Security (COMSEC) package Intelligence In-Progress Review Imagery Intelligence Intelligence Memorandum of Agreement Intelligence Summary Information Operations Information Operations Range Internet Protocol Intelligence preparation of the battlespace Initial Planning Conference Initial Phase Interpretation Report – Initial Photo Interpretation Report Imagery Production Library Integrated Process Team Leader International Security Assistance Forces Intelligence Support Cell Integrated Services Digital Network Internet Service Provider Intelligence, Surveillance, and Reconnaissance Information Systems Security Manager Intelligence Working Group Joint After-Action Reporting System Joint Air Defense Operations Center Joint Attack Weapon System – Joint Analytic Warfare System Joint Command and Control Attack Simulation Joint Conflict and Tactical Simulations Joint Center for Lessons Learned Joint COMSEC Monitoring Activity Joint COMSEC Monitoring Analysis Teams Joint Center for Operational Analysis Joint Chiefs of Staff Joint Deployable Exercise Network Joint Deployable Intelligence Support System Joint Digital Library Joint Enabling Capabilities Command Joint Electronic Combat Electronic Warfare Simulation Joint Exercise Control Group Joint Exercise Division Joint Event Life Cycle Joint Exercise Management Information System Joint Exercise Planning Group Joint Event Support Team Joint Exercise Support Network Joint Experiment Life Cycle Joint Experimentation, Test and Evaluation, and Advanced Concept Technology Demonstration/Joint Capabilities Technical Demonstration

GL-5

JETO JFIS JFT JIB JIC JIDPS JIF JIOC JIOWC JISE JLL JMD JMET JMETL JMSEL JNETS JNTC JOA JOC JOISIM JOPES JOTS JPASE JPRA JQUAD JRU JSAF JSD JST JTC JTC-I JTD JTEN JTF JTIMS JTLS JTL JTLS JTP JTS JTSA JTSST JTT JTTP JVB

Joint Effects Tasking Order Joint Forces Intelligence School Joint Force Trainer Joint Information Bureau Joint Intelligence Center Joint Integrated Database Preparation System Joint Interrogation Facility Joint Information Operations Center Joint Information Operations Warfare Command Joint Intelligence Support Element Joint Lesson Learned Joint Manning Document Joint Mission-Essential Task Joint Mission-Essential Task List Joint Master Scenario Events List Joint Networks Simulation Joint National Training Capability Joint Operations Area Joint Operations Center Joint Operations Information Simulation Joint Operation Planning and Execution System Joint Operational Tactical System Joint Public Affairs Support Element Joint Personnel Recovery Agency JC2WC [joint command and control warfare center] Joint Simulation Model Joint Reserve Unit Joint Semi-Automated Forces Joint Support Division Joint Warfighting Center Support Team Joint Training Confederation Joint Transformation Command-Intelligence Joint Training Division Joint Training and Experimentation Network Joint Task Force Joint Training Information Management System Joint Theater-Level Simulation Joint Target List Joint Theater Level Simulation Joint Training Plan Joint Training System Joint Training System Analyst Joint Training System Support Team Joint Training Team Joint Tactics, Techniques, and Procedures Joint Visitors Bureau

GL-6

JWFC JWICS LAD LAN LNO LOAC LOCE M&S MAGTF MARFOR MASINT MASLO MCCIS MDC MDST METOC MIC MIDB MILDEC MILS Mini-Ex MIPR MOA MOU MPC MRX MSEL MSEL Synch MSTP MTA MTG MUSE MWR NAS NASIC NATO NAVEUR NAVFOR NEO NGIC NGOs NIPRNET NLT

Joint Warfighting Center Joint Worldwide Intelligence Communications System Logistics Anchor Desk Local Area Network Liaison Officer Law of Armed Conflict Linked Operational Intelligence Centers Europe Modeling and Simulation Marine Air Ground Task Force Marine Corps Forces Measurement and Signatures Intelligence MASINT Liaison Officer Maritime Command and Control Information System MSEL Development Conference Missile Defense Space Tool Meteorological and Oceanographic Management Information Center Modernization Integrated Database Military Deception Multiple independent levels of security Mini-exercise Military Interdepartmental Purchase Request Memorandum of Agreement Memorandum of Understanding Mid-Planning Conference Mission Rehearsal Exercise Master Scenario Events List MSEL synchronization Marine Staff Training Program Mission Training Assessment Master Training Guide Multiple Unified Simulation Environment Morale, Welfare, and Recreation Naval Air Station National Aerospace Intelligence Center North Atlantic Treaty Organization US Naval Forces, Europe Navy forces Noncombatant Evacuation Operations National Ground Intelligence Center Nongovernmental Organizations Non-Secure Internet Protocol Router Network Not later than

GL-7

NRP NSA NSTL NWARS OA OB OPCON OPFOR OPG OPLAN OPORD OPR OPREP OPSEC OPTEMPO ORCON OSC OSINT OSISED O/T PA PAO PERSTEMPO PfP PID PLA POC POD PRI PRISM PSYOP PUM RC RFI ROE RSCN RSTA RTC RTL SA SC

National Reconnaissance Office National Security Agency No-Strike Target List National War-gaming System Objective Area Order of Battle Operational Control Opposing Force, Opposition Force Operational Planning Group Operation Plan Operation Order Office of Primary Responsibility Operation Report Operations Security Operating Tempo Originator Control Open Source Center Open Source Intelligence Ocean Surveillance Information System Evolutionary Development Observer/Trainer Public Affairs Public Affairs Officer Personnel tempo Partnership for Peace Plan Identification Number Plain Language Address Point of Contact Port of Debarkation Primary Rate Interface Planning Tool for Resource Integration, Synchronization, and Management Psychological Operations Proper use Memorandum Reserve Component Request for Information Rules of Engagement Regional Security Cooperation Network Reconnaissance, Surveillance, and Target Acquisition Road to Crisis Restricted Target List Situational Awareness Strategic Communication

GL-8

SCI SCL SCIF SF SIGINT SIGS SIMFAC SIMLAN SIO SIPRNET SITFOR SITREP SME SOF SONET SOP SPECAT SSO STARTEX STE STEP STU-III SUST TA TATACEX TACON TACSIM TAD TALON TBMCS TDG TDY TECHINT TENCAP/MUSE TF TFE T/O TO TOW TPA TPE TPFDD TPO TSR

Sensitive Compartmented Information Standard Conventional Load Sensitive Compartmented Information Facility Standard Form Signals Intelligence Synthetic Imagery Generation System Simulation Facility Simulation Local Area Network Senior Intelligence Officer SECRET Internet Protocol Router Network Situational Forces Situation Report Subject matter expert Special Operations Forces Synchronous Optical Network Standard Operating Procedure Special Category Special Security Officer Start of exercise Simulation Test Event Standard Tactical Entry Point Secure telephone unit III Sustainment Training Audience Tactical Exercise Tactical Control Tactical Simulation System Temporary Additional Duty TACSIM Analysis and Operations Node Theater Battle Management Core System Training Development Group Temporary Duty Technical Intelligence Tactical Exploitation of National Capabilities/Multiple Unified Simulation Environment Task Force Terrorist Financial Exploitation Table of Organization Training Objective Training Objective Workshop Training proficiency assessment Task Performance Evaluation Time-Phased Force and Deployment Data Task Performance Observation Telecommunications Service Request

GL-9

TTP TTSB TWIG TV UAG UAV UJTL US USACAPOC USAFRICOM USCENTCOM USEUCOM USJFCOM USMTF USNORTHCOM USPACOM USSOCOM USSOUTHCOM USSTRATCOM USTRANSCOM VCO VIP VIsIOn VOI VOIP VPN VRSG VTC VTCT VTOC WAWS WNN WSRD

Tactics, Techniques, and Procedures Training Team Support Branch Technical Working Integration Group Television Users Advisory Guide Unmanned Aerial Vehicle Universal Joint Task List United States United States Army Civil Affairs and Psychological Operations Command United States Africa Command United States Central Command United States European Command United States Joint Forces Command United States message text format United States Northern Command United States Pacific Command United States Special Operations Command United States Southern Command United States Strategic Command United States Transportation Command Visitor Coordination Officer very important person Virtual Integrated Support for the Information eNvironment Vessel of Interest Voice Over Internet Protocol Virtual Private Network Virtual Reality Scene Generator Video Teleconference Video Teleconference Theater Video Teleconference Operations Center Washington Area Wideband System World News Network Web Services Request Document

GL-10

PART II − TERMS AND DEFINITIONS

After-Action Review (AAR). 1. A process designed by a commander or director to provide commanders direct feed-back on the accomplishment of selected joint mission essential tasks, conditions, and standards stated in terms of training objectives for the commander to evaluate training proficiency. 2. An analytical review of training events that enables the training audience, through a facilitated professional discussion, to examine actions and results during a training event. (CJCSI 3500.01E) Collection Management Plan (CMP). A CMP focuses the collection process to ensure that all exercise joint mission-essential tasks, training objectives, and specified training audience processes are analyzed and reported. The plan will be of sufficient detail to accurately describe the who, what, when, where, how, and how much of data to collect. (This term and its definition are applicable only in the context of this publication and cannot be referenced outside of this publication.) Combatant Command Joint Training Schedule. A resource constrained program developed and updated annually by the combatant command staff that integrates the combatant commands' joint training plans and the schedule of the combatant commander-sponsored exercises. The schedule normally includes exercise summaries for the program year as well as proposed summaries for the following four years. (CJCSM 3500.03B) Joint Training Plan. A plan developed and updated annually by each combatant commander that defines the strategy for training assigned forces (training audience) in joint doctrine to accomplish the mission requirements over the selected training period. Specifically, the plan conveys the commander’s guidance, identifies the training audience, the joint training objectives, the training events, and required training resources. (CJCSM 3500.03B) Command Post Exercise (CPX). A CPX is an exercise in which the forces are simulated, involving the commander, the staff, and communications within and between headquarters. (JP 1-02) Commander's Summary Report (CSR). A CSR provides a written record of the significant strengths and weaknesses of a commander's staff's performance relative to the selected joint mission-essential tasks and training objectives. (This term and its definition are applicable only in the context of this publication and cannot be referenced outside of this publication.) Exercise. A military maneuver or simulated wartime operation involving planning, preparation, and execution. It is carried out for the purpose of training and evaluation. It may be a multinational, joint, or single-Service exercise, depending on participating organizations. (JP 1-02) Exercise directing staff. A group of officers who by virtue of experience, qualifications, and a thorough knowledge of the exercise instructions, are selected to direct or control an exercise. (JP 1-02) Exercise incident. An occurrence injected by directing staffs into the exercise, which will have an effect on the forces being exercised, or their facilities, and which will require action by the appropriate commander and/or staff being exercised. (JP 1-02) Exercise specifications. The fundamental requirements for an exercise, providing in advance an outline of the concept, form, scope, setting, aim, objectives, force requirements, political implications, analysis arrangements, and costs. (JP 1-02) Exercise sponsor. The commander who conceives a particular exercise and orders that it be planned and executed either by the commander's staff or by a subordinate headquarters. (JP 1-02) Global Command and Control System (GCCS). Highly mobile, deployable command and control system supporting forces for joint and multinational operations across the range of military operations,

GL-11

any time and anywhere in the world with compatible, interoperable, and integrated command, control, communications, computers, and intelligence systems. (JP 1-02) Interoperability. 1. The ability of systems, units, or forces to provide services to and accept services from other systems, units, or forces and to use the services so exchanged to enable them to operate effectively together. 2. The condition achieved among communications-electronics systems or items of communications-electronics equipment when information or services can be exchanged directly and satisfactorily between them and/or their users (DOD only). The degree of interoperability should be defined when referring to specific cases. (JP 1-02) Joint After-Action Report (JAAR). A written report consisting of joint universal lessons learned that provides the official description of an operational training event and identifies significant lessons learned. (This term and its definition are applicable only in the context of this publication and cannot be referenced outside of this publication.) Joint doctrine. Fundamental principles that guide the employment of forces of two or more Military Departments in coordinated action toward a common objective. It is authoritative; as such, joint doctrine will be followed except when, in the judgment of the commander, exceptional circumstances dictate otherwise. It will be promulgated by or for the Chairman of the Joint Chiefs of Staff, in coordination with the combatant commands and Services. (JP 1-02) Joint Event Life Cycle (JELC). Describes the design, planning, preparation, execution, analysis, and evaluation and reporting stages required to successfully execute a discrete training event. (CJCSM 3500.03E) Joint exercise. A joint military maneuver, simulated wartime operation, or other Chairman of the Joint Chiefs of Staff or combatant commander-designated event involving planning, preparation, execution, and evaluation. A joint exercise involves forces of two or more Military Departments under the command and control of a combatant commander or subordinate joint force commander; involves joint forces and/or joint staffs; and is conducted using joint doctrine. (CJCSI 3500.03E) Joint Exercise Control Group (JECG). Typically, the combatant command staff will form a joint exercise control group to plan, direct, and control joint exercises. The organization and responsibilities of the joint exercise control group may vary from combatant command to combatant command; however, the joint exercise control group will generally be composed of five major parts: Observer/Trainer Group; Controller Group; Modeling and Simulations Group; Role Players; and the Opposition Force. (This term and its definition are applicable only in the context of this publication and cannot be referenced outside of this publication.) Joint Mission-Essential Task (JMET). A mission task selected by a joint force commander deemed essential to mission accomplishment and defined using the common language of the universal joint task list in terms of task, condition, and standard. (JP 1-02) Joint Mission-Essential Task List (JMETL). A list of joint mission-essential tasks selected by a commander to accomplish an assigned or anticipated mission that includes associated tasks, conditions, and standards and requires the identification of command-linked and supporting tasks. (CJCSI 3500.01E) Joint [Personnel] Reception Center. The center established in the operational area (per direction of the joint force commander), with responsibility for the reception, accountability, training, processing, of military and civilian individual augmentees upon their arrival in the operational area. Also the center where augmentees will normally be out-processed through upon departure from the operational area. (JP 1-02) Joint Task Force (JTF). A joint force that is constituted and so designated by the Secretary of Defense, a combatant commander, a sub-unified commander, or an existing joint task force commander. (JP 1-02)

GL-12

Joint training. Training, including mission rehearsals, of individuals, units, and staffs using joint doctrine or joint tactics, techniques, and procedures to prepare joint forces or joint staffs to respond to strategic, operational or tactical requirements considered necessary by combatant commanders to execute their assigned or anticipated missions. (CJCSI 3500.01E) JWFC Joint Training Tiers. Four delineated levels of training defining the training audience participating in joint training conducted at the Joint Warfare Training Center (JWFC). Tier definition are applied to levels of training formerly known as “categories” of training. The “tiers” range from US Service core competency training to interagency and intergovernmental joint training. (This term and its definition are applicable only in the context of this publication and should not be referenced outside of this publication.) Master Training Guide (MTG). A collection of tasks and associated conditions and standards usually for a specific joint organization. Tasks are derived from joint doctrine and are grouped on a mission and/or functional basis to support organizational training. (CJCSI 3500.01E) Mission Training Assessment (MTA). A commander's subjective assessment of the command's training proficiency assessments with respect to assigned missions. (CJCSI 3500.01E) Multinational exercise. An exercise containing one or more non-US participating force(s). (JP 1-02) Multinational Force (MNF). A force composed of military elements of nations who have formed an alliance or coalition for some specific purpose. (JP 1-02) Reserve Components. Reserve Components of the Armed Forces of the United States are: a. the Army National Guard of the United States; b. the Army Reserve; c. the Naval Reserve; d. the Marine Corps Reserve; e. the Air National Guard of the United States; f. the Air Force Reserve; and g. the Coast Guard Reserve. (JP 1-02) Situational forces. Forces, not necessarily adversarial or friendly, that are present within an operational area and contribute to the uncertainty of conditions within the operational environment. These forces, such as police forces, relief forces, host government or para-military forces, or potential terrorist cells, impact the operational environment in situations associated with military operations other than war. (This term and its definition are applicable only in the context of this publication and cannot be referenced outside of this publication.) Task Performance Observations (TPO). For joint training, a listing of a training audience, training objectives, observer reports, and an executive summary for the commander to review and make a training proficiency evaluation. (CJCSI 3500.01E) Training Audience (TA). An organization (staff element, command, or other unit) that performs a particular joint mission-essential task list task. (This term and its definition are applicable only in the context of this publication and cannot be referenced outside of this publication.) Training Objective (TO). A description of the training audience, desired outcome of a training activity, and the measures for evaluating the learning outcome. (This term and its definition are applicable only in the context of this publication and cannot be referenced outside of this publication.) Training Proficiency Assessment (TPA). Derived from the primary trainer's subjective assessment of an organization by comparing collective training proficiency evaluations and other training inputs over time and against joint mission-essential tasks, conditions, and standards. (CJCSI 3500.01E) Training Proficiency Evaluation (TPE). An objective evaluation of an organization's performance with respect to training objectives produced during the execution phase of the joint training system. (CJCSI 3500.01E)

GL-13

Universal Joint Task List (UJTL). A menu of capabilities (mission-derived tasks with associated conditions and standards, i.e., the tools) that may be selected by a joint force commander to accomplish the assigned mission. Once identified as essential to mission accomplishment, the tasks are reflected within the command joint mission essential task list. (JP 1-02) US forces. All Armed Forces (including the Coast Guard) of the United States, any person in the Armed Forces of the United States, and all equipment of any description that either belongs to the US Armed Forces or is being used (including Type I and II Military Sealift Command vessels), escorted, or conveyed by the US Armed Forces. (JP 1-02)

GL-14

Intentionally Blank

jwfc event handbook 2010[1]

Documents

joint warfighting center

joint training system

jwfc training operations

jwfc organization

service training programs

service training sites

various jwfc offices

introduction handbook