National Military Command Center

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Not to be confused with White House Situation Room, National Airborne Operations Center, the Alternate NMCC (Raven Rock bunker), or other U.S. continuity of government bunkers.


The National Military Command Center (NMCC)[1] is a Pentagon command and communications center for the National Command Authority (i.e., the President of the United States and the United States Secretary of Defense). Maintained by the Department of the Air Force as the "DoD Executive Agent" for NMCC logistical, budgetary, facility and systems support;[2] the NMCC operators are in the Joint Staff's J-3 (Operations) Directorate.[citation needed] "The NMCC is responsible for generating Emergency Action Messages (EAMs) to launch control centers, nuclear submarines, recon aircraft and battlefield commanders".[1]:{{{3}}}

Mission

The NMCC has three main missions. The primary task of the NMCC is to monitor worldwide events for the Joint Chiefs of Staff (JCS). The NMCC also has a crisis response component (e.g., response to the bombing of the USS Cole) and a strategic watch component (e.g., monitoring nuclear activity).

This center is not directly necessary to initiate a nuclear attack, but it essentially serves as a communications/operations center for nearby Washington, D.C., particularly with regard to maintaining the American end of the famous U.S.-Russia hotline (the so-called "red telephone"). It coordinated the response to events such as the September 11 attacks,[3][4] the attack on the USS Liberty,[5] and Payne Stewart's plane crash.[6] The NMCC is responsible for generating Emergency Action Messages (EAMs) to launch control centers, nuclear submarines, recon aircraft, and battlefield commanders worldwide.

Organization

The NMCC is operated by five teams on a rotating watch system. Each team typically has 17–20 personnel on duty performing a wide variety of functions including communications. Teams are led by a Deputy Director for Operations (DDO) and Assistant DDO, and are divided into five duty positions:[7]

  • Leadership (one DDO and one Assistant Deputy Director for Operations (ADDO))
  • Current Operations Section (two Senior Operations Officers (SOO) and one Current Operations Officer (COO))
  • Emergency Action Element (three Senior Emergency Actions Officers, EAO, EA NCO)
  • Surveillance (one Officer)
  • Supporting Sections (approximately 8–10 individuals)

The more than 300 people in the NMCC have responsibilities that are operational in nature. The NMCC is not funded by the Joint Staff, but by the Department of the Air Force which as DoD Executive Agent provides logistical, budgetary, facility and systems support to the NMCC.[8]

The JCS J-3 Command Systems Operations Division manages the operations of the J-3 information system facilities and maintains operational control of the Crisis Management Automated Data Processing System for the National Military Command Center.

Description

Lua error in package.lua at line 80: module 'strict' not found. The NMCC includes several war rooms, uses more than 300 operational personnel, and houses the United State's side of the 1963 Moscow–Washington hotline which links the Pentagon and the Kremlin. Data into the NMCC includes warning "on the size, origin, and targeting of an attack" (e.g., from the NORAD/NORTHCOM Command Center). The NMCC's Crisis Management Automated Data Processing Systems are under control of the J-3 Command Systems Operations Division.[citation needed]

History

World War II Pentagon construction allowed a central military installation for the Navy and War Departments to communicate with theater commands, and CONUS air defense was based on warning data compiled by local Aircraft Warning Corps information centers for processing GOC observations and radar tracks to coordinate ground-controlled interception (cf. Battle of Los Angeles). As requested by Gen. Spaatz, a fall 1947[verification needed] AAF "war room" was establishment in the Pentagon ("operational early in 1948").[9]:{{{3}}}:117 Strategic Air Command began using the telephonic Army Command and Administrative Net (ACAN) in 1946 until switching to the 1949 USAF AIRCOMNET "command teletype network" (the independent Strategic Operational Control System (SOCS) with telephones and teletype was "fully installed by 1 May 1950".)[9]:{{{3}}}:77

1950 Air Force Command Post

The Air Force Command Post (AFCP) was "hastily set up" on June 25, 1950, to replace the 1948 war room when the Korean War began.[9]:{{{3}}}:117 On the Pentagon's floor, the AFCP served "as a reception point for radio messages between [General] Vandenberg and his FEAF commanders during Air Staff after-duty hours."[10]:{{{3}}} After a direct telephone line was installed in mid-July 1950 between CONAC headquarters and the 26th Air Division HQ[where?] ("the beginning of the Air Force air raid warning system"); in August "President Truman had a direct telephone line installed between the Air Force Pentagon post and the White House."[10]:{{{3}}}

Moved to a "more permanent" Pentagon facility in early 1951, the 2nd AFCP location had "a communications center [and] war room, which prepared status displays" (an "Emergency Air Staff Actions Office [was] incorporated into the command post early in 1952").[9]:{{{3}}}:117 Alternate AFCP sites in 1951 were at Langley AFB (primary) and Maxwell AFB (secondary).[9]:{{{3}}}:119 Radar tracks from the 1952 Permanent System radar stations relayed to the Air Defense Command command center at Ent AFB, Colorado, would be assessed; and suspicion or confirmation of attack would be relayed to the AFCP and SAC headquarters. The "Pentagon would pass the warning to the President, the Secretary of Defense, and the JCS"; and the SOCS allowed "relay [of] their orders to the combat forces".[9]:{{{3}}}:119

