Tactical Command System

Abstract

The Tactical Command System upgrades the Navy's Command, Control, Computer and Intelligence (C3I) systems and processes C3I 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 program provides evolutionary systems and equipment upgrades to support the Maritime Component Commanders (Expeditionary Ashore) and Maritime Patrol and Reconnaissance Force Commanders with the capability to plan, direct and control the tactical operations of Joint and Naval Expeditionary Forces and other assigned units within their respective area of responsibility. These operations include littoral, open ocean, and over land surveillance, anti-surface warfare, over-the-horizon targeting, counter-drug operations, power projection, antisubmarine warfare, mining, search and rescue, and special operations. The missions are supported by the Tactical Operations Centers (formerly Tactical Support Centers), the Mobile Tactical Operations Centers (formerly Mobile Operations Control Centers), and the Joint Mobile Ashore Support Terminal. TacMobile C2 systems are based on the Global Command and Control System - Maritime architecture which is Defense Information Infrastructure Common Operating Environment compliant. 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 vulnerabilities as identified in Operational Test (OT). 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 will expose the system to risks based upon architectural weaknesses in regards to cyber security vulnerabilities. Naval Tactical Command Support System (NTCSS): Enterprise Database and Maritime Logistics Data Network (MLDN): 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. Maritime Tactical Command and Control (MTC2): MTC2 is a software program which will provide tactical Command and Control (C2) capabilities and Maritime unique Operational Level of War capabilities not supported by the joint C2 effort. MTC2 will align with the Navy Tactical Cloud (NTC) when available, and leverage Consolidated Afloat Network Enterprise Service (CANES), Agile Core Services (ACS), and legacy Integrated Shipboard Network System (ISNS). MTC2 will field to all echelons of command (afloat and ashore) within the Navy. The goal is to provide a suite of maritime applications that enable enhanced situational awareness, planning, execution, monitoring, and assessment in support of operational and tactical level of war requirements. MTC2 will field maritime applications designed to provide automated and structured support for tactical and operational planning, decision-making, and execution. Global Force Management - Data Initiative (GFM-DI) is the Department-wide enterprise solution that enables visibility/accessibility/sharing of data applicable to the entire 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): integrates and tests Air Force produced systems that provide for an integrated and scalable planning system that provides standardized, secure, 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 Group, Commander Expeditionary Strike Group, Commander Landing Force, and Joint Task Force Commanders. NAOC2 includes Theater Battle Management Core System (TBMCS), Command and Control Air and Space Operations Suite (C2AOS), plus Command, Control and Information Services (C2IS). C2AOS and C2IS are being developed as Service Oriented Architecture (SOA) services to allow for scalability and integration with Common Computing Environments (CCE). Continuation of these efforts will significantly enhance the Joint Force Air Component Commander (JFACC) and Combined Air Operations Center (CAOC) personnel to plan daily air operations including strike, airlift, offensive and defensive air, and tanker missions in support of combat operations, addressing the requirement of war fighter of distributed planning and execution processes and 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 environment. C2AOS and C2IS will replace TBMCS in a SOA environment while bringing more flexibility to the war fighter, planner, and executor. 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. Trident Warrior (TW): TW enables early delivery of Net-Centric Operation/Warfare (NCO/W) capabilities to the warfighter via Fleet-directed Trident Warrior operational events with an emphasis on delivering Maritime Domain Awareness (MDA) with Maritime Operations Center (MOC) capability.

Open PDF

Document Details

Document Type
R2 Budgetary Justification
Publication Date
Oct 01, 2016
Source ID
0604231N_5_1319_PB_2016
Change Summary Explanation
The FY 2016 funding request was reduced by $6.8 million to account for the availability of prior year execution balances. Technical: Not applicable. Schedule: TACTICAL SUPPORT CENTER (Project 0486): N/A Naval Tactical Command Support System (NTCSS) (Project 3032): Increasing requirements in information security and functional capability have required shifts in the approach for systems design and development. The updated schedule reflects a more integrated plan to accomplish refined requirements, fact-of-life changes, and modernization of the NTCSS system. As development approaches and build requirements are solidified, changes to the schedule will reflect more accurate time frames for multiple NTCSS system builds. Maritime Tactical Command and Control (MTC2) (Project 3323): MTC2 schedule and deliverables re-baselined as required to align efforts towards Navy Tactical Cloud (NTC) testing in FY16. Requirement Definition Package (RDP) moved to Q2; waiting for final approval from Naval Capabilities Board (NCB). MTC2-Release 0 Software Requirement Specification (R0 SRS) removed from Q1FY15; no longer required. Capability Drop 2 (CD 2), Release 2 Request for Proposal Release Decision (R2 RFP RD), Build Decision Release 2 (BD R2), MTC2 Release 1 (R1), and MTC2 Initial Operating Capability (IOC) moved to the right to align with development, testing, and integration of MTC2 Build Decision Release 1 (BD R1). Navy Air Operations Command and Control (NAOC2)(Project 3324): Command and Control Air Operations Suite - Command and Control Information Services (C2AOS-C2IS) testing will now be conducted in multiple phases. Capability Package 1 (CP1) and CP2 Operational test has shifted to FY16 with CP3 being tested separately in FY17." Mission Planning (Project 2213): Acquisition Milestones: JMPS FW 64 Bit Initial Operational Capability (IOC) Details added to the schedule- Effort will occur in 2Q FY20 - The transition to a 64 bit system is needed to address current and future memory and processing limitations. Test and Evaluation: JMPS FW 64 Bit Mission-Planning Environment (MPE) Integration/Validation- 1Q FY18-4Q FY19 / 1Q FY18-4Q FY20- Continuation of 64 bit MPE integration and test efforts associated with the 43 aircraft T/M/S currently planned to utilize JMPS by FY16. The transition to a 64 bit system is needed to address current and future memory and processing limitations.
Service Agency Name
Navy

Entities

Organizations

  • United States Navy

Tags

Communities of Interest

  • C4I
  • Cyber
  • Ground and Sea Platforms
  • Sensors
  • Space
  • Weapons Technologies

DTIC Thesaurus Topics

  • Air Force
  • Command And Control
  • Command And Control Systems
  • Computer Programming
  • Computers
  • Control Systems
  • Data Links
  • Department Of Defense
  • Digital Communications
  • Navy
  • Operating Systems
  • Radio Equipment
  • Test And Evaluation
  • United States
  • Unmanned Aerial Systems
  • Warfare
  • Xml

Readers

  • Aerospace Engineering
  • Enterprise Information Systems Architecture and Joint Command Capability Interoperability Support.
  • Maritime and Naval Warfare Studies

Technology Areas

  • Cyber
  • Fully Networked C3
  • Fully Networked C3 - Command and Control
  • Space

Related Documents