DOCUMENT 501-89

DG

* 1111111UNIVERSAL DOCUMENTATION SYSTEMHANDBOOK

.AD-A217 6011ATIOi

DTIC "SELECTE

FEB 06 -990 VOLUME 1

SSYSTEM DESCRIPTION

RANGE COMMANDERS COUNCILWHITE SANDS MISSILE RANGE

KWAJALEIN ATOLLYUMA PROVING GROUND

ELECTRONIC PROVING GROUND

PACIFIC MISSILE TEST CENTERNAVAL WEAPONS CENTER

ATLANTIC FLEET WEAPONS TRAINING FACILITYNAVAL AIR TEST CENTER

EASTERN SPACE AND MISSILE CENTERARMAMENT DIVISION

WESTERN SPACE AND MISSILE CENTERCONSOLIDATED SPACE TEST CENTER

AIR FORCE FLIGHT TEST CENTERAIR FORCE TACTICAL FIGHTER WEAPONS CENTER

* DISTRIBUTION STATEMENT A: APPROVED FOR PUBLIC RELEASE;

DISTRIBUTION UNLIMITED,

0 C

REP ORT DOCUMENTATiON PAGE

August 1989

Universal Documentation System Handbook -

VOLUME 1 - System Description

Documentation GroupRange Commanders Council Document 501-89

Volume 1

Range Commanders CouncilSTEWS-SA-RWhite Sands Missile Range, NM 88002 same as block 8

Supersedes Document 501-79, AD A087072, Universal Documentation SystemHandbook - Volume 1

Approved for Public Release; Distribution Unlimited

This handbook describes the Universal Documentation System (UDS). The UDS isused to formally document requesting agency program support requirements andsupport agency capabilities and commitments to support those requirements.

Universal Documentation System, UDS 47

UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED same as report

GENERAL INSTRUCTIONS FOR COMPLETING SF 298The Report Documentation Page (RDP) is used in announcing and cataloging reports. It is importantthat this information be consistent with the rest of the report, particularly the cover and title page.Instructions for filling in each block of the form follow. It is important to stay within the lines to meetoptical scanning requirements.

Block 1. Agency Use Only (Leave Blank) Block 12a. Distribution/Availablity Statement.Denote public availability or limitation. Cite

Block 2. Reo Date, Full publication date any availability to the public. Enter additionalincluding day, month, and year, if available (e.g. limitations or special markings in all capitals1 Jan 88). Must cite at least the year. (e.g. NOFORN, REL, ITAR)

Block 3. Type of Report and Dates Covered.State whether report is interim, final, etc. If DOD - See DoDD 5230.24, "Distributionapplicable, enter inclusive report dates (e.g. 10 Statements on TechnicalJun 87 - 30 Jun 88). Documents."

Block 4. Title and Subtitle. A title is taken from DOE - See authoritiesthe part of the report that provides the most NASA - See Handbook NHB 2200.2.meaningful and complete information. When a NTIS - Leave blank.report is prepared in more than one volume,repeat the primary title, add volume number,and include subtitle for the specific volume. On Block 12b. Distribution Code.classified documents enter the titleclassification in parentheses. DOD - DOD - Leave blank

DOE - DOE - Enter DOE distribution categoriesBlock 5. Funding Numbers. To include contract from the Standard Distribution forand grant numbers; may include program Unclassified Scientific and Technicalelement number(s), project number(s), task Reportsnumber(s), and work unit number(s). Use the NASA - NASA - Leave blankfollowing labels: NTIS NTIS - Leave blank.

C - Contract PR - ProjectG - Grant TA -TaskPE - Program WU - Work Unit Block 13. Abstract. Include a brief (Maximum

Element Accession No. 200 words) factual summary of the mostsignificant information contained in the report.

Block 6. Author(s). Name(s) of person(s)responsible for writing the report, performing Block 14. Subject Terms, Keywords or phrasesthe research, or credited with the content of the identifying major subjects in the report.report. If editor or compiler, this should followthe name(s). Block 15. Number of Pages. Enter the total

Block 7. Performing Organization Name(s) and number of pages.Address(es) Self-explanatory. Block 16. Price Code, Enter appropriate price

Block 8. Performing Organization Report code (NTIS only).Number. Enter the unique alphanumeric reportnumber(s) assigned by the organization Blocks 17. - 19. Security Classifications.performing the report. Self-explanatory. Enter U.S. Security

Classification in accordance with U.S. SecurityBlock 9. SQonsoina/M riAgency Regulations (i.e., UNCLASSIFIED). If formNames(s) and Address(es). Self-explanatory. contains classified information, stamp

Block 10. Soonsoring/Monitoring Agency, classification on the top and bottom of the page.

Report Number. (If known)Block 20. Limitation of Abstract. This blockBlock 11. SuDolementarv Notes. Enter must be completed to assign a limitation to the

information not included elsewhere such as: must be ete to a nlimitedo o the

Prepared in cooperation with...; Trans. of ..., To abstract. Enter either UL (unlimited) or SAR

be published in .... When a report is revised, (same as report). An entry in this block is

include a statement whether the new report necessary if the abstract is to be limited. If

supersedes or supplements the older report. blank, the abstract is assumed to be unlimited.Standard Form 298 Back (Rev. 2-89)

0

DOCUMENT 501-89

UNIVERSAL DOCUMENTATION SYSTEM

HANDBOOK

VOLUME 1

SYSTEM DESCRIPTIONAcce: son For

NTIS CR,&,

t'J ,, ,TAJ 0]J. .4f c cl0

AUGUST 1989

Av' U ity Codes

I- '~ .A. :I *'icor

Prepared by

Documentation Group A IRange Commanders Council ,-

Publishec oy

SecretariatRange Commanders Council

U.S. Army White Sands Missile RangeNew Mexico 880020

PREFACE

The Range Commanders Council (RCC), recognizing the need for rapidturnaround support of range user requirements and the efficiencies tobe derived from Plectronic word and data processing systems, has inthis edition of the handbook, developed a Universal DocumentationSystem (UDS) format adaptable to electronic processing whilecontinuing to meet the needs of the manual (typewritten) subscriber tothe system.

This handbook supersedes all previous issues of RCC document 501-79,volumes 1, 2, 3, and supplement 2, document 501-84. Existing programsmay use the previous procedures and forms as agreed between the userand the support agency. All new programs developing documentationwill use the procedures and formats contained in these volumes.

Additional copies of this handbook may be obtained from any agencylisted in paragraph 1.6 or from the

SECRETARIATRANGE COMMANDERS COUNCILATTN: STEWS-SA-RWHITE SANDS MISSILE RANGE, NEW MEXICO 88002

0

iii

TABLE OF CONTENTS

Page

CHAPTER 1 - INTRODUCTION ........................................ 1

1.1 General .............................................. 11.2 Applicability ...................................... . 11.3 Authority ................................... 11.4 Handbook Revision .................................... 11.5 Definitions ........................................ . 21.6 Information and Assistance Sources .......... 2

CHAPTER 2 - ORGANIZATION AND STRUCTURE .................. 4

2.1 Purpose ..................................... 42.2 Objectives ......................................... . 42.3 Concept ..................................... 42.4 System Criteria ............................... 42.5 Document Organization ............................... 52.5.1 Level I Documents ................................... 52.5.2 Level 2 Documents ................................... 62.5.3 Level 3 Documents ................................... 62.6 Supplemental Documentation .................. 62.6.1 Document Extracts ................................... 62.6.2 Section Supplements ................................. 72.7 Other Documentation ................................. 72.8 Draft Conferences ................................... 72.9 Document Structure .................................. 72.9.1 General ............. ........................ .72.9.2 Document Outline ............................ 82.10 Document Implementation ..................... 82.10.1 Standard Formats .................................... 92.10.2 Format Identification ............................... 92.11 Security Classification ..................... 102.12 Document Revision ................................... 102.13 Document Reproduction ............................... 112.14 Document Distribution ............................... 112.15 Document Cancellation ............................... 112.16 Document Disposition ................................ 11

CHAPTER 3 USER AGENCY REQUIREMENTS DOCUMENTATION ..... 12

3.1 General .............................................. 123.2 Support Agency Review ....................... ..... .123.3 Objectives Categories and Requirements

Classes ............................................ 133.3.1 Objectives Categories ............................... 133.3.2 Requirements Classes ................................ 133.3.3 Requirement Priority Classification ......... 143.4 Requirements Documentation Lead Time ........ 143.5 Requirements Documentation (PI, PRO, OR) .... 153.5.1 Program Introduction (PI) ................... 153.5.2 Program Requirements Document (PRD) ......... 15

v

Page

3.5.3 Operation Requirements (OR) Document ........ 153.6 Requirements for Support Agencies ........... 16

CHAPTER 4 SUPPORT AGENCY RESPONSE DOCUMENTATION ......... 17

4.1 General ............................................. 174.2 Support Documentation (SC, PSP, OD) 174.2.1 Statement of Capability (SC) ................ 174.2.2 Program Support Plan (PSP) .......................... 174.2.3 Operations Directive (OD) ................... ..... .18

CHAPTER 5 DOCUMENT PREPARATION PROCEDURES ............. 20

5.1 Implementation Methods .............................. 205.1.1 Manual Method ....................................... 205.1.2 Automated Method .................................... 205.2 Page Format ................................. 215.2.1 Classification Markings ............................. 215.2.2 Format Structure .................................... 215.2.2.1 Header Standards .................................. . 225.2.2.2 Body Standards .............................. 225.2.2.3 Footer Standards .................................... 24

APPENDIXES

A UDS Outline ........................................ A-1B Designations for UDS Subscriber Agencies.... B-i

LIST OF FIGURES

1 Example of a manual/word processing format(unclassified) .................................... 26

2 Example of a manual/word processing format(classified) .............................. 27

3 Example of an automated system format(structured) .............................. 28

v

v i

ALL PROGRAMS, MISSIONS OR TASKS* HAVE SUPPORT REQUIREMENTS

PROGRAMS

t DATA _..

GATHERING

1 ' L ,t\ REPORTS/ ,

Iml' , <;DATA PRODUCTS ,