1953 JCS Pentagon annex

At the Pentagon, an annex established c. 1952-3 by the Joint Chiefs of Staff was "operated by the Air Force as an adjunct to the AFCP"[9]:{{{3}}}:119 and received reports from Joint Coordination Centers in Buckinghamshire, England, and Pershing Heights, Tokyo.[9]:{{{3}}}:55 ADC built a new Ent AFB blockhouse in 1954 and "in August 1955 OSD approved the “automatic” activation of the [Raven Rock] AJCC on declaration of air defense warning or notice of surprise attack.[11]:{{{3}}}

1956 Raven Rock annex
In July 1956 in the Pennsylvania bunker, a joint "War Room Annex was established" and was operated by the Air Force.[11]:{{{3}}} In 1955 the National Security Council designated the AFCP as the "national air defense warning center",[12] and Raven Rock's scope "was broadened in April 1957 [for] activation prior to emergency if JCS thought it necessary."[11]:{{{3}}}

In 1957 NORAD collocated command center operations in the 1954 ADC blockhouse (later into the 1963 Chidlaw Building and in 1966, Cheyenne Mountain Complex). On July 1, 1958, the AFCP was connected to NORAD's Alert Network Number 1, as 1 of 29 transmit/receive stations[13] (a differing "worldwide telephone system" was complete "from national authorities to unified commanders" by December 1958.)[11]:{{{3}}} Starting in August 1959 "with USAF assistance [the] JCS set up its own Joint War Room (JWR)" at the Pentagon.[11]:{{{3}}} In September 1960 at the Offutt AFB nuclear bunkers the "installation of a SAC display warning system" included 3 consoles in the Offutt AFB nuclear bunkers[14]:{{{3}}}:218 (cf. 1958 Bare Mountain bunker.) On 20 October 1960, the JCS "instructed the Joint Staff to establish a Joint Alternate Command Element (JACE)" for rotating[specify] battle staffs to the AJCC for temporary duty.[11]

1960 Joint War Room

