Dr. Leslie P. Michelson, currently Director of the High Performance Computing Center at UMDNJ, was VA Shiva Ayyadurai’s mentor and supervisor at the University of Medicine and Dentistry of New Jersey (UMDNJ) in Newark, NJ, during 1978 to 1982.
It has been nearly thirty years since Shiva and I have spoken. After observing the news following his being honored at the Smithsonian on February 16, 2012, and the abusive reaction from certain individuals, I believed that it was important to respond for many reasons. My first reason is to unequivocally authenticate that Shiva created “EMAIL”, the first email system, in my lab, starting in 1978. EMAIL, for the record, was more than just a “program“ but a complete system --- it was the “electronic inter-office, inter-organizational mail system,” the first of its kind, an integrated platform that provided all the recognizable elements of what we call email today, as related in a previous and accurate article written by Doug Aamoth in Time. EMAIL went beyond “electronic messaging.”
My second reason is to offer an appreciation of the ecosystem and environment, in which this creation of EMAIL took place at UMDNJ. Much of the abuse and invective surrounding news of the invention of the world’s first email system by a 14-year-old, is more about perhaps a shattering of a false and long-held narrative that innovation can only take place in environment of big universities, large companies and the military, and by certain people. My third reason, perhaps the most important one, is to share a different narrative, that our efforts at UMDNJ, which supported EMAIL’s innovation, demonstrate that innovation can take place any place, any time and by anybody, if the right structure and resources are provided, even in Newark, NJ in 1978 by a 14-year-old.
Let me begin by providing you a background to UMDNJ and my relationship with it. In 1975 the IT department of UMDNJ, then officially known as the College of Medicine and Dentistry of New Jersey (CMDNJ) hired me, an experimental high energy physicist from Brookhaven National Laboratories, who had some general scientific computing experience and an interest in using minicomputers, the small computers of the time, to control and acquire data from laboratory experiments.
In 1978, CMDNJ, was a young organization, and prior to its establishment as a university of the Health Sciences in December of 1981, it was (and still is) a free-standing public institution comprising several medical schools, a dental school, school for the health related professions and a graduate school of the biomedical sciences . Absent were the STEM fields (science, technology, engineering and mathematics). Rather, CMDNJ focused exclusively on clinical and basic biomedical research and healthcare. Having been signed into law in 1970 and comprised of the former Rutgers Medical School and the New Jersey College of Medicine and Dentistry, CMDNJ was establishing itself as a major academic health sciences institution.
The IT department at the time, although small, included a scientific data processing group. The group was populated with several biostatisticians and mainframe computer experts. The staff interacted with faculty from numerous departments both in the clinical and basic sciences and became quite adept at introducing machine computation to life scientists, who, given their backgrounds and given the time period had little experience in using computers. Our main local computing device, an IBM remote job entry terminal, was connected to remote batch and time sharing machines operated by an educational consortium known as the New Jersey Educational Computer Network.
Minicomputers made by Digital Equipment Corporation, Data General, Hewlett Packard and others were in fairly widespread use by 1975. They were used with growing frequency in disciplines ranging from nuclear physics to neuroscience. Medical equipment manufacturers were beginning to incorporate them as control and analysis elements in a new device called CAT Scan and they would soon give rise to a new generation of diagnostic instrumentation in which the rate of data acquisition and manipulation mandated the use compact computing hardware built into or adjacent to the instrument.
We were connecting minicomputers directly to laboratory equipment to automate data collection and effect control systems in which real time analysis could influence the generation of electrical stimulus thereby helping to guide the progress of neurophysiological lab experiments. Other life sciences disciplines were similarly suited to this kind of automation.
Although vastly less costly than mainframes, minicomputers were not inexpensive. Furthermore, we had several campuses on which to distribute the minicomputer resources including Newark, Piscataway and New Brunswick. These challenges led to the development of a network we called the LCN for Laboratory Computer Network, where more capable minicomputers were connected to one another and to smaller laboratory machines we called satellite nodes. The satellite nodes, more often than not, lacked a mass storage device -- they were very expensive at the time --and depended on the larger nodes to boot their operating systems and applications.
Today, there is a lot of talk about creating “innovation hubs” or “innovation centers.” My group at UMDNJ, far more modest in retrospect, provided an emerging ecosystem and environment for such innovation. We had the basic infrastructure, and above all were able to attract smart and dedicated people, curious and passionate, who wanted to explore new platforms. Though I ran the scientific data processing organization at UMDNJ, in a medical college in the late 70’s, it was frankly an unusual place to find the kind of experimentation that would lead to automation advances such as EMAIL that would change the way an important human-to-human communication paradigm would be mediated.
Our computer hardware infrastructure at the time comprised mainframes, minicomputers and microcomputers. The microcomputer, while an exciting and clearly promising architecture, was mainly seen in industrial controllers and as a part of larger computer components. The microcomputer had also become an obsession for many computer hobbyists. The IBM PC and subsequent wide spread adoption of desktop computing was still a few years away. Standardized networks as envisioned by the National Science Foundation’s NSFnet and its commercial successor, the Internet, were almost a decade away.
The predominant use of computers at the time was administrative business processing, scientific calculation and machine-aided design for engineering problems. However, while the role of computation in the broader context of human endeavor would lie in the distance, my hope was to explore such areas. So, I was open to finding others who wanted to participate in such exploration. We had resources, space, a network and computing power.
My team included the late Phil Goldstein who was an early innovator in the educational use of time-sharing systems and Bob Field, a systems programmer, who was very proficient in FORTRAN and database systems also joined us. Dave Ritacco, a wunderkind studying engineering at the Stevens Technical Institute, began working with us to develop user interfaces for graphics systems, predecessor to modern day presentation graphics. Marilyn Bodow and Tina Brezenoff, statistical programmers in our group, were also part of this team, looking to provide better interfaces for broader use of statistics packages.
It was in this environment that we met Shiva.
In 1978 , a colleague from our parent IT organization approached me to ask if I would spend some time with her son, Shiva, a 14-year-old high school student from Livingston New Jersey. Meenakshi Ayyadurai, Shiva’s mother, told me that her son had just completed a summer program in computer programming at the Courant Institute of Mathematical Sciences at New York University for young persons who had demonstrated promise in mathematics. My willingness to talk to Shiva, unfolded into an exciting diversion from the major focus of our work.
By the time Shiva joined the LCN as a high school scholar, a few of us were beginning to ponder the role minicomputers might play in the larger space of human interaction. We were obviously familiar with the nature of the simple interactivity between humans and machines- after all, much of the software we developed to manage lab experiments required interactivity if an investigator was to be in the loop of experimental input and resultant response. We were also familiar with the methods and protocols by which computers could exchange messages with other similar types of computers. Our minicomputers, manufactured by the Hewlett Packard Corporation, were provisioned with subsystems that supported this type of communication. Human interaction was mediated through teletypewriters and relatively primitive CRT-based display devices.
The age-honored memorandum, the primary modality of written human-human communication in the workplace was widely used at CMDNJ as it was everywhere else. The memo, regardless of the method of transport and retrieval has the general properties one-to-one or one-to-many distribution and is easily filed to keep a record of a particular human discourse. In 1978, as in decades earlier, the memorandum was delivered by hand or in the case of a campus or group of campuses, placed in a mailer and transported by an inter-office / inter-organizational/campus/intercampus paper mail process.
It did not take long to recognize that Shiva was an exceptional student and even less to determine that we could challenge him in extraordinary ways. Although beyond the scope of our responsibility, we were eager to explore the use of small computers outside of the space of numerical calculation and experiment control. The notion of automating the entire interoffice, inter-organizational paper mail process to create a system was appealing for several reasons: It was a ubiquitous process, the mechanics of which, at least superficially, could be understood by anyone; the advantage of automation was obvious in that it would be possible to significantly collapse the time frame of transactions; and there were multiple ways in which electronic automation could extend the utility of the memorandum. As far as we knew, no one else in 1978 had attempted to take on such a task.
So the creation of an electronic version of the interoffice, inter-organizational paper mail process became the object of our affection. I sat Shiva down and offered him what turned out to be one of most innovative (and fun) projects my group was ever to undertake. In return I demanded that this fourteen year old youngster channel all of his energies into the project. I made it very clear that he would be a full-fledged member of our team, treated as an adult and that we would expect nothing less from him. Livingston High School agreed to Shiva spending initially a few days a week and later to half-days at the Newark, New Jersey Campus.
Shiva was eager to begin writing code- after all that was the most fun. It was surprisingly easy, though, to convince Shiva that the code would just be a physical embodiment of our vision. Although, we would need a working version, indeed a production model, the lasting contribution would be the systems analysis that we hoped would lead to implementation that was more than the mere automation of a manual process. We wanted to develop a sustainable logical and functional framework that would add significant value and lead to further innovation over time.
Shiva’s first task was to learn how the interoffice memorandum was used at the University. Who wrote them and to whom? What was their place in the hierarchy of written documentation? What was the sender’s expectation of a reply? What volume could we anticipate? And, of course, what could we do to improve the utility of this modality? Surely, user would want more features as soon as they recognized this new potential. Could we be one step ahead?
Thus, after long deliberations, always with Shiva in the lead, we arrived at core design principles, which in the context of the day, were original, and forward looking at the very least:
|A simple user interface would require no specific computer knowledge and would provide access to all program features at the user level. Command lines are to be prohibited- our users were life science researchers, clinicians and administrators, not computer scientists.|
|The user interface would include a visual compose mode with spelling and formatting capability.|
|Interoffice memos would be stored in a structure database and replicated on each node which would also manage account and routing information.|
|Only one instance of a message would exist on any one node until the last recipient elected to delete it or save it in another location.|
|Each instance of the program would operate independently of the status of other nodes or the University’s local- and wide-area networks (such as they existed at the time).|
|Delivery would be guaranteed.|
|Attributes, considered to be part of a letter-based postal delivery system, such as return receipt requested would be implemented.|
|A full management interface with account maintenance, environment status and debugging tools would be developed.|
|The electronic metaphor of all the other elements of the interoffice, inter-organizational paper mail system would need to be incorporated: inbox, outbox, folders, memo structure, address book and other important features, that we now have in modern email systems.|
Our software tools were relatively primitive. A FORTRAN IV compiler with restrictive variable naming conventions and lacking intrinsic file system access; a non-relational, hierarchical database management system; and a simple networking environment that permitted static routing among nodes in a predetermined mesh. These tools ran on the HP1000 platform, a real-time environment not particularly optimal for the kind of development we envisioned.
These impediments turned out to be of little consequence, but certainly upped the complexity of the programmer’s task and by some measure, Shiva’s accomplishment. In fact, the inflexibility of the development and execution environment turned out to be somewhat serendipitous. Our project combined the attributes of both the interoffice memorandum and paper mail systems. The FORTRAN IV compiler limited variable names to six characters. Moreover, the RTE/IVB operating system running on our HP1000 computers limited process names to five characters. Did I hear EMAIL? Of course! Our new service was electronic and it combined many if not all of the characteristics of paper mail. I can attest that Shiva was the sole author of the entire EMAIL program and system. A few years later, Shiva, obtained a copyright on the name. Nearly 500 users used the system. The rest should be history.
Shiva had written some 35,000 to 50,000 lines of FORTRAN code across more than a dozen cooperating processes that communicated within a node and across the Laboratory Computer Network. I recall that on formal launch day, we filled a large lecture hall at the New Jersey Medical School with technical staff and other parties that were fascinated by the work Shiva had done. Here we were, all of these people: IT professionals, administrators, family and friends to learn what Shiva had done. Multiple screens and white boards filled with charts, “screen shots” and flow diagrams kept everyone‘s attention. There was a bizarre aspect that pervaded all of this. The presenter was not a distinguished scientist or clinician from CMDNJ or some other vaunted institution, but rather a very young man with a fascinating story of ingenuity and determination.
There is much credit to spread around the vast community of academic, industrial and military researchers and engineers who eclipsed the industrial revolution with their contributions to computer science and computer and network engineering. We take no credit where it is not due.
We will, however, stand firmly for the innovation that took place at a health sciences institution, an unlikely venue for the work we did. Our incentive was not fame nor fortune, but rather a challenge that arose from our own experiences and our desire to take on a challenge and place our faith on the resources of a 14 year old student from Livingston, New Jersey, who was disciplined and found a way to come to Newark, NJ to work.
There is a larger story here, one that should be evident by now. Innovation can happen anywhere, anytime by anyone. The sooner we embrace this truth, the sooner our lives will be enriched by the thousands of other “Shivas” that do not have the luxury of working in the established bastions of innovation, but nevertheless have the intellect and drive to make big contributions.
© 2012 - 2017. International Center for Integrative Systems. All Rights Reserved.