Attachment_05_-_UDS.pdf

WHITE SANDS MISSILE RANGE

REAGAN TEST SITE

YUMA PROVING GROUND

DUGWAY PROVING GROUND

ABERDEEN TEST CENTER

NAVAL AIR WARFARE CENTER WEAPONS DIVISION, PT. MUGU

NAVAL AIR WARFARE CENTER WEAPONS DIVISION, CHINA LAKE

NAVAL AIR WARFARE CENTER AIRCRAFT DIVISION, PATUXENT RIVER

NAVAL UNDERSEA WARFARE CENTER DIVISION, NEWPORT

PACIFIC MISSILE RANGE FACILITY

NAVAL UNDERSEA WARFARE CENTER DIVISION, KEYPORT

30TH SPACE WING

45TH SPACE WING

AIR FORCE FLIGHT TEST CENTER

AIR ARMAMENT CENTER

ARNOLD ENGINEERING DEVELOPMENT CENTER

NATIONAL AERONAUTICS AND SPACE ADMINISTRATION

RANGE OPERATIONS GROUP

DOCUMENT 501-12

UNIVERSAL DOCUMENTATION SYSTEM

DISTRIBUTION A: APPROVED FOR PUBLIC RELEASE

DISTRIBUTION IS UNLIMITED

This page intentionally left blank.

DOCUMENT 501-12

UNIVERSAL DOCUMENTATION SYSTEM

JULY 2012

Prepared by

RANGE OPERATIONS GROUP

RANGE COMMANDERS COUNCIL

Published by

Secretariat Range Commanders Council White Sands Missile Range

New Mexico 88002-5110 v

TABLE OF CONTENTS

PREFACE.................................................................................................................................... vii

ACRONYMS................................................................................................................................ ix

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

1.1 General ........................................................................................................... 1-1

1.2 Applicability .................................................................................................. 1-1

1.3 Authority ........................................................................................................ 1-1

1.4 Handbook Revision........................................................................................ 1-1

1.5 Definitions...................................................................................................... 1-1

1.6 Information and Assistance Sources .............................................................. 1-2

CHAPTER 2 ORGANIZATION AND STRUCTURE.................................................... 2-1

2.1 Purpose........................................................................................................... 2-1

2.2 Objectives ...................................................................................................... 2-1

2.3 Concept .......................................................................................................... 2-1

2.4 System Criteria............................................................................................... 2-1

2.5 Document Organization ................................................................................. 2-1

2.6 Document Extracts......................................................................................... 2-2

2.7 Other Documentation..................................................................................... 2-3

2.8 Draft Documentation Review Conferences ................................................... 2-3

2.9 Document Structure ....................................................................................... 2-3

2.10 Document Implementation............................................................................. 2-4

2.11 Security Classification ................................................................................... 2-4

2.12 Document Revision........................................................................................ 2-4

2.13 Document Distribution................................................................................... 2-5

2.14 Document Cancellation.................................................................................. 2-5

CHAPTER 3 REQUESTING AGENCY REQUIREMENTS DOCUMENTATION... 3-1

3.1 General ........................................................................................................... 3-1

3.2 Requirement Priority Classification............................................................... 3-1

3.3 Requirements Documentation (PI, PRD, OR) ............................................... 3-1

3.4 Requirements Documentation Lead Time ..................................................... 3-2

CHAPTER 4 SUPPORT AGENCY RESPONSE DOCUMENTATION ...................... 4-1

4.1 General ........................................................................................................... 4-1

4.2 Support Documentation (SC, PSP, OD) ........................................................ 4-1

CHAPTER 5 UDS PREPARATION INSTRUCTIONS.................................................. 5-1

5.1 General ........................................................................................................... 5-1

5.2 UDS Format Instructions ............................................................................... 5-1

APPENDIX A DESIGNATION FOR UDS SUBSCRIBER AGENCIES ....................... A-1

APPENDIX B UDS DOCUMENT OUTLINE .................................................................. B-1 vi

APPENDIX C UDS FORMATS.......................................................................................... C-1

APPENDIX D OPSEC and SECURITY CHECKLIST ................................................... D-1 vii

PREFACE

The Range Commanders Council (RCC) recognizes the need for rapid turnaround of range user requirements and the efficiencies to be derived from electronic data processing systems;

therefore, the Universal Documentation System (UDS) handbook was developed and maintains a format adaptable to electronic data processing.

This edition of the UDS handbook supersedes all previous issues of the handbook. Existing programs may use the previous procedures and forms as agreed between the requesting agency (RA) and the support agency (SA). All new programs developing documentation will use the procedures and formats contained in this version of the handbook.

CHANGES TO THIS 2009 EDITION

Change 1 Appendix C has been modified to get away from the previous “Teletype Format” and wherever possible a “fill in the form” response has been added to simplify and clarify the requester and supplier inputs.

Change 2 Chapter 5 of this document has been modified to explain the information needed to populate the new “fill in the form” inputs. This chapter also has additional instructions for each input required in the formats. Each of the format sub-headings in Appendix C has an input instruction in chapter 5.

