GCSS-J Banner

JOINT PLANNING AND EXECUTION SERVICES

PRINT PAGE Add This

The Joint Planning and Execution Services (JPES) (formerly Adaptive Planning & Execution [APEX]) is the DoD's system that supports the policies, processes, procedures, and reporting structures needed to plan, execute, mobilize, deploy, employ, sustain, redeploy, and demobilize activities associated with Joint Operations. This service assists in the evaluation of processes and thus transforms the execution of Joint Operations.

STANDARD FEATURES


  • JPES Framework (JFW): The JFW is composed of software “infrastructure” components that provide management, storage, and access to authoritative planning data. Data objects will be exposed through secure Simple Object Access Protocol (SOAP) based web services and synchronized with other planning databases as well as geographically distributed nodes. JFW will also include a separate business rules engine as well as a workflow manager in support of Adaptive Planning & Execution processes. A few of the core capabilities of JFW are:
    • JPES Permission Manager (JPM): Manages permissions for JOPES planning data and JPES data objects.
    • Data Virtualization Layer (DVL): Provides a high performance, in-memory federation of existing Authoritative Data Sources (ADS) exposed through secure SOAP based web services. JPES applications will be able to connect to the DVL to read from and write to disparate ADS.
    • JPES Policy Decision Point (PDP): Provides Attribute-Based Access Control (ABAC) through the use of a PDP which leverages Extensible Access Control Markup Language (XACML) Policy Store and Local attribute Store to make, permit, or deny access decisions on JPES resources.


 

  • Joint Force Protection (JFP): The JFP System quickly retrieves and processes essential force projection information used to support decisions made by members of the Joint Planning and Execution Community (JPEC). A specific emphasis is placed on those processes that support identifying, requesting, sourcing, validating, scheduling, movement tracking, and closing of force capabilities requested by the supported commander. JFP provides visibility into execution of a plan by aggregating data from the following authoritative planning and execution sources such as:
    • Joint Operation Planning and Execution System (JOPES)
    • Global Status of Resources and Training System (GSORTS)
    • Global Transportation Network (GTN)
    • Joint Capabilities Requirements Manager (JCRM)
    • Automated Message Handling System (AMHS)


 

  • Joint Capabilities Requirements Manager (JCRM): JCRM is a web-based software application that enables the Global Force Management (GFM) allocation process using a net-centric compliant architecture leveraging multiple authoritative data sources across the Department of Defense (DoD). JCRM was developed by the Global Force Management Continuous Process Improvement (GFM-CPI) effort under the direction of the Force Management Executive Committee (FMEC). It is the single software application for submitting and/or managing all force requirements (Emergent, Rotational, Exercise, Individual Augmentation and Contingency Planning) and is directed for use by all Combatant Commands (COCOM) and Services in the annual CJCS GFMAP PLANORD. GFM aligns force apportionment, assignment, and allocation in support of the National Defense Strategy (NDS), joint force availability requirements, and joint force assessments. It provides comprehensive insights into the global availability of U.S. military forces/capabilities and provides senior decision makers a process to quickly and accurately assess the impact and risk of proposed changes in forces/capability assignment, apportionment, and allocation. There are seven components within JCRM. Each component, except for the System Administrator Module, provides necessary information and feeds to the next component to complete deployment orders and sourced forces for planned military operations. JCRM modules are:
    • The Requirements Module - Captures “demand signal” on forces. The “demand signal” is the requirement to complete an individual, augmentee or team position to accomplish a planned military mission. These demands can be described as rotational or emergent, exercise, individual augmentee or contingency.
    • The Capabilities Module - Consists of Operational Capability Packages (OCP), worksheets, also known as Request For Forces (RFFs), mapping Joint Capability Area (JCA) Universal Joint Task List (UJTL) to Unit Type Codes (UTC), and general searches for items such as relevancy, UTCs, Geolocations (GEOLOC), JCAs or UJTLs. OCPs provide the ability to generate packages of capabilities that include pertinent Global Force Management (GFM) and Joint Operation Planning and Execution System (JOPES) information, UTC via lookup/reference to Service Authoritative Data Sources (ADS) and Type Unit Characteristics File (TUCHA), GEO via lookup to GEOCODES; transform to initial JOPES Force Requirements Nominations (FRNs); transform to Requirements and RFFs; organizationally package OCPs in a hierarchical methodology; compare OCPs between COCOMs and users; and Reuse/copy “off-the-shelf” OCPs.
    • The Force Provider Module - Utilizes nominations for the Force Provider or Joint Force Provider to create or modify force tracking number nominations, submit nominations to Joint Force Providers, accept or release Force Projection nominations, culminate in a Force Provider sourcing solution; building of Joint Force Projection Orders which allow for development of a Global Force Management Allocation Plan; and COCOM Deployment Orders (DEPORDS)
    • The Force Deployment Module - Allows the communication of JCRM with JOPES via the JOPES Data Network Service (JDNETS) interface. This interface provides reconciliation of requested, ordered and deployed data, and creation of filters to validate FTNs ordered under GFM process with FTN in a JOPES Time Phased Force Deployment Data (TPFDD).
    • The Contingency Plans Module - Supports the GFM process of capturing the “demand signal” for contingency planning requirements, and enhancing the contingency sourcing process through Force Provider visibility. It enables the user with proper roles and permissions to perform Contingency Sourcing, which supports the GFM and Adaptive Planning and Execution (APEX) planning continuum.
    • The Functional Manager Module - Allows for the management of user accounts, roles and permissions, manages reference lists as a Functional Authority via Joint Requirement Code (JRCs)/Nomenclatures, Global Employment of Forces (GEF) Priorities, and Special Operations Command (SOCOM) Priorities. The Functional Manager Module also allows, with limited external interface configuration, United States Central Command (USCENTCOM) Functional Administrator to import data from Force Requirements Enhanced Database (FRED) and the United States Joint Forces Command (USJFCOM) Joint Staff Administrators to import data from Joint Training Information Management System (JTIMS) and Electronic Joint Manpower and Personnel System (eJMAPS).
    • The System Administrator Module - Allows for a user with increased permissions to configure an external interface to modify Universal Resource Locator (URL) addresses, authenticate information, pull data from external sources; privileged functionality to cancel requirement change requests, and release object locks; manage reference lists; and view error logs.


 

VALUE TO OUR MISSION PARTNERS


JPES is a portfolio of capabilities that supports the contingency (deliberate), crisis action planning processes which rapidly transforms those joint operations plans into execution (movement) orders for the warfighters. Key elements of JPES include the JPES Framework (JFW) and Joint Force Projection (JFP).The JFW is a suite of software “infrastructure” components and services to support management, storage of, and access control to JPES data as web services enabled data objects as well as data distribution, synchronization, data business rule enforcement and workflow management in support of JPES capabilities.

The JFP Portal provides a single, integrated force projection picture that links operators and logisticians at Service, Joint, and Agency levels using real-time, web-based, and network-centric information systems. The JCRM is a web-based GFM tool that increases the efficiency of the GFM process by providing senior DoD decision makers with a consolidated database of joint forces, capabilities, and requirements. JCRM will transition to DISA from JS J31 in the July 2012 timeframe.

JPES capabilities consist of support operations, helpdesk, software license renewals, software error correction, information assurance vulnerability alert (IAVA) compliance in the Secret, development, training, and COOP nodes. Future efforts are aimed at completing the enhancement of adaptive planning and execution capabilities.