Semi-Automatic Ground Environment

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

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

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

Semi-Automatic Ground Environment
"Ground Environment of the CONUS
Air Defense Systems" (1953)[1]
"Electronic Air Defense Environment" (1950)[2]:{{{3}}}
military C3 human-computer interface
The 4-story SAGE blockhouses[where?] with 3.5 acres (1.4 ha) of floor space[3] "were hardened [for] overpressures of" 5 psi (34 kPa).[4]:{{{3}}}:264 A shorter adjoining building (left) had generators below the 4 intake/exhaust structures on the roof.[5]:{{{3}}}
Countries United States, Canada
Combat
CC-01:

Centers  CC-02:
CC-03:

CC-04:

CC-05:

CC-06:

CC-xx:

CC-yy:
NY (Hancock Field),
WI (Truax Field),
WA (McChord AFB)[6]:{{{3}}}, NY (Stewart AFB), CA (Hamilton AFB)**, MO (Richards-Gebaur AFB)*, ND Minot AFB*
AZ Luke AFB*
Project Office
Coordination
Design
Equip. contract
USAF Air Material Command
Western Electric[7]
System Development Corporation[7]
Burroughs Corporation
[7]
Operational 1958 June 26 — DC-01
1958 December 1 — DC-03
1959 (early) — CC-01
1966 April 1 — CC-05
AN/FSQ-7 IBM Military Products Division [8]:{{{3}}}
*Combat Center not completed since AN/FSQ-8 production was halted c. Nov 1958 when Super Combat Centers were planned[6]:{{{3}}}:26 with AN/FSQ-32s.
**CC-05 at Hamilton AFB, CA utilized a 3-string AN/GSA-51 computer system and was active from Apr 1/66 to Dec 31/69.

The Semi-Automatic Ground Environment (SAGE) was a system of large computers and associated networking equipment that coordinated data from many radar sites and processed it to produce a single unified image of the airspace over a wide area. SAGE directed and controlled the NORAD response to a Soviet air attack, operating in this role from the late 1950s into the 1980s. Its enormous computers and huge displays remain a part of cold war lore, and a common prop in movies such as Dr. Strangelove and Colossus.

The processing power behind SAGE was supplied by the largest computer ever built, the AN/FSQ-7. Each SAGE Direction Center (DC) housed an FSQ-7 which occupied an entire floor, approximately 22,000 square feet, of the massive concrete blockhouse, not including supporting equipment. The upper two floors contained offices, operator stations, and a single two-story radar display visible to most of the DC's personnel. Information was fed to the DC's from a network of radar stations as well as readiness information from various defence sites. The computers, based on the raw radar data, developed "tracks" for the reported targets, and automatically calculated which defences were within range. Subsets of the data were then sent to the many operator consoles, where the operators used light guns to select targets onscreen for further information, select one of the available defences, and issue commands to attack. These commands would then be automatically sent to the defence site via teleprinter. Later additions to the system allowed SAGE's tracking data to be sent directly to CIM-10 Bomarc missiles and some of the US Air Force's interceptor aircraft in-flight, directly updating their autopilots to maintain an intercept course without operator intervention. Each SAGE DC also forwarded data to a Combat Center (CC) for "supervision of the several sectors within the division"[9] ("each combat center [had] the capability to coordinate defense for the whole nation").[10]:51 Connecting the various sites was an enormous network of telephones, modems and teleprinters.

SAGE became operational in the late 1950s and early 1960s at a combined cost of billions of dollars. It was noted that the deployment cost more than the Manhattan Project, which it was, in a way, defending against. Throughout its development there were continual questions about its real ability to deal with large attacks, and several tests by Strategic Air Command bombers suggested the system was "leaky". Nevertheless, SAGE was the backbone of NORADs air defence system into the 1980s, by which time the tube-based FSQ-7's were increasingly costly to maintain and completely outdated. Today the same command and control task is carried out by microcomputers, based on the same basic underlying data.

The AN/FSQ-7 had 100 system consoles, including the OA-1008 Situation Display (SD) with a light gun (at end of cable under plastic museum cover), cigarette lighter, and ash tray (left of the light gun).

Background

Computerized command and control for United States air defense was conceived in July 1945 during the Signal Corps' Project 414A contracted to Bell Laboratories[11]:{{{3}}}:207 after "employment of an American version of CDS", the British air defense C2 system, had been identified for air defense command and control on June 12.[12]

The terms of the National Security Act were formulated during 1947, leading to the creation of the US Air Force out of the former US Army Air Force. During April of the same year, US Air Force staff were identifying specifically the requirement for the creation of automatic equipment for radar-detection which would relay information to an air defence control system, a system which would function without the inclusion of persons for its operation.[13] The December 1949 "Air Defense Systems Engineering Committee" led by Dr. George Valley had recommended computerized networking[14] for "radar stations guarding the northern air approaches to the United States"[15] (e.g., in Canada). After a January 1950 meeting, Valley and Jay Forrester proposed using the Whirlwind I (completed 1951) for air defense.[citation needed] On August 18, 1950, when the "1954 Interceptor" requirements were issued, the USAF "noted that manual techniques of aircraft warning and control would impose "intolerable" delays"[16]:484 (Air Material Command (AMC) published Electronic Air Defense Environment for 1954 in December .)[2] During February–August 1951 at the new Lincoln Laboratory, the USAF conducted Project Claude which concluded an improved air defense system was needed.[citation needed]

