Industrial computing history is more than a record of machines. It includes the software, documents, and decisions that show how organizations adopted technology and changed the way they worked. A large collection discovered in a warehouse near Castrop-Rauxel, Germany, offered a striking example: thousands of artifacts were at risk of being lost, including equipment from early data processing through the mainframe and minicomputer eras.
The Computer History Museum organized a rapid assessment and rescue effort with volunteer Alex Bochannek. Supported by a donation from SAP AG, the museum arranged to move selected artifacts to California. The experience illustrates a challenge familiar to anyone responsible for legacy technology: important equipment and records can be overlooked until their preservation becomes urgent.
What the warehouse held
The collection had been assembled from several sources and stored in a shared warehouse. Its contents ranged from Depression-era mechanical punch-card equipment to mainframes and minicomputers. More than 112 manufacturers were represented, including Telefunken, Siemens, Zuse, Olivetti, and Groupe Bull.
Hardware made up most of the collection, but the non-machine materials were also significant. About one-fifth of the collection consisted of pallets of documents and media, including historical software. Some records were unique site-planning documents and sales requests for proposals from businesses and universities considering computer systems. These materials can help researchers understand how organizations evaluated and introduced computing—not just what equipment they ultimately used.
That distinction matters when considering the development of industrial data processing. A machine can reveal its components and design, while proposals and planning records can offer insight into the needs and processes that shaped its deployment. Preserving both kinds of evidence creates a more complete account of how computing entered organizational life.
How curators assessed the collection
Before travelling to Germany, the museum team reviewed photographs of the warehouse and identified objects where possible. On site, the curators divided the more than 14,000-square-foot area into a two-meter grid. They recorded the contents of each section, noting manufacturers, models, and other relevant details when they could be established.
This method helped turn an overwhelming space into an inventory that could support decisions. The team had to assess the condition and significance of thousands of objects while working within limits on shipping and storage. The goal was not to take everything. It was to identify items with historical value, fill gaps in the museum’s collection, and preserve material that could support future research, restoration, or exhibits.
These decisions required collaboration. Museum staff contributed curatorial and software expertise, while the volunteer’s German language skills helped with the work in Germany. Operations staff handled international freight arrangements, and a moving company helped plan the transport. Other German museums and computer clubs were also given opportunities to consider items, reflecting the principle that preservation can take place in more than one institution.
Preserving more than hardware
For automation engineers and plant leaders, legacy computing can feel like a narrow subject: old equipment is replaced, and attention moves to the next system. But the collection shows why physical hardware is only part of the record. Software, planning documents, and technical media can preserve evidence about how computing was selected and used.
Historical records may also help researchers interpret the broader context around a system. A request for proposal, for example, records what an organization sought when it was considering computerization. Site-planning material can document preparation for installation. Such records do not provide a complete account on their own, but alongside the machines and software they can help build a richer picture of technology adoption.
Preservation also involves practical constraints. The warehouse had been exposed to dust, moisture, and contamination from birds and other conditions. Not every item was suitable to retain. After the selected artifacts were tagged, the museum also had to arrange appropriate recycling for equipment it did not take, while giving local groups a chance to review some of the remaining items.
Time, logistics, and the preservation window
The rescue depended on quick action. The collection faced the possibility of being sold or disposed of, and the assessment had to happen before decisions about its fate were finalized. Once selected, the artifacts still needed packing, shipping, and storage. The journey across the Atlantic was only the start: each object would require inventory work and a catalog record before it could be readily managed or made accessible to researchers.
This sequence underscores a central challenge in preserving computing heritage. Finding a collection does not complete the work. Organizations must also establish what they have, document it, protect it, and plan for responsible storage. For equipment that is common and mass-produced, a museum may already hold sufficient examples. Rare or distinctive objects—and the records connected to them—may deserve closer consideration.
The effort was made possible in part by SAP AG’s $250,000 gift, which supported shipping and logistical needs as well as storage. The contribution helped make a large international acquisition feasible, but the curatorial work remained essential: the team had to assess the material, make selections, and coordinate its movement and care.
What the rescue means for industrial computing history
The German warehouse collection demonstrates that the history of computing is held not only in celebrated machines, but also in ordinary records of planning, procurement, software, and use. For industrial automation professionals, that perspective is a reminder that technical change unfolds within organizations. Equipment matters, but so do the requirements, decisions, and processes that bring it into service.
Preserving that record requires preparation, informed selection, and collaboration across technical, curatorial, and logistical roles. When rare systems or documentation surface, timely assessment can determine whether they become usable historical resources or disappear from view. The practical lesson is simple: recognize the potential value of legacy computing materials, document what is present, and involve appropriate preservation specialists before disposal decisions are made.