Access Official Technical PDF

Share Summary:LinkedInEmail

Remote batch terminals addressed a problem that remains familiar to industrial automation teams: getting data from dispersed locations into a central computing resource in a form it can process efficiently. In a 1968 product announcement, Varian Data Machines presented its Data-mate concept as a combination of remote and central terminals designed to handle preparation and transfer tasks around a main computer. The equipment is a historical example, but the underlying design principle is still relevant: distribute appropriate data-handling work instead of making the central processor manage every step.

How remote batch terminals divided the work

The Data-mate arrangement used two types of equipment. At the remote end, a Varian Data 520/i terminal formatted and compressed data before transmitting it over duplex voice-grade telephone lines. At the central site, a Varian Data 620/i received compressed data from as many as eight remote terminals at the same time, temporarily stored it, and supplied it to the central processing unit in a selected format and sequence.

This division separated preparation and communication from the central computer’s primary processing work. The remote terminal shaped the data for transmission; the central terminal received and organized it for delivery to the CPU. The advertisement emphasized that the system could be introduced without major reprogramming of the existing computer. That detail matters: connecting a new data path is more practical when it can fit around established applications rather than requiring broad changes to them.

The arrangement also reflects a basic systems-engineering trade-off. Some work is performed near the point of data entry or transmission, while other work remains centralized. Buffering at the central terminal provides temporary storage between incoming communications and CPU processing, helping decouple the timing of those activities. The source describes the function, but does not specify buffer capacity or performance under particular workloads.

Why data preparation and transmission mattered

Communication capacity was a prominent concern in the period’s equipment announcements. Varian promoted formatting and compression as ways to increase line efficiency. Tally Corporation described systems that could take source data from perforated tape, magnetic tape or punched cards and transmit it at 1,200 words per minute over ordinary telephone lines. The same advertisement identified a serial printer rated at 60 characters per second and a stand-alone magnetic-tape terminal that could produce computer-compatible tape.

These examples show that data communications involved more than selecting a transmission line. Input media, data representation, transmission, and output all had to work together. Preparing data before sending it could reduce what needed to cross a line; receiving and converting it into a useful form could make it easier for a central system to accept. For engineers planning an integrated workflow, the lesson is to consider the complete path from source data to the processing system, rather than focusing on the communications link alone.

Other announcements pointed to different ways of connecting users and equipment. One described a portable data coupler intended to connect to a convenient telephone, while Tally highlighted a service network and a test center for addressing equipment problems. These were vendor descriptions, not comparative performance evaluations, but they illustrate that portability, service support and the ability to work with different data sources were part of the broader communications-system proposition.

Remote batch terminals and central processing overhead

The Data-mate advertisement positioned its system as a way to relieve a large central computer of “housekeeping” duties and expand capability without investing in additional central computing equipment. It also claimed an efficiency improvement of 40% or more. That figure should be understood as a vendor claim; the announcement does not provide the workload, measurement method or operating conditions needed to assess it independently.

The more general point is that central processing resources can be occupied by tasks that surround the core application: preparing records, managing incoming data and arranging work for processing. Moving some of those functions to dedicated communications equipment could change how the central computer was used. Whether that approach is beneficial in a particular installation depends on its workload, data volumes, communication constraints and integration requirements—details not provided in the historical announcement.

Applying the design principles to automation systems

Industrial automation environments often involve equipment and data sources that are distributed across a facility or organization. The historical systems described here offer a useful checklist for evaluating data movement and processing architecture:

  • Identify where data preparation occurs. Determine whether formatting or other handling can happen before data reaches a central computing resource.
  • Account for transmission constraints. Understand how the chosen representation and transfer method affect the amount of data sent.
  • Plan for buffering. Consider how incoming data is held and sequenced when its arrival does not align with processing availability.
  • Check compatibility with existing applications. Assess whether new communications equipment can be introduced without extensive changes to established software.
  • Include service and operations needs. Equipment support and practical operating procedures are part of system design, not afterthoughts.

These are architectural considerations, not a claim that 1960s terminals map directly to modern automation platforms. The source describes specific historical products and communications methods; it does not establish their suitability for present-day control systems or applications.

Conclusion

Remote batch terminals were designed to organize work across the boundary between dispersed data sources and a central computer. The Data-mate concept used remote formatting and compression, central reception and temporary storage, and sequenced delivery to the CPU. Alongside period examples of tape-based input, printing and telephone-linked terminals, it demonstrates why data preparation, buffering, compatibility and support belong in the same system discussion. For automation decision-makers, the practical takeaway is to design the full data path deliberately—and to distinguish documented functions from performance claims when evaluating any proposed architecture.

Access Official Technical PDF

About The Author