IBM System/7
| Company type | Product |
|---|---|
| Industry | Industrial control computers |
| Founded | October 28, 1970 |
| Headquarters | Boca Raton , United States |
| Products | Industrial control computer system |
The IBM System/7 was introduced as an industrial control computer system on October 28, 1970, with its initial deliveries commencing in 1971. This 16-bit system was notable for being one of IBM's earliest models to incorporate cutting-edge semiconductor memory technology, moving away from the then-common magnetic core memory.
Although IBM had previously released industrial control products such as the IBM 1800 in 1964, the System/7 distinguished itself through a unique architectural design and software framework. Its development and assembly took place in Boca Raton, Florida.
Hardware architecture
The central processing unit, known as the IBM 5010, featured eight registers primarily intended for general-purpose use; however, register R0 had specialized roles including indexed addressing and managing system I/O. In 1973, the timing for operations was as follows: register-to-register instructions required 400 ns, memory read operations took 800 ns, writes lasted about 1.2 μs, and direct input/output processes approximately 2.2 μs. The instruction set prioritized register-based commands with a minimal set of memory instructions, reflecting characteristics similar to contemporary RISC architectures. Notably, multiplication and division were implemented via software routines and depended on operating system support.
The System/7 was physically compact relative to contemporaneous systems, utilizing chassis and gate designs common to IBM products like the 3705 communications controller. Typical installations occupied one or two racks standing roughly high; smaller configurations were closer to in height. The standard console interface was the Teletype Model 33 ASR (IBM 5028), which also facilitated loading the initial boot sequence. Lacking ROM and relying solely on volatile semiconductor memory meant that the system booted by reading a small loader program from the Teletype device; this loader then fetched the complete program either from another computer, a high-speed paper tape reader, or via an RPQ interface connected to a tape cassette player. While many external peripherals communicated using ASCII, internal data processing utilized IBM's proprietary EBCDIC character encoding.
Specialization
The System/7 was engineered with various process control capabilities in mind. Its CPU incorporated four register banks assigned different priority levels, enabling interrupt handling within a single instruction cycle by switching to a higher priority bank. Dedicated I/O modules supported functions such as analog signal measurement, signal generation, solid-state or relay-based switching, and TTL digital input/output lines. The design accommodated industrial environments lacking air conditioning and offered optional adaptations for operation under harsh conditions.
Standard Hardware Units
A standard System/7 configuration typically comprised:
- IBM 5010: Processing Module – The central controller responsible for arithmetic calculations, logical operations, and overall system control.
- IBM 5012: Multifunction Module – Oversees both digital and analog input/output functions; also manages IBM 2790 device control.
- IBM 5013: Digital Input/Output Module – Dedicated to digital I/O tasks and interfacing with custom peripherals; supports IBM 2790 device management as well.
- IBM 5014: Analog Input Module – Converts incoming voltage signals into digital data inputs.
- IBM 5022: Disk Storage Unit – Released in 1971, providing storage capacities of either 1.23 million or 2.46 million words of 16 bits each.
- IBM 5025: Enclosure – The rack unit housing power supplies alongside input/output modules.
- IBM 5028: Operator Station – A standalone workstation equipped with keyboard, printer, paper tape punch, and reader. Initially required for every System/7 installation but later permitted to be shared among multiple systems.
Maritime Application/Bridge System
This solution is tailored specifically for shipboard navigation and comprises the following components:
- 5010E Processing Module – a constant element.
- 5022 Disk Storage Unit.
- 5026 C03 Enclosure – adapted to endure intense vibrations and tilting motions.
- 5028 Operator Station.
- 5090: N01 Radar Navigation Interface Module (RNIM) – connects with original equipment manufacturer (OEM) radar, gyroscopes, and navigation devices.
- 5090: N02 Bridge Console – offers a radar plan position indicator (PPI) to facilitate navigator interaction and system management.
Additional RPQs provide enhanced hardware durability, connectivity to various navigational instruments, and spare parts for onboard use.
Software
The operating system operated as a control monitor, delivering customizable assembler subroutines to support peripheral devices and applications. The smallest configurations required 8 KB of memory, with typical implementations using 12 KB or more, up to a maximum of 64 KB. The adoption of advanced semiconductor memory improved processing speed but increased costs, prompting efforts to reduce application memory usage before deployment. Development environments ran on IBM System/360 machines, with program images transferred via serial connections to System/7 development facilities. Disk overlays were uncommon prior to 1975 due to limited software capability. IBM Dolphin sealed cartridge hard drives were available but expensive; they primarily served as file systems for storing data and executable files, thereby lessening dependence on paper tape boot procedures.
Programming was predominantly conducted in macro assembly language featuring an extensive macro system for dynamic code generation. Static variable binding was typical, reflecting the fixed and specialized nature of the deployed software. Real-time interrupt latency was rigorously controlled through four priority levels combined with optimized software routines to ensure timely responses. By 1976, Fortran and a subset compiler of PL/1 (PL/7) became accessible as larger configurations enabled more sophisticated processing. System/7 programmers needed proficiency with the actual instruction set architecture.
Development frequently took place on S/360 or S/370 systems using a High-Level Assembler (HLASM) variant modified for MSP/7 macros. To increase programming versatility, IBM’s San Jose Research Laboratory created the LABS/7 operating environment featuring an Event Driven Language (EDL), which was later adapted for the Series/1 platform as the successful Event Driven Executive (EDX).
Uses
The System/7 was aimed at particular real-time sectors requiring input/output from analog devices such as temperature sensors and industrial control systems. Its commercial uses encompassed factory automation and air conditioning energy management, with AT&T among its notable clients. Nonetheless, its predominant applications were likely within classified military projects.
Example customers
A selection of System/7 users demonstrates its broad utility:
- In 1971, IBM supplied its inaugural System/7 unit to American Motors Corporation (AMC) in Kenosha, Wisconsin, for automotive emissions measurement; installation was completed within a day.
- By 1972, the University of Pennsylvania utilized System/7-connected remote terminals equipped with card readers to enforce meal contract adherence among 2,000 students, preventing fraudulent use.
- In 1978, Pfizer employed a System/7 system featuring audio-response functionality that allowed roughly 1,300 sales representatives to place orders remotely through touch-tone telephone terminals known as "Joanne".
Maritime Application/Bridge System
Introduced on October 15, 1973, IBM’s Maritime Application/Bridge System had been installed on more than 100 ships by 1979.
This system was the inaugural navigational aid to receive approval from Lloyds Register’s Control Engineering Department as Approved Control and Electrical Equipment.
Engineered to improve both safety and operational efficiency on large vessels, the system lessened the burden of data interpretation for bridge crews and enhanced the clarity of information display. It featured five key programmed capabilities:
- Collision evaluation: Merges inputs from radar, speed log, and gyrocompass to detect potential collision threats within a radius of 16.5 nautical miles.
- Position determination: Utilizes satellite navigation, Decca Navigator, gyrocompass, and speed log data to present the ship’s current location.
- Adaptive autopilot: Automatically modifies steering controls in response to changing sea conditions.
- Route planning: Allows prediction of navigational adjustments based on current position and intended destination or waypoints; routes can be stored and later retrieved.
- Route monitoring: Tracks navigator-defined boundaries using positional data and displays channels or lanes on the PPI; alerts activate if boundaries are neared.
In the late 1970s, IBM Chairman Frank Cary opted to discontinue the system’s use due to concerns over legal liability and reputational damage from possible maritime incidents. Compensation was provided to all customers for system removal.
Withdrawal
The product was officially discontinued from the market on March 20, 1984. IBM’s subsequent industrial control solution was the Series/1, which was also developed at Boca Raton.