00

vii

CHAPTER 1

INTRODUCTION

1.1 General

/> This handbook describes the Universal Documentation System (UDS). The

UDS is used to formally document requesting agency program support

requirements and support agency capabilities and commitments to sup-

port those requirements. The UDS handbook is published in three basic

volumes and a supplement.

Volume 1 describes the total UDS structure, the individual documents

within the system, and the use and control of the system.

Volume 2 includes sample formats and describes procedures for prepara-

tion of the Program Introduction (PI), Program Requirements Document

(PRD), and the Operations Requirements (OR).

Volume 3 includes sample formats and describes procedures for prepara-

tion of the Statement of Capability (SC), Program Support Plan (PSP),

and Operations Directive (OD).

A complete list of RCC documents pertaining to the UDS and to

other documents can be found in the List of Available Documents

available through the RCC Secretariat, White Sands Missile Range.'-y,,,

1.2 Applicability

The UDS shall be used by all agencies desiring support from agencies

that have adopted the UDS. Requesting agency requirements documents

and support agency response documents will be prepared in accordance

with the format and procedures in this handbook and with any supple-

mental instructions prepared by the support agencies.

1.3 Authority

The Documentation Group (DG) of the Range Commanders Council (RCC) has

the responsibility for design and control of the UDS. The UDS and the

procedures contained in this handbook have been approved by the RCC.

1.4 Handbook Revision

Recommendations for revision of this handbook may be made to the DG

members at the agencies listed in Paragraph 1.6. Recommendations for

revision must include the reason for the change, deletion, or addition

and a sample of the change with its instructions. The DG is respon-

sible for reviewing the recommendation and, on approval, for its

incorporation and implementation. Normal changes do not require RCC

approval; however, unusual or controversial changes may require RCC

approval at the discretion of the DG.

1.5 Definitions

Some the terms that are frequently used in this handbook aredefined next. For a more complete listing, refer to RCC documents

501-79, UDS Uniform Test Data and Data Product Nomenclature, Supple-ment 1 and 502-81, A Glossary of Range Terminology.

Range/Support Agency: A range/support agency is an operational facil-

ity that provides support services to qualified users as determined bycurrent directives. The words "range," "center," and "support agency"are used interchangeably.

User/Requesting Agency: Any United States or foreign governmentagency, industrial organization, or other institution with authorityto use range or support agency resources.

Sponsor: Any element of a government, military, or civilian agencywith authority to use range or support agency resources.

User Requirement: Any item of support requested by a requestingagency through the UDS.

Derivative Requirement: Any item of support required by one agencyfrom another to meet the first agency's responsibility as levied by auser requirement.

Interagency Program: A program requiring the participation of morethan one range or support agency.

Lead Range/Lead Support Agency: The range/support agency that isresponsible for coordinating total support planning and operations fora particular program, mission, or test. The lead range/lead supportagency identifies the support required from other agencies and coordi-nates the total support effort.

1.6 Information and Assistance Sources

Prospective users of the UDS may obtain assistance in the preparationof requirements from the agencies listed below:

Commanding GeneralWhite Sands Missile RangeAttn: Range Programs Division (NR-P)White Sands Missile Range, New Mexico 88002-5113

Commander, U.S. Army Kwajalein AtollAttn: CSSD-KTPost Office Box 26APO San Francisco, California 96555

Commander, Pacific Missile Test CenterAttn: Range Programs Management Division (Code 3210)Point Mugu, California 93042-5000

2

Eastern Space and Missile CenterAttn: Directorate of Plans, Programs and Requirements (XR)Patrick Air Force Base, Florida 32925-5572

Western Space and Missile CenterAttn: 6595th TEG/XRVandenberg Air Force Base, California 93437-6021

Air Force Flight Test CenterAttn: Programs and Requirements (XR)Edwards Air Force Base, California 93523-5000

National Aeronautics and Space AdministrationJohn F. Kennedy Space CenterAttn: NASA-Air Force Management Office (EX-NAM)Kennedy Space Center, Florida 32899-5000

3

CHAPTER 2

ORGANIZATION AND STRUCTURE

2.1 Purpose

The UOS provides a common language and format for stating requirementsand for preparing support responses. The UDS encompasses documenta-tion generated by user agencies which states program, mission, or testrequirements and those response documents generated by the supportagencies to define the support to be provided.

2.2 Objectives

The UDS objectives

1. establish a common language and format to provide moreeffective communication between the user and support agency,

2. standardize requirement and support methodology between tieuser and the support agency to achieve an effective planning/perform-ance interface,

3. provide a standard yet flexible and dynamic system that meetsthe requirement and support needs of both simple and complex programs,and

4. provide a format for automation and manual handling ofrequirements and support information.

2.3 Concept

The UDS is intended to establish standardization, yet be flexibleenough to be used by a number of different agencies and to apply toboth small and large programs without disturbing the basic systemconcept. Flexibility permits separate instructions to be prepared byeach support agency for implementation of the UDS at that agency.These supplemental instructions may contain procedures and policiesfor the applicability and scope, submission, and revision of docu-mentation.

2.4 System Criteria

The UDS is based on a common structure to enable users to employ onebasic format when presenting requirements to support agencies. Thisstructure is defined in a document outline that combines relatedsubjects of the various program, mission, or test phases into a mini-mum number of broad categories for simplicity and ease of understand-ing. The UDS structure relates support plans to requirements with aminimum of repetition.

4

The system provides all the necessary information that should pass* between the user and all contributing agencies to support the program,

mission, or test. The system is sufficiently flexible to be used bysupport agencies without affecting the internal management of theindividual agencies.

2.5 Document Organization

The UDS provides for the following tihree levels of user and supportagency documentation:

LEVEL USER REQUIREMENTS DOCUMENTS SUPPORT AGENCY RESPONSE DOCUMENTS

I Program Introduction (PI) Statement of Capability (SC)

2 Program Requirements Program Support Plan (PSP)Document (PRD)

3 Cperations Requirements Operations Directive (00)(OR)

Level 1. The Level 1 documents (the PI and SC) are used to initiateprogram support planning between users and support agencies.

Level 2. The Level 2 documents (the PRO and PSP) may be required toprovide additional or more detailed program information, especiallyfor the more complex programs.

Level 3. The Level 3 documents (the OR and OD) are used to plan

individual operations within a program.

2.5.1 Level 1 Documents

Program Introduction (PI). The PI document is the initial planningdocument submitted by a potential user to the support agency immedi-ately upon identification of the scope and duration of program activ-ity. The potential user should submit the PI using best availableinformation, enabling the support agency to initiate resource andtechnical planning. This information, while sometimes fragmentary andincomplete, is of substantial value to the support agency in determin-ing the scope of the program. For many programs, the PI is designedto eliminate further documentation except for conduct of specificoperations.

Statement of Capability (SC). The SC document is the support agency'sresponse to the PI. When properly signed, the SC is evidence that aprogram has been accepted for support by the support agency, subjectto approval by higher headquarters when applicable. Support condi-tions, qualifications and resources, or other considerations are ini-tially identified by this document and serve as a baseline referenceto subsequent acceptance and commitment by the support agency. The PI

* and the SC complement each other in establishing the scope of theprogram support activity.

5

2.5.2 Level 2 Documents

Program Requirements Document (PRD). The PRD is prepared by the rangeuser and is a detailed full program planning document normallyrequired for complex or long lead-time programs.

Program Support Plan (PSP). The PSP is a response to the requirementspresente in t eT and is prepared by the responsible supportagency.

2.5.3 Level 3 Documents

Operations Requirements (OR). The OR document describes in detail theprogram's requirements for each program, mission, specific test, orseries of tests. It is prepared by the user.

Operations Directive (OD). The OD is the support agency's response tothe R an is the detailed plan for implementation of support func-tions for a program, mission, specific test, or series of tests.

2.6 Supplemental Documentation

The UDS includes provisions for supplemental documentation. Thissupplemental documentation includes extracts of selective portions ofthe basic documents and supplements that are actually parts of thebasic documents but do not exist under the same basic cover nor followthe same management or distribution pattern. The required supple-mental documentation is determined by joint user-support agencyagreement at the time of program initiation.

2.6.1 Document Extracts

Documont extracts relate to derivative requirements where requirementsplaced on a given support agency result in the generation of addi-tional (derivative) requirements that must be placed on other agen-cies. Derivative requirements relate to the lead support agencyconcept where one agency is given overall support responsibility whenthe total support involves a number of agencies.

Examples of document extracts are

Program Requirements Document Extract (PRDE). The PRDE becomesnecessary when requirements which are placed on an agency in turncreate additional (derivative) requirements that must be levied onother agencies. These requirements occur when it is not appropriateto levy the original PRD on these other agencies. The derivativerequirements are prepared using PRU formats in accordance with thestandard UDS outline in appendix A.

Operations Requirements Extract (ORE). The ORE is identical to thePRDE except that it applies to the OR and relates to the lead supportagency concept where the lead agency must levy derivative requirementson other agencies. In general, the basic requirements will beextracted from the user's original OR and expanded upon by the leadagency.

6

2.6.2 Section Supplements

* Section supplements break out detailed information of a particularsection for separate distribution and in general, will be restrictedto the larger programs. On the larger programs, certain requirementssuch as data formatting, processing, and display are quite voluminousand apply to only a minority of people concerned with the program. Itis appropriate that these requirements be prepared and distributedunder separate cover. These supplements may be sections of either aPRO, PSP, OR, or 00. They are stand-alone documents and are not boundwith the basic document. They are, however, identified as a sectionof the appropriate document and retain the same format and numberingsystem as described for Level 2 and 3 UDS documents.

2.7 Other Documentation

Program, mission, or test requirements documents in all instances mustbe understandable and stand on their own; however, there is muchsupporting information that must be documented and related to therequirements so that support may be provided. Examples of suchinformation are antenna patterns, trajectory data, pyrotechnics,explosive forces range safety procedures, schedules, test operationprocedures, security guides, and mission rules and assignments. Ifthis information is documented separately, it should be referenced inthe UDS program documentation which is being developed.

2.8 Draft Conferences

