prll1g ftedduo~e~aid to /3 iunclassified5/ mi · the liist day and a-halt otf the workshop...

AD-A171 326 PRLl1G FTEDDUO~E~AID TO /3r ~ ~~ NW . (U) NLIRSQINI A~fESSOAESINCARLI NTON VA 13 NAY Bb 14f; D-E934IUNCLASSIFIED5/ MI

I~hI~1&0 1220

II

IlaU ,___

111.25 11111 1= 111.6Ilii.- 1111-_ ii

!CROCOPY RESOLUTION TEST CHART

NATIONAL BUREAU OF STANDARDS 1963-A

I. -h *. *

OO/T(3

(0N

REPORT OF THE PROCEEDINGS OF THE

DOD AUTOMATED STANDARDIZATION WORKSHOP

AT THE SHERATON NATIONAL HOTEL, ARLINGTON, VA.

MAY 12-13, 1986

Kilkeary, Scott and Associates, Inc.2009 North 14th StreetArlington, VA 22201

D T IC N00140-85-D-E034

EL ECTEiDefense Standarization Program OfficeAUG 29 1986 , OASD(A&L)

5203 Leesburg Pike, Suite 1403Falls Church, VA 22041-3466

)DISTRIBUTION STATEMENT A.Approved for public release;

u. distribution is unlimited.

" - ,m,,mm~mm nm & m mm 1

FOREWORD

This publication provides a Report of the Proceedings of theDOD Automated Standardization Workshop held on May 12-13, 1986.Appreciition is expressed to the Systems Engineering and Stan-dardization Department, NAEC, Lakehurst, N.J., for their sup-purt in this undertaking. Material used in the preparation ofthis Repu rt was assem,,led and compiled by Kilkeary, Scott andAssociates, Inc., 2009 North 14th Street, Arlington, VA. 22201

AccP'"

N TI2

RE: FOUO, Page 80 .Page 80 is a sample page. Delete the FOUO.Per Mr. Lee Rogers, .S,0 0

Dist

I1l

TABII. OF C()NTENTS

PAGE

Purpos t and Uhjt,.-tivw; I

Organization, Stru,: t!re and Attendance 1

Opening Remarks I

l );t ol Prese.ntations 2

S-'.psi.; of Presentations 3-13

Automated Specf fication., and Standards Tnformation System(ASSIST) 3

Ccptittrizt-d Standardization Search System (CS ) 4

C.w, iput.r-Assisted Ship Specification System (CASS)tnd Spe,:ifi:ation Improvement Program InformationSystem (SIPIS) 5

w.nputcr Generated Acquisition Documents System (CGADS) 6

Teehrlica[ and Managerial Support Environment/DOCWRITER('r EMS E/ n)CWR IT ER) 7

Automat*d Engineering Doctimentation Preparation System (AE)PS)andd MICOM Integrated Documentation and StandardizationSvstv,,n (MIDAS) 8

'e,-hni,-i at bt;i/(onf igoiration Management System (TD/CMS) 9

"helt Ad,.quacy and Assignment (A&A) Index 10

hjo;nev rlng Criteria Management (ECM System) and.Vt~om.itld FaqiiitY Engineering nformation System (AFEIS) 11

hc Army Spe,-ifi,-ations and Standardization System (DEPSOMIS) 12

lhle 001) Index of Specifications and Standards (DODISS) and,N.tvy Print oti Demand System (NPODS) 13

Gu.jl i!;cussion 14

I;o).,lud t g Rt.,ark- 15

I$

At tac hme nt s

I. Agenda 172. List of Attendees 21I. Briefing Material - ASJIST 294. Brtefing Material - CS 495. Briefing Material - CASS and SIPIS 61b. Briefing Material - CGADS 991. Btteftng Material - TEMSE/DOCWRITER 1158. Briefing Material - AEDPS and MIDAS 1499. Brietfng Material - TD/CMS 1771). Brieling Material - AA Index 207Ii. Briefing Material - ECH and AFEIS 22512. Brtefing Material - DEPSOMIS 25513. Briefing Matprial - DODISS and NPODS 275

!I

iI

i'a

RI'POR'r OF TiHE PROCEEI)INGS OF rHEI)Oi) AUTOMATFED STANDARDIZATION WORKSHOP

AT THI' SIHRATON NATIONAL HOTEl,, ARLINGTON, VA.MAY 12-13, 1986

PURPOSE AND OBJE*CTIVES:

K'v letter dated February 19, 1986, the Director, Standardization and Data Man-

.tgement (SDM) OASD (A&L), advised the DOD agencies of an on-going study ofoxi-;t,,Ug computer systems and data bases used to support participation in the

Ietens, Stlndardization and Specifications Program. The study was particularlyfw'.ed on svstems and data bases dealing with the identification of successive

ltvs o! telerences within specifications, standards and other acquisition

dowimeiRtt, as well as those used in the preparation, identification, management,and rajntenanice of these documents and their utilization in the acquisition pro-

,es,;. The puipose of the study was to determine the degree of commonaltybetween existing systems, whether any of them could be used by other activities,,lld whether iny could be used in conjunction with the acquisition streamlining

proces;s. Addr(::;sees were requested to identify any data base falling within the

established criteria and provide a short description of it for staff review.Their resp()nses aire Included as the first page of each System presentation.

Alter review of the responses to that letter, selected agencies were requestedto attend this workshop to discuss their systems in greater detail and to offerrecommendations regarding their potential application and use on a broader DOD

wide basis.

ON)GANIZATION, STRUCTURE, AND ATTENDANCE:

The liist day and a-halt otf the workshop consisted of presentations by agency,epresentatives des;cribing their data base(s) with follow-on questions and,.,swers. The latter part of the second day was spent in general discussion and:he development of recommended actions, which are provided later in this report.

The agenda for the meeting is at attachment 1.

rlier ,r re 52 participants in the workshop, including representatives from OASD(AL, the Army, Navy, Air Force, DNA, and interested industry concerns. A list

,t the workshop participants is at attachment 2.

Th,, workshop was co-chaired by Messrs Lee Rogers and Gregory Saunders, Senior

Staf t Ihtigiroers from the Defense Standardization Program Office.

1,11%. INt" 10EMARKS:

: ,, ii r i ,' op'ni' r ,, , 'marks, Mr. Peter Yurcisin, Director, Standardizatio'n

,Do L~ita ,1antagement, (oASD (A&L) welcomed the participants and thanked them forthir i :krest in this ,,tudy. He discussed the background leading up to the

Iiiit',ti,,, of the study and commented on efforts by some of the agencies Indeveloping data bases t) support the acquisition process and to provide bettervisibility over activities involved in the Defense Standardization and Specifi-

cation Program. He empha,ized the importance of this workshop and his interestit, capitalizing on thotie existing systems and data bases that may enhance the,o*(pilsition process, ,treamlining initiatives, and management of standardization

1 o i u m mimu -a

pro)gram .activities. HL' also emphasized the interest expressed by the Congressin I)ol)s etrorts to more efficiently control and utilize information already atits di-;posal, through the use of automated techniques. In his remarks, Mr.Yi'ircsin also described his recent experiences in international standardization,parti-iLarly with AC/315, NATO Standardization Group. He went on to desribe,he emptiasis placed by that group on the need for a comprehensive international.indirdization data base in order to better manage the myriad of on-going stand-.trili zation ac'tivities, to avoid duplication of effort, to establish priorities,to) ,,aisure progress and to improve planning and programming in the internationalstandardiza'tion arena. Mr. Yurcisin also emphasized the need for the standard-izition comminity to take a more active role in the acquisition process and tolook tot ways itt which existing data bases and the information in them can beexpanded to support other users and be made more readily available to thoseinvolved in the acquisition system.

P;.'1SEN'1'XT IONS:

A synopsis of each presentation follows in this order:

,, mted Specifications and Standards Information System (ASSIST)nputer i /.,d Standardization Search System CS

3

Computer-As: ited Ship Specification System (CASS) and Specification ImprovementProgram [itformation System (SIPIS)

Computer Generated Acquisition Documents System (CGADS)T,.-hnicaL ;iind Managerial Support Environment/DOCWRITER (TEMSE/DOCWRITER)Niit:imatod VI.igineering Documentation Preparation System (AEDPS) and MICOM Inte-

grated I)oumet tation and Standardization System (MIDAS)Techicat Data/Cnfiguration Management System (TD/CMS)Th, Adlquacy and Assignment (A&A) IndexK;.,Jiering Criteria Management System (ECM) and Automated Facility Engineering

Information System (AFEIS)1hi Army Spe,-ifications and Standardization Computer System (DEPSOMIS)The DOD Index of Specifications and Standards (DODISS) and Navy Print on Demand

System (NI'ODS)

:-H )wing !e D)OD presentations, Information Handling Services and Ziff Techni-SiI Tritormat ion Company presented an overview of services available from their,nmpaities, and discussed their ability to support the DOD within the area. of

fi il t 2Kpftt ise.

2 6

Au tomated SpecificatIons and Standards Infornmation System (ASS I ST). Presentedby the Naval Air Engineering Center, Lakehurst, NJ

This d.ita base and information retrieval system is located at the Naval AirI'ngineering Center, Lakehurst, N. J. The data base presently includes allDOIjISS information on approximately 32,800 Military and Federal SpecificationsStandards and other standardization documents, together with all of each docu-ments primary references. There are an additional 10,000 documents in the base!or which all data except primary references are included.

The system will provide a variety of management information on specifications,ind standards and other standardization documents; will provide greater visibil-ity over documents to be invoked by reference in the acquisition process; willprovide support to the acquisition streamlining process and will improve thecurrency, accuracy and management of standardization documents.

The system can provide support to a variety of users, including standardization

program managrs, standardization document engineers, system document engineers,acqisition manager, and supply managers. The following information is includedfor each document in the base: document number, issue indicator, date, documenttype, title, all primary references, FSC/AREA Class, validation date, status,agutncy interest, and QPL requirement.

Preformatted output reports include the following: Specification Tree (Pyramid),Reference List, Keyword Index, QPL Requirement, Overage Documents, AlphabeticalIndex, Documents as Preparing Activity, Interest Other than Preparing Activity,Cancelled Documents, Age and Cog Code, and Referenced by Other Documents (Refby). Other reports to be added include Non-Government Documents, Metric Docu-ments and High Cost Driver.

ASSIST Is a multi-user system. There is presently limited access to the system,using a 300/1200 Baud Voice Grade telephone line link. It does not have AD Hocquery capabilities. It is a data processing system residing in an IBM 4341mainframe computer at NAEC.

'the point of contact tor this system is Mr. Thomas J. Marchesani, Naval Airh:igiineering Center, SLSI)-93, Lakehurst, NJ 08733-5100, telephone A/V 624-7429 orA/C 202-323-7429. A copy of the presentation is at attachment 3.

3

Coinputkritzed Standardization Search System (C.S-3). Presented by Army MaterialsTechnology laboratory, Watertown, MA.

The ,:S3 data base is located at the Army Materials Technology Laboratory, Water-tow., MA. The system was established for the storage, retrieval and analysisot specifications data on a variety of materials such as ferrous and non-ferrousmetals, plastics, composites, ceramics, rubber products, finishes, and adhesivesas well as materials related processes and test methods. The data base pres-v;;tly stores iiformation and data from over 4300 materials and materials relatedspucifications, standards and other standardization documents covering 543 fed-eral supply classes.

The system enables searches on text and date fields within interrelated groupsot documents, test methods, requirements, cross reference material, referenceddoccuments, or other salient information contained within the body of a specifi-cation or standard. The system is used in the preparation of new materials or,in.nirials related specifications and standards and for the maintenance of exist-

ing dcuments. The system also provides information concerning standardizationaccompli0iments and performance, supports the overage document review and vali-dation program, and is used to prepare standardization program plans and annuala:1d 0erindiv stand.trdization reports.

system hardware tised to store the data base is a Digital Equipment CorporationVAX 11/780 Cormntier which is accessed in a time shared environment through mul-.,plexi ideo terminals which share logic through a single communications cir-ckiit. (5 was developed as an application of the DRS management element. ItcinLain s a unique command language allowing users to query and update the systemand povides two interactive modes of operation: an automatic menu driven mode,dsig-ned for ease of use and a manual mode which provides maximum retrievaltlexihllitv and reporting facilities. The system may be accessed in a multi-iset env i I oni:t.

Th.- point of contact for this system is Ms. Kathy Bamberg, U.S. Army MaterialsT#rhnology Laboratory, SCLMT-MSR-ES, Watertown, MA., 02172-0001, telephone, V 915-5567 or A/C 617-923-5567. A copy of the presentation is at attach-inat [4.

4nn

Computor-Assisted Ship Specification System (CASS) and Specification ImprovementProugram Information System (SIPIS). Presented by Naval Sea Systems Command,Arlington, VA.

Thc CASS system is located at the Naval Sea Systems Command, Arlington, VA. Iti , a living version of the "General Specifications for Ships of the United:.tates Navy" (GENSPECS), which is the Navy-s generic ship "building code" -pub-lished once a year. It is also a source for development of the initial versionot , s pcific ship's specification. The "Gen Specs" provide system levelre'juirements for ship acquisition, provide standard requirement/texts, providesShip Work Breakdown Structure format and at the present time contains some 2500referenced documents. A separate program compiles a list of these referenceddocuments and identifies the "Gen-Spec" section or sub-section where the refer-e.'cs .re used. This list is then used to monitor the status of each document,.0 t. identity potential problem references.

1' scs of the system include NAVSEA engineers, line managers, ship design manag-ersv, and ship acquisition managers. The system is presently stored on a remote1B-30)3 mainframe, to be transitioned to an in house IBM-3083 in the nearfILkre. It has multi-user capability and remote access through 1200 bauddidL-up using YTERM software from IBM PC.

The SIP management information and retrieval system, also located at NAVSEA, isdesig:;ed to provide a variety of information concerning documents critical toNAVSEA acquisition programs. These documents include Military and Federal Spe-cifications and standards, NAVSEA Standard Drawings, Design Data Sheets, andother miscellaneous documents. Information for each document in the baseincludes number, title, type document, issue/revision, FSC Class, date, valida-tion date, status (current, or revision required), NAVSEA interest, and cogni-.anlt code. Milestones are provided for documents under revision.

Ut;ers of the system include NAVSEA engineers, line managers, ship design manag-ers and ship acquisition managers, Output reports provide a listing of all,docuine:.-4 of interest to NAVSEA (with the elements of data cited above), which.ire used as a means of control of spec-related work and to determine the statusof documents to be used in procurement. The system is presently stored on aremote IBM-3033 mainframe, to be transitioned to an in-house IBM 3083 in thenvar tuture. It has multi-user capability and remote access through 1200 bauddial-up using YTERM software from IBM PC.

NAVSEA is also developing a specification referencing (spec-tree) system usingan adaptation of the "ORACLE" DBMS, to be made a part of the CASS and SIP data

lit, pouti ot contat . for this system is Mr. Norman J. Griest, Naval Sea Systems,.lmd,:, SlA-b'~, tWashington, DC, 20362, telephone A/V 222-0490 or A/C2)2-092-0491). A copy of the presentation is at attachment 7.

a)

(:imputer Generated Acquisition Documents System (CGADS). Presented by AFSC,Electronics Systems Division, Hanscom AFB. MA.

riis data base is lorated at the AFSC Electronics Systems Division, Hanscom AFB,-t.. The data base is used to prepare drafts of system acquisition and manage-

me7: doctuments such as Statements of Work (SOW) and Contract Data RequirementsList's (CDRL) for each phase of the development cycle, production and deployment,Reliability Centered Maintenance (RCM) Analysis, Multi-year Affirmative ActionProgram Mini-Plans, Program Management Plans, Acquisition Plans, and Test andEvluation Plans (TEMP). The system is designed to standardize, simplify, and,tomate the preparation of Requests for Proposals.

Thi dati base stores the paragraph text of tasking type documents such as Mili-taty Specificatiuns and Standards and applicable Data Item Descriptions (DIDS).rlrough the use of a menu and simple prompting questions it will select andprint in SOW format the specific paragraphs of each tasking document required tobe imposed. Through the process of selectively applying specific paragraphsfrom each tasking document and its DIDS, tailoring of the SOW and/or the RFQ isachieved and its format standardized.

P1 iary users of this system are acquisition/procurement offices, includinge-gineering, reliability and maintainability, configuration and data managementand logistics. It also assists standardization managers by carrying out theralboring process during the preparation of the SOW.

The system is stored on a VAX 11/780 computer. Remote access is available,using conve-.tiunal AUTOVON or commercial telephone lines. A VT-IO0 or compa-tible rem% te terminal is required. The system has DOD wide application and isnow used by the Air Force, Army, Navy and other government agencies. Futuretliancements include the addition of other output products such as Task Orders,Source Selection Factors and Standards, Instructions for Preparation of Propos-

Is, vstem Specifications, and Operation and Maintenance RFPs.

The point ot contact for this system is Mr. Richard O'Neil, AFSC ElectronicsSv';:ems Division, ESD/PLEA, Hanscom AFB, MA., 01731, telephone A/V 478-2843 orAiC 617-377-2843. A copy of the presentation is at attachment 5.

66

luchnical and Managerial Support Enviroranent/DOCWRITER (TEMSE/DOCWRITER). Pre-sented by AFSC, Space iJLvision, Los Angeles, CA.

This data base i3 lcated at the AFSC Space Division, Los Angeles, CA. Thesystem is an automated data base which assists technical specialists i writingstructured documents and managing project-related information. It provides adisciplined environment for preparing system specifications, Statements of Work(SOW), Contract Data Requirements Lists (CDRL) and other structured documeftsused In acquisition and for capturing information related to each requirement orta-,k contained in those documents. The system is an integrated word processor,a Data Base Management System, and report generator. It is used to author andmanage structured documents, as a repository for corporate knowledge, and totrain acquisition managers.

The system provides a pre-established outline for each document that it pro-doces, for example, a specification structure based upon MIL-STD-490, a SOW:tructkire based upon a format developed by the Space Division. It providesttt'orial information on how to write the document and offers additional informa-tion associated with each requirement and task, such as its source, justifica-tion, traceability to higher level specifications and other source documents,test/verification methods, and the like.

DOWRiTI-R has a hierarchical structure, hiving four major functions. These are:

o The tutorial function, which encompasses information on acquisition manage-melt, on writing the SOW, CDRL and WBS documents, and on operating the system.

o The operate function, where the document creation and writing takes place.

, 'he browse function, where the user may view but not alter the contents ofthe data base.

o The reports function, where reports are requested.

The sy,:,tem operates on IBM 3278 and IBM 3279 terminals. It is a multi-user sys-txm and cai be accessed remotely with ASCII terminals via commercial telephoneI ine s.

The witnt of contac,' for this system is Mr. Gerald Hyman, AFSC Space Division,SD/AL, P.O. box 92960, Worldway Postal Center, Los Angeles, CA., 90009-2960,telephorne A/V 833-0831 or A/C 213-643-0831. A copy of the presentation is atit iaclument 6.

lnl 7,nn nnninn nnm N NHm I i U ln NNINinI

Automated E:'.gi neeri::g Documentation Preparation System (AEDPS) and MICOM Inte-grated Documentation and Standardization System (MIDAS). Presented by the ArmyMissiles Command, Huntsville, AL.

The AEIPPS system is located at the Army Missile Command, Huntsville, AL. It isies>,ned to provide Military Specification Exception (MSE) documents to be usedtogether with an existing military specification for the procurement of non-s:iidard parts. AEDPS takes advantage of the fact that most special or uniqueapplication items call for relatively minor exceptions to an existing militaryspecification. By following the procedures prescribed in DOD-STD-35 and input-Ling the selected codes and values required, the user can have the computer pre-pare an exception document that is ready for use in procurement. Informationpresently stored in the computer includes standard text paragraph data and DOD-STD-35 codes used to prepare an MSE for any one of 124 families of parts; codesind vale-s used in the preparation of all existing MSE-s; user data; sources ofsupply including manufacturers part number, name, and FSCM; management informa-tion data; document designation including date and references; and tracking andcontrol data.

Svstem users include every major contractor and sub-contractor that the ArmyMissile Command is involved with, every project/commodity manager at RedstoneArsenal and the MICOM standardization activity. Sources for data included inthe base are user generated requirements, DODISS, CDRL, and delivery extractiondata including Engineering Change Proposals, drawings and specifications.

I'he MiDAS system is a management information and reporting system used to cap-tlire, manage and manipulate the large amounts of data derived from and used insupport of all MICOM contracts. It provides a greater degree of awareness and,ontrol in the management of Standardization, Parts Control, and EngineeringDoki,mentation. The system has 18 major data files including topics such as non-'i::dard parts, missile specifications, common item drawings, GIDEP, automated

it en reductinn, drawing control, engineering document data, document numberassignments, nomenclature recording and reporting, standardization document pro-ject recording and reporting, and AEDPS. The system is stored on a Honeywell: .vel 6 Model 57 computer having remote access and multi-user capability.

The point of contact for these systems is Mr. Jerry Nabors, U.S. Army Missile(:ommand, AMSMI-SE-TD-ST, Redstone Arsenal, AL., 35898-5276, telephone A/V74b-13Y) or A/C 205-87b-1335. A copy of the presentation is at attachment II.

. , .,.,,,,, .mm,.,nmmmmm mmmm im mmlmmmmm • m~m m mm .mmm n mllm mm m

Technical Data/Contiguration Management System (TD/CMS). Presented by BelvoirResearch and Development Center, Fort Belvoir, VA.

The rD/cMs system is located at the Army Belvoir Research and Development Cen-ter, Fort belvoir, VA. It was designed to maintain an integrated digital database ,i technical data in support of engineering and procurement actions andprovide identification, control and status accounting functions for engineeringdocumentation, i.e., Configuration Management. Source documents which comprisethe Tochnical Data Package (TDP) and provide input to the system include: engi-neering drawings, parts lists, Military, Federal and Industry Specifications andStandards, Engineering Change Proposals, Deviations, Waivers, SpecificationChange Notices and Notices of Revision. Data elements in the base include docu-me:nt identification data, revisions, nomenclature, manufacturers part number,Federal Supply Code for Manufacturers (FSCM), document size and number ofsheets.

System users include design and production engineers, standardization and pro-curement offices, contiguration management personnel and data repository staff.Output reports include over thirty user requested reports and over thirty otherreports used for quality control of data and the system. These reports pinpointproblem areas, identify missing documents, identify erroneous data, identifyaction necessary to finalize a data package for procurement, and identify engi-rpecring change action required. The most important aspect of the TD/CMS is itscapability to ensure that documentation is complete and that the changes areidentified, thus allowing TD/CMS to maintain the baseline technical. documenta-tion, track changes, generate status reports, and update the baseline for newprocurement.

The system is presently housed on a CDC Cyber 835 computer, to be transferred toan iBM 4341 in the near future. It is a single user or batch processing system.Remote access is available for data input and system support via telephone linecn'emunication link from terminals with modems.

The point of contact for this system is Mr. Richard H. Goehner, U.S. Army Bel-),oir Research, i)evelopment, and Engineering Center, STRBE-TC, Fort Belvoir, VA.,

22060-5606, telephone A/V 354-5789 or A/C 703-664-5789. A copy of the presen-tation is at attachment 9.

9

-rte Adequa'y and Assignment (A&A) Index. Presented by the Army Troop SupportCommand, Natick Research and Development Center, Natick, MA.

This data base and information retrieval system is located at the Natick

Research and Development Center, Natick, MA, The system was designed to iden-tify and provide the current status of all technical data packages for which theCenter is responsible, together with related items of supply, and standardiza-tion, i.e., engineering drawing numbers, NSNs, standards and handbooks. The

technical data package consists of a basic document and all applicable amend-ments, deviation lists, notices, supplements, engineering drawings, and etc. Thetechnical data package does not include subsidiary reference documents.

The data stored for each document includes: FSC Class, item material manager,Ceinter cognizant code, document age, ADCOP designator, engineering supportrp-quirements, validation for procurement, referenced drawings, NSFs, active pro-iet assigned for updating, and document responsibility, i.e., PA, Custodian or"ICA. The primary purpose of the AA Index is to indicate to the responsible DODpro(kiireme:1L activity the current data elements that make up each TDP and toindicate which TDPs are valid for use in immediate procurement. The secondarypurpose is to provide visibility over and current status of all TDPs assigned tothe Center as preparing activity, military coordinating activity, or Army Custo-diian.

The A&A Index serves as a multi-purpose management tool, i.e., inventory access,ready identification, current status, and procurement support. Procurement Cen-ters/Activities are furnished separate updated monthly reports on the currentstatus of TDPs prepared by Natick for items for which that Center/Activity hasprocurement responsibility.

The point of contact for this system is Mr. D. E. tuppino, U.S. Army NatickResearch, Development and Engineering Center, U.S. Army Troop Support Command,DEPM, Natick, MA., 01760-5014. Telephone A/V 256-5221 or A/C 617-651-5221. Acopy .)f the presentation is at attachment 12.

'a

10

Engineering Criteria Management (ECM) System and Automated Facility EngineeringInformation System (AFEIS). Presented by the Naval Facilities Engineering Com-

mand, Alexandria, VA.

The ECM system is located at the Naval Construction Battalion Center, Port Huen-eme, Calif., and is managed by the Naval Facilities Engineering Command, Alexan-

dria, VA.

ihe system is a management information system used to manage the development and

revision of all facilities engineering and design criteria documents produced or

used by NAVFAC. It is an inventory of NAVFAC criteria and a plan for criteriaupdate. The main objectives of the system are to determine criteria require-

ments, to plan and execute the Navy's Facility Construction Program, to maintainthe status of all criteria documents, to track scheduled and actual documentpreparation milestone dates and to monitor progress of planned versus actual

performance.

The ECM system manages an inventory of over 300 NAVFAC Guide Specifications, 700Military and Federal Specifications and Standards, 150 Standard Drawings, 130Design ainuaLs and Publications, and over 550 Definitive Drawings. The system

is an on-line, interactive MIS, written in COBOL and resident on an IBM 4300

series computtr at Port Hueneme, CA. The data base is accessed via remote ter-

minaLs located at the EFD's and NAVFAC headquarters and allows direct access forupdates and verification and to queue reports to the remote printer. It isintended that this system will be integrated with the Automated Facility Engi-

neering Information System (AFEIS), a description of which follows.

The AFEIS system is a faciLities engineering information system under develop-ment by the National Institute for Building Sciences (NIBS). NIBS contemplatesputting all government and non-government facilities engineering and design

criterii, i.e., Military and Federal specifications, design manuals, definitive

drawings, military handbooks, and a wide variety of non-government standards, on

a master data base and distributing it with search software designed for easy

user access. It is planned that a master data file, a text search index and a

word processing software package will be mastered at a central location managed

by NIBS. A data base copy on magnetic tape will be used to produce master copydisks -rd read only memory disks in sufficient copies for distribution to sub-

;v r Lbe rs.

:urretly a system pilot test is being conducted by the NIBS and is planned to:e operational for Army and Navy Guide Specifications and Reference Specifica-

tions and 11-34 by the Spring ot 1987. Other criteria documents will be added in

1988. Eventually this system will enhance more than 2,700 government and non-gover:unent facilities engineering criteria documents, involving 67,000 pages ofhard copy text, to be provided to subscribers on a single 5.25-inch optical