Copies of this handbook may be obtained from any agency listed in paragraph 1.6, from the RCC web site (http://www.wsmr.army.mil/RCCsite/Pages/default.aspx), or by contacting the RCC Secretariat office as follows:

Secretariat Range Commanders Council Attn: STEWS-RCC White Sands Missile Range, New Mexico 88002-5110

Comm 575-678-1107 DSN 258-1107 E-mail: usarmy.wsmr.atec.list.rcc@mail.mil viii ix

ACRONYMS

μs microsecond A audio AGCL automatic ground control landing AM amplitude modulation AOS acquisition of signal ATC approval to connect ATO approval to operate AV audio/video BO burnout BPS bits per second C confidential CATEX categorical exclusion C.C. cloud coverage CD calendar days CEP circular error probable CNWDI Critical Nuclear Weapon Design Information COMSEC Communication Security CRT cathode ray tube CW continuous wave CY calendar year C&A Certification and Accreditation D desired DAA Designated Approval Authority dB decibel dBi decibel isotropic dBm power ratio in decibels of the measured power referenced to one milliwatt DD Department of Defense Dens density DIACAP DoD IA Certification and Accreditation Process DoD Department of Defense DoDD Department of Defense Directive DoDI Department of Defense Instruction DOT Department of Transportation DPAS Defense Priority and Allocations System (Refer to DoD Directive 4400.1) DSS Defense Security Service EA environmental assessment EC Executive Committee EFTO encrypt for transmission only EIA Electronics Industry Association EIS Environmental Impact Statement EMSEC Emission Security EO Executive Order FISMA Federal Information Security Management Act FM frequency modulation FM/FSK frequency modulation/frequency shift keying x

FOPSK Feher’s offset phase shift keying FTS flight termination system FY fiscal year gal gallon GET ground elapsed time GHz gigahertz GPS Global Positioning System IMP impact IPG information protection guide ips inches per second IRIG Inter-Range Instrumentation Group ISDF Industrial Security Facilities Database K Kelvin kHz kilohertz km kilometers kpps thousands of pulses per second lb pound LOS loss of signal LOX liquid oxygen M mandatory MHz megahertz MIL-STD military standard mm/s millimeters per second MRTFB Major Range and Test Facility Base ms millisecond NASA National Aeronautics and Space Administration NEPA National Environmental Policy Act NISP National Industrial Security Program NISPOM National Industrial Security Program Operating Manual NOAA National Oceanic and Atmospheric Administration NRZ non-return-to-zero OCA Original Classification Authority OD Operations Directive OPSK offset phase shift keying OIS operational intercommunications system OPSEC Operations Security OR Operation Requirements ORE Operation Requirements Extract PAM/FM pulse amplitude modulation/frequency modulation PCM pulse code modulation PCM/FM pulse code modulation/frequency modulation PDM/FM pulse duration modulation/frequency modulation PM/FM phase modulation/frequency modulation PI program introduction POC point of contact POL petroleum, oil, and lubricant xi

PPP program protection plan pph pulses per hour ppm pulses per minute pps pulses per second PRD program requirements document PRDE program requirements document extract PRF pulse repetition frequency Precip precipitation Pres pressure PSP program support plan QTR quarter QTY quantity R required RA requesting agency RCC Range Commanders Council RD restricted data RF radio frequency R.H. relative humidity R.I. refractive index ROG Range Operations Group RPS revolutions per second RTDS real-time data system RTZ return-to-zero S secret SA support agency SAR special access required SC statement of capability SCG security classification guide SCO subcarrier oscillator SEP separation SPS samples per second SRO static return to off S.S. sea state SVP underwater sound velocity profile TACAN tactical air navigation Temp temperature TOPS transistorized operations phone system TS top secret TVC thrust vector control UDS Universal Documentation System V video Visb visibility VTC video teleconferencing VV&A verification, validation, and accreditation WARC World Administrative Radio Conference xii

1-1

CHAPTER 1

INTRODUCTION

1.1 General

This handbook describes the UDS. The UDS is used to formally document RA program support requirements and SA capabilities and commitments to support those requirements.

A complete list of RCC documents pertaining to the UDS and to other documents is available on the RCC website (http://www.wsmr.army.mil/RCCsite/Pages/default.aspx). Copies can be provided through the RCC Secretariat at the address stated in the preface.

1.2 Applicability

The UDS is expected to be used by all agencies desiring support from RCC member ranges that have adopted the UDS. RA requirements documents and SA response documents will be prepared in accordance with the formats and procedures in this handbook and with those supplemental instructions prepared by the SAs.

1.3 Authority

The Range Operations Group (ROG) of the 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 must be made to the ROG. Such recommendations must include the reason for the change, deletion, or addition and a sample of the change with its instructions. The ROG will review the recommendation, and upon approval, will incorporate these changes. At the discretion of the ROG, approval of recommended changes will be deferred to the RCC Executive Committee (EC).

1.5 Definitions

Frequently used terms in this handbook are defined as follows.

Range/Support Agency: An operational facility that provides support services to qualified users as determined by current directives. The words “range,” “center,” and “support agency” are used interchangeably.

User/Requesting Agency: Any United States or foreign government agency, industrial organization, or other institution with authority to use range or SA resources.

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

1-2

User Requirement: Any item of support stated by an RA through the UDS.

Requester/Supplier Code: An element of UDS formats (see subparagraph 2.9.3) as identified in Appendix A - Designation for UDS Subscriber Agencies of this handbook.

Interagency Program: The participation of more than one range or SA in a program.

Lead Range/Lead Support Agency: Responsible range/SA for coordinating total support planning and operations for a particular program, mission, or test. The lead range/lead support agency identifies the support required from other agencies and coordinates the total support effort.

1.6 Information and Assistance Sources

Prospective users of range/SA services may obtain assistance in the preparation of requirements documentation from the agencies listed below.

412 TW/TSRO

Edwards AFB, CA 93524-6680

PHONE: DSN - 527-2726 COMMERCIAL - (805) 277-3416

FAX: DSN - 527-5377 COMMERCIAL - (805) 277-5377

Naval Air Warfare Center Weapons Division

NAWCWPNS CODE 52911EE

Point Mugu, CA 93042-5001

PHONE: DSN: 351-7856 COMMERCIAL: (805) 989-7856

FAX: DSN: 351-7418 COMMERCIAL: (805) 989-7418

30th Range Squadron/DOUF Building 7000 816 13th St., Suite 205 Vandenberg AFB, CA 93437-5233

PHONE: DSN: 276-3953 COMMERCIAL: (805) 734-8232 EXT: 63953

FAX: DSN: 276-1640 COMMERCIAL: (805) 734-8232 EXT: 61640

ITT/FSC/Code 7600 ITT Federal Services Corp Vandenberg AFB, CA 93437

PHONE: DSN: 276-1245 COMMERCIAL: (805) 734-8232, EXT 61245

FAX: DSN: 275-0364 COMMERCIAL: (805) 734-8232, EXT 50364

45th Space Wing 45SW/XP (Plans) 1201 Minuteman St.

Patrick AFB, FL 32925-3239

PHONE: DSN: 854-4054 COMMERCIAL: (407) 494-4054

1-3

FAX: DSN: 854-6839 COMMERCIAL: (407) 494-6839

Pacific Missile Range Facility Barking Sands P.O. Box 128 Kekaha, HI 96752-0128

PHONE: DSN: COMMERCIAL: (808) 335-4253

FAX: DSN: COMMERCIAL: (808) 335-4484

Kwajalein Support Directorate

CSSD-KH-SP

P.O. Box 1500 Huntsville, AL 35807

PHONE: DSN: 645-1874 COMMERCIAL: (205) 955-1874

FAX: DSN: 645-1979 COMMERCIAL: (205) 955-1979

Teledyne Brown Eng M/S 132 300 Sparkman Dr. N.W.

Huntsville, AL 35807-7007

PHONE: DSN: COMMERCIAL: (205) 726-2581

FAX: DSN: COMMERCIAL: (205) 726-2695

50th Space Wing

750 OSS/DOX

1080 Lockheed Way Box 058 Sunnyvale, CA 94089-1237

PHONE: DSN: 561-3796 COMMERCIAL: (408) 752-3796

FAX: DSN: 561-4084 COMMERCIAL: (408) 752-4084

50th Space Wing

50 SW/XPSV

300 O’Malley Ave STE 74 Falcon AFB, CO 80912-3074

PHONE: DSN: 560-2087 COMMERCIAL: (719) 567-2087

PHONE: DSN: 560-4661 COMMERCIAL: (719) 567-4661

FAX: DSN: 560-2655 COMMERCIAL: (719) 567-2655

Goddard Space Flight Center Center Mission Services Manager, Code 450 Greenbelt, MD 20771

PHONE: DSN: COMMERCIAL: (301) 286-6724

FAX: DSN: COMMERCIAL: (301) 286-1725

NASA-Air Force Management Office/IM-NAO Kennedy Space Center, FL 32899

PHONE: DSN: 854-6272 COMMERCIAL: (407) 494-6272

PHONE: DSN: 854-6274 COMMERCIAL: (407) 494-6274

1-4

FAX: DSN: 854-9166 COMMERCIAL: (407) 494-9166

U.S. Army White Sands Missile Range/STEWS-NRO-BP White Sands Missile Range, NM 88002-5113

PHONE: DSN: 258-3812 COMMERCIAL: (575) 678-3812

FAX: DSN: 258-1904 COMMERCIAL: (575) 678-1904

99th Range Group/CCXT 3770 Duffer Drive Nellis AFB, NV

PHONE: DSN: 682-3655 COMMERCIAL: (702) 652-3655

FAX: DSN: 682-3808 COMMERCIAL: (702) 652-3808

2-1

CHAPTER 2

ORGANIZATION AND STRUCTURE

2.1 Purpose

The UDS provides a common language and format for stating requirements and for preparing support responses. The UDS encompasses documentation generated by RAs that states program, mission, or test requirements and those response documents generated by the SAs to define the support to be provided.

2.2 Objectives

The UDS objectives are as follows.

Establish a common language and format to provide more effective communication between the RA and SA.

Standardize requirement and support methodology between the RA and the SA that achieves an effective planning/performance interface.

Provide a standard yet flexible and dynamic system that meets the requirement and support needs of both simple and complex programs.

2.3 Concept

The UDS is intended to establish standardization, yet be flexible enough to be used by a number of different agencies. This flexibility permits individual instructions to be prepared by each SA for implementation of the UDS at that agency. These instructions can contain specific procedures for the scope, submission, and revision of documentation.

2.4 System Criteria

The UDS is based on a common structure that enables users to employ one basic format when presenting requirements to SAs. This structure is defined in a document outline that combines related subjects of the various program, mission, or test phases into broad categories for simplicity and ease of understanding. This system identifies the necessary information that should pass between the RA and all contributing agencies that support the program, mission, or test.

2.5 Document Organization

The UDS handbook describes three levels of RA and SA documentation. Generally the three levels of documentation will be required, with all being negotiable between the RA and the SA.

LEVEL REQUIREMENTS DOCUMENT RESPONSE DOCUMENT

1 Program Introduction (PI) Statement of Capability (SC) 2 Program Requirements Document (PRD) Program Support Plan (PSP)

2-2

3 Operation Requirements (OR) Operations Directive (OD)

Level 1 documents (the PI and SC) are used to initiate program support planning between RAs and SAs.

Level 2 documents (PRD and PSP) are used to provide additional or more detailed program information with specific application to the more complex programs.

Level 3 documents (OR and OD) are used to request and plan support for specific test operations within an all-encompassing program.

2.5.1 Level 1 Documents

Program Introduction: The PI is the initial planning document submitted by an RA to the SA immediately on identification of the scope and duration of a program activity. The RA should submit the PI using the best available information, enabling the SA to initiate resource and technical planning. This information, while sometimes fragmentary and incomplete, is of substantial value to the SA in determining the scope of the program. For some programs, the PI could eliminate further documentation if the SA determines the level of detail is extensive enough to proceed with producing an OD.

Statement of Capability: The SC is the SA's response to the PI. When properly signed, the SC is evidence that a program has been accepted for support by the SA. Support conditions, qualifications and resources, or other considerations are initially identified in this document, which serves as a baseline reference for subsequent acceptance and commitment by the SA.

2.5.2 Level 2 Documents

Program Requirements Document: The PRD is prepared by the range user and is a detailed program planning document required for complex or long lead time programs.

Program Support Plan: The PSP is a response to the requirements presented in the PRD and is prepared by the responsible SA.

2.5.3 Level 3 Documents

Operation Requirements: The OR is a detailed description of the program’s requirements for each specific test or series of tests. It is prepared by the user.

Operations Directive: The OD is the SA’s response to an OR and is the detailed plan for implementation of support for a program, mission, specific test, or series of tests.

2.6 Document Extracts

Document extracts relate to requirements placed on a given SA that result in the generation of additional requirements that must be placed on other agencies. Requirements relate to the lead

2-3

SA concept where one agency is given overall support responsibility when the total support involves a number of agencies.

Examples of document extracts are as follows.

Program Requirements Document Extract (PRDE): A PRDE becomes necessary when requirements placed on a supporting agency create requirements that must be levied on other agencies. Requirements are prepared using PRD formats in accordance with the standard UDS outline.

Operation Requirements Extract (ORE): An ORE is similar to the PRDE except that it applies to the OR. It relates to the concept where the lead agency must levy requirements on other agencies. In general, basic ORE requirements will be extracted from the user’s original OR and may be expanded upon by the lead agency.

2.7 Other Documentation

Program, mission, or test requirements documents must be understandable and stand on their own; however, there is some supporting information that must be documented and related to the requirements, so support may be provided. Examples are antenna patterns, trajectory data, pyrotechnics, range safety procedures, schedules, test operation procedures, security guides, and mission go/no go rules. If this information is documented separately, it must be referenced in the UDS program documentation.

2.8 Draft Documentation Review Conferences

When PI, PRD, and OR drafts are prepared, conferences should be held to discuss the complexity of the support and to consider foreseeable difficulties. These conferences provide the opportunity to initiate program coordination, to discuss security classifications, and to assess support questions. The RA distributes the draft and advises all interested RA and SA personnel when and if they should attend the review conference.

2.9 Document Structure

The UDS provides a building block concept to develop and to present requirements that result from incomplete program objectives to well-defined operational and developmental objectives for the system to be evaluated.

2.9.1 General

Requirements documents are extensions of each other and are used exclusively or in tandem with each other depending on the size and complexity of the program.

2.9.2 Document Outline

The UDS document outline in Appendix B is a common numbering system providing a standard presentation of information and serving as the framework for all documents within the UDS.

Format numbers and associated titles are controlled and assigned by the RCC ROG.

2-4

The UDS outline is composed of two major groups:

Formats 1000 - 1999 contain program administrative and technical information.

Formats 2000 - 6999 contain test/mission operational requirements.

2.9.3 UDS Formats

The UDS formats are structured to provide a definitive area in which to state requirements and specify SA responses. The UDS outline, coupled with pre-defined formats and instructions contained in the UDS handbook, serves as a checklist to prevent pertinent data from being overlooked. Only those UDS formats that best suit the needs of the particular program, mission, or test being documented should be used. The UDS documents are not to be limited to the statement of pure requirements or responses. Informational data may be provided as deemed necessary to clarify stated requirements and responses. Descriptive pictures, sketches, or graphics are encouraged. If the information or background material is voluminous, reference to a supplemental document should be considered. Supplemental documentation should be cross-referenced in the UDS document.

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 (that is, a PI and SC that contain total program information), it is also acceptable to have several PIs and SCs. This latter approach is used when different SAs provide support for unique and unrelated phases of a program, mission, or test.

For example, one agency supports engine tests for program “X” while another agency provides in-orbit support for program “X.”

The same philosophy applies to level 2 documents. A single PRD and PSP will, wherever practical, contain all program-level information; however, it is acceptable to have multiple PRDs and PSPs as explained above.

The most detailed level of requirements and support is contained in level 3 documents that describe specific requirements and support. The OR/OD documents will be prepared as single or multiple documents as required for effective management at the RAs and SAs.

2.11 Security Classification

The originating agency of a UDS document is responsible for identifying the information to be protected, including application of the proper security classification designators and any other special security markings required. When the classified sections of large documents are few in number, it may be expedient to provide unclassified basic documents with the classified portions provided in a separate classified document extract. Classified extracts will have limited distribution and be subject to the control imposed by their classification. Classified extracts should be cross-referenced in the basic unclassified document.

2.12 Document Revision

2-5

A revision is considered to be any information added, deleted, or revised in any section of a UDS document. Revisions may be made either by preparing a completely new document or by submitting the revised information. In any case, users are requested to discuss all proposed revisions with the lead SA. Pen and ink revisions submitted by letter are permissible for small changes; however, the changes should be incorporated into the next revision to the document.

The UDS documents will reflect the revision number and date of the revision. Revisions shall be numbered consecutively beginning at 01. It is recommended that the basic document be reissued, incorporating all revisions when the number of revisions causes the document to be unmanageable. Format 1030 - Revision Control and Classification will be used to identify the scope of the revision and shall be transmitted with any revised pages. Format 1030 also provides a historical record of revisions made to the document.

A standard change indicator or the use of the symbol “R” in the right-hand margin to identify revised lines in a format is encouraged. In subsequent revisions of a section, delete all “Rs” applicable to the preceding revision.

2.13 Document Distribution

Each document should contain its own document distribution list (Format 1020). This format lists the agencies or activities to receive the document and the number of copies each should receive. The originator will identify distribution for requirements documents.

Add additional distribution statements and reproduction and destruction notices as information included on the front cover.

2.14 Document Cancellation

The originator notifies the lead SA when a PI, PRD, or OR is to be canceled.

2-6

3-1

CHAPTER 3

REQUESTING AGENCY REQUIREMENTS DOCUMENTATION

3.1 General

Requirements documents PI, PRD, and OR are prepared by the RA according to a schedule negotiated by the lead agency and RA. The requirements for a program, mission, or test are included in a PI, PRD, or OR document, or in combinations as the program, mission, or test size dictate. The initial issue of each document includes the information needed to present the requirements that are known at the time of issue. Emphasis should initially be placed on identifying requirements that call for long-range planning action even though specific use or implementation details may not be known. As more information becomes available, revisions are made to incorporate the additional data. The prime consideration is to ensure the earliest possible receipt of requirement information at the SA. The user is responsible for ensuring that requirements are promptly submitted at the request of the SA and in accordance with scheduled lead times to allow for planning, funding, software development, and construction; that requirements documents reflect all major requirements; that all requirements are necessary to meet the program and mission/test objectives; and that all requirements have been officially approved and signed. The user is also responsible for ensuring that each requirements document contains a Format 1020 - Distribution List and that the list identifies the number of copies needed to fulfill the user organization distribution requirements.

3.2 Requirement Priority Classification

A priority must be defined to evaluate requirements on an overall program, mission, or test basis.

The three classifications, defined next, are Mandatory, Required, and Desired.

Mandatory (M): A mandatory classification is the minimum requirement that is essential to achieve program, mission, or test objectives.

Required (R): A required classification is support that would materially aid in achieving all objectives and is necessary for detailed analysis of system performance.

Desired (D): A desired classification is any support that can be obtained in addition to the mandatory or required classification.

3.3 Requirements Documentation (PI, PRD, OR)

Requirements documentation is compiled in accordance with the general instructions contained in this handbook and the appended formats.

3.3.1 Program Introduction

The PI is the document that officially introduces a program, mission, or test to an SA and establishes the scope of program activity. Within the defined scope, the user has freedom in planning specific operations in detail.

3-2

New program requirements may impose a need for additional tracking coverage, additional data products, different frequencies, or other accommodations not available at the support range. The criteria and qualifications of such requirements should be stressed in the PI. Users with programs involving orbital operations or large weapon systems should consider the program in phases. Phase examples are prelaunch, orbital, recovery, test location, development, and system components. In these cases, the user should identify those requirements that differ and those that are unique to a particular phase. If a particular requirement is program-wide and does not differ, then such a distinction is not necessary.

3.3.2 Program Requirements Document

The PRD, as a detailed program planning document, contains the user’s desired support requirements from the SA and may contain supplemental information needed for clarity. The need for a PRD is determined during the analysis of the PI or during early planning meetings and will be stated in the SC. The user should not delay submittal of the PRD because of incomplete knowledge of support requirements. The PRD is normally submitted by the RA according to a schedule negotiated by the lead SA and the user.

3.3.3 Operation Requirements

The OR is a mission-oriented document that describes in detail the program’s requirements for each mission, specific test, or series of tests and is prepared by the user. The PRD and OR must be complete documents capable of standing alone. The OR should not reflect new requirements that were not previously stated in the PI and/or PRD.

3.4 Requirements Documentation Lead Time

Lead times for initial documentation may vary considerably from program to program depending on the scope of support needed. Requirements documentation lead times are established through negotiation between the RA and SA. Nominal lead times in years, based on past experience, are presented in the following table.

Nominal Lead Times Program Support Requirement Lead Time (year)

New facility construction 3 1/2 Extensive software development or additions to instrumentation (not requiring major facility construction)

2 1/2

Moderate software development or instrumentation additions funded by the user

Minor software development or instrumentation improvements

1/2

4-1

CHAPTER 4

SUPPORT AGENCY RESPONSE DOCUMENTATION

4.1 General

This chapter pertains specifically to SA documentation. The SA response documents SC, PSP, and OD are prepared by the SA in response to the approved requirements prepared and submitted by the RA. Response documents are revised by the SA when requirements are changed or support is revised.

SAs will assign a document number, establish a suspense date for the publication of the resulting support documentation, notify the various support organizations of the suspense date, and publish requirements document extracts.

4.2 Support Documentation (SC, PSP, OD)

Support documentation is compiled in accordance with the general instructions contained in this handbook and the appended formats.

4.2.1 Statement of Capability

The SC provides a response to the user’s PI. The PI, in combination with the approved SC, forms a basic agreement between the RA and the SA and guides the more detailed planning directives to support organizations.

Wherever possible, the SC responds to the PI on an item-for-item basis. Responses may be presented in the general format specified by the UDS when further breakdown is not warranted.

In some cases, the SA may respond to the PI on an exception basis rather than with a definitive support plan. Also at the discretion of the SA, commonly supplied items and requirements 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 SA capability will not meet the requirements stated in the PI, the SC specifies such restraints and limitations. The SC may also serve to support funding policy directives, provide rough order of magnitude (ROM) cost estimates, and assign existing facilities (such as launch complexes, office space, assembly, and storage areas) available to meet requirements stated in the PI. If the user requires new construction, the SC may provide site approval by the SA.

4.2.2 Program Support Plan

The PSP is the SA’s response to the PRD. The initial PSP issue includes an item-for-item response to the program requirements that are known at the time of issue and stated in the PRD.

4.2.3 Operations Directive

The OD is the SA’s response to the OR and details each support function, the support equipment, the technical configuration, and the personnel duties involved in supporting the test or operation.

The OD may provide management information or technical requirements and guidelines. It is a listing of expected coverage detailing the support posture of the SA for the test covered by the

4-2 particular OD. The OD is normally prepared in sufficient detail to furnish instructions for a specific test or test series.

5-1

CHAPTER 5

UDS PREPARATION INSTRUCTIONS

5.1 General

The preparation instructions in Section 5.2 provide detailed explanations for each data entry contained within each UDS format and should be followed by both the RA and SA when creating requirements and support documentation.

Not every format is used by both RAs and SAs. The list of formats in Appendix B contains an R to the left of formats that apply only to RAs and an S to the left of formats that apply only to SAs; however, some individual data fields may not apply to either the RA or to the SA. The guide in each instance should be to provide as much data as possible but not to “force-fill” a data entry.

Lastly, by convention, PI and SC documents are limited to the use of formats whose numbers end in “00”, for example, 1000, 2200, 5300.

5.2 UDS Format Instructions

5.2.1 Universally Common Entries

In the interest of streamlining this document, this section contains instructions for entries that are shared in common with a vast majority of the formats. Some formats that contain one or more of the following entries require more information than what is covered in this section. Those formats contain additional instructions.

ITEM NO.:

Enter a sequential number, beginning at “01”, that identifies each requirement, response, or informational item documented in reference to each format. The item number used for responses to requirements will be the same as that of the corresponding item number appearing in the PRD/ OR. The corresponding PRD/OR format number will also be listed for clarification. This may need modification in certain circumstances, especially when combining two ORs into one OD.

Also, if there are supplemental SA-generated information items, explain the items on UDS Format 1052 - Special Code Definition.

REQUESTER:

Identify the RA using the code, identified on UDS Format 1052 - Special Code Definition, assigned to the requester of a requirement. Sub-requesters, similarly identified, will be indicated by the use of a slash (/) immediately following the requester code (commas may be used to identify additional requesters, since so many organizations have a slash in their title, e.g.

MDA/DTCT). For example, T/DE22 might indicate a requirement established by the National Aeronautics and Space Administration (NASA) Johnson Space Center Flight Requirements Office. Each requester/sub-requester shall be separated by a space. It is recommended that, where possible, either the assigned agency alphabetical code or the agency acronym, shown in the UDS Handbook, Appendix A, be used as standard requester codes.

5-2

SUPPLIER:

Identify all suppliers by agency acronym, such as PMRF (Pacific Missile Range Facility), RTS (Reagan Test Site), MDA/DTR (Missile Defense Agency/Directorate, Test Resources), etc.

Separate suppliers using a comma, since it is common for suppliers to have slashes in their names.

TEST CODE:

This item is a code that is assigned to a specific test requirement or information item that will identify the various test activities. The test codes are identified on UDS Format 1051 - Test Code Definition. These test codes will be used as a method of correlating support requirements to the test activity involved such that any support requirement referenced to a test code indicates that this support will be required during the particular test program activity.

REQUIREMENT ( ) INFORMATION ( ) RESPONSE ( ):

Indicate whether each item number submitted is a requirement for support from the SA or is submitted for informational purposes only or requires a response in a supporting document.

REMARKS:

Enter any information that will further explain any entries made.

5.2.2 UDS Format Instructions

FORMAT 1000 - ADMINISTRATIVE

This format is used to enter any administrative information pertaining to the program or mission.

PROGRAM TITLE:

Enter the official title of the program here.

SHORT TITLE:

Enter the official short title here. The short title can be used in all following documents to refer to the program.

RESPONSIBLE AGENCIES & KEY PERSONNEL:

Enter a description of the responsible agencies and the personnel within those agencies who provide support to the program. These personnel should include:

RA/Project Representative Requesting SA/Project Representative Contractor/Representative Lead SA/Representative

SCOPE AND PURPOSE:

Describe in detail the program’s objective and what is involved in accomplishing that objective.

5-3

TREATY COMPLIANCE:

Indicate that a competent authority has reviewed the program for applicability under international treaties, such as Strategic Arms Reduction Treaty, Intermediate-Range Nuclear Forces Treaty, Open Skies Treaty, Anti-ballistic Missile Treaty, and Chemical Weapons Convention. Program support requirements resulting from compliance with a treaty should be identified in the appropriate technical section of this requirements document.

ENVIRONMENTAL REQUIREMENTS:

Potential environmental impacts and permitting requirements will be analyzed, evaluated, and documented using the National Environmental Policy Act (NEPA) process. Following the submittal of an appropriate agency environmental analysis document, the host environmental management planning function will determine the necessity for additional environmental evaluation, analysis, and documentation. These actions will result in either a categorical exclusion (CATEX), an Environmental Assessment (EA), or an Environmental Impact Statement

(EIS).

PROGRAM IDENTIFICATION INFORMATION:

Provide the following program information.

Beginning Date Department of Defense (DoD) Element Number First Test Date Type of Program Completion Date Defense Priority and Allocations System (DPAS)

Precedence Program/Project Number Priority Number Contract Number Program Status

FORMAT 1010 - APPROVAL AUTHORITY

This format is used as an authorization granted by RAs to the SAs for the conduct of operations relevant to the successful accomplishment of a program, mission, or test. The authorization indicates that the information contained in this document levies the official user requirements for support of a given program. It serves as an acceptance of the document by the SAs in recognition of the requirements contained therein. Follow preparation instructions given in Section 5.2.1 for the entry ITEM NO.

PRECEDENCE RATING:

Enter the applicable precedence rating that is assigned to the program.

PRIORITY:

Enter the priority of the program, mission, or test.

INITIATION DATE:

Indicate the date when support is first required. Dates for special facilities or unique instrumentation should be entered in REMARKS.

5-4

COMPLETION DATES:

Indicate the date when the program, mission, or test is planned to be completed or when it no longer requires support.

SPONSORING AGENCY:

Enter the military or government organization that has cognizance and prime responsibility for the program.

BASIC CONTRACT NO.:

Enter the basic contract number for the program, where applicable.

AUTHORITY (REFERENCES):

List the basic document that constitutes authority for conduct of the program.

REMARKS:

In addition to the instructions in Section 5.2.1, enter the reason for the assigned security classification and any special handling requirements. List other contractors and their respective contract numbers when necessary. Enter, if necessary, general information pertinent to the applicability and authorization of the document.

APPROVAL:

Use this table for approval by the RAs of the needs submitted. Enter the name, rank (if applicable), title, agency, phone number, and date. Leave space for signatures.

FORMAT 1020 - DISTRIBUTION LIST

This format is used as a distribution list for this document and for both new issues and revisions.

ORGANIZATION ADDRESS:

Enter the title of the organization, address (include the post office zip code plus 4 digits), addressee’s name and title, email address, and applicable office symbol for each organization that wants a copy. Make additional entries as necessary to ensure distribution to the appropriate recipients.

NUMBER OF COPIES:

Enter the number of copies the organization will receive.

FORMAT 1030 - REVISION CONTROL AND CLASSIFICATION

This format is used as a means of revision control in an unclassified or classified document. Classified entries will not be included in the basic unclassified document.

Appropriate referenced pages should be included in the basic unclassified document where the classified information would appear. The classified pages then appear in a classified addendum

5-5 to the basic document. Care should be exercised to ensure that the complete title and other data do not render the collective pages classified under operations security (OPSEC) guidelines.

All revisions, both classified and unclassified, will require Format 1010 to show approval of the revisions. Follow preparation instructions in Section 5.2.1 for the entry ITEM NO.

INFORMATION:

Enter a description of the update, including its purpose.

UDS SECTION:

List each UDS format used in the document by its four-digit number.

ITEM:

For automated documentation systems, indicate the item numbers within the sections.

PAGE:

For manual documentation systems, enter the page number for each section.

CLASS:

Enter the classification (TS - Top Secret, S - Secret, or C - Confidential) required by the security guides beside each applicable section and its page number in this column.

CHANGE ##:

List pages affected by changes only. Most documents are nearing 500 pages now and listing every page makes this section unusable.

DATE:

Enter the date the change was approved and becomes effective.

REMARKS:

In addition to the instructions in Section 5.2.1, this entry will have any amplifying information about change pages.

As with all UDS documentation, the revision control format/section should be tailored to user/support range requirements. In Format 1030 it is encouraged that some form of synopsis of change be provided.

FORMAT 1031 - INDEX

This format is used to present the index of sections used in the document (not used in PI/SC). This list should be used as a checklist to ensure all pertinent information or requirements are documented. Only those UDS formats that are applicable need be used. The list is preprinted for reference, but when an “X” is entered opposite the format used, this format serves as an outline of contents for the document.

5-6

Enter an “X” opposite those UDS format numbers used in the document.

FORMAT 1040 - SECURITY INFORMATION

This format is used to list the security classification of classified data/information pertaining to the program, mission, or test. This format is used by the project office and not by the contractors. It will serve as a security guide for the program for those that handle data, drawings, and equipment. A fill-in table (Appendix C) is provided for the inputs. Use only that portion of the table that applies to each program. A narrative-type input can be substituted for the table inputs where required. In addition to the table, fill out all entries A-FF for which data are available. If the table is not the appropriate choice for the program, fill out the narrative-style entries listed under the table in Appendix C, following preparation instructions in Section 5.2.1 for the entries REQUESTER and REMARKS and the preparation instructions below for the rest of the entries.

INFORMATION:

Enter a brief description of the items described in the DATA PRODUCTS AND HARDWARE SECURITY CLASSIFICATION table.

SECURITY GUIDES AND DOCUMENTS:

List the various security guides and documents used to establish the classification and to control the documentation of the information elements listed in the PROGRAM/MISSION ELEMENTS entry.

PROGRAM/MISSION ELEMENTS:

Identify program/mission information elements for which security classification is required.

SECURITY CLASSIFICATION:

Enter the security classification of the program/mission elements identified in the PROGRAM/MISSION ELEMENTS entry. Designators used will be in accordance with instructions in the PROGRAM/MISSION ELEMENTS entry.

The following security classification symbols will be used throughout the document:

TS TOP SECRET C CONFIDENTIAL

S SECRET U UNCLASSIFIED

Special Warning Designators

RD RESTRICTED DATA

CNWDI CRITICAL NUCLEAR WEAPON DESIGN INFORMATION

5-7

SAR SPECIAL ACCESS REQUIRED

CLASSIFICATION AUTHORITY:

Identify the authority that issued the classification for the item in question.

DECLASS DATE:

Identify the date, if available, the classification authority listed as the date on which the item is declassified.

SIGNATURE:

Have a representative of the classification authority sign this entry.

NAME:

List the name of the signatory.

TITLE:

List the title of the signatory.

AGENCY:

List the agency the signatory represents. This should be the same as the CLASSIFICATION AUTHORITY entry above.

DATE:

Enter the date on which the classification authority representative signed the format.

FORMAT 1041 - FACILITY CLEARANCE INFORMATION

This format is used by the RA to list those nongovernment agencies that are entitled to receive classified range material, the clearance possessed by that agency, the agency that granted the clearance, and the degree of safeguarding ability that the nongovernment agency has. Follow preparation instructions in Section 5.2.1 for the entry ITEM NO.

FACILITY:

Enter the full name of the nongovernment agency facility to which the classified material is to be forwarded.

ADDRESS:

Enter the address of the agency involved.

CAGE CODE:

Enter the cage code for the nongovernment facilities to which the classified material is to be sent.

FACILITY CLEARANCE:

Enter the facility clearance and cage number of the nongovernment agency concerned.

5-8

GRANTING AGENCY:

Enter the name of the government agency granting the facility clearance and the date the clearance was granted or last renewed.

SAFEGUARDING ABILITY:

Enter the degree of capability the agency has for storing and safeguarding classified material.

AUTHORIZED ACCESS TO:

Enter the level of the material the agency is authorized to access based on the Industrial Security Facilities Database (ISDF) (DoD Defense Security Service [DSS]) website.

FORMAT 1042 - OPERATIONS SECURITY (OPSEC) AND SECURITY

Follow instructions in Section 5.2.1 for the entry REQUESTER.

ITEM:

Describe the item or event for which the OPSEC and Security reviews are being performed.

INFORMATION:

Fill out the OPSEC and Security checklist and provide any additional information. The following text describes the sections of the checklist.

Part I. PROGRAM IDENTIFICATION

A. The intent of this paragraph is to address OPSEC/Security issues that must be considered when preparing to support test and training programs. Additional information on recommended OPSEC practices is provided in the RCC document Operations Security Guide (version concurrent with publication date of UDS 501-12: 600-11). Users of a member range of the Major Range and Test Facility Base (MRTFB) are required to provide an OPSEC/Security analysis with submittal of the Level I (PI) or Level II (PRD) documentation, as appropriate. See the Operations Security (OPSEC) and Security checklist in Appendix D to identify particular program needs and requirements. Completion of the checklist is required from all users (DoD, NASA, commercial, etc.) requiring range support whether classified or unclassified. The checklist is a “living” document and used throughout the test/training life cycle.