Tactical Command System

Abstract

The Tactical Command System upgrades the Navy's Command, Control, Communications, Computer and Intelligence (C4I) systems and processes C4I information for all warfare mission areas including planning, direction and reconstruction of missions for peacetime, wartime and times of crises. Tactical Support Center: The Tactical Mobile (TacMobile) program provides evolutionary systems and equipment upgrades to support the Maritime Patrol and Reconnaissance Force Commanders with the capability to plan, direct and control the tactical operations of Maritime Patrol and Reconnaissance Aircraft and other assigned units within their respective area of responsibility. Looking ahead, TacMobile provides critical reach-back capabilities between the Maritime Patrol and Reconnaissance Aircraft, primarily the P-8A/Poseidon, and MQ-4C/Triton, and the Maritime Intelligence Surveillance and Reconnaissance Enterprise. These operations include littoral, open ocean, and over land long-dwell surveillance, anti-surface warfare, over-the-horizon targeting, counter-drug operations, power projection, anti-submarine warfare, mining, search and rescue, indications and warnings, and special operations. The missions are supported by the Tactical Operations Centers and the Mobile Tactical Operations Centers. Mission Planning: The Joint Mission Planning System (JMPS) is the designated automated mission planning system for the Navy. JMPS enables weapon system employment by providing the information, automated tools, and decision aids needed to rapidly plan aircraft, weapon, or sensor missions, load mission data into aircraft and weapons, and conduct post-mission analysis. JMPS is a mission critical system which is a co-development effort between the United States Navy (USN) and United States Air Force (USAF). Common requirements are identified and capabilities are developed and prioritized in an evolutionary approach. An individual JMPS Mission Planning Environment (MPE) is a combination of the JMPS framework, common components, and the necessary system hardware required to satisfy mission planning objectives. Most Tactical Naval Aviation platforms are dependent solely on JMPS to plan precision guided munitions, sensor systems, tactical data links, secure voice communications, and basic Safety of Flight functions. The following type/model/series (T/M/S) naval aircraft are supported by JMPS: AH-1W, F/A-18 A-F, E-2C, EP-3E, EA-6B, AV-8B, S-3, V-22, Chief of Naval Air Training (CNATRA), EA-18G, MV-22, C-2, MH-53E, P-3, Aircraft Carrier Intelligence Center (CVIC), SH-60B/F, HH-60H, CH-53D/E, CH-46E, UH-1N, VH-3/VH-60, AH-1Z, UH-1Y, MH-60R/S and E-2D. All T/M/S are required to transition to Microsoft Windows 7 due to End of Life (EOL) of Microsoft XP (April 2014)using Framework (FW) Version 1.3.5. Custom support for Windows XP is planned to allow remaining naval aircraft to be supported during the transition. Future JMPS platforms include: MQ-4C (Triton) and CH-53K. The re-architecture of JMPS will support net-centric goals by providing route "publish and subscribe" capabilities, transition to 64 bit allows for memory space expansion to accommodate future Microsoft Operating Systems, emerging technologies, and critical Cyber Security updates. Funding profile includes JMPS baseline efforts for all existing T/M/S on Windows 7 32 bit framework while concurrently re-architecting to a 64 bit framework. 64-bit development requires complete software restructure to address memory limitations and system errors resulting in JMPS computer crashes. The transition from the current 32-bit architecture (4GB RAM) to a 64-bit architecture (196GB RAM) provides additional memory access, increased planning efficiencies; creating a more stabilized architecture with fewer fleet memory crashes. Delaying JMPS 64-bit transition to the fleet will cause system crashes to continue. It will also delay required mission planning fixes based upon known software obsolescence, and decreases platform stability. Naval Tactical Command Support System (NTCSS): The NTCSS is a multi-function program designed to provide standard tactical support information systems to various afloat and associated shore-based fleet activities. The mission is to provide the Navy and Marine Corps with an integrated, scalable system that supports the management of logistical information, personnel, material and funds required to maintain and operate ships, submarines, and aircraft. The Naval Operational Business Logistics Enterprise (NOBLE) family of programs will provide direct support to warfighter readiness with maintenance, supply, and personnel administration capabilities using an open architecture framework that incorporates business process re-engineering (BPR) allowing for the consolidation of over 23 standalone application systems. These capabilities include enhanced situational awareness, planning, execution, personnel administration, and management of maintenance and supply logistics and business functions to ships/submarines, aviation squadrons, shore operational sites, and expeditionary units with a total user base exceeding 150,000. NOBLE will meet current and emerging demands for cyber, Financial Improvement and Audit Readiness (FIAR), Navy logistics and maritime maintenance mission requirements, and eliminate over 700 application/database servers. NOBLE will deploy to Navy Enterprise Data Centers (NEDC) ashore, the Consolidated Afloat Networks and Enterprise Services (CANES) afloat, and Department of the Navy (DON) commercial cloud computing environments. Maritime Tactical Command and Control (MTC2) is the next generation C2 solution that will deliver Battle Management Aids (BMA) and Maritime Planning Tools (MPT) to dynamically plan, direct, monitor, and assess maritime operations in support of Joint, Multi-Service, Coalition Forces planning. MTC2 will leverage a System of Services (SoServ) to deliver capabilities improving decision speed and dynamic synchronization of forces. BMAs/MPTs are small, capability-focused deliveries that can be rapidly developed, tested, and fielded. MTC2 will engage with the OPNAV-led Requirements Governance Board to define and prioritize the BMAs and MPTs that MTC2 will be on deliver and align to the PEO enterprise architecture (Consolidated Afloat Network Enterprise Service (CANES), Agile Core Services (ACS)) for fielding to all echelons of command (afloat and ashore) within the Navy. The program's objective is to provide a suite of maritime applications (BMAs/MPTs) that enable planning, execution, monitoring, and assessment in support of operational and tactical level of war requirements. MTC2 will field BMAs/MPTs designed to provide automated and structured support for tactical and operational planning, decision-making, and execution. MTC2 will incorporate distributed data transfer capability for enhanced operational data exchange between command and control systems, combat systems, logistics, and intelligence systems for timely threat identification, location, and status alongside blue force data. MTC2 will provide Global Force Management - Data Initiative (GFM-DI) is the Department-wide enterprise solution that enables visibility/accessibility/sharing of data applicable to the entire Department of Defense (DoD) force structure. MTC2 will be the program that fulfills a portion of the Navy's GFM-DI requirements. Navy Air Operations Command and Control (NAOC2): NAOC2 integrates and tests Air Force program of record systems that provide an integrated and scalable planning system for standardized, secure, and automated decision support for Air Force, Joint, and Allied commanders worldwide. These programs provide automated air operations planning, execution management and intelligence capabilities at the Force level to include fleet commanders, numbered fleet commanders, Commander Carrier Strike Groups, Commander Expeditionary Strike Groups, Commander Landing Forces, and Joint Task Force Commanders. NAOC2 includes Theater Battle Management Core System (TBMCS) and Command and Control Air Operations Suite - Command and Control Information Services (C2AOS-C2IS). C2AOS-C2IS is being developed as a Service Oriented Architecture (SOA) service to allow for scalability and integration with Common Computing Environments (CCE). Continuation of these efforts will significantly enhance the Joint Force Air Component Commander and Combined Air Operations Center personnel to plan daily air operations including strike, airlift, offensive/defensive air, and refueling missions in support of combat operations, addressing the requirement of war fighter distributed planning and execution processes along with significantly improving Joint interoperability. TBMCS continues a hardware transition to CCEs such as Consolidated Afloat Networks and Enterprise Services (CANES). Currently, TBMCS is the key system that is used to conduct real world air planning in the Joint and Navy environments. C2AOS-C2IS will replace TBMCS in a SOA environment while bringing more flexibility to the war fighter. Digital Warfare Office (DWO): Supports the development of requirements modeling and data science experimentation environment, mission area model-based engineering (MBE) teams, development of digital technical baselines, development of digital architectures, and the development of workforce training in model-based systems engineering. FORCEnet: Initiative's mission is to deliver Information Dominance by (a) accelerating the transformation to a Distributed, Networked force; (b) achieve interoperability based on Architectures and Standards; and (c) Experiment with, evaluate and employ the enabling technologies. Effort is a non-acquisition program that is the operational instantiation of FORCEnet. The end-state is a distributed network of weapons, sensors, Command and Control (C2), platforms and warriors.