In a test for the U.S. military at Bedford, during the 20th of April 1951, data produced by radar monitoring was transmitted through telephone lines to a computer for the first time, showing the detection of a mock enemy aircraft. This indicated the likelihood of possible future technology being produced capable of detecting and directing U.S. fighter planes to defend the security of the U.S.A. in the air, through the creation of an air-borne attack defence system. This first test was directed by C. Robert Wieser.[13]

The "Summer Study Group" of scientists in 1952 recommended "computerized air direction centers…to be ready by 1954."[17]

IBM's "Project High" assisted under their October 1952 Whirlwind subcontract with Lincoln Laboratory,[18]:{{{3}}}:210 and a 1952 USAF Project Lincoln "fullscale study" of "a large scale integrated ground control system" resulted in the SAGE approval "first on a trial basis in 1953".[11]:{{{3}}}:128 The USAF had decided by April 10, 1953, to cancel the competing ADIS (based on CDS), and the University of Michigan’s Aeronautical Research Center withdrew in the spring.[19]:{{{3}}}:289 Air Research and Development Command (ARDC) planned to "finalize a production contract for the Lincoln Transition System".[4]:{{{3}}}:201 Similarly, the July 22, 1953, report by the Bull Committee (NSC 159) identified completing the Mid-Canada Line radars as the top priority and "on a second-priority-basis: the Lincoln automated system"[20] (the decision to control Bomarc with the automated system was also in 1953.)[21]

The Priority Permanent System with the initial (priority) radar stations was completed in 1952[4]:{{{3}}}:223 as a "manual air defense system"[7] (e.g., NORAD/ADC used a "Plexiglas plotting board" at the Ent command center.) The Permanent System radar stations included 3 subsequent phases of deployments and by June 30, 1957, had 119 "Fixed CONUS" radars, 29 "Gap-filler low altitude" radars, and 23 control centers".[22]:{{{3}}} At "the end of 1957, ADC operated 182 radar stations [and] 17 control centers … 32 [stations] had been added during the last half of the year as low-altitude, unmanned gap-filler radars. The total consisted of 47 gap-filler stations, 75 Permanent System radars, 39 semimobile radars, 19 Pinetree stations,…1 Lashup -era radar and a single Texas Tower".[4]:{{{3}}}:223 "On 31 December 1958, USAF ADC had 187 operational land-based radar stations" (74 were "P-sites", 29 "M-sites", 13 "SM-sites", & 68 "ZI Gap Fillers").[6]:{{{3}}}

Development

Jay Forrester was instrumental in directing the development of the key concept of an interception system during his work at Servomechanisms Laboratory of MIT. The concept of the system, according to the Lincoln Laboratory site was to:[23]

<templatestyles src="Template:Blockquote/styles.css" />

develop a digital computer that could receive vast quantities of data from multiple radars and perform real-time processing to produce targeting information for intercepting aircraft and missiles

The AN/FSQ-7 was developed by MIT's Digital Computer Laboratory and Division 6 working closely with IBM as the manufacturer. Each FSQ-7 actually consisted of two nearly identical computers operating in "duplex"[24] for redundancy. The design used an improved version of the Whirlwind I magnetic core memory and was an extension of the Whirlwind II computer program, renamed AN/FSQ-7 in 1953 to comply with Air Force nomenclature. It has been suggested the FSQ-7 was based on the IBM 701 but, while the 701 was investigated by MIT engineers, its design was ultimately rejected due to high error rates and generally being "inadequate to the task."[25] IBM's contributions were essential to the success of the FSQ-7 but IBM benefited immensely from its association with the SAGE project, most evidently during development of the IBM 704.[26] [27]

On October 28, 1953, the Air Force Council recommended 1955 funding for "ADC to convert to the Lincoln automated system"[4]:{{{3}}}:193 ("redesignated the SAGE System in 1954").[4]:{{{3}}}:201 The "experimental SAGE subsector, located in Lexington, Mass., was completed in 1955…with a prototype AN/FSQ-7…known as XD-1"[9] (single computer system[28]:{{{3}}} in Building F).[19]:{{{3}}} In 1955, Air Force personnel began IBM training at the Kingston, New York, prototype facility,[5]:{{{3}}} and the "4620th Air Defense Wing (experimental SAGE) was established at Lincoln Laboratory"

