Proceedings of the REAPS Technical Symposium concerning the computer systems at Kockums.

The primary purpose of this discussion is to introduce a new version of the REAPS Program. In 1971 a Maritime Administration (MarAd) Advisory Group recognized a void in the area of computer aided shipbuilding. In response, MarAd acquired rights to the AUTOKON-71 system, the most widely used system in Europe. MarAd and the participating shipyards recognized the need to provide maintenance and support for the AUTOKON system. That effort was sponsored and paid for jointly by the industrial users and the government. It soon became apparent to all concerned that there was much more to be gained from computer applications in the shipyard than just running the AUTOKON system. A total shipyard program for computer automation beyond AUTOKON was needed. It was this decision that gave birth to the Research and Engineering for Automation and Productivity in Shipbuilding (REAPS) program; a joint participation program involving five shipyards, MarAd, and IITRI. Its purpose was to identify and address common problems in ship construction. The advantages were obvious. Participants could pool both the technological know how in identifying and solving problems and their resources to solve a common problem only once not repetitively at every shipyard. The REAPS program, a new concept in cooperative developments among several shipyards, was working. One thing began to change--the objectives of our development projects. Originally, they were oriented to a specific computer system, AUTOKON; now they were becoming non-system oriented, standalone modules with no relationship to a specific computer system or software package. A new concept was needed. The "new" REAPS program as it has evolved to date is a non-systems oriented program with the separation of all AUTOKON related activities. The overall concept of the new REAPS Program consists of five basic elements: Advance Planning, Technology Assessment, Development Program, Technology Information Services and Discretionary Development.

Over the past year and a half, five participating shipyards have been preparing labor time standards using MOST Computer Systems on a time sharing basis. The result has been the development of separate databases covering the following operating areas: blast and paint--platen and dock areas; Electrical--shop and outfitting; main assembly; fabrication shop; and staging erection and teardown--platen, dock and ways. The ability to transfer data from one yard to another is discussed, as well as the methodology for such transfer. The actual use of transferred data and its application is covered to the extent that it has occurred up to the date of the symposium.

An investigation of an approach to a U.S. Navy sponsored shipbuilding technology program is discussed. An approach is recommended, and a detailed project plan for a shipbuilding technology program is proposed. The U.S. Navy has announced its intention to initiate a major program for the enhancement of shipbuilding technology in the United States. The objectives of this program are to improve the quality, cost, and construction time for future U.S. Naval Ships, and to strengthen this country s shipbuilding industrial base. This motivation is heightened by the Administration plans to increase the Navy s fleet to 600 ships by 1988. This program is currently budgeted as a six-year, $80M effort, though its format has not been defined. Previously the Naval Sea Systems Command had contracted with SofTech, Inc. to assess Air Force initiatives in manufacturing technology with respect to Navy needs. Both the Navy and the Air Force have established programs to promote computer-aided manufacturing which have differed markedly in budget, in approach, and in industry involvement and acceptance. SofTech was directed to consider the applicability of the ICAM (Integrated Computer-Aided Manufacturing) Program approach to a Navy STP (Ship building Technology) Program. This paper recommends an approach to the planning, management, and integration portion of a national, participative Shipbuilding Technology Program (STP). These recommendations are SofTech s, and are not to be construed as government policy. They are based on SofTech s initial analysis, and on pertinent comments received from individuals in the Navy and the shipbuilding industry.

Proceedings of the REAPS Technical Symposium. Paper No. 16: AUTOKON-76/79-An Affordable Implementation on Prime Minicomputers. The version that is about to be implemented on the PRIME mini computer is basically AUTOKON-79 which may be defined as AUTOKON-79 with some improvements as well as several major new features. The very rapid development of the computer industry with steadily falling prices have changed the outlook with respect to computers and their uses. It is presently feasible to use inhouse computers even for very small operations to run the entire AUTOKON system with its present capabilities as well as the developments that are about to be implemented. The traditional way of processing in a batch made with a waiting time for turnaround have given way to an interactive mode of processing where results come much sooner. Gone are also keypunching, job submission, etc. No longer is it necessary to have large number of pages printed out. Output can be examined by means of an editor, i.e. a system program enabling the user to go through print files as well as other files.

The paper discusses a number of facets of Computer-Aided Ship Design and Construction (CASDAC) in which the writer has been involved. A brief history of computers in the Navy is given, some notes on the CASDAC project, the flavor of two recent programs, Navy planning and philosophy in detail design. and construction, some notes on the Computer-Aided Piping Design and Construction (CAPDAC) project, and finally some notes on the increasingly important role of computer science. The U.S. Navy has a long history in the use of computers in shipbuilding. In May 1944 the first computer came into operation at Harvard, the Automatic Sequence Controlled Calculator -- the Harvard Mark I. This was designed and constructed by Professor Howard Aiken -- at that time a Commander in the United States Navy. It was the Bureau of Ships which first sponsored the operation of this calculator and some of the first problems attacked originated from the Bureau. In 1952, the Applied Mathematics Laboratory was established at the now David W. Taylor Naval Ship Research and Development Center (DTNSRDC) to initiate computer service to the Navy. For this installation the Univac's 6th computer was installed in 1953. Early work included shaft vibrations, shell stiffening, propeller design, underwater sound intensities, pipe stress analysis, and nuclear reactor design. Within a year, this computer was operating around the clock. By 1958, clients included personnel from the naval shipyards processing programs associated with their ship construction program. By 1960 naval shipyards possessed their own computers and programs were in operation for tank capacity tables, hull deflection, voltage drop, shock mounts, sound isolation, mast calculations, weights and moments, propulsion shaft bearing reactions, pipe bend calculations and pipe stress analysis.

To complement the functions which are not furnished by AUTOKONv1, the Italcantieri Company has developed a system, named SCAFO, that solves all the problems related to the shell structures and some related to the internal panelling. It includes the following modules: Frame Table definition, Primary Inner Structures Loading (panels), Shell Landing, Primary I Structures Landing, Section Drawing, Table of Detail (interface SCAFO - Al), Body and Shell Expansion Plan drawing, Shell Expansion, Templates. Long Frame and Transverse Frame expansion (interface SCAFO - Al), Jigs, block marking and controlling data, Bevels offset, Painting Lines Heights, Draft Marks and a General Base List. In addition to the above principal modules, other programs are available; they give us offset tables for frames, decks, longitudinals and other structures. This system and a large library of A. 1 norms gave us the opportunity of merging shipyard and headquaters divisions.