Open PDF

Document Details

Document Type: R2 Budgetary Justification
Publication Date: Oct 01, 2018
Source ID: 0604231N_5_1319_PB_2018
Change Summary Explanation: Technical: Not applicable. Schedule: TACTICAL SUPPORT CENTER (Project 0486): Increase in FY2018 is in support of the focus on Systems Engineering and Primary Hardware Development efforts as TacMobile approaches the Preliminary Design Review (PDR) for Increment 3, to prepare for support of ACAT I P-8A Increment 3 Integrated Test events by FY20. Specific efforts include: Engineering and development of TacMobile architecture for P-8A Applications Based Architecture (ABA) interface and building an Engineering Development Model with appropriate P-8A ABA interface to enable and test net ready application; Engineering and development of a TacMobile architecture interface for P-8A Anti-Submarine Warfare (ASW) Signals Intelligence (SIGINT); Engineering, development and integration of Multiple Security Level enclaves, or common solution to remain interoperable with P-8A security interfaces. Naval Tactical Command Support System (NTCSS) (Project 3032): Funding in Project 3032 decreases from FY2017 to FY2018 as NTCSS transitioned development of tactical support information systems to the Naval Operational Business Logistics Enterprise (NOBLE). Software conversion efforts for Naval Aviation Logistics Command Management Information System (NALCOMIS) applications, Optimized Intermediate Maintenance Activity (OIMA) and Optimized Organizational Maintenance Activity (OOMA), transitioned to NOBLE, Project 3260 in FY2018. Naval Operational Business Logistics Enterprise (NOBLE) (Project 3260): FY2018 new start. Maritime Tactical Command and Control (MTC2) (Project 3323): MTC2 funding prioritized to address operational and tactical Battle Management Aids (BMAs) and Maritime Planning Tools (MPTs). MTC2 Project Description Document (PDD) outlines the initial project scope to introduce prototype software in a SIPRNET Development Environment to gain fleet feedback on capabilities and requirements for the MTC2 transition to an Acquisition Category (ACAT) program of record. Beginning in FY18, GFM-DI plans and accomplishments will be moving under the MTC2 Project and Program of Record. Increased funding in FY2018 provides the necessary resources for software development and integration necessary to be hosted on the enterprise infrastructure, system test, and production activities (to include logistics) required to deliver an operational planning tool prototype. Specific capabilities developed in FY2018 are enhanced tactical picture, web-enabled interface, plan/re-plan force allocation, collaboration planning, synchronization and early implementation of a layered cyber defense. Additionally, it provides resources necessary to investigate and transition Science and Technology products to satisfy detailed MTC2 capabilities. Navy Air Operations Command and Control (NAOC2)(Project 3324): United States Air Force (USAF) Command and Control Air Operations Suite-Command and Control Information Services (C2AOS-C2IS) software development delays due to software maturity and realignment of critical user requirements resulted in a schedule slip/compression for Navy integration and testing efforts. Integrated Developmental Test and Operational Tests (OT) now include Capability Package (CP) 3 in addition to CP1 and CP2, with separate OTs added for Afloat and Ashore, and has been aligned to the latest Air Force testing schedule. CP5 was originally defined as emerging requirements, but has been relabeled by USAF as C2AOS-C2IS modernization, since it will release multiple software modifications and involve multiple integration efforts. Mission Planning (Project 2213): Test and Evaluation: Framework v1.3.5 MPE integration/validation has extended from 4th QTR 2015 to 4QTR 2016 to allow full fielding of Mission Planning on the F/A-18 platform. Mission Planning schedule FY17 and out is included in Mission Planning PE 0605215N. Funding: FORCEnet (Project 9123) $4.000 million is required to support approved increases for the Digital Warfare Office (DWO). Funding supports development of requirements modeling and data science experimentation environment, mission area model-based engineering (MBE) teams, development of digital technical baselines, development of digital architectures, and the development of workforce training in model-based systems engineering. DWO funding will be moved to PU 3425 starting in FY18.
Service Agency Name: Navy

Entities

Organizations

United States Navy

Tactical Command System

Abstract

Document Details

Entities

Organizations

Tags

Communities of Interest

DTIC Thesaurus Topics

Readers

Technology Areas

Related Documents