When PI, PRD, and OR drafts are prepared, conferences may be held fornew programs to discuss the complexity of the support and to considerforeseeable difficulties. The conferences provide the opportunity tobegin coordination early, to discuss security classifications, and toassess support questions. The support agency distributes the draftand advises all interested user and support agency personnel when andif they are required to attend a draft conference.

2.9 Document Structure

The UDS provides for a building block concept of developing andpresenting requirements.

2.9.1 General

Requirements documents, the Program Introduction (PI), ProgramRequirements Document (PRO), and the Operations Requirements (OR) areliterally extensions of each other and are used exclusively or intandem with each other depending on the size and complexity of theprogram. For example, the PI is the document that officially intro-duces a program, mission, or test to a support agency. The supportagency, because of the size or complexity of the program, may requirethat the PI be followed by the PRO and OR to more definitively staterequirements.

7

2.9.2 Document Outline

The UDS document outline is a common numbering system which providesfor the standard presentation of information by UDS subscriberagencies and serves as the framework for all documents within the UDS.Section numbers, (first four digits, for example, 1405) and associatedtitles are controlled and assigned by the RCC DG.

The UDS outline is composed of the following major section groups:

Sections 1000 - 1999 contain Program Administrative and TechnicalInformation

Sections 2000 - 6999 contain Test/Mission OperationalRequirements

The UDS Document Outline and applicable UDS Requirements/Responsedocuments are outlined in appendix A.

The sections are structured to provide a definitive area in which toinclude requirements and respective support agency responses. Theoutline, coupled with pre-defined formats and instructions, containedin volumes 2 and 3 of the UDS serve as a checklist to prevent perti-nent data from being overlooked. Only those UDS sections that bestsuit the needs of the particular program, mission, or test beingdocumented need be used. The UDS documents need not be limited to thestatement of pure requirements or responses. Informational data maybe provided as deemed necessary to clarify stated requirements andresponses. If, however, the information or background material isvoluminous, reference to a supplemental document should be considered.Pictures, sketches, or graphics may also be provided under separatecover. Supplemental documentation should be cross referenced in theUDS document.

In some cases such as composite systems, the UDS outline provides for

a requirement to be stated as a composite system or as independentsystems. Coordination between the requesting agency and the supportagency will determine the best approach for documenting such require-ments. Complex requirements should be further broken down within theappropriate UDS section to allow for simple interpretation andresponse by the support agency.

Where requirements are minimal, as in the case of small programs, orwhen the requirements are only generally defined at the programplanning stage, user agency requirements may bestated in the generalsection of each UDS section or subsection.

2.10 Document Implementation

The UDS is designed to accommodate as many conditions as practical.

While it is most desirable to have single Level 1 documents (forexample, a PI and SC that contain total program information), it isalso acceptable to have several PIs and SCs. This latter approach isused when different support agencies provide support for unique and S

8

unrelated phases of program, mission, or test. For example, one* agency supports engine tests for Program "X," another agency provides

on-orbit support for Program "X."

The same philcsophy applies to Level 2 documents. A single PRD andPSP will, wherever practical, contain all program level information.However, it is acceptable to have multiple PR~s and PSPs as explainedabove.

The most detailed level of requirements and support is contained inLevel 3 documents which describe specific requirements and support.The OR/OD documents will be prepared as single or multiple documentsas required for effective management at the user and support agencies.

The UDS documents may be provided by use of electronic word and data

processing systems or manual (typewritten) methods. The method ofimplementation and the type and schedule of documents will benegotiated by the lead support agency and the user.

2.10.1 Standard Formats

Standard UDS formats are provided for entering requirements andsupport responses. These formats provide for all the necessaryinformation that should pass between the user and all contributingsupport agencies to support the program, mission, or test. Standardformats also provide for standardization of requirements presentationand ensure proper interpretation and response. Only those standard

* formats that best suit the requirements of the particular program ortest/mission need be us-d.

2.10.2 Format Identification

Approved UDS formats are identified for each UDS section. Formatnumbers are assigned by the RCC OG for each UDS section format and areidentified by using the corresponding section number for each format.The UDS Sections 1000 through 6999 are used. Exception is made for a

general purpose format as explained below.

Format numbers are assigned for the PI and SC for each section and areindividually identified in the lower right portion of the formatadjacent to the classification line in the following manner:

UDS 1010 PI UDS 1010 SC

(Date of Approval) (Date of Approval)

A multi purpose general format is provided for the PI and SC and maybe used to supplement or extend information or requirements. Thegeneral format is identified in the lower right portion of the formatadjacent to the classification line in the following manner:

UDS GEN PI UDS GEN SC(Date of Approval) (Date of Approval)

9

The format numbers for PRD/OR formats (R=REQUIREMENTS) and PSP/ODformats (S=SUPPORT) are assigned for each section and are individuallyidentified in the lower right portion of the format adjacent to theclassification line in the following manner:

UDS 1010 R UDS 1010 S(Date of Approval) (Date of Approval)

A multipurpose general format is provided for the PRO/OR and PSP/ODand may be used to supplement or extend information or requirements.The general format is identified in the lower right portion of theformat adjacent to the classification line in the following manner:

UDS GEN R UDS GEN S(Date of Approval) (Date of Approval)

The month and year of format approval by the RCC DG is printed belowthe format number.

Approved UDS formats for PSP/OD use shall be numbered to correspond tothe PRO/OR format to which it responds. For example, when format 1040R is used in PRD Section 1040, the format for PSP Section 1040 shallbear the number 1040 S. The PRD/OR and PSP/OD formats need not beidentical, but may be the same depending on the type of response datato be entered. Exception is made for the multipurpose general formatpreviously explained.

2.11 Security Classification

The safeguarding of classified information is the mutual responsi-bility of all personnel. Adherence to the related and establishedsecurity procedures is mandatory. Details for the proper handling ofclassified documents are found in the applicable agency securityguides, manuals, and regulations.

The originating agency of a UDS document is responsible for identi-fying the information to be protected including application of theproper security classification designators and any other special secu-rity markings required. When the classified sections of large docu-ments are few in number, it may be expedient to provide unclassifiedbasic documents with the classified portions provided in a separateclassified document extract. Classified extracts will have limiteddistribution and be subject to the control imposed by their classifi-cation. Classified extracts should be cross referenced in the basicunclassified document.

2.12 Document Revision

A revision is considered to be any information added, deleted, orrevised in any section of a UDS document. Revisions may be madeeither by preparing a completely new document or by submitting therevised information. In any case, users are requested to discuss allproposed revision with the lead support agency. Pen and ink revisionssubmitted by letter are permissible for small changes; however, the

10

changes should be incorporated into the next revision to the document.The UDS documents will reflect the revision number and date of therevision. Revisions shall be numbered consecutively beginning at 01.It is recommended that the basic document be reissued, incorporatingall revisions when the number of revisions cause the document to beunmanageable. The Revision Control Section 1031 will be used toidentify the scope of the revision and shall be transmitted with anyrevised pages. Section 1030 also provides a historical record ofrevisions made to the document. In some automated systems, the dateof the revision may be used in lieu of the revision number.

The use of the symbol "R" in column 72 to identify revised lines in aformat is encouraged and should be used whenever practical. In sub-sequent revisions of a section, delete all Rs applicable to the pre-ceding revision.

2.13 Document Reproduction

The documents prepared by the user must be of reproducible quality.

2.14 Document Distribution

Each document should contain its own document distribution (UDS 1020)section. This section lists the agencies or activities to receive thedocument and the number of copies each should receive. The user willidentify distribution for requirements documents; support activitieswill normally cover the distribution in the requirements document plusany distribution peculiar to operating elements for the requiredsupport. Internal organization sub levels not appropriate forinclusion in the 1020 section may be included elsewhere with thedocument as referenced in the 1020 section.

2.15 Document Cancellation

The user or originator notifies the lead support agency by letter whena PI, PRD, or OR is to be canceled. The notice includes the title,number, and date of the document. Cancellation of the requirementsdocument automatically cancels the corresponding support document.The lead support agency is responsible for notifying recipients of thecancellations.

2.16 Document Disposition

The official file copy will be maintained and retired by the respon-sible agency in accordance with applicable records disposition direc-tives. All other copies may be destroyed upon completion or cancella-tion of the program. Computerized copy, disks, diskettes, or tapeswill be handled as prescribed by local regulations for storage orprocessing.

11

CHAPTER 3

USER AGENCY REQUIREMENTS DOCUMENTATION

3.1 General

Requirements documents (Program Introduction (PI), Program Require-ments document (PRD), and Operations Requirements (OR)) are preparedby the user agency according to a schedule negotiated by the leadagency and user. The support agency normally takes the lead in sched-ule establishment because it is the most knowledgeable with respect tosupport acquisition and implementation. The requirements for a pro-gram, mission, or test are included in a PI, PRO or OR, or in combina-tions as the program, mission, or test size dictate. The initialissue of each document includes the information needed to present therequirements which are known at the time of issue. Emphasis shouldinitially be placed on identifying requirements which call for long-range planning action even though detailed use or implementationdetails may not be known. As more information becomes available,revisions are made to incorporate the additional data. The primeconsideration is to ensure the earliest possible receipt of require-ment information at the support agency.

The user should make every effort to ensure that the requirementsdocumentation is sufficient in scope to include all known and antici-pated program requirements. For this reason, an accepted P1, PRD, orOR should be revised when there is a significant change in the user'sprogram. For example, changes in such items as program scope, mile-stone dates, test vehicle characteristics, operating or launch loca-tions, and support requirements require document revision.

The user is responsible for ensuring that requirements are promptlysubmitted at the request of the support agency and in accordance withscheduled lead times to allow for planning, funding, software develop-ment, and construction; that requirements documents reflect all majorrequirements; that all requirements are necessary to meet the program,mission/test objectives; and that all requirements have been offi-cially approved and signed. The user is also responsible for ensuringthat each requirements document contains a Section 1020 - DistributionList, and that the list identifies the number of copies needed tofulfill the user organization distribution requirements. Followinginitial distribution, the user is responsible for all additionalcopies.

3.2 Support Agency Review

