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. Global Command and Control System - Maritime (GCCS-M): GCCS-M is a part of the GCCS Family of Systems (FoS). As such and responding to Congressional direction (Section 247 of Fiscal Year 2010 National Defense Authorization Act (NDAA)), it will form the basis for the evolution of new command and control capabilities and Maritime Tactical Command and Control (C2) capabilities within the Department of Defense (DoD). While sustaining and synchronizing currently fielded operations, the Navy will modernize and enhance current capabilities to support both the Service and Joint war fighter as a part of a synchronized, orchestrated DoD-wide effort that will transition the current GCCS FoS into a more agile, net-centric, services-oriented environment. These efforts will take advantage of both streamlined processes within the requirements community, such as the "IT Box" and ongoing changes in the information technology acquisition process, as described in chapter 6 of the March 2009 Report of the Defense Science Board (DSB) Task Force on DoD Policies and Procedures for the Acquisition of Information Technology (Section 804 of Fiscal Year 2010 NDAA). Mission Planning: The Joint Mission Planning System (JMPS) is the Chief of Naval Operation's (CNOs) 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, United States Air Force, United States Army, and United States Special Operations Command. 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 naval aircraft are supported by JMPS: F/A-18 A-F, E-2C, EA-6B, S-3, MV-22 and AV-8B. Future JMPS platforms include: CH-46E, CH-53, MH-53E, H-60B/F/H, UH-1N, P-3, KC-130T/J, C-2, AH-1W/Z, EA-18G, H-60 R/S, VH-71, P-8, E-2D, UH-1Y, H-53K, VH-3, VH-60 and C-130. As directed via the CNO's Navy Enterprise Architecture and Data Strategy policy, the next JMPS architecture version (Framework V 1.4) will support net-centric goals by providing route "publish and subscribe" capabilities. 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. Trusted Information Systems: Radiant Mercury is a secure information platform that provides an automated means to sanitize, downgrade, guard, and transliterate formatted data at various classifications, compartments and releasabilities. With the aid of a reliable human reviewer, RM can process nonstandard messages, such as messages with National Imagery Transmission Format products and other non/semi-formatted file types. It enables combat commanders and operational commanders, afloat and ashore, to disseminate and receive critical operational and intelligence information with coalition and allied forces. 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. Funding supports the design, development, and testing of the ISNS LAN for surface ships. ISNS includes integrated core services to provide a Service Oriented Architecture which is the mechanism to deliver the FORCEnet interface to the warfighter. The Afloat Core Services (ACS) provides a composeable warfighting environment enabling dynamic configuration of capabilities tailored to meet specific warfighting missions. As the warfighting mission changes, the capabilities or services can be re-configured on the fly to meet the new warfighting requirement. This dynamic reconfiguration of services also known as "plug and fight" meets the composeable services vision of FORCEnet. ACS also provides the common core enterprise services and framework to allow organizations ubiquitous access to reliable, decision-quality information through a net-based services infrastructure and applications to bridge real-time and near-real-time Communities Of Interest. The ACS will empower the end user to pull information from any available source, with minimal latency, to support the mission. Its capabilities will allow Department of the Navy as well as Global Information Grid users to task, post, process, use, store, manage, and protect information resources on demand for warfighters, policy makers, and support personnel. ACS will utilize a spiral process for delivering capability to the warfighter. The ISNS Inc 1, Sensitive Compartmented Information (SCI) Networks and Combined Enterprise Regional Information Exchange System (CENTRIXS) programs will begin migrating to ISNS Inc 2/Consolidated Afloat Networks and Enterprise Services (CANES) in FY09. ISNS Inc 2/CANES will serve to transition numerous Fleet networks to a single, adaptive, available, secure computing network infrastructure while delivering enhanced technologies in: Integrated Voice, Video and Data; Common Computing Environment: ACS; and Multi-Level Security /Cross Domain Solutions. Full transition to CANES Inc 1 occurs in FY 2010. Combined Enterprise Regional Information Exchange System (CENTRIXS): The CENTRIXS program provides US Navy ships with secure, reliable, high-speed Local Area Network (LAN) with access to the Coalition WAN to include CENTRIXS Four-Eyes, Global Counter Terrorism Task Force, North Atlantic Treaty Organization Information Data Transfer System, Multinational Coalition Force - Iraq, bilateral networks such as CENTRIXS-J (Japan) and CENTRIXS-K (Korea), and Communities Of Interest virtual networks such as Coalition Naval Forces - U.S. Central Command (CENTCOM) (CNFC), and Cooperative Maritime Forces - Pacific. The CENTRIXS system provides real-time tactical and operational information sharing at the SECRET and SECRET REL (Releasable) level between naval afloat units, Component Commanders, Fleet Commanders, Numbered Fleet Commanders and Coalition Forces/Allies. When the CENTRIXS network is combined with other subsystems (Radio/Satellite Communications), it delivers an end-to-end network centric warfighting capability. The CENTRIXS program is comprised of Block 0, I, and II systems fielded across the Fleet, and Increment 1 which provides a network infrastructure that allows simultaneous access to multiple Coalition WAN and incorporates the Common PC Operating System Environment which provides a server and client operating system environment for other applications and collaborative tools such as Same time Chat, Domino and Command and Control PC as means to share a Common Operational Picture and exchange information using Collaboration At Sea. The CENTRIXS program uses both Commercial Off The Shelf hardware and software and Open Standards to maximize commercial technology and support. In-service engineering and technical support ensures existing systems are upgraded and modified to keep pace with current technology and industry. Combined Enterprise Regional Information Exchange System (CENTRIXS) funding supports the design, development and testing of the CENTRIXS LAN for surface and subsurface platforms and the CENTRIXS Network Operations Center (NOC). The goal of the CENTRIXS program is to provide a cost-efficient, operationally effective network that dramatically reduces current infrastructure requirements while maximizing operational flexibility and war fighter utility in a coalition environment. Multi-Level Thin Client (MLTC) architecture support shipboard Space, Weight and Power (SWAP) reductions and include initiatives for server virtualization (ability to run multiple servers on a single server), drop scalability leveraging existing Secure Internet Protocol Router Network (SIPRNET) drops, remote authentication and remote system management. Additionally funding will provide design, development and testing for a Unit Level MLTC system (provides a compressed shipboard rack/client footprint) and initiatives to include Language Translation, Communities Of Interest (COI) and Network Enclave Agility (ability to dynamically shift between all coalition networks and COIs) and Multi-Level Chat (a Cross Domain Solution (CDS) chat capability). The CENTRIXS program will start migrating to ISNS Inc 2/Consolidated Afloat Networks and Enterprise Services (CANES) in FY09. Integrated Shipboard Network Systems (ISNS) Inc 2/Consolidated Afloat Networks and Enterprise Services (CANES) will serve to transition numerous Fleet networks to a single, adaptive, available, secure computing network infrastructure while delivering enhanced technologies in: Integrated Voice, Video and Data; Common Computing Environment (CCE); Service Oriented Architecture (SOA); and Multi-Level Security (MLS)/CDS. Full transition to CANES Inc 1 occurs in FY 2010. Submarine Local Area Network (SubLAN): The SubLAN program provides Navy submarines with reliable, high-speed Mission Critical SECRET and Mission Essential UNCLASSIFIED Local Area Networks (LANs). When the SubLAN network is combined with other subsystems, it will deliver an end to end network-centric warfare capability. The SubLAN program provides network infrastructure including an Unclassified Wireless Local Area Network (UWLAN), servers, and the Common Personal Computer Operating System Environment (COMPOSE) which provides the operating system, office automation, security, and other basic network services used by all hosted applications. Funding supports the design, development, and testing of SubLAN for addition of capabilities in support of migration to the CANES program effort. 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. FORCEnet: Initiative's mission is to (a) accelerate 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. Maritime Domain Awareness (MDA) Project 2351 and 9123 (FY09 only)): MDA is the effective understanding of anything associated with the global maritime domain that could impact the security, safety, economy or environment. MDA objectives include the persistent monitoring of and ability to access and maintain data on vessels, cargo, people, and infrastructure; and the ability to collect, fuse, analyze, and disseminate information to decision makers to facilitate effective understanding. This initiative will identify, develop and transition data fusion and mining, replication, sharing and assessment tools to achieve MDA across the non-classified, unclassified and classified enclaves. Additionally, MDA will ensure capability integration with related activities and sites (both technologies and facilities). This warfighting enhancement is designed to achieve an all-source MDA capability, leveraging existing MDA initiatives in the developmental phase and ensuring the best products transition to strategic, operational and tactical users as well as further development of MDA prototypes. The products will support all-source data fusion, development and replication of MDA related data gathered in various operations such as Expanded-Maritime Intercept Operations, sharing information with allies, and developing subject matter expertise and assessment tools to achieve MDA and enhance operational decision making. Deep Lightning Bolt / Rapid Capability Development: Transformational initiative for the Navy, focused on the introduction of technologies will have the ability to immediately enhance the Navy's Sea Power 21 objectives. Congressional Increases: FY09 includes: Congressional increase for Intelligence, Surveillance, and Reconnaissance Enhancements. FY10 includes: Congressional increase for Intelligence, Surveillance, and Reconnaissance Enhancements and Shipboard Wireless Network.

