Strategic Automated Command and Control System

From Wikipedia, the free encyclopedia
"SACCS" redirects here. For other uses, see Strategic Air Command Control System.
Command Data Buffer configuration in 1991, including part of the SACCS Replacement Keyboard (SRK), Line Printer Unit (LPU) and associated equipment rack (right edge of photo) in an underground missile launch facility.[citation needed] The 1983 "WarGames" movie scene in the ICBM launch center (filmed in a Missile Procedure Trainer at Vandenberg AFB)[citation needed] briefly shows a SACCS LCC mainframe computer[dubious – discuss] inside the launch capsule. The SAC Control System circuits that terminated at the same Remote Communications Central (RCC) had diversified routing--circuits originating and terminating at common locations were routed via diverse paths.[1]

The Strategic Automated Command and Control System (SACCS) is a United States Strategic Command command and control system to coordinate the operational functions of United States nuclear forces (ICBMs, nuclear bombers, and SLBMs).

Background[]

The ITT 465L Strategic Air Command Control System (SACCS) with its IBM AN/FSQ-31 SAC Data Processing Systems attained operational capability on January 1, 1968; and its gradual replacement began on October 6, 1975, when the SACCS original IBM 4020 Military Computers were replaced by computers (remaining FSQ-31 components were entirely decommissioned in November.)[citation needed] The Strategic Air Command Digital Information Network was deployed to replace SACCS' "Data Transmission Subsystem and part of the Data Display Subsystem",[2] e.g., on November 5, 1986, "Martin Marietta Corporation technicians began installing SAC Digital Network (SACDIN) equipment in 91st Strategic Missile Wing missile launch control centers[3] (i.e., either a rack or rack).[4] On February 20, 1987, "SAC declared initial operational capability for the when [it] operated successfully between the Headquarters SAC Command Center and the 55th Strategic Reconnaissance Wing Command Post, both located at Offutt AFB, Nebraska, and the 351st Strategic Missile Wing Command Post at Whiteman AFB, Missouri."[3] SACDIN eventually "linked 135 locations and permitted two-way message communications with ICBM launch control centers for the first time,"[3] and the Ground Wave Emergency Network communication system had a Final Environmental Impact Statement issued in September 1987.[5]

SAC Automated Command and Control System[]

In 1990 when the 465L System had been entirely replaced by the "SAC Auto Cmd/Ctl Sys"[6] for several years, the former SAC C2 system continued using that name as part (except for the SACCS Data Processing System) of "USSTRATCOM Command and Control" ( 0101316F).[7] By 1995, the "emergency war order (EWO) communication systems consist[ed] of the primary alert system (PAS), SAC digital network (SACDIN), Survivable Low Frequency Communications System (SLFCS), Air Force Satellite Communications System (AFSATCOM), [ICBM] Super High Frequency Satellite Terminal (ISST) and [UHF] voice radio communication systems"[4] The USSTRATCOM SACCS was redesignated[when?] Strategic Automated Command and Control System with the same acronym on [specify] and by 2011, the Minimum Essential Emergency Communications Network was being modernized in the .[8] By February 2012, USSTRATCOM was using the (ISPAN), and the USSTRATCOM Replacement Facility Fit-Out (PE 0303255F) was to "include secure HEMP-Shielded Command and Control Center, mainframe computer data centers, multiple 24/7 mission operations centers, storage and maintenance areas, labs/workrooms, back-up generators, Uninterruptible Power Source, Technical Control Facility, Fiber Ring, [with funding] beginning in FY13."[9]

Age of system and planned replacement[]

A Government Accountability Office report on aging and outdated "legacy systems" used by the federal government published in 2016 noted that the SACCS was one of the oldest federal IT investments, running on 1970s-era IBM Series/1 software and 8-inch floppy disks.[10] The report noted that the Department of Defense "plans to update its data storage solutions, port expansion processors, portable terminals, and desktop terminals by the end of fiscal year 2017."[10]

References[]

  1. ^ "Strategic Air Command Control System (SACCS): Description and Service Maintenance", Private Line Data Systems: Special Data Networks, Plant Series, American Telephone and Telegraph Company, July 1965, retrieved 2014-05-12
  2. ^ "Histories of Subordinate Units Reporting Directly to the Strategic Communications Division", 1 January - 31 December 1982, Vol 4 of 41
  3. ^ Jump up to: a b c Clark, Major Rita F (1 May 1990). SAC Missile Chronology 1939–1988 (PDF) (Report). Office of the Historian, HQ. SAC, Offutt AFB. Retrieved 2013-09-26. 1958…1 January Headquarters SAC established the Office of Assistant CINCSAC () at Inglewood, California. This position was designated to serve as an extenstion of Headquarters SAC and was responsible for working closely with the Air Force Ballistic Missile Division … 1966…17 April The first attempted launch of a Minuteman II ICBM by means of the Airborne Launch Control System (ALCS)
  4. ^ Jump up to: a b title tbd (Section I: Communications Systems Description) (), November 1995, retrieved 2014-05-12, The single SACDIN cabinet at PLCCs is the communications processor set (HUTE rack). … SAC Digital Network System
  5. ^ Introduction | Assessment of the Possible Health Effects of Ground Wave Emergency Network | The National Academies Press. 1993. doi:10.17226/2046. ISBN 978-0-309-04777-7. PMID 24967486.
  6. ^ Hutzler, Patricia L. (April 1990). Defense Planning and Programming Categories: A Special Tool for Special Needs (PDF) (Report). Volume 3. Appendix E, Proposed Expanded DPPC Structure. Logistics Management Institute. Retrieved 2014-05-18. |volume= has extra text (help)
  7. ^ "0101316F USSTRATCOM Command and Control". www.brookings.edu. Archived from the original on 2016-03-04. Retrieved 2016-05-26.
  8. ^ http://www.dtic.mil/descriptivesum/Y2013/AirForce/stamped/0303131F_7_PB_2013.pdf
  9. ^ "Archived copy" (PDF). Archived from the original (PDF) on 2014-11-27. Retrieved 2014-05-18.CS1 maint: archived copy as title (link)
  10. ^ Jump up to: a b David A. Powner, GAO-16-696T, Information Technology: Federal Agencies Need to Address Aging Legacy Systems, Government Accountability Office (testimony before the Committee on Oversight and Government Reform, House of Representatives (May 25, 2016).
Retrieved from ""