Support agencies will review requirements documents received from theuser. Acceptance by the support agency is dependent upon adequacy ofinformation and format. Acceptance by a support agency also directsthe staff and operating elements of the support organization to pre-pare the response documents and necessary plans for support.

12

Support agencies shall assign a document number, establish a suspensedate for the publication of the resulting support documentation,notify the various support organizations of the suspense date, andpublish requirements document extracts and support documentation. Thesupport agency will also supplement user documentation distributionlists. If further documentation is required, the support agency mayprovide the user with a block of numbers to identify these documents.

3.3 Objectives Categories and Requirements Classes

Support agency resources and support agency development are plannedand based on valid support requirements submitted by the user. Therequirements are those needed to meet user program, mission, or testobjectives. To ensure that requirements will be met, the user mustdetermine the objectives category and the requirements class(accuracy) and relate these to basic user needs. Because these objec-tives and accuracy requirements are vital to support agency planningand development, it is necessary to precisely define categories ofobjectives and classes of accuracies as well as to establish discretelevels of priorities that relate to these objectives and accuracies.

3.3.1 Objectives Categories

The three objectives categories, I, II, and III, are defined next.

Category I. Category I objectives are mandatory to the program,* mission, or test. These objectives are those items which if not

accomplished would significantly impact program schedules, costs, andverification of system performance.

Category II. Category II objectives are required to make the program,mission, or test a complete success but are not mandatory. In otherwords, they are objectives that could be sacrificed for performance,cost, time, or other constraints.

Category III. Category III objectives are desirable for such items asdesign research, environmental research, associated projects, andsupporting engineering effort. Generally, they are objectives thatwould be beneficial to meet if support can be provided with existingsupport agency capability.

3.3.2 Requirements Classes

Requirements classes relate to accuracy and reflect degrees ofinstrumentation accuracy that are used for implementing, planning, anddeveloping support agency capability. The three classes are describednext.

Class I. Class I accuracy represents the minimum acceptable accuracyvalues or integral of coverage that is acceptable to the user. ClassI needs, coupled with objective priority, are generally used forbudget justification planning, engineering planning, and operationalsupport planning.

13

Class II. Class II accuracy represents more stringent values thatwould li-hieve program, mission, or test objectives to a greater degreeof accuracy. Class II needs are generally used by the support agency Win short-range improvement/optimization planning and implementation tomeet the more stringent future requirements.

Class III. Class III accuracy generally represents the ultimate indesired capability as well as the state-of-the-art requirement used bythe support agency in long-range improvement and development planning.

3.3.3 Requirement Priority Classification

A priority must be defined to evaluate requirements on an overallprogram, mission, or test basis. The three classifications, definednext, are mandatory, required, and desired.

Mandatory. A mandatory classification is the minimum requirement thatis essential to achieve program, mission, or test objectives.

Required. A required priority is support that would materially aid inachieving all objectives and is necessary for detailed analysis ofsystem performance.

Desired. A desired requirement is any support which can be obtainedin addition to the mandatory or required classification.

3.4 Requirements Documentation Lead Time

Lead times vary considerably from program to program depending on thescope of support needed. Requirements documentation lead times areestablished by the user agency and support agency. Nominal leadtimes, based on past experience, are presented below:

INITIAL DOCUMENTATION SUBMISSION

(Lead Time in Years)

SCOPE OF AUGMENTATION NEEDED DESIRED REQUIRED

Major additions requiring new 4 1/2 3 1/2facility construction.

Extensive software development 3 1/2 2 1/2or additions to instrumentationnot requiring major facilityconstruction.

Moderate software development or 2 1instrumentation additions fundedby the user.

Minor software development or 1 1/2instrumentation improvements.

14

Requirements documentation is submitted well in advance of the firstrequested support or test date. This time is needed for the supportagency to provide the required software, facilities or instrumentationand to review, accept, approve, publish, and distribute the necessarysupport documentation.

3.5 Requirements Documentation (PI, PRO, OR)

Requirements documentation is compiled in accordance with the generalinstructions contained in chapter 2, the UDS outline in appendix A,the standard formats and instructions in volume 2, and the specificinstructions described next.

3.5.1 Program Introduction (P)

The PI is the document that officially introduces a program, mission,or test to a support agency and establishes the scope of programactivity. Within the defined scope, the user has freedom in planningspecified operations in detail. The support agency, however, willdecide if further detail should be included in the PI or if moredetailed documentation is required.

New program requirements may impose a need for additional trackingcoverage, additional data products, different frequencies, or otheraccommodations not available at the support range. The criteria andqualifications of such requirements should be stressed in the PI.

* Users with programs involving orbital operations or large weaponsystems should consider the program in phases. Phase examples areprelaunch, orbital, recovery, test location, development, and systemcomponents. In these cases, the user should identify in the PI thoserequirements that differ and those that are unique to a particularphase. If a particular requirement is program-wide and does notdiffer, then such a distinction is not necessary.

3.5.2 Program Requirements Document (PRD)

The PRO, as a detailed program planning document, contains the user'sdesired support requirements from the support agency and may containsupplemental information needed for clarity. The need for a PRO isdetermined during the analysis of the PI or during early planningmeetings and will be stated in the SC. A PRO is submitted immediatelywhen identified. The user should not delay submittal of the PRObecause of incomplete knowledge of support requirements. If requiredby the support agency, the PRO is submitted by the user agencyaccording to a schedule negotiated by the lead agency and the user.

3.5.3 Operations Requirements (OR) Document

The OR document is a mission-oriented document that describes indetail the program's requirements for each program, mission, specifictest, or series of tests and is prepared by the user. The PRO and ORmust be complete documents capable of standing alone. The OR must notreflect new requirements that were not previously stated in the PI andPRO. The OR format must be consistent with the UDS outline in

15

appendix A and the formats in volume 2. If the OR is required by the

support agency, it is submitted by the user agency according to aschedule negotiated by the lead agency and user.

3.6 Requirements for Support Agencies

Section 6020 of the UDS is used for imposing support requirements on

other agencies in interrange operations and is mainly used by a lead

support agency. When prepared by a lead support agency, section 6020

is added to the requirements document before distribution. If thelead support agency requires support from more than one agency, a

separate section 6020 will be prepared for each. When prepared by a

support agency other than the lead agency, the additional informationwill be added to the lead support agency attachment. Pages added by a

supporting agency will continue the numbering sequence initiated by

the lead agency.

Extracts of the PRD/OR are prepared by the support agency when

requirements are such that planning support must be accomplishedbefore authorization to acquire a capability is given. The extract

documents relate to derivative requirements where requirements placedon a lead support agency result in additional (derivative) require-

ments that must be placed on other agencies. Derivative requirementsrelate to the lead support agency concept where one agency is given

overall support responsibility when the total support involves a

number of agencies (refer to chapter 4).

16

CHAPTER 4

SUPPORT AGENCY RESPONSE DOCUMENTATION

4.1 General

This chapter pertains specifically to support agency documentation and

supplements the information contained in chapter 2. Support agencyresponse documents (Statement of Capability (SC), Program Support Plan

(PSP), and the Operations Directive (OD)) are prepared by the support

agency in response to the approved requirements prepared and submittedby the user agency. Response documents are revised by the supportagency when requirements are changed or support is revised.

4.2 Support Documentation (SC, PSP, OD)

The following subparagraphs describe the Statement of Capability,

Program Support Plan, and Operations Directive.

4.2.1 Statement of Capabilit (SC)

The SC provides a response to the user's PI. The PI, in combination

with the approved SC, forms a basic agreement between the user and thesupport agency and guides the more detailed planning directives to

* support organizations.

Wherever possible, the SC responds to the PI on an item-for-itembasis. Responses may be presented in the general section of each UDSsection or subsection when further breakdown is not warranted. In

some cases, the support agency may respond to the PI on an exceptionbasis rather than with a definitive support plan. Also at thediscretion of the support agency, commonly supplied items andrequirements that can be satisfied with existing capability may be

answered in a general all-inclusive statement. The approach taken

depends generally on the nature and the purpose of the program.

When the support agency capability will not meet the requirementsstated in the PI, the SC specifies such restraints and limitations.

The SC may also serve to support funding policy directives, and assignexisting facilities such as launch complexes, office space, assembly,

and storage areas available to meet requirements stated in the PI. Ifthe user requires new construction, the SC may provide site approvalby the support agency.

4.2.2 Program Support Plan (PSP)

The PSP is the support agency's response to the PRD. The initial PSP

issue includes an item-for-item response to the program requirementswhich are known at the time of issue and stated in the PRD. The PSP

formats and instructions provided in this handbook are designed simi-

* larly, to the PRD to provide parallel association between the require-

ments and the support responses.

17

The PSP document, when designed by the support agency using the U0Sformats, may be short or long in content. Short document contentincludes only those sections essential for conveying the requirementsand for confirming the support. Short documents may contain only afew sections related to administration and document control followedDy Section 2030 - Support Commitment and Section 2060 - SupportRequirements Which Cannot Be Met. Section 2080 - Requester's Respon-sibilities, and any others such as Section 2070 - Engineering Plansand Schedules may also be included. Routine boiler plate materialwhich may be program common knowledge is usually reflected in a well-developed PRD.

Long document content includes all necessary document responses and isnot simply limited to a statement of the support to be provided.Enough background material will be included so the manner in which therequirements are going to be met can be clearly conveyed in a singledocument. Sections 1000 through 1999 are used to provide informationonly, and as such do not respond to the PRD requirements. Sections2000 through 6999 are responses to specific PRD requirements unlessdesignated support agency information items. The UDS sections usedfor information items in a PSP are identified in section 1040, whichwill serve as a table of contents for the document.

4.2.3 Operations Directive (OD)

The OD is the support agency's response to the OR and details eachsupport function role, the support equipment, the technical configura-tion, and the personnel duties involved in supporting the test oroperation. The OD may provide management information or technicalrequirements and guidelines. It is a listing of expected coveragedetailing the support posture of the support agency for the testcovered by the particular OD. Requirements that cannot be met must beidentified. The OD is normally prepared in sufficient detail tofurnish instructions for a specific test or test series.