On May 3, 1956, General Partridge presented CINCNORAD’s Operational Concept for Control of Air Defense Weapons to the Armed Forces Policy Council,[11]:{{{3}}} and a June 1956 symposium presentation identified advanced programming methods of SAGE code.[29] For SAGE consulting Western Electric and Bell Telephone Laboratories formed the Air Defense Engineering Service (ADES),[30] which was contracted in January 1954.[19]:{{{3}}} IBM delivered the FSQ-7 computer's prototype in June 1956,[8] and Kingston's XD-2 with dual computers[28]:{{{3}}} guided a Cape Canaveral BOMARC to a successful aircraft intercept on August 7, 1958.[4]:{{{3}}}:197 Initially contracted to RCA, the AN/FSQ-7 production units were started by IBM in 1958[citation needed] (32 DCs were planned[4]:{{{3}}}:207 for networking NORAD regions.)[31] IBM's production contract developed 56 SAGE computers for $½ billion (~$18 million per computer pair in each FSQ-7)[28]:{{{3}}}cf. the $2 billion WWII Manhattan Project.

General Operational Requirements (GOR) 79 and 97 were "the basic USAF documents guiding development and improvement of [the semi-automatic] ground environment.[32]:{{{3}}}:97 Prior to fielding the AN/FSQ-7 centrals, the USAF initially deployed "pre-SAGE semiautomatic intercept systems" (AN/GPA-37) to Air Defense Direction Centers, ADDCs[32]:{{{3}}}:11 (e.g., at "NORAD Control Centers").[6]:{{{3}}} On April 22, 1958, NORAD approved Nike AADCPs to be collocated with the USAF manual ADDCs at Duncanville Air Force Station TX, Olathe Air Force Station KS, Belleville Air Force Station IL, and Osceola Air Force Station KS.[6]:{{{3}}}

File:SAGE CC-1 Hancock Field New York.jpg
Subsector Command Post of SAGE Combat Center at Syracuse Air Force Station with consoles and large display, which was projected from above. Archive photo taken during equipment installation.

Deployment

In 1957, SAGE System groundbreaking at McChord AFB was for DC-12[33] where the "electronic brain" began arriving in November 1958,[34] and the "first SAGE regional battle post [CC-01] began operating in Syracuse, New York in early 1959".[4]:{{{3}}}:263 BOMARC "crew training was activated January 1, 1958",[35]:{{{3}}} and AT&T "hardened many of its switching centers, putting them in deep underground bunkers",[36] The North American Defense Objectives Plan (NADOP 59-63) submitted to Canada in December 1958 scheduled 5 Direction Centers and 1 Combat Center to be complete in Fiscal Year 1959, 12 DCs and 3 CCs complete at the end of FY 60, 19 DC/4 CC FY 61, 25/6 FY 62, and 30/10 FY 63.[6]:{{{3}}} On June 30 NORAD ordered that "Air Defense Sectors (SAGE) were to be designated as NORAD sectors",[37] (the military reorganization had begun when effective April 1, 1958, CONAD "designated four SAGE sectors -- New York, Boston, Syracuse, and Washington -- as CONAD Sectors".)[32]:{{{3}}}:7

SAGE Geographic Reorganization: The SAGE Geographic Reorganization Plan of July 25, 1958, by NORAD was "to provide a means for the orderly transition and phasing from the manual to the SAGE system." The plan identified deactivation of the Eastern, Central, and Western Region/Defense Forces on July 1, 1960, and "current manual boundaries" were to be moved to the new "eight SAGE divisions" (1 in Canada, "the 35th") as soon as possible. Manual divisions "not to get SAGE computers were to be phased out" along with their Manual Air Defense Control Centers at the headquarters base: "9th [at] Geiger Field… 32d, Syracuse AFS… 35th, Dobbins AFB… 58th, Wright-Patterson AFB… 85th, Andrews AFB".[6]:{{{3}}} The 26th SAGE Division (New York, Boston, Syracuse & Bangor SAGE sectors)--the 1st of the SAGE divisions—became operational at Hancock Field on 1 January 1959[6]:{{{3}}} after the redesignation started for AC&W Squadrons (e.g., the Highlands P-9 unit became the 646th Radar Squadron (SAGE) October 1.)[38]:{{{3}}}:156 Additional sectors included the Los Angeles Air Defense Sector (SAGE) designated in February 1959. A June 23 JCS memorandum approved the new "March 1959 Reorganization Plan" for HQ NORAD/CONAD/ADC.[39]:{{{3}}}:5

Project Wild Goose teams of Air Material Command personnel installed c. 1960 the Ground Air Transmit Receive stations for the SAGE TDDL (in April 1961, Sault Ste Marie was the first operational sector with TDDL.)[40] … By the middle of 1960, AMC had determined that about 800,000 manhours (involving 130 changes) would be required to bring the F-106 fleet to the point where it would be a valuable adjunct to the air defense system. Part of the work (Project Broad Jump) was accomplished by Sacramento Air Materiel Area. The remainder (Project Wild Goose) was done at ADC bases by roving AMC field assistance teams supported by ADC maintenance personnel. (cited by Volume I p. 271 & Schaffel p. 325) After a September 1959 experimental ATABE test between an "abbreviated" AN/FSQ-7 staged at Fort Banks and the Lexington XD-1, the 1961 "SAGE/Missile Master test program" conducted large-scale field testing of the ATABE "mathematical model" using radar tracks of actual SAC and ADC aircraft flying mock penetrations into defense sectors.[41] Similarly conducted was the joint SAC-NORAD Sky Shield II exercise followed by Sky Shield III on 2 September 1962[42] On July 15, 1963, ESD's CMC Management Office assumed "responsibilities in connection with BMEWS, Space Track, SAGE, and BUIC."[43]:{{{3}}} The Chidlaw Building's computerized[specify] NORAD/ADC Combined Operations Center in 1963 became the highest echelon of the SAGE computer network when operations moved from Ent AFB's 1954 manual Command Center to the partially underground[43]:{{{3}}} "war room".[44] Also in 1963, radar stations were renumbered (e.g., Cambria AFS was redesignated from P-2 to Z-2 on July 31) and the vacuum-tube SAGE System was completed (and obsolete).[45]:{{{3}}}:9

