DOCUMENT-RESUME

ED 243 465 _ IR 011 08:9

AUTHOR Thomas, Everett L., Jr.; Deem, Robert N...TITLE Unified Database Development Program. Final

Report.INSTITUTION Clemson Univ., S.C.SPONS AGENCY Air Force Human Resources Lab.., Brooks AFB, Texas.REPORT NO AFHRL-TR-83-52PUB DATE Mar 84CONTRACT F33615-79-C-0027NOTE 129p.PUB TYPE Reports - Descriptive (141)

EDRS PRICE MF01/PC06 Plus Postage.DESCRIPTORS Aviation Technology; *Databases; Design Requirements;

Information Storage; *Information Systems; *OnlineSystems; Program beTiptions; Program-Development;*Recordkeeping

IDENTIFIERS *Aircraft Weapon ISystems; *Design (Engineering)

ABSTRACT°The objective of the unified database (UDB) program

was to develop an automated information system that would be usefulin the design, development, testing, and support of new Air Forceaircraft weapon systems. Primary emphasis was on the development of:(1) a historical logistics data repository system to proilideconvenient and timely access 'to relevant information about existingaircraft weapon systems; (2) a-fully automated logistics supportanalysis record system that would satisfy current Air Force andDepartment of Defense requirements; and (3) an overall UDB system tofunction as a closed-loop system for use throughout the life of aweapon system. This report summarizes the accomplishments of the UDBprogrhm and major UDE system features and capabilities. Report`sections describe project background; the UDB concept and objectives;the Automated Logistics Support Analysis Record (ALSAR) system, whichhas been fully developed, and partially tested using HH-60 helicopterdata; the current development status of the prototype AircraftCharacteristics Data File (ACDF), which will contain historical dataon aircraft weapon systems; related studies of the Air ForceOperational Test and EvaluationCenter (AFOTEC) requirements for anew weapon system and of combat data sources; and conclusions andrecommendations For future UDB development. A four-item bibliography,a list of abbreviations, and sample ALSAR data sheets and ACDF onlinedata screens are also provided. (Author/ESR)

***********************************************************************Reproductions supplied by EDRS are the best that can be made

from the original document.***********************************************************************

AFHRL-TR-83-52

AIR FORC

a

O

it)

N

E

S0URCE

S

U.S. DEPARTMENT OF EDUCATIONNATIONAL INSTITUTE OF EDUCATION

EDUCATIONAL RESOURCES INFORMATIONCENTER (ERIC)

This document has been reproduced asreceived from the person or organizationoriginating it.Minor changes have been made to improvereproduction quality._

Points of view or opinions stated in this document do not necessarily represent official NIEposition or policy.

UNIFIED DATABASE DEVELOPMENT PROGRAM

By

Everett L. Thomas, Jr.

Clemson UniversityClemson, South Carolina 29631

Robert N. Deem

LOGISTICS AND HUMAN FACTORS DIVISIONWright- Patterson Air Force Base, Ohio 45433

March ,19134

Final Report

Approved for public release; distribution unlimited.

LABORATORY

AIR FORCE SYSTEMS COMMANDBROOKS AIR FORCE BASE,TEXAS 78235

2

NOTICE

'When Government drawings, specifications, or other data are used for any purpose other thanin connection with a definitely Government - related procurement, the United StatesGovernment incurs Do responsibility or any obligation whatsoever. The . fat that theGovernnOnt may have formulated or in any way supplied the said drawings, specifications,or other:data, is not to be- regarded by implication, or otherwise in any manner construed,as liciepy!ing the holder, or any(ether person or corporation; or as conveying any rights orpermission to manufacture, use, or sell any patented invention that may in any way-be relatedthereto.,

The Public Affairs Office hits reviewed this report, and it is releasable to the NationalTechnical Info6nation Service, where it will be available to 'the general public, includingforeign nationals.

This repqrt has been reviewed and is approved for publication.

JOSEPH A. BIRT, Lt Col, USAFTechnical DirectorLogistics and Hirman Factors Division

ALFRED A. BOYD, JR., Colonel, USAFCommander

4