d :-k. Users ate expectod to include engineering field activities of the Army,Navy, Air Force, other government engineering and design activities (HUD, VA,

NASA), non-government A&E firms, and standards setting organizations.

The point of contact for these systems is Mr. Thomas Rutherford, Naval Facili-ties FW'.,,tneering Command, Code 04K2, 200 Stovall Street, Alexandria, VA., 22382,telephone A/V 221-0450 or A/C 202-325-0386. A copy of the presentation is atatt;jchtilent I0.

11

The Army Spe'ifications and Standardization Computer System (DEPSOMIS). Pre-sertLed by the Army Departmental Standardization Office, Alexandria, VA.

This management information and retrieval system is located at Fort Belvoir,VA., a-d is operated by the Army Departmental Standardization Office, Hq., U.S.irinv Materiel Command, Alexandria, VA. The system was designed to automatees:ential standardization information required by Army standardization activi-tiks to effectively manage their portion of the Defense Standardization Program.The system presently includes information from sources such as SD-i -Standard-izatio'n Directory, SD-4 - Status of Standardization Projects, the DOD Index ofSpecifications and Standards (DODISS), the DOD Parts Control Program, togetherwith slandardizatlon budgeting, workload, manpower and accomplishment data pro-vided by subordinate activities.

The system has the capability of analyzing SD-4 data and grouping projects by aamber of categories. It can also provide project summary data categorized by

milestones such as late start, past completion date, past completion date -notextended, number initiated, number completed, number cancelled and numberlanned. The system has also automated the information available from theDODISS. Although still under design, the system is capable of screening docu-tents by Army interest, validation date, FSC/AREA Class, and the like. The sys-tem also provides summary data on performance in the Overage Document ReviewProgram as well as the contractual application of the DOD Parts Control ProgramIn acquisition.

The DEPSOMIS is housed in a CYBER 180/835 computer located at Fort Belvoir, VA.It is an interactive data base with remote access using conventional 300/1200Kaud commercial telephone lines. System S2K is used to manage all of the baseexcept those portions dealing with DODISS, SD-4 and Parts Control.

The poxint of contact for this system is Mr. A. F. DeSantolo, U.S. Army MaterielCommnand, AMCLD, 5001 Eisenhower Ave., Alexandria, VA., 22333-0001, telephone/V 28,-6748 or A/C 202-274-6750. A copy of the presentation is at attach-

In, It 8.

12

The DOlO IT!.o , oI SpecIt t-at .iV,. 1re. , ,d by Lth. NavaIPubhI i t tons and Forms Cent. i . . .. ..

Ms. Al ice l1e [1 gave *i preseI:- .. . .... P, hic I ' i o;-.s a:.d l,orms C,,nter(NPFC) , explaining that, N ' ''C . m4we ,t o l xfense SJ:.gle Stock Point forall Military Specifications a:d - . :,;,d other St &ndaird izi on docomerts,respornsible for the preparat i ,r ', $1 dex of Specif ications arid Standardsand for the stock, storage, .I i I ,,L ttousi :ids ot standardizatio%documenits used by the 001) ifAL P, ,s el I went on ,o describe thenmanual processe; that are now , epa re the IX)IlSS catalog file (theTidex), to maintain document d p , L:, ,;, aiid Lo manage the stock, stor-.age, distribution, and replElni l c, I ifd .atiar documents. She a/a.S(odescribed the considerable amnount '' use space (approximately three cityblocks in size) required to SLOr-e :. Cbihue docuinent, Ior which NPFC isresponsible, and the manual meth,.i 1'<; ,i.ployed in responding to requests for

,)cuments. She indicated that leI ti I a request received by telephoneor message i.; 5 days and uip ti 1 ,, ,ed by mail.

During her presentat or M; . t I . . 1' Mr. Johr K,irpovich o f he NavyPublication nd Printing Sevie ',, .. ice for ia discussion of the Navy'rint on Demand System (NPODS) a4 1111s,;, to be impleneinted at NPC. Phase

o:ie of this system is interded . intJng, scock, storageand, distribu tiln of docume:nt:- ; - " ,::s; pus'cess 6"d toimprove the DOISS data f .lo .UOI). The in i I aI

thrust of the NPODS program L * ., it i docimients for fulltext stora;e on a mainframe i:, -c: prit , dmand". It isanticipated that with this c, - - I )' t .ie document managedby NPFC will have to be sto k. ts -;;,nml ican.ly reduci:.g ware-

housing space. I: , addition, k . . ceqoes;t, tot documents is expectedto be reduced to 24-48 hoicn . ; ,1ve a cki pab i lit y to bid order"requests for documents that ,i, •.;'_ I L

Future NPOD plans include the its ... • - ot sy"'tellis to make the DODiSS database available to the service., ' ,' isi managin, standardizatior.docume;its for which they are tt'; . . .(1 LIe est abI isliment of sate I Ii teNPHF. center; to provide spo., i , . estos.

ltirther dit, ils mini tCie "%l'F(' : -1 , t lvi ru,, Ms. Alice bell,N.ival Plublications and F.o-m, k,,i, ', lTabor Ave., Philadoliphla, PA,

19120, telephone A/V 442-T037 o , . w,; -on1. Detai 1:V w: tile NP(il)S programmay be obtalned from Mr. .hilis . ., ' , ;iv.i Publi'attions a:d Printlng ServiceManagement o(f ice, Code 4 1 , 1ho ,ii i Waihi r:gt)mn Navy Ydrd , Washington, DC

20371-1573, telephone A/' .-P- i' -3i9l. A copv .t ie NPFC pre-sentation is at attachment 13.

GENERAI DISCUSSION:

liriig the general session following the Service presentations, a number of top-ics were discussed. The more significant of these were; (a) the need for asingle, comprehensive, DOD wide data base and management information system toembrace enhanced existing systems such as the DODISS, ASSIST, the SD-4, author-ing systems for the preparation of acquisition documents such as SOW's, systemspecs, and CDRL's, and authoring systems for the preparation of MIL specs; (b)the :ieed for a comprehensive action plan that would schedule studies of existingsystems to determine enhancements required to facilitate DOD use, the physicallocation, equipment requirements, communication links, funding requirements,.Other systems that may be required, and schedules for conversion of the existingbases to DOD systems; (c) the need for a focal point at the DOD level to provideguidance and direction for this effort; (d) the need for a systems "integrator"to coordinate service efforts and to integrate the various systems into one, and(e) the need to determine whether other systems exist that may have DOD applica-tion.

OASD represcntatives agreed that they would become the focal point for thisundertaki-g, indicating that this function would probably be assigned to theDefense Standardization Program Office. In the matter of funding the efforts tobring about an integrated system, no specific conclusions were reached, althoughthe services were advised that funding would probably have to come from the ser-vices.

No decision was reached regarding the designation of a system "integrator",although it was indicated that one would be designated in the near future. Hr.Karpovich, of NPPSMO, suggested that the Navy Industrial Fund (NIF) be consid-ered as a source for funding, and that the development of an integrated systemand its maintenance could become a part of NPODS. NPFC was suggested as a pos-sible site for the integrated system.

Following these and further discussions, the Chairman proposed a number of spe-cific recommended actions for consideration. Each was discussed in some detailand agreed upon by the group. They are as follows.

RECORMEN DAT IONS :

I. Determine the enhancements and other changes required to the ASSIST Programand implement it as a DOD wide specification tiering/specification referencingsystem, to be centrally located, perhaps at the Naval Publications and FormsCentler.

2. A IA)1 wide DOD Lndx of Specifications and Standards (DODISS) data baseshould be implemented from which agencies may obtAin specific information ondocuments listed in DODISS for which they are responsible. This base should becentrifly located at the Naval Publications and Forms Center.

3. An enhanced DOD wide SD-4-Status of Standardization Projects data baseshould be implemented and centrally located, to provide management activitiesbetter visibility over the status of projects within areas of assigned responsi-bility.

14

4. A DOD wide authoring system or systems similar to Air Force CGADS and/or AirForce TFMSE/DOCWRITER, should be implemented to prepare automated System Speci-fications, Statements of Work, Contract Data Requirements Lists and other docu-ments used in systems acquisition.

5. A DOD wide automated authoring system should be developed and implementedtor the preparation of Military and Federal Specifications and other standardi-zation documents.

6. The DOD should undertake a study to determine the feasibility of the use ofelectronic mail or other automated media to enhance the standardization documentcoordination process.

7. The DOD should develop and implement a system to identify and monitor theuse of specifications, standards, and other standardization documents inacquisition, i.e., those documents appearing as referenced documents in Requestfor Proposals, Invitations for Bid, and contracts.

8. A singLe focal point should be established at the DOD level to develop acomprehensive plan to accomplish the forgoing recommended actions, to make taskassignments, and to monitor progress.

9. DOI) should designate an agency to be responsible for integration ot theseveral datd bases into a single comprehensive DOD wide data base. That agencywould also be responsible for evaluating existing and new technology todetermine the types of equipment that may be available for use, for determiningfunding requirements and charges to be imposed upon system users.

it. It was also recommended that the Standardization and Data Management Newsletter be used as the vehicle to describe any other Service data base(s) thatnay have DOD wide application.

CONCLUDING REMARKS:

in his concluding remarks, Mr. Yurcisin thanked the attendees for their partici-pation in the meeting, and complimented the Services on the quality of theirrespective presentations. He expressed the hope that this meeting and itsresults would trigger new initiatives on the part of the Services to achievetuither standardization data base automation, and that the Services would takeidvantage of these existing systems where ever possible rather than design theirown. Mr. Yurcisin made particular note of the Navy NPOD System, suggestingthat it may become a focal point for automated standardization data bases. Heipressed his appreciation to the Naval Air Engineering Center for their work in.devvloping the ASSIST Program and for undertaking the study of automated datahases. lastly, he indicated that the minutes of the meeting and its recommend-ations would be provided to the attendees as soon as possible and asked thatthey be given widest possible distribution.

Attachments

15

ATTACHM4ENT I

AGENDA

17

ATTACIIEB W I

AGENDA

MAY 13, 1986

0800 AM Registration

0830 Opening Remarks - Peter Yurcisin, Director, Standardization andData Management, Office, Assistant Secretary of Defense (A&L)

0845 Discussion of the Agenda - Moderators Lee Rogers and Greg

Saunders, Defense Standardization Policy Office.

0900-0930 Data Base Presentation - Naval Air Systems Command - Automated

Specifications and Standards Information System - (ASSIST)

0930-0945 Questions and Answers

0945-1005 Coffee Break

1005-1035 Data Base Presentation - U.S. Army Materials Technology Laboratory

- Computerized Standardization Search System - (CS

W035-1050 Questions and Answers

1050-1120 Data Base Presentation - Naval Sea Systems Command - Computer

Assisted Ship Specifications - (CASS)

1120-L135 Questions and Answers

1135-1205 Data Base Presentation- Hq, Electronic Systems Division, AirForce Systems Command - Computer Generated Acquisition Documents

System - (CGADS)


1220-1 330 Lunch

1330-1400 Data Base Presentation- Hq, Space Division, Air Force System

Command - TEMSE/Docwriter

140U-1415 Questions and Answers

1415-1445 Data Base Presentation - U.S. Army Missile Command - AutomatedEngineering Document Preparation System - (AEDPS)

1445-1)00 Questions and Answers

1500-1 15 Coffee Break

151)-1545 Data Base Presentation - U.S. Army Belvoir Research and Develop-

ment Center - Technical Data Configuration and Management

K Information System - (TDC&MIS)

19

1545-1b00 Questions and Answers

lb00-1630 Data Base Presentation - U.S. Army Natick Research and DevelopmentCenter - Adequacy and Assignment Index - (A&A Index)


MAY 14, 1986

0820 AM Administrative Remarks

0830-0900 Data Base Presentation - Naval Facilities Engineering Command -Engineering Criteria Management (ECM) System and Automated Facil-ity Engineering Information System (AFEIS)


u915-0945 Data Base Presentation - U.S. Army Material Command (DEPSO) -Standardization Program Management System - (DEPSOMIS)


1(00-1020 Coffee Break

1()20-105 )aLa Base Presentation - Naval Supply Systems Command -DOD Indexof Specifications and Standards (DODISS) and Navy Print on DemandSystem (NPODS)

10 50-I10 , Questions and .,,'swers

1I)5-113') Special Presentation - Information Handling Service (IHS)


1145-I 300 Lunch

1300-1330 Special Presentation - Ziff Technical Information Co.


1340-1540 Open Discussions

1 540-16001 Wrap Up

I ()h Closing Remarks

20

ATTACH1ENTr 2

LIST OF ATTENDEES

21

ATTACmHswr 2

LIST OF ATTENDEES

NAME ORGANIZATION/ADDRESS TELEPHONE NO.

Thomas Hallantine U.S. Army Material Command A/V 284-6748AMCLD, 5001 Eisenhower Ave. A/C 202-274-6750Alexandria, VA 22333-0001

Kathy Bamberg U.S. Army Materials Technology A/V 955-5567Laboratory A/C 617-923-5567

S LCMT-MSR-ESWatertown, MA 02172-0001

Alice Bell Naval Publications & Forms A/V 442-5637

Center, NPFC-435801 Tabor Ave., Phila, PA 19120

Carl L. Berry Defense Data Management Ofc. A/V 289-25555203 Leesburg Pike, Suite 1403 A/C 703-756-2555Falls Church, VA 22041-3466

Linda Burgher Defense Data Management Ofc. A/V 289-25555203 Leesburg Pike, Suite 1403 A/C 703-756-2555Falls Church, VA 22041-3466

Joi, E. Burke KSAI A/C 703-892-8990

2009 N. 14th St. Suite 408Arlington, VA 22201

Stopher Carey Naval Air Systems Command A/C 202-692-0878AIR-710Washington, DC 20361

James P. Carg[Ie BDM Corp A/C 804-461-15375 Koger Executive CenterNorfolk, VA 23502

N.J. Ccere, Jr. Naval Air Engineering Center A/V 624-2107SESD-93 A/C 201-323-2107Lakehurst, NJ 08733-5100

Kathleen Conrelly Boeing Computer Service A/C 703-821-6484Mail Stop CV-821980 Boeing CourtVienna, VA 22180

W. P. Coyne U.S. Army Belvoir A/V 354-5717R&D Center A/C 703-664-5717STRBE-TS TSFort Belvoir, VA 22060-5606

23

NAM ORGANIZATION/ADDRESS TELEPHONE NO.

Ray L. Cravy Information Handling Service A/C 303-790-0600

15 Inverness Way East

Denver, CO 80150

A.F. DeSanLtolo U.S. Army Materiel Command A/V 284-6750

AMCLD, 5001 Eisenhower Ave. A/C 202-274-6750

Alexandria, VA 22333-0001

Richar! M. Freeman Hq. FCDNA, FCLMCS A/V 244-0301

Kirtland AFB, NM 87115 A/C 505-844-0301

i eslie Garrett VSE Corp A/C 703-960-4600

2550 Huntington Ave.Alexandria, VA 22303

Kichard i. (oehner U.S. Army Belvoir A/V 354-5789R&D Center A/C 703-664-5789

STRBE-TC

Fort Belvoir, VA 22060-5606

Norman J. Griest Naval Sea Systems Command A/V 222-0490

SEA-55Z2 A/C 202-692-0490Washington, DC 20362

Jaimes Iamel Naval Sea Systems Command A/V 222-0513PMS-394 A/C 202-692-0513Washington, DC 20362

Stpven 11ofiiger KSAI A/C 703-522-13002009 N. 14th St. Suite 408Arlington, VA 22201

Patla Howard Naval Air Systems Command A/V 286-1149

AIR-51122 A/C 202-746-1149Washington, DC 20361

(Geraid Hlyman Air Force Systems Command A/V 833-0831Space Division, SD/AL A/C 213-643-0831P.O. Box 92960Worldway Postal CenterLos Angeles, CA 90009-2960

S, halie .Jc:ings Ziff Davis Technical InformationCorp.

13271 Northend St.Oak Park, MI 48237

Thomas Johnson Information Handling Service A/C 202-331-09611990 M. St., N.W. Suite 400Washington, DC 20036

24


Johi Karpvich Navy Publications and Printing A/V 288-3891

Service Management Ofc. Code 41 A/C 202-433-3891

Building 157-3, WashingtonNavy Yard

Washington, DC 20374-1573

D.Z. KC:iglht Naval Construction Battalion A/V 360-5301

Center A/C 805-982-5301

Code 156Port Hueneme, CA 93043

John Koper Naval Air Systems Command A/V 286-1145

AIR-51122 A/C 202-746-1145Washington, DC 20361

Karen E. Kristensten NCSI A/C 703-671-09095203 Leesburg Pike, Suite 1601

Falls Church, VA 22041

•;,,rv :.ucier U.S. Army Natick A/V 256-4143RD&E Center A/C 617-651-4143STRNC-EMSM

Natick, MA 01760-5014

I't;nela McAfee Naval Construction Battalion A/V 360-5301Center A/C 805-982-5301Code 156

Port Hueneme, CA 93043

Coi. Tho,',,s Ma:-sperger Office, Standardization A/V 225-7915and Data Management A/C 202-695-7915

OASD (A&L), PentagonWashington, DC 20361

Thnma J. Marchesani Naval Air Engineering Center A/V 624-7401SESD-93 A/C 201-323-7401Lakehurst, NJ 08733-5100

Ai ,:I 1. ma Aerospace Corp. Ml-169 A/C 213-648-7105P.O. Box 92957Los Angeles, CA 90009

kJI..dt., Murphy Naval Sea Systems Command A/V 222-0lolSEA-55Z3 A/C 202-692-0161Washington, DC 20362

Jerry Nabors U.S. Army Missile Command A/V 746-1335AMSMI-SE-TD-ST A/C 205-876-1335Redstone Arsenal, AL 35898-5276

25

ORGAN! VA' I ')N/AI)I)RFSS TFL, Ph '.. . -

Harr%, N,-so. Linage Conve e sio: l'echrolgis ."/" /33--,<--A- .1225 Jefferson Divi, HwyStiie 612Arlington, V/, 27"Pi,Z

.at O,;r N;va l Supply Sys teins Command ,V 225-' jiSUP-032 A/i. 202-f 9',-3o0,Washington, IC 20376

:cim d u, N,.,i Ir Force Systems Command A/V '174-24'lectronics Systms Div. A/C 6i7-37-_mts4,-ESI)/PLEA

Ianscom AFB, MA )1 731

h' ) Naval Air Engineering Centr A'/V 624-297(GSESD-93 A/C 201-32 )-2970Lakehurst, N.) 08733-5100

. -nt.. !R lardsor Defense l)mt-a Martagement Ofc. A/V 289-25s5203 Leesburg Pike, Suit? 1403 A/C 703-, o-'2),Falls Church, VA 22041-3466

.,. .oger. OASD (A&L)-DSPO A/V 289-_>1'5203 Leesbutij Pike, Suite 1403 A/C 703-756-234()Fall,; Church, VA 22041

Tom '<Itlcli tord Naval Facilities Eng. Cmd. A/A 221 -: 14 jFACO4M2, 210 Stovail St. A/C 2 (12-325-,,)38Alexan-dria, VA 2332

'ra . Air Force Systems Commanj \'V 478-574%.'Iectroziics Sy,'? ms Div. %,'C 7-U7,-5745

KS D/s I PMHafls('om AFB, MA 01131

*';. ."- (;::d, , OASD (A&L)-DSPt) A/V 289- '341)'203 Leesburg Pike, Suite 1403 A/C 703-7 56-234('Fall!; Church, VA 22041

Va I-rvm, ';Iga Aerosi)ace Corp A/C 21 1-648-71 i.-I'.O. Box 92957Ios A -eles, CA Q00')

I ' .Ii. lI .:; a t ": A " ' " - , L10)2 31st St. ,.,.Washington, )C 20007

.V, .V :.c, t l,',,al Air Sy' ,, , ,)mm-ind A/, 2,;, h 4AIR- 51121 A/'"(32-7..-'WIshir.gto , N , ' I I


Joan M. Wolk Boeing Computer Service A/C 703-827-4429

7980 Gallows RoadVienna, VA 22180

Bradford N. Worthington NCSI A/C 703-671-09095203 Leesburg Pike, Suite 1601Falls Church, VA 22041

Peter Yurcisin Director, Standardization A/V 225-0121and Data Management A/C 202-695-0121

OASD (A&L), PentagonWashington, DC 20361

27

ATTACH14ENT 3

AUTOMATED SPECIFICATIONS AND STANDARDS SYSTEM (ASSIST)

29

AIACHKENT 3

RESPONSE TO TOPICAL QUESTIONS ON ASSIST DATA BASE

I. W'hat was the system originally designed to do?

The system was designed to provide a higher degree of control overspecifications, standards, and other standardization documents in whichNAVAIR has an interest and to provide greater visibility over their use inthe acquisition process.

2. What information is presently stored?

There are now approximately 35,000 documents loaded in the data base. Forthose documents falling within the Federal and Military series ofspecifications and standards, the following data is stored:

Document numberDocument titleIssue indicator (revision symbol)Approval dateType of document (Spec, Std, Etc.)All primary referencesFSC/AREA classificationMilitary interest (Fed. Specs)Validation DateStatus (active, cancelled)Agency interest (PA, CU, review, user)

3. Who are the system users?

The system is used by specification writers and technical personnel in thepreparation of new and revised documents in identifying materials, partsand other documents that can be used as references; in identifying andvalidating the currency of all primary and lower tier references; inidentifying documents that will be affected by the cancellation of a givendocument; in identifying overage documents for purpose of the overagedocument review program; in maintaining a current list of all documentsfor which NAVAIR is responsible as preparing activity or Navy custodian,as well as those documents in which it has a review or user interest. Thesystem can also be used to support the acquisition streamlining process byproviding visibility over all of the documents to be envoked in acontract. This is accomplished by first identifying all of the documentscited in the System Spec of Statement of Work and then, by utilizing thedata base, developing a single list of all of the documents called out asreferences by these cited documents.

4. What are the sources for data included in the base?

A hard copy of the document (MIL-SPEC, MIL-STD) is used to obtain thedocument number and the number of each of Its references. As the documentand its references are loaded into the data base, each document is

Enclosure 2(Page 1 of 4)

31

4. What are the sources for data included in the base? (Cont'd)

compared by computer with a DODISS magnetic tape. All other pertinent datafor that document is abstracted through automated comparison and incorporatedinto the base. rhis includes the title, approval date, revision symbol, FSCClass, qualification requirement, agency interest, etc.

5. What hardware is used for the system?

The ASSIST data base resides in an IBM 4341 computer at the Naval AirEngineering Center, Lakehurst, N.J. The operating system resident in theIBM 4341 is MVS V3.83.

6. What types of programs/languages are used?

t'SSIST is a COBOL based system, interfacing with a multi-user S2K database. The only code that is not COBOL consists of several assembler languagesubprograms for controlling certain aspects of ASSIST's interactive promptingroutines. Querries are initiated in an interactive TSO environment throughthe execution of TSO CLIST command procedures.

7. Is internal or external support used to load and maintain the data base?

External support is used to load and maintain the data base.

8. What output products are obtained from the system?

The following output products, or reports are provided by the data base.

System Spec Ref List -A single listing of all documents referenced bythe primary documents cited in the system spec. Repetitive listing ofthe same document is suppressed.

Specification Tree (Pyramid) - A report displaying all of a primarydocument's 1st and lower tier references to as many as five levels. Italso identifies any referenced documents that are cancelled.

Keyword Index - The computer will search and find all documents in thebase that have a "keyword" in the title and will provide a list ofthese documents by number and title.

QPL Requirement - A listing, in numerical order of all documents in thebase for which a QPI has been or will be issued.

Overage Documents - A listing by date of approval of all documents (Miland Federal) in the data base.

Alphabetical Index - Provides a list in alphabetical order of alldocuments in the base, categorized by document type.


3 2

Documents by Preparing Activity - Provides a listing of all documentsin the base for which NAVAIR is preparing activity.

Interest other than Preparing Activity - Provides a listing of alldocuments in the base in which NAVAIR has a registered interest otherthan Preparing Activity. Identifies NAVAIR's interest, i.e.,custodian, review or user.

Referenced by Other Documents - Provides a report listing all of thedocuments that utilize a given document as a primary reference.

9. Is it a single user or multi-user system?

It is a multi-user system.

10. What procedure is used to maintain the data base?

Weekly indexes (such as IHS of IMI) of documents issued by NPFC arereviewed to identify those documents of interest to NAVAIR. A hardcopy of each new document is obtained and that document and Itsreferences are added to the backup of "key punch" file. Copies ofdocuments that are revisions or amendments to documents already in thedata base are obtained and compared with data already in the base.Changes to references, revision symbols, approval dates, etc. are notedand incorporated into the backup file. Periodically the data in thebackup file is auditied, corrected and incorporated into the data base.

11. Is there remote access to the system? What communication links are used?

At the present time there is limited remote access to the data base.Most of the output products are in the form of bulk reports generatedat the computer site. However, the system is designed to accommodateremote accessing.

12. Are there planned changes to the system to expand it or to addenhancements?

Planned enhancements to the system include the following:

Design and develop changes to the system to provide for interactiveupdating of the data in the base. Due to the magnitude of data beingentered into the base, it has been more economical to store informationin a backup "key punch" file and batch load material into the computeron a periodic basis. This change will provide for direct interactiveupdating of data in the base.

Identifying primary and reference documents that require the deliveryof data. This change will provide a means to identify any document ina System Spec Ref List or a document's pyramid that requires the

Enclosure 2

(Page 3 of 4),

33

delivery of data, so that data managers will have better control andvisibility over data requirements to be imposed in contracts throughspecifications and standards.

Adding Data Item Descriptions (DIDS) to the data base.

InJentifying and including a superseding document and its referencesfor any cancelled/superseded document(s) that may appear in a givenspec tree.

13. Is system documentation available?

System documentation is available, as is a Users Guide describingprocedures for querrying the system and retrieving information.

14. Is a data base management system (DBMS) used?

The ASSIST data base utilizes an Intel Systems Corporation System 2000(S2K) data base management system. S2K is a hierarchical structured data base.


34

BRIEFINJG SYI.3PSIS

.he Autr iated S,ecifications and Standards Infor.,iation System

The Naval Air Systems Comand presents the Automated Specifications andStandards Infurination System, comnonly referred to as ASSIST. This data baseand information retrieval system is located at the Naval Air EngineeringrCenter (NAEC), at Lakehurst, New Jersey.

The System Point of Contact is the Systems Engineering and Standardizationf)epartment (Code 93) at NAEC, Lakehurst, NJ.

The User Point of Contact is the Naval Air Systems Command (Code AIR-511),Washington, DC.

The System Tanager Point of Contact is the Systems Engineering and

Standardization Department, Engineering Management Branch, (Code 9322) atNAEC, Lakehurst, NJ.

The data base presently includes all DoDISS information on approximately32,800 Military and Federal Specifications, Standards, MS's, Bulletins,Handbooks, AN's and AND's together with all of each document's primaryreferences. There are an additional 10,000 documents in the base for whichall data except their primary references are included. There is now anaggregate total of 303,850 references and 207,850 keywords loaded in the base.

The system is designed to provide information on specifications, standards andother standardization documents prepared by or of interest to the Naval AirSystems Command (NAVAIR), to provide visibility over documents invoked byreference in acquisition, to support acquisition streamlining initiatives, andto improve the currency, accuracy and management of documents prepared byNAVAIR.

