LAS BISON J) Jot.~~~: 'R l ~ d. ¢'-' . ' ., ' DISCLAIMER The citation of trade names and names of manufac turers in this summary is not to be construed as offic ial Government indorsement or approaval of commer c ial produc t s or servic es referen ced herein. FORErlARD The purpose of the National Ranger Users Handbook is to familiarize current and potential users of White Sands Missile Range with the structure, organizations, measurement, and data product capabilities of WSMR and to assist the users in stating their needs to HSHR for support of their test programs. Volume I is a managerial introduction to test policies, procedures, and test support resources of HSMR. A brief description is presented of the Nation a 1 Range's operational elements and their functional objectives. Volume II is oriented to the procedures, documentation, and documentation format which is normally used at wsr~R to obtain test operations support.Part two of this handbook explains the Universal Documentation System and its application at WS~1R. Part two of this handbook provides planning guides for major support areas and defines the services and test products available at \~SMR. Inqui ries and comments concerning this handbook and requests for additiona 1 copies should he addressed to: National Range Operations Directorate ATTN: STEWS-NR-P White Sands Missile Range, NM 88002 i i INTRODUCTION The White Sands Missile Range, Range Users Handbook is published in accordance with Department of Defense Directive 3200.11. Operational and fiscal policies and procedures are consistant with policies outlined in DODD 3200.11 as pertains to those installations that are designated as Major Test Facilities and are included in the DOD Major Range and Test Facility Base. iii TABLE OF CONTENTS VOLUME I Paragraph Page Foreword i Overview of U.S. Army Hhite Sands i·1issile Range ix PART ONE -MANAGEMENT CONCEPTS AND POLICIES Chapter 1 -Contacts at WSr~R 1-1 1-1 Chapter 2 -Functions and Organizations 2-1 2-1 Chapter 3 -National Range Policies and Procedures 3-1 3-1 Chapter 4 -National Range Test Areas 4-1 4-1 VOLUME I I PART n/0 -UNIVERSAL DOCUMENTATION SYSTEM (UDS) Chapter 5 -General Description of the UDS at WSr1R 5-1 System Criteria 5-1 5-1 levels of Planning 5-2 5-1 National Range Priority Assignment 5-3 5-2 Program and Document Identification 5-4 5-3 Structure 5-5 5-4 Document Processing Times 5-6 5-7 Cross-Referencing 5-7 5-8 Chapter 6 -Planning at level I (PI/SC) 6-1 Purpose of PI 6-1 6-1 Procedure 6-2 6-2 Revision 6-3 6-2 PI Preparation 6-4 6-2 Purpose and Coordination of SC 5-5 6-51 Contents of SC 6-6 6-51 Chapter 7 -Planning at level I (PRD/PSP) 7-1 Chapter 8 -Planning at level II (OR/OD) 8-1 OR Purpose 8-1 8-1 Test Variations in an OR 8-2 8-1 General OR Procedures 8-3 8-2 Security 8-4 8-2 Revisions and Cancellations 8-5 8-2 OR Preparation 8-6 8-3 00 Purpose 8-7 8-27 iv TABLE OF CONTENTS (Con} Temporary Change to the OD Deviations to the OD PART THREE -PLANNING GUIDES Chapter 9 -Data Products Data Product Nomenclature Standard Parameters Parameter Comparisons Minimizing Data Delivery Time Error Estimates of Data Precision Expedited Data Delivery Range Performance Chapter 10 -Telemetry Remarks on Support System Capabilities TM Data Products Late Requirement Modifications Special Noncommitted Processing Digital Tape Formats Requesting TM Support Chapter 11 -t·1eteorol ogy Organization and Capabilities Meteorological Products Requesting Meteorological Support Chapter 12 -1·1i ssi 1e Flight and Laser Beam Safety Safety Policies and Approvals Flight Termination Systems Requirements Laser Beam Termination Systems Requirements Data Requirements for Unmanned Air Vehicle Test Safety f~anagement Anaytical Study Requirements Chapter 13 -Ground Safety Chapter 14 -Laser Safety Categories of Operations Procedures Paragraph 8-8 8-9 9-1 9-2 9-3 9-4 9-5 9-6 9-7 10-1 10-2 10-3 10-4 10-5 10-6 10-7 11-1 11-2 11-3 12-1 12-2 12-3 12-4 12-5 14-1 14-2 Page 8-28 8-29 9-1 9-1 9-11 9-40 9-42 9-4 3 9-43 9-44 10-1 10-1 10-2 10-5 10-7 10-9 10-13 10-24 11-1 11-1 11-4 11-6 12-1 12-1 12-5 12-15 12-18 12-25 13-1 14-1 14-1 14-2 v Chapter 15 -Security Security Planning Classification Management Storage of Classified Material or Hardware Signal Security Physical Security Visitor Control and Identification Military Security -Photography Road Block Support Recovery of Classified I t ems Documentation Marking Operations Security Ranger Sponsor/Range Users Responsibilities Chapter 16 -Recovery Capabilities Recovery Requirements and Classes Chapter 17 -Communications Radio Guidance and Control Ground/Air Communications Ground Communications !RIG Timing ~requency Control and Analysis Chapter 18 -Photography General Requesting Support Pictorial Products Chapter 19 -Health and Safety Radiological Flight Overpressures Reporting Requirements for Use of Radioactive Material in Space Nuclear Safety Laser Safety Certification of Hazards Chapter 20 -Environmental Considerations Paragraph 15-1 15-2 15-3 15-4 15-5 15-6 15-7 15-8 15-9 15-10 15-11 15-12 16-1 16-2 17-1 17-2 17-3 17-4 17-5 18-1 18-2 18-3 19-1 19-2 19-3 19-4 19-6 19-5 Page 15-1 15-2 15-6 15-7 15-7 15-9 15-9 15-10 15-11 15-11 15-11 15-13 15-15 16-1 16-1 16-1 17-1 17-1 17-4 17-4 17-7 17-8 18-1 18-1 18-2 18-3 19-1 19-1 19-1 19-2 19-3 19-4 19-4 20-1 vi ' J PART TWO CHAPTER 5 Chapter 5 introduces the user to the UDS. No attempt is made here to cover every detail of the system. Rather, primary concepts necessary to understand organization and the how and why of the system are discussed. 5-l. SYSTEM CRITERIA. A great variety of programs are brought to WSMR and the other national ranges. These programs vary in magnitude from small, onetime tests of compents, to continuing programs involving the development of complete weapons systems, to global programs requiring the support of all the national ranges. This wide range of program scope and complexity requ·ires a documentation system which is flexible and responsive. The system designed by the national ranges to meet these requirements is the Universal Documentation System (UDS). 5-2. LEVELS OF PLANNING. Three levels of documentation and six documents make up the UDS. The first and thi~d level are required for all programs, and meet the WSMR documentation requirements for most programs. Very complex programs may also require the second level. LEVEL USER DOCUMENTS RANGE DOCUMENTS I -Program Planning Program Introduction (PI) Statement of Capabi 1i ty (SC) II -Detailed Program Program Requirements Program Support Planning Documents Plan (PSP) III -Test Planning & Operations Require-Operations Scheduling ments (OR) Directives (OD) LEVEL I-is broad program planning documentation and program approval, and is always required. It establishes the WSMR priority, scope, and duration of activity; provides a mechanism for advance coordination (preliminary to program approval) and management approval; initiates technical and resource planning and identifies related milestones; and defines responsibilities between the user and the ran~e. For many programs, specially minor within the capability of the range) and short-lead time programs, the PI and SC may be designed to eliminate the need for Level II documentation. This is accomplished through providing sufficient detail in Level I to obtain a condition of readiness to support the conduct of tests. I LEVEL II -provides detailed program planning documentation and supplementsLeve1 I when more detailed requi rements/i nforma ti on is needed for supportpreparation, especially acquisition of new capabilities or facilities. (Typically, Level II documents are required when Level I documents are of the advanced planning-type envisioned when the UDS was first established. Experience has shown that most of the programs at WSMR are pushed by time constraints to combine the planning objectives of Level I and II into one submission.) The necessity for Level II documentation is determined by analysis of the PI and stated in the SC. LEVEL III -is individual test planning used to schedule specific tests. Itis test oriented and specifies, in detail, the requirements and supportassociated with one or a series of like tests within the scope of the program, as defined by Level I and II documents. The OR states a specific test to beperformed; the OD commits specific range support to the test. When an OD isapproved by range management, the use may schedule it as often as needed to support its tests. 5-3. NATIONAL RANGE PRIORITY ASSIGNMENT CRITERIA. User programs are assigned a Range priority in accordance with the WSMR mission and the nature of the program (See Sec 3-4). The four priorities used as National Priority (NP),1, 2 or 3. A single priority is normally assigned to a program. However,when the program has a wide variety of test activities and purposes, the range may occasionally design a dual priority -one priority applying to some tests and the other priority to the other tests. The qualifications for assignment of priority are listed below. NATIONAL PRIORITY (NP). To qualify for the assignment of an NP, the program must be identified by name as BRICKBAT in the Master Urgency List (MUL). For related programs not listed in MUL, the user must obtain DOD approval toacquire an NP assignment and furnish a copy of the approval to WSMR. PRIORITY 1 (Guided missile R&D firings or high energy laser R&D tests). Toqualify for assignment of Priority 1, the following four characteristics must be met by the program: a. Must require a missile or high energy laser device b. Must require the missile to be guided c. Must be R&D d. Must involve a firing or laser operation PRIORITY 2 (Other types of guided missile firingstests). To qualify for assignment of Prioritycharacteristics must be met by the program: or high 2, the energy laser R&D following three a. Must require a missile or high energy laser device b. ~1ust require the missile to be guided ' c. Must involve a firing or laser operation PRIORITY 3 (other users). This priority is assigned to all programs not qualifying for NP, 1 or 2. Deviation from these requirements may occur as stated in section 3-4. Priorities are used to arbitrate conflicts between programs for utilization of the range and conflicts for data processing support. Range priorities are in no way connected with data priorities, which are user assigned, discussed in chapter 10, nor are they in any way connected with service or agency priorities unless the program qualifies for NP. 5-4. PROGRAM AND DOCUMENT NUMBERS. A number is assigned to each user program upon receipt of the Program Introduction document. Programs are assigned three-digit numbers within blocks as follows: a. 000 to 349 Army Programs (except ASL) b. 350 to 674 Air Force Programs c. 675 to 699 High Energy Programs d. 700 to 799 ASL Programs e. 800 to 899 Navy Programs f. 900 to 949 NASA Programs g. 950 to 999 Other Programs The basic program number is used in identifying all documentation pertaining to a program during its life on the range and this number will not be assigned by the range to another program until at least 6 months after the previous program to have that number completed. All program and document numbers are assigned by the NR-PR. The documents prepared for a user program are given numbers comprised of the basic three-digit program number followed by other alphabetical or numerical characters. Three (or sometimes four) characters are added for OD numbers; two characters are added for all other document numbers. The fourth character of PI, SC, PRO, and PSP numbers is alphabetical and indentifies the document type; i.e., "A" identified a PI, "B" identifies and SC, "C" identifies a PRO, and "D" identifies a PSP. The fifth character of the number for these documents is numerical and identifies the issue number as follows: (1) For the PI and SC, the number zero (0) is used to identify the original document. Numbers one (1) through nine (9) are then used to identify any subsequent issues of these documents which may be necessary. Major changes in program scope or support requirements may require that a complete new PI and related SC be prepared. In these cases, the rewritten document is assigned a new issue number as described · here. Minor changes and corrections of the PI and SC made through normal revision procedures do not affect the .. 5-3 document identification number (i.e., the same number is used with an R-1,R-2, etc., following the document number to indicate the current revision). (2) For the PRO and PSP, the number one (1) identifies the first such document prepared within the scope of the PI/SC. Numbers two (2) through ten (10) are used to identify and additional PROs and related PSPs which may be necessary. As previously pointed out, in most instances a single PRO will suffice for complete program coverage; however, a large and complex programinvolving serveral test locations or other significantly difference aspects may find more than one PRO desirable . In these cases, the additional documents are numbered as described above. The fourth and fifth characters of OR numbers are both numerical and identifythe sequence of the ORs for a program; i.e., the number zero (0) and one (01)identify the first OR, zero (0) and two (02) the second, etc., in sequence upto ninety-nine (99). The fourth and fifth characters of the number for each 00 prepared in response to an OR are the same as the fourth and fifth characters of that OR number. The sixth or sixth and seventh, character(s) of an 00 number is (are) alphabetical and identifies the test support plan contained in that 00. 5-5. STRUCTURE. The common page/paragraph numbering system which applies to all documents of the UDS is shown below . Page or paragraph numbers, as applicable to the type of document, will be assigned within the blocks listed under Page/Paragraph Series. In addition to serving as a framework for designof the documentation system, the numbering system permits central control of forms standard to all ranges and those unique to a range . 5-4 UDS -DOCUMENT STRUCTURE CATEGORY 1 Page/Paragraph Series 1000-1099 1100-1299 1300-1399 1400-1499 1500-1599 1600-1699 1700-1799 1800-1899 1900-1999 CATEGORY 2 & 3 Page/Paragraph Series 2000-2099 2100-2199 2200-2299 2300-2399 2400-2499 2500-2599 2600-2699 2700-2799 2800-2899 2900-2999 3000-3099 3100-3199 3200-3299 3300-3399 3400-3499 3500-3599 3600-3699 3700-3799 CATEGORY 4 SUBJECT MATTER Program Information, Administrative and Technical Admi nis t rative Inf ormation Progr am and Mission Inf orma t ion System Information System Instrumentation Requesting Agencies Support Instrumentation/Equipment System Readiness Procedures/Tests Test Envelope Information Operational Hazards Unassigned Test/Mission Operational Requirements Test Operational Concepts/Summaries Metric Measurements and Data Requirements Telemetry Measurement and Data Requirements Command Control/Destruct Requirements Air-Ground Voice Communications Requirements Composite Systems Requirements Other Systems Requirements Ground Communications Requirements Other Communications Requirements Unassigned Real-Time Data Display and Control Requirements Photographic RequirementsMeteorological Requirements Recovery Requirements Other Technical Support Requirements Medica l Requirements (Manned Space Flight only) Public Affairs (Manned Space Flight only) Unassigned Coordina t e System/Data Processing and Disposition Requirements 5-5 ' CATEGORY Page/Paragraph Series 4000-4099 4100-4199 4200-4299 4300-4999 CATEGORY 5 Page/Paragraph Series 5000-5099 5100-5199 5200-5299 5300-5399 5400-5499 5500-5599 5600-5699 5700-5999 CATEGORY 6 Page/Paragraph Series 6000-6099 6100-6999 SUBJECT MATTER Coordinate System Descriptions Data Processing Flight Evaluation Requirements Data Delivery and Disposition Requirements Unassigned Base Facilities/Logistic Requirements Requirement Summaries Personnel Assignment Schedules Transportation Requirements Supply/Storage/Service Requirements Laboratory Requirements Maintenanc~ Support Requirements Facilities RequirementsUnasssi gned Other Support Requirements Other Support Requirements Unassigned 5-6 ' 5-6. DOCUMENT PROCESSING TIMES. The time required for range processing of UDS documents may be estimated by use of the data given below. adjusted for the relative complexity and difficulty of support planning associated with a particular document. (Processing time includes planning. coordinating. approval and printing of the document.) Average Number of Documents Workdays (WD)** Program Introduction/Statement of Capability (PI/SC) 65 WD Program Requirements/Program Support Plan (PRD/PSP) 126 WD Operations Requirements/Operations Directives (OR/00) 33 WD PI's which have test requirements which can be supported completely within current capabilities and present no flight safety problems ~1ill normally fall on l ow side of the AVERAGE response time. Any of the following may cause the response time for the PI to be above average: a. Difficult flight safety problem b. Support requirements outside current capability c. Conflict with other programs for items necessary to support or for location of user test areas d. Technical problems of interface between user equipment and range equipment e. Any controversial items on funding or other responsibilities If after 45 WD the range has not completed the sc. users may request and obtain an interim SC. Interim SC's will contain support statements and restraints only for those UDS paragraphs where support planning is complete. Interim SCs will be issued for planning purposes only. as they will be not be coordinated with other sponsor agencies nor approved by TECOM. They will. however, be transmitted through WSMR Command. **These averages are estimated based upon performance over the last two years. The data for PI/SC excludes the time required for TECOM approval. The ave r ages for all documents exclude time in excess of 3 days to receive additional information from users, if required. 5-7 For processing ORs, users should plan on the first few taking longer than the later ones. The first one, especially, almost always requires above-average processing time. This is due to range planners at all levels having less familiarity with the program and having to plan complete range configurations for the new program. Later ORs which require new range configurations require similarly long lead-time, but later ORs which are minor variations on previous tests can usually be staffed in less-than-average time. Users who have definite test schedules to meet should provide their requirements to WSMR within ample lead-time for range support planning. In doing this, it must be realized that the distribution about a mean of 33 WD for OR processing covers the range of 29 to 45 WD due to normal variations of . workload and complexity of requirements. Occasionally, due to maximum expediting or severe difficulties in support planning, processing times outside the normal range occur. 5-7. ~':ROSS-REFERENCING. Expression of support requirements by reference to another document as well as documents outside of the UDS. Reference may be made to documents outside of the UDS when technical or other information, therein, would be helpful to the range as background. It is recommended, and strongly encouraged, that users include material essential to range understanding of a program or requirements as an enclosure or annex to the UDS document rather than making a reference. This method of operation will ensure that all applicable information is available and used when support is being planned. -tr U.S. GOVERNMENT PRINTING OFFICE: 1985-578-733 5-8