While a lot of the basic research existed on paper, turning that into functional 24/7 systems at mega-scale was an almost unimaginable engineering challenge. The fragments which already existed were little more than one-off prototype computers like ENIAC, none of which were remotely close to big enough, fast enough or reliable enough. So they were faced with creating pretty much the full stack from transistors to storage to networking to displays - all of which had to be several generations bigger, faster and better than anything that had ever been shown to even sort-of work on a lab bench. While the budgets were huge, the requirements were equally insane and there was huge pressure to deliver it ASAP. And "it" had to actually work and then be built, deployed and operated daily across dozens of locations. It ultimately involved dozens of huge companies, hundreds of sub-contractor firms and tens of thousands of people. Pretty much everything I'd ever heard about in 1960s computing, when I dug into where the fundamental tech came from, ended up tracing back to enabling something the air defense network needed in the 50s.
I came away realizing the mid-60s scalable commercial computing industry I think of as my ancestral 'up-line' in computing, the 360/PDP systems which led to the 1970s 8-bit microprocessors which led to the 80s home computers anyone could own, would have all been at least a decade later without the crazy mad dash in the 1950s to enable the air defense build-out.
https://en.wikipedia.org/wiki/Semi-Automatic_Ground_Environm...
https://sage.mitre.org/ (see also links at the end)
SAGE also pioneered user interface technology, for example:
The first pointing device: https://historyofinformation.com/detail.php?id=727
The first naked lady on a computer: https://www.theatlantic.com/technology/archive/2013/01/the-n...
And bits of the machinery went on to a long and varied career in film and TV: https://www.starringthecomputer.com/computer.php?c=73
Any system of human controllers talking to human pilots would not be up to the task. Even a one-second delay would have meant a missed intercept. They needed machines to make the calculations and issue the orders. Those same machines eventually even controlled the interceptors directly, interacting with onboard radar/autopilot systems to remotely steer fighters into position.
Things would be/are very different today. Long-range air-to-air missiles/radar mean fighters do not need sub-second navigation accuracy to intercept fast targets. Air-to-air refueling also means fighters can loiter in position rather than panic-launch from the ground. Pilots today would balk at the idea of having a computerized ground controller drive "their" aircraft. It is now an unnecessary and alien concept.
Had missile and airborne radar tech advanced a little faster, maybe a little less than a decade, NORAD may not have asked for all those computers. Who knows what the world would look then like today. Get the sparrow (Aim-7) missile ready in 52 instead of 58 and maybe the computer revolution happens much more slowly.
He got his start because he had a security clearance and knew how to install and repair ccd camera systems do he did so for rocky flats and Cheyenne mountain. Then they asked him to build a box that had a film video camera that would take images of a crt display for record keeping. This was before it was possible digitally. So he did, he made 2. Then they needed a lift to bring down the Hughes projectors they used in Cheyenne mountain, the old kind with 3 color crt projectors. It needed to drop down the projector so they could change it out in less time than it took a nuke to come from Russia, so he did. He founded a company to keep making them, they still make them to this day.
So many companies were set up on the back of this cutting edge stuff, as well as Mercury and Apollo, satellites, nuclear reactors, submarines, jet liners, the SR-71, the Heavy Presses, it just goes on and on. Everything from one guy in a barn up to huge corporate labs. Obviously the war already boosted a lot of stuff, but the Atomic Age atmosphere must have felt like an unstoppable industrial whirlwind.
Even though the recent AI hype has been pretty feverish, it doesn't seem like we have had the same kind of top-to-bottom hopeful dynamism.
Even in the 70s/80s, some prototypes were hardwired.
One detail that caught my attention: they used triple-redundant IBM 7090 mainframes with real-time voting between systems. This is surprisingly similar to modern consensus protocols like Raft, just implemented in hardware. Makes me wonder if we've over-complicated things with software-based consensus when simple majority voting could suffice for many use cases. The key seems to be truly independent failure domains - something NORAD achieved through physical separation that's harder to replicate in cloud environments.
Would love to hear from others who've implemented hardware-based consensus systems. How do they compare to software solutions in terms of reliability and complexity?
With more complexity comes more interesting failure scenarios. Simple redundancy handles problems where components outright fail, but software never really ... fails, in that sense. It always performs exactly to design – but sometimes the design is inadequate. Replication and majority voting does not handle design flaws and errors of e.g. interaction, which are increasingly common the more softwareified a product is.
Thus we need more complicated ways to build fault tolerance into systems where we have to assume that the design is wrong somewhere, and we cannot just replicate ourselves out of the problem.
It's not hard to achieve separation in cloud environments. It's just expensive, and for most, the need doesn't justify the expense. Every once in a while you do run into things like actually all the clouds in (location) are located in the same building; or you paid for two separate strands, but a backhoe has determined that both strands are in the same bundle. Or your two redundant providers of whatever use each other to provide service.
"Closing the iris."
There will never be another SG-1
"Unscheduled offworld activation"
For a few years after the downfall of the USSR and before 9/11, there were public tours. That was a happy, peaceful time.
Here's a partial tour from the 1970s.[1]
There is no one big control room. There are about a half dozen control rooms with different functions. There are duplicate control rooms outside the mountain, and for a few years, those were primary and the mountain only had a skeleton staff. Not any more. (Although Hegseth apparently wants to move some operations to Huntsville, Alabama.)
Modern photos are available. Modest sized rooms with flat screens on the walls, desks, ordinary monitors, and keyboards. About the only unusual thing is that there's video switching, so that monitors can be copied to a big screen, or someone else's screen, when something is happening and many people need to focus on one screen.
There's now a vast flood of crap AI art and mislabeled clickbait for the Cheyenne Mountain Operations Center. Sorting out the real from the fake is becoming harder.
(One of my career achievements from my aerospace days was managing to avoid being transferred to Colorado Springs to work on their networking problems.)
Well, all the cool kids were apparently doing "Deep space radar telemetry" :)
(Those guys were around. I worked at a location in Silicon Valley which had a 20 meter steerable dish in the parking lot, the prototype for others around the world.
The Colorado Springs guys were trying to migrate off the DEC PDP-11 to some kind of microprocessor. The PDP-11 (16 bit address space) was very popular with the USAF/intel crowd. Making add-ons and plugging them into the bus was a fully documented and supported procedure, not a hack. DEC sold all the parts needed for that. The usual setup was one or more PDP-11 machines connected via a custom interface to something exotic. In the early 1980s, it was time to go to a microprocessor. But what?
They picked the Zilog Z-8000 [1], because it was the closest thing to a PDP-11. That turned out to be a dead end, but the aerospace company was already building custom interface hardware that talked to it, so they were stuck for the duration of separate projects. Did not end well. At one point I did get TCP/IP onto a pair of Z-8000 based Oynx machines, which were for a brief period the lowest cost UNIX boxes.)
But I did get to go down the tunnel and through the blast door.
pretty much the plot of Dr Strangelove
Comparing these images of the COC to what was reimagined for War Games really feels underwhelming. From the few images, it just feels very complex and overloaded with information that is just a lot to take in. Maybe it gets easier to deal with when that's what you do everyday, but it definitely has that feel of "designed by an engineer" instead of "designed by a UI professional". Essentially, it feels like every single UI I've ever made.
Everything is simplified down to a stupid hamburger menu if you want to do anything off the happy path.
I don't think the President would have gone to Cheyenne wouldn't have been time since Colorado is quite far from Washinton D.C - iirc the plan was always kneecap (NEACP[1]) once it was online (and it still is).
They obviously don’t discuss it for obvious reasons but given the options I’d say east then either north or south, Canada is nearer and air fields with sufficient length to be able to land (and is in NATO) which is why it’d be my guess at least to start with, loiter over an unpopulated area and at least the likelihood is reduced of been near a detonation is reduced, the continental US simply has too many targets, though with modern warheads been lower yield they’d likely be OK orbiting unpopulated areas out west I guess.
Yeah, the Loonies in "The Moon Is A Harsh Mistress" keep pounding away at it with space rocks launched from the Moon. It worked in the end, overall.
It's not the same as something like Threads (1984) to me.
This is easily the best, inadvertent advertisement ever for boosting the nation's missile defense capabilities, and it's ironic that it came out of progressive Netflix studios, given that progressives have insisted since the 80s that missile defense is a worthless, impossible ("like hitting a bullet with a bullet") MIC boondoggle. Thanks, Netflix!