The OD is organized according to the UDS outline in appendix A andformats in volume 3. The outline may be further structured by thesupport agency to provide ready-access to information at operatinglocations. The support agency defines section structure as needed.The major UDS section numbers and titles may not be altered andshould, where possible, provide association between a requirement andthe support response.

The 00 may be supplemented with standard operating procedures (SOPs),extracts, or similar documentation. The appropriate section in the 00will contain a reference to the applicable SOP and a short statement(one or two sentences) outlining the type of equipment and proceduresused. Examples of such standard procedures are radar and telemetryset-ups.

18

* The OD must be written in clear, concise technical language that issubject to one interpretation only. All abbreviations must be consist-ent with the abbreviations used in the OR. A common understanding ofsuch terms is essential. Other terms and abbreviations must not beused unless completely defined when first used in each document. Notmore than one abbreviation will be used to indicate the same subject,nor must any one abbreviation be used with more than one meaning.

19

CHAPTER 5

DOCUMENT PREPARATION PROCEDURES

5.1 Implementation Methods

The UDS can be implemented using either automated or manual methods.While there are some features that are unique to each method, gener-ally the documents and the structures are the same for both. Thedifference is primarily the method (automated or manual) of completingthe standard formats and preparing the documents.

5.1.1 Manual Method

The manual techniques and format follow the automated method veryclosely. The format is the same, using 8 1/2 by 11 inch paper, and isshown in figures 1 and 2. The document content is organized accordingto the outline given in appendix A. The nature of the informationshould be that typically shown in the formats contained in volumes 2and 3 of this handbook. Only those formats applicable need to beused. The document then would be typewritten and reproduced accordingto local capability and regulations. Close coordination between therange and range user is essential during the draft stages of thedocuments. Documents at levels 1, 2, and 3 should follow the guidanceprovided in this handbook. Unique to the manual method is the reten-tion and use of the standard formats as blank forms. The formats involumes 2 and 3 of this handbook are examples of the formats to beused for the manual preparation of UDS documents and are displayed in12 pitch.

5.1.2 Automated Method

The requirement for electronic transmission and processing of UDSinformation has increased yearly. As a result, the automated UDSsystem must have flexibility to quickly adapt to changing userrequirements. An 8 1/2 by 11 inch format was selected for universalcompatibility. Primary considerations are to allow use of electronicprocessing and communications equipment to expedite processing of UDSdocuments, thus reducing reproduction and distribution time for docu-ment transactions between users, and also to allow easy access tomaster record storage. Other features of automation allow informationcoding, electronic sorting, and automatic data entry expansion capa-bility. The information content is the same as described in appendixA and the formats shown in volumes 2 and 3. Graphs, charts, andphotographs which are not readily adaptable to existing electronicstorage and transmission equipment may be handled separately as pro-vided in paragraph 2.7, Other Documentation.

The basic form for automated documentation is for requirements andsupport commitments to be recorded in separate documents, for example,a PRD and a PSP. An optional method provides for combined supportrequirements and commitments. This method generally is used where

20

support commitments are only a short or abbreviated response. How-ever, either the basic or the optional method of providing supportcommitments may be expanded by the support agency as necessary toprovide greater detail. If deemed necessary, a fully-worded reply maybe provided separately and can contain an engineering plan, an engi-neering implementation timetable, a funding plan, and a cost summaryin any degree of detail desired.

5.2 Page Format

The RCC Documentation Group recognizes that documentation preparation

resources vary at support ranges and within the user community. Theformat described here was developed to provide for minimum structureand maximum flexibility among UDS subscribers. Within the frameworkof this basic format, support ranges and users may develop UDSdocumentation to maximize preparation, publication, and dissemination.A degree of freedom may be used in the preparation of documentation;

however, the support range will identify the minimal UDS documentationrequired to process user requirements.

5.2.1 Classification Markings

Space has been provided at the top and bottom of each format page toaccommodate classification markings. The highest security classifica-tion of information appearing on a page will be centrally placed atthe top and bottom of the page. Computer-generated classificationmarkings will be made conspicuous with a space between each characterin the word and with a series of three asterisks before and after theclassification. Unclassified pages will also be marked; however, no

spaces will appear between each character in the word unclassified.For example

* * * UNCLASSIFIED * * *

***CONFIDENTIAL***

***SECRET***

Additional security markings will be appropriately placed by thecognizant security authority. The documenting agency is responsiblefor adjusting the formats to accommodate necessary security classifi-cation markings.

5.2.2 Format Structure

The UDS page format is 72 (10 or 12 pitch) horizontal characters and

66 vertical lines on a 8 1/2- by 11-inch page (see figures 1, 2, and3). The format is subdivided into three elements: header, body, and

footer. The body of the format page is separated from the headerand footer by a series of 72 equal signs (=), called break lines.Break lines permit easy access to the information while ignoring theheader and the footer. No line within the body may exceed 70 columns

* of text. The 71st column is always blank. Revised lines are identi-fied by placing an R in the 72nd column (see figures 1 through 3).

21

To maximize full page print, the format provides for the sequentiallisting of UDS sections and data descriptions. The UDS section titlesact as separators between UDS sections, while a series of 70 dashes(-) act as separators between individual items within the section. Toaccommodate the electronic exchange and processing, the standards,described next, have been applied to each of the format elements.

5.2.2.1 Header Standards

Each UDS document page shall contain a standard header consisting offive elements described below: classification, program title, docu-ment type/number, revision number, and date.

CLASSIFICATION: See paragraph 5.2.1.

PROGRAM TITLE: Identifies the title/name of the program docu-ment, for example, WIDGET.

DOCUMENT TYPE/NUMBER: Identifies the UDS document type(PI, SC, PRD, PSP, OR, OD) followed by the assigned program, operation,or other identification number, for example, PRD/11111.

REVISION: Identifies the revision number of the document.Original (unrevised) documents carry the revision number "00." Thisnumber shall be incremented by 1 with each published revision, forexample, 01, 02, 03.

Note: In some automated systems, the date of the revisionmay be used in lieu of the revision number. Revision mayalso be made to the requirement level by dating the lastchange to the individual requirement (see figure 3).

DATE: Identifies the publication date of the original documentor revision.

5.2.2.2 Body Standards

The body of each UDS section shall contain the appropriate informationto define program requirements or responses. In many cases, formatsand instructions have been devised to prompt the author for requiredinformation. In those cases, all applicable questions shall beanswered either with the appropriate information or other appropriatestatement to define the status of the information, for example,unknown, to be determined, to be furnished later, or an appropriatecross-reference. Nonapplicable prompts should be answered N/A or, ifthe capability exists, the prompt itself may be removed. The body ofevery section is divided into two elements: section number and title,and structured (SORT) labels for formatted or free-form text.

The section numbers and titles identified in the UDS Outline inappendix A will be used to identify the major sections of UDS docu-ments. Section numbers and titles shall start in column I of theprinted format. The use of subsections and titles is left to thediscretion of the documenting agency. The section number and title,for example, 1000 - Administrative, must be entered as a major

22

heading. The section number and title precede the subsection numbersand titles whether or not general information is included. Structured(SORT) labels and text provide for the electronic sorting and retrievalof data from an electronic data base. Disciplined compliance to datastructure is mandatory in automated systems to facilitate the transferof documents between data bases and for the retrieval of data baseinformation.

Additional structured (NON-SORT) labels are specifically identified onapplicable formats. When used, structured labels for all documentsshall start in column I of the printed format. When necessary tocontinue the data following a structured label, that data will beginin column 2. Free-form text data will begin in column 2. Some elec-tronic UDS systems may require that text start in other than column 2.In those cases, the local system data base manager will provide thenecessary supplemental information to users of those systems (seefigure 3).

Note: The labels need only be used if applicable. To bedetermined (TBD) will be entered following the label when datais applicable but not available. Nonapplicable labels willbe followed by N/A for manual systems only.

The following labeled standards and descriptions are shown next:

ITEM NO.:REQUESTER:

SUPPLIER:TEST CODE:LOCATION: (Support Formats Only)INFORMATION:REQUIREMENTS( ) INFORMATION( ):REQUIREMENTS:RESPONSE( ) INFORMATION( ):RESPONSE:

ITEM NO.: A sequential number, beginning at 01, identifying theitem listed under each UDS section. This label is used for eachrequirement, response, or informational item documented. The itemnumber used for responses to requirements is the same as that of thecorresponding item number appearing in the document. The corres-ponding document section number is listed for clarification. Inaddition, if there are supplemental support agency generated informa-tion items, explain the items )n UDS Format 1063 - Special Code Defi-nition. Other item-related information may be entered under thislabel as shown in figure 3.

REQUESTER: A code, identified on UDS Format 1063 - SpecialCode Definition, assigned to the requester of a requirement. Sub-requesters, similarly identified, will be indicated by the use of aslash (M) immediately following the requester code; for example,T/DE22 might indicate a requirement established by the NASA Johnson

* Space Center/Flight Requirements Office. Each requester/subrequestershall be separated by a space. It is recommended that, when possible,

23

either the assigned agency alphabetical code or the agency acronym asshown in appendix B be used as standard requester codes.

SUPPLIER: A code, identified on UDS Format 1063 - Special CodeDefinition, assigned to the organization providing support. Sub-suppliers are similarly identified by the use of a slash (/) immedi-ately following the supplier code. For example, W/SAC might indicatea response provided by the Western Test Range concerning a commitmentby the host SAC base. It is recommended that, when possible, eitherthe assigned agency alphabetical code or the agency acronym as shownin appendix B be used as standard supplier/subsupplier codes.

TEST CODE: A code, identified on UDS Format 1062 - Test CodeDefinition, assigned to a specific test requirement, response, orinformation item which identifies the various test activities. Thesetest codes are used as a method of correlating support requirements.Any support requirement referenced to a test code indicates that thissupport will be required during particular test program activity.

LOCATION: The location where the support is to be provided.

REQUIREMENT: A description of the user agency support require-ment.

RESPONSE: A description of the support agency response to a userrequirement.

Note: Some electronic UDS systems may require thatadditional commitment/response information be developed(see figure 3).