Future enhancements include a means to identify documents requiring deliveryof data, adding Data Item Decriptions (DIDs) to the base and indentifyingsuperseding documents and their spec tree.

The system can provide support to a variety of users, including the following:

Standardization Program lanagers: To identify and manage docunerits in, sirjne-d Fc/-REAand other documents for which they are responsible.

Standirdi.ation Document Engineers: To identify overage documents; to assistin-preparatiun of documents; to validate currency of references in new/reviseddocuments; to identify documents affected by cancellation of given document,to identify documents requiring QPL; and to identify hazardous or costlymaterials, e.g., cadmium, platinum.

SystemDocumentation Engineers: To enhance streamlining by identifying alldocuamen-ts to be invoked by the System Spec or Statement of Work (SOW) and toassure the accuracy and currency of all documents to be invoked.

35

• ";qisi tiun ?.s: .'.vi 1 rea.t.,r v isibility o.,C r Jd cI.:,:rts to bei nvop,., in procurK er.t; to id - nti fy non -product (cost driv .r) docurients to beinvoked that should be reviewed for tailoring; to identify documents invokedby reference, i.e. guidance only, that must be specifically cited in theSystem Specs or SOW as mandatory; and to assure that all cited docu:nents andtheir references are current and active.

Supply Managers: To determined the currency of documents referenced intechnical data packages and to identify applicable documents during breakoutor reprocurement.

The following information is included for each document in the base.

Document Number All Primary ReferencesIssue Indicator -Rev. Amd., Suppl. FSC/Area Class

L/C or Coordinated Military Interest (MCA)Document Date Validation DateDocument Type - Spec, Std, Ms, etc. Status - Active, CancelledDocument Series - Fed, Mil, AN, etc. Agency Interest - PA, CU,Title Review, User

QPL Requirement

Information for the data base is obtained from the Department of Defense Indexof Specifications and Standards (DoDISS), MIL-BUL-544, List ofFederal/Military/Industry Specifications and Standards, and NAVAIR SeriesDocuments Approved by the Naval Air System Command, and the Acquisition."anagement Systems and Data Requirements Control List (AMSDL).

The system is designed to provide a number of preformatted output reports.Although it does not now have an Ad Hoc capability, it can be programmed toprovide an output report within the parameters of the data presently in thebase. Output reports include the following:

Spec Tree Reports - Provide a spec tree or spec pyramid of all of a primarydocumentrs references to the fifth tier.

Ref List Reports - A list of all of a primary document's references to thefifth tier, liifiing each reference one time at the level at which it firstappears as a reference.,

Keword Report - Provides a report of all documents in the base that have akeyword or words in the title.

QPL Reports - Provides a list of all documents that require the use of aQualifiedProduct List.

Overage Document Report - Provides a list of all documents by age andcognizant code.

Co9 Codes - Provides a list of NAVAIR Cog Codes and the documents for whichyare responsible.

Alphabetical List - Provides a list by title in alphabetical order of alla6cuments in-t-F-base.

36

, ivi'y_ 7--pjrt- P,'vides a listiq of all docu,,-..,nts in th,? )aseior .iich NIAVAIR is Prci-,sring Activity.

Cancelled Dociw.ents - Provides cancelled documents and their references.

Other Interest Report - Provides a listing of all docu-ments in the base inwhich NAVAIR has an interest as Custodian, Review and User Activity.

Age and Cog Code - Provides information on date of last standardization actionand the responsible NAVAIR Cog Code.

Ref By Reports - Identifies all documents that use a particular document as areference.

Future capability will include non-government documents, metric documents andHigh cost driver documents.

ASSIST is a multi-user data base. There is remote access to the base using a300/1200 baud voice grade telephone line link, but due to the magnitude ofdata generated by these output reports the cost of transmission of reportsother than "KEYWORDU and "REF BY" by conventional telephone lines would beexcessive. The data processing system resides in the IBM 4341 main framecomputer located at the Naval Air Engineering Center, Lakehurst, NJ.

The system has DoD wide application to support standardization managers,specifications engineers, systems managers, documentation engineers,acquisition managers, streamlining advocates, data repositories, provisioningspecialists and reprocurement technicians.

Future expansion of the base may include increased on-line support for theBOSS program, inclusion of other users, identification of other user needs andunique requirements, development of additional input/output formats andcriteria, identification of inter-communication requirements andimplementation of a network, and interfacing with other automated datarepositories.

37

CO)w0

zzw

Zw0 0 im co

F-z< 00_ F-o 0)

C, cv)<

0< C/) LL WOI 0 ,U)w ZF

w co 2

00 <

<-< ,-0

a~)w

00

I-u-z zcc w w0

z cr.

. a.:aw 0 00

C') NY

w z cz V5- 0 0 CF

Cl) ZZ a ZCC) ccw

ui ~ oHC,0) LCO) 0 Z 0H

CD~H z wZ<w<

CC <w, LLrL cc~ <

a. z <::z 0~ <0L 0L

Cl) < Cc 0 <O

CO V'

0 WQ L

0 i I-

0 < 0 w w <

°oo0 0 w

z Lo - <w>- 2: 0-

I-J L c w CCC' c o 1 . o 0 aZ W OO Z W<0ow 0 <c O

00 5> 0. 21-CO W CC~ C/))w

0 w

w<O0 Q0 - £rr O z 0 --)C -

z ao >- 0 QOHLK<H o Jo oI-_

< to~ ti- < w,,c l , J : > - ) z

0 Z WLI)C 0 Co

F- <~ < F- H 0 -IO C i

W ~ wr wcc w< W <)L u OI

0. l a . .> >w 0 0w C

< M a) < M w,<-

>. 0 >0 Z .

S M I 0 O

7 V

z zCo-- C/)

CoJ I-I-LL-CC -j zi 0 0ZZ

< mz -LJ pm%%,. -D .2 O W. 0 LJ

rLL 0 0 > <

wL 00 W/ L

w0 H : -LJ(zW 'co LUjL CO LL Z

o Co WO wc - 0 c 0Wl -H co-~-

< Ho W2 Iz<a 00 > CYLU>

tr ~ ~ cr - HI--OC)HLUW Z -J w/ L coco Z I-win)

F- ~0 m - :uU c c wu < >- Uo O ~Cr LWI (.) 0 :z QC)c

CO ~ ZZ) 0 CC z H rL< w JiO r

<I W3 <r Z5 UJ Z L / W c l 0 OMC

<~~~~~O 00UL CF- HL I-L )

CDn coO 000 < @.C 0 L)( <0 <0

a:< mLja 00 0w>a

cci

oL C) . U)a~ 1.. 0

CO E

0

.760 CL *.-L0- ~ E0- >CoJ 4)- 0 .- *. o* :3c -

F- C C/) o m 0

00-co -

F"E > cE

CL Ar u..4All!

fiColi1-*Fry

10o

C/) - q

D CO

UuJj

u )Zn cc R-vao oo

ii:12

~ fI1ce

0;>' 'ii

CO

*000 0 ZH

Iz 0z ir 0

z w 0

a . 0 C

0: z Lu c

Co 0 W oi< 0>- w w >w ~< Z> CCD 2Cwo 1 H<oa

0 00 0z 0 cC%o()0 W 0H

ZZ"- > o CO)COu3 C) ZLu >- 0 0

C. Oa:> <'C cp to 0

CO LL w z I-

0: w-0

a C.) z <o i z

Z H o-w z z

0_ Co 0 0

Z W Lu w 2z

wO cc 0 CO C.) C.

a: 0 0 w

0 w>0) 4

00

9f7

0 ar

C/) c w 0CD C/o >)- 0o

w 0> CW wof <0 wo 0 65

-< 0 W<< 0 c 0 Or2~ ow 1-

w o 1j Li

CO -woQ > co o

>- )>- J <.. Z

?Y :r, 0 L

11% e 0wV5C/) -z

zCO w

Lh< W, C/ <

<=w z/

cr)

I-zw

-woCO w a C/)

Z 00 2O _ F

a: w a0 irz

w O F- Cz

0/ z WI-- cC.))

o z 0' 5 a~

w C. Wo z 0 o 0

Co zco ix < :)

D<Wa. O wO 00 J) 0p

o co C oVJF D WbWOW -r w irOoZ 0L aZ LuC c< 3t w

mam 0w 0 w M -I< Ir /) 0 0

I~~~ NLZ 0 Zj i c-0 E 3 l F- ZC 0 w

<- < 0 z Sl z

ATTACHMENT 4

COMPUTERIZED STANDARDIZATION SEARCH SYSTEM CS 3

49

ATTACHMENT 4.

AMWL's CornFttrized Standardization Search C9ystm )

Data Base Discussion

1. The MTL data base was originally designed to manage standardizationfocuments and facilitate report preparation. The information system wascreated to provide storage, retrieval and analyses of related 9tandardizationlatq.

The dita base stores information and data from over 4,000 materials andmaterials related standardization documents within AMTL's areas of interest.It enables searches on text and date fields within interrelated groups ofdw.uments, test methods requirements, cross-reference material, referenceddolcument or other salient information contained within the body of aspecification.

'Th. Fniineerin( Statidardization staff managers, writers and data entryp,--soorrol trf" the current users of this data base system.

I!. .,ofre 4300 standardization documents (specifications, standards, amendments-r .,ane riotices) are the sources of data for inclusion and cover 543 federal-I'Iply classifications.

1. The system hardware used to store our data base is a Digital EquipmentCorporatirn VAX 11/780 computer which is accessed in a time shared environmentthrough multiplexed video terminals which share logic through a single-ommunications circuit.

6. "'he c; was developed as an application of the DRS managing element.Thi.s ;managing element contains a unique command language which allows users toquery and update the system and provides two interactive modes of operation:an automatic menu driven mode, designed for ease of use and a manual modewhich provides maximum retrieval flexibility and reporting facilities.

7. %ITL's computerized standardization program is externally supported by amtractur',l effort. A contractor is responsible for loading and maintaining

the (':;3 and will continue to provide storage, updating services and generalmaintenence provisions until such time MTL can handle an in-house operationrnd asoume data base building capabilities and maintenence responsibilities.

R. 'Itie CJ4 allowu data rotrievals from four aggregated record types. Th-inain or master set contains a great number of critical key elements or datafield!- whioh can be useful in a preliminary search. In addition, data can beretrieved from any one of three lower record types which contain data items;'rom requtrement or quality assurance provisions, comments or referencedfocumen+ information. The main or master record set is linked to the threelower rerd nd t.llow:', interactive data retrievals to be made from a siring--cord or from -iriy combination of parameters.

. The ( ;i data base is accesscd in multi-user environment. A specirilooftware program enables the multiplexer hardware to act as a "traffic copamong the terminals in our distributed system if the need arises. The systemmay have to delay access to certain files until they become free.

51

V ). Th' 1 : r ,-ling J omenrt , lontain:i programable software; which illows

p.,:i-ll mo,,le :c.,.eer to b generated for additions or updating purposes.AMTI,'I. scr- ,rns -re desi,,net to coincide with prescribed selections of data

rnt ri es.

t I RPnote ',m],nt r ,t'cc: equipment wns selected which allows several usersf, :-har-e divztributed dato processing information simultaneously. An eight,'Ihainel ;witching statistical multiplexer enhancement with 4800 bps modemutilises :i conditioned commnunication line which enables optimum terminalportormane at an economical fee. Terminals are asynchronous with EIA RS 232interface which adheres to the standard ASCII code information interchance.

I . Ih, ( is about ready to branch out with document data baseerichancements. One is for cancelled documents and one for the maintenance oftn.o indu-triil documents within MTL's areas of interest.

- cu entation is available on the description and operation of theT.r. irt, also auxilliary menu driven Help screens built into the data

hq e protrgam for on-line assistance.

14. The C,0 daLi base is an application of the DRS data base management

52

Syi)Ps ko " ('0MPIJTRiZE,) STANDARDIZATION SEARCH SYSTEM CS3

Army Matelials Technology Laboratory (MR) is AMC-s lead laboratory in materi-als, solid mechanics and materials testing technology, and is the manager ofAMC's research and exploratory development program in structural materials,meclkdalic- and -truc ural integrity. Its Engineering Standardization Divisiont.Sl)), has fiscal and echn1cal responsibility for managing that portion oftht. defense Specifications and Standardization Program (DSSP) which consists ofm;i-orials (metallic and non-metallic), materials-related processes and mate-riaLs test methods.

PSI)- managerial and technical responsibilities pertain to documents from 53

[ederal supply classifications and areas and involve preparation, revision,

co(jrdinati,)n, or review of documents covering a wide variety of materials suchas ferrous and non-ferrous metals, plastics, composites, ceramics, rubber

prodcts, finishes, and adhesives as well as materials-related processes andtest methods. New spectfications are also prepared in support of advanced

material i developed for use in weapon systems.

E1D ha,. developed a management information system over the last few yearswhich is called AMTL's "Computerized Standardization Search System (CS 3 )".The system was established for the storage, retrieval, and analysis of spe-cification data and operates on the DRS managing element which contains aunique command language for making queries and updating the data base.[nformation and data from over 4000 materials and materials-related standard-

i zation documents within MTL-s areas of interest are captured and entered intothe computer. The system enables searches on text and date fields withininterrelated groups of documents, test methods, requirements, cross-referencem-i.rial, referenced documents or other salient information contained within

the body ot a specification or standard. The CS3 which Is stored on the con-tractor's DEC VAX 11/780 computer is accessed in a time sharing environmentthrough video terminals which share a single communications circuit. The con-tractor supports the MTL supplied multiplexer hardware and manages the systemsoftware used for the multi-user program. The system operates in two inter-active modes: an automatic menu driven mode, designed for ease of use, and a

manual mode which provides maximum retrieval flexibility. The CS3 containsdata items or fields of key elements which have been aggregated into four mainrecord types. The main or master record set contains a great tumber of cri-Lical key elements or data fields which can be used for a prelirinary search.In addit-Lon, data can be retrieved from any one of three lower record types

which contain data items from requirements or quality assurance provisions,

comments or reference document information. The main or master record set is

linked to the three lower records and allows interactive data retrievals to be

made Crom a single record or from any combination of parameters.

The ESD computer program requires continued contractual assistance for sto-

ta,;p, updating services and general maintenance provisions until such time:IT can handle an in-house operation. Until such time when we can assume ourown data base building capabilities, and maintenance responsibilities we needco.tractual assistance. We are about ready to establish two new document

data base enhancements, one for cancelled documents and one for maintainingindii-trial documents within MTL's areas of interest. We need to utilize the

contract r's expertise in setting up these separate data bases but plan toOp" train ES) staff members to carry out the program. The data base enhancements

will be designed for on-line updating capabilities. Key personnel within ESD,

who are responsible for coordinating project assignments and maintainingrecords will be trained to add, update or delete documents and records asnecessary in order to maintain current information.

53

w

zw CL CO)

w w

zwcr w 2(

0 w zz c! z

_z 0

wo 0 0w)

z -C z c

U. NLi.. - <

z 0 0Xh

*J Nu IL 0 I.4 >

0 0

w0 z '0 0 CD

o a: CoLi CO

9sV

LO~

C3,

0*02

LLoaLw0 2 4

coz 0w0

8-4L. 1- Ma

>p M 0 a OaE = SD

Cfl LU cAJ

1-c .. UM.

Z Z 0 .-LLO8- 4.4 40 .-

0 Z

Cf) 2z CO 0

0. o)W 00cc 0<w

z < CO t

0<w0)

COI- CL ~ ) VZ. 00 0 LUCO> co<0 CO

0 M 0Z< <ZwP..

I- O UJ UJ

z z< 0 4ccozz IL z

0 0 w. w I-0 ;:U m ~ >0m Z

. ZIL< LU

CL . wO. 0

wL LU>z0 ~~ 0

ft 0o L 0 0

-j < 0 a-

0

0A

0

GS

z

3-6 Z La

La L

u Aa 01-4 CC o I--z . i i

01L La Zui 2La =b La 2C >

C/10 I- "A :3CoR 4c -c 0.. z c La C

C34 C. o C. " 0c z

C-) z- z-Z C) C) 1o~~ ~ co LaCL I -

~~~. -L A 2

ZC a- C) La 9- -K La

w- I- w La 2 C .d a

'c u. C In C. C 0cc Co w 0--- 14 ~ : "

LA 0 ~ a - 0

0 9

qL L-I

C2- cn LU cr

-J/( ) LUX *a:L~. La

I.- CL

co ~Lai 6.

co zCL c

C3 Lai

0A L aL&I

ci) LA.

ci~ ~ LU.0

6-4 cr- 14C La

W 4LU Lai Oi LI - q ) -

co 0 LUA 0jQ a

IAL LU Lai cr. acm

io LU 1 .-4 2 w

LAJ LU L~- 0 l I 0I ZM 4c 0 0 Z

L. ~ 1-4 0 "CL C

0.~~~ cn140C Ln01- C3g C ~LUC

I.-b L ~ LUJ LJ -

Lai CA- Ce Z UZ L :Lbi a. T' Lai 0c CLU c ,) L0 03 C3 CL _ 3

AZ a m 0L OK

co- 0- CfC -11 -C LA. 1' La04c =3cU. 0 :: d,, cc A C

ATTACHMENT 5

COMUTER-ASSISTED SHIP SPECIFICATION SYSTEM (CASS) AND

SPECIFICATION IPROVEMENT PROGRAM INFORMATION SYSTEM (SIPIS)

61

ATTACHMENT 5

NAVSEA "CASS" SYSTEM

1. The Computer Assisted Ship Specification (CASS) System isdesigned: to be a "living" version of the "General Specificationsfor Ships of the United States Navy" - GEN SPEC - (it is publishedonly once a year), the Navy's generic ship "building code"; andto be a source for production of the initial version of a., ecific ship's specification.

2. Each line of the GEN SPEC text is contained in one field of afile. Associated fields contain various "tags" such as the3 dlgit specification section number, a subsection identificationlecter, line number, descriptor codes and other codes whichidentify additional information contained in the text field. Thedescriptors indentify whether the text applies to every type shipor to a specific type, e.g.,aircrafL carrier, diesel, submarine, etc.

The text itself references many of the documents tracked inthe SIP Status Files and, in order to be able to identifypotential problem references, the embedded document references areflagged. A PL/1 program extracts those records flagged toindicate a reference is mentioned in the text, and compiles alist of each referenced document number along with the section andsubsection number where the reference was made.

3. Users include NAVSEA engineers, line managers, ship designmanagers, and ship acquisition managers.

4. The sources for data in the base are the ongoing stream ofGENSPEC changes which come before the NAVSEA SpecificationControl Board.

5. Tht hardware used is a leased IBM 3033.

6. The CASS system uses the programming language PL/I and thedatabase management system IAM (Innovation Access Method).

7. hotfi internal and external support are used to maintain and

, peratc the database.

8. futput peoducts are:

.1) An up-to-the-minute GEN SPEC section, whenever needed.I,) The annual issue of the complete GEN SPEC.c) Th, initial version of a specific ship specification

9. Th( system is multi-user.

10. The database is updated via 1200 baud dial-up, using YTERM-;oftware from IBM PC.

11. See previous item; however, user ID/account is required.

63

i2. 'Iite only near-tem change planned Is a move form the leasediBM 3033 1o a newly acquired NAVSEA IBM 3083.

13. System documentation is available.

14. The CASS sysLem uses the database management system IAM(Innovation Access Method) via PL/1 programming language.

64

NAVSEA "CASS" SYSTEM

I. The Computer Assisted Ship Specification (CASS) System isdesigned: to be a "living" version of the "General Specif~cationsfor Ships of the United States Navy" - GEN S.P.C - (it is publishedonly once a year), the Navy's generic ship "building code"; aridto be a source for production of the initial version of aspecific ship's specification.

2. Each line of the GEN SPEC text is contained in one field of atile. Associated fields contain various "tags" such as the3-digit specification section number, a subsection identificationletter, line number, descripter codes and other codes whichidentify additional information contained" in the text field. Thedescriptors indentify whether the text applies to every type shipor to a specific type, e.g.,aircraft carrier, diesel, submarine, etc.

The text itself references many of the documents tracked inthe SIP Status Files and, in order to be able to identifypotential problem references, the embedded document references areflagged. A PL/I program extrLcts those records flagged toindicate a reference is mentioned in the text, and compiles alist of each referenced document number along with the section andsubsection number where the reference was made.

3. Users include NAVSEA engineers, line managers, ship designmanagers, and ship acquisition managers.

4. The sources for data in the base are the ongoing stream ofGENSPEC changes which come before the NAVSEA SpecificationControl Board.

5. The hardware used is a leased IBM 3033.

6. The CASS system uses the programming language PL/1 and thedatabase management system IAM (Innovation Access Method).

7. Both internal and external support are used to maintain andoperate the database.

8. Output products are:

a) An up-to-the-minute GEN SPEC section, whenever needed.b) The annual issue of the complete GEN SPEC.c) The initial version of a specific ship specification

9. The system is multi-user.

10. The database is updated via 1200 baud dial-up, using YTERMsoftware from IBM PC.

11. See previous item; however, user ID/account is required.

65

'2. The only near-tc rm change planned is a wove I orm the I te..-sd

iB 3033 to a newly acquired NAVSEA IBM 3083.


14. The LASS system uses the database management system IAM(Innov.ition Access Method) via PL/I programming language.

66

L9 _

LU U

CDLCC-=

Ca C, j~

_ L

C)C,

Lj L

Q-

C)

CSp

89

CD C: -4SI I

L C C,,

LoU

-,=

a L

C!P

69

0 -LL I-i

0 LL

C2-CLU

L J

LU CDCD >- 0

L- a

toe)) =

LLJOU-

I- 0 - LUJU-j

C') Uj c,

= LUJLLI C') L

I.. - I

L&C) LL-

LAJ

0-L LU

OL

z4

0 0

00 IL

a. Qt 0 0

CcZ CO < L

IU0 0: az:0% u0 > LU - 0 0 LL I.

co CL0w 0o~ Z 0>U 0- U. CL 0 0 C4c 2 ICo Lo mULUw 0

LU c I- 1--0 05J : 0, 0o 0~ L

0l 4(O. a0: z a: IILLU IL C) 0( be

cc Co Co ra~ < 0

> w( 4 I- 0c0i co m 0 Co 0o J

cc 0L 0 0

L4 L-. 3

TL

coO

:) wo

0I 00

00cUrL

Z Z wclo z

I~~ _____

In00OZUZ

OCI)

0 0C, oz

coO

0 'I

W >~ Q

CO m0 30 30, C)

zL X z _ui coiC

4. 0. 0.cc'~.

-J o C - N C'

9- <- W-q

-3 _ ___ ___ ___ ___ ___

4c- CO

0 hcC

- 0 a- N

ozo -%

I- C9

LU w.U I-: w

0,~~ -J 9 L0 W W L9

X~~ 0,, X ,0,<c

0- m C c')09 - V- V- 9-

c- 9- 9

LUJ

r144

L)LI- L.LJ

LU-

LLLU

- LUJ

Cl9-

LU C= (. CD)

LULLL C/)I-

C/) LUJ C) cc

C:) LUJ

C) LU C/

=) -l LU- C) C/ =U L)

CD- -

cm LLJLU: LU LU) LU i

-l (-) CD

=) LA- LU) c_a C:) -JJ C

- L = LU

cc =) C/)-n C) LU=3

Cl- =L =- C.) LO LULax L LU) LU2-= LL JLU

V) CD)LU_ CP-- =L CD ccL

L - LUoC

--

C,) C/)3C

CZ)

C/)

CD,

LU(-D

C/)

C/3 L

