TO FROM : SUBJECT: Ln. AE OERG ERC January 11, 1974 SUMEX Executive Committee File T. Rindfleisch LCR Action Items and Notes From the Afternoon Session of the Second SUMEX Executive Committee Meeting - January 9, 1974 Attendees: (See attached agenda A) Morning : J. Lederberg, S. Amarel, W. Baker and C. Brewer Afternoon: As above plus T. Rindfleisch and E. Levinthal We discussed the machine configuration and current delivery schedule (see attachments B and C). A change in the configuration was proposed as in diagram "B" to ensure that the machine be made operational as early as possible. This consists of hooking the system to ARPANET through the standard BB&N TIP/PDP-10 inter- face initially and interposing the PDP-1l at a later time. The long term attractiveness of the PDP-1l remains in the ability to off load the TELNET protocol from the PDP-10 and perhaps to provide alternative file system access when the SUMEX machine is down. No objections to this approach were raised. The hardware delivery schedule was presented identifying the two current problem areas: 1) The proposed slip in line printer delivery until March 31 by Data Products and 2) The as yet tentative TIP delivery schedule. Dr. Baker offered to assist in accelerating delivery. This was deferred pending the outcome of on-going vendor negotiations to solve the problems. Dr. Amarel described the PDP-10 facility they plan to implement at Rutgers saying they were having problems locating the necessary expertise to mount the TENEX software system. We have the same problem and are trying to sélve it through collaboration with local TENEX groups (IMSSS, SRI, AI Lab., etc.). We offered to assist Rutgers as best we can (e.g. having one of their people come to Stanford to learn the system) to develop the necessary capabilities. Memo to SUMEX Executive Committee File January 11, 1974 Page 2 We discussed the general question of file security provisions in TENEX (see pp 30 ~ 45 of the "TENEX EXECUTIVE MANUAL"). There was some concern over the conflicting needs of confidentiality for some administrative and patient medical data as opposed to the general desire for an open environment condusive to sharing both internally and externally. We agreed to make a presentation at the next meeting of the available file security system to further evaluate the need for selective encrypting of data. We discussed the preliminary announcement of the SUMEX resource and approved the news release in attachment D. There was general agreement on a two~phased announcement process; an initial general release (press, ARPANET News, etc.) and a more detailed solicita- tion of participants after the system is established and the Advisory Committee set up. The immediate need for a more detailed write-up of SUMEX objectives and capabilities was emphasized to be available to BRB, Stanford, Rutgers, etc. to support informal discussions with interested people about the project. We said we would generate such a docu- ment in several weeks. Dr. Baker requested a "Mission Statement" for the Stanford half of the project (SUMEX) describing its research objectives, organi- zation, and capabilities. This is needed by BRB for administrative reasons. Dr. Lederberg pointed to some general quidelines he was formulating to screen potential SUMS users such as inability to obtain necessary computing support from other Stanford sources (SCIP), and relevance of the research to Al. These will evolve as potential users become more aware of the facility and its goals. Dr. Lederberg agreed to formulate an initial SUMEX mission state- ment. The problem of terminology was discussed from the viewpoints of overall organization and operational access through the ARPANET. There was general agreement that Dr. Lederberg's descriptors, while long, were appropriate: Overall Facility = National Shared Computer Resource for Health Research at Stanford (NS CRHR-SU) Half of the facility is allocated to "SUMEX" (Stanford Medical School users) Half of the facility is allocated to the "National Program for Artificial Intelligence in Medicine" (NPAIM) The ARPANET designation for the NSCRHR