UnclassifiedSECURITY CLASSIFICATION OF THIS PAGE (When Data Entered

*REPORT DOCUMENTATION PAGE

' READ INSTRUCTIONSBEFORE COMPLETING FORM

1. REPORT NUMBER

3FHAL-TR-83-522. GOVT ACCESSION NO. 3. RECIPIENT'S CATALOG NUMBER .

4. TITLE (and Subtitle) -

UNIFIED DATABASE DEVELOPMENT PROGRAM

1

5. TYPE O REPORT & PERIOD COVERED

Final

6. PERFORMING ORG. REPORT NUMBER

7. AUTHOR (s)

Everetr L. Thomas, Jr.Robert N. Deem

r.

8. CONTRAQT OR' GRANT NUMBER (s)

F33615-79-C-0027.

9. PERFORMING ORGANIZATION NAME AND ADDRESSClemson University .

Clemson, South Carolina 29631 ,

10. PROGRAM ELEMENT, PROJECT, TASKAREA & WORK UNIT NUMBERS62205F $,

17100020

11. CONTROLLING OFFICE NAME AND ADDRESS,HQ Air Force Human Resources. LabOratory (AFSC)Brooks Air Force Base, Texas 78235 ,

12. REPORT DATE

March 1984 .

13. NUMBER OF PAGES

110

14. MONITORING AGENCY NAME & ADDRESS (Y..different from Controlling Office)Logistics and Human Factors Division .

Air Force Human Resources Laboratory ,

tVright43atterson Air Force Base, Ohio 45434

/

15. SECURITY CLASS (of this report)'

Unp,laasified

15.a. DECLASSIFICATION/DOWNGRADINGSCHEDULE

16. DISTRIBUTION STATEMENT (of this Report) ..

'Approved for public release; distribution unlimited.

.

17. DISTRIBUTION STATEMENT (of this abstract entered in Block 20, if different from Report)t .

-. -

.

18. SUPPLEMENTARY NOTES .

,-

.,...

19. KEY WORDS (Continue on reverse side Y. necessary and identify' by bloc ntunber),

integrated logistics support logistics support analy is . system availabilitylogistics engineering logistics support analy is record systems engineeringlogistics information systems product performance easurement weapon system acquisitionlogistics planning reliability'and main ability 4

. .

20. ABSTRACT (Continue on reverse side Y. necessary and identify by block munber)The objective of the unified database (UDB) program was to develop an automated system that would be useful

to those responsible for the design, development, testing, and support a new Air Force aircraft weapon system. Primaryemphasis was on (a) development of an historical logistics data repOsitory system to provide convenient and timelyaccess to relevant information about existing aircraft-weapon systeins, (b) development of a fully automated logisticssupport analysis record system that would satisfy current Air Force and Department of Defense requirements, and(c) develop the ovefall UDB system-to function aika cloied-loop system for use throughout the life of a weapon system.This report summarizes the accomplishments Of the UDB program to date and describes the major features andcapabilities of the UDB system.

DD Form 14731Jan 73

EDITION OF 1 NOV 65 IS OfISOLETE Unclassified

SECURITY CLASSIFICATION OF THIS PAGE (When Date Entered)

4.

Objectives

The objectives were to provide a logistics database structure t ha ctical use of historical and (trrent7

logistics information. The structure was to be tested for its use in facilitating nee oLl-o' tics factors upon weaponsystem design. °j

Background

The Air Face is concerned with the lack of adequate logistics cons' tion during the weapon system design1

4process. To produce a weapon system with optimal cost and mission effect st logistics factors must be consideredvery early. and throughout the s)ystem design and acquisition process. Re oD Standards and Instructions haveindicated a strong commitment to consider logistics as an integral part of the weapon system design activity.

-The logistics information system available to the designer and logistician must be adequate. Yet,, for many years

large amounts of logistics information and data have been collected and - processed on many different weapon systems,but this was done mainly to improve the capability of existing weapon systems and the.information systems were structuredto support that end. The existing logistics systems ddnot provide timely responses to requests for information or.data,there is no traceability to the data origin, and in many instances the data are neither consistent nor accurate to the degreethat is required to support weapon system design. The Unified Data Base (UDB) program was formulatea to address theseisAies. . J , `..../.

N

Approach

The UDB development program was conducted in three phases. In the first phase, the detailed definitions,specifications, standards, formats, and computer flow charting 'were addressed and completed. In accordance withpublished DoD guidance, the UDB elements were based on Military. Standard (MIL-STD) 1388 -2.. Additional elenientswere added to allow for the feedback of historical operational logistics information and to address additional data needsassociated with common logistics support analysis techniques. The U1243 was programmedlor computer applicationduring the,second phase. The third phase consisted of the demonstration,,testing, and further de-bugging of the UDBusing two acquisition programs as test vehicles.

Specifics\i,

)

This UDB development program continued building on the resqts of a previous program that established the needfor additional data elemrts beyond those outlined in MIL-STD-I38-2 and on the results of the Tri-Services LogisticsSupport Analysis Record (LSAR) Working Group (which continuously reviews the logistics data needs and requirementsof all the Services). Specifically, the automated LSAR requirements and the various logistics-related Contract DefinitionRequirementstist (CDRL) items associated with the C-X procurement activity were closely reviewed. . -,)

^.

. , . ,The UDB can be accessed via computer terminals, by punched card input, or by high speed printers (batch

processes). About 70 different computer terminal fiirmats (screens) were designed to permit very efficient. and timelyinput, update, access, deletion, etc. of logistics information for any weapon system program. Large amounts of data input,.standard output reports, summarizations, and CDRL items are best handled via batch processes. Ample subsets f the

iiidatacan be _safeguarded from unauthorized updating, inputting, deleting, reading, etc. Audit trails are maintains as

to who input, read, updated, etc. the information and when and where it occurred.

The UDB was tested and demonstrated using the HH-60 helicopter and the B-1B aircraft acquisition programs.The historical-information side of the UDB was demonstrated on the HH-60 using previously generated data from theArmy. Some standard summary reports were generated by the UDB from this data. No potential HH-60 problem areaswere discovered. The current logistics information side of the UDB is being demonstrated on the B-1B program. B-1Bdefensive avionics maintenance jind training information for the operational, i diate, and depot levels of

a

%

1

rr

maintenance are being entered into the DB. The training and technical-manual futictionaloareasi retrieved thisIto

inarmation via terminal) from, the UDB so t at critical concerns could be relayed ithmediately to.design for appropriate

.design consideration., 4,

I

Conclusions and Recommendations r

The oejectives were attained. A logistics database structure, the UDB, -Wm] 'developed. Its practicality was

dernpnstrated by using historical information on the HH-60 program and current information on the B-1B program. As

a result of this UDB effort, both hi:storical and current logistics infOrMation can now have more influence on the design-

ofof systems.3e

It is recommended that the UDB'be further expanded to incorporate more efficiently the Air Force Operational Test '.

,..r.LA Evaluation Center (AFOTEC) results into the UDB and, thereby, into the design activity. This expansion shciuld

build on the initial work by a contractor to outline the mapping between AFOTEC data and UDB data and`to.identify

additional AFOTEC data needs that the'UDB does not currently address. The UDB should also be expanded toiwerface

More efficiently `with computer-aided design (CAD) activities that are themselvesbecoming so predominate throughout

the aerospace industry. Commonality of data elements between UDB and CAD databases should be identifiedAnd

processes to further introduce logistics factors into the CAD desigtfactivitles should be defined... . . .

I

,*

1.

PREFACE

This work was initiated by the Logistics and Human Fac- tors Divisi n, Air

Force Human Resources Laboratory, Wright-Patterson Air Force Base, Ohio, under

Project 1710, Weapon Systems Logistics and Combat Maintena nce, Lt. Col. Joseph.

A. Bi.cTroject Scientist. Project 1710-addresses the planning, developing

and managing of logistic.,A,5upport of Air Force Logistics and Combat

Operations. The Work 1.1.it was 1710:-00-f0, Unified Database f6r,Weapons

Systems'Design. WorkUnit 1710-05-20 develops logistics among,;logistics ,re-

sour,ces, systems design, and operational procedure6.

Appreciation is extended to Dr. William'B. Askren and to Mr. Russell M.

Genet for, their guidance and cliection throughout this effort. AppreC.iation

. is also extended to the many individuals of the Air Force Logistip. Command,,

Air Force Acquisition Logistics Division, and the AirsForce Operational Test

and Evaluation Center without whose assistance this work would not have been

possible.

This was a cooperative e t between Clemson University, the Lockheed-

Georgia COmpany,the BDM Corpor4tion, the McDonnell-Douglas Corporation, and

the AIL Corporation.. Appreciation is extended to the many individuals at

those organizations whose efforts made this work possible.

TABLE OF CONTENTS

SECTION I

-I.

: BACKGROUND

POLICYDIRECTIVES

\ MILITARY STANDARD (MIL-STD) 1388l'RODUCT:PERFORMANCE FEEDBACK SYSTEM (PPFS)

/-- UNIFIED DATABASE TECHNOLOGY ,"

DEFINITION STUDY

Pay

1.

1

1

1

2

3-3

UDB DEVELOPMENTT

3

. SECTION II UDB CONCEPT1, 4

CENERAII N. 4

PURPOSE 4

OBJECTIVES 4

CONCEPTUAL APPROACH 5

CLOSED-LOOP SYSTEM 5

Objective 1 5

Objective 2 5

Objective 3 0 7'

Objective 4 8

Objective 5Objective 6 9.

Objective 7 9,

Objective 8 10

Objective 4' 11

Objective7' 11

PROTOTYPE UDB APPROACH 12

INITIAL PLAN 13

UDB FEATURES 13Objective 1 13

Objective 2 13

Objective 3 15

Objective 4-7 15

Objective 8 15

SECTION III AUTOMATED LSAR SYSTEM 16

OVERVIEW 16

BASELINE 16

DOCUMENTATION 16

Data Sheets 17

Data Entry Instructions 18

ALSAR 'Users Guide 19,

Access and Security Manual 19

Maintenance and Update Manual 19

alb

TABLE OF CONTENTS

Page

SYATM DESIGN 19

GENERAL FEATURES 21

LSA CONTROL NUMBER (LSACN) 21-

PERFORMANCE TRACKING 21

Additional Data Elements 21

Task Codes 23

How Malfunction Codes and Work Center 23

'Maintenance Events/Maintenance Actions 23

'ALTERNATE ACTION 24

LSAR REVISIONS 24

EFFICIENT DATA ENTRY 25

Key Parameters 25

Header Information 25

Multiple Applications 26

NARRATIVE DATA 26

ONLINE PROCESSING 27

MENU SCREENS 27

DATA ENTRY SCREENS 28

ENTERING DATA 29

EDIT CHECKS 29

DATA RETRIEVAL 30

DATA UPDATE 30

.GLOBAL CHANGE CAPABILITY 31

GENERIC, COPY CAPABILITY 31

MAINTENANCE AND SUPPLY SUPPORT FILES 31

BATCHPROCESSING 32

INITIAL BATCH LOAD 32

Phase .1 33

Phase 2 33

Phase 3 33

SUSPENSE REPORT 34

TURNAROUND DOCUMENTS 34

PROMPTING DOCUMENTS "35

LSA/LSAR PROGRESS REPORTS 38

LSACN Status Report 1 38.

Data Sheet Status 38

REPORTING SYSTEM 39

DARCOM LSA REPORTS 39

DATA ITEM DESCRIPTIONS (DID) 40

REPORT SELECTION SCREENS 40

TAPE OUTPUTS 42

REPORT REQUEST SUMMARY 42

vi 9

441

TABLE OF CONTENTSr

Page

SECTION IV AIRCRAFT CHARACTERISTICS DATA FILE 44GENERAL 44

PURPOSE AND USE 44.Conceptual Phase 44Preliminary and Detailed Design. Phases 45'06,S Phase 45Research and Development (R&D) Activities 45TECHNICAL APPROACH 45MODES OF OPERATION 46

Data Entry 46Data' Retrieval 46

DOCUMENTATION 46ACDF DED 47Data Input Record Layouts 47Users Guide 47

Programming Documentation 49ACDF RECORD CONTENTS 49

AIRCRAFT RECORD 49MISSION RECORD 50

BASIC MISSION PERFORMANCE RECORD 50SYSTEM DESIGN AND PERFORMANCE RECORD 50ENGINE RECORD 50SYSTEM UTILIZATION RECORD 50

SYSTEM FEATURES RECORD 50AVIONICS SYSTEMS RECORD 51SYSTEM R&M COST RECORD 51

OPERATIONAL SUPPORT AND COST RECORD 51

Aircraft Level/AFR 80018 Format 4 51

Work Center by Aircraft 51Support Cot by WUC 52

R&M Data by WUC 52

Maintenance Action by WUC 52

NATIONAL STOCK NUMBER RECORD 52

SUBSYSTEM RECORDS 53ON-LINE SYSTEM 53

RECOV COMMANDS 54

QUERT COMMANDS 55LAC Command 55LAV Command 55'

LDE Command 56LEN Command 56SEL List Command 56

AVS Versus Equipment 57.

4, Engine Data 58

National 'Stock Number Data 58ON-LINE CRT SCREENS 58HARD COPY DATA

b 58

vii

10

SENTION V'

TABLE OF CONTENTS

Page

AFOTEC AND COMBAT DATA 59

GENERAL 59

OT&E REQUIREUENTS 59

OBJECTIVES AND APPROACH 59

AFOTEC INPUTS AND OUTPUTS 59.

UDB CAPABILITY 60

OT&E RESULTS 60

COMBAT REQUIR4MENTS 61

'OBJECTIVES AND APPROACH 61

SUMMARY OF RESULTS 61

SECTION VI CONCLUSIONS AND RECOMMENDATIONS FOR FUTUREDEVELOPMENT 62

CONCLUSIONS 62

FUTURE RESEARCH AND DEVELOPMENT 162

ALSAR 63

Production Support and Software Maintenance 63

Redesign to Support MIL-STD-1388-2A 63

Transportability 63

Word- rocessing Capability 64

F tional Users Guide 64

ACD 64

Load Data 64

Interface Programs 65

Trend Data Graphics 65

OT&E INTERFACE 65

INSTALL AND DEMONSTRATE UDB 65

COMPUTER-AIDED DESIGN (CAD) 65

REFERENCES 67

ABBREVIATIONS 68

"APPENDIXES

A ALSAR D SHEETS 71

ACDF ON.-LINE DATA SCREENS 89

11

LIST OF FIGURES

FIGURE I UDB IN WEAPON.SYSTEM LIFE CYCLE 6

2 TOTAL AIRCRAFT WEAPON SYSTEM3 PROTOTYPE UDB FEATURES 14

4 DATA SHEET MENU SCREEN 185 ALSAR SYSTEM btSIGN. 20,

6 A2SHEET MENU SCREEN 27

7 ASHEET ONLINE SCREEN 28

8 BSHEET ONLINE SCREEN 28.

9 ESHEET ONLINE SCREEN 29

10 GENERATION OF PROMPTING DOCUMENTS 36

11 USE OF PROMPTING DOCUMENTS 37

12 DATA-.SHEET STATUS 39

13 ALSAR REPORT MENU SCREEN '41

14 CMRS REPORT SELECTION SCREEN 41 '

15 MODMETRIC TAPE SELECTION SCREEN 43

16 NRLA TAPE SELECTION SCREEN 3 43

17 SAMPLE ACDF DATA INPUT RECORD LAYOUTS 48

18 FUNCTIONAL DISPLAY OF ACDF DATABASE 54

19 ACDF RECORD SELECTION DISPLAY SCREEN 55

LIST OF TABLES

TABLE 1 ALSAR DOCUMENTATION 17

2 ALSAR PERFORMANCE TRACKING' 22,

3 ALSAR OUTPUT REPORTS, 1104 ACDF DOCUMENTATION 47

5 ACDF RECORDS FOR EACH AIRCRAFT MDS 49.,

6 SYSTEM FEATURES RECORD 57

7 AFOTEC SYSTEMS USED s. 60

al

-

2

O

DIRECTIVES

4

SECTION

;BACKGROUND41t

POLICY /

The need for improved weapon system availability, supportability, and

overall cost-effectiveness has been a continuing concern of the Department of

Defense (SOD)., DOD Directive (DODD)-5000.39, "Acquisition and Management of.

Integrated Logistics Support for Systems and Equipment," establishes impor-

tant policy addressing this need. It defines management and technical

activities to be accomplished throughout the weapon system acquisition pro-

cess with emphasis on Integrated Logistics Support (ILS) and Logistics Support

:Analysis. (LSA). Specifically, DODD 5000.39 stresses the need (a) to

,effectively utilize information about existing operational equipment to

establish a BaselineComparison System (BCS), (b) to integrate LSA activity

into the overall system design process, (c) to establish and maintain a common,

consistent Logistics Support Analysis Record (LSAR) used to support both ILS

and Reliability and Maintainability (R&M) development efforts, and (d) to

verify the 'LSAR during operational service of the weapon system.

-

MILITARY STANDARD (MIL-STD) 1388

-Military Standard (MIL-STD) 1388 describes the LSA tasks to be

accomplished during a system acquisition program to satisfy the objectives

of D00155000;39. In'additiOn, MIL- STD - 1388 - defines the.LSAR needed to

document .the results of LSA, In 1973 the AtMy Development and Readiness-,* .

Command (DARCOM) developectethe LSAR Automated Data Processing (ADP) system- -

to implementHMIL-STD13882 'DARCOM Pamphlet 750 -16 (DARCOM, 1979) is the

governing-documenCfor the system.

Lack or.LSA/LSAR standatdization between service acquisition efforts

lird to the fotmation. of a Joint Service LSA WOrking Group in November 1978.

The working group's efforts were speCiTically directed toward standardization

13

of the LSAR input data sheets and data element,definiions. In June 1981,

the working group effort resulted in a draft revision of MIL-STD-1388. In

December 1981, the DARCOM Materiel Readiness Support Activity.(MRSA) was

assigned to DOD LSA Support Activity mission. This mission included the

requirements to develop a MIL-STD on LSA documentation and a standard DOD

LSAR ADP system. As a result, in June 1982, a draft MIL-STD-138872A was

developed. A revised draft (MIL-STD-1388-2A, 1983) was carefully reviewed by

industry representatives, and the approved version is expected to be

published in May 1984.

Concurrent with development of MIL-STD-138 A, MRSA has been develop-

ing-a DOD LSAR ADP system. At present, the concept for this system, written

in American National Standard Institute (ANSI) COBOL, is for batch processing

of input data resulting in sequential master files. The difference between

the DOD LSAR ADP systet and the DARCOM 750-16 ADP system is that the DOD.

system will accept all inputs at a single entry point; relieving the

functional user from having to know which one of the five DARCOM ADP system

programs to use for a given input.

PRODUCT PERFORMANCE FEEDBACK SYSTEM (PPFS)

On 27 September 1979, the Air. Force issued Program Management Directive

'(PMD) L-Y9094(1) directing-the definition and development of a Product

Performance Feedback System (PPFS). The primary objective of the PPFS is to

provide an historical data repository of design-related information about

operational systems for use by system designers, analysts, and support

planners invol,yed in new weapon system and equipment acquisition programs.

The PPFS will be automated to provide convenient and timely access to rele-

vant design, reliability and maintainability (R&M) and support cost data to

establish initially a baseline comparison system (BCS) for the new weapon

system being developed. Once the new weapon system becomes operational, the

PPFS will provide performance data feedback to those responsible for

operation and support (O&S) throughout its life cycle.

14-2-

UNIFIED DATABASE TECHNOLOGY

DEFINITION STUDY

During 1978-1979, the Logistics and Human Factors Division of the Air

Force Human Resources Laboratory (AFHRL) conducted a study to define the

requirements and establish a plan for development of an integrated system

that would assist in satisfying the requirements and objectives stated in

DODD 5000.39. This work by Thomas and Hankins (1979) and Thomas, Hankins

and Newhodse (19.80) resulted in a concept and development approach for the

Unified Database (UDB) system. As conceived, the UDB addressed the require-

ments of DODD 5000.39, MIL-STD-1388, PPFS, and the specific Air Force

requirements associated with ILS throughout the weapon system acquisition

process.

UDB DEVELOPMENT

1

In January 1980 AFHRL began a three-pha ed effort to develop a proto-

type UDB system, with each phase lasting apt: oximately 1 year. The objective

of Phase I was to accomplish detailed definition and system level design

of the UDB. The objective of Phase II was to develop the UDB. The objective

of Phase III was to test and demonstrate the UDB. This UDB development

effort was completed in March 1983. This report provides an overview of the

UDB concept and summarizes the results of the development effort.

SECTIaN'II

UDB CONCEPT

GENERAL

In this section the overall concept of the UDB is presented. It was

necessary to have a global perspective of the UDB concept to insure that

the "building blocks" were deVeloped consistent with the overall objectives.

The UDB development status will be covered in later sections of this report.

PURPOSE

The purpose of the UDB is to assist government and industry organiza-

tions in accomplishing the objectives of DODD 5000.39, MIL-STD:-.1388, current

ILS reporting requirements typically imposed on Air Force acquisition pro-

grams, and PPFS.

OBJECTIVES

The primary objective of the UDB program is to develop an integrated

system that will provide mechanisms (a) to establish and maintain an

historical data repository of relevant information about operational weapon

systems, (b) to enable convenient and timely access to the historical data

repository and provide information in a useful form and content, (c) to

assist in establishing a BCS for use in trade-off studies, analyses, and

predictions about the new weapon system under development, (d) to assist

in developing, managing, and utilizing a common LSAR throughout the acquisi-

tion process, .(e) to provide convenient interfaces between LSAR and standard

analytical models for predictive .and planning purposes, (f) to update the

LSAR with measured values during the Operational Test and Evaluation (OT&E)

phase, (g) to validate the LSAR using operational field data during the O&S

phase, and (h) to utilize the UDB as a means for product performance measure-

ment and feedback.

16

CONCEPTUAL APPROACH

CLOSED-LOOP SYSTEM

In order to satisfy the UDB objectives optimally, a closed-loop system

is needed to insure consistency and compatibility. Figure 1 shows the

closed-loop nature of the UDB in terms of its objectives and the time-phased

activities of the weapon system acquisition process.

Objective 1 - It was concluded early in this program (Thomas et al.,

1980) that the Air Force should establish and maintain a central Historical

Data Repository (HDR) for each major product category such as aircraft,

missiles, and ground electronics. The HDR will contain design, R&M, and

support cost information about operational weapon systems and equipment.

In the future, as weapon systems are developed using the UDB concept, the

'HDR would contain validated LSAR for these systems.

The design data in the HDR, for a given weapon system configuration

would remain constant, while the R&M and support cost data would be

periodically updated using existing field data collection systems such as

Ghe Maintenance Data Collection System (MDCS) Air Force Logistics Command

(AFLC) DO-56 systems, and the Visibility and Management of Operational

Support Cost (VAMOSC) system. If and when modifications to a current weapon

system are made, the design data in the HDR will be changed to reflect the

modification, and the corresponding R&M and support cost data in the HDR may

be correlated to the modified design configuration. In this regard, main-

tenance of the HDR will be relatively difficult until such time that oper-

ational weapon systems populating the HDR are developed using the UDB

concept, and therefore have an active LSAR. (This point will be discussed

later under Objective 4.)

Objective 2 - The automated HDR will process input data, as appropriate,,

to create output information in the form and content desired by users.

Information in the HDR will be stored on disk or on tape, as appropriate.

Regardless of the data storage mechanism, the HDR will provide users

-5-

OBJECTIVE I

HISTORICAL DATA REPOSITORY

CURRENT WEAPON SYSTEMS

SYSTEMS W/VALIDATED LSAR

OBJECTIVE 2CONVENIENT ACCESS, FOR

PRODUCT PERFORMANCE MEASURENEW SYSTEM DEVELOPMENT

OBJECTIVE 8PRODUCT PERFORMANCE MEASUREMENT

AND FEEDBACK(R a M AND COST TRENDS)

FIELD DATACOLLECTION SYSTEMS

DATA ON WEAPONY T M I.SA A 111 A-o

tYsTEms W

OBJECTIVE 3 OBJECTIVE 4 OBJECTIVE 6 OBJECTIVE 78CS FOR LSAR FOR:NEW VERIFY LSAR VALIDATE LSAR

NEW WEAPON WEAPON SYSTEM W/TEST DATA W/FIELD DATA

SYSTEM REQUIREMENTS AND MEASURED MEASURED

DEVELOPMENT PREDICTIONS VALUES VALUES

OBJECTIVE 5

DATAGENERATINGTECHNOLOGY'

f

DESIGN /DEVELOP /PRODUCTION

OBJECTIVE 4' OBJECTIVE .7'UPDATE LSAR VALIDATE LSAR

FOR 'kW/FIELD DATAMODIFICATIONS

N REQUIRE TS AND MEASUREDPREDI IONS VALUES /

,.........

oT8E l EARLY oas I CONTINUING 0 a S

UDB IN WEAPON SYSTEM LIFE 40CLE

FIGURE I

18

7

convenient and timell( access to selected information-via remote on-line

cathode ray tube (CRT) terminals.

In the weapon systet acquisition and support environment, conven!nt

and timely access to relevant data is extremely important. If this

capability is missing, the utility and cost-effectiveness of the MDR is

severely comprotised. There is simply little.value in having an HDR loaded,

with valid and useful information if users 'cannot get it when they need it.

Objective 3 - The cbmmunity of organizations involved with new weapon

system acquisition programs' would use thee HDR to identify the BCS for the

new weapon system under development. The BCS would be either a currently

operational weapon system, or a composite system composed of equipment from

two or more currently operational systems. Once the BCS is identified based

on design characteristics, users would selectively retrieve R&M and support

cost information from the HDR to serve as baseline of departure for the new

weapon system.

The BCS would first be established at the top system level, then at

the major subsystem levels, and finally at the component levels, as appro-

priate. A most convenient and useful feature would be to enable users to

retrieve selected BCS information from the HDR in LSAR format for each

desired level of indenture. Establishing the BCS in LSAR format would

greatly assist the government in establishing system level availability and

R&M requirements. It would be enormously helpful to industry for allocating

system level requirements to major subsystems and lower indenture levels.

Finally, it would greatly reduce the time and cost required to accomplish

trade studies and analyses for obtaining predictions atall levels in the

LSA/LSAR process. In addition to achieving substantial time and cost savings,. .

such a BCS capability would greatly enhance the effectiveness of the ILS

activity throughout the system acquisition process.

Achieving the capability to transfArm field data into comparable LSAR

data, and vice-versa, is the key to creating a truly closed-loop UDB system.

This capability will be totally achieved only if a mechanism is developed

to resolve the basic incompatibilities between field data collection systems

and the LSA/LSAR system. requirements. The UDB achieves this by a set of

transformation tables.

-7-

19

2

S

Objective 4 r When the user retrieves the BCS information on tape from

the an in LSAR form and content, the automated LSA13. (ALSAR) system of the

UDB will enable the user to load the BCS. The BCS would be used, to support

the LSA activity.for the new weapon system development program. the-results

of Air would be recorded in th LSAR for the new weapon system. The

ALSAR will provide a cross -reference,, between the BCSand the new weapon system

LSAR at each level of indenture, as applicable. This feature provides a con-'

venient audit trail for future use`.

Since the detailed LSA/LSAR must be accomplished by industry, the ALSAR

will provide on-line and .batch features to enhance systems engineering',

integration throughout the design, development, And production phases of the

new weapon system acquisition process. The LSA/LSAR would be, accomplished at

the system and major subsystem levels early in the design/development process.

As the preliminary and detailed design is expanded to lower indenture levels,.

the LSA/LSAR expands accordingly.

The ALSAR provides the mechanism to create, manage, and utilize a

common, consistent LSAR database for the new weapon system to thd lowest

reparable level, and for all ILS elements.. The ALSAR will machine generate

standard output reports. that satisfy most, of the'ILS related requirements

associated with new weapon system acquisition programs. This automated,

feature will result in significant cost sivings in report preparation and

will enhance consistency and cost-effectiveness in planning and developing

the required ILS elements. 4W'

It is envisioned that all required, allocated, and predicted values for

the new-weapon system LSAR would be rfecorded in he ALSAR by the end of the

full-scale development phase. To be sure, however, the ALSAR would continue

to be used throughout the production phase to reflect design modifications

and assist in the development of ILS elements. furthermore, the ALSAR would

continue to be msed during OT&E and O&S, but this will be discussed later.

Objective 5 - .Standard models are available to assist in accomplishing

LSA during the design and development of new weapon. systems. The Network

Repair Level Analysis (NREA) Model and the Logistics Composite Model (LCOM)

are examples of these important tools. The UDB `should be designed tb provide

-8-

3.

an interface mechanism between ALSAR and these standard models.

In Figure l'this capability is sho `as Data Generating Technology.

While the current- UDB has addressed this area, there is tremenHOUs potential

for future development to improve and enhance this capability. An important

example is the interface between the HDR and ALSAR with computer-aided

dTsign and computer-aided manufacturing (CAD/CAM).

Objective 6 The ALSAR will provide tha capability to record allocated,

predicted, and measured values for parameters required to d ermine the

operational suitability and effectiveness of the new weapon sys Prior

to OT&E the ALSAR will contain allocated and predicted values for the new

weapon system LSAR. When the weapon system moves intosche OT&E phase,

measured values based on test results may be entered using the on-line or

batch system of the ALSAR.

This ALSAR feature will enable the government and contractors to

compare requirements, allocations, predictions, and measured results in a

consistent and directly comparable manner. To the extent desired and

applicable, comparison with the BCS could also be achieved. This capability

will permit early identification of specific problem areas and permit

problem resolution on a managementLby-exception basis. This process will

permit early verification of LSAR in areas where no problem areas exist.

4611

Objective 7 - During the early O&S phase the existing field data

collection and reporting systems (MDCS,. D056, VAMOSC) will be used to vali-

date the new weapon system LSAR. On the right side of Figure 1, a

dashed-arrow is shown that implies that measured values for validation of

the new weapon system LSAR are provided directly from the Field Data

Collection Systems. Although this is not totally possible due to the

incompatibility between the LSAR and the field d6.ta systems, as was mentited

in the discussion of the BCS under Objective 3 above; the UDB Transformation

Tables make it possible to scope degree.

At the beginning of the new weapon system program a BCS will be created

and loaded into the ALSAR. ,When this new weapon system eventually moves

into the early O&S phase, the UDB Transformation Tables will be used to

21

process the field data collected on the newly fielded weapon system.

Instead of creating a BCS, however, the output at this point will reflect-

measured,valdes for appropriate LSAR parameters of the newly fielded weapon

systenr. When this output is loaded into the ALSAR, the measured values

derived from field data may be*4used to validate the LSAR for the newly fielded

weapon system.

When the newly fielded weapon system LSARis validated, this LSAR

record will be loaded in the HDR r use by future weapon system development

programs. This is shown in Figure' 1 by the arrow leading from the validated:

LSAR (Objective 7) to the block in the HDR titled "Systems with Validated

LSAR." Selected portions of the LSAR may be stored on disk, while other

portions may be stored on magnetic tape. When this newly fielded weapon

system, or any portion thereof, is used as the BCS.for a future'weapon system,

a complete and validated LAR will be available for the BCS. As the HDR is

increasingly populated with weapon systems flit- which a Validated LSAR is

available, the full potential value of the closed-loop UDB system will be

realized.

Objective 8 Another important function of the automated HDR will be to

provide trend data for selected R&M and support cost paraMeters. This is

shown in Figure 1 as product performance measurement and feedback to those

responsible for continuing development (modifications), operation and support

of a weapon system:

Again, the capability to accomplish this function totally will be

dependent on the mechanisms discussed earlier to create the BCS and validate

the LSAR for a new weapon system. As shown in Figure 1, the Field Data

Collection Systems would supply information for currently operational systems; -

both those with and without the LSAR.,:The UDB would process these field data

and calculate and capture trend data as a function of selected LSAR parameters

over time/utilization. These trend data would be available to users via

on-line command and displayed on CRT terminal screens or hard copy printout

as shown by Objective 8 in Figure 1.

he rationale for utilizing the same mechanisms to create the BCS, vali-

date the new weapon system LSAR, and supply trend data for. the new weapon

-10--1'L., 22

system during the O&S phase is straightforward. The R&M and support cost

parameters of interest should and do remain applicable throughout the life

'cycle Of a weapon system. In-the beginning the_baseline values are

established, followed by requirements and allocated values. Next the pre-,'dieted values are established during design, development, and production.

In the OT&E phase, test results produce measured values-to verify the

predictions and identify problem areas. Finally, the field data collected

in the O&S phase supplies measured values to validate the parameters of

interest. These validated parameter values are then stored in the HDR and

used as the,BCS for future weapon system acquisition programs, as appli-

cable. Using the same mechanisms to accomplish these functions is both

practical and necessary to facilitate a consistent, compatible closed-loop

UDB system.

Objective 4' A vitally important concept of the UDB is that the LSAR

for a given weapon system will be maintained throughout its life cycle.

During the design, development, and production phases, the ALSAR captures

design informat.ion as part of the overall LSAR for a nea weapon system. As

the weapon system moves into. OT&E and O&S, ghe measured values are used to

verify and validate the LSAR at a function of its design characteristics,

concept of employMent, and concept of maintenance.

Figure 1 shows thatthose responsible for developing and supporting

a new weapon system would continue to utilize the ALSAR to maintain the

new weapon system LSAR throughout the O&S phase. During OT&E and/or

early O&S, design-related problems may be identified that require modifica-

tions to the weapon system. When this occurs, LSA will be yeaccomplished,

as appropriate, and the LSAR will be updated to reflect the modified design

configuration. Similarly, if and when changes to the operational and/or

maintenance concepts for the weapon system and eminent, the LSALSAR will

be.updated to reflect these changes whether or not design modifications were."

also made.

Objective 7' - After modifications are incorporated in the weapon system,

the ALSAR will again be used in conjunction with the HDR to validate the

4

23

updated LSAR. This step would also be accomplished if only a change to the,

operational and/or maintenance concept was made. Once validated, the mod!-.

fiedLSAR would be stored in the HDR for use on future prograMs'. Trend data

on R&M and support cost parameters would be prov,ided for the modified weapon

system on a continuing basis, as appropriate.

PROTOTYPE UDB APPROACH

Conceptually, the UDB could be used to support many types of DOD

weapon systems and equipment. The UDB development effort was limited to Air

Force requirements for aircraft weapon systems. Figure 2 portrays a total

aircraft. weapon system and how the UDB would be used by the Air Force and°

contractors throughout the acquisition process.

AIRCRAFT

AIRFRAME, ENGINES,

GEAR, FLIGHT CONTROLS,

AVIONICS, ELECTRICAL,

HYDRAULIC, ARMAMENT,

CREW STATION, ETC.

SP ARE PARTS

PROVISIONS

TRAINING TRAINING

EQUIPMENT PROGRAMS

TECHNICAL AIR CREWS

DATA GROUND CREWS

'PACKAGING/

TRANSPORTATION

iv.BILITY AND MAINTAINABILITY

RTABILITY AND AVAILABILITY

LI (PRIMARY SYSTEM) (SUPPORT SYSTEM)

UNIFIED DATABASE TECHNOLOGY

PROVIDES HISTORICAL DATA/BASELINE COMPARISON

"s ASSISTS INTEGRATION OF DESIGN/SUPPORT/ILS

USED BY AF/CONTRACTORS THROUGHOUT ACQUISITION PROCESS

SINGLE/CONSISTENT RECORD FOR R&M AND LOGISTICS ELEMENTS

PROVIDES PRODUCT PERFORMANCE MEASURE/FEEDBACK

IDEVELOPMENT I PRODUCTION I .01-1(E OgS

WEAPON SYSTEM ACQUISITION PROCESS

TOTAL AIRCRAFT WEAPON SYSTEM

FIGURE 2

- 12_24

;.INITIAL PLAN

As dis,gs4.,ssed earlier, the ALSAR and HDR are.the mostimportant features

of the closed-loop UDB concept: Given'these features, the data generating

technology would then be extremely useful in accomplishing.LSA. The initial

plan for the 11,9A effort waso focus primary attention on .the HDR and data

generating technology, and to use the DARCOM ADP/LSAR system to satisfy the

requirements of ALSAR. A detailed study of the DARCOM system, holliever,

revealed that it could not accommodate the UDB objectives for'the ALSAR.

Becau e the ALSAR is vitally important to the viability and utility of the

overall UDB, primary emphasis was shifted to development of this fully auto-

mated LSAR system, with secondary emphasis on the HDR.

. UDB FEATURES

Figure 3 shows in bold-lined.boxes the two major features of the

UDB system; the ALSARand the Aircraft Characteristics Data File (ACDF).

.These features were developed so as to be consistent and compatible with the

UDB system objectives discussed earlier in Figure 1 and shown in Figure 3.

A discussion follows as to the degree to which these objectives were satis-

fied in the UDB development effort.

Objective 1 - The ACDF represents the HDR for currently operational air-

craft weapon systems. For each mission, design, and series (MDS), the ACDF

will contain design characteristics data and processed field data pertaining

to utilization, R&M, and support cost parameters. Initial programs have

been developed to process data from D056E and VAMOSt,to update the ACDF.

Objective 2 - The automated ACDF provides convenient and selective

access .to data via remote on-line CRT terminal screens. This capability will

assist users in determining the BCS for a new weapon system and selectively

retriejing BCS'information. Using the same capability, users may retrieve

information from the ACDF to assist in determining the performance of

.productsrin terms of R&M and support cost parameters.

-13- 25

OBJECTIVE I

OBJECTIVE 2CONVENIENT AUTOMATEDACCESS TO ACDF DATA

TO.

IDENTIFY BCS ANDRETRIEVE BCS DATA

DETERMINE PRODUCTPERFORMANCE

MANUALLY

ESTABLISH

BCS RECORD

AIRCRAFT' CHARACTERISTICS

DATA FILE (ACDF)

FOR CURRENTLY OPERATIONALAIRCRAFT WEAPON SYSTEMS

I DATA

\

UTILIZATION RamAND SUPPORT COST. DATA

OBJECTIVE 8

-ACDFUPDATEPIT ER FACE

4

,..s.I CONVENIENT AUTOMATED ACCESS , .

-`,.... TO TRACK PRODUCT PERFORMANCE USING....._ ACDF DATA . (NO R SPA AND COST

- TREND DATA AVAILABLE. NO,

\--4-- OBJECTIVe"3 *----.. AUTOMATE15' OUTPUT FOR. '''',LSAR MEASURED VALUES)

BCS/LSAR 1,, --.......\ OUTPUT NOTI

\ AUTOMATED 1.o

FIELD DATACOLLECTION SYSTEMS

D056E a. VAMOSC

N: NO PROVISION TO\ LOAD VALIDATED

LSAR DATA

IN ACDF

\I41 I OBJECTIVE 4 I OBJECTIVE 8 I OBJECTIVE 7

AUTOMATED LSAR SYSTEM (ALSAR)

CAPABILITYTO. LOAD AND

UTILIZEBCS/LSAR

CAPABILITY TO ESTABLISH,. MANAGE, UTILIZE LSAR

DATABASE DURING DESIGNDEVELOPMENT, PRODUCTION

CAPABILITY TOVERIFY LSAR

WITH MEASUREDVALUES DURING OT B E

CAPABILITY TO

UPDATE /VALIDATELSAR DURING .

0 B S PHASE '

OBJECTIVE 5INTERFACEFOR USING

STANDARD

MODELS

PROTOTYPE UDB FEATURESFIGURE 3

9R

Objective.3 - The transformation tables necessary' to relate field data

toLSAR terms have been developed. As discussedearlie,- this is a:very

important and needed 'Capability; first, to permit.. establishment of.a BCS/LSAR,

and second, ,to permit validation of. the new weapon systenl LSAR using existing,

field data collection systems-,. Development of this capability should be

accomplished, in future UDR eff.Orts..

Users must manually create.a.BCS record using data elements and values

currcntkr retrievable from the ,ACDF.. Using the BCS data retrieved from the

ACDF, users may utilize the field o-LSAR transform4tion tables for con-

structing maqually:BCS:data that could:be loaded in ALSAR,..

Objectives'4 -7.:= The ALSAR system has' een fully developed to Satisfy

Air Force:requirements. A BCS may be loaded into the ALSAR and cross-

refeencea'to the new weapOtr.system,LSAR. .The system is ,fully automated to

assfStin systems engineering` integration' and to create,. manage, and.

utilize.a common, consistent record for all ILS elements; ALSAR.programs*

are available to ceate.outputs from the LSAR that may be batchlOnciA ed as

input to standard.logistics modpls. The ALSAR has-an extensive outputo .

Summary report papabiiity.in'aCcordance with standard Data Item Descripti6nS

(DID) typically;, required in,Air.Force programs. . /-

The2ALSAR has provisions' for recording.fileaSuredvalbes.Afor R&M

meter's toThe tested dUring OT&B THiSprovisiOn'may also be used

toentMeaSureciaiueS:iolialirdate the LSAR the:O&SphaSe.. As

discussed:Under Objectivliowever,:the ACDF, capability to.prOcess:field

data..So astip machine output the requIred LSAR measured' values hAS not yet

been..deyeloped.!:

Objective 8 The same ACDF programs used for0b:jeptiv.2 may Used'

to track the continuing performance of operat-i-enalWeapon systemS.,The.

ACDF presents_ average values_for numerous R&M,:andsupport.cost paraMeteis.-

'NO trend data' capability is ptovided in the prototype. ACDF, but it is

expected that futuresUDB:effots will address this need.

-15- 27

SECTION III

AUTOMATED LSAR SYSTEM

OVERVIEW

As dikcussed in the previous sections, the ALSAR is a vitally important

part of the UDB'. 'Specifically, the ALSAR is needed to satisfy, Objectives 3,

4, 6, and 7 shown in Figure 1 and discussed in Section II. The ALSAR system

discussed in this section has been fully-developed and partially tested,

using HH-60 helicopter data. Since December 1982, the system has been

successfully used in a production mode to support the Defensive Avionics

portion Of rhe B-1B Strategic Bomber Program. As this program progresses,

the ALSAR system features will be fully validated for operational use on

-6-other programs.

BASELINE1

The DARCOMP 750-16 data elements, data definitions, and data sheets/

records were used as the baseline for the ALSAR system. To the extent

practical, consistent with Air Force requirements, compatibility with the

DARCOM baseline was maintained. Substantive additions to the.baseline were

necessary, however, in order to develop a fully automated system that would

satisfy Air Force and DOD requirements, and provide many useful and cost-

saving features for,industry-and Government users. Since the ALSAR is a

fully automated database system, none of the DARCOM ADP/LSAR software or

programs are used:

DOCUMENTATION,

The ALSAR system has been fully documented and delivered to the Air

Force. In Table 1 the individuaqe docuMents associated with the ALSAR are

listed.

rr

.1.. -167

28

TABLE 1. ALSAR DOCUMENTATION

Document

Data Sheets

Data Element Descriptions

Data Entry Instructions

ALSAR Users Guide

Access and'Secu-pityManual-.

Maintenance and UpdateManual

Software Documentation

Purpose

- Dqta input sheets used by ALSAR

For data elem9ts oneach data0

sheet.

For entering information abouteach data element on,each datasheet

For using each feature Qf theautomated system

On-line procedures to controldatabase security

Instructions for ADP mainterQanceand update

Complete programming documen-tation for ALSAR system

Data Sheets.

The ALSAR input data sheets A through J are listed in Figure 4 and in-

cluded in Appendix A. Figure 4 is actually a CRT menu screen of the on -line.

ALSAR system. These data sheets contain all of the data elements in the

ALSAR system. The on-line CRT screens used to Input data are designed in a

manner consistent with the card record layouts on each sheet. A data sheet

status output report may be machine produced, on command, in the format and

content tical to each input data sheet.

In A T ix A the reader will notice that the basic 80-Column card

format is use

requirement t loped so as to retain consistency with the

DARCOM ADP/LSA possible. Since the DARCOM 'system is

basically a sequential e ba ch processing scheme, it requires the -4

80-column card format along ith duplic. ion of key information on ea

card. The fully automated AR system would permit core simplified,

to sheets.

h- ta sheets. This was the result of an Air Force

efficient, and user friendly For example, Data Sheet A

1 DPR LSAOM -01, MENU SCREEN 1, AFHOID, AFM0111XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXRXXXXXXXXXXXXXXXXXXXX AS OF XXXXXXX XX/XX/XX

MENU 1

SHEET

A OPERATIONS AND MAINTENANCE REQUIREMENTSa ITEM RELIABILITY(R) AND MAINTAINABILITY(M) CHARACTERISTICS

TASK ANALYSIS SUMMARYD MAINTENANCE AND OPERATOR TASK ANALYSIS

E SUPPORT AND TEST EQUIPMENT OR TRAINING MATERIALDESCRIPTION AND JUSTIFICATION

F FACILITY DESCRIPTION AND JUSTIFICATIONSKILL EVALUATION AND JUSTIFICATION

H SUPPLY SUPPORT REQUIREMENTS

1 AUTOMATIC TESTING EQUIPMENT/TEST PROGRAM SET DESCRIPTIONTRANSPORTABILITY ENGINEERING CHARACTERISTICS

-

Tg,A

LIST OF REPORT REQUESTS TYPE RPTMENU

DATA SHEET MENU SCREEN

FIGURE 4

could be changed to display the Logistics Support Analysis COntrol Number

(LSACN) only once, rather than di playing it on each card. In future UDB .

development efforts, consider'ation will be given to designing the data

sheets in a manner consistent with the fully automated ALSAR system.

Initial user reaction to the ALSAR data sheets may be negative because

of the redundant key data elements appearing on all sheets and the data

elements added to the A, B, E, and H Sheets appear to increase the user

workload. In fact, the fully automated ALSAR system eliminates the need

for.users to enter redundant data. The new data elements added to the data

sheets enable the ALSAR to satisfy multiple Air Force and DOD requirements

and to facilitate automated output i'eporting that will result in significant

time and cost savings.

Data Entty Instructions

All of the data elements on the ALSAR data sheets are defined in the

i Data Element DeScriptions (DED) document. The Data Entry Instructions (DEI)

30

document tells the user how to fill out each data sheet. Since the ALSAR is

fully automated for on-line data entry and update, it is not mandatory that

users manually fill out data sheets.. In any case, users should be thoroughly

familiar with, the ALSAR procedures and conventions regarding data entry in

order to capitalize on the many useful and time-saving featUres of the fully

automated system.

ALSAR Users Guide

While the DEI instructs the user in how and where to enter the results

of the LSA on each data sheet, this guide describes the on-line and batch

functions of the ALSAR system and provides instruction for operation and

use of the on-line system. This includes procedures for retrieving CRT

terminal screens to enter, update, and display information in the database

relating to any data sheet and also for requesting hard copy or tape output

summary products and reports available from the ALSAR system.

Access and Security Manual-

This document provides instructions for establishing and controlling

the ALSAR database accessibility and security. While this on-line feature

is easy to use, it provides great-flexibility in controlling the access and

update capability of functional area users.

Maintena ce and U ate Manual

This cument providesiinformation of interest only to computer center

personnel responsible for the maintenance and update of the ALSAR systeti,

This document, alonith- the complete software documentatiOn package, should

be sufficient to permit installation, operation, And maintenance of the AL.SAR

at a computer facility that has compatible hardware and system software.

SYSTEM DESIGN

Figure 5 shows the basic design approach for the fully automated ALSAR

system.- Notice that the ALSAR utilizes the Integrated Database Management

-19- 31

_\

System (IDMS) developed by Cullinet Corporation. The IDMS components used

a are the Integrated Data Dictionary, data Dictionary Reporter, On-Line Query,

Data Communications Monitor, and Database Manager. Clemson University

developed a general purpose software package for creating CRT terminal

screens and performing full screen edits. This package is with the

ALSAR.

All. on -line application programs are designed to run with the IDMS Data

Communications Monitor, an efficient and multi-tasking communications monitor.

This enables excellent responseifor larger multi-terminal real-time systems

and also provides for automatic journaling of alrtransactions.s

IDMS

'e Integrated Data DictionaryData Dictionary ReporterOn-Line QueryData Communications MOnitorDatabase Manager

GENERAL PURPOSESOFTWARE

Screen MappingFull Screen Editing

APPLICATION PROGRAMS

On-Line FeaturesBatch FeaturesANSI-COBOL with

embedded IDMSverbs

ALSAR SYSTEM DESIGN

FIGURE 5\,,

There are approximately 300 application programs written to accompli h

the on-line and batch functions of the ALSAR. They are written in ANSI CO OL

with embedded IDMS verbs. Each program was designed with functional

modularity in order to allow for ease of maintenance and adaptation to new .(

environments. The application system ccitains a complete security subsystem.6.

that can be used to control access to and modification of data by users.

This security feature also'provides a complete audit trail of changes made

-20-

during op-line operations:

GENERAL FEATURES

There are several important features of the ALSAR that relate to the

overall LSA process and specific DOD requirements.

LSA CONTROL NUMBER (LSACN)

The LSACN is a key data element in the ALSAR system and is comprised of

the Work Unit Code,(WUC) and the Work Breakdown Structure (WBS). This

hpproach accomplishes several important objectives addressed in DODD 50a()%39

and MIL-STD-1388.(-1tj.rst, it permits convenient and effective management of a

commonconsiatent database of information necessary to support all ILS.,

elements. Second, it provides an effective mechanism to relate field data to

LSAR data during the O&S phase, thus facilitating Validation of the LSAR for

a weapon system. Third, it provides an inherent cross-reference between WUC

and WBS for correlation of support costs.to acquisition costs.

The ALSAR does not depend upon the LSACN to generate provisioning

technical doCumentation, as does the DARCOM system. The manner in which

ALSAR accomplishes automatic generation of provisioning documentation is

discussed later. Since this approach is used, the ALSAR assigns LSACNs only

to the lowest reparable level of the end item. Assignment of LSACNs to

nonreparable items is not required.

PERFORMANCE TRACKING

The Air Force typically requires that"the performance of specified

parameters be verified in OT&E and tracked during O&S. In order to achieve

the objectives of the MB, specifically Objectives 6 and 7 in Figure 1 'Which

address this Air Force requirement, several features were incorporated into

the ALSAR system.

Additional Data Elements

Numerous data elements were added to the A and B Data Sheets, as shown

in Table 2. With these additional data elements the required or allocated,

33

TABLE 2. ALSAR PERFORMANCE TRACKING

I. PERFORMANCE PARAMETER VALUES

REQUIRED /ALLOCATED VALUE PREDICTED VALUE MEASURED VALUE

SYSTEM LEVEE. ONLY

MISSION COMPLETION SUCCESS PROBABILITY

AVAILABILITY:PlC, PMC/M, PM/S. PMC/MiSAMC, NMC/M. NMC/S. NMC/MISFMC, WPT/SORTIE

BASE LEVEL 1465 /PH: BOTH ORGANIZATIONAL LEVEL AND INTERMEDIATE LEVEL

SUPPORT GENERALSCHEDULED AND SPECIAL INSPECTIONS (03 4 04)

PREVENTIVE MAINTENANCE.CORRECTIVE MAINTENANCETOTAL BASE LEVEL MW /RU

BASE LEVEL: ROTH ORGANIZATIONAL LEVEL AND INTIERKEDLITE LEVELMEAN MAINTENANCE M/H TO REPAIR (MNHIR)16Uff1024 ELAPSED TIME TO REPAIR

DEPOT MMI/PH:PROGRAMMED DEPOT MAINTENANCECOMPONENT REPAIR /OVERHAUL

MISSION RECONFIGURATION TIME:MEAN ELAPSED TIME90th PERCENTILEMEAN CREW SIZE

ANALYTICAL CONDITION INSPECTIONMEAN ELAPSED TIMEMEAN MA HOURS

QUICK TURNAROUND TINEELAPSED TIMEMAINTENANCE MAN-MENITTESCREW SIZEAIRCREW MAN-MINUTES

FAULT DETECTION/ISOLATIEN AND FALSE FAULT INDICATION

RELIABILITY:MEAN TINE BETWEEN REMOVALS (MTAR)MEAN TIME Born= CORRECTIVE MAINTENANCE (tawINHERENT MALFUNCTIONS (TYPE 1 MI3)0INDUCED MALTUNCTIONS (TYPE 2 wooNO DEFECT (TYPE 6 MIEN)PREVENTIVE (SOTEODIEM REMOVALS) (MIEN)MEAN TIME BETWEEN MAINTENANCE ACTIONS (MENA)RATIO OP. MAINTENANCE ACTIONS TO wainimmicE EVENTSMEAN TIME TO REPAIR

TI. COST TARO= VALUES

I.ESTIMATED ACTUAL

SYSTEM LEVEL ONLY

ESTIMATED AND ACTUAL UNIT (VLTAVA!) COST - ROTH RECURRING

4 NON -RECUIMG

ESTIMATED AND ACTUAL ANNUAL

INITIAL SUPPORT =tram= COST' ROTH C01PECULIAR S.E.

SPARES COST- BOTH INITIAL AND REPLIENISEMENT SPARES

BASE MATERIAL COST/Tit

BASE POL COST/TR

TECHNICAL PUBLICATIONS COST A QUANTITY

TRAINING COST - PERSONNEL 4 MATERIAL/EQUIPMENT

NUMBER OP PEOPLE MINED infEW SKILLS REQUIRED

FIDGRAirfED DEPOT MAINTENANCE cosTrn

COMPONENT REPAIR/OVERHAUL DEPOT COST/YR

INITIAL DEPOT SUPPORT EQUIPMENT COST

FACILITIES COST - BOTH FOR BASE LEVEL 4 DEPOT LEVEL9

BOTH AT RASE i DEPOTLEVELS

SUBSYSTEM L COMPONENT LEVELS

PAUL; DETECTION /ISOLATION AND FALSE FAULT INDICATION

RELIABILITY:MEAN TIME BETWEEN REMOVALS (NM)MEAN TIME BETWEEN CORRECTIVE rum (polo0INHERENT MALFUNCTIONS (TYPE 1 MEM)INDUCED MALFUNCTIONS (TYPE 2 MEM)M3 DEFECT (TYPE 6 HERMPREVENTIVE (SCHEDULED REMOVALS) HERMMEAN TIME BETWEEN MAINTENANCE ACTIONS (MINA).*

_RATIO OP MAINTENANCE ACTIONS TO MAINTENANCE EVENTSMEAN TIME ID REPAIR

BASE LEVEL /1111/71 - ROTH ORGANIZATIONAL (ON-EQUIP) ANDINTERMEDIATE (OFF- EQUIP) LEVELS

PREVENTIVE MAINTENANCECORRECTIVE MAINTENANCE

'TOTAL BASE LEVEL. MMH/711

BASE LEVEL MEAN.MINATENXCEPREVENTIVECORRECTIVE

DEPOT LEVEL M111 /FU AND MEAN TIME TO REPAIR (MIR)

WORK UNIT CODE BY TASK CODE: (TASK SUMMARY)TASE FREQUENCYEASE TIM (ELAPSED)TASK MANHOURSNO. OF HEN/TASK

I t ACTUAL

SUSSYSPQ1 i COMPONENT LEVELS

RCS SUPPORT COST AMP

NEW SYSTEM SUPPORT T DATA PROVIDED/UPDATED IN ACDF

r

.-22- 34

predicted, and measured values of performance parameters may be recorded and

tracked throughout the life cycle of a system. These parameters may bef1

measured at the system, major subsystem, and component levels if desired.

At the system level, data elements were also added to the A Sheet to

capture predicted and measured values of selected cost parameters. The

predicted values would be entered early in the development phase, and the

measured values during the production phase. This information would be

valuable.in the future for establishing cost estimating relationships and

improving predictions on future weapon system programs. At the subsystem and

component levels, the UDB will use the ACDF to capture selected VAMOSC data

to track cost parameters for a weapon system.

Task Codes

The,ALSAR uses the following approach to assign maintenance task codes

Jar Air Force applications. The fifth and eighth positions of the Task Code

use unique task identifiers, as applicable, to facilitate comparability

between LSAR and field data sygtems.. All other positions of the Task Code

are assigned in accordance with MIL-STD-1388-2A. The manner in which ALSAR

utilizes the WUC and Task Code is crucial to verifying the LSAR for a

weapon system after. fielding.

How Malfunction Codes and Work Center

The ALSAR D Sheetrincorporates a How Malfunctioned (How Mal) code

for-further relating the LSAR data to field data.. The ALSAR also uses an

automated scheme to relate the Skill Specialty Code (SSC) primarily respon-

sible for a task to a performing work center, thus providing another

necessary link for comparing LSAk data to field data.

Maintenance Events/Maintenance Actions

There are other features incorporated in the ALSAR system to bridge the

inherent gap between LSAR and field 'data. For example, the procedures for

documenting maintenance requirements on the B Sheet result in automatic

identification of maintenance actions that comprise a maintenance event. All

-23- 35

of the abOve features, plbs some provided but not mentioned here, areineeded

to effectively utilize field data to update and verify the LSAR, thus making

the ALSAR a useful tool throughout the life cycle of a weapon system.

ALTERNATE ACTION

Each ALSAR data sheet has a data field to record an Alternate Action

Code (A, B, C, etc.). When an LSA/LSAR is accomplished for multiple design

concepts, the Alternate Action Code is used to partition the data for each

separate concept. The provision is useful in trade-off studies and provides

a permanent record, if desired, for candidate approaches considered. Since

the Alternate Acy.on Code is a key parameter, the alternate' chosen as the

final design is designated as Alternate Action A. In this way the primary

' LSA/LSAR record for an entire end item will be partitioned under a single

Alternate Action Code. Alternate Action Code is used to designate the

BCS for the new weapon system within the UDB, thereby providing .a fully

automated BCS' conveniently cross-referenced to the new weapon system LSA/LSAR.

LSAR REVISIONS

The specific LSA/LSAR requirements of any given program Will determine

the extent to which the ALSAR data sheets are completed. For each card on

each data sheet required by a given acquisition program, users may determine

the specific data elements that must be filled in to constitute a completed

card. Some programs may require All data elements on a given card, while

others may require only a portion of the card to be filled in. The point

is that only the user on a given program will know what constitutes a com-

pleted card and data sheet.

The Update Code (UC) in the right-hand column of each card'(see Appendix

A) will be used to indicate whether the card is in-work or completed. When

the user changes the card status to "completed," the ALSAR will automatically

record and track subsequent revisions using the UC and date. The same is

true for a completed data sheet. This provides an automated capability to

assist ILS Managers in monitoring the progress of LSA/LSAR activity in terms

of initial completion status, as well as the revisions made to completed

247-

36

.tt

of'

work. From an historical perspective, this capability will provide an LSAR

audit trail that may be used throughout the life cycle of a weapon system.

This may be particularly useful when tracking the performance of key para-

meters, since it will provide a date benchmark corresponding to equipment

modifications during 0 &S.

'EFFICIENT DATA ENTRY

As mentioned earlier, the ALSAR data sheets were patterned qfter the

DARCOMP 750-16 formats. As a result, there is significant redundaacy'of'key

data elements on most of the data sheets. The fully automated .ALSAR has been

designed to eliminate the requirement for the user to enter redundant data.

Some of the automated features incorporated to save user time and effort are

discussed below.

Key Parameters

The ALSAR database is structured to utilize key parameters such as .the

LSACN, Alternate Action, and Manufacturers Part Number (MPN). While it is

necessary to specify key parameters when using the on-line system, the

.machine will automatically enter these specified'parameter values on multiple

cards, 'as appropriate. For example, it is not necessary to enter the LSACN

on each card of the A, B, C, Dl, E, F, and G Sheets.

Header Information

The first three cards of the A, B, and C Sheets contain identical'

header information. When an A Sheet is completed for the system, and major

subs)4tem levels, the ALSAR will automatically enter the B Sheet header

information. Similarly, when a B Sheet is completed for component levels,

the C Sheet header information will._ automatically be entered.

When information describing a part is entered on the B, C, or Dl Sheet,

the ALSAR will automatically enter selected parts information in the Supply

Support (H Sheet) record or the Support/Test Equipment (E Sheet) record, as

appropriate. This provision not only saves data entry time, but insures

consistency between the maintenance, supply support, and support equipment

records.

Multiple Applications

The first time a Line Replaceable Unit (LRU), Shop Replaceable Unit-

(SRU), or repair part 'is recorded in the maintenance record (B, C, or DI

Sheet), a basic Supply Support record (H01, H02 and H03 cards) will be

established for that part. This basic record will not be repeated even

though a part may be used in multiple applications in an end item. For each

individual application of the part, only the application significant informa

tion must be entered. The ALSAR system transfers available information to

the basic record the first time a part is identified, and prompts the user

to Complete the hasic.and applicadon significant information. For- sub,:

sequent.applications of that part; the ALSAR system notifies the user that

only application significant information is needed, and automatically ,

i.,t;Fr

aggregates-relevant provisioning'information for the part.

The same process is used for support and test equipment on the E Sheet.

The first time a particular piece of _equipment is required tO'support a

maintenance task,,,, the machihe will, transfer the available information and

prompt the user to complete a basic E.Sheet. When subsequent maintenance

tasks require this piece of equipment, the ALSAR will automatically record'

,these requirements by maintenance task and^the item being Supported. In a

similar manner the.ALSAR permits a basic record for each ,Facility (F Sheet)

and Skill (G.Sheet)'; and automatically records each individual requirement

for this logistics resource.

NARRATIVE DATA

The narrative cards. on the ALSAR data sheets incorporate a card.letter

and sequence line number ,(Seq. No.) provision that. enables virtually/. '-

Unlimited space for narrative 'information. This provision will enable`ILS

Managers to further integrate and support the effOrt8 of.those respons'ible'.

for technical manuals through the ALSAR. The proVision is required to:enable

the ALSAR to produce important output reports such as the Support Equipment

Recommendations DocumenC(SERD).

. 38

ON-LINE PROCESSING

The ALSAR system utilizes on-line CRT terminal.;screens to enter, re-

trieve, and update information in the LSAR,databAs.e.' In addition, all of the

output products available from ALSAR maybe requested usinz the on-line

system. The ALSAR Users Guide shown in Table 1 provides the detailed infor-

mation for operation of the on-line system.

MENU SCREENS

:Thirteen Menu screens are provided for those getting a quainted- with

the system. Figure 4'is the menu screen thaC.shoWs all of the ALSAR data

sheets. Placing an X by one of the data sheef*Will,causethe menu for that

sheet to be displayed.. For example, placing an X by the-Sheet will display

the A-Sheet menu screen as shown in Figure 6. All of thecard records on-the

A -Sheet are shown in' igure 6, and to display a screen for a particular card

record, the user would..simply place an Xby the desired card.

A -

ALL di;t14414ps atquIg

commini

ALT -ACT

A02

AO3A

A032

.A04

A05

,

AO6

3

A07 A138

Al4A08 _

A09 A15-

A10

All

Al2

Al3A

'THE:COMkAWAFTER EACH OF THESE HAY BE

A16

A17

A18

A19

U - UPDATE F -'FORCE

0

A-SHEET, MENU SCREEN

FIGURE 6

-27-

DATA ENTRY SCREENS

.

There are 70 on-Tine screens to enter, retrieve,' and. update information

in the database. Each. screen consists of data elements:f0 one or more card'

records on one of theedata sheets, in Appendix A. Figures 7.add, are repre-.

sentative.examples'of these on-line: ScreenS. Tig6te-T:is the',Screen for the

A05 and A06 cards.ofthe' A-Sheet, and Figure 8 is for the.A101,802,-and-.

BO3A cards of the 37Sheet. Each on -line screen may be called by: simply;"

entering a command.for the desired card along, with the reqUired

DPR LSA011..01. DATA SHEET A. ORO LEVEL /ON -EQUIP MINT. AFA030. AFAO3UAS OF ADCCCOODC XX/XX/XXI

CARD. A05 LUCASUET INS?,PRIM INST:POSTOP INSIA

'r,4 '.4.010MI STATION

INTERN INS?,

CA.ADI A06 LSACHPERIODIC IttSP MEAN ELAPSED TI1E(16) NUN MAN HRA(2I),, .

UNSCHEDULED KURT MEIN ELAPSED TIMOR) MEAN MAN 0AS(I1).:::::

TURNAROUND MEAN ELAPSED TIME(36) ::::: MLA MAN HRS(41) .1,

HUSTON PROFILE CHANGE MEAN ELAPSED.TINI(40,1, MAN MAN .HAA(51 ...-.. .

--..

)00000000COE NUMBER STS SUPPORTED(I6)

KEAN MUSED TIME(22) MEAN MN mRS(27)

LEAN ELLPSEDTIME(32) MEAN MAN HWY?)

MEAN ELAPSED TIME(42) 1 MEAN MAN HR (47)

KEAN ELAPSED TIME(52) MEAN IAN HRS(57)

MEAN ELL.PSEDJIMI(62) 'IMP( NAN NES(67)EffiglE(89)

KEXXXXIDCOCI

M/H PER HOUR SCHEDULED :(06) 7-- UNSCHEOULED(61

MGR= MAINZ M/H SCHEDULED (66) UNSCHEDULED(72)'t U.IPDATE(iar7i

it A-SHEET ON-LIVE SG:EEN

FIGURE 7

)2000ODOZOS END ITEM ACRONIN CODE(4) '

CODE(26) ALT ACTIONO2

ATUS(34) DWG cusinIT,ElT, nolioe) -75(44) ''A

okycsat .

DilIATE(60)

ITIN NAHR(16) '

/II, TTPX(75) MODEL(42) SERiES(S2)

54) CONVERSION FLETOR(61- OPOUT(60)

'CARD, 50 L.S101 ZODOCCIMOZ Mt PART NUN(16) ,* . LANC(12)

.

FSCNO3) DUO NUMBER(30) LANC(54) F3CM(55),, ......-.. ,UTDATIMATT-

:...

..

-

.7'5031 LUCA )0000000002 NPR PART NOI(16).

DWG NUN(7S)

B-SHEET 'ON-LINE SCREE13

FIGURE-8

ST COPY AVAILABLE

Fo*.ex4101e., .e'nteing the E012.'command, ng with t.1-4e4Sired,A;SACNnd

AlternateyAction will retrieve the screen shown in Kigur'9..;,this screen

6147.3171-ol, DATA POST E. STE OR TANG MATERIAL OESC AND JUST - AFE01D.4/201U1AS or rocoocorzlocirofnoci

'ALTORtarl Lauri

CARD, 101 LUCA XECOCOCCETE END ITEM ACRONYM CODE(161SERVICE DES CODE(261 FSCE(27) ALT ACTION(32) X REV C0131(33$ 15:-

DATA SHIRT STATUS(14)- DWG CLASiTITTSERIAL NUMBER UP, FROM(36) TO(48)DATE, TlAximommioATrser TEST SIT LSICN(64

CARD, 102 LSACA }COCO:MCGEE ITEM AM(1O)ITEM DES CODE, TTPI(35) MODEL(421 SERIES(S2)SUFFIX 0E5(54) CONVERSION FACTOR(61 CALIA ToutpranfTAs)CAIT SUPPORT EQUIPMENT(66) CIT/GPE(67) :TEM mo(66) wormed)

CARD, 101A LSACN )0000000o= MFR PART Norm)F5CA(13) DWG NUM:M(181CONTRACT aiiiiR(60)

CARD. 1030 LSACN MOOMOCCOI rum PART NUM(16)JAG :NM(30)

.ARC(32)LANC(54) F5G1(SS)

UPDATE-Tin- -.

VPDATE(80)

E-SHEET ON-LINE SCREEN

FIGURE 9,,

Jes

.also contains the E02, E03A, and E03B cards. When the screen is retrieved,

dic:.t8ACN is machine entered in each card, as indicated by the 'X's in the,

LSACNjields.'

'Thepumbers in parentheses af,te4.*.eaWdata elemeint denOrYte the column

number, of the':first positiqn for, 4"data element field. This feature will

reduce eriorsit'ahen_data,:a.being entered from hard-copy worksheets. The.

screen cursor is progrlimMe4 to move automatically to the next, unfilled44, -

data field-to"simp.lify'andeipedite data entry.

,.ENTERING DATA

Oncela.sCreen has been displayed, the user May complete all or part

of the'd4ta'ejements, nS desired. Changes or corrections may be made on the

screen prier .to'llitting the "ENTER" key on the terminal. The "ENTERTkey

records thescreendisplay on the ALSAR database, assuming data have been

(

entered b)i;,the. user.

EDIT CHECkS.

The on-line gSrstem incorporates edit checks for selected data elements.

BEST COP' AVAILABLE 41

4

The edits performed on each "screen are'described in the ALSAR Users Guide,

and generally consist 'of checks fOr_required presence, alphanumeric

characters, field size, special codes-, and format. When the user attempts

to enter data that.do not pass an-edit check,. the CRT terminal screen will

indicate the error by flashing the affected data element field. and will not

allow any of the data on the screen to be entered in the database. At this1

point the user has two options. First, the user may correct the errant

data on the screen and then enter them in the database. Alternately, the

user may force the errant data to.be entered_in the database:. This is

accomplished by using the Force '(F) command and then pushing the "ENTER"

key. The F command would be used when it is not convenient or possible to

determinethe cause of .an error immediate*, and the majority of the data

on the screen are correct.

DATA RETRIEVAL

When inforfration has been entered on the database, such data ma)%

retrieved Old displayed by simply calling the screen for the card, with

appropriate parameters, on which the data were enteried When errant data

were forced, the ALSAR system will display the,:kranel:data field with a

series of question marks (???), whether retTleX7ed.oriline or on har -copy

, printout.

DATA UPDATE

Except-for key parameters which are protected lields, any informa-

tionin the ALSAR database maybe updated at the discretion of a user.

After'the appropriate on-line screen containing the information of interest

is retrieved, the UPDATE (U) command would be used to.i'dti4ate this mode.

At this point the user may make any desired modifications or deletions by

§imply typing over the existing data and entering the updated information

in the database.

When an Update is accomplished on, a card previously coded "COMPLETE"

in the Update Code (UC), the ALSAR will automatically reco,rd the update as

a modification'to the LSAR. The purpose and value of this feature-was

-30- 42

discussed earlier.

':,GLOBAL CHANGE CAPABILITY

At times it y.be.lecessary,.to change key parameter values ,(LSACN,_

MPN, etc.) ..,prevous y entered in the database. While such changes are not

possible using the UPDATE command, batch programs are provided to accomplish

changes in a global manner. For example, if an LSACN requires a change,

this program will replace the old LSACN with the new LSACN at every appro-

priate location throughout the database.

GENERIC,POPY CAPABILITY

When an LSA hasp 3e4h'accomplished on an item and the LSAR entered in

the database, the user may find that all or part of this information may

-4- be applicable to,another item for which; LSA /LSAR is required. The ALSAR

system will., on user command, selectively copy all or part of the database

record for one LSACN to another LSACN, whether it be one card or multiple

data 41eits. Once the desired copy function has been accomplished, the

update capability would he used to make corrections, as necessary, to

satisfy unique requirements of the newly created LSACN record.

MAINTENANCE AND SUPpi UPPORT FILES

Supply supporrequirements are basically derived from maintenance. -

requirements, as ate)the requirements for personnel, 'support equipment,

training, training equipment, facilities, and technical manuals. Maintenance

requirements are derived from the'system level operational and support con-

cepts, and from detailed R&M-analyses at all levels of hardware indenture.

The ALSAR system incorporates features that, in essence, take the main-

tenance requirements documented on the B, C, D, and D-1 Sheets and .automt-

ically,create basic records of other support requirements on appropriate

data sheets (E, F, G and H). These features were mentioned earlier in the

paragraph addressing efficient data entry for multiple applications. Using

this approach, the ALSAR system assures consistency and compatibility

-31-

43

between the maintenance requirements and the other ILS elements.

Portions of the B, C, and Di Sheets are used to drive the supply

support requirements documented on the H-Sheet. The CO3 card is used to

establish the top-down hardware breakdown in accordance with engineeting.

drawings and the MPN to Next-Higher-Assembly MPN relationShips. Usihg this

information, the. ALSAR automatically creates H40 cards from which the

Provisioning Parts List (PPL) is machine produced. Using this app-Aach,

the ALSAR eliminates the need to use the LSACN to produce provisioning

technical documentation as required by DARCOM. This permits the LSACN to

be assigned only to the reparable level using the WUC/WBS, which in turn

results in the significant advantages discussed earlier. Non-reparable

items are appropriately accounted for and documented,in accordance with

.standard reporting requirements.

pen specific LSA requirements for a given acqp. ion program do not

e 4logically result in a complete top-down breakdown e MPN to Next-Higher-IIII

Assembly MPN relationship for the total system, thi user Would utilize the

ALSAR on-line system to enter H40 cards to add missing parts, as applic'able.

The ALSAR system processing will notify the user when and where gaps in Jr

the PPL exist.

BATCH PROCESSING

INITIAL BATCH LOAD

The Initial Batch Load can be used for initial loading of the data-

base or for subsequent additions of new records if the key inforfflation is

unique. It is not intended for update or editing capability for existing

data. The system accepts ALSAR card formatted data from sequential files.

There are three phases to the load process, each of which performs edits on

the input data and produces a report. These reports should be used to

guarantee the integrity of the loaded database.

Phase 1

In this phase the card images are read, edited individually while flow

assurance editing is

from the

phase is

pleted.

rest of the

a control

done, and finally, the narrative data are separated

inputs. The first report ti-At is produced from this

ort which is to be used until this phase is com-

It is a sequential listing assigning a control nu

reference. Next an edit report is produced detailin wh

ber for

h fields

error And indicating whether insufficient previous cards have been

future

are in

received.

This report also warns of possible key parameter information problems that

may be encountered in Phase 2. Regardless of the error, all should be

corrected to insure a'sound database. The edits performed are identical

to those for the on-line data entry process. Phase 1 should be rerun

until an error-free run is obtained, or it is determined that all remaining

errors are inconsequential.

Phase 2

Most of the database records consist of multiple cards, but sometimes

a card is used to create one database record and occasionally cards are

broken down to produce multiple database records. Phase 2 performs the

function of breaking down and/or building up the cards to obtain these

records., It produces a sequential file and a report which warns of in-

complete information, duplicate information, or unidentifiable data detected

in this process. The report identifies the sequential number that was

assigned in the first phase, pinpoilting the exact card to be checked.

Phase 3

The third and final phase takes the records created from Phase 2 after

all errors are corrected and actually stores them onto the database in their

appropriaee-position. Again some errors may be detected since records are

connected to each other in a like fashion as the cards were in Phase 2.

When duplicates are found, or inadequate connecting records are available,

then an error is flagged to indicate further action is required to store

-33- 45

the record properly.

SUSPENSE REPORT

There are times when it is appropriate to store cards onto the data-

base which have a field in error. This may be done from the Initial Batch

Load when all of the card edit errors are not corrected in Phase 1 of that

process. Errors may also be ored from on-line processing. When an

element fails to pass an edit, the element will blink on the screen. If

the error cannot be corrected, the user can force the rest of the data on

the screen to be stored by typing an "F" for forced update in the command

field and pressing the "ENTER" key. The eleifent in error will be stored

as question marks. This feature allows the valid data to be stored and

available for use, and saves the time that would be required to re-enter

the data from scratch later.,.. ,'W

Each dat4baSe record has a suspense flag th will be setyllen,.-er

is stored,inthatteaord. Periodically, a:Sp.sp'en1e Report.J-W11).ldentgi',

all cards ',that haVe elements in error. The software will re-editall ..

records that:are flagged suspended,:_lf-a14.errors in the record.have been.,...

corrected, the suspense flag is turned off. All remaining errors will be

included in the.Suspense Report.

The Suspense Report is used to insure that errors are identified so

that corrective action can be taken. Errors listed on'the report are

sorted by card type, by LSACN. The card images correspond to the data.

sheets, and errant data elements are identified. Errors may be corrected

by calling the screen with the data in error and re-entering the element

°using the Update Command.

TURNAROUND DOCUMENTS

When data are entered on the database via on-line or batch processing,

the ALSAR will generate a Turnaround Document if desired by the user.

These hard copy printouts display information in data sheet format and

provide additions/changes to the database that occurred during the

processing period since the last turnaround was generated. When database

-34-

46

transactions were modifications or updates to information previously

entered, the Turnaround Document will display a before and after image.

The purpose of the Turnaround Document is to provide a hard copy

printout of information actually loaded in the database to functional area

users who are responsible for the accuracy and completeness of the data.

Dataa` elements that did not pass edit checks and were forced on the data-

base will appear as question marks on the Turnaround Document. The user may

u e this document to verify and correct data entries. This would be partic-

ularly useful when engineers/analysts responsible for data quality do not

actually, perform the data entry. Managers could use the Turnaround Documents

to monitor the LSA/LSAR activity and for hard copy backup files, as desired.

PROMPTING DOCUMENTS

Although systems engineering is a highly iterative process involving

many different functional areas, it can generally be described in the follow-

ing way. The process starts with design engineering activity. Next, the

results of design engineering are used by reliability engineering to

accomplish failure modes, effects, and criticality analyses (FMECA) and other

important functions. Next, the results of reliability engineering would be

used by maintainability engineering to determine the maintenance and support

requirements necessary to achieve and sustain a fully mission capable weapon

system. These three steps can be thought of as occurring in a serial manner.

When maintainability engineering completes the detailed task analyses-and

identifies support requirements necessary to repair and sustain the weapon

system in operational status, the activities of many other functional areas

may be accomplished in a generally parallel manner.

. The ALSAR system uses Prompting Documents to assist in the integra-

tion of all functional area activities involved in the systems engineering

process. When information is entered in the database by one functional

area, the ALSAR keys on selected data fields to determine if the data

entered are needed by another functional area user. If so, the machine

generates a Prompting Document to that functional area. The Prompting

Document preprints information needed by the next functional area to

3 5 -

4 t

4 7

accomplish additional LSA and reminds the user that additional LSAR input

data are now owed to the system. The information on the Prompting Document

is extracted from portions of the data sheets in Appendix A and is presented'

in a(format consistent with these data sheets.

Figure 10 shows the basic approach used to generate and distribute

Prompting Documents. It is seen that specific data sheet cards generally

relate to the functional area across. the top.. The card numbers in the

body of Figure 10 relate to the data sheets in Appendix A. Since the

specific functional area responsibilities may vary from one organization to

another, the prompting scheme is table driven. That is, the Prompting

Documents mailbefl'exiblytallored:to fit any particular organization.

DESIGN

ENGR

RELIAB'

ENGR

MAINTAIN'

ENGR

TRAINING,

SE/TE

HUMAN

FACTORS

FAOLITIES PROVISION-

ING

TECHNICAL

MANUALS

TRANSPORT-

ABILITY

INFOFROM:MIDI,

H1,1.

ROM:1 05

D1 06

INFOFROM:A,E,H

INFOFROM:CoD,E,I

INFOFROM:C DoEEl

INFOFROMB C-D

,

B 071 B 04.BB 05

B 04 AB 06B 08B 09B 10

i1f

J 02

'

J 11

TECH.

ORDERS

(T.O.)

t

ILLUS-TRATED

PARTS

BRAKDOWN

(IPB)

i .II 81

H 10H 20H 30

--I

G 02G 03

G 09

E OZV 05".

.

F 10

EE

r k

'x.28

D 03D 04

.

D1 0501 06

,

-?-t,

.0 3 _.

C

1 0t

..,

,. 4

. 1

A -04'

051 06

g, _

INPUT TERMINAL

.giq09D1('-f

V.fi1

ii:41,RbMkING DOCUMENTS

.

.

Figure 11 showS 'tWprOcVS!.begirining, in Step 1 with design engineering

entering a functionaI:ASIgnAson.bk the item under analysis. A

Turnaround Dotument isOentfba4..tbdesign engineering, and a Prompting

Document is sent to reliabil#ne'ering,iStep 2. When reliability enters

the information it the is repeated and a Prompting

Document is sent to maintainability'engineering, Step 3. When maintain-

ability engineering enters the information, it owes the system, Step 4

simultaneously sends prompting documents to one or more functional areas as

shown on the right side of Figure 11, depending upon the particular support

requirements. That is, if support requirements for that functional area

exist, a Prompting Document is sent; otherwise, it is not sent.

DESIGN

ENGR

RELIABILITY

ENGR

MAINTAINABILITY

ENGR

LSAR CONTROLGROUP

LINPUT

DATABASE

r.,

OUTPUTS

PROMPTINGINPUTURN-AROUND

OUTPUT SUMMARY REPORTSTO USERS ON COMMAND

USE OF PROMPTING DOCUMENTS

FIGURE 11 -

IHUMAN FACTORS.

ISUPPORT/TEST EQUIP I

[TRAINING

I'TECH DATA I

IFACILITIES I

SUPPLY SUPPORT I

ITRANSPORTATION I

SAFETY I

In actual practice the systems engineering process should involve

Design, Reliaility, and Maintainability Engineering working as a team to

investigate and evaluate alternative design concepts in an iterative closed-

loop manner. Similarly, the maintainability engirieers should.team with

Provisioning, Technical Manuals, and other functional areas to evaluate the

overall support requirements and capabilities..;This evaluation, in turn,

should be fedback to the design and R&M loop to insure that supportability

factors influence design alternatives and decisions.

-37- 49

The Prompting Documents provide a useful mechanism to enhance timely

integration and feedback in the overall systems engineering. Managers

could use this capability as a'tool to assist in formally organizing the

integration activity and in monitoring the results,.

LSA/LSAR PROGRESS REPORTSa

.Managers 'and functional area analysts may, on occasion, have a need

to review the current status of the LSA/LSAR effort for'a given program.

The ALSAR system currently provides two reports for this purpose.

LSACN Status Report

This report has been designed to list all of the active LSACNs associ-

ated with a given program effort. The report, which may be requested using

an on-line menu screen, provides a list of all currently active LSACNs in

the database for a-specified end item. For each LSACN the report will list

all of the data sheets that have been entered, along with the date that each

sheet was last revised. If the LSACN requires new skills, the G-Sheet for

each of the required new skills is reported along with the status of each

G-Sheet. If the LSACN requires facilities, the F-Sheet for each required

facility is reported along with the status of each F-Sheet.

Data Sheet Status

The ALSAR system will provide a hard copy printout of,the current

status of the data sheets that exist for a specified LSACN. The on-line

screen shown in Figure 12 may be used to obtain this output. The user

may specify one or more of the data sheets. The output will include all

of the information in the database for each sheet requested, including

narrative. The format and ''content of each sheet will be identical to

those of the corresponding data sheet in Appendix A, except that cards for

which no data exist will be omitted. The data sheets requested will be

T printed in alphabetical order.

-38-

50

DPR LSAOM-OS, SHEEltREQUEST, AFMOSD, AFMOSUXXXXXXXXXXXXXXXXXXXXAXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX AS OF XXXXXXX XX/Xx/XX

SHEET REQUEST

THE FOLLOWING REQUESTS REQUIRELSACN ALT-ACT

C

F I

D ALSO REQUIRES A TASK CODE

G ALSO REQUIRES A SKILL SPEC CODE

J ALSO REQUIRES A DRAWING NUMBER

THE H SHEET REQUEST REQUIRES H.MPN END-ITEM LSACN

DATA SHEET STATUS

FIGURE 12

REPORTING SYSTEM

f

Many reports may be generated by the ALSAR system. Table 3 lists the

reports that fully comply with standard specifications.

DARCOM IIISA REPORTS . ./110

The LSksummary reports shown Table 3 are the standard DARCOM reports

that the ALSAR system is programmed.to generate. The reports shown are,

those currently required by theAir Force. The ALSAR also generates the

,D-220 output-,for provisioning purposes.

51-39-

, TABLE 3. ALSAR OUTPUT REPORTS

LSA -02

LSA -03

LSA -04

LSA-05LSA -06'

LSA -07

LSA -08

LSA -09

LSA-10LSA -11

LSA -12

LSA -13

LSA -14

LSA -16

LSA-17'LSA -20

LSA -27

LSA- 30

LSA SUMMARY REPORTS

DIRECT ANNUAL MAINTENANCE MAN,HOUR BY SKILL SPECIALTYCODE AND CATEGORY OP MAINTENANCE

PERSONNEL AND SKILL SUMMARYRELIABILITY AND MAINTENANCE SUMMARYMAINTENANCE ALLOCATION SUMMARY .

SUPPORT ITEM UTILIZATION SUMMARY.;,. ,

CRITICAL MAINTENANCE TASK SUMMARY.SUPPORT ITEM REQUIREMENTS BY SKILL SPECIALTY

AND MAINTENANCE CATEGORY . .

SUPPORT ITEM REQUIREMENTS BY MAINTENANCE CATEGORY..AND SKILL' SPECIALIY CODE

SUPPORT LtTEMS LISTSUPPORT ATUS'-LISTSPECIAL TRAINING. DEVICE SUMMARYSPECIAL FACILITY...REQUIREMENTS

SUPPORT EQUIPMENT'GROUPING NUMBER UTILIZATIONSUMMARY

TRAINING TASK LISTPRELIMINARY MAINTENANCE ALLOCATION SPRELIMINARY MAINTENANCE ALLOCATION SUMMARY TOOL PAGETOOL AND EQUIPMENT REQUIREMENTSSPECIAL TOOLS LISTSPECIAL TOOLS LIST

CODE

DATA ITEM DESCRIPTIONS

DI-S-6176 SUPPORT EQUIPMENT RECOMMENDATION DATA (SERD)DI-S-6177 CALIBRATION MEASUREMENT REQUIREMENTS SUMMARYDi -V-6183A/M CONSOLIDATED SUPPORT EQUIPMENT LIST (CSEL)DI-L-6147A PRESENTATION AND PACKAGING DATA '

DI-V-6181/M REPAIR PARTS/GSE PRICE LIST (JET ENGINE)DI -V-6185A/M LIST OF STANDARD/MODIFIED HAND TOOLSD220 AFLC PROVISIONING SYSTEMDI-V-7008 COMMON BULK ITEMS LIST (CBIL)DI-V-7006/M INTERIM SUPPORT ITEMS LIST (ISIL)DI-V-7004 LONG LEAD ITEMS LIST (LLIL)DI-V-7002 PROVISIONING PARTS LIST (PPL)DI-V-7005 REPAIRABLE ITEMS LIST (RIL)DI-V-7007 TOOLS AND TEST EQUIPMENT LIST (TTEL)DI -V-7016D/M PRE-PROCUREMENT SCREENINGDI-H-3256 TRAINING EQUIPMENT LIST (TEL)

DATA ITEM DESCRIPTIONS (DID).

( CMRS )

Table 3 also shows many complex reports that the ALSAR can generate

in total compliance with standard DIDs. The SERD, CMRS, and CSEL are

reports that are extremely costly to accomplish manually. Using the

ALSAR procedures and conventions, these reports are completely machine

generated. Likewise, the provisioning technical dq&imentation listed

is completely machine generated.

REPORT SELECTION SCREENS

All of the reports listed in Table 3 may be requested via on -line

report selection screens. Figure 13 is the Report Menu screen.ftOm the

ALSAR Users Guidel Placing an X by the desired report will prodUce,the

-40- 52

- appropriate Report Selection Screen. For example, if an was placed,

by CMRS,,,,thgeport Selection Screen shown in Figure,14 Wouldappear.

RPTORM1, REPORT REQUEST .SELECTION, AFR15D, AFR15UXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX AS OF XXXXXXX XX/XX/XXI

REPORT REQUEST

_ LSAO1 .YLSA02. r' ,;; LSAO3 _ LSA04 L i105- .. LSA06

LSA07., :LSADES LSA09 LSA1O LSA11 LSA12 ..

, _

LSA13 LSA14.' , LSA16 - LSA17 LSA20 , LSA27.'

L5A30 '0CBIL ', ':CMRS' : ,2qE1- _ D220 _ ISIL

.:11.1L, MODMETRIC _ NRLA PPL RIL

SERD TEL TTEL

PKRQ PRESERVATION AND PACKAGING DATARPGP REPAIR PARTS/GSE PRICE LISTSMHT LIST OF STANDARD /MODIFIED HAND TOOLSSCPR PRE PRpCUREMENT SCREENINGLSAS LSACN STATUS REPORT ,:

ALSAR REPORT MENU SCREEN

o FIGURE 13

CI

RpTOR-131-AFR15D4AFRO1Uxxxxxxxxxlb&O*;fxxxxxxxxxxxxxxxxxxkxxxxxxxxxxxxxxxxxx AS 4F,'_XXXXXXXX XX/XX/XX

REPORT SELECTION FOR .

SUPPORT EQUIPMENT RECOMMENDATION DATA (SERD)CALIBRATION/MEASUREMENT REQUIREMENTS SUMMARY (CMRS)CONSOLIDATED SUPPORT EQUIPMENT LIST (CSEL)

SRV DES CDLOCATIONALT ACTAGCY CDCOPIESLSACN

END ITEM LSACN

END ITEM ACRONYM CODE

(SERD ONLY)

(CMRS ONLY)

(CMRS ONLY)

CMRS REPORT SELECTION SCREEN

FIGURE 14

53%me

This screen is aISo used to request:the SERD and CSEL reports. The user

would then enter the information necessary to speeify the CMRS report for c'

the desired end item, indfcate:how many copies are desired, and specify

the location of the printer to be used to produce the hard copy report.

All of the output reports'haye similar Report. Selection Screens,

with the. required report specification parameferS:listed.'0

'TAPE' OUTPUTS

-The ALSAR sysfeM can alio generate tape,,outputsthat may be used as

.A.npUt,to three standard models used by the Air. Force; the Mod - Metric;

1IFft.d LCOM.

'FigUres 15 and 16 are- he onIine,RepOrt Selection Screens for

requesting:theALSAR.Io.:generafe .the .output tapes for the MOD -METRIC

and.NRLA,.tespectivelyA pseUdoBaSeLevel History TapelABV6DA) and

.B-4 Master File Tapeare generated for input Co fhe.ILCOM. The ALSAR

USersCuide provideS'Oetailedinstructions for building a constant data

file'to enable the ALSAR to generate the, ABD6DA using LSAR data.

REPORT REQUEST SUMMARY

The ALSAR has an on-line screen that dispia9s a current status summary

of all the reports that have been requested by a specific user but that

have not been printed. This screen may be used to check the status of-a

report, to delete or hold a report, or to initiate some thanges to the

originalreqUest.

PD

ri

-42-- 54

9

fRPTOR-40, AFR1SD, AFRO1U .t

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXFXXXXXXICXXXXIONMMIC{XXXX AS OF 2IY:XXXXXX)<X4FX/XXREPORT SELECTION FOR MOD-METRIC (MODE) .

AGCY CD ALT ACTBUDGET MIN BUDGET MAXLRU BUDGET

7BACK ORDER

9OUTPUT DEVICE INPUT DEVICE DBSO

NUMBER OF BASES ---FLYING HOURS

ORDER & SHIP TIME '

PRINTER DESIGNATOR PRINT QUANTITY COMBINEDEVICE,

BASE REPAIR TIRE,

BSTART . BSTOP

TITLETITLE /COMMENT

DEPOT REPAIR TIME ' PRIME ALC

CFAC , PBINC

MOD-METRIC TAPE SELECTION SCREEN

FIGURE 15

1

. RPTOR-41,. ARISD:,:AFROIUM000o0010000000Og(I to meREPORT SELECTION 'FOK'NETWORK REPAIR LEVEL ANALYSIS (NRLA)

AS OF XXXXXXXX XX/XX/XX

AGCY CD ALT ACT

REQUESTED LRUS

DEPOT WORK BREAKDOWN STRUCTURE END.1ITEM ACRONYM CODE

REPAIR CYCLE TIME DEPOT CON .> DEPOT OS BASE

.

°TYPE I: END ITEM NAME Nuppl BASES RATIO. Oi'FORCE .99_SERVICE LIFE EQUIV.' MEAP.SYS OPERATION HOURS

SENSITIVITY ALT: LOWER RATIO _.99 UPPER RATIO .99-EXTREMES/COMPLETE RUN IDENTIFIER

TYPE 2. BASE SHOP HHRS BASE TURNOVER RATE -'.99.9

DEPOT SHOP 94RS DEPOT TURNOVER RATE ,i9,1

TYPE 3: ORDER/SHIP TIME CONUS .999 PACKING COST CO S.-,,__.99

ORDER/SHIP TINE OS . ', .999 PACKING COST OS . ..'" .99.

:..-

TECHNICAL COST

-NRLA TAPE SELECTION SCREEN

FIGURE 16

-43-

3

55

4.

SECTION iv

AIRCRAFT CHARACTERISTICS'DATA

GENERAL

In this section the Cqrrent development status of the protytye.

Aircraft'Characteris4s. D'ata File (ACDF) is presented in summary form.i

The reader is encouraged to.review again Figure 1 and the discussion of the

conceptual UDB approach and objectives presented in Section II. In ,

addition, the reader,is encouraged to review again Figure 3 and the dis-

cussion of the UDB features relative to the overall system objectives.

PURPOSE. AND USE

The purpose of the ACDF. is to provide a Mechanism where ent

and industry users have .Convenient and timely access to design, R&M, and

support cost information about existing operational aircraft weapon systems.

Primary users of the ACDF would.be those'from Government and industry who

are`-::xeStionsible. for the acquisition and support of.new weapon systems and

equipment.

(I'nceptual Phase

In. the early weapon system planning stages; the ACDF would be useful

to tIlOse responsible. for establishing system and major subsystenirequiTe7

ments, and specifications. The ACDF design and utilization data could be

used to assist in identitfv- ,the,the BCS for the new weapon system. When the,. .

operational and support concepts are formulated, the R&M and support cost

data associated with the BCS would assist in establishing the system avail-

:ability and R&M requirements and in the allocation of R&M system require-

ments to the subsystem levels. In general, the ACDF datacan then bsbused

in conjunction with early LSA/LSAR efforts to support and influence trade-

off studies of alternate design approaches fior. .theanew weapon system.

56

fl

.9 Preliminary and-Detailed-Design Phases

A the desi.gn.attivity proceeds through increasing levels ofdetail,

the ACDF may be used to obtain BCS data at lower hardware indenture levels.

The procesioof4bsiag.the BCS in conjunction with LSA/LSAR to support design, ..47

tradeoff studillelioand analyses can be used throughout the preliMinary and

- detailed design phases..

'

O&S Phase .1

When the rrew weapon system becomes operational, the ACDF can be used

to measure and evaluate the system performance in terms of R&M parameters

and support-Costs. Field data from the MDCS and VAMOSC systems would be

processed by ACV programs'and provided to users via the on-line access

system,

. Research and-Development (R&D) Activities

Those organizations'involved with R&D to develop new or improved

predictive models and tools: would be users of the ACDF. Timely and con-)

venient access'to.1this database would greatly reduce the cost and increase

the effectiveness of data collection efforts'by a large community of

researchers. The results of R&D efforts that utilize the-ACDF for source

data would be easier to compare and validate, as opposed to those that

didi.not use a common data source.

1/0

TECHNICAL APPROACH

%.

The ACDF was developed Under the concept thit it would eventually

be impleMented and maintained at a central Government facility. Since

the specifiC machine and softwareenvironment to house the ACDF was not

known, there was a strict requirement to design the system for optimal trans-

portability. Asa result of this requirement, and the need for an efficient .

online capability to serve remote users, the ACDF was designed as an

interactive Time - Sharing Option,t(TSO) system that utilizes the Virtual

.Storage Access Method (VSAM).' Application programs are writtsal exclusively,

I

-45-57

in American National Standard Common Business' Oriented Language (ANS COBOL).

VSAM records are designed to group or categorize data in a manner intended

to ehhance;the utility of the ACDF to multiple users and the efficiency

of operating the, system.

MODES OFAPERATION

Data Entry'- The ACDF system data files would be initially loaded

and subsequently updated by the organization responsible for operation and

maintenance of the ACDF. Batch load programs would be used for data entry,

which would be be accomplished by the host computer facility. Remote

on-line users would not have the capability to enter or modify data in

the ACDF.

Data Retrieval Data loaded in the ACDF may be retrieved by any

authorized user via on-line CRT terminal screen, or batch output programs

generating, hard copy printouts. Users may specify and request hard copy

outputs using the on-line mode of operation. The ACDF output for speci-

fied data is presented in the same image, form, and content, whether

displayed on the CRT or hard copy. Users operating CRT terminals with .

screen image printers could obtain hard copy of selected data. The system

is designed to permit dial-up line access to the ACDF.

DOCUMENTATION

Table 4 lists the documents that record the results of the ACDF

development. effort. This documentation, dated April 1983, has been

delivered to the Air Force.

-46- 58

TABLE 4. ACDF DOCUMENTATION

DOCUMENT

ACDF Data ElementDescriptions (DED)

ACDF Data Input RecordLayout

ACDF Users Guide

ACDF ProgrammingDocumentation

ACD1' DED.

PURPOSE

Defines each data elementin each ACDF Record

Defines the record layoutsfor data input to ACDF

Provides instructions for useof the on-line system

Contains all programs developedfor operation of the ACDF

Unlike the ALSAR which used DARCOMP 750-16 as the baseline, no base-

line system was

. in the DED were

Hankins (1980),

available for the ACDF. As a result, the data elements

selected on the basis of the previous work by Thomas and

which included a major industry survey that investigated

the data needs of those responsible for weapon system design, R&M, and

logistics support. The ACDF DED provides the definition for each data

element in the system, including the field size and other characteristics.

'Me data elements are then organized into specific records for greater

utility to the user when retrieving ACDF data.

Data Input Record Layouts

This document.contains the data sheets depicting the layouts for each

record in the ACDF. Those responsible for loading data in the ACDF would

use these data sheets in conjunction with the DED to inputs data. There

are 66 data input sheets covering all of the ACDF records'. An example of

the data sheets is shown in Figure 17, which includes a po:ftion of the

System Features, ElectfIcal Power Supply, and Hydraulic PciJer Supply Rrds..

Users Guide

Thiis document provides detailed instructions for usinirthe on-line

-47- 59

;-

NIIIUIIIIIIU

IIIIIIIIIIIUIU

IIIIIIIIIIIIIIIIIIIIIUIIIIIIIIU

IIIIIIIIIIIIIIIIIN111111111111111111111111111110111111111110.11111111111111111111111111111111111111101

11111111111111111111111111111111111111111111111111111111111111111111111111111111111

1J

1

MI11111111111111111111111111110111111111111111111111111111111111111111111111111111

0111111111111111111111111111111111111111111111111111111111111111111111111111111111

5414/'

14 ve-

p

v. _

i1

1ii

11-

N111111111111111111111111111111111111111111111111111111111111111111111101111111111

111111111111111111111111111111111111111111111111111111111111111111111111111111111111

.

PI.,

,I

552

A

1,

system to retrieve data from the ACDF. Procedures are given to retrieve

data from each record, and for special functions that present data from

multiple records. The manner in which the data are displayed on the CRT

terminal screen for each record is also described in the Users Guide.

Programming .Documentation

This-48O -page dOcnment includes a- , -

tion prbgralli.,4sSociaied0.th the ACDF.

includes theprOgram naive; calling and

or sequential :fileS.a..0910,NnC:pion

ology used The source Codefdiveacll.iirOg'ramiS also included.

ACDF RECORD CONTENTS

description'of each COBOL applica-

Documentation on each program

called programs, copy code, VSAM

of the program, and.the method-

The records described in the DED are listed in Table 5. The ACDF

would contain information in each one of those records abput each air-

craft's MDS. A brief description

presented next..

of the contents of these records is

TABLE 5. ACDF RECORDS FOR EACH AIRCRAFT MDS

SYSTEM RECORDS

AIRCRAFT GENERALMISSIONBASIC MISSION PERFORMANCESYSTEM DESIGN AND PERFORMANCEENGINESYSTEM UTILIZATIONSYSTEM FEATURESSYSTEM R&M/COSTOPERATIONAL R&M/COSTNATIONAL STOCK. NUMBER

AIRCRAFT RECORD

SUBSYSTEM RECORDS

AIRFRAMEAVIONICSCREW STATIONELECTRICAL POWERENVIRONMENTAL CONTROLFLIGHT CONTROLFUELHYDRAULIC POWERLANDING GEARPOWER PLANT INSTALLATION

This record is basically header information thit provides a top*;

level description of a particular aircraft weapon system.

-49- 61I

MISSION RECORD

This record containsinarrapiVe:dnfOrmatiOn from the Air Force Guide

(AFG-2) briefly describing the'primaryapd'.seCondary missions of an air-

craft MDS.

BASIC MISSION PERFORMANCE RECORD:.:

This record contains. inf'orMation ..from 'the AFG-2 for the basic mission

performance. The data eleMenWAnd'Adlinitions are consistent with AFG-2.

The record is designed toThccoMlilodatedifferences in,AFG72 data between

aircraft MDS.

SYSTEM DESIGN'AND PERFORMANCERECORD

This reCorcLcontains:informaqon..abouttop-Jeyel systerit(design and.

'operationq performance,charatteristics,of an aircraf'MDS. The infOrma-t

don includes dimensions, weights, thrust, speeds; rap ate of. Climb,

and altitudes., It also provides the total number of 4-; and

5-digit 4dUC items associated_ with an aircraft MDS.

ENGINE RECORD

This record containsHAFC43 design and performance infOrMatipnabOut

engines used in operational aircraft MDS. The data elements and Aefi47

tions are consistent with:AFG-3.- The record is designed to accommodate',

...differences in AFG-3 data between engine types and mod4s.

SYSTEM UTILJZATION-REORD:

This.record,Contains dnformation about,the fleet utilizarionof

aircraft MDS. Ttjnclpdes''the active inventory, base level flying;.. time

and sortieS, average sortie length, and other relevant fleet informatiOn:

SYSTEM FEATURES. RECORD

k

ThiS'record contains information aboUt top-level Systeeidesign

featuredipcOrporated:on an aircraft MDS. The features include weight:.;ClasS..,.

,

-50-

62

number of aircrew personnel, type crew escape system, type engines, number

of engines, type engine installation, wing geometry, type flight controls,

type and number of electrical and hydraulic systems, type avionics installed,

built -in -test units, and many other features.

it AVIONICS SYSTEMS RECORD

This record contains information that identifies avionics equipment,:,

by standard equipment nomVelaturej$W, that is installed on an aircraft

MDS. For each SEN the record specifies whether or not built-in-test pro-

visions are incorporated.

SYSTEM R&M COST RECORD

ThI8 record contains t913:,:leVel R&M an' cost Information for

an aircraft MDS. The informatiOttIncludes unit fly-away cost, system

level support costs, base and depot level maintenance manhours, base

level maintenance manhours per flying hour (MMH/FH) and sortie; and overall::

MMH/FH.

OPERATIONAL SUPPORTSUPPORT AND COST RECORD

This record contains detailed R&M and support cost information for,

a weapon system. There are five sub-records, all of which will .bauseful

to those responsible for LSA/LSAR activity on new system acquisition

programs.

Aircraft Level/AFR 800-18 Format 4

This sub-record wovides system level R&M data in the format and

content specified by Air Force Regulation (AFR) 800-18, "Reliability and

Maintainability Program" (formerly AFR 8Q-5). This record breaks out pre-

ventive and corrective maintenance into all the required categofIes addressed

in LSAR, and provides standard R&M parameter terms for each category.

Work Center by Aircraft

This sub-record groups R&M data by work centers associated with an

.41_rdraft MDS, For a large aircraft MDS, this record could. contain data for

apprQamately thirty (30) R'Ork centers..

.

Support C

4

This sub-record contains support cost information that may.pe

retrieved at the 5-digit WUC level, or summarized' at the 2-, 3-, 4-digit

WUC levels. The machine, stores only the 5-digit WUC data, and internal

programs calculate summarized values, on request by usrs. The data elements

and definitions in

related td-cost.

R&M Data by WUC

Thissub-record contains R&M parameter data at the-lOWeeveltiof.

-WUC'indentures.,'The data are.expressecLin terms compatible

required fotdetailed levels of LSA /LSAR for neW system acquisition

programs.

this record arecOnsistent'withYAMOSC data elements.

4,1

Maintenance Action by WUC

This sub-record contains summary data by WUC, sorted by standard Air

Force maintenance "action taken," "how malfunctioned," and "type how

malfunctioned" codes. The reader may recognize that provisions On the

B- and D-Sheets of the ALSAR. will relate to this sub-record in the ACDF.

NATIONAL STOCK NUMBER RECORD

This record contains informAtion that enables users to cross-reference

a National Stock Number,(NSN) to a pa'rt number, determine each aircraft MDS

that uses the NSN, and determine the-WUC assigned to the NSN on a given

aircraft MDS. In addition, the record contains cost and weight information.

about an NSN.

-52-64

SUBSYSTEM RECORDS

There are nine individual subsystem records in the ACDF.. These k.

include airfraM6 crew station, environmental control, electrical power,

flight controls, fuel, hydraUlics, landing gear; and power plant: The

Avionic Systems Record was, diseased earlier. Each'subsystem record con-

tains deAn, weight,,and WUC/NSN cross - reference information.

Dps'igners and logisticians. could use the subsystem r cordsough-

.out thel'design and development act5.'ixity for a new system_ acquJ4,itiOl''

Trograt. The WUC/NSN cross-refereiice.tould be used in conjunction with

the NSN and Operational Support/Cost'Records to evaluate the-performance of

equipment in various aircraft MDS$.

'ON-LINE SYSTEM

The on-line interactive system is designed to permit users to request:

infoimation selectively. and have it displayed on remote CRT terminal screens.

The ACDF database is actually structured in accordance. with the records. in

Table 5. Functionally the database may be viewed in a manner similar to

that shown in Figure 18. The database is, designed to facilitate retrieval

of all or part of the information in the database,,about a particular aircraft

MDS.

The ACDF provides design and weight information for each subsytem

record. It also provides WUC/NSN cross-reference information. The WUC

can then be used to retrieve desired R&M and support cost information about

the subsystem.

-53-65

BASIC SYSTEMFEATURES,

AIR5I(AFT

M S

ENGINE

AVIONICS

°MUNITIONS

SYSTEM DESIGN/PERFORMANCEENVELOPE ANDBASIC-MISSIONPARAMETERS.

SYSTEM,UTILIZA-TIONRECORD

SYSTEMSUPPORT '(RIM) ANDCOST

;

SYSTEM LEVEL

SUBSYSTEM LEVEL

FOR EACH SUBSYSTEM

1. SUBSYSTEM DESIGN

2. SUBSYSTEM WEIGHT

3. SUBSYSTEM WUC BREAK-DOWN/NSN V-REF

4. SUPPORT/COST2-DIGIT WUC SUMMARY5-DIGIT WUC INFORMATION

wUC SUBSYSTEM

11,000 AIRFRAME12,000 CREW STATION13,000 LANDING GEAR14,000 FLIGHT CONTROL16,000 ESCAPCCAPSULE,20,000 POWER PLANT(ENGINE)41,000 AIR CONT., etc.42,000 ELECT. POWER SUPPLY45,000 NYS, POWER SUPPLY

etc.

FUNCTIONAL DISPLAY OF ACDF DATABASE

FIGURE '18

RECORD COMMANDS

-.7

Once the user is logged on and "READY" appears on the screen, typing.

the "ACDF" command. will retrieve the.menu screen shown in Figure 19. The

user may then select and enter the CODE for the desired RECORD NAME shown

in Figure 19. When the desired record code is entered, the lchine will

prompt the User, to enter the aircraft MDS of int- Brest. When the appro-

priate MDS.is entered, the ACDF'will display the reqUested information

on the CRT terminal screen. If the user desires all of the information.

in the ACDF about a particular MDS, the user would enter "ALL" rather than

the code for one record. The sAtem will then display the informatio4-in

all of the ACDF records for the aircraft MDS specified.

-54-

elsWELCOME TO THE AIRCRAFT CHARACTERIST;C TATA BASE

PLEASE ENTER CODE FOR RECORD NAME DESIRED

CODE RECORD NAME'

ACF AIRCRAFTAFR, AIRFRAME SUBSYSTEMAVS AVIONICS SYSTEMSBMR BASIC MISSIONCSP 'CREW STATION & FUSELAGE DATAECS EI.NIRONMENTAL CONTROL SUBSYSTEMENG E4GINE DATAEKS, ELECTRICAL POWER SUPPLYFCR FLIGHT CONTROL SUBSYSTEMFEA SYSTEM FEATURESFSR. FUEL SUBSYSTEM

CODE

HPRLGRMDRNSNOSC

PPSSDP

SRNUTI

RECORD NAME

HYDRAULIC AND PNEUMATICLANDING GEAR SUBSYSTEMMISSION AND DESCRIPTIONNATIONAL STOCK NUMBEROPR SUPPORT/COSTPOWER PLANT SUBSYSTEMSYSTEM DESIGN & PERFORMANCESYSTEM R & M COSTSYSTEM UTILIZATION

END, TO END THIS JOB

PLEASE .ENTER CODE FOR INQUIRY MODE DESIRED

INQUIRY MODECODE

LACLAVLDE

4. LENSELSEL

LIST-ALL AIRCRAFT MDS AND SRDLIST ALL AVIONICS EQUIPMENT SRDLIST DATA ELEMENTS WITH RECORD CODELIST ALL ENGINE MODEL NUMBERSSELECT ALL AIRCRAFT WITH A SYSTEM FEATURE

,

LIST DISPLAY A LIST OF SELECTABLE FEATURES WITH INDEX VALUES

9

I-

ACDF RECORD SELECTION DISPLAY SCREEN

FIGURE 19

QUERY COMMANDS

The interactive ACDF system enables the -user to query the system for

selected information, The CODE for each of several INQUIRY MODES t listed

at the bottom of the RECORD SELECTION DISPLAY screen shown in Figure 19.

LAC Command

When the user enters this. command, the MDS and Standard Reporting

Designator (SRD) will be displayed for each aircraft weapon system for

which data exist in the ACDF.

LAV!.Command

When the user enters this command, the Standard Equipmqnt

(SEN) will be'displayed for all avionics equipment in the ACDF.

-55- 67

Nomenclature

:LDE Command

,,When the user enters the LDE command, an alphabetical listing of all

the data'elements.in the ACDF is,displayedshowing the record in which it

is used. This feature would be paricutarly'usefurwhen the user is

interested in 'one or more specific data elements, but does not knoW how

to retrieve them. -

user enters-the LEN,coMmand list of all engine model number's

Reebrd is displayed.

SEL List Command

'System Features (FEA) record contains data elements that describe

basic characteristics of an aircraft weapon system.. When the user entersI

the. FEA.'command,'the machine will prompt for the desired aircraft KIDS. When

the rips Isentered, the machine will display all of the system features that

are incorporated on that MDS.

The SEL-LIST:cotmand, when entered, will'display ajist of aliof the ,q.

data elements'in-the System Features.Record along witIO:an Index. Number. for

each feature as shown in Table .6. In addititin., the maChine'will prompt : the

user to enter the Index NUmb7r interest this is ae0(4mplished, the

Machine will display all of the aircraft MDSslat have '0..kted

features.

Some of the systeM features will require, addUional information, which

the machine will prompt the user to "provide.. For eXaMplewhen the user

wants to find all aircraft MDSs that have two engines"eMbeddeclAn the

fuselage, Index Number 10, is to be entered bythe user The' machine would,

then prompt the user to enter the number of::engines. When:"V! entv-e4

.the system would display all aircraft MDSs that have two engine's embedded

in the fuselage.

68

8

TABLE 6. SYSTEM FEATURES RECORD

INDE':: VALUES OF SYSTEM

INDEX FEATURE

1 MANUFACTURERAIRCRAFT TYPE

3 PRIMARY MISSION4 WEIGHT CLASS

AIRCRAFT DENSITYNUMBER AIRCREW

7 CREW ESCAPE6 TYPE ENGINE9 TOTAL NUMBER OF ENGINES10 NG OF ENGINES IN FUSELAGE11 No OF ENGINE ON FUSELAGE PODS12 NO OF ENGINE IN WINGS13 NO OF ENGINE ON WING PODS14 TYPE ENGINE INSTALLATIONIs ENGINE AUGUMENTED

_16 VARIABLE GEOMETRY INLETS;7 THRUST REVERSER18 WING LOCATION19 VARIABLE WING GEOMETRY2G WINGS WITH INTERNAL FUEL TANKS21 HIGH TECHNOLOGY WING22 BOUNDARY LATER CONTROL23 INDEPENDENT FLIGHT CONTROL24 FLY-BY-WIRE CONTROL SYSTEM25 STABILITY /CONTROL SYSTEM26 ELECTRICAL MULTIPLEX27 IIINDEPENDENT ELECTRICAL POWER26 AUXILLARY POWER UNITS29 INDEPENDENT HYDRAULIC POWER30 HYDRAULIC SYSTEM PRESSURE21 H'0AAULIC DEPENDENT SUBSYSTEMS32 HF COMJNICATIoN SYSTEM_!3 VHF CONNuNICATION SYSTEM'34 UHF CONNMICATIoN SYSTEM35 Fm CONNuNICATION SYSTEM36 RADIO NAVIGATION SYSTEM37 RADAR 'NAVIGATION SYSTEM36 A/WRADAR39 IR NAVIGATION SYSTEM4G ELECTRO OPTICAL

AVS V, r ,ic, u 'Tine n C

A

FWURES AVAILABLE FOR INQUIRY

INDEX FEATURE

41.

42

43

444546

47

4849

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

7879

A/A MISSILESA/G MISSILESCRUISE MISSILESRFSHUDECMINTERNAL GUNSON-BOARD MAINTENANCE RECORDERLANDING GEAR TYPENUMBER OF LANDING GEARSNUMBER OF WHEELS/TIRESDE-ICINGANTI-ICINGBLEED AIR SYSTEMTYPE OF OXYGENAUTO PILOT SYSTEMAUTO PILOT/ILS COUPLEDTERRAIN .FOLLOWING/TERRAIN AVOIDANCE (TF/TA)AUTO PILOT COUPLED TO TF /TA.AUTO PILOT COUPLED TO WEAPON DELIVERY SYSTEMFLIGHT DIRECTORWEAPON CONTROL SYSTEMEXTERNAL STORE STATIONSCAMERAS OBI BOARDAIR-TO-AIR REFUELINGWINDSHIELD RAIN REMOVALAIR TURBINE MOTORSAVIONICS EQUIPMENT COOLINGRADAR ALTIMETERCRASH DATA RECORDEREMERGENCY RADIO BEACONCOMMAND/CONTROL EQUIPMENTFIRE SUPPRESSION SYSTEMLANDING GEAR KNEELINGLANDING GEAR CASTERING/STEERINGTAIL BUMPERBUILT-IN-TEST SYSTEMSSTRUCTURAL COMPOSITE MATERIALAVIONICS/WEAPON,CONTROL COMPUTER SYSTEM

Iii uf-;e r wants to know the avionics equipment installed on a

jO ve a I rural t MDS, the user would enter AVS and the MDS. If the user

! to know all of the MDS that use a particular piece of avionics

equipment , t he w;er would enter AVS and the SDI for. the equipment.

r)7- 69

'Engine Data

Using the Engine Record (ENG), speciA prompts are available fiat

petmit the,user (a) to obtain all the dAta associated with tte engine

installed on a given aircraft MDS, (b) to'find all aicraft MDSs that usego

a particular engine, and (c) to obtain all the information available about111

a particular engine.

National Stock Number Data

Using the National S;qck Number Record (NSN), special prompts are

available to find all' aircraft MDSs thak use a particular NSN in a

specified major subsystem, (b) to find all aircraft MDSs that use a partic-

ular manufacturer's part number (MPN) in a specified major subsystem, (c) to

find all the major subsystems on a p#rticular aircraft MDS that Utilize a

specified NSN, and (d) to find all data for a particular NSN installed in a

specified major subsystem.and aircraft MDS. 4

ON -LINE CRT SCREENS4

Data retrieved from the ACDF system will be displayed on:remote CRT

terminal screens. Many ad the screens fbr the ACDF records are included in

Appendix B. The data would be displayedirexactly as shown'for'each record.9.

When all of the available data will not fit on a screen image, the continued

data would automatically wraparound to the next screen.,

HARD 'COPY DATA

The on-line system permits userso

to request hard copy p.rintouts of ACDF

data. The'ACDF Users Guide Akovides iliktryctions for requesting batch print-

outs. The outputs will Be displayed in the same form and content as shown

in Appendix B.

SECTION V

4+

AFOTEC AND COMBAT DATA:At

414Cti GENERAL

The UDB dowelogment program effort covered in the previous' sections was

accomplished by Clemson University. Two additional efforts that were

relativelys'Slnall in scope were accomplished as part of the UDB development

program. The first was a study of the OT&E requirements for a new weapon

system, which was accomplished by the BDM Corporation. The second was a

study 9f combat data sources, which was accomplished by the McDonnell-Douglas

. Astronautics Company

ra,

OT&E REQUIREMENTS

.

OBJECTIVES AND APPROACH.

e

A ) . 0The, objectives of this effort were, first, to investigate the'data input

-*

and output rqqthrements if Vhe Air -For&st Operational Test and EvaluationS

Center (AFOTEC) durig an air4aft OT&ElAuitability assessment and, second, l

. - 44 .;,.,:

4o determine the'eictent4to which the prototype UDB would satisfy these4, 'a,.

needs. Two major tasks were undertaken to satisfy these objectives. The

first,,,,,was To identify and evaNtate all- of the data input requirements and. . ,

data output products of the standard AFOTEC computer programs used in anV no

aircraft OT&E suitability #sg4ss ent. The,second task *as to compare the

le,

.

,ALSAR and ACDF Capabilities of f UDB with the result*of the

,first tast

AFOTEC INPUTS AND OUTPUTS A dk

rable 7 lists the primary systems used by AVEC. The data elements0

1required for input to each one of these systems .were defined Simli arly,

the output products of each one of these systems were' defined, and the lit

individual data eleme4s of each product were identified. A matrix wfise.

developed for both input requirements and'output product91 shalki4

individual data elements by source and system used.

J.-59-

TABLE 7. AFOTEC SYSTEMS USED

INPUT OUTPUTREQUIRE- PRODUCTSMENTS SYSTEM USED

X D056 - AFLC Product Performance System

X MDCS - Maintenance Data Collection System

X SEDS - System Effectiveness Data System

X MILAP - Maintenance Information LogicallyAnalyzed and Presented

X MMICS - Maintenance Management Informationand Control System

X CDEP - Common Data Extraction Programs

X X MISEDS - Machine Independent SystemsEffectiveness Data System

X X OMNIVORE - AFTEC Data Base Access and Analysis,System

X X COO Cost of Ownership Model

X X. LCOM - Logistics Composite. Model

X X ' MCSP Mission Courilletion SuccessProbability Model

UDB CAPABILITY

Using the matrices developed in the task above, a comprehensive list

/*CE data Ilements was prepared to define the specific input and output require

', met-Its of AFOTEC. This'list was compared with the ALSAR and ACDF system

capability of the prototype UDB.. As a result, approximately 80 data elements

were identified that could not be supported by the existing

OT&E RESULTS,

The results of the OT&E requirements effort were documented by the

BDM Corporation and delivered to the Air Force -in April 1982. The objectives

of this effort were fully satisfied, and the results will be used in future

UDB development efforts.

60

COMBAT REQUIREMENTS

OBJECTIVES AND APPROACH

the objective of this effort was to investigate the feasibility of a

9161

combat unified retrieval syst. and its incorporationinto the UDB system.

eThe approach included tasks (a 6 investigate and identify all significant

sources of data on maintenance and logistics support in combat environments

and also to identify available combat data retrieval and generating tech-

nologies, (b) to collect a representative sample of combat data from

available identified sources, (c) to analyze potential approaches and design

requirements, including software, necessary for the Air Force to obtain,

store,. access this combat information, and (d) to outline corresponding

detailed design requirements, for a combat database, that are compatible

with the prototype UDB, and that will allow fot combat information retrieval.

SUMMARY OF RESULTS

The results of this effort were documented by McDonnell-Douglas

Astronautics Company and delivered to the Air Force in March 1983. The

report provides a discussion of available combat data sources and related

information,.and provides sample combat data that could be included in a"

Combat Unified Retrieval System (CURS).

The report concluded that it *would be possible to use the UDB system

as the baseline for the development of a CURS. The detailed design require-

ments for a CURS and UDB interface were no& defined.

0 ,e°

73

SECTION VI

CONCLUSIONS AND RECOMMENDATIONSFOR .

FUTURE DEVELOPMENT

CONCLUSIONS

I

The UDB will satisfy many of the objectives discussed in Section II and

shown in Figure.l. Progress to date has demonstrated that it is technically

feasible to achieve all of the objectives of the conceptual closed-loop UDB

system. While much development work remains to be accomplished, the ALSAR and

ACDF systems provide a solid foundation on which future development efforts

can build.?

The ALSAR is a fully automated and advanced system that is being used

in a production mode to support the defensive avionics pottion of the B-1B

program. Since this is its first application, the system has not yet been

validaeed. The ALSAR has performed satisfaCtorily to date, andWumerous

problems in the system have been corrected. As the B-1B program progresses,

the ALSAR system will be increasingly validated.

The ACDF system has been initially developed, but is far behind the

ALSAR in terms of verifiCatxiqp testing. All of the ACDF features covered

in Section IV are available in the prototype, but additional development

work will be needed before it is ready4o,be implement6d by the Air Force.

FUTURE RESEARCH AND DEVELOPMENT

Future MOW development efforts shabld include tasks necessary to

fully achieVe the closed -loo UDB objectives discussed in Section II and, .

shown in Figure 1. In addition, work to Ofihance the overall UDB system

should be accomplished in future efforts. Specific recommendations for

future R&D t.fork are presented ..tn the follotingparagraphs.

ALSAR

Production Support and Software Maintenance

Production 8upport to'the B-1B, and possibly other development'A'-'

grams, should continue using the existing ALSAR sySteM. Until such'tired,

that the existing ALSAR validated, this effOrt wiQ l require soft -14

ware mDltenance support to fix problems when they-are discovered. If' '

program users are operating remotely from the host ALSAli. facility, yfoduction,

support will be requireefroth,thehost,

From the standpoint ofthe UDB development program, contindedsupport

to progilams using the existing*ALSAR isneceSsar to Validate, the advhnced

features of the system. From the standpoint of' Force acquisition"

programs, the existing ALSAR system,fully satisfies-current Ait Forte *nd "DOD

requirements and is available now as Government property.

Redesign to Support MIL-STD-138872A

The ALSAR was designed and develop0 using DARCOMP

baseline. When MIL-STD-1388=2A is approved, the ALsARsy

redesigned to support this new MIL-r$TD; While retaining °t

currently available in the system. Thins is a major task

significant redesign of the database architecturQ, with c6

R0

7

r

effects throughout the on-ling 'system,,batch system, repor

documentation.

,,,,TranspoXotability.,

4

be

features

quire

ing ripple

system, and0

CP

d

ALSAR Is' urrentlfaesigned to ale Int4gptedDatabase

ManagAer4VSySteim ('.IDMS) 43/eloped Corporationo As

the AUSAR,Aste4 is tv..a8p4taVie, lyto letati6ns that have acompatible6 ;A

opera#4

0)ardWa f'and tpa rigtenvirenmeht:

Futtre UDB'deVeltip effortstpOuld include an investigatpn of OA.

technic l-and.46nolic anta08-A4 disadvantages of system transport-2.- 44f,'

, . 0. ,

/ ,

i

abilii?.-. the effort'','Shoul ''onAIder alternatives, that rangefrom maximp

to m mourn trangloArijiliynd dva/uate the 'global iMpact of pasic'tq.. A , .

4 ' ,

. t,; , >' ,

Lf'

,,,l''

4:441.

PviA, 763-

f!

4.

changes in requirements by the Government, standardization

Government, achieving closedIocip UDB objectives, and othin

Word-Processing Capability

The need exists for an ALSAR word-processing capabil

data in the' LSAR database. Future UDB efforts should iri;

,:investigate and develop an optimal and, generic interf

the AISAR'and currently available word-processing syst m

would be a' useful and cost-effective tool for those

accomplishing L$A/LSAR on any acquisition prograM.

Funciibnal-Users Guide. ,

'1

,eThere. is a ,critical need for , a detailed manual to ins

,,, : ..,y,,-, , ..4

area 4ers on4.'tbe use 0Whe ALSAR in the LSA procesS-,1-- o' !'

orilarrative-4

:task to -

141).1-tY be:W

ca ability

hle fo

sy e94pmettX progelam. While the DED, DEL,-

developed for the ALSAR, a much more detailed VS

MIL-Sp-1342,2A pr6vides an' enormous amount of

not-.ade'quatelyaddreSs'this s cif><c need. The 1'

functional

..may given weapon

*de were

is needed. Although

information, it does

1 Air SystemS CoMmand,

"Mlintenance?lanniag and. Analysis Program Guide,!''iS'

anexcellent eXample-of What?i4s needd4.

-Thd7AdiWsystdm, scribed In Section IV has'lbe n initially developed .

been validated. The systdWrepresentS a gOod start,tested'iibUt hasino

t,,addtional:developlent work is'needed o satisfy objectiVeS 3 and

(481

Shown , Sec tipn Figure 1.r

'In fl,ltpre pDB Oforts, the A DF should be loaded with actual' data forlb,

several airerOft MD5S% If the Air Force plans to use the UPB in the future

tii, pport a 'SpecialrIc new aircraft weapon system acquisition program, the

should1a0oaded with data about similar aircraft MDSs that are currentlyct,

'SpefatiOnai.t

',,

Interface Programs

The capability is needed to enable users to identify a BCS in the

ACDF and to have the system automatically produce a BCS output tape in ALSAR

format. This capability addresses Objective 3 shown in Figure 1 ind dis-

cussed in Section II, The programs,required to achieve this capability would

also satisfy Objective 7 shown in Figure 1.' Future UDB development efforts

should include this important work. In addition, continued work is needed

to refine and test the interface programs to process and load D056E and

VAMOSC data.

Trend Data Graphics

Although the on-line retrieval and display capabilities discussed in

Seftion IV have been developed, there is a need for the capability for

on-line retrieval and display of R&M trend data with graphics.1.

ODT&E INTERFACE

The prototype UDB effort included an investigation of AFOTEC require -

men s Arcraft suitability testing during OT&E. Future UDB development,

effCsrls should implement the findings of this effort. Specifically, the,

ALSAR and ACDF should be modified to provide, as minimum, the additional

data elements identified in the investigation of AFQTEC requirements.

INSTALL AND DEMONSTRATE UDB'

In future UDB development efforts the current ALSAR and ACDF systems

should be installed, tested, and demonstrated in a Government computerJ.

facility at Wright-Patterson AFB, Ohio. Subsequently, modifications and

enhancements should be installed, tested, and demonstrated. Software .

maintenance' should.also be provided throUghout the UDB development effort.

COMPUTER-AIDED DESIGN (CADF)'

?'The ACDF and ALSAR system of the IJDB represent significant computer

tools to aid in the design and systems engineering process. The UDB does

Y

-65-

VP,

not accomplV the function of modern CAD systems used to explore alterna-.

,

,,,tives and to establish the actual design of:(arairframe structure, m614

lines, compartments, and assemblies, (b) electronic.circuit boards and com-

pOnents, and (c) the many other uses for primary hardware, support equipment,

and facility design.

In future UDB efforts it is recom ended that R&D be Conducted to

investigate alternative approaches for eveloping a, generic interface14

between the UDB and various CAD systems currently available. The purpose

of such an interface old be to provide an improved mechanism whereby

useful R&M and logi tics support related information is.provided to the

design engineer such that logistics factors may influence design activity and

decisions that occur in the early planning and throughout the design process.

FolloWlbg this effort, the development of promising alternatives should be,.

Pursued.

-66-

1. DARCOM Pamphlet 750-16. DARCOM guide to logistics support analySis,.

,,,

Headquarters United States Army_Materiel Development and Readiness

Command:- .DARCOM Materiel keadinesS Support Acitivity, Lexington,

Kentucky, January,1979.

Military Standard 1388-2A. Department of Deft se requirements for a

logistics support analysis record. 'Headquarters United States Army

Materiel Developm6flt'd Readiness Comman . 'DARCOM Materiel. Readiness;

S,wpport Activity, Lexington, Kerucky, March 1983.

Thomas, E. L., & Hankins, R. J. OUse of human resources'data in weapon.-4

system design: Identification of data/data systems and related. tech-

nology. AFHRL- TR- 79 -36, AD-A080 598, Wright- Patterson AFB, Ohio:

Advanced Systems Division; Air Force Human Resources Laboratory,

January 1980.

4. Thomas, E. L., Hankins, R. J.,,& Newhouse, D. A. Human resourceso

data in weapon system design: An initial plan for.development. of-a

unified database. AFHgL-TR-80-25'AD-A093 282, Wight-Patterson AFB,

Ohio: AdvancedSysteMs' DiviSion, Air Force Human Resources' Laboratory,

October 1980.

t';

ACDF'

.ADP

AFB

AFG

AFIIRL

AFLC

'AFR

AFOTEC

ALSAR ,

ANSI

.AI;1 IP!'111 AsilaNS

Aircraft Characteristics Data-File'

Automated Data Processing

Air Force Base

Air Force Guide

Air Force:Human Resources Laboratory

(Air.Fore Logistics Command

Air Force Regulation

Air Force Operational Test and :Etaluation Centei

.Automated Logistics Support Analysis Record

American National. Standard InStitute

BCS Baseline ComparisOn System

.. , ..

CAD/CAM Computer-Aided Design/Computer-Aided Manufacturing.

CER Cost Estimating Relationship-

. ,

.

....,

CMRS - Calibrationand Measurement RequiremehtS SumM\406 4.. f

COBOL Common BuSineSS Oriented Lariguage.

CRT" Cathode Ray Tube

CSEL Consolidated Support Equipment List

DARCOM . U.S.

DARCOMP DARG0,;.vit mphlet

DED ,Data;'_'t

t DescriptiOn

rmy Materiel Development and:Readiness Command

.ctin

DEI Octa Entry ustructions

DID Data Item De'scription

Obb Department of Defense

-68- 80

'DOD

FMECA

HDR

How Mal

41.

Department of Defense Directive

Failure Modes, Effects, andCtiticalit,y Analysis

Historical Data Repository.

'.-How Malfunctioned

IDMS Integrate Database Management System

ILS Integi'ated Iogisticg:Support

LCOM Logistics Composite Model.

1RU Line Replaceable Unit

LSA logisticS Support Analysis

LSACN

LSAR Logistics SupportAnalysis Record

MDCS Maintenance Data Collection, System

MDS- Miss-idn,,Design, and Series

Logistics Support AnalysisControl Number

MIL-STD

MMH/FH

MOD- METRIC

MPN

MRSA

OLA

NSN

Military Standard

,Maintenance Manflours per Flying Hour

OT&E

PER ,

PMD

Spares Provisioning ModelA , q *.

Maqufacturer'sPart Number

DARCOM Materiellteadiness Support Activity

Network Repair-Levi.Analysis,:

National Stock Number.

Opertionoandipport

Operational Test` and EvaluatiOn

PataMetric Estimating Relationship.

Program Management Directive

Product Performance Feedback System

1'PL Provisioning Parts List

RM Reliability and Maintainability

SF.N Standard Equipment Nomenclature

Seq. No. Line Sequence NuMber.

SERD .Support Equ.ipmen( RecommendationS oement

SRD ,Standard Reporting Designator

SRU y Shop Replaceable Unit _=

SSC Skill- Specialty Code.

TSO Time Sharing Option

RUC Update Code

bllB - Unified Dat4aSo

VAMOSC

VSAM

WBS

WUC

ViSibility and lipOlent Of Operational Support Costs

Virtual Storat4q sVriethOd,,,;vi

...A 9

Work BreAdown'Sertdr6

Work Unit Code

82

ArlIrNDI X A

;-; AR DATA -HL FT

III I ,InDt 11I 1 \ COI.) .1 I II.: Ilk' 'kilt ' I ';

, I,;AR

I in t in I fill otor to

4

S3

S.

9

I

V

DATA SHEET A: OPERATIONS AND MAINTENANCE REQUIREMENTS

A/111

/411.1111 IL

1. '1,14

',Al N 1 1,1 'WEIS WIN..

-'14:1,1H1 .1,01,,1,101i4h'1"1.1 1 1 1 1 1 1 I 1 I

111411,

14111.11it HI N

1..111.1 1'11ID1,Il1 131410

'1111' 1 I I I I I

'.ACNN14.01114

!tit.1 I ,14 ,161 1H1'1111,1111:11114p,

,61,,41,1:1:i42.51L1 25 271.[12913411 3.;

CODE4 F 53.0AF NIL 111M ACRONYM

11 I1 E1_ I I 1 1 1 e I II I I 1

2 ITEM DESIGNATOR CODEI ITEM NAME

34

g OwG 9 SERIAL NuMHER EFFECTIVITY

Al .E7 iiiff9+121.414 (15146141 4814915 I F2153

CLASS FROM -It. TO

DATE

SUBMIT 1EU BY.

10 DATE"

YR MO

PAGE .OF

aa E X.T

5 T57

I I I I II II58 9 MM 13101

TYPE UDEL14, 1,Hh[20L-j.,:ii±ki.,021-24241-3-4,,hThhi 35 .36 37 EM 9 2 45 46 47

.5111114 4141

;1 It I

3.CONVSIONFACTOR

70 71 7. 747.a1714f7-1_ I I.

1:41

BC)

MI 491W 51 52 53 54155 MEM 94:31M 3 65 6 64271M73 4 51711M '9 80

111.11-31 PART NuMHER i 2 FSCM 3 DRAWING RUNNER

1611 71111119120121122123p4I51261211281291A31 33 3.M361j7

4 l ' ' I ' I A I I I I I 1 I I I I 1_1 1_1 1_ ,L, 1_1_, 1 1 1. 1A i I I I ' l " I 1 1 4 1 I 1 I I I 1 1 1 1 1 1 1 1 1 1 11 1.1 1 1

MI A`o HI MANI EIA',1

1I1t.411pil.11

311137,11411411:1-11FTP1` 4.4) 4iL6142151

I I I I

4 FSCM

It I I 1 1 -1 1 . 1 1 1 I-5

LI__ 1 1 1 1 i I 1 1_ 1 1_ L 1I I 1 I 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 I I I 1 1 1 11':1

4m84,N, At:NANINGRAIN 4% A

ANN-A 4

BA'47114ACIIIEV. I. I 141.N

NT l'ilAtgti4 r ;? t; MISSION CROME0oPtIREETDiOrt SUCCESS PRO

I . t 14 51!'111N I 9110111 li2115114115 )1.17 111119 42115fM.7128 29 3" 33 341. 4 45 46 48 4 51 52aatit.ed T

IIt41 I I I I 1 11111 1 11 1 1

N 41111 N

I.I

I 1 114

i' t

A 1q1

4 SW: II

I

1 1 1 1 1.61316_k(Az

1_l_ 1 1 1 1. 1 1 1 i 1 . 1 1 1 1 _ 1 .1, 1 1 _ I. 1 . 1_ ..1 t __I I. 1 a.,,,ANI:ATIoNA1 MAINTENANCE / ON EQUIPMENT MAINTENANCE AIR FORCE!. /AVUM ARMY i. MAINTENANCE REQUIREM NTS (RECO%) TO TENTHS OF HOURS)A NuMHER OF H DAILY INSP`

YR . ta .1I .1 A, N iTSPEMS SI IPP EYAILIAL__ .... . ...

C PREOPERATIVE INSP 0 POST OPERATIVE 'NSF E HOME STATION CHECK F iNTERMFDIATE INSP

I t, I 7 I N 19 1W 1.I Itli211 1114115 16 F1181-1472( 21 221A2.426 2-ThEi_LAS131 3213314136 3711E11291441 .11 .1 4 45146 47iiill

ma. .. .1 ,FA ,,,,_ AL. .144 44

CDEINIMEMMEMES Or .

;071E-4171441---""6 6 .667 6 69 71 72

t i l l ' 1 I H 1 1 1 1 1 ( 1 1 _ l i l t 1 1 1 ! I L ! 1.1 1 1 1 ill .1 lit ILLE

72 73 76 77 78 79 80

G Pt RIODIC NIP H UNSCHEDULED MAINT TuRNAROUND J MISSION PROFILE CHANGE K M/H PER HOUR L ANNUAL MAIN M/11

41+AN MAN .3 MI 44 414N n115 Fat AN 0.4. AA, ao. LLA5 WHEDULED UNSCIED01. ED SC4D111 UNSCHE Dth ED

mt AN

411-44414 {4-5 46-R14441_ 5152 53.154_15.5 W15-05* till6L-E-:3-k_-4/6. 6 7 GKITEaliT-...I'1,1,i81911°1"i'21"I'41'"4,114119P1 12 -12,1 T61221 ,LL1'. 2±1172,...9,_ 3

I 1 I I I I I 1 1 1 1 I l T 1 111I 1 111t l 1111IN? I HUT 111411 TM! I `,0PPOR I' MAIN T I NANCE .AFT OAT /THIRD k CHEF ON /OFF F 001PAIL NT

NOMBE F4 0 tt_WAILI_TATI 1,4 CHISK INTERI `,ACN T.11171 M SuPPMal tilt itit

Poi MAIN It NANCE I MAINTENANCE Ht 1., f Mk NTS I Rt (..111,10

( 12f NuMkik R OF 11 M/41 PER N1t11H4111t 51STE MS SLOP ',CHF DICED UN. IIFOUIIII

.21.1q:41,-.1.., 2 7 2Hk915451

AV 614N NW,

1.14 '.1' 1.191 41'111-1,1f:4P, 161:14-111,

IIIn 1 It! ILI? 1 it!! 11 1

- ARMY I MAINTENANCE REOIAREMENTS (RECORDED TO TENTHS OFevigac P E M Fi7TIFTiti A N.ALA.I.

r52 53 54 55 56t57

1 t

HOURS)

-1/11.4'h_3113 AN .., SCHEDULED CHE DUI E D SCR/ DU1 INWIlt DUI ED

33 pl.+ 1 2 4 45 4ti 47148 49

1 1 1 1 1 1 I 1 11 tiltU TENTHS OF HOURS)c ANNUAL Ulm T m/H

st HI DUI I 0 UN5LHF Dui 1 Cl

141 315413i36 17 38r19FILF11411`? 41431444?14 N149150151 152153-15415516.F 4585416LibPF46416516616 7168169P 711-7211:_41151!4771171317d01 1 . 1 1 1 1 1 1. I 11 I 1 I I I 1 tit Ili t. t t 1 111.1.1 1. I I I 1 1 1 1 I I'll.,` 11 1,(1,' 1.11FD ITEM AvAR ABILITY (IACONO IN PERCENT(

. ,.- .. ..., ,_ , ...., ..,,., m, 41.1.4 INAN, ../.4,1 . ./ ,,,, .1 P/4/ 4' 1,44, 411/14. 1.14.41 4 .144, u.em It , mt A, .11111 41.... MI J : 0310 /11../ i hal a ..,iou r, , .E., . t o ., 1, II LI 1 10 130 D _.....,....,

I I" rr' I 'I'. I _Il ,Fil- k1,--1,41,9 ',1.'1213 '4L-,1,,it '61-',1,,,f,i 321,11,413 361371.1439 44 I_142 44145 51 5215315415. 56-1-57158159 6+-1-Wik 3 64-161661.67F11( 69171rilli17174E,1761111DIFS so- ,_-,-- -,-

1 1 1 1

I HI H

iti It ITS it1,1TI III_ t.TA LI1 tit tij_._1_11.,c;TIM END 111 1.1 41411 ABU Ill ICONT INIIED) c2 NOT M SSION CilPABLt I NMC

.. '1-11 ... [7,C1( 0 Mt SU. P.D.C1( 0 NE Su.iu P3t I1 .:47.03.'177 !An! 414 14 I. 1- -14 _44_6_ 7.1S-L1 -14, 13.51 .5-ES5. 5ki 7.5!3 .__9.±1P4i 3 t 4-FiE16_7_ 6 l:16917ft 7.1±±11L76f7

f 121

F

I II 1 11 (1.1 I 1 I I I I I T__1, I t l III

3

DATA SHEET Al: SUPPLEMENTAL OPERATIONS AND MAINTENANCE DATE PAGE OF

. REQUIREMENTS. SUBMITTED BY E X T

..--..

7I_-...J

.....-

I

.

1

I. i''''(NumliF R ',

4717' I 3 1 i

. ', l SACN':2 .17TIMATED UNIT COST (FLYAWAY) 3 ACTUAL UNIT COST (FLYAWAY) 4 ESTIMATED 0 8 5

COST (ANNUAL)5 ACTUAL 0 11 S COST

(ANNUAL 1 .4IDJED,-Ac. rii RECURRING B RECURRING A NON RECURRING B RECURRING

qG-'1;f4f4 F T I 7 3 4 1516 i i i i : F 4 p o 2 I 22 23 24 2 5 2 . 2 7 2 8 2 9 3 E 3 1 32 33 34 36 37 38 39 41 42 43 44 .1 46 47 48 9 50 I 2 3 54 55 56 7 58 59 6 61 636 65 66 67 8 69 7 7772 747 78 7980A I I A

4 API)I41)10137 F4

_LEI, I4

1.,,.1 t 1 I _1 L 1 4. 1,17,71

L SACN ' 1 .,P-

75T8T 8 10 II- FrAa

_L. L__F_A, _L__L.A 1 _L_ L 1___L._ . l I 11 III...1t TNITIAL SUPPORT EQUIPMENT COST 3 INITIAL AND REPLENISHMENT SPARES COST

4 teSE MATERIAL COST 5 BASE PETROLEUM, OILAND LUBRICANTS ( POL )COST

6 '''''co>.

6,-P 'COMMON S 1 PECULIAR 9 E. A. INITIAL SPARES B REPLENISHMENT SPARES

8 rfiCOMEZIMMIMITRIMMXIMMEMZIMESIZEDEIMMEM1_1 1 I 1 L.

EGMEEECCOMMEEIMEDEBELIESOMMIECIMI

1_11_11 1 I

i4 MIMEO 9 80,_^ 1 ' I''.L "_.,_1.

rAPPNuMfit R

Tr' 1 ' Li_A 1 5 A

1_ 1 1

=t17'. 1 4 II,t'API)

..,,,,

ILI 14'Y .14 L

N, 7..11. 4

rELIZIMIXIMEGEMEIZLBOI I I__A__ 741,1, L ..1. 1_1_1 1 1.1 LIII_ILI__.1 1 IIII.i.__I

.,

LSACN .,

6 CM U mouramorliminum.I

l 1 ( 1 1 1 1 1 1..11

.L.BASE LEVEL (CARD AI3A) DEPOT LEVEL (CARD Al3B) 4 NUMBER

OF PEOPLETRAINED

S. NUMBERsENEW/MODSKILLS

6 M,._

U

7980

2 TECHNICAL PUBLICATIONS COST AND QUANTITY 3 TRAINING COSTTOTAL 'COST

2, 2.mem1 1 1 1 I 1 1 1 1

NUM: TA .1" "'llErli 'WM' PERSONNEL

4 WIERIZIEEEEEVIEZEIENEZB MATERIAL OUiPMENT

6 MENIESIZZIOZEILEEMIEMENREEMra, MEEEIMS133 ESIEEEEMBEDEELEGEMIZAELEIELO

1 I 1 1 1 1 1 I I 1 1 1 iIII 1 1 1 I 1 1 1 1 1 1 1 I 1 1 I

I._ 1 _L__1 1 1 1 1. 1 1

LSACN

I e I I 12 MI 4 51F,''''' I r 1811L

1_1_1_1_1_1 _1_1_1 1 I 1 1_1._2 PROGRAMMED DEPOT

MAINTENANCE COST(POW

171819 MOM 330...

3 COMPONENT REPAIR/

OVERHAUL COST

4, INITIAL DEPOT SUPPORT

EQUIPMENT COST

5 DEPOT FACILITIES

COST

6 BASE LEVELFACILITIES COST

7 ccw

4tuCD,-

Li

68K771-.)71 72 7. 7.rTI7iiiW.T179802:MMIEMEMEMMI qM E 7 Er, 39 Mali1 I Li. 1___L___1 II III iiill41454614 7-PTF1 9 50 51 545-i154 55 6 5 58- 9 0 . .. 3 4 65 7

1111_1_ 1__1_,_1____I__1._1__IIIIIIII

ISACN,

.,,,,IliTc,7-1112,3-1,L3r,,.,

iiiiiiiii lillit 1 1 1 1 1 1 )1 1 I 1 1 1

2 SUPPORT GENERAL MMH / F11_ . . . .. ._

3 SCHEDULED AND SPECIAL INSPECTIONS 103 804) MMH/FHA ORGANIZATIONAL. EvEL B INTERN MATT Lt EL A ORGANIZATIONAL V B INTERN DIATE LEVELI ALLOCii-117F8119

2 cnia_znizi IR2123

j ME A$ 1 ALLQC28129130131

Lf_R p32133 3

3 E.A

36 37 394I L 2 PRED ,magramminwariff..1,12F

A i ' 1 5 14

2,1125 2642 4 an 44 45CIE6

Ecm maim 20m . Ensmanomomm mmonso 79490

1_1 I _I: LA_____i_L_I.2 PREVENTIVEA ORGANIZATIONAL

I 1 I 1 t___ 1_1_ Meg. OEN 1 I I L 11.Aui,

.,11popi P

' ,I.. I ' 1 ''

__I__ - - _1

I ;ACT

'11'1718 910 1' 1' 13 4 NES

_I__IMMH/FH 3 CORRECTIVE MMH FH

__J__I__ _1_1 _L_L_1__L_1__

tinLEVEL B INTERMEDIATE LEVEL A ORGANIZATIONAL LEVEL B INTERMEDIATE LEVEL

I ALLOC

'7 I4

I I I I

2 FRED 3 ME AS DICIMINEI 2 PRED MEAS I ALLOC 2 PRED 3 MEAS. I.ALLOC 2 PRED 3 MF AS

20E11E2

t 1

24 EMEEDEEMEllI t i I 1 i

i' MICIMEIMEDESE1 1 i .1_1_1

'`'

41 MICE

t I4 C203314111121EIMBEIMIZZEI3

I t_

57 MEE 36,1_ t 1 I.

64 EIZZIEDECIMERSIONIZI 7 MEMO '''' "'-'

1 1 1._1_1__1__1-1 1 I 1,1 IALA

A Nt.

T,o 51HE ',

71.,21 J.:-_i 7 A

EJ: 'SgiE {4

71 ., I- 5 I. 4

1 _ 1 .1 1 1 1 1 I I

LSACN,

51r1181910 li 111431415

.1

2 TOTAL BASE LEVEL MMH/FH_I _t__I __I

3 MEAN MANHOURS TO REPAIR.1___2 _l___1_

4 MAXIMUM T411E TO REPAIR__I___1 _L_

ELAPSED TIME) timA ORGANIZATIONAL LEVEL B INTERN DIATE LEVEL

I ALLOC 2 PREDMMHTR ORGANIZATi A LEVEL B INTERMEDIATE LEVEL

I ALLOC 2 PRED 3 MEAS 3 MEAS I ALLOC Eimmummim I ALLOC 2 PRED 3 MEAS I ALLOC 2 FRED 3 MEAS161)-FI18 19 20 21 22 ES 7425 6 "'7 28 a 1 gmaggiamozam aggEmcnorpcommegman gpmemE fio mmpiimm c7 61,111.917TT 747717417, 7617 7178174 90

I 1 I 1 I I I 1 1

i 1 AC 74

"16_ LIR 12 1 1 ;) 11 i 112 11 3114115

I I I I II 1 I T. i 1 1 i 1 i _i_ t i. 1_1_1 L 1 t i. 1L l_i_l_ L i I t I i I ,__I2 DEPOT DINH/ FI4

.1_1 _i_l_ ___L_13 MISSION RECONFIGURATION TIME'

ci6

D1161/111111111±_DEPP I AINIENAK.f. _

B COMPONENT REPAIR/OVERHAUL

3 MEASA MEAN ELAPSED TIME 8 90TH PERCENTILE C KAN

CR1 WSIZEI ALLOC 2 FRED 3 ME AS I ALLOC 2 FRED I REQUIRED . 2 PREDICTED

45147 8 91_ 1_ L

3 MEASURED I REQUIRED 2 PREDICTED 3 MEASURED1611 7118119 26121 iniii 241-25Vi.12 29 29 31 32 al 34 gm 7 38 9 41 2 44

L

50 52 3 54 5 EimmmEtim 65 4 65 6 67 MISMEIM 72

i__L_L_

7 garg@mal 79,80

1 1 i'IRISW1

II IMIIFI7

IIIIIIIII1 7 A4 II

'''

L_1'L I L I 1_1_1_1_ i 1 1 L 1 1____.:_l_L_I__L__l_ Li i____L, ANALVTICAL CONDITIDN

__t _ .1.._ ___ _1 _t_l_ .1 .1 _I __L43. QUICK ilailiARQUHIL:LIME_,L_LI4_43DECT,OR (±col

MEAN MEAN A ELAPSED 01..51 B MAINTENANCE MANMINUTES C CREW 0 AIRCREW MANKINUTESu

ELAPSED TIME MAREEDEOPI I REQUIRED 2 PREDICTED S SE ASURED REQUIRED 1 PREDICTED 3 MEASURED SIZE I RIQuilECO 2 PREDICTED 3 MEASURED

71 :1. I 44 9 A

.'1_1r L'Ll9 '' I INIMMI 5 16 17 113101161122 I 24 5 6FAIMEI5C-'31 EMI 42ZEINEMEITIOXIKEEZ 4 6131LEICEMIIM EMISEDESEIEMMEMIZIMMIEBEICEICIEBEBRENE7 TrEMEI 980

1 1 1 1 1 i m I 1 1 t I i t 1 1 1 t 1 I 1 I' 1 1 I I I I I 1 17 1 1181 11 t Ittt 1171 1 111 111I1O

86 87

I

DATA SHEET B: ITEM ELIIABILIT'Y(R) ANt MAINTAINABILITY(M) C1ARACTERISTtCSDATE _____PAGEOF___SUBMITTEDBY _____ EXT ___A1JRNATEiJIILI7]

2 END ITEM ACRONYM 1 IR 8 DWG 9 SERIAL NDER EFFECTIVIT 10 DATE'LSA N IFOC /W8S/WUCI I.-.. I

NUMIIER CODEI. l

CLASSI

- OM I YR MO IDA

F R I F7h!h!k4T1iJ3 j2 27 2B 32 344 l3I39I4I 81 6I3 65IDE16I6Il7I it2113I74lIII8 01 I tl Li_ LL1 1 1 L 1JJl ILJ LLL J -I - I 4_L I_i ii II

CASDI

. tYicsIAYc cs oivE-_________________ ________ TYPE Nj_ * 34FACTOR

810121 Li I I LI L_I_L JLLJ I I L1L_LJI4_.LJA -. - 11_11 LI 1

Cor4 Nnsb.r LSACN I MFR PART NUMBER 3 DRAWING NUM6ER :C[

dJIiE [ii11 191[101I I2I311a15j6117118119 I2c(21 I22I28l24l25l26I27I28I23c3I j3? 313l35I36l 37 339I4c4II421*3I4445J46147I4el49I515I I52i534 53 16316 J65I667J68169I7c I72I73I74I11.76lfllTht

__i______I____I_I_I 1111 .I lilt I 111111 II ij__.l.__i__.i II I 11111 I II I III I 8 II! tI 111111.11 II

I III I Il i_ilJi I LLI 1 1L1 Ll_L_ LJ!_ii_ t_1tLl 11_I I 1.i1I 1 1 LLJ1J1INtAIN4ILIY ASF

_______2 BUILT IN TEST INTEGRATED TST SYSTEM (CITS'A0__________ 4

4 II Ii LIINRE8LSACN ___________________________________________________________A FAULT 1%)

uLTISOLATIONc%ir

'

5ff3j4 3j 67J4ji4II jl2jI3{I45 6 Il 18 9 2) 22 2 27 28 31 321!3I34138 36j57j38j39 4IJ4 41 8 49JTSl 52153154)5336 I 3 4 6 0 7li2jlSjl4}TTJl6Jl?)YOjl9

CARl)

NIMRURLSACN

1L....LI4BtLITY I .S -.

IA MEAN TIME %TW EN REMOVALS HTBR B NI N TIME E'MAJNTENANC2 - MTBMI ERENT .'VP6 I NBM -I ALLOCATED 2 PREDI TED 13 ME.SIJRED - I ALLOCATED - 13 MEASIWED II I ANIOCA'jE0 5 SMEASIIRED

iI_J3 1! 516 17181 IO[iJ.1iF4 IS 161I71181191 2! 22 .k!9k141I42 49I5Ij5II32I53I5453I 8[59Iéc162I 1t?I7I 72j'1i4j17j77j1

C LLLI L LLLJ. ij_i I iJ_1_LJJ_IJ_L_I I I L _L_L5LLf !_L._LI_ _ I I 1i__ L i'1_i_t \14I I I I LtIL-81LNT!N1if 8IkAII TII -*.I4,.

4flLSACN IA INDUCED M8I.jI.RITION - TWE2M B F DEFECT - TYPE 6 MTRH i NTI 0 REMOSWLI Il71 84'L lu

NIJMI1ERIt PREDICTED 12 MEASURED I PREDICTED 12 MEASURED I Egoa- 12 MEASURED _.

ijiJf 5j6 [Jj]IlI2II3jI4II5 jI9I.3I245l26j27 2 I 2 I49I2l534l536 SE SB 61 3 67 8 9!14IIT13l74W78I7711el

A ji

ICI _L I I L1_i _LiL I L I L_L_! _J JS_L_LLL L_L _J J_ _LL_lL4_IL-_L L_J 1_LJ,J I i_iL. t4 Li 1 i 1 L I L L L,

NUMBERLSACN

IJ.E!I..i.t!!L(ALY$IS __' 8 ?

A FAILURE MODE 6 PNLURE S(BIPTOIS - 4 _ L(RE. EFFECT _ AND CRITICALITY ___ F T5K CE'

jJfl 9 0 1112 13 14 6' 8 112I73174l7!l76t77l789 I'

J_1_S.LA _11 I I_I I _ I _ I I I __ I 1 1 I _ I _ I I _ I _ I _ I A _ I _ I _ I _ I _Ii_.i_0j_L _ I _ I _ I I F _ Ill _ I _ I I I _ I I I _ I _ I

I LI _I_iJ_L_LlL_L_IL I_L1_I_L_I_J_LL4 L11 I,_LL4_,J_sIjl_II.II.II.LI_I II_I_I)I1 I IiI _ I' 4_i _1L03.ILi1_

BLOI6tAIL1LSACN

LLLLIIII008 I T IW5!9iIRj4DIR __J 10

i 01 7 1A

_____LSACN

I L 1_I L_Li 1 .1 L

IY;i18)CTION S__S F _____ 'HLLJ__L1_L_L_L_L_L_LJ_L_L_L_L 11J J_LL_L.J_4_I_i_i4_I__LJ 1 1 _ L_I-th-L4 J ILLJ! - I_4_I_J 6' 1 I_I I _ I J _I

11.1Cold N6e

1 111111111LSC___ IILLl1_ji.LIl4JJ tiiiIIII4AlI1 WT1IQUALITATIVE AND QUANTITATIVE MAITA84ABIL QIJIRE I.EAR I-IA EDNARACI!TICSFAI_S4NIJ1RONMEN _ AL, fTC _

I _ IYI _ It I i'1i _ I _ Ii _ III I i I IJ8 I LJ -

l 2f3 jI 5IIn18t9t 2I3fjI5

I

6131j14f .i

Ca d1(oAe, I_MANTENANCECQIdC5PT S!QMO N

I

______LSACNi_i L_L_I__L_L_L_I_L I _ I _ I _ I _ I I. 1.i_j_L. '-F I I _ 1 _ I __ I I 1A I _ I _j_J1 L I _ J_J. L L.L_ -

1 dACN1 1 .iiHii. L II iIL I4I_LL I_L _____________ i __ kijil Lt __ I' _ I I

Co14Nsrbs I

J1L_ _LI.1_i_lIi_.I__L_.L_ Il_L_j _ I _ I _ 1-1 1_1f 1 _ I _ I I _ 4 I I _ IL.i_1_J_j7L_.LJ__L.._i._I _ 4 _ t _ I _ I F I 11 I I I I _ I I Id 11 L III _ -I' _ I

5 6 7 8 9 '0 II 12 13 14 IL .4 17 18 9 21 22 23 2 25 28 SI 32 33 536 37 38 .7 C

l's,

4N

..

DATA'.,

SHEEir : M RELIABILITY(R) AND MAINTAINABILITY(M) CHARACTERISTICS DATE, PAGE OF

_. (SUPPLEMENTAL DATA AT THE TWO DIGIT WORK UNIT CODE LEVEL) SUBMITTED BY EXT :

-

....,k4.i ..e.

.

.

,,.,;,1

,--.1 4`;,s.i,

ateI '

.

) .

!'.

10:.

.10

-,,; --V

.

CARD;,,

N,,UTAFIER

, 114.2

11,;,4, I 44 ..),

,", l.CARD: ,;

NumITEP'

112131<ir

4 , 2 I

,

""t

LSACN

.

610iFOTIT112-171-17.i-F;

I BASE LEVEL MAINTENANCE MANHOURS PER FLIGHT HOUR

A ORGANIZATIONAL LEVEL ION-EQUIPMENT) B INTERMEDIATE LEVEL (OFFEQUIPMENT)

I PREVENTIVE 2 CORRECTIVE 1 PREVENTIVE 2 CORRECTIVE

A ALLOC B PRED C MEAS A ALLOC 8 RED C MEAS. A ALLOC. B PREY C MEAS A. ALLOC. B. PRED MEAS.

16 El it3 19 20E322 23 24 25E327 28129131i31 32133134135 3613713439 40141142143

L .

4414514614T

t 1

4449150 51

t .

52153154155

. t .

56157158159

. t

60161162163r16466167168169170171172173174175 76177178179

1 t, LI t , t Li.80

,l_ .i.` 1 . I- ',.. L_,.k, _a,,_

' t,, .,:(I. L SACN

5161 1 1 In1 1 V I?AL? 12,1_,1_1!2,12r4,5

1 1 i .... t 1

1,_st.....1_,.,... L.._,,,,L_, _._____,_ .L,_____,._i__,,_. A., _l____ L.._k_,_I_I BASE LEVEL MAINTENANCE MANHOURS PER FLIGHT HR ICON'T1'

1,,_.

2. BASE LEVEL 3. DEPOT MAINTENANCE

MANHOURS PER FLIGHT

HOUR

_1___._ _.a

4 MEAN TIME TO

REPAIR (MTTR)

=,

A TOTAL BASE LEVEL 1.114H/FH A MEAN MAINTENANCE MANHOURS

I. PREVENTIVE 2 CORRECTIVE 1 PREVENTIVE 2. CORRECTIVE

A ALLOC B PRED C MEAS A ALLOC B PRED C. MEAS. A PRED B. MEAS A ALLOC B PRED C MEAS. A ALLOC B PRED C MEAS A PRED B MEAS

141E312 20T2112423\2412512612 28129130131 32133134135 36137138139 4E441142143 444514447 48149150151 52153154155 56157158159.0616216.3 64165166167 6816470171 72173174175 76177178179 80

II It. . t . t, It. ,I. I . e f 1 f T i t

Dtim:

1 4,14ISACN FAILURE CAUSE

,

SEO.

NO

1 Il1-1_4_411.6/1819H ', A._41.

10 11 2 13114115 16 18 19 20 21.12.4411_7425 261_2712131221A3_1_132133_13_4_M_34,3115d_344441123A±514447h814417 58 59 11Q1 6 316 41 6 36El671681691toll 11721731 T4616.771781791 l L-1-1.

80

a .......,

1,..,. ill I,

: ., F

_,

I SACN

_I-

I FAILURE DETECTION METHODSE0

NO

,, , ,,1 6 1,1,495y, pp 310115

, , , , , , , , , , , , ,_, , , , , ,16 11 7118 012012

..:

DATE' PAGE OFIp_DATA SHEET C: TASK ANALYSIS" SUMMARY ..

SUBMITTED BY:. lir EX T

P

I

-.105

1

/

CARD'

NUMBER

_i jd 314

1 LSACN (FGC/WBS/5111C)

5 Fri FT 8 CIIMI 1 ffj 13 El 5

2 END ITEM ACRONYM CODE

16 02030:11EMEnga 24 25

4 FSCMSR

26 27 EDMES 31

14.-4 Y

i,..;03, RE.

a Damao 9 SERIAL NUMBER EFFECTIVITY. . 10 DATE.. i!FROM ! 1 YR MO' DA

32 33 34 35136137 3813914C141142143144145146 4814915E451 15215315415515157 58159 60161 62163 64 65166167168169170171172173174175176177 7817980C 0 1LA

CARD

NUMBER

1 11 It 1 11 1 1

LSACN L"

,0

6 7 01311111110111811111DILIIIIMIESSIMEE24EEMEGECIEDEEMESEEMEMIDEUE4IIMICECCOM

L, 1_1 1 1 1 1 1 1 1 1 1 L 1 I 1 1.____L _I _Li_ _1___4_._ l 1 L A 1__1 -_1_2. ITEM DESIGNATOR CODE ?

1 ITEM NAME `1 ,

t

SAN

t 1 _1_1_1 _1-.1_1 _L 1 i

U

TYPE MODEL St.ern SUFFIX FACTOR

54201:13MIZIMICEMEMMI 2 3 4 71:111MEE9113i 53 5E721111X1MaialliEMEILIEBIE 9 BO

,C.J.P. 12.. 1 .'

CARD,

NUMBER

.1- L-1.-1-1-1-..1-1..., I.,..1.-

LSACN

-1, ...L..1-.1-1.- 1 .1, -1 .., I .!---1--1.-...A.---1. L I 1 1 I 1 I,,I

I MANUFACTURER'S PART NUMBER

-LV 2 r CM.cc

32 33 3 36 37

ti

....1-.1--.1 .,.....t..1 ...!--.1 -Li3 DRAWING NUMBER

38 3. 0 41 42 434 45 4. 47 48 4. 50 51 52 53

1111

z 4. FSCMcr

54 5 56 57 58 5.

..4---,I _ ..L.--1-1,Z,..,-I-.5 NEXT HIGHER ASSEMBLY PART NUMBER

60 61 63 64 65 6.67 68 69 70 71 72 73 74 7576

4.1 .

t±'

77 78 79

U

801 2 3 1 4 5 1 6 17-18 19 110111 112113114115

111111111116117

I

18 191221

1

22 23 241251261271281293031

111114-,C_191_31C 0 3 B

1 1 I

CARD

NUMBER

1 1 2 r, 14

_ 1._.1 _.1 1 A I_ 1 L_-1-_ _i____1_1__.1 --1-1 _..1__ 1 1 1 _4 Jam_ 1 1-1_1_

lll 1 111.1. l . 1 1 , 1 1 , I

1111 lll II1 II1111I t 1 ,__I

LSACN.

516 17 re f9 Fol.! iTr2Tifi7F5

. -,__,.__1_,_),.

TASK SUMMARY,,__.74__11 .I. _, L _L _1_11_1__1

PERSONNEL SUMMARYI TASK CODE 2 TASK 4 ELAPSED TIME (REC TO 1001hs OF FIRS

-,R jE f,a a

7 SKILLSPECIALTYCODE I

Y.

S ul

9 NO 10. MAN HOURS (REC TO 100ths OF HRS) II. R ONTS FOR

16 17

WPIIIIWKIILey_____A___

18 19

FREQUENCY

ECVENCYTO

(THOUSAND)

A

3ALLOCATED

ST

a

PREDICTED

,36137158139140

C

MEASURED

,41142143144145

OF

MENPERTASK

56157

A

ALLOCATED

4. .58159160161162

B

PREDICTED

63164165166167

C

MEASURED

68 69 70 71 72

1.7

n2 F

731\75

SUPPORTEQUIP

dGROUP- 3INC IDNO E

76 77 78

t.,

Ii

79 RO20 21 22 23 2412;1261242FF,

30 31132133[34155 46 4748149150151152153154 55

C 0 4 AI I 1 I 1 1 1 Ti 1 !tilt! 1 l 1 1 I 1 I 1 1 I i i

, 1111111111 1111 I. I It I I 11 1 l 11 I IIIIII I 11,1 l'ItlI 1 I t 1 1 41:21111 , liil I Oil II!. 1 Ilt t 11111 1 I lilt 1111 I 1 I.l

, , , , Iii,i 1 tfit1 lilt l 1 I 1

t 1 t

1 i t t

It1 1 1

I

I t t I

I 1 , 1 1 1 .

1 I Ir I

1 t I I

I 1

I 1

i 1 I

I 1 I 1

I t t t

1 t t t

Itttlii I 1 1 1 i

I ' t t I

I , , I

i , I t , I

11 11 1 1

1 t I t 1 1

I ; 1 l 1 1

1

1

1

t

I 1 I t

1 1 I 1

I 1'' I 1

11, TiIII!

t 1 1 1

, t

I 11I 1 I 1

1 l I

i ittI L_t__L:_.

111_1_1 i t 1

/-

1 I [

1 T l

1 , T 1

_.., r ,Jill_dJ 1 I__L

4

1 l

1 __L__

1 t

it.

- L - 1 _ 1 _ _ 1 1 I. 1 1 Iiii__I_ ._I__1_____ t I I 1 1 1 I I l 1 1 1 1 1

Ili.11I I t

I 1 t IIII--L__I_._L__ 1 111. I tilt1___,____1_ ,_ , , I I , , I ,

11_1 1J I it l'i t'l 1 Ili, I i I 1

_ _1_1_1._ 1L1 -1 1 1 1 I 1 1 1 I 1 I 1 1 I I t_i__1 J_ __1_._ _1_ I it. t 1 1 1 I

_1__L_

1 _L__1_ i 1 i tile ,1111I I 111 I itl I It 1 111111 , lilt t t t 1 I I

I 1 4_ _L 1 i_t___LIL 1_1_11 1 1 I L L l 1 , 1 i l L

'41_1_1_1 Jilt I I t I I t I 1 1 t t t 1 i ' t 1 I t I I I i_1 2 1 1 t__111 i l I I 11 1

_i

1 1 I , I 1 ___L-t_t_l_L-1-t I I 1_1_

i I I

-1 _LILL_L .1 J. 1

__I _Lk1

I 1- ,

__11 __L_1

1 _L 2_1

__I i___I 1___

_-L__L__t__L_

___I. _l___T__I__

_1_1_4_1_

LI_ L_,I I t

_l_l_i1 1

_.L._1.-...

_l_i_Lit _

_ _ , ,

I I L 1 1 1 I 1 1 t

-1- _ _ _L__L_1 1 I 1_ 1 I t 1

, i !mil1 I I

.__1 _1_1_

t 1 -. 1.. i _L__L__I

_L_I_1 _1_1_.I t I t '.4!_t_L_.___L-_L__L__L_

1_1_ I L_

J___I___L_L_

I 1 I 1

_1_1 I _t_.'__I__ _..L_ _I__ _

_1_1 _1_1_1-

I _I J 1 1 1_1-1 Li I t I

_L_

1 .1 I L-,_1___i_a_t-1_ _t__1_1

6'1 1 I t_i___1_-. L_

t I

1 l L I. _1 I 1_1_1 _L...1-

_,_ _I_ I _ 1 1 1 _I _L-.L_L_L_l_

-__T_._r__i__ 1 1 I 1 1_1__.-_t_ _i__.1

__1.__I A _1

_1._ _t_T___I_i44,......1.

-.1---1 _-_-_L_ .1__I

L__t__,L

_ ___ ..__L__

111,1 __..t__1_,_i___

5457

_i_i__1__L_

__L_L,_

I_Li_1 1 1

C

IIILIL_L_LL1 1 2 5 4 15 1-E IR 1 9141 112113 174115

..L_I__I .L.

t 'I_J___I__I__1_

1 L_i 1 a L_ A._ L

46 47 44915( 51152153154 55

_1_1____

1.6 '17 11174. 21. 21 22 23

_L__L__C_L__L_,

241251262571213129

_L ..i .1

30311-32133134135 3613 7.138139110/414214 44145

___; .___;_i __L

5/11546-0161P63164165166167 68169170171172 /3 74 44...7617; 78 79 80 93

...

14. DATE : ' PAGE OF'MAINTENANCE.DATA SHEET 0:. AND OPERATOR TASK ANALYSIS Pil'fSUBMITTED BY: EXT

TANN "IDENTIFICATION I . .

1

-- .1

--.1

.

Ni' R :...---I CONTROL. NUMBER 2 TASK CODE 3 END ITEM ACRONYM 4 ITEM NAME 5 MANUFACTURERS PART NUMBER 6 F S C7 1 T 0

70 DA

2 3 5 130110 °MS 3 MIMI

A16 MI IN FIES2I 332

L1L_1__11I

24 EIZIMMECISMIIMESIEIMMESECEDMIKEICEICLIZZICEEM50

111111II_IMEEMEIMEZMIZICEMZEDZI3E33

ILL11_1111_111LLIII67 MCDIEMBEIMENIZI 794 80

D 0 i,_ 1 _L_CARD

5111,1113

I ICIICIIII 1 I 7 1

I L 54 CONTROL NUMBER 2 TASK CODE 3 TASK IDENTIFICATION44, 5:r.4a. II c.., nor

HOWMALCODE

7 REFERENCEWORK UNIT CODE

e IIIOIN.411

l.,

11 3 4 5 auciammonao IA gram9 20Egoga 24 2511111 30111 34 mama= 4oal 42 43 mmcnommam 52 mmma3mEmmammi 64 65 66 67 M69 701111/1/1 79 ND

° , ° 21 i i iiiii ,.1.___ACRO,,,,

, 12 I 3 I 41 SIN5 F6 F

2 SEQUENTIAL TASK DESCRIPTION 3 VE: uxtrer" Es'inii% '''f-4191-1011TT

1 1213 141" 6 17 '6 19 4 2' .2 333MEEIMEIMEIESIMERECIMBEEICEIMIZIE11=231:15171671MEIMSIMMOMMIMEMIMMIIIMME1 69 Ei 71 MGE16211113MIZIO 60

0 0 5 A 1111111/11.11111Iil==WIN11111111111111

_

1 1

_ _ __ _ 7_1_7_11_1-1 1_11_1 1_1_.1_1 1_1__ 11111.1111 1 J---/- =WI

_L i___1_, 111 1 1 a " ' 1_111_1111.11111.11=

8 9 10 11 12 MOM 7 18 19 20 21 /23 24 25 26 11111 411134 11371140142 431111.1 49 5011/111111/1163ECM 66 67 . 69 70magrammomamm 80

_1_111111I1_1__1..../_1_1_11_1_11/11111111111111111111IIIIIIII.11.111111 ErI I 1 " MIMI

'.i__1

1.1.11.1MNMINN.

-

6

.

/11 I_ 1_ 1 121_ 7__LI77.11Ji'1.1.1;7' iiiiiiiii___L_LA

, . 1 1 iiiiiiiii , L_L_.7_,_ ..A.-1 _l__L_17 1 ' 1 J 1__L__I_, I I *. L 1 I A-1_1-1 ' ' . ._1_, .4_1.

8 19 101141211311415 16 17 119 4 21 MI 241126 / 26 29 301133 34 gm 310 34i0j4142 43 4--r;ITT*4-6-14-iW1-5-44i$45M45 1-515i31-A6016p M63t zi 67 11170 71 12150/ 111 80n 1 i. ,

1__i_ I I I I 1_1__1. I I I 1 1 1--1 MisommramounsI i I 1 IMINNT1111

L 3

_

4 5

_,__

6 7

__L_L_1_1__1/__L__11_1 1.1-1 1-L L:. A L 1 L..1__4__I 1_1_, . I I I / 7 . . a_ _117 .--1_11-1,__ 1_1_ 1_1_1_1 a I I I L__L__L `,.. 4, I 7 I I L...J.1 I 1 1 1 1 1_1__Li,.I._ _1'._1 1. 1 1 1 1-1-L-1-1_1_1 i " i i 1 1,-1-1,-L-L---1-1 1 1 1 7 1 1 7 I a 1 1 7 I 7 . t 1 7 I 1 1 7 1 1 I ' _L-L__.1 ' I I N--1_1--1_1_,

8 9 10 1 I 12 1 3 14 15 16 ®1R 120 11M,3 24 126 27 28030132® Emm0 39 40142 43 441111111 52 154 55 56 57159 .4 I 163 64 66 67 68 70 71 M 73 74 Mn=0 () 3 i 1 1_1 1 1 1 1 1_1__1_1_1 I_ L 1_1_1_ 1_1_1 1_ I I . 1 I I I 1 1 1 7 L t 1 i 7. 1 I I I I I 7111.__1 1 1 1:_1__ -1 .1__1__1 i

3

.1

-;

4 5 6

_L _1 _1_1-L 1 1 1 1 1 1 1 I L_ 1_1_4_...1_1_1.1.4__L_L___1 _I_ ^.lllll .1111 I iiiiii 1'1'1.11.11.'7 l __1__1 _L_I I L I L L I 1 1 L__:L_Li_ _ _1_1_1_1_1_1_1_11111lia

1 1 1_1 1_ 1_1_1 .1_L_L 1 1 I 1_ 1_1 1 1 L /_1_1_1_ 11 1 1__A__L_L_A I I I_1_1_11 _1_ _l__L__1 _1_1_1_1 _1_114_ ....,_,MININ111

814111 12 13 4 5 6 17 IN 19 20/1124 25 111281111134 11M6131140 142 43111471211 52 .. 1111111111,411163 64 67 68 70 71 rimgamptgoop 80

t ,) 34111117111 1 71 11111.11M

_

3 4 6

.11 L 1 L., ttttt I. lit1,1-_,--_11__1., _1_1 -1--1 .121._.L11.111i

1. 1_1 1. i A I A A i__L_A 1 1 11_1_1 1 1 1 1 1 1 1 1 1 1 I 1 1 A 1 1 IIIII1__L_1 1 1 1 1 1 LA 4 i_y_. __L__l__1_ A

1 1 1 1 1 1_l_1_1_ 1 1 I 1 J-1_1 1 1 7 ' I. I 1 I I 1 1 I 1 L_L_, . 111.1.111_1_1 .1_1___1_1_1

Rtdi0111144411447 iR 19120121122123 241426 27 9 29 30 31 32134136138 39 4( 142M01147 :1501152 3Q ©m ®58 mem 62 63 64 67 68 7.71 ©7374 mem m 80

I 3 '. IllIllit ilitIA A 1 111 ...

I 1 l I 1 1 iii 1-1-- . L.

e-

.__LIAAIIIAIIIA1 1 1 1 11__1-1_ 1_1 1. 1_1_1 1 1 1 1 1 1 1 1 1 1_1_L-1 I I 1 /,,, 1 1 I 1 L_1_1_1_ .1-1- __ - _4 _L

I c I c._ i__, / I 1 1 1 I I i i i i A I 1 1 1 1 I 1 I ' iii 1 ' 4_/_1 _1_ _L_1__1__1

69 70 71 72 73 74 76 7 TB 79 80I 7 3 4 5 6 7 8 9 10 1 1 12 1 3 114 1 5 6 1 7 18 19 20 2 1 22 2 24 2 P . 2829 30 31132 3 34 35 3 6 738 39 40 4 1 42 43 44 5 6 47 4 50 51 52 54 55 5 57 58 59 61 62 63 64 5 66 67 6B

, :-AHD,,NJYFIF

, Li , t4-,i SSC. A

,16171,,19 ,T-,-

MAN-HOURSA MINUTES

MAN-HOURSB MINUTES 3 SSC C

MAN -HOURSC MINUTES 4 SSC D

MAN-HOURSD MINUTES

MAN-HOURS 6 'TOTAL Il5 SSC E

E MINUTES ELAPSED THE

,,t,IFi [15 6 2011 24 126121 30 31 32134 35 37 38 39 40 41 42 Dom= 47 48 4 5052 mcmmicomomm 64 166 67 68 69 70 pmemmo la 79 BO

4 94

DA A All a 0"A '

O BEICM01100 DENIM El Ma EMEAMESIMEZEMEMMIEMICIEMEIMMIZEMMOOMMMESE11=====r ISM SIMMEMZIENE

IMEla 001000EIDEEEEMBEEIMEMELIMMEIMMEMEMENZEIMEICECES=MMLBCOMMEDIMMEMOMMEMESMEMEEITICEMISIMMEMEIMIIM

AloulmoupoD 0 5

UMMEMEMOM.01.000000

D 0 5

EM.OMIMWEI

10

10

10

pummangingmmemommomommecrammcmmmmmimmmmmmmommmmmmmmmmmMOM= 1OMMEMEM.0.001.0.10 0........O 0.0110.0

MMOMMOMEIMMOMMIMAIO=0.010.10.

0.00.00.0.00.1.0

OMMOSIMMMOMMOMM MMMMEMMEIMMCMCMLIMMEM.MMMIEMMEEMMMMIMMMMEE=MCOMMNNW.........

20

25OMEOMMMEMEMMOMMMMMIMM=MMEEMMEMEEMEMMEEMMT.M_MM

70

70

70

SO

SO

S0

iv 111011000E1000111EEIMINICOMMETZEZEIMMIMECEIMILIMEMEMMETIOICEIMI=EEMEEMEIMEE=MIMMEIKEESEGIUMMEIMECCINM= 1111111111 11111111111111.11

O 6 El 001.011.11101101.100110.111.01110011111101110MI 0.0011MMM10.00.1000..10010.011..110.MO D 0.00.00.00.0.001..1.010BM MOMMEM1.0.0100011.01110010110.101101.1.11O M 00100.0.0 .00.0000.0101.10000/...0

O 000 MNIMPIIIMIll 1111111.111111011MINIMMUNIMIMMI

3 SSC

D 0 6 A

D

0

0O

0

DATA SHEET E: , SUPPORT AND TEST EQUIPMENT OR TRAINING DATE: PAGEi

OF.

MATERIAL DESCRIPTION AND JUSTIEICATION.

SUBMITTED BY: EX T :1ALTERNATE LSACN L , L -.....---

$.11213

...T,

I

.

CARDNUMBER

TRDIFI

E 1 °I 1

CARDNUMBER

I LSACN (FGC/ W BS / WUC) 2 END ITEM ACRONYM' '.

E DWG= CLASS

9 SERIAL NUMBER EFFECTIVITY 10 DATE , II TEST SET.

L5ACNFROM TO YR

qfl, R 0 10 1 12 in 16 nocommem25: 2,130,0aram .seel 7 IMTI:MTIMITIMMTIMIIMMIMMITIMIMMTIMF:3FITIMM:169 To 71 72 73 74 7, 76 77M 79 BO

1 1____1_, 1_1_11 1 L_1_1__L__1_ 1_1 Li _L__L__L__1_L _I L _1_1_1_ , _ ,

uL l. 1.....L _ L _I__ _I_ 1 1

L SACN

_I _1_ i.

2 ITEM NAME

__L _L3 ITEM DESIGNATOR .CODE 4

cosocluoort . B ITEM NUMBERMODEL 02111=1232:111111 [e

INfi.92e. /WIZ

NtAIRIR4

0 1 34A

_ _ _, _1_1_ L __I_ 1_1_ 1.

LSACN

OEM I 1 I t

u1 _1_1 1_1- .L___L___I-1._ 1 1 .1_1=1_1____ _ . _ .

2 MFR PART NUMBER

__I

t, 3 F ,S C 1.1 4 DRAWING

.1_1_1

NUMBER I" 5 F S C M

_1_1_1_1_-

6. 'CONTRACT NUMBER

Ti ono 910 0000 15 18 11111:111:103111123ECEMED9 3°31 37 MEMESEMEIEEMOILEICEEDITIMCCIMMENGEMMIZIMIZIM 6P 1:11MITMEEIM26? MIMI 70Ina 3 MEC 77 79 80. ,.4.' 1 11 I l 1 1 1 1 1 A. I I , 1 ,

I

.. It I I I I I

l ; 11---1. , 1

U7

.14

,Itt.1.4 1 g

C. A ODNUMBER

1 121314-

EY-) 4 i

CARD

NUMBER

E1M1

1 .I___L 1_1_,___L__ I i_e_

' LSACN

1 ,__ . I. I_1

2. TYPE

ITEM

CODE

1 , , I , I ,

3 OPERATING_ _I j ___I_L

4 STORAGE 5 re[

PC.'"cooe

_1-_. .1___l _1_

r.A

LENGTH0

WIDTHC

HEIGHT0um r

E FWEIGHT 11111

A 1BLENGTH WIDTH

CHEIGHT

D Etot T WEIGHT LNiT

5 Daum ,0 mmeg ,4 15 16 12 13 19 Essmaim26 27 ms 30 31 32 3363 MC3 138 39MIM 42 mmcammmmEgm 53 =MITE 61 62 63M S 66 .7 migi mm631E017 al 9 80

uD

1 _.r_,.A.LA_L L_ u_t_ _I

, L S A. N.

s-.

1 NI 1_, i 1 i t i1 _k____LJ___ _1_1_1 1,

.1 3. UNIT COST 2

.. A.

:. (NONRECURRING)

_L. I _1 L___I

4 UNIT COST

( RECURRING).*

2 5 TOTAL.

2' QUANTITY REC6 EXTENDED UNIT PRICE -

T 51.11.

1:7,pm -

_L__ _L_L_.1 9 TEL

CHANGEo CODE

_LL11_1 l_L__II

I I I_ i T i I 1 f t t. _ _ 1 ..1 _t_ A L__L L___L_ 1-1_1-1-1 A__A I 1 , _L _L_ _L__Lt_

TEST MEASUREMENT AND DIAGNOSTIC EQUIPMENT

cal°'NUMBER LSACN

5 OnCIDEMD31310 15

2 PARAMETERS MEASURED. OR SIGNAL PROVIDED' (T MOE)

16 MIMIIMIIIESECEMIZSECEI3°01EEMIZIEECIESEDEMalD3M:12C2MMMCEMMESMIZIMIMMEIDED8*

3 RANGE FROM 4 RANGE (TO)

MEI 77 IE 79

u

80

--,,VALUE 11111=1=131611011111111.11grIll.

MI'MEASUREMENT TERM

3.1IMEMZIWITI 374112 3 4F . 0 6 I L I , , L L , 1 A m . , I I i 1 1 1 1 1 1 1 1 1 1 1 1 - l 1111.4i I.-l1 1IIII 1111111 11111Ili1 IIIIIIII Illitti 1 IIIII,

.11111

.

CARDNUMBER

L S'ACHTi TOLERANCE PLUS I . 1 6 TOLERANCE .MINUS ( ) 7 No 1.,

8 REMARKS um

eoVALUE ... MEASUREMENT TERM VALUE MEASUREMENT TERM

2 3 4 5 6 00010 MIMIC 15 16 M le mEEEpag 23 Esecrams 30 rammmgazglancEn 42 mancomcmm52 ogpmpEsmEs 61 62 MiMajli .9 To00 T3017,077 0 9

E 7 , , I 1 I I I I ...1 t r t T I t 1

111_11 I

1 1 1 1 111I I I 1 i I 1

1111111 11,11111 1 t

I

1111111111111111111111111111I 1 1 1 l I l i l 1 1 1 l 1 1 1 1 1 I I I 1 I 11 1 1

10 , ,

1 I 1 1 1 1 IIIIIIIt _ 1 _ 1_CARD

NuMBER

1- 1

s

_1_1_1_ 1_1_1_ 1L 1__LLSACN

1_ -1 LI L_I__1 ,2 JUST IF !CATION ( INCLUDE RE ASON CRIT cAL DESIGNATION, CARD E02, BLOCK 6 y

4

5COUCNCENUloec.

77[7817980

.TI? I 3 4 5 6 IM 8 010 MEMO 15 16 M F8 CO iIjiir2ii325 2. 7 28 mamma 5 mungegi 42 MI 4 4:MMT:MM 52 MCI:TIMMS. :61 MMTM 66 M69 70 71 2 73 74 ill 6

E A° 1 811EARD

NUMBED

1_1_1'1 PAHE 11111111 1_1__111111....11 1 1 1 11_111111 I 1 1 __I 1 1 1 I 1_1_1_1_1_1_11_1_1_1 __L._ L__L_I_L _1_,L,04014101[

NumetA

_uI 1z_l_ tz .i 1_1 I

L S A C N.., .

2 DE SCRipT ION OF OPERATION /FuNCTION,

E , I I , I A i I I I i I I , I I I I 1 L__LA__I__L_L I I I . I L_I .t_liz_L 1 _t___L_I 1 I I t I I L_L__r___L_ L 11 1 1 I I I J:. 1 1 L L 1.._

MONK Cmummy

L.,

L.,7

10.,_9 ,

CARDNUMBER

, , , .,

4 L SI, C N

_L.,.

.CHARACTERISTICS /NARRATIVE2 DESCRIPTION,-

E .1 1 LO iCARD

NUMBER

1 1 1 1 I I '1 1 I 1 L J. 1_,_I_ 1_1_1 I _._i_StOVENCENUNIER

I 1 A 11' L_ 1".. , _L____.LSACN

1 it III II11:1111.__I__L__I___LLIII _L__1___L__L.,__L__ _...1LI

12 ADDITIONAL SKILL. SPECIAL TRAINING REQUIREMENTS ..

E 1 ' 1 ' 1

CARDNUMBER

I A 31_I_1 L.1 L A 4 I I_ 1 A I 1 i 1 i I 1_1__L_L_L I_L__,__4_ L_u1 1 L 1 _L 1___1___LL_1_

L S A C N

1 1_4_4 L.-1 1___1 .1..._1:_l_1_1_1--1_1_, L 1 I 1 1 1 __L_L 1_1_1 _L_J_ _1 _Lscouctct

2 INSTALL ATION FACTORS WOW P

E1 12 13 14

....

805 6 7 [ETt9 10 11112 13 1411 16 17 18 19 21521 22 2324 25 26127 28 2930 31 32 33 34 35 36 37 38 3914041 42 43 44 45 46 4748 49 50 51 52 53 54 55 56157 58 59 604,, 64 65 6667 68 69174711772173 74 7576 77 78179

9899,

.1 .. 1 .V..

DATA SHEET E I: ADDIT I ^ ''''' " . E FOR REGISTRATION. -AND DATE, PAGE OF. PROCU : PROVAL SUBMITTED BY: '{XT'% 4. -- --. --

; -I

00cpI

'.

k ,

.

L ' .TMDE ITEM DATA ,POWER REQUIRED ---______..............

CARD-NUMBER

1 I? 1-3-F

E I I I 3 I,___R,=-.6 1 1 141:___RWAR__,

E t!. 1 5 r

I LSACN

51617 13 9 lOriFIF3431_1_ :1-- 1_____L___1_1__ 1.__L.

iL SACN

2 OPERATINGVOLTAGE

i6 )7 IT3

_1_17

, FR 5 WATTSRANGEii

19 2 21 22 23 B 290.3, 1ME1 I,_ I_ _ 1_1._ i 1 1

6 OTHER FACILITIES

34MIMIIIIMI 39E 4 121431M451M1M1485:1131M52031EMBILIM3131 3013366315/311112 7 EBEEME2FLICEIII 79 BOi i t I 14_i_ 1_1_1_1_1_1_ 1 1__._L I 1 1 1_1_ I Li 1_ j I L L I 1 1 LI___.1 _1 _. __1_ _i ,_l___L_I_I. _L__A_L _I ._3 LIFE CYCLE STATUS 4 MFR ODE L NO

1

MFR NAME 09 S COST1 1_1_1 I i 1 1__L_ I 1_1_

16L__L_ I i I 1 1_1 1_1_1_1 1 I L 1_1__L__L i 1 1 t i I t_l___I t__1 L__1__L__L_1 1 i__L i 1

_II LSACN

_1_1_ _1_1_1_ _L _1 __b_i _i_i_L_2 MANAGING CMD/AG .., OTHER USING CMDS/AGCYS . . .14:APROPONENT 5. OPERATORS MANUALS1_1 1_1 1 __i__t __LA_

13

_I_ . _____L ___!.,1._;., , I 1 I. 1 1 L1 L 1 L_L I t. I.T 1 i 1 1_ 1 1L i___1_ 1 1 L

.1 . _

NUMBER I LSACN

.A. ,,,4.1. .. __L__L__A__L-L __t

2 NSN '..__t___L, ,L__._1_,L__

4. SKILL SPECIALTY3 LINE ITEM NO 5 SELF TEST

-1:2MCBCCILEMEZZIEMEM-

,:"..,

9vMESECIMEMESIMI

.,__I _I__ _t___

8 IATBF

_I_9 MTBMA

65 M1111

'S, II MT T R

.112 1317 6309 10 111)21131145.1E 1 I 16_1 l. I _1_1 ,L__1___;_LJ_I_

S;41,, 11 LSACN I '

03191DIEEMM23 .*.b' EBECIEMESCIMEEIMMOMIEDIMMCICEICEIT.;1. r." 1_1_1 1 1_ I__

69 OMB 7 6312173M0E18 0

L__L A L J__I i___L_ 1_1_1_1__LI_L__I__.1:1._L_ _1_ .I _L_1_1_1_1_ _1._L_I _I _1 _2 METHOD OF AOUIRIN SIGNAL --- I W- YE . I 1 , 7 , (___, I _ i _ i _ _ 1_,.1___1 I 1 .._itua, I LSACN

L i_I___1_1_ 1 1441/_,1___11_ 1_1 L 1 1 1 1 1 A i i`_, I I I I I J1_I i I iiitii I L_l_i _I_ _i_l_ _ __i _ ___ _ __I_ _I_ __I __L_t_1__I _1_1_1:1_1 _2 STANDARDS FOR COMPARISON

1 I '',To° g'E I I. 41 8 , i A _L__I i i i , i . . 1 4.___L_ i L, 1_1_1_-_-1.--1 L_1 1 1 1 1 - 1 I_ 1_i__L_L__L=1_i. ti I__ L__ 1 I__ 1 i I 11141_1_1_1__I. l_L l__L_L___I_L_LA L It_

._ . - , = _L_I___i__L _1 __L,____I

a TMDE REQUIREMENTS DATA 1POWER AVAILABLE TO OPERATE TMDE5 Van I LSACN ' 2 VOLTAGE 3 FREQUENCY L. 5. WAT S %PIA

28 MiM 3233 C5350337i OTHER FACILITIES

38 MMMIMIMM4546M481MM 51 mamigg56mgnmozzimrsimm67 68Egamiggpmemmeo 79 BOi 12,1314

E I 1 L 9 ICARD

ta 1 617111E1 0 MEI 13 manystomEE_i_ . 1_1 .4_ A _1_1_1_1_1_

I LSACN '

21

1 1_L

2 24 25M 27

L 1 _1_1 _l__1_1_ _L 1 I I 1 1 1___I 1 L_ L 1 1__L_L_L__I__ L.1_1_ I L I 1 L__i 1 J l_i L I__L__ 1_1_1_1_ 1u

_I_

2 FGC/wes/wac__I _1 _1_1_1_

3 TASK CODE 44 PARAMETERS TO BE MEASURED (OUT)

_

5 RANGE (FROM) 1. S FOVALUE MEAS TERM

I__ I 1 1

NOi 12.1 0 1 _

CARDi __i L_ L. _i 1J 1

LSACN

1,_I 1 1 L L L I J 1 1 L_1 L I 1 1 1 L i 1 i._1_ I__ L_ 1 I__L . . . _ _

6 kir,TGE (TO)_ _ _ ._L . _ _ . . _ _ .1_11_.

7. TOLERANCE PLUS (41__L __L __LA. __L _ ___1_ _L. __

8 TOLERANCE MINUS I-)_/1 - __L_ ..I__.1_. _ _I _

9 REMARKS REF__l_ .1 _ _1_ _1 _1

10 TEL ITEM_ .1. _I_

S E 0

NONUMBER

IVALUE MEAS TERM VALUE MEAS. TERM VALUE AI S TERM START END NUMBERJr411314

I

4 4 4 4 4 4

1 % i / I 9110 1/1_11.2J 13114115--4

1611711(411912Ct214 4 14 4

122121,24125126p4 , 4 4 4 4

712131.29130131

4 4 4 4 1 4 4 4

32133f 34135136137_1381394 44 1 , 1

4.11411421431441451461474 i IL

4814 915015112 1,4.711 55 47156159k461162163 .416516C 67 68169 70171172173174175176 77 78179 80--- --I .1-CARD

NUMBER

--1. LSACN h. 3LslpFANE

l'h AUTHORITY FOR '1A00 CHANGE

1 1 1 L 1 L LL__1_

6 IDENTIFY SOURCE OF PLANNED OR ESJAB. TRAINiNGtr

1. 1 I_ 1 L 1 1_ 1 ''L L_ I L L 1 L L_ L L 1 I 1 i t I L 1 L 1 1 I I I

SEG. NO

SE0NO .

E i 2 i 2 i 1_1_, 4_ 4 I

CARDNUMBER'

4___, ti

I LSACN.

-L1 _J =1_1 _L___L__L _l_ _1

3 IF NO, EXPLAIN !EST IF YES, EXPLAIN HOW SIGNAL IS LiBTAINED

,E_, 2 , 3 1_CARD

NUMBER

L L._ 1 1_4. _A-_,L__A 1

1 LSACN !._1:_l 1___I 1 .- 1 1 .1_ .1 L__ i __I 1 i I___I I 1 1 1 1_ L_L_L_ I L i _l_ L_I_I__I____L .1_ 1_1. L L 1 i .,1 1 1 1 i _1 1 ... .1 _L _.

3 INTERFACE ADPT, /SIG.SIG GOND REQUIRED, ENTER "Y" OR "N" a EXPLAIN_1..1__5E0

_,

7 12 i 3 4 5 01100 10 CM 13 I4 IS 6 17 cm24122 3 4 5 6 2 213 2' 31 Empolmj 37 Ecommanagum 48 49 Enpme155 mmp 9 ZMIOSIMEGS Mrin CAI 59 70 71 mica 76 77 '8 In 80,,E , 2 I -4 I

. CARD.NUMBER

I I I L .F,L_I__L.._1_ L i

i LSACN ;,A _I J_ L I L_L3 TMDE REG..

INDEX NO.

...1_ i .1._ I._ r_ 1 _.1,._1=1_,L __l_.. L __ 1_ i. L . 1_ _1,, L :1_1 1_..1 _l__I__L_1___1_,J__ Li ,_L_1_4 .1 _1 _L L 1 /,__/ _ _1 _1 1 _i__1_.L__L__1_1___

5 TECH DATA ;PKG AVAILABLE ,. ENTER "Y" OR "N" a EXPLAIN

_i__L_

NO.

A 2.E 5ICARD

NUMBER

A I I i -LA.. 1 1 i _ 1.

I LSACN ' /'.

11.1 , 1 1 1

3 IF ECONOMIC ANALYSIS

_ 1 I I i 1 L 1 _ 1 1, 1 _ 1 . 1 1_,1_ I. 1 1 I 1 1 . . 1 l_L L 1 1 _ 1 I _1 i 1 1 1.I I _I L._ I . I I 1 1_ I _1_ L__I _A_

WAS 'PERFORMED, ATTACH COPY, IF NOT EXPLAIN .

_ 1

5E0NO

LL

.E , 2 , 6 ,°I

i I I 1 1 L t i I i__4. ' 1_ 1 1 i I 1 I i 1 1 1_ 1 J : 1 1 i i I I, 1 I i 1_1_1 1 1_1_1_ 1_ L. A__ 1 I_ L 11 L I I_ . _ _ _ -----------LSACN

_I . . _ ._i _ __I__,Ii_L_(ST TOTAL OTT .1.1ZZar 1 m. ..,. '.." 1 IV: .41.'""OOTIAL OTI 6.1.1A 0:1101,

_l_i_L_L_I . _1_1_1 _L_L__L__L_LOCATION

1 1 1 1 I I 1 1 1 1 L I I id L_I_I.

--j-_,,,,,,,,I0F.R

E 2 1 7 1,1 1.111 1 . 1 . I

I LSACN

roz,mgt. t12 la1 1 1 1 I 1 ) L I L._ 1 1 1 1 A 1_I i I I I 1 L I I__I I 1_1 I 1 1 I I 1 1

I.L . _ . . . . _ _ _ _1 _ _ _ .1 _I_ _l__L,..4,1 LOCA ION I 01.1.017, LOCATION [ 0.1/111MTV LOCATION

._.4,:,,,,,,,

6 1 2 1 8 1 I i i i i i i i i I ,.1 I _ LIL 1 1 J 1 I A 1 _1 1__1. 1_1_ -1 __l_ I 1 1 :1 J_I L_1 ___L 1 1 1 _L_L_I__1__I 1_1_1_1_1_ 1 1 . I 1 A 1 1 1 I i A L I I_

I LSACN -_.1_,_ . _L_ _1 _1

2 REMARKS A

_I

li?47A

94'1121314 5161 7 9 1311011 12,113114115 1611 7119119 20k 122 124241HI2G l27 i2it29 3451W33 34 46137 34391441.144514614 i 413149 SO151152 53 54155156157 58 595861162 53 54 65166167 68 69 70 71 72173174 7517677178 9 BO

1 Cl

DATA SHEET E: SUPPORT. a TEST EQUIPMENT OR 'TRAINING MATERIAL DATE I PAGE OF

DESCRIPTION 'a JUSTIFICATION (SUPPLEMENTAL DATA) SUBMITTED BY: . EXT:

ip

., di,

'

X

CARD

NUMBERI LSACN

5 01301010 OMNI i6

2 STATUS CODE .16 nijellEESI 2 23 MI25 Ma 28reffnEimm 35

3 USABLE

ON

CODE

36 37 38 3.

4 T. 0

TYPE

Man

6 MATCH

BIDCODE

nir11TrOPm Ornm.).N...

la .0011.1.11/117411

....1,1"'''`7A.

411 SUPERCEDES LSACN

1.1.:11

71 MIMIIZIMM 47 izi :.I 1 2 1 3 14 11:1113MIMIIIMI

55 MIM 58 EalalaMME6631331a111111.111111111.1111111E 3 0 A

CARD

NumBERI LSACN 2 REASON FOR DELETION / SUPERSEDURE DATA .

ERNMENT TYPE

StGNATION

4 PRIME 'CONTRACTOR S PART-

NUMBER (WHEN DIFFERENT FROM THEMANUF TURER'S PART NUMBER)

_

=

I 2 11 4 5 ago s 10 MIM1 13 14 15 16 allanmSIM 23 24 251=28 maimmEommsommat cmcgmicomammemmommeoam 63111.m. cacummumichapup 78 79 110t

E131.L IA

CARD

NUMBER

'13_13 1.4

EJ 31?;A

L.J...1-E..-1...-1...-1-1,.....1--t---1...-11.-1.-1-

I LSACN2 SYSTEM'.

NUMIER

I 1-1-1.-..L...3 END ITEM

SPECIFICATION(kIS)

4 RRPL /

GAPL

5 SPARE

FACTOR

6 SMR

CCOE 5

7 ALLOWANCE/LMEAVINETLENFUNCTIONANCE

8 BASIS OF ISSUEu

5 C1000011101E1 4 151'1 1 I t , 1

'6 ISIMICIELMS3 23 2 MIMED1 1 1 1 1 1 1 1 1 )

Z I 32 MC1E/ 3 111E174/ CB C1:15148 47 'CIEBESIEEMESIMESEIM60 61 ME3Y22367 EMI 4E17 MCIMEN/17179 BOi . i _L 1 1 I I l l l 1 1 1 1 1 1 1 1 t 1 1 1 1 l 1. t i

CARDNUMBER

il2 13 11E . 1 3 1 3.I.A

. CARD

NUMBER

I LSACN

.)

2 TRUE VENDOR PART NUMBER 3 TRUE VENDOR NAME 4.'FSCM -u

5 0 7 0E1 calE1190151 1 1 1

'8 UMW 22 III60 25 ME 28 MEE132 3111E2IMES IMEIIMEELEMERVICEEIMIMMEZIMMITZIEF.71311ZIMMIMEEIMMEM 71 MITIMMIZIEGITI79 801 1 1 1 1 1 1 1 1 MOO

1 LSACN2 LSACN

(ITEM SUPPORTED)3 T 0 DESIGNATION

4 T (I040

6 T 0FIGURE

7 T. O.ITEM

8 T. O. DATE LEADTIME

0YR ma DA. MO

' I 2 1 3 14 5 16 1 7 18 1 8 110111112113114115 16 113113OCEIIMI 23 IMIENIMITIIIECEINSIET34E2 36mcimEtaimmaimmtsm -17111111:91M- MIZE- BIC. I mcmcommmaimmulaciraso 79 BO

i 1 , 4A ,1 1 1 1 1 1 1 I 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 J 1 1 1 1 1 1 1 E1 11111 l l '

i 1

_l___,I t I 1 I 1 1 1 1 1 I 1 1 1 I 1 1 1 1 1 1 l 1 1 1 1 1 1 1 1 1 1 1 1 11111111 1 1.---,

1 1_1 1 1 1 1 1 1 1 1 1 1 1111111111111111111 i 1 1 1 1 1 1 1 1 1 1 1 1 1

1CARD

NUMBERI LSACN

2 NOOF

COMP

3 TMDECOMPONENTLSACN

4 ,TMDECOMPONENTLSACN

5 TMDECOMPONENTLSACN (.,

6 TMDECOMPONENTLSACN

7 T NDCOMPONENTLSACN

_LI_8 SEC u

NO#

2 4

E, 3,5,_I 1_1._1 I,IIIIIIIIII

5 6 pun= 12 13 MI 5 16 7 1319 201322 3314E3E 7 28E15. I Eammommommai mumanam. A ansiummm mozal m1 6668 69Em 7 73311E 7. 77 78 79 BO

I I t 1

IIIIIIIII_L____L_ 1.11..11.11111111__L_I 1 IIIi _A

1 I__

L'_i -.5.

_L_L_L____L

-....../.1'.-i

.v.

. .

. 1

. '

102 103

5,"

DATE PAGE OF6DATA SHEET F: FACILITY DESCRIPTION AN JUSTIFICATIONSUBMITTED BY:. EXT .-

.

0,

1

;

.

.

C OCO

I

CARD

NuMBER I LSACN(FGC/WBS/WUC) 2 END ITEMACRONYM CODE %

4 FSC1A 4

..

B. DWG-CLASS

. ID DATE

II. FACILITYCAT CODE

9 !TIM. NAME (FACILITY) ,DAYR MO DA

I 2 3 13 5 ormarogimmii5 mono 20mgm24 25 iimmismegm 34 IMMEE59 Man 43 mmomEmom 52 M54 CMCMICIMMIES 63 =66 SE 69 70 mmr3commoveim BoF i A III INIIIIIIIIIIIIIIMINIIIIIIIIMINIMMINIME11111111111=1111111111111_Jo.

CARD

NUMBERI LSACN (FGC/WBS/WUC) 2 FACILITIES COST 4 FACILITY

AREA

S FACILITIES LEAD TIME

A ,TEST 014

C

.CT

D

FANO

II 2 3 0 5 1111130101/111:11=15MU 113811:6124 25 MIMES 30E6E134 mom, 39 MITM 43CCMCE4 4 MEM 52 1=56 Ezmmais 63311266 tgE 69 20 mp 73 mama=80

F .1.9.1.1._La

CARD

NUMBER

L L L-1-1.-1

LSACN (FGC/WBS/WUC)

I- 1 L_I I NUM= 1_1_, .3.....111JIIIIIII.t. IIIIL O.

FUNCTIONS TO BE PERFORMED, C 8 0 SHEETS5E0 NO 0nI LSACN (FGC/WBS/WUC) 2 TASK CODE I LSACN (FGC/WBSAYUC) 2. TASK CODE I. LSACN (FGC/WBS/WUC) 2 TASK CODE

F 0 2 A

F 0 j B

2 3 4

NuMBER''

F, 0 L3_L

1 L_CARD

NUMBER

F 0 _ 1 . . ± . L _ _

i Ili L .CARD

NUMBER

001110010 II BEllogi6.. LSACN

Dna 201112425 2 2 293 31 3233 34 35 1 3 el: 39 CE 41 1:9 431M 4 EEO 49 M51 Es 2=1359 5 ral 63 6 65.667 6L69 707! 7 73 74 75 6 77 78 7

5E0 NOI. FACILITIES REQUIREMENTS

1 1 1 1 1 1 1 1 1 1 1 1 i i L 1 l i l t 1 t i 1 i 1 I 1 1 1 1 i 11111 111 1 11 1 11 1 LLSACN I FACILITIES DESIGN CRITERIA °

-L-L-5E0 NO

I I I ] ! I I I ' . ! M I M I L I A M ! ! ! 1 1 1 1 I I I I I I I I L l I I 1I 11111111111 III I I I I I I I I I I It5 aacfingrommi,,D7am

LSACN

om 23 24 25 2 28E030133 El 34 35 E-12:139 COM 43=46E84 49 MEE 52 ;ES 2:1560111 9ms 63 64 65 66 67 ' 69 70 MO 7 74 75 75 71178

I FACILITIES INSTALLATION LEAD TIMES E0 NO5

F' 0 5 mu1_4

5E0 NO---bi46

NUMBER

11,1 11 11 1 1 --1--1-.1-4-1-4-1-1 1 I 11 I 1 1 1 1...l..1--1-1-1.--/11.1 1 It 1.1--1,.-1--11.1iiiiiiit_11.,l1 I. i 1..11 1,1 1.,_

1 TYPE OF CONSTRUCTIONLSACN

I I I,

t i l i t i t t i _ l0

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 I I I I 1 1 1 1 1 1 1 1 1 1 1 1 1 11 1 1 1 1111 1 11 1 11 1 1 11 1 1 1

F 0 6'

I 2 3 4 Olanap10 MIIBMIDO 16 rant:120 MEMIO 25 ISECIES31 33 4 35 MIZE 39 4.42 43 44 MICHEMITIT1152 1:11:1:01M58=11163 64 6 66 87 69 70 71 .7374 sommizzCARD

NUMBER LSACN I. UTILITIES REQUIREMENTS SEO. NO

F 0 21 IL1 111 11 1 1

II 111 1 111 1 11111111111111111111111111111111111111111111 I 11111 a IIL. lilt ri_.,

NUMBER

I I I I I I I I i L I 1 I" I I I I I I

lig_I_ _.L

LSACN I FACILITY UTILIZATION SE0 NO

F10.18 1 11111111-11 111111111111111111111111111111111111111111111111111111111111I 2 3 4 5 OW 9 ,om.2=0,6

LSACN

17E19 200122 2 24 25 2 27 28 303I 34 35 ME: 39 Mal 4 2 43 44 4 46 =call 52 rTIM56 57 58 59 MIME.31 64 66 67 69 70 71mM:1E176 7 ECE 80C P

NUMBER

_I. FACILITY UNIT COST RATIONAL .. SE0 NO

F0 91 IIIIIII IIIIIIIII IIIIIIIII I I I I I tits IIIIIIIII IIIIIIIIIIIII,III IIIII I II1...._1__I I t 1 ittliill ti

ark R LSACN---

I JUSTIFICATION .-, SEQ. Na

F i 0 MOMMEN

I 2 3 4 5 6 7 8 9 10 I I 12 13 14 15 16 17 i8 19 2. 12.2 2425 2.2 2829 3 31 3213313413513437138139 4O4II42I43l44145146l47l48l49Sc54 52 5354 5556 57 58 596I 6.63 64 .6 67 . 69 70 71 .7 74 5 76 71. 60

1.

C-

.DATE PAGE OFDATA SHEET G: SKILL EVALUATION AND JUSTIFICATIONSUBMITTED BY: EXT

X.

CARDMIMBER

i d , i ^ _,

_ ."..

1 LSACN (FGC/WBS/WUC/ 2 END ITEMACRONYM CODE 171 'r 4 FS

7,.. cm g N

jy: ia.. . a

.; 8 DWG 9 SERIAL NUMBER EFFECTIVITY 10 DA E,1

':.:.ii.: CLA55- FROM TO YR MO DAY

1311 8 010 1 1 2 1 3 e l 1 5 6 r th o g g g E 2 1 r p m :25 26 r i 28E13E132 33 343 0337 38Ems 42 EEEE4 7 48/502152 53 54 EzmE013333 3 64®310111 70 7 i MIZZIRIZZIn 7961°11 I

CARDNUMBER

1 1._1__1 1 1 1__1 1 1

v-...1.LSACN

',.1_1_ L 1_,___1_1 1 I Li__ I _L.1_1,1_ I 1 I 1 1_ 1___ 1 I_1 1 1_1 1 L__I____L 1 L 1 1 1_1_1_1,__ _l_._

DUTY POSITION REQUIRING A NEWOR REVISED SKILL

__LI__T

trw"OUVIWOVin"

_1 _1 _1_ __1 _1 ,u' =

1 121 3 14 5 mgocuo m 12 mci 15 16 pmplargli22 "mum Egm 51 ®m 34 15 36 37 imam 41 42 /1/1////0050/1/1/1/1/1103/301 62 /100/3333:31 7000300223, 79 80

G 1°1?1

CARDNUMBER

1 .1_ 1.1____1_1_1_1_1 L_

LSACN

1_ 1 1 . 1_1 1 1_1 1 1 1 L_1_1 ,_1____ 1 1 ii I_ i_ I. )._1_, L ! I I t i_ i_i_i_t_i 1_ L 1_1 A J. I I J_ 1 1 1 L L Li L_ _ _L__1_ .1.__ _1_ _1_1_1 _ .

.

I. (SKILL SPECIALLY FROM WHICHPERSONNEL CAN.BE OBTAINED)

1.

Tr,.0,

.1, 4 RECOMMENDED7, RANK/RATE/GRADE

SSC NUMBER SSC NUMBER3l IALITABY CIVILIAN

RANA/RAM OWE

2 31215161

610131CARD

NUMBER

r 1 8 1611711811912121122

1 L_Li_l I2:3124125126127128.129

I I I_L_l_ I

3C131

1

32 33134135

1

36137138139 40141 421431444614614714614616016116216.31641661661671613 69141162165164165166f64616917017 I 172173174175176177178179 BO

_ 1 1 _A. .1_1_1_1_1 1 1-LSACN

1 1 1 1 1 1 1 1 1 1 1_ J___1_,_1 I Jul I 1 1 1 I 1_ 1 1.1 I I A. . . _1 _.1

FUNCTIONS ici iE PERFORMED, C BO SHEETS'_,1

ujI. LSACN (FGC /WBS /WUC) 2. TASK CODE I LSACN (FGC/WBS/WUC) 2. TASK CODE -TrtSACN (FGC/WBS/WUC) 2. TASK CODE

6 1 01i L ` LG03141B

CARDNUMBER

0.1915 L11 L.

G 1_01 i_112153'14

CARDNUMBER

_l..1_1__i 1 i i i i. 1 1 1 1 1 1 1 i i 1 1 1 1 1 1 1 ) 1 1 1 1 1 1 1 1 1 1 1

L1_ L_Li1 1 1 1 1 1 1

I I I I I I I

1 1 1 1 1 1 1 I 1 1 1 1 1 1 1 1 1

I I I I I I I I i_1__Li. 1_,. I L) L.111 1 1 1

1_ L.1._ I.I._.I__1 1_, I. 4._ L _L 1_.1___I___

LSACN1 _1_1 _Li I I___L_I I L_L 1 L_L_L_I__ __L_I:_l

I ADDITIONAL SKILL REQUIREMENT, (SKILL REQUIRING A NEW OR REVISED SKILL CODE). ,

Sequence 0Nurn4r

_l_j__ti1 1 l 1 1 I 1 1 I I I I I 1 1 I 1 1 I 1 I. 1. I 1 l I I I I 11 1 1 I 1 1 1 I 1 I 11 I 1 I 1 I 1 I I !III I 1 1 1 I I I 1 I I I 1 1 1 I

_Li 1 I I I I I I I IIII-W1IIIIII III I I I I I i 1 1 III I !MIMI I I I I I MI I II I I I I I I I I I I I Ii_

516 7 8 9 10 11 12 13 14 15 6 /118 19/21 22 23 24 25 2627 28 293031 32 33 34 35 3437 38 39 40 41 42 43 MI 03. al 9 0 51 52 53 54 5 56 57 58 9 6061 2 63112333i681170 71 72 73 74 75 7 7778 /9 1BD

j LSACN

1 1 1 1 I l

I PHYSICAL AND

1 1 1 I. 1

MENTAL REQUIREMENTS,

I 1 1 1 I 1 1 1 11 1 1 1 I 1 1 1 1 I I I I I I I I I I I I I I I II I 1 1 11 1 1 1 1 I III I l 1 I 1 1 I

Seuence uNuqmber m

L_L_..--I I

-..-1-1equenceSNumber

n

0101614 1 I. I 1

__1_1 I 1 I 1 1 1 1 1 1 1 1 1 I 1 1

L,_ 1 L_i_i___Li_

I. EDUCATIONAL

1 1 1 1 1 1 1 1 1 1 1 11 ) 1 1 1 11 1 I. 1 1 1 1 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 1 11 I I l 1 1 I 1 1

t 1_ I L l_m_._*i___1___ 1 1 I_ 1 I:_1_1,J_ 1 1 1 4.79.,.1 I-1 1 i".___1_1_,L1-1_919[6.1_

NUMBER

_Li _11_1_1_1_1_1 LLSACN

__L _l_LI _ __I _1 _t_L _LI _1_1-1-1,--.1.. . .1

QUALIFICATIONS (ACADEMIC SUBJECTS, SPECIALIZED SUBJECTS, SPECIALIZED DEGREE AND LICENSES, ETC )

6401714 ] I I I I I I I I I I I I I I I I 1 1 1 I I 1 1 I 1 l 1 1 1 I I I I I I I I I I I I I 1 1 1 1 1 11 1 1 1 1 1 1 1 I I 1 1 1 1 1 1 1 1 11 1 1

1 lel0 0

11 1 1 I I 1 1 1 I 1 1 1 1 III 1 1 I 11 1 1 1 1 1 1 1 II 1 1 1 1 I 1 I 1 1 1 1 1 1 1 1 1111 I III 1 1 1 I 1 11 1 1 1 11 11 1 .1_177178179 BO

SeNuquencmber

en

1 121 3 4

CARD .

NUMBER

5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 1 22 23 24 25 26 7 28 291 31 32 3 34 35 37 38 39 4 41 42 43 44 45146147148 49 OS 11431545AS 5758 59160161162163164165166167168169170171112W74175176

LSACN I JSTIFIATION'UCGLOLE1i A

_1_1GLOJB i

CARDNUMBER

11 I 1 1 1 1 1 1 1 1 11 III 1 1 1 1_1__L__L_11_1-1-1 III 1 1 11 1 1 1 1 1 11 1 1 I 1 1 1 1 1 I' 11 11 I I I I 1 1 1 1 1 1 111 1

1

_L_I__ =,Sequence UNumber

I I 1 1 I I 1 I 1 1 1 1 II 1 1'1 1 1 1 1 1 II 1 1 1 11 1 1 1 1 1 1 1 ( I III I I I 1 II 111 1 1 11 1 1 1 1 1 11 1 1 1 11 11 1

I I 1____1_ 1 --L_A I. 1_ I _.1- j_,A 1_ _1,_ j_ L_i_ i. t. j_ j_ J .L..1_1 1 I I 1 I 1 1 1 L _k 1_, 1 1 _1z_1_4__3 1 1..,tL-1.... LJ I ...1 i L4 1-411 I. i_i_I. ADDITIONAL TRAINING REQUIREMENTS.

,.._1 _1_1 _1 __I

LSACN

_0101914

1 1 I

11 1 1 1 1 1 1 1 1

1 1 1 ( I L I 1 1 1

1 1 1 1 1 I I III 11 1 11 1 1 1 111 1 1 11 1 1 1 1 1 11[111(1 1111 1 1 1 1 1 1 1 1 1 11,8)1 1 1111 1

1 1 1 I 1 1 1 1 1 1 1.1 1 1 1 1 1 1 1 ) 1 1 1 1 1 1 1 1 1 ) 1 1 1 1 1 1 1 1 1 1 1 1 6 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

G 0 97 78 7980i 2 5 4 5 6i71-8 9 H111 12 13 14 15 16 17 i8 19 2(21 22232425 26 7 28 2 3031 32 33 34 35 36 37 38 39 4 41 42 43 4 45 6 4 4 49 5 51 52 53 55. 7 58 59 6 61 62 3 64 65 6 7 69 7 71 72 73 74 7 76

4

106 107

o- , DATE: PAGE OF

- DATA SHEET H: SUPPLY . SUPPORT REQUIREMENTSSUBMITTED BY EXT: tt

,__1

of

I

OCE--

1

.

CARDNUMBER

.' 1 21.13 1 1 0 . 1 1 8

MUtARaR

MANUFACTURERS PART NUAtiER 1 i 4 FSCM 5. ITEM NAME 7 OTY/EIiiiiPEOF ITEM

xd i g

13. TOTALOTY REC.

9--

CRC

/PMC

-8

.MO 13.13

d

5 5 I a CIEIMIDIE1 al 6 alal 9 0 22 23 Fa zormaim ampEpaimamaino 4041 Imam 4040 alalamillaaa3CE se tom 69 60 61 62 63 64 65 Tl6 68 e9 70 II 73 4

E3 CONVFA

7576 77 .

I t . t t i. I 1 . 1 1 1.11 t i . 1

I MANUFACTURER'S PART PSISMBER 2 MFG.I .

PART NUMBERI 1 1 1 1 . . 1 1 .

OVERFLOW

_ I I. 1

! 4. LENGTH.1 __

5 WIDTH 6. HEIGHT

7- 1

7 UM

-I- 1

8 WEIGHT 9 UM w II. Ul 12 UI PRICE

7 3 13E1130H 10 1 1 16` CARD

NUMBERInpH , .0 1 I ., c

UMNUMBER

ZD .stionnnimommnamomm_, , _2,_1,,

.1._,D

6 EICIEIMITIMIEI tE111:11312:11211111111 1 1 1 1 1 1 1 1 _1_1 `,1...1 __L. _L.

I MANUFACTURER'SS PART NUMBER

24 12113rE111161E3ClatIllalElalMalalalC013011:3 05

. I ..I 1_1. 1 1 . 1 .1...1._ 1 1 1 4. 1 1. .... 1 1 -1.. .1_ 1 i .

2 PACKAGING REQUIREMENTS CODE

alallalaialaREICEIMEE1a3 ST 1213a1Mal Marl eo 65 03103031121 22 EU r4 001320 a1

47.1,,`

L 1111.14. HAZARDOUS CHARACTERISTICS CODE

A. EconomicORDER QTY.

pi

!' '7'o"'LIT

,Kup,amEimmummommEammmmmmm7s.L , , , , .... ,..AAA_A_.,_, A,

I MANUFACTURER' S PART . NUMBER

m 32 330mmmmmmmm00 m.304.090mmmmm0mmamommm0mmm.m10 1um mmomm m, , A ,, ,_., ALA , .........1 ,_,_...,.... , , , , , _, I .t I .11 I. 1 I. _L.. I.

2 ADDITIONAL REFERENCE NUMBERS I.. .1..7.1 .1._.1

5. FSCM

.71 .1_1.

6. MAOT 1

I .1 I. . 1.1 ..i.. L

B UNIT PR CE

t 1

9 OUP

,

h 11 11;1 11 111111!1 1v 1111111 1 .111 11 l 11 11 di mmmimm mmmthmmmmmomom mmuo mNs muummilm

1111

- mm.milmul=.NIMIIMINUItt,L 4 ,..?__i_cH 4 0 , 2 , D

CARDNUMBER

1[2 1.,F.11:0131

, CARDNUMBER

rl-,_ I , 1/ I , 0 , 4 , A

CART

NUMBER

-1- i I if.H 6 , 5 , A

CARD,,,,,,,ER

. i , 1 , i .

,_,_, MII ,

i MANUFACTURER'S PART NUMBER 2 NATIONAL STOCK NUMBERN0127. . . -

CON 8. TAT (REP CYCLE) 9. REPL TASK DIST

TAT 1 GSU 10 RIC

9 6 7 Einesom i 3 14 15 013118 020 in 22 25 1:025 Elri/III z. EIEBEINEEIMO 56 allilelal 0, alai 00 45 C3 47 alaNZIE1113EFJECIEHLIEEIF3 59 CElalal " MI65 811 es 0 71 pim ,5 ,5 ID 71 lom1'111111111 11...11_1.

I MANUFACTURER'S PART NUMBER

.1__1__I.111.111 iiiii2 BASIS OF ISSUE

1.1 1

5. BASIS OF ISSUEI 1 1

4. OASIS OF ISSUE 116.1.

BIIL1

I 1

1 1 1 1

1 1 1 I 1111QUANTITY BOI END ITEM Si

34 5OUANTI

36 37Y 801 END TEM

4117111171117151711111W1718 49 30

II

UANT5 mulizizineg

I . 1

7 FAIL FACTOR

TY 801 ENO ITEM63 0

§ 9

:65 66

OTT.

OTT.er cricciamagEmonjornin11HLI. I. L. 2 13 8 16 Ulidlaiii 73 227124125

I I I !

2611712812 32 33 36139140 58 0 e0 lel 62, , , 1 1

1 1 1 1 I 1 1 1 1 1

I MANUFACTURER'S PART NUMBER

1 1 1 1 1 1 1 I 1 .

'. 0. FAIL

t I _ . I I . 1

FACTOR I ILEAC FACTORI . I 1 1 1 I

ED

2.LSA. CONTROL NUMBER 3 SMR t..1 MAINTENANCE

FACTOR (61/2/0/6TI.

SCR9'.

MR T5

%OCR

%g /ASSY 10. REMARKS

5 ID 8 9 0 mai 5 6THEIArs0 2' Eimaimmujano 31 32 34 35 37 36 39 maim 43 44 cpcial pcpc3Emomcna3 54 eci.,.......rn,,...crwm...,,..ra2 63 64 cop 67 es woo 72 manam 77 DEDEN

..i MANUFACTURER'S PART NUMBER

, 00 8 9 10 11111 i3 op 16 1111 10 DEDrimincipmrporao

11111'1:III2 LSA CONTROL NUMBER

Ti

. iiil...4 MAINT TECH

IIII5 MA1NT TECH

IIII MAINT

IITECH

II7 MAINT

IITECH.

1 II 118 MAINT. TECH

FACTOR 3i9 MAINT

FACTORelialje5LeozLii

P C C

I t 1

TECH.

_ 1 L._ I_ . : _I .1.1.TO MAINT - TASK DIST.

TIM

..,,,,

.., FACTOR I FACTOR 11 FACTOR UI FACTOR M Mes[ 71E4

9. S C CC

9

75E41

0 TEL CC001

R /RT7 75

ANSE

32 33 alcumB Se 39 0010100110 49 000 50 51 13E3 04 EDEDDE:3 59 corm 61

R

CARDNUMBER

11i1111'11 /IIII MANUFACTURER'S PART NUMBER

111111.11112 LSA CONTROL NUMBER 3 Pt. ION

I 1 I .1

4. NHA PLISN6.

5.SAME AS PLISNPRIOR ITEMPLISN

7 PRIOR ITEMPCCN 8 N

'.1 2 I IL._3.11 ° . 6 I

CARDI NUMBER

i -1 2 1314!-, =. 0 ,.. , , AH I O i 7 1 0

Ford Number.,- Ii 1i L.

11 0 i 8 ,

CARDNUMBER

I , 1 , I.'!,._, ",9 1.11 0 9 B

1 . 1 1

CAW)

. I ii , I!! LI, 0 , A.

HiiOfE,Cold. Number11 7 ,[7.11

H 2 1 0 i A31 . 2 O ,BCold Number

1 1 i 1 .% F.k 3 t 0 1 AH'', 3-,-¢-,-0

5 00000 0 I MCI IS ElallEIIIIESMITIMalIrdliaMANUFACTURER'S S PART NUMBER

29 E01:381011111III 111 11112 LSA CONTROL NUMBER

32 EIZIIMECICall 55 alalallaiallalag103011a1 00 ITIEEEIMIallaMCIIIEIEDMICICEIMILOCEICKEITIIIIElal ?I 250000761 1 i1 1

OHL/KIT/SETIII!! 11 11 11,1t.I 1 1. L 1 _1._ . i 1 .1 7 .1. 1____I__L,_ 1.,..,L..,t i

.3 PLISN = 5 REFERENCE DESIGNATION'i I- 1-111 7 1-11-19-EiriTTiiri,i. 11_1111LLT_Dtho 21 22 23 24r25-1Ter27128129130131 32 330 35 in 37 Se 39 4. 41.182183148183114714/1188100.131 182 b3.1.5_4_111LNIIAT Ltd le191,_014L1.421.31441,5141, le ilitojith: 73 74 75 7 7 TS p-.

1111\I 1 1 II I 1111xL1iL1 1111___L_I___1_1_L__, .. 1 . =. ___._ 1___1_ L .__.._ . =

i 1 1 1 1 ' I I 1 1 1 1 1 1 1 1

I MANUFACTURER' S PART NUMBERli [di L_ir,-6-1., Tu,_,4.1.,),.. um 2021

_1_1_ ...1_1___.1.___1

1 I I I I I I 1 1 1

2 LSA CONTROL NUMBER- 1 1 1 I

3 506 4 TRUE

1.--.1-I I

VENDOR

_1_1._I I I I I I I I . I 1 I 1 1 . 1 1 1 1 1 1 . 1 1 1 I I I 1

PART NUMBER

I I I

S SCM

. I 1 . 1 . . 1 .

00025 26 27 25 30 31

I I I 111 11112 LSA CONTROL NUMBER

12 33 35 3637 38 3940a 42 3 44am 71811 4900 ®5354.1500©25^ 61 063 a3mccp, 66 1111 TO 71 72 73 0 750100191

1 1 111111111111I MANUFACTURER'S PART NUMBER

,Ii_li re 1517,17FF; 0 IT alalall zo

1 11 II 1 111 1 I 1

3 TO DESIGNATION

weimpo a 9 a) ) aiallalOallailalalah,

47u0,..6

52

I

1 I 1

. 6. T01FIGURE NO !ITEM NO

8. T.0YR

DATEIn DA611

III9:no

1 .AF

11-11-EMI

III 111.

alrata 24 25 26 27 2, 29.19011 54 1,11130611331731:11000IXNIII .1111.1111.

walEami, 1 ,_,_, , I , I . I 1._ _.L. ,1 1 I 1 1 1 1 1 1 1 I i l l

I MANUFACTURER'S PART NUMBER

1 1 . 1 1 1 1.1 iii2. LSA CONTROL NUMBER

_111_11_1_I 1 1 1 1 1 1 1 I 1 I I I I

3 CHANGE AUTHORITY NUMBER

I5 SERIAL NUMBER EFFECTIVITY

1 I 1 I

B REP OR SUPISN4 IC FROM TOO 6 PCC 7TIC

fi a 10.11 00 51,151,0 9 IMG/ 22 InECIGHtlraMEI 500 2 iliE3 55 alallai 30 al , 42 000 6 Ca 4. 0000 5 CM DI 55 mma] 655460 eemKS 9 El N. 72 1100000_L_

_IlaiI , , 1 1 , , 1 1

., . , i i 1.1 1 1 1 1 I I 1

1 MANUFACTURER'S PART NUMBER3 Lig=112 0 1121 gutki

_L....,

2 .1_34 CONTROL NUMBERLa

8 I 1 1 1 1 1 1 1 I I 1 1

3 CHANGE AUTHORITY NUMBER 4 PTYI I

SHIPPEDt I I. I .15 OTT PROCURED e' 04401501%4

.1 t I

7 PRORATED OTT sPAORAICDI I

Put

i t

32 33 abo_belabe jTsTI:o_inil.2 43 44 6

11 1 1 147 48 4951557-13-1 53 54 FpOrfal11120

1 1 Iso I 0 s 6. CE10313111123 MI z MGM" WEI

1_1_1 i___I. i 1 EMONOMM1111 1 till! NEUI

, tiiillill1 MANUFACTURER'S PART NUMBERili L7 rii Lif101 JIllifirIFEIEWILTIZO

1 1

2 LSA CONTROL NUMBER21 22_1211-241T11211.1=1A529 30 31

.1_1 _1_1_11t i 1 21 I I 1 1 1 1 1 I

3 PROVISIONING NOMENCLATUREI

31232 33 34 35 ED 511_,Itoj.1.21.3 44 45 46 aim= 30 00054 5 um 9 e0 611612 68164 5511i5E5Lise 59 r0 II r2 7300000

. 1 1 1 1 I 1 1_1_ 11 111 1_1_1_1 1 . 1 t 11411141'1 ..1 J. I 11_1-1_ L 1 1_1_7_1 1_1 ..,_ .1____1_1___I

i 1 1 1 1 1 1 1 1 1 1 1 1 1 1 . 1 i . iii 11 11 iiiiii 109

DATE . . PAGE OFDATA SHEET H : SUPPLY SUPPORT REQUIREMENTS SUPPLEMENTAL ,

SUBMITTED BY' EXT

l.il

CORD

NUMBERi MANUFACTURERS PART NUMBER

5 DEEM 10 WIMBUIE116 IEIEZI 2°,

A 1_1_ 1,_t. A_ 1.___L_t_l_t I L. t_ 1_

I MANUFACTURER'S PART NUMBER

4 3 FSCM

EIMMECIMMEBEIMIIIMENCEMINEIMI

4 NEXT HIGHER ASSEMBL(PART NUMBER

4° MOISJCIDSIMBIE

i 1 ,1 , 1 1L_L---IJ___l_E

A 6 FSCM 7 NEXT HIGHER RECOVERABLE ASSEMBLYOR ATTACH TO PART NUMBER

49 321 52 0:12:11 59 MEMEMI

11111111.1111111

aL 9 FSCM

65 66 MED 69 °

3 1

Cc

11 MIESEMMECHEIIII11_1

..

80

to

6

1 121 3 14

H,4,0,A1:1_,4 ,O,B

CARD

NUMBER

2.

YE ,

3 DESTINATION

(SRAN)

___t_t.

4 DELIVERY SCHEDULE_A....A_

5 SEQ.

NUMBERA. JAN 13 FEB 0 MAR D APR MAY F JUN G JUL

1121514 5 6 7 13 9 10 1 112 13 14 15 16 17 18 19 20

t_l_i___t_t_i_t_i_t_l I A_ 1 _ i __I

I MANUFACTURER'S PART NUMBER

23 24 25 26 27 28

i t t_l___L_

29 31 32 33 34 35 36

1KIM 45 46 47 m! 7 58 61 62 63 64 65 66.7 8 69 70 71 72 7 4 75 76 7B 79

_..1,_L_

7 SE0

NUMBER

BO

H.L5 i 0 IA

CARD

NUMBER

Hil-,Ti,:_i , 5 ,O Le

3 DESTINATION

(SRAN)

,.J,J,4 DELIVERY SCHEDULE 5. PRORATED

6 REQUISITION NUMBERH. AUG I SEP, J OCT K NOV I: DEC. FROM ELIN

5 BOOB 10 11113111C1121 16 11 ILIEIMSEEEMMEMEMMESESESSEIESEDEEIt J A A A 1 A t___L__1 1_1_1

a 121LECEMMEELI 490 ESEEIMEEMEIEMMEKEIMIIIMMNIMEMEEIMEMMINE1O M N I . .II I i t I 1. 1

_ _1_1_1_ .1_1_1. __A__A_ _ A__A_1 _l_t_L_IINSERT CARD NUMBER AND HEADINGS AS REQUIRED (ADDITIONAL H30 CARDS FOR EXAMPLE)CARD

NUMBERI MANUFACTURER'S PART NUMBER

.0

314 51E1. 718 19 110111112113114115116117118119120 21122123124125126127128129130131132133134135136 37 38L39 4 41 41.14 5 47 Lial*452bASN36M28h161216k11LII465 66 68 69 70 71 72 73 4 75 76 7 78 79130._t_12_1

1 1 1 A__L1 I I ( I I I ( 1 ( I I 1 1 L 1 tiltii_uIt(LItIltill(tilit I 111111111 llllllllllllllllll1 11 1 I 1 1 I I 1 1 1 l 1 1 1 1 1 1 I 1 1 1 l I l 1---1 1- 1 I i 1 1 -,11111111 1 IIIIIIIII1111111,1111_A_A_A. -1__I-

1_1_1_11111111_1111 11.111 1 I 11 1 III I 1111111111IIII1 IIIIIIII111111111111IIIIIIIII___l_1 _L

111 11 11 I 1 1 1 1 1 1 l 1 1 l 1 1 1 1 1 1 1 1 1111 1 111 11 .1 1 1_1111 1 1111111 llllllllllllllllllI__ 1 1 1 1 1 1 1 1 1 t 1 I I 1 1 I 1 1 1 1 1 1 111 1 11_1 11 J11111_11 1 1 1111 1 _l_LtIll lll 11 lllllllllll1_1

LA 1 I I I 1 1 1 f I 1 1 1 1 I 1 1 I l 1 1 1 I 1 1 1 IttA 1 11_1111111,111111_11_ ll _111111111.1111__1_

11111111111111111111111111111111111111111.1,111111111 1 111 1-1.-1---L--1_111111111tItli

1 1 1 1 1 111 1 1 111 1 it 1 1 1111.11111111 11_11111 L 1 1 1 1111111/1 1 1 tk 11 1111111111111111 1___I _L

__1_ i 1 1 1 l l I 111111 1 1 1 1 111111111111111/11 It 1 It 1 11 11.1111111111 1 1 1111111 11111II III 1 1 1 1 1 1 111111 111111 1 111111111 1111 11111111111 11111 1111 11 1 1 1 l l 1 11 1111111_ 1 1 1 1 1 1 1 1 1 1 1 1 I 1 1 1 1 1111 1 1 1 111111111 1 11111 1 llll I 1 I 1 1111111111 1 1 I 1 1 11 1 111 1111

1.1 1111t1111111111 111111 111111111_1111111_1111111111.11111111111111111 1 1 , tillI I 1 1 1 1 1 1 1 11111111 111111 111111111 1 1111_1 A_ 1 ( 1 1, 1 1 1 1 1 lllllllllllllllll 11111 I 1 t

i 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1_1_t t illi_t 1111 .111 illt ll 1 1 1 1 1 1 1 1 1 1 t 1 1 1 1____L_AII 1 I I t 1 1 1 I 11111 1 1

a t r

11111111111111111 1111_1_11111111111111111111111111111111 III I I I 1 1 1 1 1 1 1 I 1 1 1 1 I 1 11 1 1 1 1 1 1 11 1 1 1 11 1 1 11 111111 11111111111 lll llllll I I _t 1 1 11111III 111111111111111 11111111111111111_11111_111111111111111111111111111111111111 i

111 IIIIIIIIIIII1 1 1 l 1111111 1 1 1 1 1 1 1 1 1 1 1 1 I 1 1 I l 1 111 1 I l 1111111_111111111 1 1 1 1 1 1 1 1 1 1 1 1111111111111 1 1 1 1 1 1 1 1 1._1-1._

I I I 1 1 1 I 1 1 1 1 1 1 1 1 1 1 1 1 I I 1 I 1 1 1 1 111 1 I 1 1 LI I 1 1 1 1_,1 1,t1111111111111111 1 1 1 1 11111111111111 1 1 1 1 1 1 1 1 1 1 1 1 1 1 I I l l I I I I 11 1 1 1 1 _1111 1 111 1, 1111111111111111111111111_ 1111111

1 1111 1 1 111111111 111111111111111 I 1 1 I 1 1 1 1 1 1 1 1 1 II 1 11_11.1111111111111111 1111111 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 l 1 1 1 1 11 1 1 1 1 1111111111111111111111 1 1 111111

11213 i4 516 7 13 9 110 I I 12 13 14 15116117118 19120 21 221231241251261271281297031 32 33 34135136 37 38139 40141 42 43 44 454647 49 5051 52 5315415515615715815916061 62163 64165166 6768169170171172173174175176 77178179 80

1111

ADATE t PAGE OF.'-

DATA SHEET 1 : AUTOMATIC TESTING EQUIPMENT /TEST PROGRAM SET DESCRIPTIONa : SUBMITTED BY: EXT: e

.

-

..

COCT,

I

-

CARD

NUMBERI LSACN ( FOC/ WSB/WUC) 2 END ITEM ACRONYM COO; 4 FSCM .,

.4" a D*6 9 SERIAL NUMBER. EFFECTIVITY 10 DATE

..

CLASS FROM TO YR MO DA

OD 4 5 130E1110 01011313 15 16 OCIOCEOD11111125 MGM 29 CalEit 3. 6°E1 52 ECM 55 MIEMENCOMS 64E66 67 EltE To CIEMENIEEOMI 79 BO

, . ,.,._ , A.

Cord Number

L L...4..-...L....1-..1.-1-1......1...-'LSACH

II OiiiiMICMC/MECEEZEME2

II MINI I t tt L i_k_x_I_ L 1 1._ 11_4,...,1_....1.-t..,12 ITEM NAME

....L.L../...3 TYPE MODEL MI 4 TRD NUMBER '

/2_, 2. .1.

Cord Rumba

....L.J.1_jL,,j_L,1_,LSACN

, , 1 , 1 , I 1 1 1 t o 1 1111111111111111111III 1111.1111111111

2 MFR PART NUMBER g 3 FSCM 4 DRAWING NUMBER 2 5 FSCM ,1 , , 3 LA 1 1 1 1 1 1 t I 1 1 t t 1 1 1 i i 1 , t i I l I t l t l l l l l I I I I 1 1 1 i1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 11

Lill ,_3_,J3

CARD :NUMBER

1 , ,,,_.L. k. , I k 1,...,1_1 -1,-1-1 I I___1-_.1L-J__A-i1u=LSACN

-2. ITEM NAME

3 AUTOMATIC TEST EQUIPMENT 1DENTIFICATICN

._

TYPE MODEL Nr0 SUFFIX

!-.. 9 L4 .L.

Cord Number

4 ..4-4 1-4...1-4....1.-.1c-ALSACN

J....1.....A.-1...L.Ai....L./....1L,A 1...J-1.1...-.J.,.-J..1-.4..,12. MFR. PART NUMBER I 3 FSCM ' 4 DRAWING NUMBER 5. FSCM

u

1 0 5 A1 1_1,11 lit I t I t llllll .1

5 i_B

6

'1 1 2 13 14

CARDNUMBER

5 ki 7111..91212112.12114115 47 j2.614122. 2 312,1PLIL.5AL242 28 29 321,33 35 36 37 38 39 .11 I 2 43 5 7 48 5. 51 52 S3 55 56 57 58 59 .. 61162163164165.166167168169 70 71 72 73 74 75176 77 781798C

LSACNAUTOMATIC TEST EQUIPMENT SEC

NUMBER2 GENERAL SPECIFICATIONS

LL0 ,6 LA

Card Welber

__L_I___LI 1 1 I 1 1 1

LSACN

1111 111 ol1 1Lt.....1'1_111111111111111111111111111111_1_1 _1_1_1 1]__L__1__L A_ 1_1_1_1. t

.2 STIMULUS PARAMETERS RANGE AND TOLERANCE

_i__00.

NO M*

_I 1

Cord Number

_,I. LL 1 1_,.1_1-1-1_LSACN

1 1 1_ 1 1 1 1 1 1 1 L 1_ 1 1--1-1 k 1 I I I I I I I I I I I I 1-1_1 1 1 1 1 I 1 1 LA-1-1-1 1 1 1 L / 1

RIOMAWR

.,_1 --1-,1-12 REQUIREMENTS PARAMETERS RANGE AND TOLERANCE

6 L...._1_1__l_1

CARD

NUMBER

11 tt_l_l Ittli I 1 I I I I L.A.

0LSACN

TEST PROGRAM

r4 UNIT COST

2 MFR. PART NUMBER 3. FSCM A. NON-RECURRING B RECURRING

1911t ACARD

NUMBER

1 1 I I I 1 I I 1. I I 11--1.-1 1 I 1 1 1 1 1_1 I i 1 1 t 1 1 L I t J , 1tt 1 I i 1 I l 1_1_1 A t_i 4 A__i___1_ J. 1_1_1_, -1-1-I-1-

LSACN6

_I_ - -

2. DTP MFR. PART NUMBER3 FAULT ISOLATION

_t_l___L _I

&me il, pg,vow rums

11row

Rataut.,.

I ,0_, 7_,E1_

CARO

NUMBER

A 1 11111111 tt_t__IIIIIIIIIIL I 1 ____L__t_L I 1- 1 1_1 I I I _I___1_1__L_l_l__L_J__L_1__L 11 1_1 1_1_1_1 1 1__1. I I a L_ L_

LSACN

TEST PROGRAM INSTRUCTIONr m

4 UNIT COST

2. MFR. PART NUMBER 3 FSCM A. NON - RECURRING B RECURRING 5 MP' MFR. PART NUMBER 6 FSCM

I 0I 2 1 3 4

CARD

NUMBER

6 7 Ell 9 I mom J5 16 r i z a e r z e m 2 3 2 4 2 5 2 7 2 8 2 9 3 0 3 1 32 a n 35 36 37 38 39 mg:Immo 46 47:=2131121=155 56 571:1EZ 6061 asimms68 69E171 onitala 77 78 79 8C

LSACN

INTERCONNECTION DEVICE 5)

,5 APPORTIONED UNIT COST cow

2 ITEM NAME 3 FR PART NUMBER 14 A. NON- RECURRING B RECURRINGwe,

uurt

,li_c) L9, /

CARDNUMBER

r___L_j 1._ i I 1_.1 I 11 1 ,....1 1 1 1 I 1 1 I I 1_1_1 1 I 1 1..._LI 1 l I I 1_,_1... I I. 12_1_1...._, 4._

,___L

LSACN1

J _l_ .1 _..,L_J_J_I _1_1 _t .1_1,,tIFAULT ISOL4.71t0 REPLACABLE UNITS

2 LSACN 3 ITEM NAME 2. LSACN 3 ITEM NAME

1 0,_

1 2 1 3 [ 16 17 18 19 t20 21 22123 24 25126 4 47 4 4 51 52 5 54 55 56 57158154461 162163164165166167168 69170 H-7074175 76 r7178 79 e031471819 10111 12113 14 15 2 28129 30131132133 34135136137138 39 +40141 42 43 4 5

112 113

DATA SHEET J: TRANSPORTABILITY ENGINEERING CHARACTERISTICS z

, DATE: PAGE OF

SUBMITTED BY EXT

'

NUMBER_0 i/I:

1 L SA CONTROL NUMBER 2 END ITEM ACRONYM 3 ITEM NAME 4 F S C M 5 DRAWING NUMBER 6 DATE11 YR MO DA

5 16 17 18 1-916-1-1112-1445 1811131i5 21V223124125 45146147148149 66 67 69 TO 71 74 75 Eva 78 79 80

.,..J

_LI 2 I 3 t 4 24_712112913C1, 3132133134135136 7 38139 40 41 42 43 44

j-1 ° I ' l0CARD

NUMBER

-I 1-

' DWGCLASS

1- 1 1-11 1-1 3 MODE OFr TRANSPe-

1--,1-- -1- 1---_....1---1.--1.--/--1-1 1-4./....-.11....1-...-1...1....1,....e....1.1...../ -.1....1......1.........-1...1_ 1.-...1..../...-1. I.--1-...1-,=.1....L.J....1 L.I.....1.1.....1.-.1.-.4.-..J------1 1 I L.J..1--JL.-1,....1-1 ..)...-1

SPECIFIC MODE REQUIREMENTS .4 L/M

1,0 1 1

LI 2 1 3 4

CARDNUMBER

5_16[ 8 9 10 11 2 13 14 15 16 17 18 IN 201113 44 25 :128 1130013212 34 35 1:211112140:42 431111: 1:1:149:STB52 1111111:0131:159:211 00 64 366 671:69 70 11:174 MITI T7 78 79 801 net PATiONA

ty1111112CPERATIONA1

WIDTH30PERATI

HEIGHT4 ',UPPING

LENGTH5 5 1PP NA

WIDTH6 SHIPPING

HEIGHT7

UMB I TEN

WEIGHTI9.NAX SHIPPING

WEIGHT

10. 11 CILUM FRONT

12 OLPCENTER

13 OLPREAR

c.,D

J 0 3_, , _

CARDNUMBER

_,_ t_

' CGLLENGTH

__L_,__ ____,_, t., MIMI z ,i.___,.._. __.,,-- MI 4 I ,,..., L L___L___1_1...L2 CENTER OF GRAVITY LENGYH ,,,

DATUM REFERENCE LOCATION3 CGL

WIDTH

_r_,_,

4 CENTER OF GRAVITY WIDTHDATUM REFERENCE LOCATION

CGLHEIGHT

,,...,.).. 1 t_t4 -4_

6 CENTER OF GRAVITY HEIGHT'DATUM REFERENCE LOCATION

L.

UM0

0 L41 3

CARDNUMBER

.

5 16 7 8 9 10 MI2 El 14 15 16 17 18 19 20 21 Efj 24 GI 6028 29 30 31®33 34 35 36138E040M 42 43C:46m:um 52 pm 55 Emmanamm 63 644166 67 069 7000074 75077 g3 79 802 T /L

'LOCATION. F:LENGTH

3LENGTH DATUM REFERENCE LOCATION

4 Tit_

LOCATIONLENGTH

5

'WIDTH DATUM REFERENCE LOCATION6 Tit. 7 ..

LOCATION HEIGHT DATUM REFERENCE LOCATIONtor.,

LENGTH .4.APLAr

J L° 1 5 _ _ i _

1 1 1_

I I I 1 1 1 1 1 1 1 1 1 1 1 I I I I I I I ! 1J__L__L.._L__L.4.1.111I 1

I 11 11 1.11 1 4 I 1 I 1 I 1 1 1 1 1 1

I 1 1 I 1 1.1 1 1 1 1 I .1 1 1 1..1. 1.1_1_1_1_ 1111111.111111111.1111 1111111111

111 IIIIIII It 111111 ___L_

,.....111CARD

NUMBER

L i l 1 111 11 1 111 1111 1 !III111 1 11 1_11 4-, 1..-4.....4- ...-4 -1-.1-1. 1--...1.,..L/ a

1

2PS/C FLP PS/C CLP

3PS/C RLP El 5 OTP

FRONT

_1.-:...L.-J.....

6 OTPCENTERM

7 OTPREAR

NO8 PS/C FT

10.PS/C RT

12OSS

...J....L113.

HAZARDOUS CHARACTERISTICS CODE1-1

n

_J,°J.6 1UM

NUMBER

.L_1_,1_1_1._B VF

VERTICAL

_1-1 1 1-..I. 1--1...1..._1- I- I2 s a VF

LATERALS 8 VF

LONGITUDINAL4

MEASUREMENT TERM RESONANCES

4 -14-4.-.4

42 1- 3 1 4

CARDNUMBER

5 64319110 1

1

1 2 2t314_115 16 1761 19 20121122 124125126[27128129130 31 A33114135 3613438139

12MINIMUM

SPEED

4 41 42 43 4414514614T

15

TRL

42-16

UM

5451 j5215317

TIREPRESSURE

54_15515610T158159

113

T GP

608A63

r2N0TER'AXLELENGTH

64_.k5166167

1iITERAXLELENGTH

68169 70 71

f712TERAXLELENGTH

7217317417.5

I2Fx3TERAXLELENGTH

761776179/802

.? FOOTPRINT',. AREA

3

UM

4 FRONTOVERHANG

LENGTH

5 REAROVERHANG

LENGTH

6GCH

7WHEEL

LENG8TAHs

8

UM

9

AA10

CA

II

AD

13MAXIMUMSPEED UM

19

UM

J 0 8

CARDNUMBER

IV/HEELEDVEHICLE

TYPE CODE

2 AXLE LOAD AND TRACKWIDTH DATA

3 AXLE LOAD AND TRACKWIDTH DATA4

AXLE ,LOAD AND TRACKWIDTH DATA

5AXLE LOAD AND TRACK

WIDTH DATA

6 AXLE LOAD AND TRACKWIDTH DATA

7UM

8UM

J.,-...

9. TIRESIZEREF.

.--..1.-4 .

J 0 9

22 2312412512612712812913013132 33 14 35 33.±313132142.4.1151±3. 41.I5/z.±81495451 52 55 56 57 58 sa I 63 64 66 67 68 69.12 71172 72174175 7677k/14779 80' I 2 I 31 4

:AID wuunr 1.1

LI 8 9 10 II 1121131141144 T118119120 ?I_5_16_. .

SPECIALIZED ENVIORNMENTAL CONSIDERATIONS It vxiuOW. ,_.1..,j_L , 1111111r1 111'111 11111,1111__,_ _.____,_ 1 1 t . : , L 2 , , , ,,, , , i lll l l l l lA

1 1. 1 1 1,1 1 1 t a, 1 ,,,,, ' 11 ...,

1,, llllllllllll 1 llllll I llllll 1 1 llllll t 1 1 1 1 1 1 l 1 1

1 1 1 1 /--1.1-- 1--1--1- 1 I 1 1 I 1 1 1_ 1,t___L.....,__s__L- 1_ i I 1L-1 1 L 1 t x11111111.111.1,1_J____LA....1..,CARD NULAI1Ell

. tj_JL_J.IILIIISPECIALIZED EQUIPMENT

tvik.h..i.s,NPPRO n

J i .l 1 l 1 l 1 t 111111111111 f 1 1 111 4.1 l 1 f 1 111111 1 1111111111 111 _1_1-1.1.1.11111 ,11/1111 1 1 1 / 1 1 1 111

1--1---,--- 1- --1--J-1J. 1 1 l

,I fit 3 1 4.AID SINKER

J 1121_,

516V 41i3191 '421444,611 7 fl_81912d21_122121124125_126_127213291_303i3213313Abs[361371381391A41_142 43 4.1_146.44s11/18149145R153 S 55 56 57 5 59 54421 If_13164 661§131.tthL° 71 7 73 74 75 77178179 80REMARKS 'LI riP g

,_ . . . , L 1-1_1 1111t1 1 ta I 11.L.1..111'1 111111111111111111 11111111 111 11,,y,,,, llllll .,,,,,, ,,,,,,,,, 11111111/1111111 /1111 /1

114115

APPENDIX B

ACDF ON-LINE DATA SCREENS

In Section IV the ACDF records are listed in Table 5,and the on-line menu screen used to retrieve theserecords is shown in Figure 19. This appendix containsthe CRT terminal screens for several ACDF records. Theinformation will be presented in the order shown foreach record. Since all of the information in a recordmay not fit on a single screen, the system will"instructthe user when additional information is avaiable in arecord. The user would then hit the ENTER key on theterminal to display the "next page" of information.

L

fr

116-89-

cD.

SYSTEM DESIG::/PERFOFVAMCE RECORD

Display Format:

AFG-2 DATE XXXXX -1 T.O. DATE XXXXX REPORT DATE 99/99/99

AIRCRAFT RECORDAIRCRAFT MDS H, < XXXXXXXXXXXXXXXHX AIRCRAFT SRDMANUFACTURER XXXXXXXXXXXXXXXXX

VERTICAL HEIGHTFUSELAGE VOLUMEMAX PAYLOAD LENGTHWING AREA .

WING SPAN - MAXWING SPAN - MINWING INCIDENCE ROOTWING DIHEDRAL.TREAD WIDTH

SYSTEM DESIGN99.9 FT

999999 CUFT999.9 FT9999 SQ FT999.9 FT999.9 FT.

9 DEG9 DEG

99.9 .FT

AIRCRAFT EMPTY WEIGHT 9999999 LBSDESIGN WEIGHT 9999999 LBS

T.O. GROSS WEIGHT 9999999 LBSMAN FUEL WEIGHT-INTERNAL 99999 LBSPAYLOAD WEIGHT 999999 LBS

OPERATION AND PERFORMANCETOTAL THRUST r MAX 999999 LBSTAKE OFF DISTANCE 9999'FTSTALL SPEED - MAX NT.RATE CF - MAXSERVICE CEILING

c:raAT CEILINGTIME CLIME 20000 FT -NILMAX SPEED SEA LEVEL MILSTRUCTIJRAL SPEEDAVE SPEED @ COMBAT ALTFERRY RANGEBASIC SPEED 99900 FT

LANDING DISTANCELOAD LIMIT POSITIVEnAN WING LOADINGTOTAL 2 DIGIT HUGSTOTAL 4 DIGIT WUCS

XXX

/ PERFORMANCE RECORDFUSELAGE LENGTHMISSION PAYLOAD VOLUMEMAX PAYLOAD WIDTH

WINGWINGWING

SWEEP - MAXSWEEP - MININCIDENCE - TIP

BASIC WEIGHTCOMBAT WEIGHTMAX EXTERNAL WEIGHTMAX LANDING WEIGHTMISSION PAYLOAD WT.

TOTAL THRUST - MILTAKE OFF SPEED

999.9 FT999999 CUFT99.9 FT

99 DEG99 DEG9 DEG

9999999 LBS9999999 LBS99999 LBS999999 LBS999999 LBS

999999 LBS999 KTS

999 KTS9999 FT/MIN RATE OF CLIMB - MIL 9999 FT/MIN

99900 FT SERVICE CEILING 1 EC OUT 99900 FT

99900 FT99.9 MIN TIME CLIMB 20000 FT-::A 99.9 MIN9999 .KTS MAX SPEED SEA LEVEL ::AX 9999 KTS

9999 KTS AVERAGE SPEED - FERRY 999 KTS9999 KTS AVE SPEED COMBAT @ SL 999 KTS

9999 NM COMBAT RADIUS 99999 IC!

9999 K'S9999 FT STALL SPEED 0 LANDING WT' 999 KTS

9.9 LOAD LIMIT NEGATIVE 9.9

599 LBS/SQ FT99 TOTAL 3 DIGIT WUCS 9999

99999 TOTAL 5DIGIT.WUCS 999999

DASIC MISSION PERFORMANCE RECORD

Display Format:

AFG-2 DATE XXXXX -1 T.O. DATE XXXXX REPORT DATE 99/99/99

AIRCRAFT RECORDAIRCRAFT MDS XXXXXXX XXXXXXXXXXXAXXXXXXXX AIRCRAFT SRO'MANUFACTURER XXXXXXXXXXXXXXXXXXXXX

BASIC MISSION RECORDTAKE OFF GROSS WEIGHT 999999 LBS

XXX

MISSION FUEL WEIGHT 999999 LBSPAYLOAD (XXXXXXHXXXXXXXX) WT 999999 LBSPAYLOAD (xxxxxxxxxxxxxxx)'.WT 999999 LBS'

WING LOADING 9999 LBS/SQ FTSTALL SPEED(POWER OFF) 999 KTS

TAKE OFF GROUND RUN SL 9999 FTTAKE OFF TO CLEAR 50 FT 9999 FT

RATE OF CLIMB AT-SL AT BASIC MISSION LOAD (BML) 9999 FT/MINRATE OF CLIMB AT SL AT BML WITH ONE ENGINE OUT 9999 FT /MIN

TIME CLIMB TO 99000 FT. 99.9 MINTIME TO IB TO 99000 FT. 99.9 MIN

SERVICE CEILIN AT MAX AIRCRAFT WEIGHT (MAW)SERVICE CEILING W ONE ENGINE OUT AT-MAW

coms RADIUSAVERAGE CRUISING SPEEDINITIAL CRUISING ALTTARGET SPEEDTARGET ALTITUDEFINAL CRUISING ALTTOTAL MISSION TIMECOMBAT WEIGHTCOMBAT A UDECOMBAT SPEEDCOMBAT CEILINGMAX RATE OF CLIMB-SL(BM

9999999

99999999

999999999999.9

99999999900999.99900099999

NMKTSFTKTSFTFTHOURSLBSFT

KTSFTFT/MIN

99999 FT99999 FT

SERVICE CEILING AT COMBAT WE T 99900 FTSERVICE CEILING WITH ONE ENGINE UT AT =EAT WEIGHT .99900 FT

MAXIMUM SPEED 99000 FT 9999 KTS

BASIC SPEED 99000 FT 9999 KTSLANDING WEIGHT 999999 LES

GROUND RCLL AT SL 9999 FT

GROUND ROLL SL - AUX BRAKES 9599 FT

TOTAL DISTANCE 50 FT 9999 FT

TOTAL DISTANCE - AUX. BRAKES 9999 FT

118

S4TEN FEATURES ,RECGRD

Display Format:

AFG-2 DATE -1 T.O. DATE XXXXX REPORT DATE 99/99/99

AIRCRAFT RECORD1%.AIRCRAFT NDS

MANUFACTURER

TYPE AIRCRAFTPRIMARY MISSIONWEIGHT CLASSDENSITYNUMBER AIRCREWAIRCREW ESCAPE SYSTEM

SYSTEM FEATURES RECORDXXXXXXXXXXXXXXXXXXXXXXXXXXX999K < NT <= 999K999.9.99

J

.,ENGINE -.TYPE XXXXXXXTOTAL ENGINES 99

IN FUSELAGEIN WINGSINSTALLATIONENGINES AUGMENTEDVARIABLE GEOMETRYTHRUST RE RSER

9

9

INLETS

. MODEL NUMBER XXXXXXXXXX SRD-' XXX

"FUSELAGE PODS 9

WINGS PODS 9

X7v1XXXXXXXX-An. Al A

XXXXXXXXX

'WING LOCATIONVARIABLE WING GEOMETRYDOES THE AIRCRAFT WINGS

XXXXXXXXXXXXXXXX

CARRY INTERNAL FUEL XXX, INCORPORATE HIGH TECHNOLOGY LIFT XXX

UTILIZE BOUNDARY LAYER CONTROL XXX.

NUMBER OF INDEPENDENT FLIGHT CONTROL SYSTEM 9

INCORPORATE "FLY BY WIRE " CONTROL SYSTEM XXX.INCORPORATE STABILITY/CONTROL SYSTEMUTILIZE ELECTRICAL MULTIPLEX SYSTEMSNUMBER OF INDEPENDENT ELECTRICAL POWER SUPPLY SYSTEMS. 99ONE OR MORE AUXILLARY POWER UNITS XXX'NUMBER OF INDEPENDENT HYDRAULIC POWER SUPPLY SYSTEMS 9

HYDRAULIC SYSTEM PRESSURE 7/A..AAl

NUMBER OF HYDRAULIC DEPENDENT SUBSYSTEMS ' 94r

DOES THE AIRCRAFT HAVEHF CONNUNIOATIONS XXX VHF COMMUNICATIONS.. AAAUHF COMUNICATIONS XXX FM COMMUNICATIONS..RADIO NAVIGATION XXX RADAR NAVIGATION.... AA"A/A RADAR XXX IR NAVIGATION. XXX

'ELECTRO-OPTICAL SYSTEM XXX HEADS-UP DISPLAY.... AAA

119

INTERNAL GUNS. XXX A/A MISSILESA/G MISSILES CRUISE MISSIL=bRADIO FREQUENCY SURVEILLANCE EQUIPMENT....ELECTRONIC COUNTER MEASURES EQUIPMENT t 1

ON BOARD MAINTENANCE RECORDERLANDING GEAR LIPE XXA." r'NUMBER OF LANDING GEARS.. 9 NUMEER OF WHEELS/TIRES 59DE-ICING ANTI-ICINGTYPE OF OXYGEN 7XXXXX BLEED-AIR

AUTO PILOT XXX AUTO PILOT / ILS.... .AA

TERRAIN FOLLOWING/TERRAIN AVOIDANCE(TF/TA).XXXAUTO PILOT COUPLED TO TF/TA XXXAUTO PILOT COUPLED TO WEAPON DELIVERY SYS XXX

x.vFLIGHT DIRECTORWEAPON CONTROL SYSTEM XXXEXTERNAL STORE STATIONS 99

CAMERAS ON BOARD. TYPECAMERAS CN BOARD...PURPOSEAIR TO AIR REFUELING X XAIR TO AIR REFUELING TYPE XXXXXXXXXXXXXXXXWINDSHIELD RAIN REMOVAL XXXAIR TURBINE "MOTORS XXXAVIONICS EQUIPMENT COOLING XXXAVIONICS EQUIPMENT COOLING AGENT XXXXXXXRADAR ALTIMETER XXXCRASH DATA RECORDER ON BOARD XXXEMERGENCY RADIO BEACON XXXCOMMAND / CONTROL EQUIpMEiT INSTALLED XXXFIRE SUPPRESSION SYSTEM XXXXiXXAXXXXAAAK AXXXXXX

LANDING GEAR KNEELING XXXLANDING GEAR CASTERING/STEERING XXX'TAIL BUMPER XXXBUILT IN TEST (BIT) XXX

EQUIPMENT/SYSTEM WUCXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXxxkxxxxxxxxxxxxxxxxxx XXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXSTRUCTURAL COMPOSITE MATERIAL XXXAVIONICS/WEAPON CONTROL COMPUTER SYSTEM XXXXXXX%AAX

120

'Dispray Format:.

I

I !

':,U.',YSTP,1 RECORD

ELECTRICAL POWER. .SUPPLY DESIGN DATAFcR, AIRCRAFT.). AAAaX,C., (ERD XKx)

ELECTRICAL, ELECTRICAL

?ELECTRICAL

GENERATORS - ENGINEGENERATORS - HYDRAULICKVA @ GENERATORKVA7 TOTALGENERATOR RPMTYPE GENERATOR

HARDWIRE TERMINATION,METHODSLRU NOMENCLATURELRU CONNECTOR WUC

POWER SUPPIrY WUC 99 LRU TERMINATION ME5HODPOWER SUPPLY 4-DIGIT WUC 999 BUS NOMENCLATUREPOWER SUPPLY 5-DIGIT,WUC 9999 BUS-WC

BUS,TERMINATION'METHOD

DRIVE MECHANISMGENERATOR DRIVE TEMPERATURE:-

99

9999999

99999'

XXXXXXXXvvv'MvXXXv-XXXXXXXX'/XXXXXXXX:

Gi',NERATOR'- TENPERA'TURE

INVERTERS - INSTRUMENTSINVERTERS - CTHER THAN INSTRUMENTVOLTAGE, -A-C INSTRUMENT JOVERARCZoNVERIERS,

CIRCUIT BRE,AKERS RATINGSLOWEST AMPS6

HIGHEST AMPS. .

CIRCgT BREA?EF6.- TOTAL'VOLTAGE,A-C, THREE PHASEVOLTAGE, A-C, SINGLE PHASEVOLTAGE', A-C. CYCLES.ANFERES -

BATTERY TYRE

BATTERY - .;:uniER

BATTERY - 'VOLTAGEBATTERY - ANPEREMOURSVOLTAGE, 'D -C', AIRCRAFT

ELECTRICACDIGTRIBUTION.METHOD

. .6

HARDWIRE TERMINATION METHODS .LRU NOMENCLATURELRU CONNECTOR WUC,Loop TERMINATION METHODgUS pOUE.NCLATUREBUS 'WUC'

BUS T,ERNINATION-METHOD

999

9999

9

99999

9999

999999999999.99

9

99

99

99A

......

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

HARDWIRE TERMINATION METHODSLRU VOENCLATUREI:RUCONNECTOR WUCLRU TERMINATION METHODBUS. NOMENCLATUREBUS WUCBUS TERMINATION METHOD

FUSE RATINGS LOWEST AMPSHIGHEST AMPS

MINIMUM FREQUENCYMAXIMUM FREQUENCY

0:0-C BUSES

POWER'DISTR/SUTIONBOXES A-GCONNECTORS, 'ELECTRICAL - TOTALTRANSFORMERS: ELECTRICAL,- TOTALMULTIPLEX TERMINALSA-C BUSES .

EXTERNAL 'POWER RECPTACLES,-"ELEcTRIcat

TRANSFORMER/RECTIFIER, ELECTRICAL TOTALCONDUIT LENGTHHARDWIRE - LENGTH

.

A-C POWER'SUPPLY COMPONENTSD-C POWER SUPPLY COMPONENTSA-C AND &-C COMPONENTS

'ELECTR:CAL POWER SUPPLY SUESYSTEN WEIGHT

ti

XXXXX

XXXXXX"T{v"......

XXXXX

c . 0

Ant.A.XXAXXXXXXXXXXX'XXXXX.{.{XAA4..CA AA

XXXXXVAAl.Zi6XXXXA

'XXXXX

99

99

999999

9

999999'

99

999

9

999999

9999.9999999999

ELECTRICAL GROUP GROUP WEIGHT:ELECTRIeAL GROUP, A-C VOLTAGE SYSTEMELECTRICAL. D.-C.. VOLTAGE SYSTEM

ELECTRICAL POWER SUPPLY. WORK UNIT CODESWORK UNIT .

CODES NOMENCLATURE "

999999999999

"'NATIONAL STOCK NUMBER

42000 ELECTRICAL POWER SUPPLY42XXX XXXXMXXX%.{,./.AAAXAAAAA44A..XXXXX ,XXXXXXXAXXXXXX42XXX AXXXAX:..w..{...ZAXAA XXXXX:..AAXXX 122

ENGINE RECORD

Display Format:

SOURCE FOR THIS DATA IS FROM AFG-3 DATED JUN 59ENGINE: TYPE TURBOJET MODEL NUMBER J57-P-43WENGINE MANUFACTURER PRATT & WHITNEY 150-HR-QUAL-TEST MAR56PRODUCTION STATUS: OUT OF PRODUCTIONNUMBER OF ENGINE PRODUCED 741 AT'AN AVERAGE COST OF S 205,135COMPRESSOR TYPE IS COMPOUND, TWO-SPOOL AXIAL WITH 16 STAGES.TY?E OF FAN

COMPRESSOR STAGES - LP ROTOR 9

- LP FAN 0

- HP ROTOR 7

NOMINAL PRESSURE RATIO 0.0NOMINAL BY PASS RATIO 0.00:1.MAX DESIGN PRESSURE RATIO OVERALL 12.00:1.

FAN .00:1.

L? ROTOR .00:1.

HP ROTOR .00:1.

MAX ALLOWABLE BLEED AIR 0.0 %MAX RATED AIR FLOW 180 LB/SEC.

MAX RATED AIR FLOW - FAN 0 LB/SEC.

MAX RATED AIR FLOW - COMP 0 LB/SEC.COMBUSTION CHAMBER TYPE ANNULAR OUTER / 8 FLOW THROUGH CAN-A=LAR I!MER CHAMSTURBINE TY?E AXIAL - DUAL ROTORTURBINE TOTAL STAGES 3

LP ROTOR STAGES 2,

HP ROTOR STAGES 1

MAX RATED TUR3 INLET TEMP/SLS 1600 DEGREES F

MAX ALLOWABLE TURB INLET TEMP/SLS 0 DEGREES F

TURBINE COOLING NONE.

EXHAUST NOZZLE TURBINE FIXED AREA.

AFTERBURNER TYPE NONEMAX EXHAUSC EXIT TEMP / $LS 0 DEGREES F

TYPE OF IGNITION , LOW TENSION, HIGH TREQUENCY GLA: TYPE ACD2, 2

ACCESSORY DRIVE PROVISION 0

THRUST TO WEIGHT RATIOLENGTH - OVERALL 167.3 IN.

DIAMETER - NOMINAL 38.9 IN.

AFTERBURNER DIAMETER NOMINAL 0.0 IN.

ENGINE WEIGHT (DRY) 3870 LB.

ENGINE WEIGHT (WET) 0 LB.

GUARANTEED RATINGS AT STATIC SEA LEVEL STANDARD CONDITIONS.(LB) (LP /HP) (LB/HR/LB) MAX (LB/SEC)

MAXIMUM 11200 06400/09650 0.775 0 0

MILITARY 11200 06400/09650 0.775 0 0

NORMAL 9500 06100/09350 '0.765 0 0

ABSOLUTE ALTITUDE 55,000 FT. .

LIMITING MACH NR AT SL. 0.8

THE AIRCRAFT(S) USING THIS ENGINE ARE

AIRCRAFT SRD ENGINE SRD

B-52F ABF :J57-P-43W XBY

B-52G ABG J57-P-43W XB1

'KC-135A ACX J57-15743W XSD

-93-

t-

HYDRAULIC A FMEC:!ATIC PO;;ER 3.,:PPLy rEuEsTsTEN RECORD

Dlsplay Format:

HYDRAULIC & PNEUMATIC POWER SUPPLYFOR AIRCRAFT xxxxxxx (SRD XXX)

HYDRAULIC SYSTEM DESIGN

DATE 99%99/99

HYDRAULIC SYSTEM 3-DIGIT WUC 99

HYDRAULIC:SYSTEM 4-DIGIT WUC 999

HYDRAULIC SYSTEM 5 -DIGIT WUC 9999-

HYDRAULIC SYSTEMS TOTAL 9

HYDRAULIC SYSTEMS - ENGINE DRIVEN 9

HYDRAULIC SYSTEMS - ELECTRICAL DRIVEN 9

HYDRAULIC PUMPS - TOTAL 99

HYDRAULIC PUMPS - ENGINEHYDRAULIC PUMPS ELECTRICAL 99

HYDRAULIC SUPPORTED SUBSYSTEM 99.

HYDRAULIC PUMP FLOW - ENGINE 99

HYDRAULIC PUN? PRESSURE - ENGINE 999

HYDRAULIC PUMP FLOW - ELECTRICAL 99

HYDRAULIC PUMP PRESSURE - ELECTRICAL 999

HYDRAULIC TANKS CAPACITY 999

NUMBER OF HYDRAULIC TANKS 99

HYDRAULIC SYSTEM PRESSURE - MAX 999

HYDRAULIC PUMP RPM - ENGINE RATIO .999

HYDRAULIC TANK PRESSURE 99

HYDRAULIC PUMP RPM - ELECTRICAL. 9999

HYDRAULIC PUMP - AUXILLARY 9

HYDRAULIC PUMP FLOW AUXILIARY.- 99

HYDRAULIC PUMP PRESSURE - AUXILLARY 999

HYDRAULIC sysTEN OPERATING TEMPERATURE - ItAx 999

HYDRAULIC MOTORS HOURS 99

HYDRAULIC VALVES 999

HYDRAULIC FILTERS 999

C .

PNEUMATIC POWER SOURCEPNEUMATIC CYLINDERS NUMBER 9

PNEUMATIC SYSTEM - NUms711 9

PNEUMATIC PRESSURE - MAXIMUM 9999

PNEUMATIC SYSTEM COMPONENTS 99

HYDRAULIC S. PNEUNATIC SUBSYSTEM WEIGHT

HYDRAULIC & PNEUMATIC GROUP WEIGHTHYDRAULIC SUBSYSTEM WEIGH'

PNE=ATIC SLESYSTEM WrcV7

9999

9999

HYDRAULIC AND PNEUMATIC SUPPLY WORK UNI: CODESWORK UNIT

CODES NOMENCLATURE .NATIONAL,STOCK MUMBER

45000

45XXX45XXX45XXX45XXX45XXX45F.C

HYDRAULIC AND PNEUMATIC POWER

A..A4MXXM%XXXXAAANXXX:Anta:,....XXM=X%4AAZAXA,,:aCMXXXXXXX%XMX =XXX-. '1AA

XXXXNMMXxxXMXXXXXXXXZZaXMMXXXXMXXXXXxXNAAX,..AA...AA,..AA..ai

-94- 12,4

9999

CODE: OSCRECORD NAME: OPERATIONAL SUPPORT/COST

Additional Input RequirementsThe user will be prompted for the aircraft MDS and then for the code forthe desired sub-record as follows:

CODE SUB-RECORD NAME1 - AIRCRAFT LEVEL/AFR 800-16, FORHAT 4 DATA2 - WORK CENTER BY AIRCRAFT DATA3 - SUPPORT COST By WUC DATA4 - RAN BY WUC DATA5 - MAINTENANCE ACTION BY WUC DATA

1. AIRCRAFT LEVEL/AFRB00-16, FORNAT 4 DATA

When code 1 is entered, the data elements listed below for this sub-reCord will be displayed as shown in the display format.

Display Format:

FOR AIR:RAFT NDS

' FLYING HOURS 999999 99999 LANDINGS 99999

FROM DAY 999 OF 9999 (YEAR) TO DAY 999 OF 9999 (YEAR)

.

PREVENTIVE MAINTENANCE

MMH/FHON-EQUIP SHOP TOTAL

MNH /SORTIE

* ON-EQUIP TOTAL

PREVENTIVE 999.9 999.9 999.9 999.9 '999.901 GENERAL SUPPORT 999.9 999.9 999.9 999.9 989.902 GENERAL SUPPORT 999.9 99.9 999.9 599.9 999.905 GENERAL SUPPORT 999.9 999.9 999.9 999.9 999.906 GENERAL SUPPORT 999.9 999.9 999.9 999.9 999.907 GENERAL SUPPORT 999.9 999.9 999.9 999.9 999.909 GENERAL SUPPORT 999.9 999.9 999.9 '999.9 999.9SUBTOTAL - GENERAL SUPPORT 999.9 999.9 999.9 999.9 ,999.903 SCHEDULE INSPECTIONS 999.9 999.9 999.9 999.9 999.904 SPECIAL INSPECTIONS 999.9 999.9 999.9 999.9 999.9SUBTOTAL --INSPECTIONS 999.9 999.9 999.9 999:9 999.9TOTAL 999.9 999.9 999.9 999,4 999.9

CORRECTIVE MAINTENANCE

INHERENT MALFUNCTIONS 999.9 999.9 999.9 49.9 999.9INDUCED MALFUNCTIONS 999.9 999.9 99.9 999.9 999.9OTHER MALFUNCTIONS 999.9 999.9 ,C99.9 999.9 999.9SUBTOTAL ALL MALFUNCTIONS 999.9 999.9 999.9 999.9 999.9NO DEFECT 999.9 999.9 999.9 ,999.9 999.9TOTAL CORRECTIVE MAINS 999.9 999.9 999.9 999.9 999.9PRODUCTION IMPROVEMENT (TCTO) 999.9 999.9 999,9 999.9 999.9TOTAL EASE LEVEL MAINTENANCE 999.9 999.9 999.9 999.9 999.9

-95-125

CFERAT::NAI ENFFIRT,CO37 RECORD

2. WORK CENTER F.': AIRCRAFT DATA

When code 2 is entereli, the data elements listek below for this sub-

record will be displayed4as shown in the display fo. t. A display for

each applicable work center will be presented.

Display Fornat:

WORK CENTER FOR AIRCRAFT NDS NXXXXXN

FLYING MCURS, 999999 SORTIES 99999 LANDINGS 99999

FR= DAY 999 OF AR) TO DAY 999 OF 9999 (YEAR)

WORK CENTER TOTAL MANHOURS TOTAL ELAPSED TIME MAINTENANCE'ACTICNS mT2nA

H2112 999999.9 999999.9 999999 9999.9

MEAN MAN HOURS/ACTION MEAN ELAPSE TINE/ACTION MEAN CREW SIZE

9999.9 9999.9

OFF-EQUIPMENTWORK CENTER TOTAL MANHOURS TOTAL ELAPSE TINE MAINTENANCE ACTIONS

H2112 999999.9 999999.9 999999

99.9

MEAN MAN HbURS/ACTION MEAN ELAPSE TIME/ACTION MEAN CREW SIZE

9999.9 9999.9 99.9

ON-EQUIPMENTWORK CENTER TOTAL MANHOURS TOTAL ELAPSED TIME . MAINTENANCE ACTIONS ET2NA

K2100 892.0 682.0 20 4.6

MEAN MAN HOURS/ACTION44.6

MEAN ELAPSE TIME/ACTICN MEAN CREW SIZE

. 34.1 1.3

OFF-EQUIPMENTWORK CENTER TOTAL MANHOURS TOTAL ELAPSE TIME MAINTENANCE ACTIONS

K2100 202.0 176.0 14 .

MEAN MAN HOURS/ACTION MEAN ELAPSE TIME/ACTION MEAN CREW SIZE

14.4 12.7 1.1

4

NOTE: The first work center example shows field sizes (9's)for the data elements. The second shows actual data

from a C-5A work center.

1:

--\-g6- .126

ale

3. SUPPORT COST BY WUC DATA tWhen code 3 is entered, machine prompts user to enter WUC of interest.When entered, the data elements listed below for this sub-report will bedisplayed as shown in the display format. The user may enter a 2, 3, 4,

or 5 digit WUC.

Display Format.

OPERATIONAL AND SUPPORT COST EATA DATE 93/99/99

PEPORTIN3 PERIOD FROM 99-99 THRU 99-99

AIRCRAFT ms WUC Z.:C .......

VIC

NEXT HIGHER ASSEMBLY WORK UNIT CODE XXXXX

NATIONAL STOCK NUMBER

QUANTITY PER APPLICATION 999 RESPONSIBLE ALC COZE X

COST BASE DEPOTCONDEMNATION,,SPARES 59,999,999 5999,999DIRECT MATERIAL 59,999,999 5999,999EXCHANGEABLE MOD CLASS IV 59,999,999 5999,999EXCHANGEABLE MOD CLASS V 29,999,999 5999,999EXCHANGEABLE REPAIR $9,999,999 5999,999MATERIAL MANAGEMENT OVERHEAD 59,999,999 5999,999OFF EQUIPMENT LABOR 59,999,999OFF EQUIPMENT OVERHEAD 39,999,999ON EQUIPMENT LABOR 59 . 999 . 999

ON EQUIPMENT OVERHEAD 59,999,999SUPPLY MANAGEMENT OVERHEAD 59,999,999DEPOT LABOR COST 5999999DEPOT LABOR HOURS 5999,999DEPOT NUMBER OF OPERATIONS 5999.999.DEPOT OTHER COST 5999,9992ND DEST. TRANSPORTATION 59,999,999TOTAL' .WORK UNIT CODE 5999,999;999 59,999,999

NUMBER OF PARTS CONDEMNED 999,999

_97 127

40.

CPERATIOMAL LPFCAT/C25T F.ICORD

4. RAN BY WUC DATA

When code 4 is entered, the machine prompts the user to enter the WUC cffinterest. When entered, the data elements listed below for this sub-record will be displayed as shown in the display format. The user mayenter a 2, 3, 4, or '5 digit WUC.

Display Format:

R&M DATA BY WUCREPORTING PERIOD FROM (MONTH/YEAR) TO (MONTH/YEAR)AIRCRAFT MDS XXXXXXX WUC XXXXX XXXXXXXXXXXXXXXXXXXXNEXT HIGHER ASSEMBLY WORK UNIT CODE A...XXNATIONAL STOCK NUMBER XXXXXXXXXXXXXXXQUANTITY PER APPLICATION 999 RFNNSIBLE ALC CODE

REPAIRABLE THIS STATION 999,999

NOT'REPAIRABLE THIS STATION 939,9994

MEAN TIMES BETWEEN MAINTENANCE (MTBM)

MTSM

.INDUCED 99999

INHERENT 99999NO DEFECT 99999

OTHER 99999

PREVENTIVE 99999

OFF EQUIPMENTINDUCED MANHOURSINHERENT MANHOURSNO DEFECT MANHOURSOTHER MANHOURS'PREVENTIVE MANHOURSTOTAL MANHOURSMEAN CREW SIZE

STANDARD DEVIATION99.99999.99999.99999.99999.999

MEAN MANHOURS TO REPAIRMEAN ELAPSED TIME TO REPAIR

ON EQUIPMENTINDUCED EVENTSINHERENT EVENTSNO DEFECT EVENTSOTHER EVENTSPREVENTIVE EVENTS

MEAN CREW SIZEMEAN ELAPSED TIME TO REPAIRMEAN MANHOURS TO REPAIROPERATING TIME

999,999999,999999,999999,999'999,999

9,999,999 MAINTENANCE ACTIONS 999,99999.9 STANDARD DEVIATION 99.999

99,999.9 STANDARD DEVIATION 99.999

99,999.9 STANDARD DEVIATION 99.999

999,999999,999999,999999,999999,999

9 99.999,999.999,999.9999,999

INDUCED MANHOURS 999,999

INHERENT MANHOURS 999,999

NO DEFECT MANHOURS 999,999

OTHER MANHOURS 999.999PREVENTIVE MANHOURS 999,999.TOTAL MANHOURS 9,999.999

STANDARD DEVIATION 99.999

,STANDARD DEVIATION 99.999

STANDARD DEVIATION 99.999

STANDAAD DEVIATION 99.999

NOTE: Standard Deviation provided if available:

-98- 128

CFERA:13MAL SUPPORT/CPS: FECPD

5. MA:NTENANCE ACTION 37 WUC DATA

When code 5 entered, the machine prompts the user to enter the NUT ofinterest. When entered, the data elements listed below for this sub-record will be displayed as shown in the' display format. A display willbe presented for each set of Action Taken, How Malfunctioned, and Type

How Malfunctioned Codes reported. A summary of all the displays is

presented at the end for the WUC selected. The user may enter a 2, 2,

4, or 5 digit WUC.

Display Format:

MAINTENANCE ACTION DATA

AIRCRAFT -MDS KNXXXXX WUC XXXXFLYING HOURS 999999 SORTIES 99999FROM (DAY/YEAR) TO (DAY/YEAR)

LANDINGS 99999

WORK UNIT CODE: XXXXX ACTION TAKEN: X HOW MAL COLE: 999 TYPE HOW i!A2: 9

" UNSCHEDULED MAINTENANCE ",

MAINTENANCE MEAN MAINTENANCEHTSNA MANHOURS' ELAPSED TIME CREW SIZE ACTIONS9999.9 9999.9 999.9 99.9 9999

" SCHEDULED MAINTENANCE ". 0 MAINTENANCE MEAN MAINTENANCE

MTBMA MANHOURS ELAPSED TIME CREW SIZE ACTIONS9999.9 9999.9 999.9 . 99.9 . 9999

WORK UNIT CODE: 65ABO ACTION TAKEN: Q HOW MAL CODE: 799 CUTE HOW MAL: 9** UNSCHEDULED MAINTENANCE "

. MAINTENANCE MEAN MAINTENANCEMTBMA MANHOURS ELAPSED TIME CREW SIZE ACTIONS

.0 .7 .7 1.0 0

** SCHEDULED MAINTENANCE "MAINTENANCE MEAN MAINTENANCE

MTEMA MANHOURS ELAPSED TIME CREW SIZE ACTIONS.0 .0 .0 .0 0

---- SUMMARY OF MAINTENANCE DATA ----AIRCRAFT NDS C-5A WORK UNIT CODE 65AB** UNSCHEDULED MAINTENANCE **

MAINTENANCE MEAN MAINTENANCEMTEMA MANHOURS ELAPSED TIME . CREW SIZE ACTIONS93.2 . 1.4 1.4

. 1.0 1

** SCHEDULED MAINTENANCE **MAINTENANCE MEAN MAINTENANCE

MTBMA MANHOURS ELAPSED TIME CRtW SIZE ACTIONS.0 .0 .0 .0 0

NOTE: The first example shows the field sizes for themaintenance action data elements. The second exampleis actual C-5A data. The third example shows a summaryof maintenance actions froM actual C-SA data.

-99- U.S.* GOVERNMENT PRINTING OFFICE: 1984-769-056/406

129'

4,)