Open PDF

Document Details

Document Type: R2 Budgetary Justification
Publication Date: Oct 01, 2011
Source ID: 0604231N_5_1319_PB_2011
Change Summary Explanation: Technical: Not applicable. Schedule: See below Mission Planning (Project 2213): Acquisition Milestones: JMPS 1.2.4 OTRR (4Q FY08 - 1Q FY09) - Operational Testing (OT) resources not available during 4Q FY08. JMPS V.1.4 OTRR (4Q FY10 - 4Q FY11) - Slipped due to prime contractor delays in meeting exit criteria for Preliminary Design Review (PDR). JMPS V.1.2.4 OT (4Q FY08 - 1Q - 2Q FY09) - Corresponding change in OT schedule to reflect change in OTRR schedule. JMPS V1.4 OT (4Q FY11 - 2Q FY12 to 1Q-2Q FY12) - FW 1.4 Development Schedule Slip. Test and Evaluation Milestones: JMPS 1.2.4 MPE Integration/Valid. (2Q FY09 - 4Q FY13) - JMPS 1.2.4 Integration will continue to be fielded longer than planned due to FW 1.4 schedule slips. JMPS 1.4 MPE Integration/Valid. (1Q FY11 - 4QQ FY15) - Slipped due to prime contractor delays in meeting exit criteria for PDR (Preliminary Design Review). JMPS V1.4 FQT (1Q FY 11 - 1Q FY 11) - Slipped due to Air Force Contracting Delays. JMPS V1.4 DT (2Q FY09 - 2Q FY 11) - Sipped due to Air Force Contracting Delays. Production Milestones: JMPS V1.4 IOC (3QFY13 - 3Q FY12) - FW 1.4 IOC established during Integrated Baseline Review (IBR) completed May 09. TACTICAL SUPPORT CENTER (Project 0486): MSC decision is scheduled for 4th Qtr FY11. Operational Test is scheduled for 2nd Qtr FY12. FRP is scheduled for 4th Qtr FY12. 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. Global Command and Control System - Maritime (GCCS-M) (Project 0709): In August 2009, the MDA approved an alternate material solution of Increment 2 was approved to support the requirements of Group Level ships, Unit Level ships, and submarines. This solution was based on the Office of Naval Research (ONR)-funded project extensible Common Operational Picture (XCOP). The Increment 2 Milestone C decision is scheduled in FY2010. Radiant Mercury (RM) - Schedule slip of RM Version 5.0 from 4QFY09 to 3QFY10 caused by delay in award of follow-on developer contract. CENTRIXS (Project 2307): The CENTRIXS-M program achieved MS C in July 2009 and the schedule has been modified to reflect a shift for Increment 1 (Inc 1) Development Test/Operational Test (DT/OT) Force Level (FL) from Jul 2010 (Q4 FY10 ) to Feb 2010 (2QFY10) and Increment 1 FL Full Rate Production (FRP) from 2Q FY10 to 3Q FY11]. Inc 1 FL Initial Operating Capability (IOC) is updated from (2Q FY11) to (2/3Q FY10) and Inc 1 Unit Level (UL) FRP is updated from (1Q FY12) to (4Q FY11). Inc 1 Low Rate Initial Production (LRIP) deliveries shift reflects updated production leadtime. Inc 1 DT/OT UL is scheduled for Jul 2010 (3QFY10) with a Inc 1 UL Fielding Decision scheduled from 4QFY11 to 1Q/FY12. Full transition to CANES Inc 1 occurs in FY 2010. COMPOSE 4.0 Software deliveries changed from 2Q FY10 to 4Q FY11 and has been updated to reflect current software fielding schedule. ISNS (Project 2307): ISNS Inc 2/CANES Material Development Decision (MDD) shifted Milestone B 1Q FY09 to 3Q FY10. In addition, a fielding decision for D(V)X has been added in 2Q FY09. Full transition to CANES Inc 1 occurs in FY 2010. SubLAN (Project 2307): Multi Level Security requirements have been removed from SubLAN POR. Maritime Domain Awareness (MDA) (Project 2351): MDA program schedule has been modified to reflect an acceleration of the MDA Fielded Enterprise Node integration to complete in FY11. This includes planned and approved enhancements to the MDA Fielded baseline to optimize performance with the Enterprise Node while realizing life-cycle cost savings through reduced hardware footprint at deployed locations. For Expanded-Maritime Intercept Operations (EMIO), the changes reflect the completion of the End to End EMIO capability enhancements which resulted in reduced time to capture, transmit, analyze and act on maritime boarding information from days to hours. The schedule also reflects increased testing and validation of EMIO capabilities supporting transition. The schedule has been updated to facilitate Requirement Manager's incorporation of stakeholder inputs. FY11 from previous President's Budget is shown as zero because no FY11-15 data was presented in President's Budget 2010.
Service Agency Name: Navy

Entities

Organizations

United States Navy

Tactical Command System

Abstract

Document Details

Entities

Organizations

Tags

Communities of Interest

DTIC Thesaurus Topics

Fields of Study

Readers

Technology Areas

Related Documents