The Joint War Room (JWR) consoles became operational in November 1960 and on December 21,[11]:{{{3}}} the AFCP reverted to a USAF mission when its "joint and national responsibilities" ended.[15] The September 1960 Winter Study Group and the October 1960 WSEG Report 50 recommended "interlocking the various fixed command posts" into a "coupled command system" with mobile centers and a "bomb alarm system".[14]:{{{3}}}:232 The subsequent National Defense Communications Control Center (NDCCC) opened[where?] on March 6, 1961[16] as part of the National Communications System (NCS) framework "encompassing all federal assets"[17] including approximately "79 major relay stations scattered around the globe" (cf. the NORAD CMC's 427M NCS).[18]—the Final Report of the National Command and Control Task Force (Partridge Report) was completed on 14 November 1961.[19] After developmental cost overruns, "OSD in mid-1961 changed both the SAGE and SAC 465L programs to pre-battle systems [and instead] approved a Post-Attack Command Control System (PACCS) for SAC and a Backup Interceptor Control (BUIC) system for ADC and NORAD".[11]:{{{3}}} The Raven Rock JACE "was activated on 11 July 1961 under USAF Brig. Gen. Willard W. Smith [with the 5] staffs permanently stationed in Washington and an administrative section at Ft. Ritchie" (rotations began in October 1961),[11]:{{{3}}} and development of the USAF's "separate, austere Post-Attack Command and Control System (PACCS)" began in July 1961.[20]:{{{3}}}:306

1961 NCC Task Force

"The National Command and Control Task Force, headed by General Partridge, submitted its findings on 14 November 1961" (Partridge Report), which recommended "the Joint War Room become the National Military Command Center (NMCC)"—it was "to become the nerve center of a National Military Command System" with underground and mobile alternate command centers.[11]:{{{3}}}:15 An 8 March 1962 JCCDG plan for a Lua error in Module:Convert at line 272: attempt to index local 'cat' (a nil value). addition to the JWR was too expensive, and the group postponed NMCC planning until WWMCCS planning was completed (a concept was complete in late March.)[11]:{{{3}}}:15 On 2 June 1962 Secretary McNamara issued a memorandum directing that the NMCS be put into operation,[21] and a committee under the Director of the Office of Emergency Planning recommended on 11 June 1962 that the NMCS include civilian executive departments for emergencies.[11]:{{{3}}}:16 The JCS approved the NMCS plan on 19 June, and the Joint Command Control Requirements Group formed in June 1962 revised the plan which SECDEF approved in early July.[11]:{{{3}}} September refinements in the plan were approved by SECDEF on 17 October in DOD Directive S-5100.30, which conceived the WWMMCCS with five types of C2 systems with the NMCS to serve the President/SECDEF/JCS as the primary type of system and containing the NMCC, the ANMCC, 3 NEACP aircraft on 24-hour ground alert, 2 NECPA ships, "and interconnecting communications".[11]:{{{3}}}

1962 NMCC

The NMCC was begun in early 1962[22]:{{{3}}} (opened early October)[23] when the JCS area with the Joint War Room was expanded from ~7,000 sq ft (650 m2) to ~21,000 sq ft (2,000 m2) by 1965[20]:{{{3}}}:315 (the Pentagon's "Navy Flag Plot" coordinated the Cuban Missile Crisis blockade.)[20]:{{{3}}}:312 The NMCC was initially considered an "interim" location until the Deep Underground Command Center (DUCC) could be completed below the Pentagon (never built). In December 1963 "SAC accepted the first 465L elements and began to send a limited flow of [data] traffic through them."[11]:{{{3}}} The NMCC had "direct communications with MACV headquarters in Saigon" during the Vietnam War.[24]

1972 upgrade

The WWMCCS "ADP upgrade program" included 1972 computer installations (e.g., 2 COC "Data Net 355 computers")[18]:{{{3}}} and c. mid-1972, additional NMCC expansion enlarged it to ~30,000 sq ft (2,800 m2) and included the Joint Operational Reporting (JOPREP) system.[20]:{{{3}}}:317 In 1977, the NMCC was 1 of 6 initial sites of the WWMCCS Intercomputer Network (WIN) developed from a 1971-7 experimental program with testing and use by the JCS.[25]:{{{3}}} The Command Center Processing and Display System (CCPDS) replaced NMCC UNIVAC 1106 computers c. 1977 with "dedicated UNIVAC 1100/42 computers" for console and large screen displays.[25]:{{{3}}} By 1981 as part of the WWMCCS Information System (WIS), the NMCC received data "directly from the Satellite Early Warning System (SEWS) and directly from the PAVE PAWS sensor systems".[25]:{{{3}}}

The NMCC at (tbd side of the Pentagon) coordinated responses[specify] to the 2001 September 11 attacks[26] (AA Flt 77 struck the west side) and other events. By 2008, the NMCC had the NMCC Alert Center for intelligence fusion in the National Operations and Intelligence Watch Officer Network.[27]

In popular culture

See also

References

  1. ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ http://s3.amazonaws.com/911timeline/2002/cnn090402.html
  4. ↑ http://www.mcguire.af.mil/news/story_print.asp?id=123048097
  5. ↑ https://www.nsa.gov/public_info/declass/uss_liberty/nmccd.shtml
  6. ↑ http://www.historycommons.org/entity.jsp?entity=national_military_command_center
  7. ↑ http://media.nara.gov/9-11/MFR/t-0148-911MFR-00756.pdf
  8. ↑ http://dod-executiveagent.osd.mil/agentListView.aspx?ID=46
  9. ↑ 9.0 9.1 9.2 9.3 9.4 9.5 9.6 9.7 Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ 11.00 11.01 11.02 11.03 11.04 11.05 11.06 11.07 11.08 11.09 11.10 11.11 11.12 11.13 11.14 Lua error in package.lua at line 80: module 'strict' not found. (quotation from p. 18)
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found. (cited by Wainstein p. 119 footnote 14)
  13. ↑ Preface by Lua error in package.lua at line 80: module 'strict' not found. Directorate of Command History "ALERT NETWORK NUMBER 1 On 1 July 1958, a new Alert # 1 network was placed in operation (the old network was to remain in operation as a back-up until 1 August 1958). The new network connected NORAD on 1 July 1958 with 33 Stations that required air defense alert and warning information. This included such agencies as major commands, air divisions, regions, and the USAF Command Post. Only 29 of the stations operating on 1 July were both transmit and receive stations, the other four (TAC Headquarters, Sandia Base, ADCC (Blue Ridge Summit), and the Presidio at San Francisco) were receive-only stations. …the new system…gave NORAD the ability to tell which station received its alert messages and which did not. The new system also had two master stations -- NORAD and the ALCOP at Richards-Gebaur AFB. This feature permitted the ALCOP to continue operations of the network and carry on with the alert procedures should NORAD become a war casualty."
  14. ↑ 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found. (cited by Wainstein p. 119)
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found. (Cited by Chapter 2)
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ 18.0 18.1 Chapter 2: Defense Communications Agency and System p. 19[full citation needed]
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ 20.0 20.1 20.2 20.3 Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ 25.0 25.1 25.2 Lua error in package.lua at line 80: module 'strict' not found. (pdf p. 64)
  26. ↑ http://s3.amazonaws.com/911timeline/2002/cnn090402.html http://www.mcguire.af.mil/news/story_print.asp?id=123048097
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
External images
image icon floor plans & photos
image icon photos

Lua error in package.lua at line 80: module 'strict' not found.

Retrieved from "https://infogalactic.com/w/index.php?title=National_Military_Command_Center&oldid=2203238"