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. Global Command and Control System - Maritime (GCCS-M): GCCS-M is the Maritime implementation of the Global Command and Control System (GCCS) Family of Systems (FoS). It supports decision making at all echelons of command with a single, integrated, scalable C4I system that fuses, correlates, filters, maintains and displays location and attribute information on friendly, hostile and neutral land, sea and air forces, integrated with available intelligence and environmental information. It operates in near real-time and constantly updates unit positions and other situational awareness data. GCCS-M also records data in appropriate databases and maintains a history of changes to those records. System users can then use the data to construct relevant tactical pictures using maps, charts, topography overlays, oceanographic overlays, meteorological overlays, imagery, and all-source intelligence information coordinated into a Common Operational Picture that can be shared locally and with other sites. Navy commanders review and evaluate the general tactical situation, plan actions and operations, direct forces, synchronize tactical movements, and integrate force maneuver with firepower. The system operates in a variety of environments and supports joint, coalition, and allied forces. GCCS-M is implemented Afloat and at Ashore fixed command 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 capabilities, 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 of the aforementioned T/M/S are required to transition to Microsoft Windows 7 before Microsoft XP support ends April 2014 by using Framework (FW) Version 1.3.5. An extension of Windows XP is planned to allow all naval aircraft to be supported during the transition. Future JMPS platforms include: MQ-4C (Triton) and H-53K. The next JMPS architecture version will support net-centric goals by providing route "publish and subscribe" capabilities, transition to 64 bit and emerging technology and Information Assurance (IA) requirements. Funding profile includes 64 bit development which requires a complete software restructure to address memory limitations and system errors resulting in JMPS computer crashes. Failure to move to 64 bit will result in an inability to support future advanced platform mission planning needs based on processing space and capability. Shipboard Local Area Network (LAN)/Wide Area Network (WAN) : Integrated Shipboard Network System (ISNS): ISNS provides Navy ships with reliable, high-speed SECRET and UNCLASSIFIED LANs, providing the network infrastructure (switches and drops to the PC), Basic Network Information Distribution Services and access to the Defense Information Systems Network WAN, Secure and Nonsecure Internet Protocol Router Network (SIPRNET and NIPRNET) which are used by other hosted applications or systems such as Naval Tactical Command Support System, Global Command and Control System - Maritime, Defense Messaging System, Navy Standard Integrated Personnel System, Naval Mission Planning System, Theater Battle Management Core Systems, and Tactical Tomahawk Weapons Control System. It enables real-time information exchange within the ship and between afloat units, Component Commanders, and Fleet Commanders, and is a key factor in the implementation of the Navy's portion of Joint Vision 2020. 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 provides Navy with the ability to deliver maritime domain-unique tactical Command and Control (C2) capabilities from Maritime Operations Centers down to the lowest tactical unit of operations. MTC2 supports alignment and provides interoperability of Navy C2 with the Department of Defense (DoD) joint C2 way-forward. The program will fully align with joint C2 data and service exposure and consumption goals, architectures, and Net-Centric Enterprise Service efforts. These resources support the evolutionary acquisition, materiel solution analysis, technology development, engineering and software development of these capabilities. 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. GFM-DI is the enterprise solution for force structure representation and MTC2 will be the data source for the Navy's force structure representation. In FY 2014, GFM-DI will perform design and development for integration into MTC2 and will align to the joint command and control objective architecture (jC2 OA). 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.

Document Details