INFORMATION: A description of user or support agency data sub-mitted for informational purposes only. Information shall not beconstrued as a requirement nor as a response to a requirement.

Additional structured data may be required to satisfy the requirementsof electronic UDS systems. Data base managers of these systems areresponsible for providing any specialized formatting instructions totheir subscribers (see figures 1, 2, and 3).

5.2.2.3 Footer Standards

Each UDS document page shall contain a standard footer consisting ofthe following elements:

Page Number. Identifies the sequential page number within adocument starting with 1 at the first page of the document. Where adocument contains a series of tests, each test may be numbered usingthe test number followed by a sequential number starting with I on thefirst page of the test. Pages added to the beginning of a manuallyprepared document or imbedded text, as the result of a revision, willbe identified by the page number 0 followed by a sequential series ofdecimal numbers beginning at .1 for each page added. For example, twopages added at the beginning of a document will be numbered 0.1 and0.2. Pages added between two sequentially numbered pages, as the

24

result of a revision, will be identified by the addition of a decimalfollowing the page number of the preceding page, followed by a sequen-tial series of numbers beginning at 1 for each page added. For exam-ple, three pages added by revision and situated between pages 25 and26 will be numbered 25.1, 25.2, and 25.3. Pages added at the end of adocument, as the result of a revision, will take on the next sequen-tial page number following the last page.

Classification. (See paragraph 5.2.1.)

Format Number and Format Approval Date. Used for UDS documentcontrol purposes onTy, and not required to be shown (see paragraph2.10.2).

25

.......... 10 ........ 20 ........ 30 ........ 40 ....... 50 ........ 60 ........ 70.

H3 CLASSIFICATION: * * * UNCLASSIFIED * * *H4H5 PROGRAM TITLE: WIDGETH6 OOC TYPE/NO.: PRD/11111 REVISION: DATE: 03 MAR 86H7

B1 SECTION NUMBER - SECTION TITLE (EXAMPLE 1)B2B3 ITEM NO.: 0184 INFORMATION: TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT RB5 TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXTB6B7 SECTION NUMBER - SECTION TITLE (EXAMPLE 2)B8B9 ITEM NO.: 01BIO REQUESTER: T/DE22B11 TE T CODE: 01 02 03 04B12 REQUIREMENT(X) INFORMATION( ): TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT RB13 TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXTB14B15 SECTION NUMBER - SECTION TITLE (EXAMPLE 3)B16B17 ITEM NO.: 01B18 SUPPLIIER: W/SACB19 TEST CODE: 01 02 03 04820 RESPONSE(X) INFORMATION( ): TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXTB21 TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT RB22B23 SECTION NUMBER - SECTION TITLE (EXAMPLE 4)B24B25 ITEM NO.: 01B26 REQUESTER: T/DE22B27 SUPPLIER: W/SACB28 TEST CODE: 01 02 03 04B29 REQUIREMENT(X) INFORMATION( ): TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT ReB30 TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXTB31 RESPONSE(X) INFORMATION( ): TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT832B33B34 NOTE 1: The examples above represent a typical expression ofB35 requirements, responses, and informational data in the UDS836 using the manual or word-processing assisted methods ofB37 preparing unclassified documents.B38B39 EXAMPLE 1 = TYPICAL INFORMATIONAL ITEMB40 EXAMPLE 2 = TYPICAL REQUIREMENT ITEMB41 EXAMPLE 3 = TYPICAL RESPONSE ITEMB42 EXAMPLE 4 = TYPICAL REQUIREMENT/RESPONSE ITEM (COMBINED)B43B44 NOTE 2: Numbers 10-70, H1-H7, 81-853, and FI-F6 are for informationalB45 purposes and are not part of the format and are not printed.B46H = header, B = body and F = footer.B47B48B49 NOTE 3: THIS EXAMPLE FORMAT IS NOT TO SCALE.B50851

B52B53F1F2F3F4 CLASSIFICATION: ***UNCLASSIFIED*** UDS GEN RF 5 JAN 890F6 Figure 1. Example - manual/word processing format (unclassified).

26

H ......... 10 ........ 20 ........ 30 ........ 40 ........ 50 ........ 60 ........ 70.H2H3 (U) CLASSIFICATION: * * * CLASSIFIED * * *H4H5 (U) PROGRAM TITLE: WIDGETH6 (U) DOC TYPE/NO.: PRO/11111 REVISION: 00 DATE: 03 MAR 86H7