On "June 26, 1958,…the New York sector became operational"[4]:{{{3}}}:207 and on December 1, 1958, the Syracuse sector's DC-03 was operational ("the SAGE system [did not] become operational until January 1959.")[22]:{{{3}}} Construction of CFB North Bay in Canada was started in 1959 for a bunker ~700 feet (210 m) underground (operational October 1, 1963),[46] and by 1963 the system had 3 Combat Centers. The 23 SAGE centers included 1 in Canada,[47] and the "SAGE control centers reached their full 22 site deployments in 1961 (out of 46 originally planned)."[48] The completed Minot AFB blockhouse never received an AN/FSQ-7 (the April 1, 1959, Minot Air Defense Sector consolidated with the Grand Forks ADS on March 1, 1963).[citation needed]

The Subsector Command Post ("blue room") had personnel on the DC's 3rd floor and a Display and Warning Light System for the operator environment, e.g., Large Board Projection Equipment projecting from the 4th floor[5]:{{{3}}} (top, Cape Cod shown on 3rd/4th floor wall)[where?] and Command Post Digital Display Desk[49] (center, with operators)

Description

The environment allowed radar station personnel to monitor the radar data and systems' status (e.g., Arctic Tower radome pressure) and to use the range height equipment to process height requests from Direction Center (DC) personnel. DCs received the Long Range Radar Input from the sector's radar stations, and DC personnel monitored the radar tracks and IFF data provided by the stations, requested height-finder radar data on targets, and monitored the computer's evaluation of which fighter aircraft or Bomarc missile site could reach the threat first. The DC's "NORAD sector commander's operational staff"[50]:{{{3}}} could designate fighter intercept of a target or, using the Senior Director's keyed console[51]:{{{3}}} in the Weapons Direction room,[5]:{{{3}}} launch a Bomarc intercept with automatic Q-7 guidance of the surface-to-air missile to a final homing dive (equipped fighters eventually were automatically guided to intercepts).

The "NORAD sector direction center (NSDC) [also had] air defense artillery director (ADAD) consoles [and an Army] ADA battle staff officer", and the NSDC automatically communicated crosstelling of "SAGE reference track data" to/from adjacent sectors' DCs and to 10 Nike Missile Master AADCPs.[50]:{{{3}}} Forwardtelling automatically communicated data from multiple DCs to a 3-story Combat Center (CC) usually at one of the sector's DCs[9]:{{{3}}} (cf. planned Hamilton AFB CC-05 near the Beale AFB DC-18) for coordinating the air battle in the NORAD region (multiple sectors) and which forwarded data to the NORAD Command Center (Ent AFB, 1963 Chidlaw Building, & 1966 Cheyenne Mountain). NORAD's integration of air warning data (at the ADOC) along with space surveillance, intelligence, and other data allowed attack assessment of an Air Defense Emergency for alerting the SAC command centers (465L SACCS nodes at Offutt AFB & The Notch), The Pentagon/Raven Rock NMCC/ANMCC, and the public via CONELRAD radio stations.

SAGE System

The Burroughs 416L SAGE System (ESD Project 416L,[52]:{{{3}}} Semi Automatic Ground Environment System)[43]:{{{3}}} was the Cold War network of computer sets and centrals that created the display and control environment (SAGE) for operation of the separate radars[52]:{{{3}}} and to provide command guidance for ground-controlled interception by air defense aircraft in the "SAGE Defense System"[53] ("Air Defense Weapons System").[35] Burroughs Corporation was the prime contractor for SAGE electronic equipment which included 134 Burroughs AN/FST-2 Coordinate Data Transmitting Sets (CDTS) at radar stations and other sites, the AN/FSQ-7 Combat Direction Central at 23 Direction Centers, and the AN/FSQ-8 Combat Control Central at 8 Combat Centers. The 2 computers of each AN/FSQ-7 together weighing 275 short tons-force (2,450 kN)[54][this quote needs a citation] used about ⅓ of the DC's 2nd floor space[5]:{{{3}}} and at ~$50 per instruction had approximately 125,000 "computer instructions support[ing] actual operational air-defense mission" processing.[55] The AN/FSQ-7 at Luke AFB had additional memory (32K total) and was used as a "computer center for all other" DCs.[56] Project 416L was the USAF predecessor of NORAD, SAC, and other military organizations' "Big L" computer systems (e.g., 438L Air Force Intelligence Data Handling System & 496L Space Detection and Tracking System).[57]

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