C/*)

V')

LUJC-D

LU

-AJ

LUJ

LUL

CCD

LUJ

C/))

C:))

LIJLwal: C- /

LUl

ar0-

C)/

C)D

F--

LUJ LUJ

LU CD

00

--; LU-C) 4) LU C-1L

-l- C)

LUJ CD LUJ C4)

-- C: L-

F-- PQ~- U0

LUJ Ln LU CD

C=) cz - U (-) V) =D L

P- M-- L LUJ:> LUJ LUI <r C)

of' - I-- =) -J c_ =

L -. CD L LU

(.0LU 0-a: C:)

C=)

9L

I-

LL wL L

z z7A. a z

0 0

w 0CA w2f I-

0 &

0 x 0

C)

LL

C/)

CL LU -

_ L.) LO

LC/)'-4 LU

w

I-- LU

C))

LUL

C/ () C) L

0-

LU C/)

-41 CD_

Cl,~Q C;;-LI

C) LU C)

(L) LI)

-j-

LALU C.-- w

611 0001 00 .SEC.S.611 .03/03/80 COHEN 6121 1982 EDITION

611 0002 01 <BGENERAL SPECIFICATIONS FOR SHIPS>611 0003 01 <BOF THE UNITED STATES NAVY>

611 0004 01 <ODEPARTMENT OF THE NAVY>611 0005 01 .SKO1.611 0006 D1 <ONAVAL SEA SYSTEMS COMMAND>611 0007 00 <OSECTION 611>611 0008 00 .SKOI.611 0009 00 <OHULL FITTINGS>611A0001 00 .SEC.<0611a. General>61lA0002 00 This section contains general requirements for hatch davits, padeyes, cleats,611AO003 00 jackrods, eyebolts, rubbing and chafing plates, corrosion protectors, propeller611A0004 00 guards, and sounding platforms.611BOO01 00 .SEC.<0611b. Davits>611B0002 00 <OGeneral.-> Hatch davits shall be provided in number, location, and capacity as611BOO03 00 necessary for the convenient and rapid handling of stores to and from storerooms, and611B0004 00 for striking down ammunition to magazines. Hatch davits shall also be suitable for611B0005 00 handling stores and ammunition over the side of the ship if other611BOO06 00 portable or permanent arrangements are not provided for this purpose.611B0007 00 In general, all hatch davits shall be portable and furnished complete with tackle.611BO008 00 Stowage locations for portable davits shall be carefully selected for convenience to611B0009 00 point of use, so as not to form an obstruction in lines of traffic,611B0010 00 to be protected from boarding seas, and to eliminate the possibility of davits being611B0011 00 jarred out of position and falling into the line of fire of guns or missiles.611B0012 00 The number of sizes of davits shall be kept to a minimum and all davits of the same611B0013 00 capacity shall be interchangeable.611B0014 00 <OWorking load.-> Ammunition handling davits shall be designed to handle a working611B0015 00 load equal to the heaviest piece of ammunition stowed in the magazines served by the611B0016 00 davit, except that if chain hoists or electric wire rope hoists are attached, the611B0017 00 davit shall be designed for the capacity and weight of the hoist.611BOO18 00 Stores handling davits shall be designed for a working load of611BOO19 01 1,000 pounds, except that those for destroyer types and smaller ships shall be61IBC020 01 designed for a working load of 500 pounds.611P 021 00 If the capacity of ammunition davits is approximately that of the stores davits bot611 022 00 types shall be designed for the heavier working loads.ull )023 00 Working and test load label plates in accordance with Sect. 602 shall be installed611BOO24 00 on each davit.611B0025 00 <OSockets for davits,-> Sockets shall be provided at all hatches to be used for611B0026 00 striking down stores or ammunition. In general, they shall be located at the corners611B0027 00 of hatches but clear of the corner radius of strength deck hatches.611BO028 02 Sockets shall also be provided on all superstructure levels for handling material frot611B0029 02 one level to another.611BOO30 00 Sockets shall also be provided in other locations, where necessary, for handling611BOO31 00 machinery parts through hatches between machinery spaces and workshops and engineer611B0032 00 storerooms.611B0033 00 For ships not furnished with permanent or other portable arrangements for handling

78

60

611BOO34 00 stores and ammunition over the side, sockets shall be provided, located port and611B0035 00 starboard, forward, amidships, and aft, as required to use davits611B0036 00 for this purpose.olCO001 02 .SEC.<O611c. Portable weight handling devices>blCO002 02 Sockets and fittings shall be installed for stepping portable cranes, sheer legs,611COO03 02 or other portable weight-handling devices, in locations where they can be utilized fo611CO004 02 handling heavy ammunition, torpedoes, and machinery parts through hatches and over th,611C0005 02 side and for handling stores in cargo nets over the side of the ship.611DO001 00 .SEC.<0611d. Padeyes>blDO002 00 Padeyes shall be provided in number, location, and capacity as necessary for611DO003 00 convenient and rapid handling of stores to and from storerooms and for striking downbllDO004 00 ammunition to magazines.611DO005 00 Padeyes shall be provided over auxiliary machinery as may be necessary for lifting611DOOOb 00 parts of the machines during overhaul and repair.611DO007 02 Padeyes shall be installed on the outer shell for use in unshipping propellers and611DO008 02 rudders.611DO009 02 Below the full load waterline, recessed lifting fittings, drawing, NAVSHIPS No.611DO010 02 R?805-1834505?, shall be used in lieu of padeyes for ships capable of a sustained spee(611DO011 02 of 20 knots or more.611DO012 00 Padeyes shall be installed for Jacob's ladders, anchor ladders, and abandon ship611DO013 00 ladders.611DO014 00 Padeyes shall be so located and installed that the load will be applied in the611DO015 00 plane of the eye.611DO016 00 For replenishment-at-sea padeyes see Sect. 573.611D0017 00 For lifting requirements for machinery components see Sect. 200.611E0001 00 .SEC.<0611e. Cleats, jackrods, and eyebolts>611E0002 00 <OGeneral.-> Cleats and fairleaders shall be installed for the proper leads and611E0003 00 belaying of signal halyards and rigging.611E0004 00 + Eyebolts, ringbolts, deck screw reversible eyebolts, cleats, and other fittings6IIE0005 00 +necessary for the attachment, working, belaying, and securing of all parts and611E0006 00 +appliances shall be fitted. All deck screw reversible eyebolts of611E0007 00 +equal size shall be interchangeable. All deck screw reversible eyebolts and other611E0008 00 +portable fittings on deck shall be arranged to leave the deck flush when the portable611E0009 00 +parts are removed and stowed.611E0010 00 C Sockets and supporting structure shall be designed to safely withstand the largest611E0011 00 Cload that can be applied to the eyebolt.611E0012 02 S <OCleats.-> A galvanized steel cleat shall be provided in a convenient location fol611E0013 02 Seach hatch fitted with a weight-lifting eye. The cleats shall be welded to the611E0014 02 Sstructure.611E0015 02 Cleats shall be provided for checking steadying lines for boats611E0016 02 and aircraft while they are handled by cranes, and also for securing lines from boats611E0017 02 alongside.611E0018 02 Cleats shall not installed on bulwark rails or in other locations where undue611E0019 02 interference would result when handling material over the side.611E0020 05 Fittings for securing aircraft in hangar and on flight deck shall be as required b)611E0021 05 Sect. 588.611E0022 02 <OJackrods.-> Jackrods shall be fitted for attachment of awnings and weather clotht611E0023 02 Jackrods shall be fitted to the sides of the ship forward of the accommodation611E0024 02 ladders to permit the use of boathooks from small boats.

4,-

7 9

-7

.f3h5 21,1 OF THE BATTsAV" SBA SISTROS COMMAND

SECTION 611 5BULL FITZGS

to6lia. General

This zection contains general requirements for batch davits, padeyes. cleats,jackrods, eyebolts, rubbing and chafing plates, corrosion protectors, propeller yuards.and sounding platforms.

15

611b. DavitsGenaal.- datch davits shall be provided in number, Location, and capacity as

necessary for the convenient and rapid handling of stores to and from storerooms, and20 tar striking down ammunition to magazines. natch davits shall also be suitable for

handlJing stores dad ammunition over the side of the ship if other portable or permanentarrangeamnts rer not provided for this purpose.

In general, all hatch davits shall be portable and furnished complete with tackle.Stowage locations for portable davits shall be carefully selected for convenience to

25 point of use, o as not to form an obstruction in lines of traffic, to be protectedfrom Doarding seas, and to eliminate the possibility of davits being jarred out ofposition and failing into the line ot fire or guns or missiles.

The number of sizes of davits snail be aept to a minimum and all davits of the samecapacity shall be interchangeable.

30 locking load.- hamunition handling davits shall be designed to handle a workingload equal to the heaviest piece of ammunition stowed in the magazines served by thedavit, except that if chain hoists or electric wire rope hoists are attached, the davitshall be designed for the capacity and weight of the hoist.

Stores nandling davits shall be designed for a working load of 1,000 pounds, except35 that tnose for destroyer types and smaller ships shall be designed for a working load

of 500 pounds.It thi capacity of ammunition davits is approximately that of the stores davits both

types shall be designed for the heavier working loads.goraing and test load label plates in accordance with Sect. 602 shall be installed

40 on eaca davit.Sockets for davits.- Sockets shall be provided at all hatches to be used for

striking down stores or ammunition. In general, they shall be located at the corners ofhatches out clear of the corner radius ct strength decs hatches. Sockets shall also beprovided on all superstructure levels for nandling material from one level to another.

65 Sockets shall also be provided in other locations, where necessary, for handlingmachinery parts through hatches betveen machinery spaces and workshops and engineerstorerooms.

for ships not furnished with permanent or other portable arrangements for handlingstores and amunition over the ide*, sockets shall be provided, located port and

so starboard, forward, amidships, and aft, as required to use davits tor this purpose.

611c. Portable weight handling devicesSock:?ts and fittings shall be installed for stepping portable cranes, sheer legs, or

55 other portable weight-handling devices, in locations where they can be utilized forhandling heavy ammunition, torpedoes, and machinery parts through hatches and over theside and for handling stores in cargo nets over the siae ot the ship.

60 6114. PedeyssPadeyes shall be provided in nuavr, location, and cjpacity as necessary for

convenient ana rapid handling of stores to and from storerooms and for striking downammunition to magazines.

Padejes shell be providod over auxiliary machinery as may be necessary for lilting65 parts of the machines during overhaul and repair.

Padeyes shall be installed on the outer shell for use in unshippiang propellers andrudders.

below the full load waterline, recessed lifting fittings, drawing, PAYSUIPS No.80S1834505, shall be used in lieu of padeyes for ships capable of a sustained speed of

70 20 knots or more.Padeyes shaLl be installed tor Jacob9s ladders, ancnor ladders, and abandon ship

ladders.Padeyes shell be so located and installed that the load will be applied in the plane

ot the eye.75 For replenishment-at-sea Eadeyss see Sect. 573.

80 SECTZOM 611

T8

F7ULCC

z

Go 0

0 i 4w 0iP

z0

.w m a

00

z of D--

ww

Cf

Z 00

W Diw c

cc. LL-rn.

CL M,

z

REFEREICE DOCUMEMTSSORTED BY REFERENCE NUMBER

DATE: 2/8/82 PAGE 4

REFERENCE SPECiininininminmmmmmmininnjjminmini....

2. FEDERAL STANDARDSSED -T D- * 2 .......... .... 532

FED-STD-H-28 ........................... .................. 532bFED-STD-H28 ............................................. 075bFED-STD-H28 .................. ............................. 75bFED-STD-H28 ............................................. 75cFED-STD-141 ............................................. 631fFED-STD-4 6 ............................................. 150aFED-STD-595 ............................................. 632hFED-STD-595.............................................. 631fFED-STD-595 .............................................. 6311FED-S TD- 791............................................... 556e

3. MILITARY SPECIFICATIONS

ML-C-17 ............................................. 095-404MIL-C-17 ............................................... .. 404cMIL-C-17 ................................................ 404dMIL-R-26 .............................................. * .... 475dMIL-F-68 .................................................................... 512dMIL-P-116 ............................................... 0809MIL-P-116 ................................................ .. 262fMIL-B-117 .......... .................................... 269gMIL-F-151 ................. ................................ 516cMIL-F-151 ...................................... o ........ .64MIL-W-13. ............................................... 657 £MIL-F-173 ................................................. . ..... 631jMIL- -2 3 ..................................... ... ...... 63 bIL- - 370 ................................................ .631

MIL-H-37. ............................................... 571dMIL-1-31 ......................................................... . 10SfMIL--671 .................................................. 3562MIL--694 ....................................... . ... . .......... 611DOD-E-69 ................. ............ * ......... ..... .6311DOD-E-60 ........................................... .. 6311MIL - -70 ................ .......... ...................... 601MIL- 1-742 .............................. ........... . ... 65bMIL-S-742 ............. ................................. 0 0fMIL-S-862 ........................................... &... 562fMIL-R-900. .............................. .. *......... .... 624cMIL-R-g00 ........................................... .... 6244=KIL-R-900 ....................................... ........ 624f5MIL-R-900 ........................... *....... *.......o.....624fMIL-S-901 ............................... *............... 625lKIL-S-901 .................................. o........... 672a3MIL-S-901 .............................................. 072l3MIL-S-gO1 ........................................ *..... 072a11MliL-S-90 • ............ *............. *..................6 s

MIL-8-901B ....................... ........... o.......... M all1MIL-8-901C ........... . . . ...........0....... . . .. 72 lMIL-S-901C ...... :...........8 ............. o......... 072al16

REFERENCE DOCUMENTlSSORTED DY SPECIFICATION NDBER

DATE: 2/8/82 PAGE 11

REFERENCE SPEC

*****SECTION 100 '**

Military Specifications

MIL-P-1144 ...... ................ *... ... ........ .. .... ..1MmMIL-W-2038 ....................................... & ................ 10ftMIL-W-15154 ............................................. 100aMIL-W-24126 .......................... o .............. .. . aMIL-S-19653 ............................................. i0 bMIL-A-22397 ......................... ................... l0 bMIL-C-22804 ......................................... o ....... ... . . I00bMIL-P-1144.. ......... o .... .................... .* .... slowMIL-W-1514 ... o ........ ..... ...... * ... ... ....... slowMIL-W-2038 ................ . .. . . ............ . . .. l 5MIL-L-2594 .............................. ...... ...... sIowMIL-W-15154. .......... ........ ...... .. * ........ .. . dMIL-P-18066 ........ ........ .... . . ... ................... lowMIL-L-19140. ............................. ... 9.. .... lowMIL-F-19710 ....... o .................. . .*. ........ ...... 1 0dMIL-A-22397 ............. o . .................. ..... . 100MIL-W-24126..... .... o ............ ................... .... lowMIL-W-151o ............................ . . . . . ...... l1ef

MIL-S-862 .................. .......................... 10 fMIL-P-1144 ......... ........... . ................ . .... iSOfMIL-W-2038 .......................................... ... lof

NIL-S- - 363 ........ ........................ ....... .. ... losaMIL-ST-S-716 ....... ......... ...... ....... ...... 100d

Design Data Sheets

DDS 1 0-6. ...... .............. .. .. . . . .*. .... . .... . lfl

Industry Standards

ANSI A199.1. ..... .. . .... ................ .......... l dILTH D2559 .... .. ............. ..... .........

DDSTh 32090........................................... 0f

miscellaneous

XKVSHIPS 250-336. ... ... ... .. ...................... l aMNL-W-24126 ........... .. ...... ... * ....... . . . . . lO0dMVSZA 0900-LP-000-1000..... ........ 9 9 ....... 9....9... 1dPS-i ..... ...... .......9.... ......9.. 99. 9 . ......... .9. 8d

84

NAVSEA "SIP" INFORMATION SYSTEM

1. The CoinpuLer As;Isted Ship Specification (CASS) System isd.-signed to provide information concerning documents criticalto NAVSEA acquisitions, including Federal and MilitarySpecifications and Standards, NAVSEA Standard Type Drawings,Design Data Sheets, and miscellaneous other documents.

2. rnformation stored in this database includes number, title,type of document, issue/last revision date, validation date,:;taLus (up-to-date, minor revision required, substantial revisionrequired, etc.), estimated cost for revision required, interest"preparer. user, etc.), cognizant NAVSEA code, and for documentsunder" revision various milestones and other data associated withthtc revision. Tiering relationships are not currently containedwithin the INQUIRE database, and we are using instead ORACLE for

that aspect of our specification information.

3. Users include NAVSEA engineers, line managers, ship designmaiigers, and ship acquisition managers.

4. The sources fir data in the base are the ongoing stream ofrt.visions to specifications, standards, handbooks, design datasheets, ,nd standard drawings which come before the NAVSEASpec ific ition Control Board; and DODISS updates.

J. The hardware used is a leased IBM 3033.

U. The SIP information system uses primarily the INQUIRE databasemanagement software.

7. Both internal and external support are used to maintain and,)peratE, the database.

&. Output pcoducts art:

aj) PrinLoUtS contLaiing numbers, titles, last revision date,coguizant .-ode, etc., for those Federal and MilitarySpecifications and Standards, NAVSEA Standard and Type Drawings,D)esign Data Sheets, and other documents critical to NAVSEAacqu i s i t ion.;.

h) Prliitoits contaLning mitostones for documents currently.111', Vi,' e(d 1)y NAVS .'.

85

9. '1K : . stem iu multi--user.

10. The database is updated via 1200 baud dial-up, using YTERM IsLtiware from IBM PC.

1I. See previoua item; however, user ID/account is required.

12. The only near-term change planned is a move from the leasedIBM 3033 to a newly acquired NAVSEA IBM 3083.

I". System documentation Is available.

14. INQUIRE is the primary data base management software used bythe SiP information system.

y 'Ia1

86

NAV S iA " I" 1NF( R M ATI N S YS TE H

I. The Speci fI CaL ioil mprovtment Program (SIP) informatiorn)ysten de signed to provide int f ormat ton coucerning documentsrtical to NAVSEA acquis;tions, including FederalI and Military

speciflc,itions and Standards, NAVSEA Standard Type Drawings,Designi Data Sheets, and miscellaneous other documents.

2. Information stored in this database includes number, title,type of document, issue/last revision date, validation date,status (up--to-daLe, minor revision required, substantial revisionrequired, etc.), estimated cost for revision required, interest(preparer, user, etc.), cognizant NAVSEA code, and for documentsunder revision various milestones and other data associated withthe revision. Tiering relationships are not currently containedwithin the INQUIRE database, and we are using instead ORACLE forth.tt aspect of our specification information.

3. Users include NAVSFA engineers, line managers, ship designmanagers, ana ship acquisition managers.

4. The s,,urces tor data in the base are the ongoing stream ofrevisions to specificaitions, standards, handbooks, design datasheets, and standard drawings which come before the NAVSEASpecification Control Board; jtd DODISS updates.

5. The hardware used is a Leased IBN 3033.

6. The SIP information system uses primarily the INQUIREdatabase management software.

7. Both internal and external support are used to maintain andoperate the database.

V. Output products are:

a) Piintouts containing numbers, titles, last revision date,ogniw'aut code, etc., for those Federal and Military Specificationsand Standards, NAVSEA Standard and Type Drawings, Design Data.';eets, and other documents critical to NAVSEA acquisitions.

b) Printouts containing milestones for documents currently

being revised by NAVSEA.

9. The system is multi-user.

I0. The database is updaLed via 1200 baud dial-up, using YTERM

software from IBM PC.

II. See previous item; however, user ID/account is required.

487

1I2. The only lkea-Lerm change platned is a move form the leased

IBM 3033 to a newly acquired NAVSEA IBM 3083.4


14. INQVIRE Is the primary data base management software used by

the SIP information system.

I

88

68

C-LUL

U)-

U--

LUJ _ LU

CL-~ U)

C)c of CD

or) - L

C)J <1 LUJ F-

LJ D= C3

* LU U) LUI ;_

0:f LU

0... N) C'2 M C / ) -

cn LL JL - C/)CD w LU LUJ

- LU LUJ

C' C D

-4) U) CC/) 5) L1

C'-- LUJ CDC/ ~ CD LUj 0- %

0-1 C/) >- LUJ U)

LU- - t- I- c-Qv -- i C

C_ V) - 0- U-

_k- LU C') U-U 'HLUJ 6- U-

C:) F- V - U- U) U LUJ U) C:)

-L PCI CD

C)~ C~ CIL F LUL

_ I. a_. LU- c U

U') 0) L-) LUJ

LUJ cn LUJ LUJ U) CD -Iccr -- L UCl C' C

CD LU Lu LU L L

cn .- 0.- 0.-- UI--lH

06

tv

0 0

40

wz

4.j0

L)I

UIN N 4~

S-- 1-4 M~ ' N N N N NN N N X

0.XXXNXXXXC>-X> -X>- )( >.NNNNNNNNN.NNNN)X NXXXXNNNt. ) )

- - -000 -- 0 c-0--

0 V) ~ o l\-01 \t m- . -. "C- -"%L~ fN al .r.N \LC

6.J X

C; V)> 0U

M* > I- 0 ) -,x w jL )u 0D zV

< t- z a) r u i~ 0 nZ

0 e Z L- L) - - Z- M -- Lo - M- - > L- L~ V)0C). ) >- > Q )

. M V) X- Z C.-- Z. ~~ )-~ QC 0 > ) U. 20 z OULo = S - <) ^. U - l -L .JU cr U V-4 0 z.J -- z ) l L

-. < - -j - ~0-)L.U-o x) Q) 0 >-- S -)W-K Z >- Z - .D O c -~-XW )C0 0 r J) --- -l

- , -L - */ ~- < E - Z--00 - £/:C/) -4 <4f~'~

2 S-)Z- 45 x :r U-~0O -L122 .rwu z~ 2b2 ZI = -- 2 < MU 0 Cf - 2r l W-0-ZZO ozwx4.w 000 12

2 = x~o o SaI)<.' ZM OOMOC.-Z CL-Z Z C- 0;: - m U OIZZ-- Z4-- (-

<2 .2- 0-- mU 0I-d .- - a- .Ja< . w CCZ 0 - Z 4 Z --C) r<. << . 2 2-O)-4U) 0 ==)~4W- -0Z n.--4ZZ-

0 ...- z<>'...-= 0f-iIz-C)) -00-.J<-L.i -cs ..- -01-mm< <<<- .a 0 - )-O) W L/)I 0 -x 22xz4U0< 0 l.x w u.JIw .. AU0I)Cf(n lU =.J<ZC D2..a b z) z zZ > )Lf

n ZZxZZZZZO~--C).anwwxo200 42)U ZmZ2Zz -W~ 00 z )

.7Z -f Z

T6

N. .04 N

C I

0C

In

zM D

L) z

<

4c C

-- -- - - -

C0 CC O 0 --- CC00000C C- CC= C C)

_r N N N -7-. 7N N I v- j- 7=- r- 7--- - r Z=-

c C 0 N N N O0 0 O'O'0 'o c, 0 z:,

-iC CON CZO OOC aC C CC Z N C\C CC CC= - -0-- -

o' CC Z cC CC C c =C - 0C=CCCCC C Z C CC CC CC CC(0'c - o o ~ - r-- C W I o m w o

z < EO4 ZE

o Uz so w wI X U_ j_

= 0 L< a< < "

o~~ ~ c 0 .. I~ . CC C CZ C CC C CC CC=~Cz x C

OM 0- 0-J0 U- o o~

4Z U = (4w1u -WOW C ~ 0U -- U, U=)c,~n

U ~ ~ -c < I< E M~ CL. (L x tJ I -0-- J 01 0 M __j< X< 4 -.-- x >aJ -- XC0 -v a, <

-- Z -- U ~z n 0 w LL.J -i ~ <x C-.-0LLJOU, . -L. .

I ZC 4 = ZC ajC..J---~----

- - -~ -Z00 -C -~ -- -C 0 -ZCL 0. 0 ,.) 0 ZO .- a.

>

V)0 o -- >U~ E a - 0- z , 0N-C--C C-

Z *Z- 4C ccaa4 goJC co 00 ~ > O .co cocccocc 0 3 COC..h lLi ~~~I4< --, N 1%CUO -r... CC I% IN - "Z

L- rn -~ J -in* r4 t- yv0. U- .<.--z M4La44

L M X.- LULZC I a0 ZJ EC *Zj6 0L aa~ L -r4 :M

4~~~ cx=Xo - ICC. '111-C.-J".--U() -

cy-, -,

N NU

N' UN CI \

mI.J-* N0 N'..l \ ~ CJCj-C

LI-=: c. Co o C C SC C C - 0 0 = - -occ P- doIa D0NC% W - - NNN r '

0;; a"C o rJ c ; o 0 o '

10 0ajaI COW aX . < ) V

m4 z -W x u L

< I x 0 00 00 00* 00 00 0N0 00 00 00"00 0. 00 00zo 0 i m09 -

>a -wx'WLN N"- - x~" ' C

o M W < '0O O'O~iz wz.-C-V z

1 -~uer i~tr Z ;-w ZMI. j000 4=a .- 00C

;D z CL - 00 <- ~- -- =--LLJM .>-- -C-CuW- Z'.'IL -

1~0 0 00L-0 - 0- 0000 -0 00 np-00ou~ 00 0 -

Z 0 L: 0CX -a Q .0W>wC Wa z 0

0. , a ) Z ULU ~ w

0) <. 2JO CM aZu n< W wwoc xm. O<UU0000...00

LW=a wU4 .- U 0 .4 -Clcd)-J U - Q- . >- 0 < <2 a >2-0 'W z - ~ 2 Cx . U- a

0 ~ a < 4 2 0 flU 44.J -> -30. .U) .) L4 0- -O ZZ 2

< U) a - = C flU .CLUOO ,a0.UJJ>U)>..JO .U ).. 4L. U)O -- 4 .4. .4~) 4aU)2(i P U2 U00L4*)- 0 2 0 ---22 2- _- 1 240 )~ <14.0 CL4LU<..(J - - --=

U) F07 xi clf7 7 X .~ .27 .(i .. .00 1- Z- L .7 -0L.7 7>~ *0 .7 T-Z

N "U 10 4 L^ U4 =2 z 020rJc)= 0 N.: Z ~ *7 Z 5 Z L.-0U) I. .2 a ZZ2~.4 00(. U -20lU) )0Ui-Z-2 L -UU).4rQ

- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ m an 4 Z o-)0 44-4 - . 0 U ~ 4 Q U 0 0 U

E6

N~ NN~ N

400

U.1I

4-x z

4( 0

NN N

N- =- - ,- N N '

>4- I

0 r L . _ . L C r a a a aL0a a.00 0.0Z.0C0a00000.00000 0.00 000 00 0 0. 0

0~ s x3'~A ~ 0 z z

0 -w 0'>-*W MX\ M C~ - n0 Zj oc

L; - j_

2 0 zo24M C

< 4 -. - I Ij "0 >0 24

=M - 0 V) 9 ~06 0 '3.u.<4-

40~1 10 0 -nV- o < o

> >>>>>> >>>>>> >l>>>>_0>-00

99 40 -0 000Q00-GD 00J- MOWOM4' MN 0 WO WWWN NN 0 N )

an ---- > -- -~ -. 4- - -~ - -N . .

4WO co W w 4 V-NX N w xN

ZM - N- N

-oC c,= ~ =C N C3 :!== CNO =n tN a-

CC -o ~ ~ ~ ~ ~ ~ N N N~4 -CjC\ N- N

> > -

z

C, 0>- (fta

a.0 Wt 000 00 ZCC O w ov 0 W0C C 0 0 C zz Z<- wx-NCjC'J I -' _j3 N' f0~e N

o~ cr >U) -JO r-f 0f' tf

xS -- X Xtff-fiL; WW

a.- -O - 0 0''- % - Nt~t-'

cr .ft N NWOE= NWUNWC %.OC W~o ~ ~ c .w" !-:E '3''3O'33'ft .OO33O333''''% '''3333O33 o'3fo''O'O'3O'OOf<'

=>) WSU - - J - < )- C- L

In Z - -J

ft. I 0WX ~ c o ZZ wan Nw q=- - v)wn -U L u

I~~~ '. f LJ u> .

Zt - S L L.f - C' - ac

CC =t 0>..- C.O N C. ,ZZIn I (fl4..j .- a, 4 -r j '- UXO\Z NZ. 3 I

ZN 0Y Zt - L" N Ca> C.2J)O. N -0

-~ ~~~~~~ X.. Xt X XX - -0 -- -LOL -0..- -0 -~0. -fU) - .. J

u U 0 V.,f V5 4 CU) -~ ~ -(lhU ) -U.i - -C 0-s 0- -C

U)A V- Aa VS -I -- --- -- -~ U~ -0- L . f -Z. -JO-.- --- X-4-U)~ ~ ~JL 0 C X--t.S x00J ) xZ - -~ x4 m..u-.x

p o'0 '0 ~ L4 0 0 '0 '0 ~ .-. S6

O0 00

0I CD 00 000 00 0o 0 0o 0o c 0z

z co

2 00 C zu 0 0 0 Go co c

'0 N Ia V)

-1 -M Il0'0 I- a

P .t.- aY Q a

I0 I- 0- UJI000 0

I.. In I

a CO 0 "-)i. 0 0 '0 aLJO-0 ac \0 '0 j \0

Cta- a c c I o c o 00 CD c l owz -I

- ~ I I ' 0 >0i~~~~ a *;*0- 1 0 ' ~ ' ~ 0 0 0 0 0x'0> a: 0

> 0

uC.

I; I n I

z. <

\Z0 -_ 11% -.0 o z3 \0 10 \

0 402~~~~~~1 0 L.O I - 0 0a' 1L - ~ 0 0- N 0 0 N o '

0.Ix I < .

2~ ~~ 000I . ~a>0 0 "I - 0 3 0 . 5-'0 1- '~ . - - i0- a IO C601 1 X <0 co a.S '0, 1- - II -N <<

29 0o m- OZ --) w N'-- - - 4 a- 0:l 0 1 -

0 x 15

'X oz c N - -. -

z .- w <. y N I, N(

4 - L; x Z x 2

96

-40 40

0.

00 ; C

CL 00%0 00 00 0000 00000o 0006- L 06U

6j: ,-----------------------------

>aZL

4 :

w 60 C 0 0 0 GD00 O 00D0 O0 000w0C0 0 0 0 w00 0 0w

0 a 0

0. ZJ 0L 0Lr La - Q - a l .Q -M -a -a -Q La

0 >>

o . -

- =* ** Ix Ix x % ix x "- z ' 4 0' -- %0

L; - 000000000--X00000003 0=0-0

0 Ww > 6j c- .. -

z- 0Uo - : -z X -to

z 0 2C - 0 Z ) 0 w n00 -

Uxt - 06

I -j

