Naval Network Warfare Command (COMNAVNETWARCOM) Updated: 13 Jul 08 History of NAVNETWARCON (August 2001 - May 2002) ========================================================================================================= Commander, Naval Telecommunications Command (COMNAVTELCOM) Washington DC ( - Dec 1990) Commander, Naval Computer and Telecommunications Command (COMNAVCOMTELCOM), Washington DC (Dec 1990 - Aug 2001) Naval Network Operations Command (COMNAVNETOPSCOM/NNOC), Washington DC (Aug 2001 - May 2002) Naval Network Warfare Command (COMNAVNETWARCOM/NNWC), Norfolk VA (May 2002 - ) ========================================================================================================= The Commander, Naval Telecommunications Command (COMNAVTELCOM) was located at 4401 Massachusetts Ave. NW, at the Naval Security Station (NAVSECSTA) in Washington DC. In December, 1990, the Commander, Naval Telecommunications Command (COMNAVTELCOM), located at the Naval District Washington's Nebraska Avenue Complex in Northwest Washington DC, was renamed the Naval Computer and Telecommunications Command (COMNAVCOMTELCOM), Washington DC. COMNAVCOMTELCOM was an Echelon II command in an active, operational status under the direct command of the Chief of Naval Operations (CNO). The CNO's coordinator for NAVCOMTELCOM was the Director, Space and Electronic Warfare Directorate (N6). COMNAVCOMTELCOM provided administrative management and operational direction to the following echelon III commands: three (3) Naval Computer and Telecommunications Area Master Stations (NCTAMS Lant in Norfolk, VA, NCTAMS PAC in Honolulu, HI, and NCTAMS EURCENT in Naples, Italy); Naval Computer and Telecommunications Station (NCTS) Guam; the Director, Communications Security Material System (DCMS), in Washington DC; the Headquarters, Navy-Marine Corps MARS Radio Station; and the Naval Electromagnetic Spectrum Center (NAVEMSCEN), Washington, DC. The mission of COMNAVCOMTELCOM was to develop, control, and disseminate fleet and shore operating procedures and interface criteria to ensure compatibility for legacy Defense Message System (DMS) automated communication systems and end-user applications with newly introduced systems. COMNAVCOMTELCOM implemented Navy Information Resources (IR) Management policy within the claimancy. COMNAVCOMTELCOM provided, operated, and maintained, as required, all Navy ashore communications resources and all non-tactical information resources for command, control, and administration of the Navy and those elements of the Defense Communications System assigned to the Navy. COMNAVCOMTELCOM adviseed Commander, Naval Space Command of validated communication requirements that demanded development or modification of satellite communication systems. COMNAVCOMTELCOM formulated policy on and exercised authoritative control over the Navy Communications Security (COMSEC) Material System, and reviewed or initiated actions in cases of loss or compromise of CMS distribution material. Telecommunications included all types of information systems in which electronic or electromagnetic signals were used to transmit information between or among points. The Naval Telecommunications System (NTS) was comprised of all the end terminal processing equipment, transmission, switching, cryptographic, and control devices used to transmit operational information in the Navy. The mission of Naval communications is to provide and maintain reliable, secure, and rapid communications, based on war requirements, to meet the needs of Naval operating forces. Naval communications must also satisfy the requirements of the Defense Communications System (DCS) and the National Communications System (NCS). The Naval Communications Processing and Routing System (NAVCOMPARS) was an automated system that served as the interface between the Automatic Digiatal Network (AUTODIN) or other networks ashore and operational units of the Navy. There were five NAVCOMPARS sites: NCTAMS EASTPAC, NCTAMS WESTPAC, NCTAMS MED, NCTAMS LANT, and NAVCOMMTELSTA Stockton, CA. The primary purpose of NAVCOMPARS was to provide security, speed, and systems compatibility for the Naval Telecommunications System (NTS). The NTS provided electrical and optical communications from the Commander in Chief and Naval Commanders down to all Naval forces under its command. The NTS was used primarily to exercise command and control over the Naval operating forces; not the shore establishment. Most shore establishments were served through the Defense Communications System (DCS). There were overlapping portions of each system, where necessary. Operational direction and management control of the assigned elements of the NTS were the responsibility of the Commander, Naval Computer and Telecommunications Command (COMNAVCOMTELCOM). In Naval communications, COMNAVCOMTELCOM determined the responsibilities of each of the various commanders, whether a Fleet Commander or the Commanding Officer of a ship. Direction and control of all Naval fleet broadcasts, ship shore, air-ground, and other direct fleet-support telecommunications were assigned to the Fleet Commanders in Chief (FLTCINCs). All Pacific Fleet Naval broadcasts were under the operational direction and control of the Commander in Chief, Pacific Fleet (CINCPACFLT). The same applied to Atlantic Fleet Naval broadcasts. These broadcasts were under the operational direction and control of the Commander in Chief, Atlantic Fleet (CINCLANTFLT). Fleet Commanders in Chief were responsible for the adequacy of communications to satisfy the needs of their respective fleets. They, in turn, assign broad communications responsibilities in the form of Fleet Operation Orders (OPORDs). OPORDs were to be complied with at every level down through individual Commanding Officers of operating ships. The Commanding Officers used only those portions of the Fleet Commander's communications OPORD that affect them. In this simple, yet direct, manner, the NTS was administered at every operational level in the fleet, according to that ship's mission and communication needs. With the merging of Automated Information Systems (AIS) and telecommunications, the mission and responsibilities of COMNAVCONTELCOM greatly increased. Due to changes in the claimancy of NAVCOMTELCOM, each of the former NAVCAMS was redesignated as a NCTAMS, and merged with a NARDAC. The four NCTAMS were NCTAMS EASTPAC, Honolulu, Hawaii; NCTAMS LANT, Norfolk, Virginia; NCTAMS WESTPAC, Guam; and NCTAMS MED, Naples, Italy. The world was divided into four Naval Communications Areas (NAVCOMMAREAs): Western Pacific (WESTPAC), Eastern Pacific (EASTPAC), Atlantic (LANT), and Mediterranean (MED). All communications activities within any of these geographical areas were organized to operate under the operational control of a NCTAMS. Those communications stations that did not merge with an AIS activity became Naval Computer and Telecommunications Stations (NCTS) or Naval Computer and Telecommunications Detachments (NCTDs). On December 1, 1990, NAVCAMS EASTPAC and NARDAC Pearl Harbor merged to form the Naval Computer and Telecommunications Area Master Station, Eastern Pacific (NCTAMS EASTPAC). The command was again renamed on October 20, 1997; when NCTAMS EASTPAC and NCTAMS WESTPAC merged. The new name, Naval Computer and Telecommunications Area Master Station, Pacific, better reflected the command's regional operating area. The former NCTAMS WESTPAC at Guam became a Naval Computer and Telecommunication Station (NCTS). In the Summer of 1997, the U.S. Naval Computer and Telecommunications Area Master Station, Mediterranean (NCTAMS MED), Naples IT, area of responsibility was enlarged to include U.S. Navy telecommunications facilities in Bahrain and in Diego Garcia. On October 1, 1997, the region's name changed from Mediterranean to Europe Central, reflecting the wider area of responsibility. NCTAMS Med became the U.S. Naval Computer and Telecommunications Area Master Station, Europe Central (NCTAMS EURCENT), Naples IT. The world is now divided into three Naval Communications Areas (NAVCOMMAREAs): Pacific (PAC), Atlantic (LANT), and Central Europe (EURCENT). All communications activities within any of these geographical areas are organized to operate under the operational control of a NCTAMS. These Master Stations are the major telecommunications sites within a NAVCOMMAREA, and are the primary keying stations for that area. NAVCOMMAREAs are the entry points for Navy Tactical Satellite Systems and also operate and maintain one or more Defense Satellite Communications System (DSCS) terminals. The three NCTAMS have, as part of their organization, a Fleet Telecommunications Operations Center (FTOC). The FTOC is the focal Point for fleet communications support. To support the operating forces of each Fleet Commander in Chief (FLTCINC), the authority to exercise operational direction over all NAVTELCOMs is delegated on an area basis to the Commanding Offiers of the Master Stations. Operational direction is decentralized down to the Commanding Officers of the three NCTAMS. These Commanding Officers report to and are immediately responsible to the FLTCINC. COMNAVCOMTELCOM, however, exercised overall operational direction to assure integration of the worldwide system, taking into consideration the requirements and priorities of other FLTCINCs and/or higher authority. The appropriate Fleet Operational Telecommunications Program (FOTP) manual provided specific information. Within the various NAVCOMMAREAs were alternate NCTAMS. They coordinated control of communications under the direction of the primary NCTAMS. The Navy decided that the public infrastructure for information technology (IT) was mature enough that they could depend on it, rather than own and operate a separte Navy system. The Navy also realized that the IT infrastructure could be treated like a utility that someone else capitalized, operated and maintained. Navy Marine Corps Intranet (NMCI) is a Department of the Navy program to deliver comprehensive, end-to-end information services enterprise-wide to the United States Navy and United States Marine Corps through a common computing and communications environment. This environment will enhance system and software interoperability and enhance information exchange capability for garrisoned and deployed forces as well as individual users. NMCI includes everything necessary to ensure the transmission of voice, video, and data information. It includes associated capital infrastructure improvements necessary to meet quality-of-service requirements, as well as maintenance, training and operation of that infrastructure. NMCI work will be performed at more than 300 Navy and Marine Corps bases located across the United States, Guantanamo Bay in Cuba, Puerto Rico, Japan, Guam, Hawaii and Iceland for an estimated 360,000 Navy and Marine Corps uniform and civilian work force members. The Defense Message System (DMS) has been established as a joint program to integrate common user, organizational and individual messaging and directory services. DMS provides writer- to-reader messaging services to and from worldwide DoD locations, including tactical deployed users, and other designated Federal Government organizations; as well as Allied users and Defense contractors. The primary objective of the DMS Program is to reduce cost and staffing by eliminating the resource intensive and archaic Automatic Digital Network (AUTODIN) system. A secondary objective is to improve support and security to the warfighters by implementing advanced messaging and directory services, building on commercial products and incorporating international standards. One of the core elements for successful Navy DMS implementation is the Operation Control Centers currently designated Area Control Centers (ACCs) and Local Control Centers (LCCs). Area Control Centers - formerly called LCC Level 3s - are the focal point for Navy DMS management in a specific Area of Responsibility (AOR). ACCs are planned for NCTAMS LANT, NCTAMS EURCENT, NCTAMS PAC and NAVCOMTELSTA San Diego. The ACCs primary mission is management of the DMS components in their AOR. ========================================================================================================= Naval Network Operations Command (COMNAVNETOPSCOM/NNOC) In August, 2001, the Chief of Naval Operations ADM Vern Clark approved the creation of the Naval Network Operations Command (NNOC) to oversee the Navy's major information technology programs. The command, a result of the merger of the Naval Computer and Telecommunications Command (COMNAVCOMTELCOM) and Task Force Navy Marine Corps Intranet (TF NMCI), was based at the existing NAVCOMTELCOM headquarters located at the Naval District Washington's Nebraska Avenue Complex in Northwest Washington DC. CAPT Charles G. Cooper, commander of NAVCOMTELCOM, initially took the reins of the new command. NNOC operated the "Information Technology for the 21st Century" (IT-21), a program designed to upgrade network systems aboard ships. The NNOC also operated the Navy's computer network attack and defense work through IT-21 and the NMCI procurement with Electronic Data Systems (EDS) Corporation. The creation of this command allowed the Navy to support the command and control of deployed forces through a network of global information technology systems and services. The merger resulted in a single organization with responsibility for operation and management of the Navy's voice, video and data networks. Naval Network Operations Command (NAVNETOPSCOM) operated and maintained the Navy’s global information technology systems and services, including enterprise networks; through assigned worldwide communications activities and related contracts, which supported warfighting operations and command and control of Naval forces, and performed such other functions and tasks as were directed by higher authority. The CNO established Commander, Naval Network Operations Command as the single focal point for Navy base level communications policy, procedures, and resources; consequently, operation and management of the Navy's Base Level Information Infrastructure (BLII) had become a core mission of NAVNETOPSCOM. ========================================================================================================= Naval Network Warfare Command (COMNAVNETWARCOM/NNWC) Effective May 1, 2002, the Navy disestablished COMNAVNETOPSCOM and established Naval Network Warfare Command (COMNAVNETWARCOM) and NAVNETSPAOPSCOM DET. The headquarters element of COMNAVNETOPSCOM was incorporated with the operating elements of Naval Space Command in Dahlgren, VA and formed the newly titled Commander, Naval Network and Space Operations Command (COMNAVNETSPAOPSCOM). Selected organizations were realigned to report to COMNAVNETWARCOM. The remaining COMNAVNETOPSCOM elements at the Nebraska Avenue Complex in Washington, DC were realigned as a detachment of COMNAVNETSPAOPSCOM. The NAVNETWARCOM command itself did not have a huge staff, but the staff was the headquarters for all decisions, identifications and directions for a global staff of 7,000. Naval Network Warfare Command (NAVNETWARCOM), is an Echelon III shore activity, which included 23 subordinate Naval information technology and information operations organizations. NAVNETWARCOM provides a single source of information support to the fleet, through assumption of central responsibility and authority over all aspects of information management. COMNAVNETWARCOM was dual-hatted as Commander, Naval Space Command (COMNAVSPACECOM) and served as the Naval Component Commander to USCINCSPACE. Several commands were placed under the authority of the Commander of NAVNETWARCOM, including the Naval Network and Space Operations Command (NNSOC) in Dahlgren, VA; the Fleet Information Warfare Center (FIWC) in Norfolk, VA; the Navy Component Task Force, Computer Network Defense (NCTF CND) in Washington, DC; and the Director, Communications Security Material System (DCMS) in Washington DC. NNSOC was established coincident with NAVNETWARCOM, through the merger of the existing Naval Space Command in Dahlgren, VA and the Naval Network Operations Command (NNOC). The Space and Naval Warfare Systems Command (SPAWAR) was assigned to report for additional duties to the NAVNETWARCOM Commander for matters related to fleet support and execution-year requirements. The Commander of the Naval Security Group (COMNAVSECGRU) was assigned to report for additional duties as the NAVNETWARCOM Director of Information Operations. This three-star flag-rank command is the type commander for Navy networks, and its establishment shows the Navy's recognition that networks, as warfare enablers, are becoming increasingly important to today's warfighter. Establishment of NAVNETWARCOM realign the various staffs needed to support the concept of one Naval network and to support that network's end-to-end operational management. Naval Network Warfare Command (NETWARCOM) is the Navy’s central operational authority for space, information technology requirements, network and information operations in support of Naval forces afloat and ashore. the NAVNETWARCOM mission statements include: to operate a secure and interoperable Naval network that will enable effects-based operations and innovation; to coordinate and assess the Navy operational requirements for, and use of, network, command and control, information technology, information operations and space; to serve as the operational forces advocate in the development and fielding of information technology, information operations and space; and to perform such other functions and tasks as may be directed by higher authority. Naval Network Warfare Command serves as a Functional Component Commander to U.S. Strategic Command (STRATCOM). NAVNETWARCOM Little Creek, Norfolk VA: http://www.netwarcom.navy.mil/. ========================================================================================================= COMNAVTELCOM to NAVNETWARCOM In December, 1990, Naval Telecommunications Command (COMNAVTELCOM) was renamed the Naval Computer and Telecommunications Command (NAVCOMTELCOM). On July 9, 2001, NAVCOMTELCOM was renamed the Naval Network Operations Command (COMNAVNETOPSCOM) (NNOC), which was disestablished on May 1, 2002; when the NETWARCOM command was formed. On May 1, 2002, the Naval Network Warfare Command (NAVNETWARCOM) was established. Twenty-three (23) Naval information technology and Naval information operations organizations were subordinated to NAVNETWARCOM, which assumed central responsibility and authority over all aspects of information management. Subordinate commands included: Naval Space Command (COMNAVSPACECOM) Dahlagren VA Naval Network Operations Command (COMNAVNETOPSCOM) Washington DC Disestablished May 1, 2002) (Formerly NAVCOMTELCOM, formerly COMNAVTELCOM) Naval Network Operations Command Det Washington DC (at the Nebraska Avenue Complex) Naval Network and Space Operations Command (COMNAVNETSPAOPSCOM) (NNSOC) Dahlgren VA Merger of COMNAVNETOPSCOM Washington DC & COMNAVSPACECOM Dahlgren VA on May 1, 2002. Fleet Information Warfare Center (FIWC) in Norfolk, VA Merged with NSGA Norfolk VA on November 5, 2005 to become NIOC Norfolk, VA> Navy Computer Incident Response Team (NAVCIRT) Little Creek, Norfolk, VA Navy Component Task Force Computer Network Defense (NCTF CND) in Washington, DC Moved to NAB Little Creek, Norfolk VA. Renamed Navy Cyber Defense Operations Command (NCDOC) Little Creek, Norfolk VA in June, 2006. Space and Naval Warfare Systems Command (SPAWAR) (ADDU for Fleet Support) Naval Security Group Command (COMNAVSECGRU) (ADDU Director of Information Operations) Disestablished on September 30, 2005 and re-established as the Information Operations Directorate (IOD), Naval Network Warfare Command, on October 1, 2005. Three Naval Computer and Telecommunications Area Master Stations NCTAMS LANT Norfolk VA, NCTAMS MED Naples It, and NCTAMS PAC Honolulu HI Naval Computer and Telecommunications Station (NCTS) Guam Director, Communications Security Material System (DCMS) Headquarters, Navy-Marine Corps MARS Radio Station Naval Electromagnetic Spectrum Center Later additions: Navy Global Network Operations and Security Center (NAVGNOSC) at Little Creek, VA. Navy Satellite Operations Center (NAVSOC) at Dahlgren, VA. Maritime Integration Center (MIC) at NIOC Norfolk VA. Marine Cryptologic Support Battalion (MCSB), HQ at Ft. Meade, MD. ========================================================================================================= DCMS Washington DC The Director, Communications Security Material System (DCMS) was subordinate to the Commander, Naval Telecommunications Command (COMNAVTELCOM), which was renamed the Naval Computer and Telecommunications Command (NAVCOMTELCOM). On July 9, 2001, NAVCOMTELCOM was renamed the Naval Network Operations Command (COMNAVNETOPSCOM) (NNOC). COMNAVNETOPSCOM was disestablished on May 1, 2002; when the NAVNETWARCOM command was formed. On May 1, 2002, the Naval Network Warfare Command (NAVNETWARCOM) was established and DCMS Washington DC became subordinate to NAVNETWARCOM. On May 1, 2006, DCMS Washington DC moved from the Naval District Washington's Nebraska Avenue Complex in Northwest Washington DC to Andrews Air Force Base, in Clinton, MD. Also on May 1, 2006, the command's name was changed from DCMS Washington DC (Director, Communications Security Material System) to NCMS Washington DC (Naval Communications Security Material System). ========================================================================================================= Navy Component Task Force, Computer Network Defense (NCTF CND), Washington, DC On May 1, 2002, the Naval Network Warfare Command (NAVNETWARCOM) was established and the Navy Component Task Force, Computer Network Defense (NCTF CND) located in Washington DC, became subordinate to NAVNETWARCOM. In ??? ????, the NCTF CND moved from the Naval District Washington's Nebraska Avenue Complex in Northwest Washington DC to the Naval Amphibious Base at Little Creek, in Norfolk, VA. In July, 2002, NCTF CND became part of the Navy Computer Incident Response Team (NAVCIRT) Little Creek, Norfolk, VA. In June, 2006, NAVCIRT was renamed the Navy Cyber Defense Operations Command (NCDOC) Little Creek, Norfolk, VA. The Navy Cyber Defense Operations Command reports to the NNWC's NetOps Information Operations and Space Center (NIOSC). NCDOC Little Creek, Norfolk VA: https://www.ncdoc.navy.mil/ ========================================================================================================= Fleet Information Warfare Center (FIWC), NAB Little Creek, Norfolk, VA The Fleet Information Warfare Center (FIWC), located at Little Creek Amphibious Base, Norfolk, VA, became operational on October 1, 1995. In July 2002, FIWC was subordinated to the Naval Network Warfare Command. On November 5, 2005, FIWC Norfolk VA and NSGA Norfolk VA merged to become the Navy Information Operations Command (NIOC) Norfolk VA. NIOC Norfolk is responsible to provide Computer Incident Response, Vulnerability Analysis and Assistance, and Incident Measurement protection services to fleet and shore establishments. The Center provides the facilities, equipment, and personnel for directing the defensive information warfare program, including detecting and responding to computer attacks. The Navy Information Operations Command (NIOC) Norfolk Maritime Integration Center (MIC) reports to the NNWC's NetOps Information Operations and Space Center (NIOSC). ========================================================================================================= COMNAVSECGRU Washington DC On July 27, 2005, the Fleet Information Warfare Center Detachment (FIWC Det) San Diego CA and the Naval Security Group Activity (NSGA) San Diego CA merged to become the Navy Information Operations Command (NIOC) San Diego, CA. On November 5, 2005, FIWC Norfolk VA and NSGA Norfolk VA merged to become NIOC Norfolk VA. The Naval Security Group Command was disestablished on September 30, 2005; and all functions and missions were transferred to the Naval Network Warfare Center (NNWC), located at Little Creek Naval Amphibious Base (NAB) in Norfolk, VA. The COMNAVSECGRU offices and personnel were reassigned as the Naval Network Warfare Command, Information Operations Directorate (IOD), Ft. Meade, MD on October 1, 2005. Also on September 30, 2005; Naval Information Warfare Activity (NIWA) Ft. Meade, MD stood down; and was renamed the Navy Information Operations Command (NIOC) Suitland MD. Simultaneously, the Naval Information Warfare Activity Detachment (NIWA Det) San Antonio TX was renamed the Navy Information Operations Detachment (NIOD) San Antonio TX. Also on September 30, 2005, all Naval Security Group Activity (NSGA's), Naval Security Group Detachments (NSG Det's) and Naval Security Group Support Detachments (NSG Supp Dets) worldwide stood down. NSGA's were renamed Navy Information Operations Commands (NIOC's) and NSG Dets and NSG SUPP Dets were renamed Navy Information Operations Detachments (NIOD's) on October 1, 2005. The NSGA's that became NIOCs included: NSGA/NIOC Bahrain, Manama, Bahrain; NSGA/NIOC Denver, Aurora, CO; NSGA/NIOC Ft. Gordon, GA; NSGA/NIOC Ft. Meade, MD; NSGA/NIOC Hawaii, Schofield Barracks, HI; NSGA/NIOC Medina, San Antonio, TX; NSGA/NIOC Menwith Hill, England UK; NSGA/NIOC Misawa, Japan; NSGA/NIOC Pensacola FL; NSGA/NIOC Sugar Grove, WV; NSGA/NIOC Whidbey Island, Oak Harbor, WA; and NSGA/NIOC Yokosuka, Japan. The NSG Det's that became NIODs included: NSG Det/NIOD Alice Springs, Australia; NSG Det/NIOD Brunswick ME; NSG Det/NIOD Digby, England UK; NSG Det/NIOD Griesheim, Germany (closed 30 Sep 06); NSG Det/NIOD Groton CT; NSG Det/NIOD Kaneohe Bay HI; NSG Det/NIOD Potomac, Washington DC (closed 30 Sep 06); NSG Det/NIOD Rota, Spain (closed 30 Sep 06); NSG Det/NIOD Seoul, South Korea; NSG Det/NIOD Souda Bay, Crete, Greece; and NSG Det/NIOD Yakima WA. NSG Det Diego Garcia, BIOT closed on September 30, 2005. The NSG Support Dets that became NIODs included: NSG Support Det/NIOD Anchorage, AK; NSG Support Det/NIOD Camp Smith, Pearl Harbor, HI.; NSG Support Det/NIOD Chesapeake, VA; NSG Support Det/NIOD Dam Neck VA; NSG Support Det/NIOD, Molesworth UK; and NSG Support Det/NIOD Norfolk VA. NETWARCOM IOD Ft. Meade MD: http://www.nnwc-ftmeade.navy.mil/. ========================================================================================================= Marine Cryptologic Support Battalion (MCSB) (formerly Marine Support Battalion) MCSB Headquarters Company, Ft. Meade, MD. MCSB Company A, Denver, Aurora, CO. MCSB Company B, Ft. Meade, MD MCSB Company D, Ft. Gordon, GA MCSB Company G, Menwith Hill UK MCSB Company H, San Antonio, TX MCSB Company I, Kunia, HI MCSB Company K, Marine Corps Detachment, Corry Station, Pensacola, FL MCSB Company L, Suitland, MD Marine Cryptologic Support Battalion (MCSB), Ft. Meade, MD: http://www.nnwc-ftmeade.navy.mil/marines/index.htm ========================================================================================================= Naval Network Warfare Command (COMNAVNETWARCOM/NNWC) Effective in June, 2008, NETWARCOM assumed Fleet Intelligence Type Commander (TYCOM) responsibilities, in addition to its Information Operations (IO), Networks and Space missions. NETWARCOM was also tasked to serve as the Fleet Advocate for Intelligence Surveillance and Reconnaissance (ISR) capabilities and readiness. This action responded to CNO Guidance Task 5.1.1, to "continue realignment of Naval Ingelligence at Echelon III into the existing NETWARCOM TYCOM. Fleet intelligence and ISR have proven very successful in multiple combat operations, in the last decade, and significant improvements in training and readiness have been achieved. However, the current organization and process for generating intelligence and ISR readiness is not coherent across all Navy Warfare areas, does not provide for adequate ISR acquisition risk assessment, and will not keep pace with the increasingly complex and dynamic potential threat environments of the future. Therefore, CNO directed significant changes in Naval Intelligence alignment, and assignment of intelligence TYCOM and Fleet ISR advocacy functions to NETWARCOM is a key part of this intelligence transformation. Generating and sustaining the world's best intelligence capability, fully integrated in all Navy warfare areas to win decisively across the fll spectrum of conflict, in any joint or coalition environment. While continuing to report to Commander, U.S. Fleet Forces Command; NETWARCOM assumed the additional missions of optimizing intelligence readiness across all Navy Warfare areas, and began serving as the Operations Forces Advocate in the development, integration and fielding of ISR systems. NETWARCOM assumed the lead for providing synchronized and integrated intelligence manpower, equipment and training to Fleet and Naval Component Commanders, Maritime Headquarters/Maritime Operating Centers (MHQ/MOC), and all Navy Type Commanmders. NETWARCOM was not given the task of being the conduit for current and operational intelligence to the Fleet, which remained with the purview of Combatant Commanders, and the Office of Naval Intelligence (ONI). However, NETWARCOM was assigned to directly engage OPNAV N2 to ensure capabilities and processes are in place to deliver the best current/operational intelligence to the Fleet. Source: CNO WASHINGTON DC 161250Z JUN 08 NAVADMIN 169/08 ========================================================================================================= Compiled by: Michael R. "MO" Morris, CTOCS, USN, Retired CTO SeaDogs WebSite Manager, CTO SeaDogs DataBase Manager, CTO SeaDogs Historian Waldorf, Maryland E-Mail: CTOCS_MO@hotmail.com ================================================================================== Visit the CTO SeaDogs Community WebSite at: http://groups.msn.com/CTOSeaDogs ==================================================================================