• Document Type: R2 Budgetary Justification
• Publication Date: Oct 01, 2014
• Source ID: 0604231N_5_1319_PB_2014
• Change Summary Explanation: Technical: Not applicable. Schedule: TACTICAL SUPPORT CENTER (Project 0486): FRP is scheduled for 4th Qtr FY12. Global Command and Control System - Maritime (GCCS-M) (Project 0709): In August 2011, ASN (RD&A) issued Fielding Decision Review (FDR) approval to field GCCS-M 4.1 Force Level (FL) and Unit Level (UL) configurations. Group Level Final Engineering Drop delivered to government; Development Test, Technical Evaluation and Operational Test in FY 2013. Operational Assessment was dropped in FY 2013 as Director of Operation Test & Evaluation (DOT&E) and Command Operational Test & Evaluation Force (COTF) determined it is not needed for GL 4.1. FDR is an FY 2013 funded effort which slipped to FY 2014. Global Force Management - Data Initiative (GFM-DI) development included in the GCCS-M baseline in FY 2012. Mission Planning (Project 2213): System Development: JMPS FW 64 Bit Prototype - Details added to the schedule. Effort runs from 1Q FY13-4Q FY13 - Determine the complexity and create prototypes for the migration of components from the existing 32-bit JMPS to a 64-bit Mission Planning Environment (MPE). The transition to a 64-bit system is needed to address current and future memory and processing limitations. JMPS FW 64 Bit Architecture Development- 1Q FY15-4Q FY16/ 3Q FY14-4Q FY17 - Development is required to transition from current FW 32 bit to 64 bit architecture. The transition to a 64-bit system is needed to address current and future memory and processing limitations. JMPS FW 64 Bit Mission Planning Environment (MPE) Integration/Validation- 1Q FY17-4Q FY17/ 1Q FY18-4Q FY18 - Delay due to JMPS FW 64 Bit Architecture Development schedule. Development is required to transition from current FW 32 bit to 64 bit architecture. The transition to a 64-bit system is needed to address current and future memory and processing limitations. JMPS V1.4 Development Test- 1Q FY12-3Q FY12/ Removed from schedule - Due to USAF Increment IV (PE 0208006F) Critical Change Review, FW V1.4 will not achieve Windows 7 transition need date. FW 1.3.5 will be utilized in lieu of FW 1.4 during Windows 7 transition. JMPS V1.4 MPE Integration/Validation - 1Q FY12-4Q FY16/ Removed from schedule - Due to USAF Increment IV (PE 0208006F) Critical Change Review, FW V1.4 will not achieve Windows 7 transition need date. FW 1.3.5 will be utilized in lieu of FW 1.4 during Windows 7 transition. JMPS V1.3.5 Mission Planning Environment (MPE) Integration/Validation- 1Q FY12-4Q FY13/ 1Q FY12-4Q FY15 - An extension of Windows XP is planned to allow all naval aircraft to be supported during the Windows 7 transition. Windows XP custom support contract with Microsoft to extend use of Windows XP-based JMPS MPEs including FA-/EA-18, EA-6B, E-2C, E-2D and AV-8B past April 2014 end-of-service for Windows XP. JMPS V1.2.4 Mission Planning Environment (MPE) Integration/Validation- 1Q FY12-4Q FY13/ 1Q FY12-2Q FY14 - An extension of Windows XP is planned to allow all naval aircraft to be supported during the Windows 7 transition. Windows XP custom support contract with Microsoft to extend use of Windows XP-based JMPS MPEs including FA-/EA-18, EA-6B, E-2C, E-2D and AV-8B past April 2014 end-of-service for Windows XP. 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): Acquisition Milestones: MTC2 will follow the DoD Rapid Information Technology Acquisition process. Milestone decisions are no longer applicable, but rather replaced by Build Decisions (BDs) and Fielding Decision Reviews (FDRs) for each release of new capabilities to the user community. The MTC2 Materiel Development Decision (MDD) will be documented and supported by a Build Decision (Release 1) which will authorize entry into the program's Incremental & Iterative Developmental & Deployment (IIDD) phase and development of intial software capabilities required by the fleet. A FDR will be conducted following the successful completion of an Operational Test. Subsequent tentative BDs/FDRs have been added to the schedule, which will be further updated as funding and user needs are finalized in the future. If subsequent decisions are made to not follow the DoD Rapid Information Technology Acquisition process, the standard DoD 5000 acquisition process will be used. Schedule: Build Decision Release 2 and Fielding Decision Release 1 moved to the right to reflect lessons learned from previous Program Executive Office Command, Control, Communications, Computers, & Intelligence (PEO C4I) pilot programs following the DoD Rapid Informaton Technology Acquisition process. The following Build Decisions, Fielding Decision Reviews, Operational Tests, and Development Tests are linked together and align to the acquisition process. Engineering Drops 2, 4, and 5 were moved to align with the Build and Fielding Decisions Reviews. The Build Decisions and Fielding Decisions were also moved to align with the contracting process of six months from release to implementation of a task order. The Developmental Tests were exchanged with the Operational Assessments to align with the Integrated Defense Acquisition, Technology, and Logistics Life Cycle Management Systems. Developmental Test 4 and Operational Assessment 4 were moved to the right to reflect a 12-18 month test and delivery cycle.
• Service Agency Name: Navy

Entities

Organizations

• United States Navy

Tags

Communities of Interest

• C4I
• Cyber
• Electronic Warfare
• Energy and Power Technologies
• Ground and Sea Platforms
• Human Systems
• Space
• Weapons Technologies

DTIC Thesaurus Topics

• Air Force
• Command And Control
• Command And Control Systems
• Control Systems
• Cross Domain
• Information Systems
• Naval Operations
• Navy
• Network Protocols
• Operating Systems
• Personnel Management
• Radio Equipment
• Surveillance
• System Software
• Systems Engineering
• Test And Evaluation
• Warfare

Readers

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

Technology Areas

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