The SAGE network of computers connected by a "Digital Radar Relay"[58]:{{{3}}} (SAGE data system)[59] used AT&T voice lines, microwave towers, switching centers (e.g., SAGE NNX 764 was at Delta, Utah[60] & 759 at Mounds, Oklahoma[61]), etc.; and AT&T's "main underground station" was in Kansas (Fairview) with other bunkers in Connecticut (Cheshire), California (Santa Rosa), Iowa (Boone)[62] and Maryland (Hearthstone Mountain). CDTS modems at automated radar stations transmitted range and azimuth,[63] and the Air Movements Identification Service (AMIS) provided air traffic data to the SAGE System.[64] Radar tracks by telephone calls (e.g., from Manual Control Centers in the Albuquerque, Minot, and Oklahoma City sectors) could be entered via consoles of the 4th floor "Manual Inputs" room adjacent to the "Communication Recording-Monitoring and VHF" room.[65] In 1966, SAGE communications were integrated into the AUTOVON Network.[61]:{{{3}}}

SAGE Sector Warning Networks (cf. NORAD Division Warning Networks) provided the radar netting communications for each DC[6]:{{{3}}} and eventually also allowed transfer of command guidance to autopilots of TDDL-equipped interceptors for vectoring to targets[38] via the Ground to Air Data Link Subsystem and the Ground Air Transmit Receive (GATR) network of radio sites for "HF/VHF/UHF voice & TDDL"[60]:{{{3}}} each generally co-located at a CDTS site. SAGE Direction Centers and Combat Centers were also nodes of NORAD's Alert Network Number 1, and SAC Emergency War Order Traffic[66]:{{{3}}} included "Positive Control/Noah's Ark instructions" through northern NORAD radio sites to confirm or recall SAC bombers if "SAC decided to launch the alert force before receiving an execution order from the JCS".[6]:{{{3}}}

A SAGE System ergonomic test at Luke AFB in 1964 "showed conclusively that the wrong timing of human and technical operations was leading to frequent truncation of the flight path tracking system" (Harold Sackman).[45]:9 SAGE software development was "grossly underestimated"[19]:{{{3}}}:370 (60,000 lines in September 1955):[67] "the biggest mistake [of] the SAGE computer program was [underestimating the] jump from the 35,000 [WWI] instructions … to the more than 100,000 instructions on the" AN/FSQ-8.[68] NORAD conducted a Sage/Missile Master Integration/ECM-ECCM Test in 1963,[69] and although SAGE used AMIS input of air traffic information, the 1959 plan developed by the July 1958 USAF Air Defense Systems Integration Division[6]:{{{3}}} for SAGE Air Traffic Integration (SATIN) was cancelled by the DoD.[70]

Radar stations

SAGE radar stations, including 78 DEW Line sites in December 1961,[71] provided radar tracks to DCs and had frequency diversity (FD) radars[72] United States Navy picket ships also provided radar tracks, and seaward radar coverage was provided. By the late 1960s EC-121 Warning Star aircraft based at Otis AFB MA and McClellan AFB CA provided radar tracks via automatic data link to the SAGE System.[4]:{{{3}}} Civil Aeronautics Administration radars were at some stations (e.g., stations of the Joint Use Site System), and the ARSR-1 Air Route Surveillance Radar rotation rate had to be modified "for SAGE [IFF/SIF] Modes III and IV" ("antenna gear box modification" for compatibility with FSQ-7 & FSG-1 centrals.)[32]:{{{3}}}:21

Interceptors

ADC aircraft such as the F-94 Starfire, F-89 Scorpion, F-101B Voodoo, and F-4 Phantom were controlled by SAGE GCI. The F-104 Starfighter was "too small to be equipped with [SAGE] data link equipment" and used voice-commanded GCI,[4]:{{{3}}}:229 but the F-106 Delta Dart was equipped for the automated data link (ADL).[citation needed] The ADL was designed to allow Interceptors that reached targets to transmit real-time tactical friendly and enemy movements and to determine whether sector defence reinforcement was necessary.[23]

Familiarization flights allowed SAGE weapons directors to fly on two-seat interceptors to observe GCI operations.[citation needed] Surface-to-air missile installations for CIM-10 Bomarc interceptors were displayed on SAGE consoles.[73]

Improvements

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

