Joint Operation Planning and Execution
IP - 3100
INSTRUCTOR: KENNETH HILL
DESCRIPTION: This lesson presents an overview of the Joint Operation Planning and Execution System (JOPES) to include procedures, personnel, and equipment.
OBJECTIVES: Comprehend the Joint Operations Planning and Execution System (JOPES).
SAMPLES OF BEHAVIOR: Each student will:
1. Relate JOPES to JSPS and National Security Objectives
2. Describe the purpose JOPES.
3. Know the types of planning guidance and content found in JOPES volumes 1,2.
4. Describe the relationship among GCCS, JOPES and the ADP planning systems.
1. Scan JOPES Volumes I and II provided in your seminar room.
2. Review the CWPC Desktop Reference for the definitions of the following:
a. JOPES. b. JPEC d. GCCS f. JDS g. TPFDD
Read Joint Staff Officer's Guide 1993, paragraph 509, "JOPES", pages 5-30 through
1. Relate JOPES to JSPS and National Security Objectives
c. Supports national security objectives, senior-level decision-makers and their staffs at the National Command Authority (NCA) level and throughout the JPEC. The JPEC includes the following:
(1) National Level: CJCS, JCS, Joint Staff & Services
(2) Theater-Level: Supported Commanders (including Service Component Commands
(3) Supporting Organizational Level: Supporting Commands and their components, Defense Agencies, Non-DOD departments and agencies & Allied Commands and agencies.
2. The Purpose of JOPES:
a. JOPES is the integrated joint conventional command and control system used to plan and execute joint military operations. (JOPES Vol. 1).
b. Also, JOPES standardizes the content of OPLANS & CONPLANS, policies and procedures, and deployment data requirements.
3. JOPES Volume I: Planning Policies and Procedures. (Joint Pub 5-03.1) (To be rewritten as CJCSM 3122.01) (CJCSM 3122.02, 9 Dec 94, the Manual for Time-Phased Force and Deployment Data (TPFDD) Development and Deployment Execution provide procedures/information for building TPFDDs.
a. Chapter 1 is an overview of the planning process.
b. Chapter 2 describes the joint planning process.
(1) Describes the relationship between the Four interrelated systems
(a) National Security Council System (NSC).
(b) Joint Strategic Planning System (JSPS), including its
(c) Planning Programming and Budgeting System (PPBS).
(d) Joint Operation Planning and Execution System (JOPES).
(2) Describes the JOPES functions.
(a) Threat Identification and Assessment.
(b) Strategy Determination.
(c) Course of Action Development.
(d) Detailed Planning.
(3) Relationship between JOPES functions and deliberate and crisis action
c. Chapter 3 describes, in detail, the deliberate planning process, responsibilities and time requirements.
(1) Operation Plans. OPLAN (Contains a complete TPFDD).
(2) Concept Plans. CONPLAN (With or without TPFDDs).
(3) Functional Plans.
(4) The phases in the deliberate planning process will be discussed in
detail in IP-4410 and IP-4415, The JOPES Deliberate Planning Process.
(a) Phase I - Initiation.
(b) Phase II - Concept Development (5) steps.
(c) Phase III - Plan Development (8) steps.
(d) Phase IV - Plan Review.
(e) Phase V - Supporting Plans.
d. Chapter 4, JCS Review of Operation Plans.
(1) Review of CINC's concept of operations (Phase II.)
(2) Review of US unilateral, bilateral, NATO, and US-Canada plans (Phase IV.)
(3) Review criteria:
(c) Joint Doctrine.
(4) Review Comments.
(5) Review Results.
e. Chapter 5, Crisis Action Planning (The phases of CAP will be covered in detail in IP-5000).
(1) Phase I Situation Development.
(2) Phase II Crisis Assessment.
(3) Phase III Course of Action Development.
(4) Phase IV Course of Action Selection.
(5) Phase V Execution Planning.
(6) Phase VI Execution.
f. Chapter 6, JOPES Administration.
(2) JOPES database manager responsibilities.
(1) Annex A - Crisis action planning checklists.
(2) Annex B - Crisis reporting procedures and sample message formats.
(3) Annex C - Warning Order.
(4) Annex D - Commander's Estimate.
(5) Annex E - Planning Order.
(6) Annex F - Alert Order.
(7) Annex G - Deployment orders.
(8) Annex H - Execute Order.
(9) Annex J - Operation Order.
(10) Annex K - Commander's Evaluation Request.
(11) Annex M - Components response to CC Evaluation Request.
(12) Annex N - TPFDD LOI.
(13) Annex P - Staff estimates (Responses to the planning directive.)
(14) Annex Q - References
4. JOPES Volume II, Planning and Execution Formats and Guidance. (Includes a classified supplement). (CJCSM 3122.03, Final Draft, 3 Jun 95 Classified supplement is CJCSM 3122.04 also in final Draft
a. ENCLOSURE A - ADMINISTRATIVE GUIDANCE
(1) Plan Identification (PID, ULNs, Fms, and CIN/PINs)
(2) Security Markings & Classified/Unclassified Elements
(3) Format and Content of OPLANS, CONPLANS (with & without TPFDDs) and OPORDS
(4) Distribution of OPLANs.
(5) Release of OPLAN information.
(6) Conflicting guidance.
b. ENCLOSure b - restricted Access policy.
c. enclosure c - format and content of oplans
d. Enclosure D - format and content of conplans and functional plans
5. GLOBAL COMMAND AND CONTROL SYSTEM (GCCS):
b. Among other capabilities, it integrates:
(1) GCCS replaces/enhances WWMCCS/JOPES functionality.
(2) Client-server environment, open architecture system, mostly in the UNIX environment.
(3) Wide area network (WAN) like capability.
(4) Windowing/pull down menu capability.
(5) Operates at the SECRET level.
6. GCCS Navigation uses NETSCAPE applications on a distributive architecture.
a. Allows users at different sites to access common data sources, as opposed to identical data.
b. Users can search for data using search engines and then users can format useful information/presentation.
c. GCCS offers a COMMON OPERATIONAL PICTURE for the warfighter and planner.
7. JOPES SOFTWARE APPLICATIONS THAT RESIDE ON GCCS. JOPES is not a single application, rather it is a set of applications that can be used independently but interact with a shared database. The JNAV window is where most JOPES applications (except JFAST, which must run on a DOS machine) can be accessed. These JOPES applications are grouped by function and are defined below.
a. Requirements Development and Analysis (RDA):
(1) Provides an easy TPFDD manipulator.
(2) Graphic representation of TPFDD -- routes, origins ports destinations.
(3) Used as a planning and execution tool.
b. LOGSAFE (Logistics Sustainment Analysis and Feasibility Estimator)
(1) Sustainment and resupply estimator system
(2) Establishes gross logistics requirements.
(3) Uses TPFDD data
(4) Based on UTC consumption file
(5) Cargo category codes
(6) Feeds results into TPFDD (CINS)
(7) Resupply tonnage by class and subclass of supply
(8) Reserves transportation ACE
c Integrated JOPES Programs. Some of the applications that use TPFDD information to generate additional plans data.
(1) Scheduling and Movement Module: (S&M)
(a) Capability to retain and compare allocations versus actual manifests.
(b) Carrier support across multiple OPLANS.
(c) Primary purpose is to provide schedules and manifests of
(d) Like other GCCS applications - enhanced Graphical User
(2) Ad Hoc Query. AHQ provides the capability to precisely select the information you wish to extract from the database. Then AHQ lets you send the output into a display, report, or file.
(3) JFAST (Joint Flow and Analysis System for Transportation). Answers the questions.
(a) Is OPLAN grossly feasible?
(b) Will force arrive on time?
(c) Can support be furnished?
(d) Are lift assets sufficient?