(A z u

-11&zz-2- 1 z- -7 N -I~ G - - z z

N, 2 "I "I 0.2 T N *. N.TI.NZT"1 \ l~ . r-. 0 0-o c m v L --, c -- U U c

- 6> Z 2 2222 0-0 - 0llaXZ *-J l0~~~~~-L *- 2 X X X > - c~f0~

L6

-LJ

LW

Cl-J

00 twLL WuiniflochO'C'3(' I I

0-0O - 0o (')w4ot*- -TQ61 C CI -t w c o r-r#in (DI I Il-I--tii VC) I IJI I WJI I a a o )

I.-U-E

LU

bt

ATTACfMET 6

COMPUTER GENERATED ACQUISITION DOCt3KWTS SYSTEM (CGADS)

079

OEPARTMENT OF THE AIR FORCE)ICAUQUARTEe ELKCINO$4C SYSTEMS oCA1mOm (*AFuC)

HANOWM AIO EASE. UASSACH4UUTrGrr f5.1405

I AL IR. O'Neil)7 MAR '"

s.tiqce: Request for Informatlon on CGADB

Ho Rq AWSC/eLEQ

1. Reference the folloing letters:

a. Office or'Assistant Seeretary of b onso Neyo, OStudy ofspecification$ and standacds aesated computer system," 19 Feb 56.

b. Igq UaSAV/ROX Ltr, same subJect, 26 reb 56.

a. Nq AreC/PLJQ endorsement to 1.b above.

2. Please provide EID/ALZ (Mr. O'Neil) a copy of the responses f0m the otherdata base users. The following Lnfotmation is provided in response toreferenced requests. The queienS, copied from reference I.e., Attaekment 1,are answered in the same order they were asked.

01. What was the system orLgnally deaigned lo do?

Ale CGAD9 is a software program used to Prepare drafts of systemacquisition end meanagement documenot, Users do not need to know AnythingaboUt computer proruimnflg and minimal System acquisition expertence isadequate. nequiruenks are tailored and unjqtlely cleated tar any acquisitionphase. Duplication Is diasQouraged by providing guidance to put tasking in thethe east appropriate document, loe. SOW, speclfication, CIRL, o Contractschedule eta. For example# technical requirements hould appear in thespeoification only and i3 be repeated anyAhate else.

01. What Info:mation to presently stored (e.g. document designation,references, approval date, edo.)?

AZ. COADS stores question., answees, action mesaaes, end Actualparagraph text. Reerences to applicable NIL-skandards/epocifioatione Aadstaff specielists OR are Identified.

03. Wno are the system users, i.e. fcquieition/pcocurseent offices,standardization anagers. speoLftearlon vrLtecs, maintenance, logistio ?

A3, Primary ueers re cquiaLtion/procucement offices vhoh Include*englnesting, Ham, configuration, data, logietics, etc. CGADS assistsCtahderdigatlon Managers by carrying out tailoring. Opeeifiatijon writer& mayuse it as a refecence to understand rhw the SOW and CDRL were created.Personnel may also acces, the z50 plan.

, O O 1 0 0 N 1 G 7 : G T 9 8 / o E

101

94. What lre the *ouro* to& data included In the base?

A4. Igo staif *pecialists creat, the data bsae information. For example.the staff systems engineer vites the system engineering section of the 30W.

03. What hardvare in used lot the syOtem?

AS. System hardware Consists Of I DEC VAX 11/710 mint-cowpUter, VT-100terminal oc orptiblea, and dedicated word pcooessor (e.g., Wang, CPT).

Q4. What types of progrema/lenguages are good?

As. PORUTR 77

Q7% is internal or enternal support used to 1oad and maintain the data

A7. We do not Use any other program to load C44". Currently onlyooAnttotr englneers Can load and maintain the ata base. We Lnaend to haveQleakt trained to do rOUtLAO data base updating.

Q8. What output products ae obtained frou the system?

AW. Statement of Work a AiL phases.COA

Program Nanagement PlanI30 PlanRdliabil1t Centered Kaintenance (ACM) - develop end track sc heuled

aIntemenoe.Output Is uSU411Y a ptintsd copy which my first be VLeGed on a OUT

before printing. Stagg points o contact ao aplicable cotecenoeo

(xZ-utaArd/peoItIast&..l Ata Identfltied. OutpuL m&7 be btafereed todedicated word prooeaaoca to be ocalered.

00. Is it a single user or miLt-uer system?

A$. COAvP La a multi-ami system. Anyone who oan access the system (gae011) My use It simultaneously with other user.

Q10. What prooedurss are used to maintain the data baa.?

A0. tff sPCialieta update the data base text. The syetadM/IfLOtoatf aPprove. data bane change4 A support conbractor Inoerporatesapprove4 changes into the OAh date bae. (Son alao #71

L G I-00 O N T7-/ GS3 9 : T 98 10, 10

102

QlU. IS there remote acceas to the system? lhat communication links ageused?

All. Remote access in aoOompllmhba by dialing any one of seayWl phoneVmubeg via voice quality autoven or eomierciol phone lLnes. See 05 forbadware requl remnta.

Q12. Are there planned chang~e to the sysem to expend It or to add

*fthanboeantS7

AI2. In the neat term, we plan to modify CQhAb so the a olerk may makeroutine update to tne data bame (a #7). At that tima, v will upd&te thedlata bass) to includle thfe 499eots a o - - 47 Defense system& Softwte

Develoiment, 4 June 85, and othte policy ohaaqee. Ihtpnsion of CCAIS toprepare the system specification Is the next planned major effort. ZItercacewith other systems euch a Contract onto anelemont System (CDNI) ace behingconedered.

013. i system doou 4tation available?

A13. r-Lated documentation to available.

a. *our¢* code and data base latingb. Doea iptlon and Operation NoOkletc. Requitrements Documents (not autbentilated)d. Veers Manual 'not authenticated)

g14. 10 a dat bee udnagr4Aent Systa (DNS) uae7

Ai4. Nee.

ROBBIT M. STANTONbirect.r, Ingineerig and TestfeuUty for Acqulsition coLSUtI05and Technical Operations

10,3

Synopsis of

Computer CGnerated Acquisition Documents System (CGADS)

CGADS is an automated software system used to generate technical and mangement

acquisition documents, such as the SOW and CDRL. NO computer experience and

minimum acquisition experience is required. Using autovon or commercial

telephone lines, local ESD and remote access is possible. Documents

colt-sining miniatum re(lar(-;rents can be prepared in minutes and are

sj'ecifially tailored to individual acquisitions. ESD staff prepared the data

bne an, simple questions/answers for each of their specialties. Users answer

the-e qpiestions, by replying yes, NO, or Undecided which creates the text.

They may view what they hdve created on their local terminal. The documents

may be printed on local or remote printers or may be Transferred to a

dodic-itl. word processor for completion

The C(:A[S data bVise must be updated by staff to reflect new policy and to

simplify its iintensnce so that other than an engineer/programmer may. update

it. The software may be extended to create other acquisition products having

DOD wide application or tailor new or existing documents for unique

service/agency use.

105

'AD-4171 326 PROE~N~O TNE PDAUOTDINI O 2/3ES1CALITNV 13 myLUR I -E34

pU14CLASSIFIED / /2 M

1,6 12. 12.5

= 1111II i11 I.*O -

1111.2 111 ON4 i .

'CROCOPY RESOLUTION TEST CHART

NATIONAL BUREAU Of STANDARDS-1963-A

L-

LOI C3

C) C.)

0r C)l

C:)

~ C/) 0

LA- I- <

ck: C:) X:

CO Ck - LL) ~

"CvL- V~ CD -L NCJ LL ) CXe a) ~ ~

C-4 L9-. >< -

Cl) -CC*< UC~~~ )4 .71 )

C) LLI

L ~ ~ * C3l -LA

00 --

Coe) 0 U

Liir C') C/

- LL) C) 3

cr C3LU C) C) C)0- ~* L

C' 1 Cl

801

C3LAJ V--

LAJL&J

LIJ

LI.-

0L I

Lii

C> cc C)

8-41-41.I-A LO2C > I.C) a.. I

LL Li

lz LL. LL.LaAc-.&. Co C

*A *L 0ico

601

L&J

(.D

4-3

I-CO

I-L

TOTT

Ca)

C)

Lai

C)

C-,-C3) L

I-C) (3

C,, (JF

C) w

CC)co LL. 2

ca 2:J

LAii

1- 3 ;Lc C.3

LLI-I- Lii

CHART #1 SYSTEM IDENTIFICATION

CALL ME FOR GENERAL QUESTIONS ABOUT C

CALL FRED SANTINO FOR TECHNICAL QUESTIONS SUCH AS COMPATIBILITY OF YOURLOCAL EQUIPMENT WITH ESD's

CALL THE "HELP DESMK IF YOU THINK YOU ARE DOING EVERYTHING ALL RIGHT, BUTCM APPEARS NOT TO BE WORKING.

CHART #2 SYSTEM DESIGN

PREPARES ACQUISITION AND MANAGEMENT DOCUMENTS

SUCH AS 5(41. MflRL AND OTHER TECHNICAL AND MANAGEMENT PLANS

DESIGNED TO SIMPLIFY AND AUTOMATE RFP PREPARATION

STANDARDIZES FORMAT

SPECIFIES MINIMUM REQUIREMENTS

REQUIREMENTS ARE TAILORED

UNIQUE FP CREATED FOR EACH ACQUISITION

USER FRIENDLY

PERSONS WITH NO COMPUTER EXPERIENCE AND MINIMUM ACQUISITION EXPERIENCECAN USE IT.

PLANNED UPDATES AND EXPANSIONS

ADD ENHANCEMENTS

ADD OTHER DOCUMENTS

ASSIST IN fl]M) EXPANSION

CHART #3 SYSTEM CHARACTERISTICS AND USAGE

DESCRIPTION

INFORMATION STORED: QUESTIONS, ANSWERS, ACTION MESSAGES, ACTUALPARAGRAPH TEXT

ORIENTED TO ANSWERING SIMPLE YES OR No QUESTIONS

APPLICABLE MIL-SPECS, STDs IDENTIFIED BY TITLE/DATE

APPROPRIATE DID'S FOR EACH TECHNICAL AREA IDENTIFIED

STAFF PR'S NAME/PHONE GIVEN FOR EACH TECHNICALSPECIALITY

lii

WHO CREATES DATA: ES STAFF SPECIALISTS CREATE THE TEXT FOR THEIRSPECIALTY

AD HOC: USERS CANNOT FORMULATE THEIR OWN QUESTIONS. MUST USE ONLY THEQUESTIONS IN CM.

STRUCTURE: THERE IS IO SEPARATE DATA BASE. DATA BASE IS EMBEDDED IN

THE CM SOFTWARE.

EDITING: MUST BE TRANSFERED TO A DEDICATED WORD PROCESSOR.

MAINTAIN DATA BASE: STAFF SPECIALISTS UPDATE THE DATA BASE TEXT. I'MTHE SYSTEM ADMINISTRATOR AND APPROVE THE FORM OF THE CHANGES. ASUPPORT CONTRACTOR INCORPORATES APPROVES CHANGES INTO THE Cm DATA

BASE.

DOCUMENTATION AVAILABLE: A. SOURCE CODE AND DATA BASE LISTINGB. DESCRIPTION AND OPERATION BOOKLET

C. REQUIREMENTS DOCUMENTS (NOT AUTHENTICATED)D. USERS MANUAL (NOT AUTHENTICATED)

SYSTEMS USERS: PRIMARY USERS ARE ACQUISITION/PROCURF"-NT OFFICES WHICHINCLUDES ENGINEERING, R&M. CONFIGURATION, DATA, LOGISTICS, ETC.0GADS ASSISTS STANDARDIZATION MANAGERS BY CARRYING OUT TAILORING.SPECIFICATION WRITERS MAY USE IT AS A REFERENCE TO UNDERSTAND HOW THES0W AND MJRL WERE CREATED. PERSONNEL MAY ALSO ACCESS THE EEO PLAN.

OPERATIONS:

OPERATES ON THE ESD VAX 111780 MINI-COMPUTER

REMOTE ACCESS

DIAL AV L78-XXXX OR (G17) 377-XXXX :2102, 2231. 2368. 2454

TYPE ESDVAX. NO SPACES. HIT CARRIAGE RETURN ONCE. HEAR TONE.

PROMPT USER NAME: TYPE ESDRFP. NO SPACES. HIT CARRIAGE RETURN ONCE.PROMPT PASS4JFOR: TYPE CGADSUSER. NO SPACES. HIT CARRIAGE RETURN

ONCE. I REQUESTED THIS PROMPT BE REMOVED

EQUIPMENT NEEDED

VT-100 TERMINAL OR COMPATIBLE

DEDICATED WORD PROCESSOR, IF WANT TO DOWNLOAD AND DO WORD PROCESSINGWITH CMADS OUTPUT

PRODUCTS

I. SOICIJR[ FOR THE CONCEPTUAL PHASE

2. M0W/0IRt FOR THE VALIDATION

II.

3. SO4CDRL FOR THE FULL SCALE DEVELOPMENT

4. SO041C FOR THE PRODUCTION

5. OIMCDRL FOR THE DEPLOYMENT

6. RELIABILITY CENTERED MAINTENANCE (RCM) ANALYSIS

7. MULTI-YEAR AFFIRMATIVE ACTION PROGRAM MINI-PLAN

8. PROGRAM MANAGEMENT PLAN

9. ACOuISITION PLAN

10. TEST AND EVALUATION PLAN (TEMP)

CHART #q STATUS AND RECOMMENDATIONS

STATUS:

(GADS NOW USED DOC WIDE

AIR FORCENAVYARVIWV'T AGENCIES

WE HAVE AN OPERATIONAL SYSTEM AND HAVE A CONTRACTOR ON BOARD TO ASSISTUs.

RECOMMENDATIONS:

ENHANCEMENTS

ON LINE EDITING

SIMPLIFY DATA BASE UPDATING - BY DATA ENTRY CLERK VSENGINEER/PROGRAMMER

UPDATE DATA BASE - NEW POLICY

ADD MORE PRODUCTS

TASK ORDERS, SYSTEM ENGINEERING TECHJICAL ASSISTANCE (SETA) CONTRACTS

SOURCE SELECTION FACTORS AND STANDARDS

INSTRUCTIONS FOR PREPARATION OF PROPOSALS (IFPP)

SYSTEM SPECIFICATION ("A" SPEC)

OPERATIONS AND MAINTENANCE (OWM) RFPs.

113

TAILOR CGADS FOR SERVICE/AGENCY USE. NOTE DATA BASE IS EMBEDDED IN THESOFTWARE.

PRESENTLY, ESD CAN ONLY PROVIDE UNMODIFIED CM SOFTWARE AND WHATDOCUMENTATION WE HAVE. EACH USER DO WHAT THEY WISH WITH IT.

ESD DOCUMENT CGADS MORE FULLY. ESD MAKE AVAILABLE NEW DOCUMENTATIONAND UNMODIFIED CGAMS SOFTWARE.

ESD, THROUGH ITS CONTRACTOR, MODIFY GADS S/W FOR SERVICE/AGENCYUNIQUE USE. [ACH AGENCY FUND ESD CONTRACTOR EFFORT.

I I 4

A"lACI'I '4T 7

TECHNICAI AND MANAGERIAL SUPPORT ENVIROIFNT/DOCWR [TER

(TEMSE/I)OCWRITER)

ATTACHIENT 7

DATA BASE 'I PICS

1. Thc TEMSE/Doc-,writer system was originally designed to aid thepreparation of A-level specifications, in accordance with MIL-STD 490, andStateno.nts of Work. Soon after start of developnent it was generalized toaid in the preparation of any document with numbered paragraphs.

2. Information stored falls in three categories:

a. High level tutorial on SOW preparation.

o. Description and by-paragraph tailoring guidance of MIL-STDs.

c. Technical and managerial support information for each paragraph oft.we document in preparation.

d. Specification, CDRL an WBS Modules are under development and closeto conpltion.

. TEMSE users are individuals in or supporting acquisition or procurem-ntoffi~ces who are preparing SCWS, CDRLs, System Specifications, and otherstructurod documents such as Ccinputer Resources Integrated Support Plans(CRISPs).

4. The sources of data in the Corporate Memory data base are theacquisition and logistics staff personnel.

TEMSE runs on IBM mainframes and can be transported to an IBM PC.%'r/370. The potential to rehost to a Zenith PC AT is under investigation.

6. TEMSE is programmed in PASCAL, PL/l, and SPITBOL.

External support to load and maintain the data base is currentlyprovidod by an FCRC, The Aerospace Corp.

,i. S(Us and CDRLs have been generated and made contractural documents. AserLos of eleven CRISLs are currently in preparation.'. 'EMSE i- a multi eusr system.

J. ConfLguration control banners label each corporate memory data basef .(Id as a means to control the contents of the data base and indicatec urrenc-y of the information to users.

It. The system can be accessed remotely with ASCII terminals viac'muercial telephone lines.

IZ. TEMSE is a multi-faceted operational tool. There are minorenhancements in progress.

13. A copy of the TEMSE Users Manual accompanies this letter.

14. TEMSE contains its own tri-structural, mechanical DBMS which wasdesigned to accamodate unlimited expansion of paragraphs and subparagraphsof document as they evolve, expand, and are restructured.

i. :-"STEM IDENTiFICA7ICJN,The naffe oi t h js sv s Ien. i TEMSE'1DOWF TEF,. ThE svstem, point

-contact +or uesiom asoeti, is M--. -- Matt, tt-e user point oz

:Cnt act IS MSN. V. SLIQ&'. and tre svsten !T,anaOer is M r. M. LLbo*S[v:ei 1 i rorm The ,-'erosp'ac& Co-poraltion. The :-:act- Div~ision Proaramin. rger- is M,-. Cner aldc Hvffan, SD 'AL.

'--,'TEM1 DEidJSr' ITrEMSE ii-: aesi oned 'to hel p write aic! mriae strUCtUr'ed dDourets

lnvlUdinq speci~ications. CDRLs. SOWs,. and WE4S. In adcition. the--"Etenv is e repc-satorv n-f corporate k:no'wedqe and wirll SUPPortand auloment a variety, o+ trainina applications.

WhiAt. nisiles TE!ISE ULILual arid especi al lV USet~l( 15 itscapabilitv to enter and store informetion related to each reoUire-merit Rlona side the- actual tex;t o-f thec reOLI.remrent itself. It is,P Lser-frienidlv. menU-driven systern whicn is diesicined *or a personwith little computer e; perience.

Planned chanoeE include stLudvinc the miaration to the PC.optimizino the rUntime ec-4iciency, and improving the audit trailLapabi lit\Y.

S"'CTEM UJSERS.Prime users are acquisition manaqers, Who Must prepare

strulctulred documents +or peneral and contractual application. Thesvstemr has beer used to prepare SOWEs. CDRLs. specs, CF:'ISF's_ ardapplication proaram users' manuals.

4. -YETEM DESCRIPTIONThe corporate memory database is comrisec o4 staff analvsis

Oct aCaL1s1tiOri management svstems. IDIDtE, tutorials, and, specimenoaraoraphs iron: a variety o-f documents.

Ir additior, to qener-ating standaro noUSer-cdefined contract-readyv dOCUnsents, the civstefy provices :tr&ceaLti::-tv and veri-ficationiaiitrices and accountaoil it,,. sort ano cor-tent aniilvsis repoots.

The syr-teni IF, m7U.l-User * pe-m~tt .rir- rer-ote access usirlcst. ncard phone !-,vies. Thie svsterr -roes !otr. date, processina'Ard word roncessrcj p-~rabilities and :, mai-trame-baseo.

P. ECOMMENDAT IONSThis svstemr was recommended for E'OL-wice aprlicatiorn by the

inspector General ir, their laudator\ write-up. The system canbE e4±F~\'c1Y u'sed tc- promote strearrlinina. tailorina. andstandardization because o+ its wide varietv o4 applications as,, niarauerial tool ft-r the creation and control o+ reoUirements+or ell DOP activities.

*Iechni ca! iAr., tanaoeri al -UC.Jport Envi ronmen-t

O~C)

p

z c_ 0~

x 0 C0

C) U0 L J

U) <U <C)

LL& cc W

UJ ZL C w>-=<i < N

E "- ::!:z

0 0 0 <

0Z

cn+n c

OCl)

C/) LUJ

m ~ LU

o CDD

00

LU ZJ

C..) le (cc L-JLw

< - CD

cc) C0 C/)aC LLU cCD C

< C-) z

E LU <

C)

CL)0 LLU<w

CC/

C) uC

0

L~CL-JL

o)C) c

<0-

_ z <

C0 0 0- < 0&-

C.) 0D mDCL ~ U

LL LU 0 c 0

cc0 0 LU) LoLL. -J >-zC) > L L

04 c c * 0 * 0

I-+

00(.

INJ < L.

Z < AJ

I- L><L,

z -J

_ .L&JJ LAJ

0- LP L

co

MO* -~C C.,. m C Co.;

I C

zo 13-J Z=C

L).

C' LLJZgm ac LA,

QD ::>w

zI- LA, LO) Q - 0

I-6'JCLQ.

0n4

Ic,

C.,CL

LUI LU

LCL

CL z- LUJ C) ;LU L LU

-. m 0L 2< LLJ 0 -L. :

L) 1 CD LA~L U 0 L-L Z0)

Q)~C C/ O .. J LCC~ l =L L o < M 2

C C L 0 2 <Z 0u cc--

C 0 <U LULm z 'Z UU C-)CCz cc~cc CDM ) az

LLIULU0E c j3: C C

C) < < = )W 0" U

CCc4 LC*4) C (n4

CLL

LU WC) z< E

-PJ

x~ c LU

< Z- w i

9L 1.- Z _. _

0 L -- u. LLU

<- LA- 0

-J 0 J

00

U.'

z

U)U

+ 9 c ..

og o

ZCD'

LU

z

COD z <

LU0

E ~ z

CA <

00Clc cc0 cc

+

ccm| i m

+. LZT

CJ

CC,,

LAJ

LU>C) -J

CL

4-J

> z.2a OuLui

6) .- 4 S2

44. 80

.* .

. . . . . .

.0 . .

= C.4

wL w m

o x > 0.- 0 4S n U

C0 U)

U . > .0

LA - y- - L & - XL -:

0 ( w L *- v- .wU w2 U * z U) wD0 0~ uw iu-oiO )ju Ifl a -0a ofw 0 3 ~U w Q 0 UJW

.y0 z X I- L- I2~ W2U -\O -. C) U9k3 t u- Z LL-w lI-LI w 0 zW

:1 .- L tLL 0~U L uJ wU 02 UoL > ~ 4l(L W&0 - UCU w 0 U0 M MUU

x-W -w00 0

W um ~f~~N * In Ut'b~~~~~~ ~~~ .. .~ .~ . .l ~~. 1 P ' E~p 1 i n i n i n i n e n i * n

-+ - - - - - - -

.4 .4 . . .4 . . .4. . .4 .4 .~ .~ . . . . N j ri \! N ( N

-I -I-

. . . . . . . . . . . . . . . . . . . . . . . . .

. ... . . . . . . . . . . . . . . . . . . . . . . . . .

w

0

S. .... . .. ..... ............ . . .

. . . . . . . . . . . . . . . . . . ". . . . . . . . . . . . . . . .2.0. . . . . . .

. . . . . . ._ . . . . E . . . . . . . . . . . . . .

• . .' . . .# . . . . . . . .

. . . U . . .. . .... . . . . . . . . . . . . . . .

. .- . .- . . .0t(3

. .. . . . . . -. . . . . . . . . . . . . .

L'1 . . . . . . . . . .0

S. . . . -.. . . . . . .L . .- . .. ......... ............... . . . . .

M . . ..... .... . . . . . . . . . . . . .

I 1 I I I I I

U+ 04V , ~ ,L ' Ia E . . . . . . O . . . .

IL 0.0 U CJ ' I * . u . .i .

C 9jOCUICL u 0-'.0 O0 uU r

Z r 0 9; (1 +1 0r- f 0 cC a 4( M a u co 4- M iCC L 0 to 0. ED CD r- .4 0 Gn U 0 OL. CO i W 0 0) U n LD I f

w u 30 -4 (U t' En of I4 cu 41 0 1 Cn 1U 0 +U EUN N i nILOu ~ U v a .M 0 a I 0 0 C a -

0 ~ I 0 iU. 4- 4E ~NNNN NE U N EU IU I U

0,~. 0 Z U 4 4 lb -4 - E 4 -- 4 4 -4 4 4 J44 . -4 - 4-4a (u 0 in an P u an in Qn an in Ln in Uni ni na,~ ni ni ' na

Z D(

OtT

+ ---

a

a

S, , - - - - - - - - - - - - - - - - -

C.

L 0 -a

L . .,. -0 0 ,*,C') cr L 0 0 n

>. V 4-I e C,---,- " -"" " €. r '-" 0 D.

S.,a 0 -> Eu'' EM " E 0 0" - w 2 "

. , -, --- 0 U, -, w i/ 3-

V 0,.- 4 Ln -"- 0,

IC~~~0 C to:3E _ Au L 0L

CS~C C- L- oC.-0

co 0J u w - m1.j u C m " .I r-- ' *- .. 0 .,M V Cs 0 m"' M w,

SS &-,,-- --- u 4- E 0 c V r - C L m

:I, 0 a .& ' ".0 0Q- " ccua O

- ' 0 . c S l.- cc, - - -" ,

0 G;($. T-,- 0) ", r- L. .. G

E vC o ,S,- 0443 , Lk -- --. Q) U"' I ,0 ' 4) -Z V

' ' 0 E a) 3 w L- C,.- r. ;

4-j 4A a) m) a)" L-O $ . " C) -uo ;; AS J- .. , J A V) to M- - U.. w CT " C-

W J ). 4 CA S S r s-I 0 W - W 0.- u _ . 6- M.. >: -

W~~~~~ 000 (UC C >. (I. : r V --- CC

V, I.-mmmm mmm C' -m -: V -

+ TET

cdo 0

0l~ Vc 0 i

0 C

0 alC0

21 - 0

u Li

M u a a

0 0 ED yI

0 I >

c cDn s .D LE lD

C r c

cc0 C m COJ 00e

z ) L44 E

C X 40

0 aL4 - L w V

sita U 4' 6E L' Al 4- 4'

0. U L .')- w41 4'4' Al E. 50x LI Go -

V~~ a 0 au 0 L&. 'al >a W (A0a W- - 0 v+a isA 4) 4'0 0) 4' 41. M

+1 u a a V 00 :) aCL 'N- )n ma a 1- m,:' " * . '

U. W, I5 --

V i0 40 L 0 IC 4' USAC-a 0 0 C 6 a C L0 C 0' - 0EU) aa. af a.I 0l T, .

4ft fir L

-~ 0

Vii L r 4al a)C L

oCC

0 0Ju 41 -

I(n *

I0 - iv

mu: 0 IUmn U 4

O A - 0 C_w D~C Dvr

3- c v

0 --m

M En 0y M EvUa, L- -. Mm4 a)~ In4-0.C

0 V i4

41 4' W 4 4' U.

U Ci M r"4m 41 IDD

L. i .- mv L &

Z Ih.C I ivCL

L ' L EL W

00 0a 40w L IW(W

ou ma 41 UU4 ) I

6Lv Sol40 a L 0,1a 0 I-a L 41- PLD5< U Cc

4.

cccc

LU

0L.. I -j

C) <

E 2 LU)< <

LU .C

0L