B1 (U) SECTION NUMBER - SECTION TITLE (EXAMPLE 1)B2B3 (U) ITEM NO.: 01B4 (U) INFORMATION: TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT RB5 (U) TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXTB6 ---B7 (U) SECTION NUMBER - SECTION TITLE (EXAMPLE 2)B8B9 (U) ITEM NO.: 01B10 (U) REQUESTER: T/DE22B11 U) TEST CODE: 01 02 03 04B12 (U) REQUIREMENT(X) INFORMATION( ): TEXT [EXT TEXT TEXT TEXT TEXT TEXT RB13 (U) TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXTB14B15 (U) SECTION NUMBER - SECTION TITLE (EXAMPLE 3)816B17 (U) ITEM NO.: 01B18 (U) SUPPLIIER: W/SACB19 (U) TEST CODE: 01 02 03 04B20 (U) RESPONSE(X) INFORMATION( ): TEXT TEXT TEXT TEXT TEXT TEXT TEXTB21 (U) TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT RB22B23 (U) SECTION NUMBER - SECTION TITLE (EXAMPLE 4)B24B25 (U) ITEM NO.: 01B26 (U) REQUESTER: T/DE2227 (U) SUPPLIER: W/SAC28 (U) TEST CODE: 01 02 03 0429 (U) REQUIREMENT(X) INFORMATION( ): TEXT TEXT TEXT TEXT TEXT TEXT TEXT R

B30 (U) TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXTB31 (U) RESPONSE(X) INFORMATION( ): TEXT TEXT TEXT TEXT TEXT TEXT TEXTB32 ------B33B34 (U) NOTE 1: The examples above represent a typical expression of835 (U) requirements, responses, and informational data in the UDSB36 (U) using the manual or word-processing assisted methods ofB37 (U) preparing classified documents.B38839 (U) EXAMPLE 1 = TYPICAL INFORMATIONAL ITEMB40 (U) EXAMPLE 2 = TYPICAL REQUIREMENT ITEMB41 (U) EXAMPLE 3 = TYPICAL RESPONSE ITEMB42 (U) EXAMPLE 4 = TYPICAL REQUIREMENT/RESPONSE ITEM (COMBINED)B43B44 (U) NOTE 2: THIS EXAMPLE FORMAT IS NOT TO SCALE.B45B46B47B48B49B50B51 (U)B52853 (U)F1F2F3F4 CLASSIFICATION: * * * CLASSIFIED * * * UDS GEN RF5 JAN 89F6 Figure 2. Example - manual/word processing format (classified).

27

Hj ......... 10 ........ 20 ........ 30 ........ 40 ........ 50 ........ 60 ........ 70.

H3 CLASSIFICATION: * * * UNCLASSIFIED * * *H4H5 PROGRAM TITLE: WIDGETH6 DOC TYPE/NO.: PRD/11111 REVISION: 03/12/86 DATE: 03 MAR 8fH7

=

B1 2805 - OTHER COMMUNICATIONS - TELEVISIONB2B3 ITEM NO.: AAAA BBBB CCCC DODD EEEE FFFFFFFF GB4 REQUESTER: HHHHHHHHHHHH HHHHHHHHHHHHH HHHHHHHHHHHHB5 SUPPLIER: IIIIIIIIIIII II I I III I I I I I

B6 TEST CODE: JJJJJJ JJJJJJ JJJJJJ JJJJJJ JJJJJJ JJJJJJ JJJJJJB7 TYPE EQUIPMENT: KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKB8 SUBJECT TO BE REVIEWED: KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKB9 LOCATION: KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKBIO PERIOD: KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKB11 PURPOSE/REMARKS: KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK RB12 RESPONSE: LLLLLLLLLL MMMMMM NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNB13 NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN RB14B15 NOTE 1: This example represents an automated UDS system format whereB16 each requirement and its response reside together in theB17 database. While the system maintains the basic UDS integrity81 data structure is strictly defined for electronic processing.B19B20 The following codes are used in the example above:B21B22 A - SEQUENTIAL ITEM NUMBERB23 B - UDS FORMAT NUMBER *B24 C - DATA BASE IDENTIFICATION CODE *B25 D - UDS SECTION NUMBER *B26 E - REQUIREMENT APPROVAL STATUS *B27 F - REQUIREMENT APPROVAL DATE *B28 G - REQUIREMENT SECURITY CLASSIFICATION *B29 H - REQUESTER/SUB-REQUESTER CODESB30 I - SUPPLIER/SUB-SUPPLIER CODESB31 J - TEST CODESB32 K - REQUIREMENT/TEXTB33 L - SUPPORT AGENCYB34 M - COMMITMENT DATEB35 N - RESPONSE TEXTB36 R - REVISION SYMBOLB37B38 NOTE 2: This format is a structured automated version correspondingB39 to UDS Section 2805.B40B41 NOTE 3: Data structures on automated systems vary due to hardware/B42 software limitations, therefore, a universal format for all843 systems is not yet defined. For this reason, format usage isB44 left flexible for the developer of the system. Any specialB45 codes developed will be explained in UDS Section 1603 -B46 Special Code Definition.B47B48 NOTE 4: THIS EXAMPLE FORMAT IS NOT TO SCALE.B49B50 * Examples of Item No. supplemental information.B51B52B53F1F2F3F4 CLASSIFICATION: * * * UNCLASSIFIED * * * UDS GENF5 JAN 8F6 Figure 3. Example - an automated system format (structured).

28

APPENDIX A

UDS OUTLINE

A-i

0APPENDIX A

UDS OUTLINE

DOCUMENT CODE: PI = PROGRAM INTRODUCTIONSC = STATEMENT OF CAPABILITYR = PROGRAM REQUIREMENTS DOCUMENT/OPERATION

REQUIREMENTSS = PROGRAM SUPPORT PLAN/OPERATIONS DIRECTIVE

DOCUMENT SECTION AND TITLE

PROGRAM ADMINISTRATIVE AND TECHNICAL INFORMATION - SECTION 1000

TO 1999

ADMINISTRATIVE

PI SC R S 1000 - AdministrativeR S 1010 - Approval AuthorityR S 1020 - Distribution ListR S 1030 - Revision ApprovalR S 1031 - Revision Control and ClassificationR S 1040 - Index of UDS Sections UsedR S 1050 - Program/Mission Security InformationR S 1052 - System Security Classification 0R S 1054 - System Security Classification MatrixR S 1056 - Security AuthorizationR S 1060 - PrefaceR S 1061 - Special Abbreviations and NomenclatureR S 1062 - Test Code DefinitionR S 1063 - Special Code DefinitionR S 1064 - Key Technical PersonnelR S 1065 - Technical References

PROGRAM/MISSION INFORMATION

PI SC R S 1100 - Program/Mission Information - Program DescriptionR S 1110 - Experiments DescriptionR 1120 - System Mission CapabilitiesR 1125 - System Functional DescriptionR 1130 - Mission/Test DescriptionR 1131 - Mission/Test ObjectivesR S 1140 - Test Program Operations Schedule

0A-2

SYSTEM INFORMATION - VEHICLE/TEST ITEM/SPACECRAFT/PAYLOAD

PI SC R 1300 - System InformationR 1310 - Vehicle/Test Item DescriptionR 1311 - Vehicle/Test Item CharacteristicsR 1312 - Vehicle/Test Item DrawingsR 1313 - Vehicle/Test Item Ordnance Items DescriptionR 1314 - Vehicle/Test Item Ordnance Items DrawingR 1315 - Vehicle/Test Item Flame Plasma Model of the Exhaust

PlumeR 1320 - Spacecraft/Payload DescriptionR 1321 - Spacecraft/Payload CharacteristicsR 1322 - Spacecraft/Payload DrawingsR 1323 - Spacecraft/Payload Ordnance Items DescriptionR 1324 - Spacecraft/Payload Ordnance Items DrawingR 1325 - Spacecraft/Payload Flame Plasma Model of the Exhaust

Plume

INSTRUMENTATION SYSTEMS - VEHICLE/TEST ITEM/SPACECRAFT/PAYLOAD

PI SC R 1400 - Instrumentation SystemsR S 1405 - Frequency Utilization Summary

METRIC TRACKING SYSTEMS - VEHICLE/TEST ITEM/SPACECRAFT/PAYLOAD

R 1410 - Metric Tracking Systems Operating DescriptionR 1411 - Metric Tracking Systems Transponder CharacteristicsR 1412 - Metric Tracking Systems Antenna SystemsR 1413 - Metric Tracking Systems Diagrams

TELEMETRY SYSTEMS - VEHICLE/TEST ITEM/SPACECRAFT/PAYLOAD

R 1420 - Telemetry Systems Operating DescriptionR 1421 - Telemetry Systems CharacteristicsR 1422 - Telemetry Systems Antenna SystemsR 1423 - Telemetry Systems DiagramsR 1424 - Telemetry Systems Analog Channel DescriptionR 1425 - Telemetry Systems Digital FormatR 1426 - Telemetry Systems Data Recorder Characteristics

COMMAND SYSTEMS - VEHICLE/TEST ITEM/SPACECRAFT/PAYLOAD

R 1430 - Command Systems Operating DescriptionR 1431 - Command Systems CharacteristicsR 1432 - Command Systems Antenna SystemsR 1433 - Command Systems Diagrams

VOICE CO>>IUNICATIONS SYSTEMS - VEHICLE/TEST ITEM/SPACECRAFT/PAYLOAD

R 1440 - Voice Communications Systems Operating DescriptionR 1441 - Voice Communications Systems Characteristics

A-3

R 1442 - Voice Communications Systems Antenna Systems

R 1443 - Voice Communications Systems Diagrams

COMPOSITE SYSTEMS - VEHICLE/TEST ITEM/SPACECRAFT/PAYLOAD

R 1450 - Composite Systems Operating DescriptionR 1451 - Composite Systems CharacteristicsR 1452 - Composite Systems Received Data CharacteristicsR 1453 - Composite Systems Transmitted Data CharacteristicsR 1454 - Composite Systems Antenna SystemsR 1455 - Composite Systems DiagramsR 1456 - Composite Systems Operating ModesR 1457 - Composite Systems Data Recorder Characteristics

TELEVISION SYSTEMS - VEHICLE/TEST ITEM/SPACECRAFT/PAYLOAD

R 1460 - Vehicle/Test Item Television Systems OperatingDescription

R 1461 - Vehicle/Test Item Television SystemsCharacteristics

R 1462 - Vehicle/Test Item Television Systems AntennaSystems

R 1463 - Vehicle/Test Item Television Systems FormatDescription

R 1465 - Spacecraft/Payload Television Systems OperatingDescription

R 1466 - Spacecraft/Payload Television Systems CharacteristicsR 1467 - Spacecraft/Payload Television Systems Antenna SystemsR 1468 - Spacecraft/Payload Television Systems Format

Description

OTHER SYSTEMS - VEHICLE/TEST ITEM/SPACECRAFT/PAYLOAD

R 1470 - Recovery Location AidsR 1480 - Other Systems

REQUESTING AGENCY'S SUPPORT INSTRUMENTATION/EQUIPMENT

PI SC R 1500 - Requesting Agency's Support Instrumentation/EquipmentR 1510 - Characteristics

SYSTEMS READINESS/PRELAUNCH TESTS

PI SC R 1600 - Systems Readiness/Prelaunch TestsR 1610 - Readiness/Prelaunch Tests IdentificationR 1620 - Readiness/Prelaunch Tests SequenceR 1630 - Readiness/Prelaunch Tests Terminal Countdown

TEST ENVELOPE INFORMATION

PI SC R 1700 - Test Envelope InformationR 1710 - Major Mission Events - Launch PhaseR 1711 - Major Mission Events - FlightR 1712 - Space Maneuver - Application of Thrust

A-4

TRAJECTORY INFORMATION

R 1720 - Trajectory Plan ViewsR 1721 - Trajectory Profile ViewsR 1722 - Launch TrajectoryR 1723 - Orbital and Space TrajectoryR 1724 - Terminal Trajectory

OPERATIONAL HAZARDS

PI SC R S 1800 - Operational HazardsR 1810 - Operational Hazards Reports

TEST/MISSION OPERATIONAL REQUIREMENTS - SECTIONS 2000 TO 6999

TEST OPERATIONAL CONCEPTS/SUMMARIES

PI SC R S 2000 - Test Operational Concepts/SummariesR S 2010 - Ground Support Instrumentation SummaryS 2020 - Support Plan SummaryS 2030 - Support CommitmentsS 2040 - Funding InformationS 2050 - Implementation ScheduleS 2051 - Personnel Assignment ScheduleS 2060 - Support Requirements Which Cannot Be MetS 2070 - Engineering PlanS 2071 - Engineering Plan - Alternate

S 2080 - Requester's ResponsibilitiesS 2098 - Flight Safety Operational ConceptsS 2099 - Range Derived Requirements

METRIC MEASUREMENT AND DATA

PI SC R S 2100 - Metric DataR S 2110 - Metric Data - LaunchR S 2111 - Metric Data - MidcourseR S 2112 - Metric Data - Orbital and SpaceR S 2114 - Metric Data - TerminalR S 2115 - Metric Data - SignatureR S 2116 - Metric Data - Other

S 2117 - Metric Data AccuraciesR S 2120 - Metric Data Parameter RecordingsR S 2130 - Metric Data Network CoverageR S 2160 - Metric Data CoverageR S 2170 - Metric Data - Engineering Sequential

0A- 5

0TELEMETRY MEASUREMENT AND DATA

PI SC R S 2200 - Telemetry DataR S 2210 - Telemetry Recording IntervalR S 2220 - Telemetry Analog Strip Chart Recording FormatR S 2230 - Telemetry Event Recording FormatR S 2240 - Telemetry Decommutation Processing SpecificationsR S 2260 - Telemetry Coverage

COMMAND CONTROL/DESTRUCT

PI SC R S 2300 - Command Control/DestructR S 2310 - Command ControlR S 2320 - Command DestructR S 2330 - Command Up-Data LinkR S 2340 - Command Up-Data Link RecordingsR S 2360 - Command Up-Data Link Stations Coverage

AIR/GROUND VOICE COMMUNICATIONS

PI SC R S 2400 - Air/Ground Voice CommunicationsR S 2410 - Air/Ground Voice Communications RecordingsR S 2460 - Air/Ground Voice Communications Coverage

COMPOSITE SYSTEMS

PI SC R S 2500 - Composite SystemsR S 2510 - Composite Systems - DetailR S 2520 - Composite Systems - Parameter RecordingsR S 2530 - Composite Systems - Event Recording FormatR S 2540 - Composite Systems - Analog Strip Chart Recording

FormatR S 2560 - Composite Systems Coverage

OTHER SYSTEMS

PI SC R S 2600 - Other SystemsR S 2601 - Other Systems - Directed EnergyR S 2605 - Other Systems - Support InstrumentationR S 2606 - Other Systems - EnvironmentalR S 2610 - Ot er Systems - DataR S 2660 - Other Systems Coverage

GROUND COMMUNICATIONS

PI SC R S 2700 - Ground CommunicationsR S 2710 - Ground Communications DetailR S 2720 - Ground Communications Network DrawingsR S 2730 - Ground Communications Network Transmission - VoiceR S 2731 - Ground Communications Network Transmission - Secure

VoiceR S 2733 - Ground Communications Network Transmission - TeletypeR S 2735 - Ground Communications Network Transmission - Secure

Data

A-6

R S 2736 - Ground Communications Network Transmission -Television/Data

R S 2737 - Ground Communications Network Transmission -Facsimile

R S 2740 - Ground Communications - Intercommunications SystemsR S 2760 - Ground Communications Terminations - VoiceR S 2761 - Ground Communications Terminations - Secure VoiceR S 2762 - Ground Communications Terminations - Point-to-PointR S 2763 - Ground Communications Terminations - TeletypeR S 2765 - Ground Communications Terminations - Secure DataR S 2766 - Ground Communications Terminations - Television/DataR S 2768 - Ground Communications Terminations - Voice RadioR S 2769 - Ground Communications Terminations - MiscellaneousR S 2770 - Ground Communications RecordingsR S 2780 - Ground Communications - Telephone

OTHER COMMUNICATIONS

PI SC R S 2800 - Other CommunicationsR S 2805 - Other Communications - TelevisionR S 2810 - Other Communications - TimingR S 2820 - Other Communications - SequencerR S 2830 - Other Communications - Visual Countdown and Status

Indicators

REALTIME DATA DISPLAY/CONTROL

PI SC R S 3000 - Realtime Data Display/ControlR S 3010 - Realtime Flight Control/Support CentersR S 3020 - Realtime Flight Control Data AcquisitionR S 3030 - Realtime Displays and ConsolesR S 3031 - Realtime DisplaysR S 3032 - Realtime Console Command PanelsR S 3033 - Realtime Console Analog RecordersR S 3034 - Realtime Console DrawingsS 3035 - Realtime Console Module DescriptionS 3036 - Realtime - Summary of Console LocationsS 3037 - Realtime - Summary of tonsole Module LocationsS 3038 - Realtime Data Displays and Consoles - Functional

Block DiagramS 3039 - Realtime - Other Group Displays and Controls

R S 3040 - Realtime Data FormatsR S 3041 - Realtime Tracking Data Format ControlR S 3042 - Realtime Telemetry Data Format ControlR S 3043 - Realtime Telemetry Data FormatsR S 3044 - Realtime Command Data Format ControlR S 3045 - Realtime Remote Site Data ProcessingR S 3050 - Realtime Data TestingR S 3060 - Realtime Data InterfacesR S 3061 - Realtime Data Interface CriteriaR S 3062 - Realtime Data Interface Criteria DrawingsR S 3070 - Realtime Data ComputerR S 3080 - Realtime Data Distribution

A-7

PHOTOGRAPHIC

PI SC R S 3100 - PhotographicR S 3110 - Photographic - DocumentaryR S 3120 - Photographic - Engineering

METEOROLOGICAL

PI SC R S 3200 - MeteorologicalR S 3210 - Meteorological - MinimaR S 3220 - Meteorological - ForecastsR S 3230 - Meteorological - ObservationsR S 3240 - Meteorological - Instrumentation Location DiagramR S 3250 - Meteorological - Space EnvironmentR S 3260 - Meteorological - Consultant Services

RECOVERY

PI SC R S 3300 - RecoveryR S 3310 - Recovery - Ships and Aircraft CoverageR S 3320 - Recovery - Items To Be RecoveredR S 3330 - Recovery - Salvage and DispositionR S 3340 - Recovery - Planned AreasR S 3350 - Recovery - Contingency AreasR S 3360 - Recovery - Abort Areas

OTHER TECHNICAL SUPPORT

PI SC R S 3400 - Other Technical SupportR S 3410 - Other Technical Support - AircraftR S 3411 - Other Technical Support - SeacraftR S 3420 - Other Technical Support - TargetsR S 3430 - Summary of Frequency ProtectionR S 3431 - Emitting Systems ProtectionR S 3440 - Geodetic and Gravitational DataR S 3450 - Other Technical Support - Training

MEDICAL

PI SC R S 3500 - MedicalR S .3505 - Medical - Bio-ScienceR S 3510 - Medical - Personnel - ActiveR S 3520 - Medical - Personnel - StandbyR S 3530 - Medical - Facility,Equipment,Services

PUBLIC AFFAIRS SERVICES

PI SC R S 3600 - Public Affairs ServicesR S 3610 - Public Affairs Services - Personnel AssignmentsR S 3620 - Public Affairs Services - News Media Personnel

Positions

A-8

DATA COORDINATE SYSTEMS

P1 SC R S 4000 - Data Coordinate Systems Description

DATA PROCESSING

P1 SC R S 4100 - Data Computer Processing SpecificationsR S 4110 - Data Computer Processing Specifications - DetailR S 4160 - Data Processing - Other

DATA DISPOSITION

PI SC R S 4200 - Data DispositionS 4201 - Data Disposition - Data Availability

R S 4205 - Data Disposition - ReportsR S 4210 - Data Disposition - Detail - Metric TrackingR S 4211 - Data Disposition - Detail - TelemetryR S 4214 - Data Disposition - EnvironmentalR S 4215 - Data Disposition - Detail - Voice/TV RecordingR S 4216 - Data Disposition - Detail - PhotographicR S 4217 - Data Disposition - Detail - MeteorologicalR S 4218 - Data Disposition - Detail - Computer ProcessingR S 4219 - Data Disposition - Detail - Miscellaneous

BASE FACILITIES/LOGISTICS

PI SC R S 5000 - Base Facilities/Logistics

PERSONNEL ASSIGNMENT SCHEDULES

P1 SC R S 5100 - Personnel Assignment SchedulesR S 5110 - Personnel Assignment Schedules - DetailR S 5120 - Personnel Assignment Schedules - Housing

TRANSPORTATION

PI SC R S 5200 - TransportationR S 5210 - Transportation - Surface Logistics ScheduleR S 5220 - Transportation - Air Logistics Schedule

SERVICES

PI SC R S 5300 - ServicesR S 5301 - Services - Administrative, Personnel, and OfficeR S 5302 - Services - Fire and RescueR S 5303 - Services - Security and SafetyR S 5304 - Services - Community, Education and Food ServiceR S 5305 - Services - Utilities (Electrical, Water, and

Sanitation)R S 5306 - Services - Procurement, Shipping, Receiving, and

Stock ControlR S 5307 - Services - Handling, Storage, and DisposalR S 5308 - Services - Air Conditioning and Environmental

Observations

A-9

R S 5309 - Services - Physical and/or Life Science ExperimentsR S 5310 - Services - Propellants, Gases, and ChemicalsR S 5320 - Services - Fuels and LubricantsR S 5330 - Services - Miscellaneous Lubricants, Hydraulic

Fluids, Preservatives, Etc.R S 5340 - Services - Vehicles and Land TransportationR S 5341 - Services - Ground Handling EquipmentR S 5350 - Services - Requesting Agency AircraftR S 5351 - Services - Air OperationsR S 5360 - Services - SeacraftR S 5361 - Services - Marine OperationsR S 5370 - Services - Chemical CleaningR S 5380 - Services - Purchase of Equipment or Supplies

LABORATORY

PI SC R S 5400 - LaboratoryR S 5405 - Laboratory - Technical Shops and LabsR S 5410 - Laboratory - Chemical and Physical AnalysisR S 5420 - Laboratory - Special Environment

MAINTENANCE

PI SC R S 5500 - Maintenance

R S 5510 - Maintenance - Buildings and Grounds

FACILITIES

PI SC R S 5600 - FacilitiesR S 5610 - Facilities - DrawingsR S 5620 - Facilities - Launcher and Platform Characteristics

OTHER SUPPORT

PI SC R S 6000 - Other SupportR S 6010 - Other Support - Test Instrument Maintenance and

CalibrationPI R 6020 - Other Support - Requirements for Support Agencies

A-10

APPENDIX B

DESIGNATIONS FOR liDS SUBSCRIBER AGENCIES,

B-i

APPENDIX B

DESIGNATIONS FOR UDS SUBSCRIBER AGENCIES

AGENCY ALPHABETICAL AGENCYACRONYM CODE

WSMR A White Sands Missile Range, NMLeRC B Lewis Research Center, Cleveland, OHNWS C National Weather Service, Washington, DCDOD D Department of Defense, The PentagonESMC E Eastern Space and Missile Center, Patrick AFB, FLAFFTC F Air Force Flight Test Center, Edwards AFB, CAGSFC G Goddard Space Flight Center, Greenbelt, MDMSFC H Marshall Space Flight Center, Redstone Arsenal, ALLaRC I Langley Research Center, Hampton, VAJPL J Jet Propulsion Laboratory, Pasadena, CAKSC K Kennedy Space Center, Cape Canaveral, FLNWC L Naval Weapons Center, China Lake, CAARC M Ames Research Center, Moffett Field, CAPMTC N Pacific Missile Test Center, Point Mugu, CANOMTS 0 Naval Ordnance Missile Test Station, WSMR, NMMSD P Munitions Systems Division, Eglin AFB, FLWFF Q Wallops Flight Facility, Wallops Island, VAERDC R Electronics Research and Development Command,

Fort Monmouth, NJCSTC S Consolidated Space Test Center, Onizuka AFB, CAJSC T Johnson Space Center, Houston, TXASDC U U.S. Army Strategic Defense Command, Washington, DCUSAKA V U.S. Army Kwajalein Atoll, Marshall IslandsWSMC W Western Space and Missile Center, Vandenberg AFB, CADFRF X Dryden Flight Research Facility, Edwards AFB, CANASA Y National Aeronautics Space Administration

Headquarters, Washington, DCWSTF Z JSC White Sands Test Facility, WSMR, NMAFWL AA Air Force Weapons Laboratory, Albuquerque, NMARMTE AB Army Materiel Test and Evaluation Command, WSMR, NMUTTR AC Utah Test and Training Range, Hill AFB, UTYPG AD Yuma Proving Ground, Yuma, AZAFWTF AE Atlantic Fleet Weapons Training Facility,

Roosevelt Roads, Puerto RicoTFWC AF Tactical Fighter Weapons Center, Nellis AFB, NVNATC AG Naval Air Test Center, Patuxent River, MDAFOTEC AH Air Force Operational Test and Evaluation Center,

Vandenberg AFB, CAPMRF AJ Pacific Missile Range Facility,

Barking Sands, Kauai, HICSOC AS Consolidated Space Operations Center, Falcon AFS, CO

NOTE: For additions or deletions to this list, contact the RCC Secretariat at(505) 678-1107/1108, Autovon 258-1107/1108.

B-2