Joint Operation Planning and Execution System Cell
DRAFT 11 May, 1999
Go back to: Corps as a Warfighting Headquarters
The automated data processing portion of JOPES provides the capability to construct an automated deployment data base designed to interface with management systems of the NCA, Joint Staff, combatant commands, Services, Commander in Chief, United States Transportation Command (USCINCTRANS), and Defense agencies. The CEAC and component commanders use JOPES for CAP, involving COA development, detailed deployment planning, execution, and redeployment operations.
Beginning with CAP Phase I, JOPES is used to assist in COA development by coordinating and providing force and deployment data, deployment estimates, and transportation feasibility studies. During deployment execution, JOPES provides the NCA, the Joint Staff, combatant commanders, CEAC, and supporting commanders with the information required to monitor the progress of the deployment and to exercise positive control of C2 of the force deployment battle space.
Explicit provision should be made for the CEAC to make inputs via GCCS. Equipment and trained JOPES operators will be made available to the CEAC when the mission requires JOPES capability. If physical constraints or other factors preclude JOPES equipment and operators from being assigned to the EAC HQ, the establishing authority must make provisions for the CEAC to input to the JOPES data base. Deployment Considerations EAC HQ may be structured for incremental deployment.
Command and Control
Each deployment increment should include a capability for C2 of forces assigned to or supporting the CEAC and should come complete with logistics, communications, and security support. Liaison Increment. When directed by the CEAC, a liaison increment may deploy in advance of the EAC HQ. This increment is not designed for (nor is it capable of) C2 of combat operations. It acts as an advance party for the EAC and assists in receiving the forces. In addition, it acts as an interface between local US and foreign agencies, often serving as a forerunner to a military coordinating committee. Initial EAC HQ Increment-Advanced Echelon (ADVON). This increment should provide a minimum capability for C2 during the buildup of the EAC. It must be designed for the planned method of insertion (e.g., airborne, amphibious). The design of each increment should consider the mission and whether forcible entry into the JOA is required. It also should be noted that an afloat EAC organization normally will not deploy incrementally. The EAC will enter EAC HQ deployment requirements in the JOPES data base.
COA Development and TPFDD
During TPFDD development in support of COA development, the supported combatant commander and CEAC (if designated) are responsible for developing the concept of operations. The supported combatant command and the EAC, in conjunction with their Service components, update the JOPES TPFDD with force deployment requirements to support the employment concept. TPFDD can be initiated by loading from existing OPLAN in the JOPES data base, or by creating a new TPFDD when no OPLAN exists. JPEC uses the TPFDD to analyze various COAs. Analysis includes transportation feasibility, shortfall identification and resolution, constraints analysis, and deployment estimates. Results of TPFDD analysis are reflected in the commanders estimate. Execution Planning. The execution planning phase represents refinement of gross planning conducted during COA development. During this phase, the supported combatant commander is the focal point for the JPEC. The supported combatant commander directs refinement of the TPFDD in the JOPES data base. The combatant commanders, Service components, supporting commanders, Services, and providing organizations source requirements and validate the TPFDD to the supported combatant commander. The supported combatant commander validates TPFDD requirements to USCINCTRANS for movement scheduling. USTRANSCOM components, AMC, Military Traffic Management Command, and Military Sealift Command provide movement schedules for the requirements in the sequence requested by the CEAC and validated by the supported combatant commander. Initially, USTRANSCOM will focus scheduling efforts on the first 3 to 7 days of air movement (including surface movements to aerial ports of embarkation) and 30 days of sea movements. Throughout the execution planning phase, USTRANSCOM will provide required updates to movement schedules in the JOPES data base. Deployment Execution Deployment begins as specified in the CJCS execute or deployment order. USTRANSCOM updates schedules for validated movement requirements and provides actual departure and arrival reports in the JOPES data base. All changes to validated TPFDD requirements must be approved and revalidated by the supported combatant commander. Changes to validated TPFDD need to be identified to the supported combatant commander as soon as possible via GCCS teleconference supporting the operation.
Execution (CAP Phase VI) may be ordered without the benefit of the planning accomplished in CAP Phases I through V. In this case, execution and planning occur simultaneously. Upon receipt of the CJCS execute order, USTRANSCOMs actions are focused on deployment. If the CJCS execute order is received before completion of execution planning, USTRANSCOM will provide all available deployment information. Procedures for coordinating and monitoring deployment of non-unit-related personnel and resupply are also provided.
CEAC responsibilities during employment include the following. Force and Resource Monitoring and Management. Monitoring the current status of assigned forces and their resources and providing information to assist in the allocation and movement of forces and materiel.
Preparing plans relative to current and future operations.
Directing the implementation of OPORDs and monitoring the current air, land, sea, space and special operations situation; ensuring support for combat operations; and reviewing the enemy threat and issuing follow-on orders, as appropriate.
Submitting reports to the supported commander and heads of other agencies as prescribed in Joint Pub 1-03 (to be converted to CJCSM 3150.01), "Joint Reporting Structure (JRS) General Instructions," and other directives.
Redeployment may be directed when operations have terminated or movement of the EAC is directed by higher authority. Based on guidance from the CEAC, the JPG could be used to accomplish redeployment planning. Commanders should make the same considerations for redeployment as for deployment in regard to phasing of command, combat, combat support, and combat service support elements out of the JOA. JOPES will be used to provide redeployment status and to schedule common-user lift assets.