Inactive

Continuity of services is required for support of GFM, which provides critical software development and implementation of a modernized net centric JPES to replace the existing JOPES. The DISA JPES Pro... Continuity of services is required for support of GFM, which provides critical software development and implementation of a modernized net centric JPES to replace the existing JOPES. The DISA JPES Program Management Office (PMO) and Joint Planning and Execution Community are delivering the next generation of services that provide force planning, deployment planning and execution (force projection) capabilities to the warfighter. The JPES PMO currently manages the following legacy systems: JOPES and Joint Capabilities Requirements Manager (JCRM). These legacy systems architectures are aging and require increasingly expensive sustainment efforts, which has led to the requirement for modernization and the transition to a net-centric, service-oriented architecture. JOPES is the joint system used to monitor, plan, and execute mobilization, deployment, employment, and sustainment activities associated with joint operations and exercises, as well as identify force requirements in service of the GFM allocation process. These services require specialized subject matter experts and technical knowledge of the JOPES software systems and configurations, as well as specialized knowledge of the replacement JPES software systems and configurations. To avoid a gap in mission-essential services and to ensure the successful sunset of JOPES, the JPES software development and implementation must continue without interruption. The increased ceiling is required to provide the Minimum Viable Product (MVP), continue software development and implementation, reach the Operational and Sustainment phase of JPES, and allow JOPES to sunset.