+/

+ w: t

*

LLJ

==,

urnn

.2 0

Q0 CC, Cc

wQ

:!*

+0

o 1IIC, C,, | - I i I

+6 1

CLAJ

CC W LU

9L-

uj)~ z -- -LU -. D

LU L9 -- I.-

9- ccU)

0A 0 0

+ 9E T

ap . 4 - 4 . 4

C'-

r. - N - -

+ LE I

10

C 0

crU-

C. A Au' 7

S0

C u , '9 -.-9- 0 -

* , It if -

on in in n, C.)-

C\CJ

z

LUJ

CLC

o o

_ LUI

C/ 05 <

LU LU n*r LUL C.) L

<J zS 1.-LUI <

ccC

6C4-+

z -

c-,rzLUD ~C..D

= W L;U

Ea =

C):

>--

r Lucn) > 0 1~(n ccLU<

C.D C/)C) uJ C :> 0

C) LUJC-) LL-C0 z

4 ml -U 0U-CL C/ LUD/

0> >< 2C ULL C) LU

_ L <

C) <)I.- LUOctl Cl)

_ =LU > <

LUu

LU CD~ LU L

LU L)J LU =m) co w )

LU I; ~ LU L 0 C)Cl)'~ LU

0O 0 U < 0 <0L

4S2C

4. DATA BASE VJJAGz-MV;-

" Datz Base and Main Memcry Scner-.as

:wc cnaractee:.zatiOns cf any cata rase are Its screnm(ie. its o-09

ca' descrict..on aflc ;.ts vnvsjca. Wen-ato. e are more concerned wi.th

'-l ca; tase scaem~ here, s:.-e tne evt- de-:i :j.C)ved n ne jmvle-

tMentat~on exceeds that intenced -or tnis overview. :. the disc-uszion tha~tfc.ows, we use "imp lementa-..or" to. mear. a map= fror. a scnema to a part-c-..-ar :vpe of data structure anc its associated o~eratiors ir. mar memory.

141,

Logically, a prcject's data base cnnsists c' tne following seven f :es:

o Large data fileo Document fileo Paragraph file*o Personnel fileo Item fileo Template fileo lemplate element file

;, file's description is referred to as its schema. A schema for ai-.ven file is a collection of fields (i.e., atomic variables) describing,simultaneously, two kinds of objects associated with tnat file. The first isa tuole which is an instance (i.e., a particular set of field values) of theschema in -he file and therefore in the data base. The second object type isa noe which is an instance of the schema in main memory and therefore inneitner the file nor the data base.

Being described by the same schema, tuples and nodes are similar incontent. For a given schema, however, nodes contain all of the fields inthat schema while tuples do not. Thus, the set of tuple fields is a propeirsubset of the set of node fields. We refer to those fields belonging to bothtuples and nodes as "data base" fields and to those belonging just to nodesas "main memory" fields.

An example of a "main memory" field would be the variables of typepointer which are used to link togetner the nodes as they are read into mainmemory.

Each field in a schema is of a particular type or, in other words, itbelongs to a particular domzi7,. A field's domain dictates, among otherthings, wnat values (e.g., integers, strings, etc.) may be assigned to thatfield.

We summarize our terminology below:

o Field - atomic variable (i.e., repository for data)o 1uple - collection of fields in the data baseo Node - collection of fields in main memoryo File - collection of tupleso Schema - description of a data base fileo Domain - type or description of a field

All files are implemented as linked lists. The document file, forexample, has the structure:

dec I doc 2 -- doc n

where the project contains n documents.

*The paragraph file is organized as a tree structure. This is discussed inmore detail in Subsection 4.1.3.

142 10

Tne caa base is given structure as a whOle by defining links between

files. These :inks exis" a!, pointers froa :uples in cne file to tupies inanother. Bence, the l~nKs nave an implied "dlrection" associated with them.

In Subsections 4.1.1 through 4.1.7, we discuss each of the seven database files in terms of its schema and inter-file linKs.

4.1. Large Data File

The large cata file is used to store "general text" associated with

documents and their paragraphs. For a given document, general text consistsof the extended document t:tle and the general text for all of its paragraphs.

For a given paragraph within the document, general text includes ad-vice for that paragraph and the general text for all template elements as-signed to that paragraph.

For a given template element, general text includes advice, predefinedtext, suggested text, and finally the actual text (i.e., user data) written

for that element.

Note that since one document contains, in general, many paragraphs anda given paragraph contains many template elements, a tree structure would bethe most natural representation of the large data file. As we shall see,however, it is not necessary to define the required links explicitly, sincethe large cata file "innerits" a tree structure from the paragraph file.

The large data file contributes little to the overall data base struc-ture, since it contains no pointers to other files. It assumes the role offinal repository for textual Gata.

4.1.2 Document File

The document file is usec to store information about documents in-

cluding:

o Document titleo Due dateo Document managero Template defined for this documento First paragraph of document

o Next document in linked list

".i.3 Paragraph File

The paragraph file is used to store infcrmation about document para-

gzaphs. It is implemented in main memory bcth as a linked list an(- as a treeof paragraph nodes. Figures 3 and 4 contras: the two structures.

In Figure 3, the paragraph file is shown as a linked list. This im-plementation facilitates data base operations that are transparent to theuser, such as copying paragraph tuples to and from main memory.

143 1l

i I Iii I ! i

? a 7 a n e r

''I i ' -t K

?a-- raan Ncce

Figure 3. Paragraph File as Linked List

The tree of Figure L is the more meaningful implementation from theuser's viewpoint. To see why it is desirable to store paragraphs in a tree.suppose an author wants to renumber, within a docment, a particular para-grapn (e.g., 3.2). Then, assuming that some contextual structure existsbetweer that paragraph and its descendant paragraphs (e.g., 3.2.1, 3.2.1.1,

.£., etc.), the author will typically desire to maintain that structureusing th4 paragraph numbers. This necessitates renumbering the descendantsas well. The tree structure clearly expedites this renumbering process.

The required information can be generated at the time of implementa-tior. as follows: The parent link of any paragraph can be determined eitherimediately (c.g., the paragraph is the first child) or inauctively vIaparent-equivalency of sibling paragraphs. Thus, the tree of Figure L, can begenerated from the CHILD and SIBLING data base fields. Next, the linked listof Figure 3 can be obtained by a left-to-right pre-order traversal of thetree o Figure 4.

144

I Ii~

?AR~ ?K. S ? arC -

-- ; 'cce S-

Figure 4. Paragraph File as 'ree

4.1.4 Personnel File

The personnel file is used to store information about project person.-nel, including authors, managers, and memters of the administrative staff.Associated with each perscn in the personnel file are the following fields:

o Person's name (first, middle initial, ast)o Person's phone numbero Persons mail stationo Person's employee numbero Person's cost codeo Person's supervisoro Next person in the personnel file

13145

.5 Item Fie

The items file is used to store infrormation about template elements

assigned to the current paragraph. This file snould not be confused witth thetemplate element file (see Subsection 4.1.- which is used tc store in:orma-i:or, aDout template elements contained in the document template.

In general, there are many more item file records than tem:,ate ee-

men: file reco:ds, since a project has many documents, a given document hasmany paragraphs, and each paragraph points t a unique linked list of assign-ed template elements. The number of records in the template element file, onthe other hanc, exactly equals the number c: elements in the document tem-

plate. Thus, the numoer of records is incependent of the number of para-graphs in the document.

4.1.6 Template File

The template file is used to store information about templates asso-

ciated with the project. Since two or more documents may share the samu tem-Plate, one's first incl;nation is to assume that there are at least as manydocuments as templates in the data base. This is not necessarily true, how-

ever, since it is possible for a given template to describe no currentlyexisting documents.

-.1.7 Template Element File

The template element file iE used tc store information about templateelements contained in the current aocument :emplate. We reiterate the dis-tinctior. made in Subsection 4.1.5 between tnhs file and the item file.

:. Data Base Routines

Routines for manipulating data base objects (i.e., tuples and nodes)are categorized by the files on which they operate. The functions of theroutines vary little from file to file. For the most part, only the types ofnodes and tuples they operate on make them different.

In particular, five of the files (all but the large data and personnelfiles) have exactiy five routines that are specific versions of the generi.croutines.

4.3 Audit Trail

It was stated in Subsectirn 3.2 that certain data base modifications

are logged in an aud:t trail. There is an "audit trail facility" which con-s-sts of routines for storing and retrieving audit trail data.

When one of the data base routines of Subsection 4.2 is called, DOC-WRITER automatically calls a corresponding audit trail routine which writesto an audit file nforation about changes to the data base. The audit fileexists as a direct access dataset and contains the following information:

146 14

C -ser .L -den-t f-es ,ser wn.z made :i.e modification.cc - :den-;:i.es mcc;ifiec cccimer~tc Paragraph number -:den-.: 44es mnodifiec paragrap-c Timestanr - ine and~ cate Cf M.odificationo :teu number - dentifies modified template elemento 01c data - erriate element data as tney existed before

;oolfcatior.

Teaudit .Ie is per--od.-ca.Iy arctru-ved to secondary szrage in crders&/e ~spa(e.

Audittraprecords car, be accessed 4j sro±re. o xi~e

u;ser coul obai-i a!- modifications to zhe third :empla:e element of para-graon 3.L.1 of cocument "DOC-00V" tnat occurred between t-e dates 1-10-32 and

147

ATTACHMEW 8

AUTOMATED ENGINEERING DOCUMENT PREPARATION SYSTEM (AEDPS) ANDMICOM INTEGRATED DOCUMENTATION AND STANDARDIZATION SYSTEM (MIDAS)

149

ATTACiENT 8

What was the system originally designed to do? Provide MilitarySpecification Exception documents to be used with an accepted military specifi-cation for procurements of nonstandard parts. Intended to provide visibilityto existing documentation and prepare time-and-cost-effective documentation ifnone already exists.

2. What information is presently stored? (a) Standard text paragraph data andDOD-STD-35 codes used to prepare an MSE for any 1 of 124 families of parts;(b) Codes and values used in the preparation of all existing MSEs; (c) Userdata; (d) Sources of supply: Mfgr Part Number, FSCM, Name; (e) ManagementInformation Data; (f) Document designation, date, references; (g) Tracking andcontrol data.

3. Who are the system users? Every major/subcontractor that the U.S. ArmyMissile Command (MICOM) is involved with, every project/commodity manager atRedstone Arsenal, and the Standardization Activity of MICOM.

4. What are the sources for data included in the data base? (a) User generatedrequirements; (b) DODISS; (c) CDRL 1423 (on all MICOM contracts); (d) Approveddeliver extraction data (i.e., ECP, Drawings, Specifications)

5. What hardware is used for the system? Honeywell Level 6 computer with(a) 2,048,000 bytes central memory; (b) 736 MB on-line disk storage; (c) 300BAUD remote input capability; (c) 900 LPM line printer; (d) 55 cps letterquality printer; (d) DEST optical character reader; (e) 9 track 1600 bpi magne-tic tape drive (used exclusively for backups); (f) GCOS 400 operating system(software).

6. W! at types of programs/languages are used? COBOL with some ASSEMBLERsubroutines.

7. Internal or external support? A mix of both in-house as well as contractor

effort.

8. Output Products? (Explained in accompanying vugraphs.)

a. Reports d. STARS g. DNA j. Item Reductionb. Specifications e. WASP h. Review/Prepare k. Nomenclaturec. Tracking Data f. CID i. GIDEP

9. Single or multi-user? Multi-user.

10. What procedures are used to maintain the data base? (a) MSE processingautomatically updates much of the data. (b) Revisions or change notices toDOD-STD-35 dash part books.

11. Is there remote access to the system? Yes.What communications links are used? Asynchronous RS232C

12. Planned changes/enhancements? Page scanning capability - faster band rate -

currently planned to make the system the cornerstone of MICOM's Parts Controland Standardization Program.

13. Is system documentation available? Yes.

14. Is a data base management system used? No. However, AEDPS is designed toprovide key linkages between data files such that all data relevant to aspecific data item can be retrieved for document preparation, inquiry, andsystem tracking and control. 151

SYNOPSIS

The AEDPS prepares exception documentation that, together with an existingmilitary specification, can be used for procurement purposes. AEDPS takesadvantage of the fact that most special or unique application items call forrelatively minor exceptions to an existing military specification.

Standard paragraphs have been written that cover many exceptions and that permitfills, write-ins or the completion of sentences. These paragraphs are stored ina computer along with identifying codes. By inputting the selected codes andvalues required, the user can have the computer print an exception document.The exception document along with its base document can be used for procurementof the unique part.

The characteristics used to generate AEDPS documents are stored in computermemory. Inherent in the AEDPS program is the ability to search thru allspecifications residing in memory and compare any number of selectedcharacteristics. Thus, all existing specifications are made visible andduplications are prevented.

The system includes extensive management information reports and a user inquirycapability for status of a document in-process.

Input requests for AEDPS processing can be from a remote location and canconsist of full input requirements or message type input requesting AEDPSaction.

All documents are stored in computer memory and can be easily revised asrequired. The AEDPS documents can contain multiple parts (tabulated documents).

The AEDPS consists of 12 major data files requiring approximately 50 MB ofon-line storage.

The current AEDPS document file contains 4,649 documents.

The MIDAS system was devised to capture and manipulate a great amount of data ina short time. MICOM has numerous data requirements in all contracts, and theMIDAS system captures that data and automatically manipulates it for greaterawareness and control in the Standardization, Parts Control, and EngineeringDocumentation management systems. The key to the system is that it includes 18major data files and 30 cross reference files. The system feeds off AEDPS butis separate and apart in use and content. The system lends itself to activemanagement at the local level for the parts control arena as well as providingremote access for system users.

LjjJ

C/- C/)

~CO

I-at z

9- 0

0 z

z z

CLO

0 <

o w

oo z

t.',

CLCO uj10

ul LL-

.Ccw

< <2-Ci

wi

< *0 Z 1C -

Qzi -

-~~~ .zinj >~ C4 -0 4.-

C)~z~ z-4-

HO C)m ~> > m< - m Z <

_ , _Z

:0c m-1 Z >

0

.- A :S YSTEM UTILIZING 'A -COMPUTER TO PRODUCEENGMEERING DOCUMENTS'

*USER INSTRUCTIONS PROVIDED IN DOD-STD--35

* PROf?,VJDES 'A MEANS ,OF CONTROLLING 'NONSTAND,-PART, DOCUMENTATION

* JINT ROD U CES STANDARDIZATI ON IN DESIGN STAGE

in

-0 m

-i =

;YSrEi4 DESIGN

CAPAB ILITIES

V13 of E:r--r '-tect ion and 2c"rrec -4on (E!J]AC) Cen cra -ocess ing Memnory

* ~2~ ~Rt-mce -_vncnrcnous C-.ni-,municaticns

-'0, lnu 20J 1pm L~nie r'nters

lz oie Let,. r Quality Printer

)ff ~ rito Systen (OlAS'

ll n~ve- al Nct- Svst ,ns (UD^S) 300 3aud Modemis

9 Trick, :6sco- ai, Maanetic Taue

158

-lox

uj 4

Li UJ Zi 0-

- .U L L r-Jr

0< W~

a- Q(fl

0zr z_______ 4 5 0- ac

o 0 z aowoX0

Ix' w 11. 0 u -na-i

-j - a m A

1L& CLo~ -J ' 4

U) w~ 1 . 0N O (04C/) Z)0z L

0I) 0 *0IN-( ~ C.) U j<C Z.

ga0 (M 0j 0(3 <

d% W, WOkm

(Yd CL4- - 4 49(4

Cfl~~( .0 0' 0(W~(~ *L 0 ca- Vi W C> (n 4 0 1. 10N r z: -

oM F or)~a2 Cr* CL 0i P- 0*('

-- .- N - o Fn 0fZ0Lo DX n

(D 0 0 Z- C ,-g- i. -z. 0r - Li)0 .N 44 DCV)) 0 (n0

LLL cr g (

4 0 4 iZ

MICOM INTEGRATED DOCUMENTATION S STANDARDIZATION

SYSTEM (MIDAS)

!D NCN-STANDARd PARTS (STARS)0 WEAPONS! SYSTEM APPLICABLE SPECIFICATIONS PROGRAM

(IASP)

* MISS;LE SPEC.FICATIONS (MS)

t COMMON ITEM DRAWINGS (CID)

1 CO'"E.RNMENT! INDUSTRY DATA EXCHANGE PROGRAM (GIDEP')

Q AUTOM4ATED ITEM REDUCTION STUDY (AIRS)

0 2C0t CUSPENSE FILE (SUSPMF)

& CrAW!NG CONTROL FILE (DCFLE)

* ENGiNEERING DOCUMENT DATA (EDO)

* DATA ITEMS (DI)

* DOCUMENT SUMMARY LIST (DS)

• DOCUMENT NUMBER ASSIGNMENT (DNA)

0 DATA ITEM COST (DICOST)

* OFFICIAL NOMENCLATURE RECORDING & REPORTING SYSTEMI(NOMEN)

• STANDARDIZATION DOCUMENT PREPARING ACTIVITY PROJECT'RECORDING a REPORTING SYSTEM (PREPARE)

S.0 STANDARDIZATION DOCUMENT REVIEW PROJECT RECO[ib ._ .REPORTING_ SYSTEM (REVIEW) --. ..

* S MIDAS INQUIRY

* AUTOMATED ENGINEERING DOCUMENTATION PREPARATIONSYSTEM (AEDPS)

. .. . . .. . -" . ... . : i ... ." --( i1

CHANGES/ENHANCEMENTS

MICOM INTEGRATED DOCUMENTATION AND STANDARDIZATION (MIDAS) SYSTEM

7he MIfDAS system is currently made up of 14 subsystems, each Containing d Ispeci ic type of data. These systems were designed to provide better contro7Ind faster access to inforrnacon needed in the standardization proces%.

icn system Proviaes reports in various sequences, either total file or seiec-eQ'L, a. Lnquiries use menus for inquiry type selection ana disolayea prompts Thr;ser entry of required data. An example of this will be shown later.

A recent addition to the MIDAS system is multi-file inquiry capacility thatprovides information from various MIDAS files by document number, vendor partnumber or NSN. More about this capability later.

"=mDined, the MIDAS systems include 18 major data files and 30 cross referencefiles requiring aporoximately 200 megabytes of on-line disk s:orage. All areprocessed on a Honeywell Level 6 Model 57 computer and all have remote access,multi-,ser capability.

162

MIDASINQUIRY

DOC NUMBER -. VENDOR NSNPART'NUMBER

AIRS *AIRS *AIRS *DNA *PNIF GIDEP

WASP STA RCID GIDEP

DIMIx USER -OPTION.

1 3

7)

<Crn(n

ZLCL

00

zwWw

wl ix

cr0

Jww

tom-t.

CD)

I-0

w>

w0&

C,

IJjI w

a. d Ia->-J

CL CO'~ -j

ix w zz0 cD 0

00

-Zw C-D

00 >t-xLto 0

L9! -

w

0

Ix

~ LuCL IL

cw >

z -(0 LU - jLU 0- L

m, Cf 0

CL 0LiU

> <w c N

a: >

0 >,La 0

cc

z (n

0

00

L, a-,u z < LLii Lii LIi

-j 0< LL. io 0 ci)

a- 0,

z

U)0

LLI

40

c U)

Cz C/~~a Li- Q

0

CDDzzw LI

z a: <

-0~ LLC) a:u Z

cr 2r z0 cr LiL.

z > (1)0iZ > 0 Li

0) Z

0I LL. x

o ~ <,~z x HZ

-~OLT

Inn

0L

a...0l

hi

<wLL u

C,))

CL

ILIT

00

Ir >;0-in

LOJ

ww

w IL ct

z a -aw cc >Iz, 0 I

LL*00w w0

i Z

4L

zw

4n <

ww

U, w

00crw

Qa

ELTI

0 Un(fl:

a.a-w aJ

CD 0 >

z cr CT)

00

cr << c-

z D

D - 0) C.

o Li j

UL

Uw'Iii

ww4-

0ILU

a.0* Lm

SLT

-Nn

ChLaJ

~ -a- -,

z LCD Gz 'I,C.,, C0