Partially solid-state AN/FST-2B and later AN/FYQ-47 computers replaced the AN/FST-2,[63]:{{{3}}} and sectors without AN/FSQ-7 centrals requiring a "weapon direction control device" for USAF air defense used the solid-state AN/GSG-5 CCCS instead of the AN/GPA-73 recommended by ADC in June 1958. Back-Up Interceptor Control (BUIC)[6]:{{{3}}} with CCCS dispersed to radar stations for survivability allowed a diminished but functional SAGE capability. In 1962, Burroughs "won the contract to provide a military version of its D825" modular data processing system[51]:{{{3}}} for BUIC II.[10]:{{{3}}} BUIC II was 1st used at North Truro Z-10 in 1966,[10]:{{{3}}} and the Hamilton AFB BUIC II was installed in the former MCC building when it was converted to a SAGE Combat Center in 1966 (CC-05).[74] On June 3, 1963, the Direction Centers at Marysville CA, Marquette/K I Sawyer AFB (DC-14) MI,[specify] Stewart AFB NY (DC-02), and Moses Lake WA (DC-15) were planned for closing[46]:{{{3}}} and at the end of 1969, only 6 CONUS SAGE DCs remained (DC-03, -04, -10, -12, -20, & -21) all with the vacuum tube AN/FSQ-7 centrals.[10]:{{{3}}}:47 In 1966, NORAD Combined Operations Center operations at Chidlaw transferred to the Cheyenne Mountain Operations Center (425L System) and in December 1963, the DoD approved solid state replacement of Martin AN/FSG-1 centrals[75]:317 with the AN/GSG-5 and subsequent Hughes AN/TSQ-51. The "416L/M/N Program Office" at Hanscom Field[52] had deployed the BUIC III by 1971 (e.g., to Fallon NAS),[76] and the initial BUIC systems were phased out 1974-5.[51]:{{{3}}} ADC had been renamed Aerospace Defense Command on January 15, 1968,[77] and its general surveillance radar stations transferred to ADTAC in 1979 when the ADC major command was broken up (space surveillance stations went to SAC and the Aerospace Defense Center was activated as a DRU.)

Replacement and disposition

Science fiction author Larry Niven admiring a SAGE console at the Computer History Museum in 2007

For airborne command posts, "as early as 1962 the Air Force began exploring possibilites for an Airborne Warning and Control System (AWACS)",[4]:{{{3}}}:266 and the Strategic Defense Architecture (SDA-2000) planned an integrated air defense and air traffic control network. The USAF declared full operational capability of the 1st 7 Joint Surveillance System ROCCs on December 23, 1980,[43]:{{{3}}} with Hughes AN/FYQ-93 systems,[78] and many of the SAGE radar stations became Joint Surveillance System (JSS) sites (e.g., San Pedro Hill Z-39 became FAA Ground Equipment Facility J-31.) The North Bay AN/FSQ-7 was dismantled and sent to Boston's Computer Museum.[citation needed] In 1996, AN/FSQ-7 components were moved to Moffett Federal Airfield for storage and later moved[when?] to the Computer History Museum in Mountain View, California. The last AN/FSQ-7 centrals were demolished at McChord AFB (August 1983) and Luke AFB (February 1984).[51]:{{{3}}} AN/FSQ-7 equipment was used as TV/movie props (e.g., in Time Tunnel and Voyage to the Bottom of the Sea).

Historiography

SAGE histories include a 1983 special issue of the Annals of the History of Computing,[79]:{{{3}}} and various personal histories were published, e.g., Valley in 1985[80] and Jacobs in 1986.[81] In 1998, the SAGE System was identified as 1 of 4 "Monumental Projects",[82] and a SAGE lecture presented the vintage film In Your Defense followed by anecdotal information from Les Earnest, Jim Wong, and Paul Edwards.[28]:{{{3}}} In 2013, a copy of a 1950s cover girl image programmed for SAGE display was identified as the "earliest known figurative computer art".[5]:{{{3}}} Company histories identifying employees' roles in SAGE include the 1981 System Builders: The Story of SDC[83] and the 1998 Architects of Information Advantage: The MITRE Corporation Since 1958.[84]

Direction Centers