(I-

z<-J

zz

0

0ra.

9LI

cc,.0-

0~0

o00

LUL

w LLw00

a.

L0

Qz

0

ATTrACHM I-NT 9

r:F.(HN ICAL t)ATA/CONF [CURATLON MANAGEMENT SYSTEM (TDICMS)

177

ATTACHDMENT 9

Note: Statements are keyed to the questionnaire.

Tchnical Data/Configuration Management System (TD/CMS)

. tthe system was designed to maintain an integrated digital data base oftochnical data in support of engineering and procurement actions and provideidentification, control, and status accounting functions for engineeringdocumentat ion.

2. The information stored in the TD/CMS includes data elements extracted from the

engineiering documentation. Examples of TD/CMS data include documentidentification data, revisions, nomenclature, manufacturers' part numbers,

Federal Supply Code for Manufacturers (FSCM), document size, numerous relatedaates, and number of sheets.

1. S;ystem users include design and production engineers, standardization and

procurement offices, configuration management personnel, and data repositorystaff.

:n'ngineering source documentq which provide input to the TD/CMS data baseinc1ido :ogi neering drawings and associated lists: change actions includingEngineering Change Proposals (ECPs), waivers, deviations, and Notices ofRevisions: ind Military and Industry Specifications and Standards.

ThE, system is presently installed on a Control Data Corporation (CDC) Cvber835 computer at Fort Belvoir. It will be transferred to an IBM 4341 computer.it Fo rt- elvy'e r during this fiscal year.

6. The TD/CMS programs art, written in the ANSI Standard COBOL language.

7. VExtorial, ('.e. Contractor) support is used to maintain the data base.

8. Ouitput products include over 30 user requested engineering technical dataroporLs and over 30 other reports used for quality control of data and thesysttem. (Sot attached).

The TD/CMS is a single-user or batch processing system.

10. AII new and revised engineering source documents, including change actions,which pertain to end items and subassemblies for which Belvoir Research,Developmenr, and Engineering Center is responsible are routinely entered intothe TD/CMS to maintain the currency of the data base. Data elements areextracted from the document,;, keypunched, or keyed via terminal, andtransmitted for batch edit/update.

11. 'h, ;tr-ictr has remote access to input and retrieve data via a Data 100'emne lob Entry (RAE) device. Remote access is also available for data input

-ird system suipport via telephone line communication links from terminals witholo'lm. 'io ha:tch pro,-,,es ng steps to updnto the data base and extract outputfor reports are done twice a week.

12. The system is continuously being expanded and enhanced to add new capabilities;s thev ar- ident ifod by the users.

13. Complete documentation is available as follows:Comptiter Operation Manual - AT)SM-18-L99-JD-CDC-OMSystem/Subsystem Manual - ADSM-18-L99-JD-CDC-SSProgram Maintenance Manual - ADSM-18-L99-JD-CDC-MM

14. [l1- POT'CMS does not use i Data 13ise Mana vfmealt Systtem (DBMS).

SYNOPSIS OF

The Technical Data/Configuration

Management System (TD/CMS)

U. S. Army Belvoir Research, Development,

and Engineering CenterFort Belvoir, Virginia

System Manager POC - Richard H. Goehner System/User POC - Norman E. Lekang

(703) 664-5789 (703) 664-2071

AV 354-5789 AV 354-2071

The TD/CMS maintains an integrated digital data base of technical data in

support of engineering and procurement actions and provides identification,

control, and status accounting functions for engineering documentation.

Source documents which comprise the Technical Data Package (TDP) and provide

input to the TD/CMS include: engineering drawings, associated lists including

part,; lists, and Military and Industry Specifications and Standards.

Engineering Change documents are also entered into the TD/CMS. These

include: Engineering Change Proposals (ECPs), Waivers, Deviations,

Specification Change Notices, and Notices of Revision.

The TD/CMS establishes, maintains, and reports baselines for end items and

subassnnblies. These reports are used to confirm that a TDP is complete and

adequate for procurement. The system also provides reports for selected

documents including Specifications, Standards, Control Drawings, and Change

Actions.

-80

NARRATIVE - TD/CMS BRIEFING

Sheraton National Hotel

Arlington, Virginia

May 13, 1986

Slide Key Points

I am hert! to present you with information concerning the Belvoir

Research, Development, and Engineering Center Technical

Data/Configuration Management System. The System Point of Contact

(POC) is Norman Lekang who also acts as the User POC. He has been

involved with the system since its initial design. The System

Manager POC is Richard Goehner, Chief of the Configuration and

Engineering Data Management Division at Belvoir.

Arpas we will cover include:

o What the system was designed to do,

o How the svstem relates to Standards and Specifications, and

o Why TD/CMS is relevant to all DOD activities.

2 TD/C:MS was developed in the 1960's in response to problems which

resulted from data accumulation, growth in the rate of generated

information, changes in engineering equipment, and advanced

t.':Inoligy which included the initial routine use of computers to

generate, store, and print data.

181

3. These factors resulted in the Configuration Management challenge -

how can we identify the configuration of equipment, maintain control

of changes, and provide accurate, current status accounting

in format ion?

I'h,. answer was TD/CMS. TD/CMS was designed to maintain an integrated

digital data base of technical data in support of engineering and

procurement actions and provide identification, control, and status

accounting functions for engineering documentation. The design was

h:is'd on current DOD engineering specifications and standards plus

input from Belvoir (then MERADCOM) engineers concerning their

operational requirements. The system operates on a large mainframe

computer and incorporates indexed sequential files.

5. Perhaps a definition is in order . . (read slide).

6. TD/CMS input is extracted from the actual source documents which

define the hardware items. For example, this generator requires

drawings, associated parts lists, Federal, Military, and Industry

Standards and Specifications, DODISS information, engineering

changes to correct deficiencies and incorporate enhancements, and

FSCM data.

7. The scope of the TD/CMS related documentation includes more than 40

different drawing types, such as you see here.

182

8. A single Level 3 drawing provides extensive data including:

o the data elements which identify the drawing (the identification

number, FSCM, drawing size, nomenclature, number of sheets, date,

revision level),

o Related Specifications and Standards which appear in the notes or

the List of Material, and

o Parts with their IDs, quantities, and item or find number.

9. Data is also extracted from Standards, including Federal, Military,

and Industry standards you see here.

10. All Federal, Military, and Industry Specifications which apply to

TD/CMS end items, are entered into the TD/CNS files. Data extracted

from the End Item Specifications includes the identification of

applicable documents as indicated in Section 2.

11. Tn addition, information is extracted from Change documents including

Specification Change Notices, ECPs, Waivers, Deviations, and NORs.

12. Standards and Specifications are a key part of the TD/CMS and many

data elements are captured from these documents. The currency of the

TD/CMS records is maintained from information derived from the DOD

Index of Specifications and Standards and the National Standards

Association Bulletin. The TD/CMS reports show the document status

183

(active, superceded, cancelled, replaced) and provide information

concerning changes, notices, amendments, and supplements.

13. All of these documents contribute to the Technical Data package which

defines the required design configuration and assures adequacy of

item performance.

14. The most important aspect of the TD/CMS is its capability to function

as a gatekeeper who ensures that the documentation is complete and

that thp changes are identified. This allows TD/CMS to maintain the

baseline technical documentation, track changes, generate status

ruports, and facilitate update of the baseline for new procurement.

15. In 'D/CMS . (read slide).

. For example, TD/CMS allows the user to determine the impact of a

hardware change from a rivet to a bolt in all applicable end items.

TlTe same capability exists for tracking changes to both end item and

reference specifications or standards.

17. The TD/CMS manages the data entries by cross-referencing input from

source documents to all applicable end items and subassemblies.

18. Output products include over 30 user requested reports and over 30

other reports used for quality control of data and the system.

184

rD/CMS reports are available which specifically address Standards and

Specifications. They also appear on reports for end items or

subassemblies. For example, specifications and standards are related

to a specific TDP and correlated to individual drawings on the TDPL

report.

19. In summary, TD/CMS supports

20. 'rD/CMS puts you, the user, in control!

'D/CMS has been used by Belvoir Research, Development, and

Engineering Center for nearly 20 years and has proven to be a

cost-effective contributor to the management of engineering

documentation. The data base content has met the test of time and

usefulness.

At present, reports are provided on a scheduled basis. Ad hoc

queries are provided as requested. Enhancements are made

continuously to incorporate up-to-date capabilities. We are also

monitoring the efforts underway in the DOD DSREDS (Digital Storage

and Retrieval Engineering Data System)/EDCARS (Engineering Data

Computer Aided Retrieval System) program and the Army Material

Command rommodity Standard System (CCSS). Additional improvements

tinder investigation include a direct, online interactive capability.

185

z0

OOf.

i

zm.wj

cl-

8lef

m m - - th

681

wU0z

\OI-

a low

C 0"0cc

au

061

. o

0I-

zlow0 , U0

LU. ...... ...I--

W O _

i.

CLz0 2U LOU

.z Zi~m Z -'(I, & c o Im~0 Gomm~rZ <W C.) <

0 UJ LL Lzoc 0"W oo

Z6T

LAZ %A

>0 a

muza

K LLZ 0 1

0o

I- Z

U In

Z~z

0z 0

0I

E61

-j zcc 0

(I2 ( Jn(n 1z U) ZL F- Z

LI0 0 JJ -'00. u uZU

z mz rLU 0 - uu - DUF:5(Da: U - UZ H) Z g j z C

an u 2 o z 0oj C)utjcr0 : rZL C>0 ~ Xw& - Z0LU 0-(n c z 0 xf) OL U

0 W ~ 0 C / Q ~ j o.<

Ico<0 0 < fl

ccc0 F- (

~cc,

T, 71-

Rz 11- 1

t 0 J.3z

9I

* I

\. , .:",I

iii :;,;1ti -*~~ i llq I ii I U"i

fil. 1 !

// . !,4,' '1, 1, [*

4'4

I * jl

,A/ /9 !

,196il0 ,7 •! i!

il V11 11446 STANDARDS

IL 111 1344Is sit iMh

MILITARY STANDARD- ...

TIST METHODS

ELSCTUICA1 CONNECTORS

SWl. 1. P%- kill %1 1 Ill %

L.."a vocabulary forK. 469"',information processing

AI

UPECIJCATI01 ChANGE NOTICE(Set guMw-69 6 A IfSNCIcTIOS) oST PREPARtD

~. I6UA? un ACCS . a. CfOE I01811. 4. VIEC. NO

STRBE-JOE. Delvoir RDE Center j ooiuo 81349 . ILR-4364FFt. Delvoir, VA 22060-5606 1.i CM Ws I4.

______________0 81349 001~F

YVA'HML2r1PUN~4 6. " AL ot W ' ". 9. co"?IK1 mSe. 101ACTAL ACTIE

TA- 13215E9750 86CE0212 DAAKO-85-C-5237IS. CMOllSllQ asEN 0(S KN6OE I . 40TECTIIVIY

Roller, Rubberized

m11S NOTICE INTO"s S[CIPIIgTS wAr At SPcCIFIcaio? ICNNIPICO IV 11014 10,02 4401 REVISION LITIflE

SM LOC NAS AS CWof SA O, ME PAGES O411G5 MI1S SCN KING MS EoO FUOIN12MU -II01 AMD

CamoIvMG MAE SAnI A S 5t515 SMl ". THE PAGFS OF M A PGE M ini5 AM SATE LISTIO S(LOW 10 ME

SANWAV Ofr CHANGED PAGES. ""ItiO 011 NON.LISIE PAGIES Or M9 ORIGINAL. ISI OF ME RIEVISION

S 15.1 INI LOCN 4. CONS ITUTt MI CUSS rT VERSION Of ThIS SPECIFICATION.

Iq. 14. --. !1 I,.

SCm N O. PAGES C.ARGEO (IIUCATE OCLETIONS) 5 A OATE

001f: Page 4 04 Feb86

Paragraph 3.5 Fabrication.

Line 9, Delete: "steam"

Reason% Either steam heat or dry heat - pressure,-

autoclave is acceptable.

11. S ¢IC CONC I+ C" I,, PATE

C, Bridge Division, BR.6C, Ft. Belvoir, VA 22060-5606

D D , =r 1 6 9 6 "J A " " i g # A W gr . * d g o p 1 6 . p p" "@ . *A * ' ' " ' * 't e .o w ed p o s t .

197

861

z -w%A~~E LU 9L 0

Z L- CcC u>.

0 0 0 0

z~~ Lu A

u ~ .2 - ,

L< Zz jI. j2 ZLLU umL

<z Z

LAJJ OZEML>0s **sse

0

H w

0

C.)D(U O< L .

CL) <U n C/

C/ -C/) C)

WZCD ccHwauinD<crj L

00000a ..

ooz

U'UA. ___

U7''Ui

UFA

(fl Nz

ww

.IL V c

FlwZM ZCLWWWOUo U) IX

Co pz

z

0 B

Ale

("Iz

12

IAz0

z L

tA 0 9

m - -

0

LO. -i t- 0A

< 2 02tA ?' - -

IA -J

IL wF 0.

< LI 2JLL

LA wi tA Lu 0=j tA F- 00 0 0

soz

0

zU)z z 2l

LU z LU z -0 OC

C, 0l ur

z a '* 0. Ca.

cc cc

,)Oz

IL

ATTACHMENT 10

THE ADEQUACY AND ASSIGNMENT (AAA) INDEX

207

ATTACH149NT 10

NIDF (

TOPICS FOR DISCUSSION

1. The systpm was designed to store the identity and current status for all

of our responsible Technical Data Packages and related items of supply and

standardization i.e., engineering drawing number, NSNs, standards, and hand-

hook. Our standardization document responsibility encompasses both MCA and

custodial documents as well as our own prepared documents.

2. The data stored for ea-h document are: Federal Supply Class, item

material manaqer, internal document managers (preparing and technical per-

sonnel), age, ADCoP designator, engineering support requirements, valid

or invalid for procurement, referenced drawings/NSNs, Active Project assigned

for 2pdatinq, and document resporioibil]ty i.e., preparer, MCA, or custodian.

3. Our system has no users that can gain access to the computer. The system

is updated/edited via key-punch cards. However, the procurement centers,

standardization mana'ers, specification writers, maintenance and technical

personnel receive monthly reports from the system that pertain specifically

to them.

4. We receive data for inclusioninour system from this Center, Item Material

Managers, Procurement Centers, and other standardization activities.

5. The hardware used for our system is a UNIVAC 1106 computer.

6. The system's programs are written in COBOL.

7. The system is maintained internally (See No. 3).

8. The following monthly reports are obtained from the system: management

run (all inclusive printout), procurement center runs, ALPHA/FSC listings,

cross reference (document to NSNs/DRWGSA drawing list, ADCoP designation,

CID, Workload by type document, and summary reports totalling specific

documents.

it. See No. 3.

10. See No. 3,

11. There is no remote access to the system.

12. Our current computer system which is called a sequential i. le syste.n is

being revamped and a complete on-line data base management system (DBMS) should

be in operation sometime in the latter part of 1987. The DBMS will enable us

to access the system via remote terminals.

13. Our current systems documentation are available upon request.

14. We do not have a data base management system.

209

ASSOCIATES 32 NCM AFL N TOA~fj~ Sa3NAO Y NI--D 3/3

NNA? Ot N

F----- m

3a.

!CROCOPY RESOLUTION TEST CHARTNATIONAL BUREAU OF STANDARDS-1963-A

NRDEC

SYNOPSIS OF BRIEFING

NATICK's STANDARDIZATION AND SPECIFICATION COMPUTER SYSTEM IS CALLED THE

ADEQUACY AND ASSIGNMENT (A&A) INDEX. THE A&A INDEX CONTAINS THE IDENTITY AND

STATUS (PROCUREMENT AND STANDARDIZATION) OF ALL NATICK's TDP ASSIGNED RESPON-

SIBILITY AS PREPARING, MCA, OR CUSTODIAN ACTIVITY AND INCLUDES RELATED ITEMS

OF SUPPLY AND STANDARDIZATION. THREE VERSIONS OF THE A&A ARE PRODUCED TO

MEET USER's NEEDS: (1) INTERNAL MANAGEMENT RUN THAT CONTAINS ALL THE DATA

IN THE BANK, AS LISTED IN ATTACHED CHART, FOR NATICK's STANDARDIZATION DOCU-

MENTS, (2) CENTER RUNS WHICH CONTAIN TDP LISTINGS TAILORED TO EACH RESPONSIBLE

PROCUREMENT ACTIVITY, AND (3) INTERNAL REPORTS CONTAINING DATA TAILORED TO

VARIOUS ELEMENTS OF RESPONSIBILITY AT NATICK. THE PRIMARY PURPOSE OF THE A&A

IS TO INDICATE TO EACH PROCUREMENT ACTIVITY THEIR TDPs THAT ARE ADEQUATE/VALID

FOR IMMEDIATE PROCUREMENT. THE SECONDARY PURPOSE IS TO PROVIDE VISIBILITY OF

STANDARDIZATION STATUS OF THE DOCUMENTS. THE COMPUTER PROGRAMS ARE WRITTEN IN

COBOL AND THE A&A INDEX IS UPDATED/EDITED MONTHLY VIA AN INTERVAL KEY-PUNCH

OPERATION.

WE RECEIVE DATA FOR INPUT TO THE A&A INDEX FROM THIS CENTER, ITE4 MANAGERS,

AND OTHER STANDARDIZATION ACTIVITIES. DATA THAT iS APPLIED TO EACH LISTED

DOCUMENT IS EXPLAINED IN THE ATTACHED A&A INDEX LEGEND.

THE A&A INDEX SERVES AS A MULTI-PURPOSE MANAGEMENT TOOL i.e., INVENTORY

ACCESS, READY IDENTIFICATION, CURRENT STATUS, AND PROCUREMENT SUPPORT.

PROCUREMENT CENTERS/ACTIVITIES ARE FURNISHED SEPARATE, UPDATED MONTHLY REPORTS

ON THE PROCUREMENT STATUS OF ALL THEIR RESPONSIBLE TDPs FOR WHICH NATICK IS

THE PREPARING ACTIVITY. THE A&A INDEX GENERATES MONTHLY/QUARTERLY REPORTS FOR

BOTH INTERNAL AND EXTERNAL DISTRIBUTION IN HARD COPY OR MICROFILM. SAMPLE

PAGES OF REPORTS ARE AVAILABLE FOR YOUR REVIEW.

THE ATTACHED CHARTS LIST THE TITLES OF REPORTS THAT ARE PRODUCED ON A

MONTHLY AND QUARTERLY BASIS. A QUICK RUN DOWN ON THE PURPOSE OF EACH REPORT:

VIEWGRAPH I - MONTHLY REPORTS VIEWGRAPH 2 - QUARTERLY REPORTS

210

THE A&A INDEX IS CURRENTLY BEING REVAMPED AND A COMPLETE ON-LINE DBMS IS

SCHEDULED TO BE IN OPERATION BY THE LATTER PART OF 1987.

ALSO, NATICK STORES THE FULL CONTEXT OF EACH CURRENT STANDARDIZATION DOCU-

MENT THAT IT PREPARES ON FLOPPY DISCS FOR FAST RETRIEVAL FOR UPDATING OR REPRO

DUCTION. NATICK's CURRENT AND HISTORICAL STANDARDIZATION DOCUMENTS ARE ALSO

STORED ON 16MM FILM REELS. FURTHER, NATICK HAS A SEPARATE COMPUTER PROGRAM

THAT MONITORS THE PROGRESS OF ACTIVE STANDARDIZATION PROJECTS.

3 ATTACHMENTS

LEGEND OF A&A INDEXVIEWGRAPH CHART OF DATA BASEVIEWGRAPH CHARTS OF REPORTS

211

CLZ

00R @3.0

U @3 r o..0 z 4)Ch 0 t . .- L.

n 4) .- >,ki 0 . .6-I UI

6 0

C V3 L.i~) ~to~U0.. 0 Os1

to c .0 >@4

J* ;~

V) 0 0 u 6c 0 V @

. X 0 ~ 4j~ U).U&.U .

4J . c o4toa oz 0VA' -. C Wu e z

V -4- 14 -0.w-'- .0* .04

4) adJ z-Is -.

'tic .4 L

in FA F. cw 6 L.0 4

'C : , .. c UU U L.4.3. z~. -V H .C

. ~ t I-

w , 0 m600~~0 -C1. >

OM 0.v .@3' f3 - 0 00m U1 S. (

c - 0

4 ~4j00 0 C-.

gn v .. t0 .0

ac 'o a 0. L WI-:). 8to .4 M z. lit SD

8) 1-J 0. in A-94A

M Z

41'L 00 0

to cr .> ga V0

C~ CF).3 to

5 -U 00 .3

04 c @

4) IV' I

01,-4 .ILI u ..>, C 0 in

611

0 C 06U

0

0 0Ad 6

4.)

a. > -

0 -00

.~u W)) IA

a 061 0

*jC a -. 4go a Z

uI -.

%W c 4L... 0 u 1c .4 C04. 41 V a0C.4 .10S.) 01 o 4.) 41 c44)w- C6 tA

V, 1.)6 00 Al.* 1 L.L o v -I V a .S U*.4 v V 0 trZVA 4 V .C -A

UU '0 C 0. 41 .i.FA 0 ) a -W &.a 1 ..q 0 0 -.

-K 1 0- V1 A'4 6 cS 0

.a6 'a.1'4U) 6. 41 006

_~~~~0 u V1 -a 06-' a o a- j &d cc. al to .. 4c -a E1 c

614 v 1 0 W 0 oS%. 0146 b60 0 0. 41 I J6

I*-d. ..4 ca * E4' 6

L. - $2 0w IN a. Q - cU,. 41 4) 33 % 5vI .0 S.g

41%4a ad V U a4l41 6V w a * 0 c a0 6...j -aa.a a ' 0 0 6' c 0a. 40 4E j &o o~a 00 6)' c 4a 4

V) ~ h a a u W%a- IAA aL a Id~

.0~~ 610 61 .0C *~1 .0 Z. Id W'-'4. 8 -. 4 a-6 - a~~ - W)a' 1 61m V) a o 6 Z -C C to~ a J t

~ sa 06 * 1c -. -4 c-CL 1 4j- a 4D. o..woo o~i. I- . 0 - 0. U

"o 4) - -Z M~ R s M . ...u'A '..-C ... Ic -U 4 a-*-*. f

0 a~~~ 4 , 04).4

4, 04-2 0 1 0 0. 0

44 .4 4-'0U3 tv L, 0

41

0l 4,>-44

94 94

*-4 41IX , 4

z4 M9C 0 0a.40 0, *0 Q

,. V2 -0 4.,0:b

tj, a~ 4,. %U) I ." U)

- u C) -4e4

10 bOW 0 o

a4 0 0

00-.4 0 0 .1 r -

..4 4 4 0 ad

~~. *U) 4

.-4 4,1 00 00

4, a~ . 4 ,j cc0

o 0j414 0 4,j

I- W C-

0.occ-oL b01

. 1 0 U.h h O -- *0hO

41 C -4 -4 .0 1

CA. L.E a Xw b

4Ai4 *

-~ 9TZ

UAUA

41~ in

o 02c E

cU4 0

V IV v to 4

01 4060 ..

CO 441Q

v1 (1 .-

0- 0 0.0 fo.- C ) - 00 64j0 4..

0 e-0 C

*~4 41 iU

IV a 'CO

) C6 0 *&D W4 L. C 0 W-

3

VCU u a F ac..EU 0- ) 4 2 0

41 60 Ck. 41 w u 0 AZa c~,- 0- B o1 g . 6c 1-4 C

. 0 .- -N W oL ca C u V0 ).4 .C - " *..4 C -w4 CO 0. - > 0

-~ ~~~ 4a 0)4 0b 1 ~ a0 ~ ~ a a.1 .v V

v1.0 01 41 -' EUU*o 4 mw a 0 u- u L2 m % 0V.4 a - * .6 to

caa1 41~ 4111414,- MI 4 0c9 .auC 4 U a W -- 4Q UOV~ a a to c oU*01 0 a. c v .*a V 0 V a *a*0 V v V a V

>- . 0..q

0 *6 ' C-1)4411.

I. a 0 0 0CC aa a m O

0 4c * ~

C 4) J )

0.0 0 UL

to 0~* to)C

d )< A - U)o

414 1. 0 .- 1 w 4

01 -4 aw 60 cC)~~4 to)C 0 0z~- b~ ~

U))C .1:a4

V) tnIV .. Iv 0 -4)C .. 0oww.

4GA 0, -- 1 V. toC -- ,-

L. 4) 0 .44 -4 men E-4,

o Lf)I E ) to en0"~~o b a

a) - , V)U

>) ) a 44 *j .0. to 4 ~ CC)C 41 e - A m 0 0U

0 > 0 4)4j.". 4j W0 0. 0 bo 0 U) . .4 *

C) u :C)) 4)~0 U -. - JAJ 0 %* 4 0 C 'C *l 0&.

cc C .. c ~ O :41 1w 0&. .00. U U 0 xL

0K 0 0 cC4'U

0 Ld *0 U-C0 >~C &. to C

£4.3L to 0 . * ~ 6.00 4-' c a~ Q bC41

*aJ V . > 0 00 L,0 0)>>

&. c . a.4 .4 ~ f"U c .q Q "L.* I: 0. Q.. CC 'M

0W C) AU0 toB. ) to go m0 ~ c. Ck .414 4 v 0 C) 0 0-4 41

C co L. Nl , w 0) 061

CJ L. 4. =~i - 0 4,, .'n cc- o =*A( j v) IU *..4 o m A. 4-j.. V~,4 ) .4 6

0) - 0 0J 9D -00C f to..I c- t )64L. 0o 'a 00 41 L. -I.. a m go m)1 U40

IVN IV0a * 0 mQ w~ Q. C 0.%4

'a to 0~ 0 (n t cc m J (0 o0 9t.C)..

.- C6C &00.0-4. c0) a C) I.C 0. C)CVVI.)J 0 toL~ C 0 ) * 4~0 )

Q 113M N 0

P-4 *. 1J V '

0 SIZ

> .

4) v m 04~u A

Ij 4 0.

0 0 0'in V.in

W 14.j0. 1 . .V An

0a - k

4) 40

'4. 0i. 04 0 U 44

a %- 0Ui 0,

Inn .. %4414 0 d)to0 4) W. 0 44- '

SI CI a1 A4 '0'

01 to v m.

w1 0o V0406. 0 4U-J -4 4) 00 0 .00 Q

0 ho j 0 O U 6. .4-j 41. -c .. & /0,

'0 4,1 C C6- " A . 4 '93 4)0a- .- w 1

.. w ,.-. -4-%.J a b.-

we .0 -A v~n 4 4z -) -. b. dA 41Of4-PC40 -.. s O. u U tol

00 60 -.4 Lov . .0 a aa 4 41u A I .6

a v 0 0 x0 No,~4 'a c a -4 #qv 0 %a ww 0 42 c to' aS

on1 va 4t I -410 -. a.

41 a 0.v D . x- 00 0 4w 04 be .0g' 01 '0 W. 6 4

0 > zt-. a.. w 41'i) 4- w 14 z

§ 9 4 1 L a'* 4. FA ox A# 1

U) V) +j 6.

V 0.

S..

*)4 0 o

.- U)

z 0 0

4.) 4.

to -W

E %4e 4)r9 Al ~

EC0 3 IV4 440 )(t4) 0 >

ba 44. -.

a >94.1 4) W 0 uu

C) M - 0 Ecc bC0~ a) .. % dw

ul 4a. 0~

44 0) .

c 0

6 m) 4.)

C6 4) i

ig c0 bl .

to 0 0 U~ 0 0 -, gn 0.0

V U)*0 0U.2

0 .C 0

to*- 0 0 L. Z

00 0 4 u 0 >U.Z 1J - 0 M"~ 0 Ctv 9) 4 FA M to '.A C

.0 5. -" v Qc W0

0 C- 0 4 C 0V Id . 0 144) U) U. 0. ) 4-41 (

.CvO£ 0 0 ~0 2

W3 a, 4

0-0 3

06

0- 0

w 00

4J.

'I. 0 e 40I.. V . . .

C c a ,0v c . 0c u *4 1

0 c G) 00 w t

0- ba4) 0 c

c4).. & do 41 A.w t c

I41 0 I4) W- 4.1 0

In~4 '-. in v o

to u x 0 ) 04 9: c r

inL .B 0 . 4) 0 vtoQ. :V x V0 '0 "m 00

wsi 4) c01 C - 0c 0b

to 0 a Vo if 4.1 4) 0~-@1 VC 96 U W0*C -- (n

0 0c4 1 qQ6 A

so c u 41 Aj 00t04 o c*) US U) c ciG 0)cr 01 9 )J

c N A1 0 4- -f 2&&4 kX&

0 4) LL ) C 0) 0..a 044 4 n-4v 4 L. -- 1.. 6 &d 1 " 0 tto 0 06U 0 IV0)4 0C 4) i 0c V a.0 J2 r~- ~- lowi -4 * . ~.0) L. 04a L.4j41 44

CCL to ue-i V) M.)0 v di 41C 10 u cC 0 I ..

S.. 10 .0 4) 0 ) 4)41 ..4 (6-~4 J 5

) .a >6a vVa cr .Liv 00 ee- 0 s4o

mC c 0 00 UW 4J) 0

- 9 VI 4 cC L ~4JIn) 0 c V)a 4MWz 00k -

zs- 3c Z

=- 0c l-Mwlm-

0 & I- I-ooc MC* Cul~~ ~ ~ ccC= C i=

1= ~ LUC= = %-= .-

0c be LAJ -J.JCDLL

= 2m 1.- ~ 6- LU-J

3c = LA -M 4c===LU L L J =2!

L- = J 0LUCR

LU

j -0I =or-

I-w I- U L

2- I- =MCL LLLL J C/=0 0i VCDML-= q< 00LL=C-

=JOI 0 - -m-

LU~~~uu COO . ~0L

La.I) UOcI- LU- 0'-

- = LuJ L.J

=L U J U.O Lw-C-) 0 -==V)W=CV) 1

- 7-

Cc* I

f--

=C03 -j

W-C= 0~

IM1c.LUJ LU)

W- LIP) L~

-r.

me am Cl a a)LW CC Ci cct O ~ @ am 2C4 ft"

-J =

09

Op(Nd

ATTACHMENT 11

ENGINEERING CRITERIA MANAGEMENT SYSTEM (ECH) ANDAUTOMATED FACILITY ENGINEERING INFORMATION SYSTEM WAEIS)

225

ATTACHMENT 11

Engineering Criteria Management (ECM) System

The ECM System is a management information system developed for the IAVFACEngineering and Design Criteria Management Division and used to manage thedevelopment and revision of all criteria documents produced or used by IAVFAC.It is an inventory of NAVFAC criteria and a plan for criteria update. Themain objectives of the ECK System, which uses the combined input of NAVFACHeadquarters and the EFDs are: (1) to determine criteria requirements, (2) toplan and execute the Navy's Facility construction programs, (3) to maintainthe status of all criteria documents, (4) to track scheduled and actualmilestone dates, and (6) to monitor the progress of planned versus actualperformance.

The ECM System is an on-line, interactive MIS, written in COBOL and residenton an IBM 4300 series computer at FACSO, Port Hueneme, CA. The data base isaccessed via remote terminals located at the EFDs and NAFVAC Headquarters.The on-line system will allow direct data access for updates and verificationand will allow a user to queue reports to his/her remote printer immediately.

The ECM System works hand-in-hand with GSS, P-34, the NFGS Data Base and DM-50to provide an accurate, up-to-date MIS. As NAFVAC criteria documents are 0updated and approved at Headquarters, the appropriate ECM System data base Crecords are updated. Most data base records are currently updated by the 0activity responsible for preparing or updating a document. Other records areupdated only by Headquarters personnel.

0The ECK System maintains an inventory of over 300 EAVFAC Guide Specfications, <700 Military and Federal Specifications, 150 Standard Drawings, 130 Design MManuals and Publications, and over 550 Definitive Drawings. The data base Zalso contains data categories pertaining to professional engineer/architectassignments, organization elements, job descriptions, job milestones, and Zresources data.

mz