1963 SAGE Direction Centers
Sector DC # and site AFB, etc. ST Blockhouse use
New York DC-01   Lua error in package.lua at line 80: module 'strict' not found. McGuire NJ [specify]
Boston DC-02   Lua error in package.lua at line 80: module 'strict' not found. Stewart NY
Syracuse DC-03   Lua error in package.lua at line 80: module 'strict' not found. Hancock Field NY
Washington DC-04   Lua error in package.lua at line 80: module 'strict' not found. Fort Lee AFS VA
Bangor DC-05   Lua error in package.lua at line 80: module 'strict' not found. Topsham AFS ME demolished 1985[85]
Detroit DC-06   Lua error in package.lua at line 80: module 'strict' not found. Fort Custer MI
Chicago DC-07   Lua error in package.lua at line 80: module 'strict' not found. Truax Field WI In use as of 2014 as Covance labs[86]
Kansas City DC-08   Lua error in package.lua at line 80: module 'strict' not found. Richards-Gebaur MO
Montgomery DC-09   Lua error in package.lua at line 80: module 'strict' not found. Gunter AL
Duluth DC-10   Lua error in package.lua at line 80: module 'strict' not found. Duluth IAP MN
Grand Forks DC-11   Lua error in package.lua at line 80: module 'strict' not found. Grand Forks ND demolished
Seattle DC-12   Lua error in package.lua at line 80: module 'strict' not found. McChord WA
Portland DC-13   Lua error in package.lua at line 80: module 'strict' not found. Adair AFS OR
Sault Ste Marie DC-14   Lua error in package.lua at line 80: module 'strict' not found. K. I. Sawyer MI
Spokane DC-15   Lua error in package.lua at line 80: module 'strict' not found. Larson WA
Los Angeles DC-16   Lua error in package.lua at line 80: module 'strict' not found. Norton CA abandoned
Reno DC-17   Lua error in package.lua at line 80: module 'strict' not found. Stead NV
San Francisco DC-18   Lua error in package.lua at line 80: module 'strict' not found. Beale CA
Minot DC-19[87] (not completed)
[specify]     
Minot ND
Great Falls DC-20   Lua error in package.lua at line 80: module 'strict' not found. Malmstrom MT
Phoenix DC-21   Lua error in package.lua at line 80: module 'strict' not found. Luke AZ
Sioux City DC-22**   Lua error in package.lua at line 80: module 'strict' not found. Sioux City AFS IA
DC-23*[specify]
DC-30* [specify]
Goose
Flag of Canada.svg
DC-31   Lua error in package.lua at line 80: module 'strict' not found. CFB North Bay ON
DC-32* [specify]
*Some of the originally planned 32 DCs were never completed, e.g., Minot's blockhouse never had a Q-7,
and DCs were planned at installations for additional sectors: Calypso/Raleigh NC, England/
Shreveport LA, Fort Knox KY, Kirtland/Albuquerque NM, Robins/Miami, Scott/St. Louis, Webb/San Antonio TX.
*The DC-22 AN/FSQ-7 was an AN/FSQ-8 that was retrofitted to have the LRI, GFI, and other components/software specific to the Q-7.[6]:{{{3}}}
External media
Images
image icon XD-1 consoles
image icon Situation Display with SAM sites "FOX"[specify] & ""BED"
image icon SAGE PPI with entire East Coast
image icon operator with light gun
image icon room diagrams for each DC floor
image icon combined CC/DC at Syracuse (p. 265)
image icon 2002 DC-12 photo (McChord/Seattle)
image icon 1968 CC-05 Combat Center interior photos (Hamilton AFB, CA)
Video
video icon On Guard: The Story of SAGE on YouTube (1956)[8]:{{{3}}}
video icon In Your Defense on YouTube

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found. (cited by Schaffel p. 202/311, which has "Smith sent... a list of... requirements needed before the Lincoln system could be deployed [by] 1955 [including] filling gaps in radar coverage below 5,000 feet and identifying friend from foe more quickly and reliably.")
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. The SAGE Blockhouse - Future Home of the Cold War / Peace Museum. Coldwarpeacemuseum.org. Retrieved on 2013-09-18.
  4. 4.00 4.01 4.02 4.03 4.04 4.05 4.06 4.07 4.08 4.09 4.10 4.11 4.12 Lua error in package.lua at line 80: module 'strict' not found. [captions of p. 198, 208, & 265 photos] NOTE: Schaffel's history uses the same name as "The Emerging Shield: The Air Defense Ground Environment," Air University Quarterly Review 8, no. 2 (spring 1956).
  5. 5.0 5.1 5.2 5.3 5.4 5.5 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.00 6.01 6.02 6.03 6.04 6.05 6.06 6.07 6.08 6.09 6.10 6.11 6.12 Preface by Lua error in package.lua at line 80: module 'strict' not found. "USAF also set down a new schedule (see table preceding). This schedule was to be included in an entirely new SAGE schedule (Schedule A) to be prepared by the SAGE Project Office. The phasing was to be as follows. The last combat center, AN/FSQ-8, to be installed under SAGE Schedule 7 (Improved), was to be at McChord AFB (25th Air Division). Subsequent combat facilities and equipment were to be cancelled with the exception of (1) one AN/FSQ-8 that was to be converted to an AN/FSQ-7, using FY 1959 funds, to be installed at the Sioux City DC, and (2) the combat center building at Minot." (improved) On April 1, 1966, Combat Center CC-03 at McChord AFB, WA was inactivated in conjunction with the activation of Combat Center CC-05 at Hamilton AFB, CA, and the combining of 25th, 26th and 27th NORAD divisions into the new Headquarters Western NORAD Region at HAFB. CC-05 utilized a 3-String AN/GSA-51 computer system. CC-05 and Headquarters Western NORAD Region were inactivated at Hamilton AFB on December 31, 1969.
  7. 7.0 7.1 7.2 7.3 Lua error in package.lua at line 80: module 'strict' not found.[when?]
  8. 8.0 8.1 8.2 Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 9.2 Lua error in package.lua at line 80: module 'strict' not found. (p. 7)
  10. 10.0 10.1 10.2 10.3 Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 11.2 Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found. (cited by Schaffel pdf p. 311)
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.(20th of April 1951 - p.1, National Security Act 1947 - p.12, April 1947 - p.13)
  14. Lua error in package.lua at line 80: module 'strict' not found. (cited by Schaffel p. 197)
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found. (cited by Volume I p. 187)
  17. Lua error in package.lua at line 80: module 'strict' not found. (citation 29 of Volume I, p. 25)
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 19.2 19.3 Lua error in package.lua at line 80: module 'strict' not found. (The Redmond & Smith citation for the operation plan identifies the date)
  20. quote from Schaffel p. 191; Condit p. 259 footnote 1 cites: "CCS 381 US (5-23-46) sec 37."
  21. Lua error in package.lua at line 80: module 'strict' not found. (cited by Volume I p. 108 footnote 69: "Before the end of 1953, it was also decided that the Sage system being developed by Lincoln Laboratories would be used to control the Bomarc.69")
  22. 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found. (Condit includes detailed numbers of 1954, 1956, and 1957 radar stations on p. 269 Table 13.)
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.(this source was also referenced at a time earlier than 2015-08-05, for info: ...ADL... - Interceptors)
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. 28.0 28.1 28.2 28.3 Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found. (cited by Schaffel p. 207/312)
  31. Lua error in package.lua at line 80: module 'strict' not found. (cited by Schaffel pp. 311, 332)
  32. 32.0 32.1 32.2 32.3 Preface by Lua error in package.lua at line 80: module 'strict' not found. Directorate of Command History: Office of Information Services; p. 21: "DC's, and CC's, which were to screen and evaluate the reports before forwarding to NORAD headquarters. 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 [at Ent AFB] 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."
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. 35.0 35.1 Lua error in package.lua at line 80: module 'strict' not found. (cited by Volume I p. 257)
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found. (identified by NORAD Hist. Summary Jan-Jun '58 p. 7)
  38. 38.0 38.1 compiled by Lua error in package.lua at line 80: module 'strict' not found.
  39. Preface by Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found. (cited by Volume I p. 271 & Schaffel p. 325)
  41. Lua error in package.lua at line 80: module 'strict' not found. (cites Miller 1961)
  42. Lua error in package.lua at line 80: module 'strict' not found. pdf p. 17
  43. 43.0 43.1 43.2 43.3 Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
  46. 46.0 46.1 Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found. (the quotation is annotated with footnote 35)
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. 50.0 50.1 Lua error in package.lua at line 80: module 'strict' not found.
  51. 51.0 51.1 51.2 51.3 Lua error in package.lua at line 80: module 'strict' not found.
    a. Lua error in package.lua at line 80: module 'strict' not found.
    b. Lua error in package.lua at line 80: module 'strict' not found.
    c. Lua error in package.lua at line 80: module 'strict' not found.
  52. 52.0 52.1 52.2 Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found. (Edwards footnote 55 cites Harrington p. 370)
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. 60.0 60.1 Lua error in package.lua at line 80: module 'strict' not found.
  61. 61.0 61.1 Yahoo! Groups. Dir.groups.yahoo.com. Retrieved on 2013-09-18.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. 63.0 63.1 Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. 66.0 66.1 Preface by Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found. (Foreword is part of pdf that includes "Editor's Note" and a transcript of Benington's 1956 symposium paper beginning with the Introduction—"This paper looks ahead at some programming problems that are likely to arise during Forrester's 1960-1965 period of real-time control applications."—through Summary: "The techniques that have been developed for automatic programming over the past five years have mostly aimed at simplifying the part of programming that, at first glance, seems toughest—program input, or conversion from programmer language to machine code.")
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Missile Master Plan [1] [2]; identified by Schaffel p. 260: "…the Defense Department to issue, on June 19, 1959, the Master Air Defense Plan. [sic] Key features of the plan included a reduction in BOMARC squadrons, cancellation of plans to upgrade the interceptor force, and a new austere SAGE program. In addition, funds were deleted for gap-filler and frequency-agility radars.21 [1959 NORAD/CONAD Hist Summary: Jan-Jun]"
  71. Lua error in package.lua at line 80: module 'strict' not found. (Schaffel p. 268 citation 39)
  72. Lua error in package.lua at line 80: module 'strict' not found. (Schaffel Ch 8 footnote 64 cites this report on pp. 223/312)
  73. http://comptrollerlegal2002.tpub.com/d02658/d026580062.htm Formerly Used Defense Site C02NY0714
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found. (cited by Schaffel)
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.. Articles include:
    Lua error in package.lua at line 80: module 'strict' not found. (cited by Edwards, 1996)
    Lua error in package.lua at line 80: module 'strict' not found. (cited by Schaffel 310)
    Lua error in package.lua at line 80: module 'strict' not found. (citation 15 of Edwards, 1996)
    [verification needed]Lua error in package.lua at line 80: module 'strict' not found. (cited by Schaffel p. 310)
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found. (cited by Schaffel p. 205/311: "Although technically a Lincoln unit, SDC did much of its work at RAND Headquarters in Santa Monica, California. RAND designers developed the Model I software that allowed realistic training for [SAGE] technicians scheduled to operate the first direction center.")
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. Lua error in package.lua at line 80: module 'strict' not found. (image of entrance sign with arrow: "Bangor North American Air Defense Sector")
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found. (GATR R-19 "was located at Minot AFB" DC-19.)

Further reading