(A

227

SYSTEM IDENTIFICATION

NAME

ENGINEERING CRITERIA MANAGEMENT SYSTEM/CUSTODIAN-REVIEWER-USER-MCA-PREPARER MANAGEMENT SYSTEM

SYSTEM POINT OF CONTACT

MR. GARY JOHNSONCESO• CODE 15612CUSNCBCPORT HUENEME, CA 93043

00

USER POINT OF CONTACTa

SAME

0

SYSTEM MANAGER POINT OF CONTACTz

MR. THOMAS RUTHERFORDNAVFAC, CODE 04M2 z200 STOVALL STREET .4

mALEXANDRIA, VA 22332

z

229

SYSTEM DESIGN

DIIRPOSE

r STANDARDIZE CRITERIA MAItAGEMENT

0 LIFE CYCLE MANAGEMENT OF CRITERIA UPDATES

0 MILESTONES

6 INHOUSE/CONTRACT COST DATA

0 PRINTING COSTS

3* AVERAGE AGE P

00

0 WORKLOAD MANAGEMENT p

0 BY BRANCH

* BY INDIVIDUAL o

2

230

SYSTEM DESIGN

CAPABILITIES

0 PROVIDES ON-LINE SUPPORT TO USERS

9 ADD DATA/RECORDS

I VIEW/UPDATE EXISTING RECORDS

* QUERIES FOR STANDARD REPORTS

* QUEUE BATCH REPORTS TO HIGH SPEED PRINTERS

8 AD-HOC QUERIES

0a

PLANNED ENHANCEMENTS 0

06 EXPAND USER ACCESS0 PROVIDE ADDITIONAL MANAGEMENT REPORTS 0

* INTEGRATE WITHAUTOMATED FACILITY ENGINEERING INFORMATION SYSTEM z

z-4

x

ztom

/

231

SYSTEM USERS

wHO

0 PROGRAM MANAGERS

* STANDARDIZATION MANAGERS

9 SUPERVISORS

0 ENGINEERS

* EQUIPMENT SPECIALISTS0 SPECIFICATION WRITERS

WHAT FOR0

I PROGRAM MANAGEMENT

0 DATA MANAGEMENT

* WORKLOAD MANAGEMENT mz

* HUMAN RESOURCE MANAGEMENTz

x

232

INFORMATION STORED

0 DOCUMENT IDENTIFICATION

0 SECOND LEVEL REFERENCES

* APPROVAL DATE

m

0 PLANNED/ACTUAL MILESTONES 000c

* FINANCIAL DATA a

I>0 PRINTING COST DATA 0

zI

IZ0 HEADQUARTERS/PREPARING ACTIVITY/ETC NOTES z

4Z

I

233

DATA SOURCES

0 CRITERIA DOCUMENTS

* PROGRAM MANAGERS

* USERS

30 SUPERVISORS

x

00

CTP C

n* EIC's

eq0 SPECIFICATION WRITERS

U

2

Ab-4

eqeq2S

234

SYSTEM OUTPUT

0 ON-LINE QUERIES

r S CRITERIA DATA0 MANAGEMENT REPORTS

9 USER REPORTS

0 BATCH REPORTS

0 CRITERIA DATA

0

0 USER REPORTS

0

z

z-4

z(APt

235

SYSTEM TYPE.

S MULTI-USER

0 NAVFAC HO

* EFD'S

* CESO

2360

ACCESS METHOD

* REMOTE

* UTILIZES NFS NETWORK

6 LEASED LINES (16.8K BPS)

* CURRENTLY USES BISYNC COMMUNICATIONS PROTOCAL

* WILL BE CONVERTED TO SNA/SDLC

0

0z

-4

0

z

0

z

237

QUERY CAPABILITIES

* STANDARD REPORTS AVAILABLE FROM ON-LINE QUERIES

* AD-HOC QUERIES THRU "ADR DATAQUERY/DATAREPORTER" SOFTWARE

0

0

C

mz

238

EQU IPMENT

S MAINFRAME DATA PROCESSING SYSTEM

0 IBM 4381 COMPUTER AT CENTRAL SITE

* IBM 4341 COMPUTERS AT EFD's

* WILL USE PC'S AS REMOTE TERMINALS AND AS STAND ALONE

PROC ES SORS

0

0

0Cmm0

mzfyi

239

RECOMMENDAT IONS

ACONCEPT COULD BE USED DOD-WIDE

COORDINATE DEVELOPM4ENT OF A COM4MON SYSTEM WITH OTHER DEPARTMENTS

0acft

0

zxVt

240

Automated Facility Engineering Information System (AFEIS)

1. AFEIS is designed to provide specification and drawing (design criteria)data in text form on a optical disk, together with software, to make theengineer's job easier. It will replace reams of paper with a 5 i/4-inchoptical disk weighing a few ounces. It will replace the manual effort ofthumbing through volumes of paper with a high speed full text retrievalsystem. It will replace the manual keying of text to project specifi-cation documents with an electronic transfer to a word processor.

2. AFEIS currently has Naval Facility Guide Specifications and P-34 and OCRSpecifications.

3. Users will be the engineering field activities of the Army, Navy, AirForce, other government engineering and design activities (e.g. HUD, VA,NASA), non-government A&E firms, and standard setting organizations.

4. Sources are Naval Facilties Engineering Command criteria and criteria ofthe Office of the Corps of Engineers.

5. Hardware:

~Central Data Base: IBM 4341

User Sites: IBM PC/AT or compatible CD/RON reader

6. Programs/Languaes:

e Full text search and retrieval language (to be selected from among 6)

* MultiMate word processor

e •OSS as modified for use in KS-DOS

MS-DOS

7. A contractor will be used to maintain control data base - to be selectedby the National Institute of Building Sciences.

8. Average answers are output from the system for quick review and

research. Word processing documents can be created from query retrievalsand output also.

9. AFrIS is a multi-user system.

10. Army and Navy preparing activities follow a regular update cycle.NAVFACBNGCOK and OCR approve final versions of criteria and release toNIBS and the central data base manager for subsequent release.

241

. ... j . . . ... . .. . . ...__

Automated Facility Engineering Information System (A191S)

11. Since the data base is distributed on optical disk, no remote access orcommunication links are deemed necessary.

12. The system will be expanded to includu all design and engineeringcriteria for facilities including drawings. The time target for this isSpring 1989.

13. There is no documentation at this point. The system is in the pilot andexperimentation stage. It should be operational by Spring 1987.

14. No DBMS is used. A full text search and retrieval package will be usedinstead.

242

Atit ,:'.it id 1;W i I LLy fKita , 'Ltiiy, Ii it i,"i.0 ion y ,:t (AI"I'L.)

Ths, AF.-', i; s ;I engine'er iig information .:.y-stv'-, under development by theNat ional InstLtute for Buildinag Science,:; (N IiB)L. This tystem., when fullyimplemented, will replace the 1' 34 and Db 50 sys;temns.

NIBS contemplates putting al guvernmlent and non-government fac.iltiesengineering and design criteria (e.g. specifications. design manuals,definitive drawings, Military handbooks, standard drawings, military andederai specifications, and a wide varitey of non-government standards), on a

m:ste" data base and distributing it with sophisticated text search softwaredesigned for easy user access. Currently, it is planned that a master datafile. a text search index, and a word processing software package will bemastered at a central contract location under NIBS management. The master database will probably reside on an IBM 43XX. A data base copy on magnetic tapewill be used to produce a master compact disk read only memory (CD-ROM) diskwith sufficient copies for distribution to subscribers.

Subscribers having an IBM PC/AT or similar equipment with a CD-RON reader,will be able to access all criteria and drawings on the disk using the search "

software package and move text found useful to the word processor fordevelopment of project specifications. 0

-CSince text :earch is being used. a data base manager is not needed. Search mtire should be approximately five seconds for an inquiry. 0

Currently. a system pilot test is being conducted by the NIBS and a privatecontractor and it is planned to be operational for Army and Navy Guide 0Specifications, and Reference Specifications, and P 34 by the Spring of 1987. <

MOther criteria documents will be added in 1988. M

zThe torget users for this Ly-t,,m are all architectural and engineering firns mneeding access to construction criteria and all Government activities and z

public works offices.x

Zystem documentation and the specitic search software to be used in the Mzoperational system will be :jvailable in the Fall of 1986. Current CO-ROM C

technology allows 256,000 pages of Lext onr a ') 1/4" optical disk. It is M

currently planned to distribute the txL data base, search software, andseveral utilities to facilitate use of the data base for an annual subscriberf,,e of less than $500.

243

oaf~

hI

a

IL

AUTOMATED FACILITY ENGINEERING INFORMATION SYSTEM

(AFEIS)

0 SYSTEM MANAGER/POINT OF CONTACT - NATIONAL INSTITUTE OF

BUILDING SCIENCES

* USER POINT OF CONTACT - TO BE DETERMINED

* AN AUTOMATED INFORMATION SYSTEM FOR READY ACCESS TO

FACILITY CONSTRUCTION SPECS

- USER ORIENTED

- QUICK SEARCH/RETRIEVAL CAPABILITY

- RAPID CONVERSION

246

AFEIS SYSTEM DESIGN

0 PLACES ALL GOVERNMENT AND NONGOVERNMENT FACILITIES

ENGINEERING CRITERIA ON AN OPTICAL DISK USABLE IN AN

IBM-PC/AT ENVIRONMENT.

* REPLACES 67,784 PAGES OF HARDCOPY CRITERIA WITH A 5 1/4

INCH OPTICAL DISK.

m

S PLACES CAPABILITY FOR RAPID RETRIEVAL/USE IN HANDS OF 00c

USER ON THE OPTICAL DISK: •n

- SEARCH/RETRIEVAL SOFTWARE 0

- WORD PROCESSOR0

- DATA/TEXT HANDLING UTILITIESzm

S INITIALLY NAVY/ARMY GUIDE SPECIFICATIONS (SPRING 1987).

LATER (87-88) ALL FEDERAL CRITERIA.z

* PUBLISHED FOUR TIMES PER YEAR ON A SUBSCRIPTION BASIS

(S500/YR OR LOWER).

247

AFEIS SYSTEM USERS

S ENGINEERING AND PUBLIC WORKS ACTIVITIES OF FEDERAL

GOVERNMENT.

* STANDARDS/CRITERIA PREPARING ACTIVITIES OF PRIVATE

SECTOR.

* A/E FIRMS

- NOW DOING WORK 00

- BIDDING WORK 0- DESIRING TO BID WORK -4

<

E EDUCATIONAL/RESEARCH INSTITUTIONS Z

z

9 STATE/LOCAL GOVERNMENTS x

THE SYSTEM IS TO BE USED FOR RESEARCH OF CRITERIA AND THE

PREPARATION OF PROJECT SPECIFICATIONS.

248

AFEIS INFORMATION BASE

nDllMFNT NUMBER PAGFiS

DESIGN MANUALS (FAC) 103 13,390

DESIGN GUIDES (COE) 96 9,600

TECHNICAL MANUALS (COE) 190 5,700

TURNKEY HOUSING (FAC) 1 144

"P" PUBLICATIONS (FAC) 13 1,300 P1

GUIDE SPECIFICATIONS (COMBINED) 650 16.250 C0m

FEDERAL CONSTRUCTION GUIDE

SPECIFICATIONS (COMBINED) 325 8,1250m

INSTRUCTIONS (FAC) 8 40z

zSTANDARD SPECIFICATIONS (FAC) 7 175 z

P1x

MILITARY/FEDERAL SPECIFICATIONS 2(COMBINED) 617 12,340

STANDARD DRAWINGS (FAC) 150 150

DEFINITIVE DRAWINGS (FAC) 570 570

TOTALS 2,730 67,784

249

AFF[S SOURCES FOR DATA/INFORMATION

0 NAVAL FACILITIES ENGINEERING COMMAND

• U. S. ARMY CORPS OF EN6INEERS

* OTHER U. S. GOVERNMENT AGENCIES (E.G., HUD, VA, NASA)

0 PRIVATE CRITERIA DEVELOPMENT ORGANIZATIONS (E.G., AST) I"I,

0aCm'1

-4

0I

zm

z.,4

x

250

AFEIS OUTPUT

* FULL TEXT OF DOCUMENT SEARCHABLE

S SELECTED TEXT CAN BE MOVED TO WORD PROCESSOR ACCESSABLE

FILE

0 REFORMAT UTILITIES CAN BE USED TO STREAMLINE/REORGANIZE

TEXT M

00

t SUBSEQUENTLY A WORD PROCESSOR AND UTILITIES CAN BE USED0

TO PREPARE:

- REPORTS0

- LETTER TEXT n

z- PROJECT SPECS

z

xm

z

251

AFEIS SYSTEM CHARACTERISTICS

0 A MULTI-USER SYSTEM

- EVERY USER HAS A DISK

- CAN SUPPORT MULTIPLE TERMINALS OR NETWORKED PCS

S DOES NOT USE COMMUNICATION LINKS ALTHOUGH OTHER PCS CAN

ACCESS A CENTRAL CD/ROM READER USING NORMAL PC COMM

LINKS OR NETWORKS

00* SYSTEM WILL HAVE ON-DISK QUERY CAPABILITY FOR WORDC

0

PHRASE, OR KEY-WORD-IN-CONTEXT SEARCH/RETRIEVAL

(5 SECONDS OR LESS RESPONSE TIME)0mzS AFEIS IS A PC BASED COMBINATION WORD AND DATA PROCESSINGzSYSTEM -4m

xmz

252

RECOMMENDATIONS

9 AFEIS SHOULD BE USED THROUGHOUT DOD (AND THE FEDERAL

GOVERNMENT AND THE PRIVATE SECTOR) TO:

- REDUCE PAPER VOLUME

- REDUCE DISTRIBUTION COSTS

- INCREASE UTILITY OF CRITERIA

- ASSURE MORE PRODUCTIVE AND RELIABLE USE OF

ENGINEERING RESOURCES (THINK TIME)

- SPEED ACCESS TO SPECIFIC DATA 00cn

* ANYONE INVOLVED IN FACILITY CONSTRUCTION SHOULD SUB-

SCRIBE TO AFEIS0mz

z

mxm

zm

253

ATTACHMENT 12

THE ARMY SPECIFICATIONS AND STANDARDIZATION COMPUTER SYSTEM (DEPSOMIS)

255

1. SYSTEM IDENTIFICATION

SLIDE #1 THE ARMY SPECIFICATIONS AND STANDARDIZATION COMPUTER SYSTEMIS THE DEPSO-MIS.

THE DEPSO-MIS USES SD-4 AND DODISS DATA SOURCES IN ADDITIONTO ARMY STANDARDIZATION ACTIVITIES INPUT, TO PROVIDE MANAGEMENTORIENTATED INFORMATION.

SLIDE #2 THE SYSTEM IS OPERATED BY HQ AMC AND ASSISTED BY BDM CORP WHOIS CONTRACTED TO ADMINISTER THE DATA BASE. A CYBER 180/835COMPUTER LOCATED AT FORT BELVOIR IS THE HOST COMPUTER FOR THEDEPSO-MIS. CURRENTLY THE 14 STANDARDIZATION ACTIVITIES SHOWNARE USING THE SYSTEM. THIS REPRESENT OVER 95% OF ARMYSPECIFICATIONS AND STANDARDIZATION WORKLOAD.

2. SYSTEM DESIGN

SLIDE #3 THE DEPSO-MIS WAS DESIGNED TO AUTOMATE ESSENTIAL STANDARDIZATIONINFORMATION REQUIRED BY STANDARDIZATION ACTIVITIES TO EFFECTIVELYMANAGE THEIR PORTION OF THE ARMY STANDARDIZATION PROGRAM.

THIS STANDARDIZATION INFORMATION INCLUDES SUCH DATA AS PROVIDEDIN THE SD-4, SD-i1DODISS AND SO FORTH.

SLIDE #4 THIS SLIDE SHOWS THE INPUT, OUTPUT AND FLOW OF DATA THAT PROVIDESMANAGEMENT WITH THE INFORMATION FOR PLANNING, BUDGETING ANDDECISION MAKING. THE DATA FLOW FOLLOWS BASIC COMPUTER CONCEPTS.

SLIDE #5 THIS SLIDE SHOWS MAJOR STANDARDIZATION PROGRAM AREAS OFINFORMATION THAT ARE REQUIRED BY STANDARDIZATION MANAGERS TOSATISFY THEIR PROGRAM REQUIREMENTS.

SLIDE #6 DATA BASE REVIEWI WANT TO DISCUSS AND PROVIDE YOU MORE INFORMATION PERTAININGTO THE DEPSO-MIS DATA BASE. THIS SLIDE IS AN OUTLINE OF THEDATA BASE AREAS THAT FOLLOW.

SLIDE #7 FUNCTIONALLY, THE DEPSO-MIS PROVIDES FOR A MENU, CONSISTINGOF THESE CATEGORIES AND TYPES OF INFORMATION FOR USE IN QUERYING,REPORTING AND SUMMARIZING.

SLIDE #8 THIS SLIDE IS A DIAGRAM OF HOW THE DATA INTERACTS WITH THE MAINCOMPUTER AND TERMINALS. THE SYSTEM IS INTERACTIVE AND INCLUDESA SEPARATE FILE FOR MAINTENANCE, BACKUP AND SECURITY REASONS.

SLIDE #9 DATA INPUT MAYBE INTERACTIVE WITH THE COMPUTER OR LOCALLYPROCESSED AND TRANSMITTED BY MAIL. IN EITHER CASE, THE DATAIS SCREENED BY THE DATA BASE ADMINISTRATOR PRIOR TO INCLUSIONIN THE DATA BASE.

257

SLIDE #10 USING THE SD-4 DATA CURRENTLY IN THE DEPSO-MIS DATA BASE ANYPROJECT CAN BE SCREENED AND LISTED IN A GIVEN CATEGORY (I.E.OVERAGE, METRICATION, CIDs ITEM REDUCTION, ETC) FOR STATUS REPORTSAS SHOWN ON THIS NEXT SLIDE #11.

SLIDE #12 THE DEPSO-MIS ALSO INCLUDES AUTOMATED DODISS INFORMATION WITHLIMITED SEARCH AND DISPLAY CAPABILITY. IT CAN BE SCREENED BYPA, CUSTODIAN, VALIDATION DATE r-SC... HOWEVER, THE DODISS DATABASE IS STILL UNDER DESIGN AND LILL REQUIRE A CONTRACT EXTENSIONTO COMPLETE THE DESIGN.

SLIDE #13-14 THE NEXT 2 SLIDES ARE PARTS CONTROL FORMATS THAT ARE INTHE DATA BASE ARE USED IN PARTS CONTROL REPORTING.

THE FIRST SLIDE OF THESE TWO RELATES TO CONTRACT PERFORMANCEBY EACH STANDARDIZATION ACTIVITY.

THE SECOND SLIDE REPORTS PARTS CONTROL ACCOMPLISHMENTS BY ASTANDARDIZATION ACTIVITY FOR A MAJOR WEAPON SYSTEM/EQUIPMENT.

IN ADDITION TO THESE TWO REPORTS THE PCP DATA BASE CAN BE QUERIEDAND SCREENED ON SELECTED DATA ELEMENTS; I.E. CONTRACT NAME,NUMBER, TYPE.

SLIDE #15 AND 16 THE LAST TWO SLIDES ARE SAMPLES OF THE DEPSO-MIS SUMMARYREPORTS. THE SUMMARY REPORTS ARE FORMAL REPORTS FOR MAJORSTANDARDIZATION AREA OF INTEREST THAT USUALLY LIST STANDARDIZATIONACTIVITIES PERFORMANCE BY QUARTER/YEAR.

SLIDE #15 THIS SLIDE SHOWS THE STATUS OF OVERAGE DOCUMENTS FOR A SPECIFICARMY STANDARDIZATION ACTIVITY BY QUARTER/YEAR.

SLIDE #16 THIS SLIDE SHOWS THE STATUS OF OVERAGE DOCUMENTS FOR A SPECIFICPERIOD FOR ALL THE ARMY ACTIVITIES.

NOTE: THE DATA SUPPORTING THESE REPORTS IS INPUT BYSTANDARDIZATION ACTIVITIES IN THE DEPSO-MIS PERIODIC REPORT.

2

258

LL U

Pz0 0u

0

.j Z

~LU

zwU

09Z

v I.

Am 4

uwa.I-

19Z

~0

1 Z Z0 0

-- U0.%AI0

LL.

I-0z2%A 0 -I

IfI=

LUz 0 ofLA.oW 0

0ILMzzILl

u 4A

LU UJ

z% 040

ALa

£ 9z

WZ

a.w$A I2

us

o toUA 0

aaU.0

0.0 v 80 -j s 9 -IA 4 0 wCL w w

q 2V -d ovz 90

3 92z n 1

.. w'j 2 v00 W2

t9z

z

LU

zo0

m 0

U.Oaw

_ z00c

0u 0 %A

* S • Sc

C

0

aa

Z I-

41 LL.

ILA %A

M( ~ >m~

%bo*ftwo -

z 1 -eg >

99Z

loo go

S~l IA

LA 0 r9L

cr U'

.A*m

0 L16-%Ao

I61

L 9Z

In in

a I f"0Imn C

o InIIA v

LU

a Ii

I.-. I.-

#AUO

0 I

I U

89Z

>0

ILAjOO 0

I n Un $

.Lt 1!

0°n IC I ih. _u ; E I I iL,. cr. IL4 z

LAI

0 .

41:

0

-1

elm) im

69Z

*w-I-.-a0000mqaowe 4

- 4 a~ toaM N MM i0 0 cc0

w Iwz

o1

mwU.-w V -

4A 00 r4 V, e4

ILI- - in M In q --

OZ ~

0 IL2~ a-'or &-

v IA

0 0o v

IA '

a t 9.- M, %N f4 ovM

#4z

MA %A

0 L

I-.L

tAm

I-<zLUwwL

wL 0 %A Lj

000

9 TLZ

Iv

v

za

0U

van CY

CZ 0

SIL

t3 . q_ _'

zza

04

Vz

w2

UV

4c 4c UAw22 i L

-a

zI- X

2 F.-4w U91

W6

U, z -w

0- 0c An

UU 0

020

U' Oz

9o 2

4A v2

.2 4iSv

00

zU

ul2

LP~

- -Z

0 z zLU f4

LUU

I-60a

LIIU

> _ _ _ _cc_

w 5J

in 'LAWaU LULw0wau

IL a a9L '

'Jo C o9

|1l,

0

!OA

|g

II-

0 z U

a-

00

o z

9 '4 __

9'.1-

Vn L z -

~W W a

Oct

ATTACIHENT 13

THE DOD INDEX OF SPECIFICATIONS AND STANDARDS (DODISS) ANDNAVY PRINT ON DEMAND SYSTEM (UPODS)

275

ATTACI4ENT 13

NAVAL VUBLICATIONS AND FORMS CENTERALICE BELL, PRESENTOR

SPFCIFICATIONS AND STANDARDS RELATED COMPUTER SYSTEMSMEETING HELD AT SHERATON NATIONAL HOTEL, ARLINGTON, VA

MAY 13-14, 1986

BRIEFING SYNOPSIS

The system being described has been contracted but is not yet implemented.

Full implementation is anticipated by February 1987. The current processing

methods for standardization document issuing and DODISS preparation is

encumbered by manual efforts. The only automation accomplished today through

computer visage is the DODISS catalog file. The present filing system stores

catalog information without capabilities of on-line update or inquiry.

rhe new system, NPODS, is described in two subsystems, the order entry and

the print!nn. The Navy Publications and Printing Service Office,

Philadelphia and the Nava. Publications and Forms Center are the users of NPODS.

The ordir entry stibsystem will contain basic data for item identification,

inventory management capabilities, DODISS catalog data, requisition processing

requirements, and have the ability to provide statistical data both standard

and unique.

The priniting subsytem will contain the full text of standardization

documents and be capable of producing the paper imaged documents for requestors.

Remote acceps to non-iscr activities is not included.in the initial

inntallatlon (f NPOIDS, but f- considered among future enhancement.

277

- 6LF

CP>

CP>

C-C,

1--4

COO>,

OBZ

[,-,

_ rT. <I-:

Cow> F--4

DoM C4-)b1-4 DOM DN-

'--4M[U

4- Colo>

i_-..

li-,

COPS)

C-,4-mmlCP

Emm_ i-coo _m

-4 r~i 63

_ _ _ _ ( u. '

COO _o>2

COP 0U N =

_iz LQ

.0 COP>~_= COO_

COO[>

CO* -

_ ~COOP

coop>-C-rm06r1

[U CO[>

_COP>

FE-miCO>

Colo,$_ -4 _

CO*

FE-mCO_C*-

_COO>

COOD

C=C:

- -

mC-:

rt

- m.

RIC=

- _t

=2

wEE _ Q C-"--' -Z i::m Z

I - o<:Z

= =

CO

9-4 9-4

- --- --- --

98Z

[I I

f< >

-4

-4n-

4c=4

-4 [OP>

co* E-[U w

LC4=_I-.C[OP>

CCOO>

CCOO_ _O IC-

_=Ono

....-.

C*

CO>

COOP> r~

6=4 w4 "u4= 9= -6q 1

_Can

68Z

W.4~ &--

=004~~ Cop><.

&--@ I-4 [&Q

coopC> &A4 &M

~~COP>-- 4 '~ =OP>

1- C, ~C>m

06Z

Co-

COP>

1COO_

r~3d=

COP LaJ _O

4C>

---------

16Z

IZ

CCOO

CO>

1 "I

I '

NAVY AUTOMATED PUBLISHING SYSTEM(NAPS)

The Navy Automated Publishing System (NAPS) is the overall concept for allinitiatives in electronic information storage, retrieval, multi-media output anddistribution of Navy Printing and Publishing. NAPS is adopting state of the artautomated publishing and printing technologies for transition to a digital technicalinformation database with a print-on-demand capability. The NAPS conceptcapitalizes on developments and trends in information technology towardimproving the movement, storage, local availability, and timeliness ofdocumentation Navy-wide. NAPS will integrate independent data bases to processinformation utilizing electronic preparation, production, and distribution of fullpage images. The application of database management and automated publishingand printing techniques will reduce overhead costs, labor intensive warehousingrequirements, out-of-stock conditions, secondary printing, and out-dated technicalinformation.

The Navy Publications and Printing Service (NPPS) plans to integrate this conceptthrough service bureau type facilities. These service bureau facilities are currentlyco-located with major Navy activities throughout the world. The corporatestructure of NPPS enables it to provide both policy and line control over all itemsprinted within the Navy. This responsibility is ultimately controlled within the NPPSManagement Office; thereby allowing coordination for all automation initiatives atone central location.which allows for total system compatibility. The IndustrialFund concept under which NPPS operates allows for the purchase of requiredhardware and/or systems for operating purposes under a capital equipmentprogram whereby such equipment or system can be reimbursed on the basis of theservices provided to customer activities.

By capitalizing on this coprorate structure, NPPS needs only to network its presentfacilities to transition from a manufacturing based entity producing line items ofprinting to an information processing organization which will offer Navy a fullyautomated network of central data bases structured to improve movement,storage, local availability, and timeliness of documentation.

NAVY PRINT ON DEMAND SYSTEM(NPODS)

The NPODS project was initiated in 1979 as an attempt to more rapidly provideMilitary Specifications and Standards to the user community (primarily the privatesector) and to eliminate out of stock conditions and back order problems throughthe use of automated data base publishing techniques. The objective of the NPODSinitiative is to reduce labor costs and response times associated with printing andhandling shelf stock. Appropriate ADP and Congressional Joint Committee onPrinting (JCP) approvals were solicited and granted by the JCP in January of 1982and by GSA/NAVDAC in October 1983.

NPODS is being developed in support of the Naval Publications and Forms Center(NPFC), Philadelphia. The system consists of three functions: order entry, digitalstorage, and demand printing. Orders for non-digitized documents will be satisfiedvia warehouse picking personnel using computer-generated retrieval lists. The data

293

base will consists of approximately 800,000 pages, which will be stored on optical .disk and output on demand on high speed laser printers. Expected to handle 45million pages annually, the project is funded at $5.5 Million under NPPS NIF for FY8S-86.

Many small businesses made bid requests on NPODS through the 8A Small BusinessSet Aside Program of SBA. The contract was awarded in Feb 1986 to Capital SystemsInc. in conjunction with groups from the Ziff and Xerox corporations. Theirproposal offerred initial scanning of 85% of the original collection, which precludedthe need for a second phase.

Site preparation and total system implementation is anticipated within one year.

Concurrent with the initial NPODS project, a study will be conducted to determinethe feasibility of mi grating the NPODS pilot project to other NPPS sites as well asdemand printing aboard ships. In addition, the following specific functions will beexplored: (1) alternative storage media such as optical disks and conversiontechnologies; (2) the ability for specified document sponsors to access the data basefrom remote sites in order to make online revisions/changes; (3) the ability forsponsors and users to query the data base and perform content searches; and (4) theability to provide an online Department of Defense Index of Specifications andStandards (DDSS).

Additional document collections that have been identified for potential NPODSapplication include forms, directives, technical manuals, and other administrativematerial currently stocked at the NPFC.

OPTICAL DIGITAL DATA DISK CONVERSION SERVICES

A specification has been written which will provide a digitization service bureaufacility to Naval activities through their local NPPS. Such a service contract, whenawar~ded, will provide for various types of scanning technologies and the masteringof the scanned data to optical disk storage media. Due to our NIF structure, allservices can be acquired with customer activities reimbursing NPPS on the basis ofservices provided or units produced. This will obviate the necessity for individualactivity funding and establish a vehicle which will also provide Navy inherentcompatibility.

294