***BY ORDER OF THE COMMANDER***

![](media/image1.emf){width="1.2118055555555556in"
height="1.304861111111111in"}

***45TH SPACE WING INSTRUCTION 99-101***

***31 DECEMBER 1997***

***Test and Evaluation***

***45TH SPACE WING MISSION PROGRAM DOCUMENTS***

**COMPLIANCE WITH THIS PUBLICATION IS MANDATORY**

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**NOTICE:** This publication is available digitally on the 45 SW LAN and
NUAFSPC CD-ROM. If you lack access, contact your Publishing Distribution
Office (PDO).

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

OPR: 45 RANS/DOU (Ms Martha A. Dodgen) Certified by: 45 OG/CC (Col
Philip G. Benjamin)

Supersedes 45 SWI 99-101, 7 October 1994 Pages: 20

Distribution: F;X

HQ AFSPC/DO (1), SCRI (2), Peterson AFB CO 80914-4100\...3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

This instruction implements AFPD 99-1, *Test and Evaluation Process*. It
states the policies, procedures, and instructions for preparing,
submitting, and processing documents in the Universal Documentation
System (UDS). The instruction applies to 45th Space Wing, range
contractors (as a compliance document) and to range customers through
current Memoranda of Understanding or Interservice Support Agreements
between the customer and 45 SW. Users of this instruction should
familiarize themselves with the contents to ensure they meet the
established suspense requirements for submitting and processing
documents. Specifics for each of the documents are included in the
individual chapters.

***SUMMARY OF REVISIONS***

The revision of this publication is to meet the format standards
required by Air Force. No content material has changed. Some required
format changes have been made to allow for the conversion process.

**Page**

**Chapter 1 GENERAL 3**

1.1. Purpose 3

1.2. Key Terms 3

1.3. Abbreviations and Acronyms 3

1.4. Responsibilities 3

**Chapter 2 SECURITY 6**

2.1. Purpose 6

2.2. Classification Markings 6

2.3. Operations Security (OPSEC) 6

**Chapter 3 DOCUMENTATION [SYSTEM 7]{.smallcaps}**

3.1. Purpose. 7

Table 3.1. Document Organization 7

3.2. Document Organization 7

3.3. Flexibility 7

**Chapter 4 Program Introduction and Statement of Capability 8**

4.1. Program Introduction (PI) 8

4.2. Statement of Capability (SC) 8

**Chapter 5 PROGRAM REQUIREMENTS DOCUMENT AND PROGRAM SUPPORT PLAN 9**

5.1. Program Requirements Document (PRD) 9

5.2. Program Support Plan (PSP) 9

**Chapter 6 OPERATIONS REQUIREMENTS DOCUMENT AND OPERATIONS DIRECTIVE
11**

6.1. Operations Requirements (OR) 11

6.2. Operations Directive (OD) 11

**Chapter 7 DOCUMENTATION PROCESS 12**

7.1. Purpose 12

Table 7.1. Lead Times Prior to Mission Execution (PI/ PRD) 13

7.2. Procedures 11

Table 7.2 Documentation Lead Times 13

Table 7.2.1. Documentation Production Times 14

7.3. Categories of Objectives and Requirements Classes 12

Table 7.3. Lead Times for Theoretical Trajectory Tapes for Ballistic
Missile Flights and

Space Missions 17

7.4. Lead Times. 12

7.5. Assignment and Numbering of 45 SW Programs 14

7.6. Document Covers 15

7.7. Distribution of Documents 15

7.8. Document Cancellation 15

7.9. Annexes 15

7.10. Revisions 15

7.11. Miscellaneous Documents 16

7.12. Guidelines for Preparing Formats 18

***Forms Adopted***

DD Form 1494, Application for Equipment Frequency Allocation 7.11.3.1.

45 SW Form 2010, Launch Forecast 7.11.3.9.

45 SW Form 2050, Launch Operation Schedule Request 7.11.3.9.

45 SW Form 2091, Operation Schedule/Forecast Request 7.11.3.9.

45 SW Form 2135, Photographic Outline 7.11.3.7.

**Attachment 1\-- GLOSSARY OF ABBREVIATIONS, ACRONYMS AND TERMS 19**

**Chapter 1**

**GENERAL**

**1.1. Purpose.** The documentation system and procedures described in
this instruction are prescribed for use at the 45 SW and are comparable
in format and text to documentation in use at all major ranges and test
facilities. The Universal Documentation System (UDS) provides a common
language and format for stating requirements and preparing support
responses. The UDS is based on a common structure to enable customers to
employ one basic format when presenting requirements to support
agencies. However, 45 SW requires certain modifications or adaptations
to the UDS and these are described within this instruction.

**1.2. Key Terms.** See attachment 1.

**1.3. Abbreviations and Acronyms.** See attachment 1.

**1.4. Responsibilities:**

1.4.1. The 45th Space Wing mission is to provide launch and tracking
facilities, safe procedures, and test data to a wide variety of
customers. The customers include the Air Force, Army, Navy, Ballistic
Missile Defense Organization (BMDO), National Aeronautics and Space
Administration (NASA), United Kingdom (UK), the European Space Agency
(ESA), and various private and commercial organizations.

1.4.2. The Plans office (45 SW/XP) serves as the office of primary
responsibility (OPR) and single point of contact on all new work until
such time as that new work is accepted as a directed range effort and
the statement of capability is signed and distributed. 45 SW/XP\'s other
responsibilities include:

1.4.2.1. Initial point of contact for prospective range customers.

1.4.2.2. Accepts new workloads or significant changes to existing
workloads, staffs the requirements, and prepares the range\'s statement
of capability or letter of acceptance to be returned to the customer.
Prepares, negotiates, authenticates, and administers all agreements
between the range and customer.

1.4.2.3. Provides the customer with all necessary information to use the
range to include available resources, documentation, initial cost
estimates, and a step-by-step process of working with the wing.

1.4.2.4. Analyzes future customer requirements and coordinates and
formulates plans for support by 45 SW resources. Maintains familiarity
with potential customers\' programs, aids potential customers in
obtaining information on Eastern Range capabilities to facilitate
potential customers\' program planning and the wing\'s long-range
planning and actively markets Eastern Range capabilities.

1.4.2.5. Acts as the wing focal point for commercial customers,
executing mini-agreements, annexes to commercialization on the Eastern
Range. Also, acts as the focal point for evaluating customer
satisfaction through personal contact, written surveys and other means
as appropriate.

1.4.3. The Safety office (45 SW/SE) establishes, directs, and manages
the overall safety program in flying, nuclear, explosive, missile,
ground, industrial and system safety. Prepares range safety input to
Statement of Capability (SCs), Program Support Plans (PSPs) and
Operations Directives (ODs) within the time lines provided in this
instruction in response to customer test requirements. Computes destruct
criteria and prepares appropriate displays for the safe conduct of
missile and space vehicle launches. Provides flight control officers for
all major launch operations on the range with the responsibility and
authority to terminate missile flights in accordance with established
policies and procedures. Provides estimates and estimate revisions for
all safety support as required by this instruction.

1.4.4. The 45th Logistics Group (45 LG) manages the operation and
maintenance of all Eastern Range instrumentation to include sensors,
command, control, communications, metric optics, radar, telemetry,
timing, and countdown, data collection systems, and range critical
computer systems in support of spacelift and ballistic missile test
operations. They manage and direct wing contracting, logistics support,
quality assurance, and transportation functions.

1.4.4.1. The 45th Maintenance Squadron (45 MXS) manages the daily
operation and maintenance of Eastern Range instrumentation to include
sensors, command, control, communications, and computer (C4) systems at
six Atlantic sites and a ship. These systems support all spacelift
operations and ballistic missile tests from Cape Canaveral AS, Kennedy
Space Center, and supports many operations and tests conducted by other
ranges. 45 MXS chairs the Deficiency Validation Board (DVB) which
approve validated requirements to modify the Eastern Range System (ERS).
45 MXS is the interface for the 45 SW and the SMC/CW-OLAK. 45 MXS is
responsible for the overall operation and maintenance of the range
instrumentation and systems performance analysis and for ensuring that
the time lines within this instruction are not impacted. 45 MXS is
responsible for operational test and evaluation (OT&E) as well as
operation and maintenance (O&M) of all 45 SW instrumentation providing
support to range customers including communications, metric optics,
radar, telemetry, command, timing and countdown, and data collection
systems. 45 MXS is also responsible for O&M of all range real-time and
post-mission data process systems and for providing estimates and
estimate revisions for all 45 MXS support as required by this
instruction.

1.4.4.2. The 45th Logistics Support Squadron (45 LSS) controls and
directs logistics support functions and resources to meet spacelift
requirements, to include providing quality assurance over wing, DoD, and
NASA programs for space launch systems and payloads, including shuttle
and range support; directing and controlling the execution of mobility
readiness plans during contingency operations, mobility operations and
peacetime exercises; managing the War Reserve Material (WRM) Program;
supply accountable officer for fuels and munitions; and functionally
controlling the Standard Base Supply System (SBSS) contract.

1.4.4.3. The mission of the 45th Transportation Squadron (45 TRNS) is to
manage transportation and traffic services for efficient movement of
personnel and material to include DoD space launches; and coordinate
airlift and sealift to the downrange stations and other world-wide
destinations. They operate an air terminal in support of the Air
Mobility Command (AMC) peacetime exercises or contingency operations;
provide planning and organization for air transportation activities; and
process passengers and cargo for movement by military air. 45 TRNS
provides traffic management services for personnel, personal property,
and commercial surface freight movement to include freight operations at
Port Canaveral; and manage and operate preservation and packaging
activities. They are the functional area chief for the
contractor-operated vehicle operations and maintenance.

1.4.4.4. The 45th Contracting Squadron (45 CONS) provides contracting
services to meet all 45 SW and tenant requirements. They award and
administer contracts for supplies, services, construction, research, and
development. They also provide contract administration for contracts
awarded by other DoD and NASA offices for space launch systems and
payload programs.

1.4.5. The 45th Support Group (45 SPTG) is responsible for the Range
Visual Information Technical Services (RVITS) and the Launch Base
Services (LBS) contract which supports the photographic and optical
systems and facilities, security and civil engineering supporting launch
operations. They ensure that estimates and estimate revisions are
provided for all RVITS and LBS support as required by this instruction.

1.4.5.1. The 45th Security Forces Squadron (45 SFS) establishes,
directs, and manages the overall security program for Space Launch
Systems. Prepares range security input to SCs, PSPs, and ODs within time
lines provided in this instruction in response to customer requirements.
Identifies security requirements and provides necessary controls in
support of secure launch operations. Provides estimates and estimate
revisions for all security support as required by this instruction.

1.4.5.2. The 45th Civil Engineering Squadron (45 CES) provides, operates
and maintains facilities, utilities, housing, environmental, fire
protection, base operability, and explosive ordnance disposal (EOD)
support for the 45 SW and other assigned units in support of DoD and
commercial space launch or other assigned programs. They also provide
estimates and estimate revisions for all civil engineering support as
required by this instruction.

1.4.6. The 45th Operations Group (45 OG) is responsible to the 45 SW
Commander for the direction of real-time range operations, support
planning, and scheduling.

1.4.6.1. The 45th Range Squadron (45 RANS) is responsible for
operational control and allocation of resources in support of range
operations. 45 RANS is the primary point of contact between range
customers and the ER, and is the 45 SW staffing agency after SC turnover
to support the assigned programs with planning, documentation, support,
resources, funding, operations control, and data accuracy. They also
plan and direct instrumentation platform deployments. 45 RANS is also
responsible for the application of the UDS and adherence to the system
by both the customer and range organizations within the confines of the
UDS Handbooks and this instruction. They also provide estimates and
revisions for all range support as required by this instruction.

1.4.6.1.1. Range Scheduling (45 RANS/DS) is responsible for the
management of long and short-range scheduling, support planning and
resource utilization, and is the primary point of contact for range
customers to schedule activities in their 24-hour scheduling center.

1.4.6.2. The 45th Weather Squadron (45 WS) is responsible for natural
aerospace environmental support and service as needed, including
monitoring plans and programs to determine meteorological requirements
and recommending actions as necessary to satisfy these requirements. 45
WS provides pre-mission staff support and launch weather forecasts for
all Eastern Range operations. Provides CCTV weather briefings for all
operations. Acts as OPR for natural aerospace environmental support.
Provides estimates and estimate revisions for all weather support as
required by this instruction.

1.4.6.3. The 45th Operations Support Squadron (45 OSS) provides
comprehensive spacelift operations support to fulfill national
requirements. Support functions include assisting in flight hardware
processing and launch operations, overseeing the establishment of wing
operations training programs and policy, and managing all airfield and
air traffic services for three geographically separated airfields. They
also provide estimates and estimate revisions for all spacelift
operations support as provided by the 45 OSS.

1.4.6.4. The 1st Space Launch Squadron (1 SLS) is the launch agency for
Delta II launch operations conducted at the Eastern Range in support of
DoD and non-DoD programs. The 1 SLS provides overall mission assurance
to the Mission Director through management of launch vehicle processing
from receipt at Cape Canaveral AS through launch. It operates and
maintains assigned launch facilities, booster processing facilities, and
other associated or mission specific facilities. They provide estimate
and estimate revisions for all Delta launch support requirements as
required by the 1 SLS.

1.4.6.5. The 3d Space Launch Squadron (3 SLS) is the launch agency for
Atlas II launch operations conducted from space launch complex 36A at
Cape Canaveral AS, in support of vital payloads supporting national
requirements. The 3 SLS mission is to mitigate risks to booster
processing, integrated operations, pre-launch, launch and post-launch
activities by providing Government insight and oversight of Martin
Merietta launch processing activities in support of DoD missions and in
accordance with the Expendable Launch Vehicle Commercializa­tion
Agreement for commercial launches. The 3 SLS is responsible for safety,
security and resource protection throughout launch vehicle processing.
They operate and maintain assigned launch facilities, booster processing
facilities, and other associated or mission-specific facilities. They
also provide cost estimates and cost estimate revisions for any Atlas
launch support as required by the 3 SLS.

1.4.6.6. The 5th Space Launch Squadron (5 SLS) provides heavy spacelift
capability for deploying DoD and commercial spacecraft from space launch
complex 40 at Cape Canaveral AS, in support of warfighting CINCs,
National Command Authority, and commercial space launch programs. They
provide command management and engineering expertise for launching Titan
IV, Centaur, and Inertial Upper Stage boosters.

1.4.6.7. All other 45 SW organizations will coordinate their support
planning for the customer with 45 RANS.

**Chapter 2**

**SECURITY**

**2.1. Purpose.** These security instructions are provided for personnel
who prepare and control 45 SW Operations Documents in accordance with
DoD 5200.1/AFI 31-401, *Managing the Information Security Program*, and
the UDS Handbook, Volume 1. The originating agency of the 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.

**2.2. Classification Markings:**

2.2.1. Each classified document will show on its face the overall
classification, source of classification, date or event for
declassification, office of origin, and date of origination. The overall
classification of a document will be conspicuously marked permanently at
the top and bottom on the outside of the front cover, the first page of
the interior pages and on the outside of the back cover. All other
pages, except those that are blank, will be marked at the top and bottom
according to content to include \"unclassified\" when no classified
information is contained on such a page. These instructions are in
accordance with DoD 5200.1-R/AFI 31-401.

2.2.2. 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 or annex. Classified extracts will have limited distribution and
should be cross-referenced in the basic unclassified document.

**2-3. Operations Security (OPSEC).** When applicable, authors of
documents will consider AFI 10-1101, *Operations Security (OPSEC)
Instructions*, and, if required, will include an OPSEC annex or
incorporate specific OPSEC procedures within the document.

**Chapter 3**

**DOCUMENTATION SYSTEM**

**3.1. Purpose**. The official documentation system in effect at 45 SW
is the Universal Documentation System (UDS) approved and adopted by the
Range Commanders\' Council (RCC) at their 31st meeting, November 1967.
Details of the system are shown in the RCC UDS Handbook, Volumes 1, 2,
and 3. The UDS is based on a common numbering system which serves as the
framework for all documents within the UDS.

**3.2. Document Organization.** The UDS provides for three levels of
customer and support agency documentation (see Table 3.1). They are as
follows:

3.2.1. The level 1 documents are used to initiate program support
planning between customers and support agencies.

3.2.2. The level 2 documents are for additional or more detailed program
information, especially for the more complex programs.

3.2.3. The level 3 documents are used to plan separate operations within
a program.

**3.3. Flexibility.** The UDS can be used in situations involving a
single customer and a single support agency or for operations involving
multiple customers with multiple support agencies. For multiple
customers and multiple support agencies, the recommended approach is to
use a lead range agency to coordinate all the customer and support
agency documents. Depending on the size and complexity of the program,
one or two levels may be combined. For example, the PRD/OR or PSP/OD may
be combined if this is a more expedient approach. Only those applicable
pages and sections of the UDS formats from the UDS Handbooks need to be
used in these documents.

**Table 3.1. Document Organization.**

+-----------------------+-----------------------+-----------------------+
| **LEVEL**             | **CUSTOMER            | **SUPPORT AGENCY      |
|                       | REQUIREMENTS**        | RESPONSE**            |
|                       |                       |                       |
|                       | **DOCUMENTS**         | **DOCUMENTS**         |
+-----------------------+-----------------------+-----------------------+
| 1                     | Program Introduction  | Statement of          |
|                       | (PI)                  | Capability (SC)       |
+-----------------------+-----------------------+-----------------------+
| 2                     | Program Requirements  | Program Support Plan  |
|                       |                       | (PSP)                 |
|                       | Document (PRD)        |                       |
+-----------------------+-----------------------+-----------------------+
| 3                     | Operations            | Operations Directive  |
|                       | Requirements (OR)     | (OD)                  |
+-----------------------+-----------------------+-----------------------+

**Chapter 4**

**PROGRAM INTRODUCTION AND STATEMENT OF CAPABILITY**

**4.1. Program Introduction (PI).** The Program Introduction introduces
new programs to the 45 SW. Customers submit the Program Introduction
according to lead times shown in Table 7-1. Customers prepare the PI
using procedures in the RCC UDS Handbook, Volume 2. This document is
prepared by the customer to inform the range of the customer\'s support
requirements including test and evaluation of specific systems,
sub-systems, and equipment. On the first page of the PI, the customers
are required to evaluate the environmental impact of their programs and
to indicate whether or not they have complied with the National
Environmental Policy Act. However, when there is a new DoD/NASA payload
or a minor support requirement change, a PRD may be appropriate and a PI
may not be required. All commercial space launch customers that wish to
use 45 SW resources, will process a PI through 45 SW/XP. They will
obtain sponsorship with the Department of Transportation prior to
seeking support and sign a mini-agreement with the 45 SW. PIs for
payloads on commercial vehicles will be submitted to the appropriate
commercial contractor. Any payload that requires a significant or unique
reevaluation of range resources will be processed by 45 SW/XP. All new
T&E, booster or payload programs that are not commercial, will require a
PI (according to 45 SWI 25-202, *Acceptance of New Workloads*) be
submitted to 45 SW/XP (shuttle payloads are exempt).

**4.2. Statement of Capability (SC).** The statement of capability is
prepared by 45 SW/XP from inputs provided by applicable range staff
elements and outside support agencies (if any) for signature of the 45
SW Commander. The SC is the range\'s response to the PI and provides the
customer with a preliminary cost estimate, acceptance of the program,
and any prerequisites for support. It also informs the customer if
second or third-level documentation must be prepared. To complete a
statement of capability, 125 days are required. Requirements that cannot
be satisfied with resources available will be identified and
recommendations made on resolving the deficiency. If other documentation
is required from the requesting agency, the following disclaimer will be
added to the Additional Documentation Required portion of the SC\'s
Section 1000 Administrative:

> \"This document does not represent final commitment of 45 SW resources
> to support specific program requirements. Final commitments must await
> evaluation of specific requirements as defined in the Program
> Requirements Document and the Operations Requirements Document.\"

In some cases, a program will be accepted for planning purposes only,
with detailed support requirements and cost estimates provided in the
second and third levels of the UDS, with the concurrence of the office
of primary responsibility (OPR) for the second and third levels of the
UDS. If not otherwise specified, the SC will also serve to support
funding policy directives, and assign existing facilities such as launch
complexes, office space and processing facilities. If the user requires
new construction, the SC will provide preliminary site approval. The PI
and the SC complement each other in establishing the scope of the
program support activity to include the most comprehensive cost estimate
possible with applicable assumptions in deriving the estimate. Along
with the preliminary estimate, a full explanation and agreement on how
the program will be funded will also be included. If resources or other
support is not identified or committed, the SC may be sent out with the
concurrence of all 45 SW groups. 45 SW/XP and the OPR for second and
third levels of the UDS will mutually agree upon and resolve any
remaining open issues.

**Chapter 5**

**PROGRAM REQUIREMENTS DOCUMENT AND PROGRAM SUPPORT PLAN**

**5.1. Program Requirements Document (PRD).** The PRD is the customer\'s
request to the range describing in detail the customer\'s requirements
for support of the program. It will list test parameters, reports, data
reduction, test analyses, and evaluation requirements. The document is
to be submitted according to lead times shown in Table 7-1 and is
prepared using the applicable UDS formats as outlined in RCC UDS
Handbook, Volume 2. 45 RANS will forward the PRD for PSP processing
following 45 SW/FM confirmation of program funding. Information, even
though not complete, should be submitted as early as possible,
especially when support of certain items require long lead times. As new
or revised requirements develop, the original pages are revised, or
others added, and submitted as a revision to the PRD.

5.1.1. A PRD is not mandatory for programs that do not require range
development or for programs of short duration. However, submission of a
PRD will help to ensure that existing equipment will be available during
the time period required by the customer. A PRD is highly desirable when
off-range support is required. The range will initiate a critical
analysis of stated requirements for timely identification of those
support requirements which cannot be met. 45 RANS forwards the PRD to
the RTS contractor who acknowledges receipt in writing within seven
calendar days. This reply includes a detailed schedule of actions which
will culminate in publishing a consolidated PSP to include appropriate
cost estimates. PSP preparation time lines are given in Table 7.2.1.

5.1.2. PRD drafts are prepared and conferences which are coordinated
through the 45 RANS will be held for new programs when considered
advantageous to the range customer. The draft document provides the
opportunity for early coordination and clarification of requirements and
an assessment of support questions that may arise. The PRD Extract
(PRDE) becomes necessary when requirements are placed on an agency
which, in turn, creates additional (derivative) requirements that must
be levied on other agencies. These requirements occur when it is not
appropriate to levy the original PRD on these other agencies. The
derivative requirements are prepared using PRD formats in accordance
with the standard UDS outline and are completed within 15 calendar days
of PRD receipt.

**5.2. Program Support Plan (PSP).** The PSP is the official wing
response to the PRD. It is a plan of action and estimated costs to be
followed by the range and its supporting elements. The RTS contractor
prepares a schedule outlining the preparation of the PSP and sends it to
agencies responsible for review. After the review, negative or positive
responses for all items are sent directly to the RTS contractor. Each
functional area chief (annex and cost center) shall provide a revised
cost estimate as part of their PRD review and input to the PSP as
applicable. The RTS contractor prepares and forwards a preliminary list
of PRD requirements which cannot be met to 45 RANS within 30 calendar
days. 45 RANS will coordinate a solution or take action to renegotiate
support requirements. 45 RANS will then inform the RTS contractor of
actions planned or taken so they may be incorporated into the PSP.
Additional requirements coming from the Range Safety Operations
Requirement (RSOR) and the Range User Handbook, will be referenced in
the PSP along with cost estimates to provide the customer with a
complete list of program requirements and costs. The PSP is then
prepared by the RTS contractor and will be ready for 45 SW staff review
within 90 calendar days after receipt of the PRD.

5.2.1. The following disclaimer should be added to all PSPs generated by
the Eastern Range (ER) in Section 1010-Approval Authority and under
Remarks:

> \"This Program Support Plan (PSP) does not represent final commitment
> by the United States Government to support your program. This PSP is
> based on requirements as defined in the Program Requirements Document.
> You should understand that further refinements specified in your
> Operations Requirements Document may result in the identification of
> requirements which the government may be unable to support.
> Furthermore, manpower and scheduling priorities may preclude support
> as outlined in this PSP.\"

If the PSP is for a commercial program, the following sentence should be
added to the above statement.

> \"You should also understand that the United States Government
> reserves its right to priority access in accordance with Article XII
> of the Department of the Air Force, Model Expendable Launch Vehicle
> Commercialization Agreement, Revision 2, dated 12 May 1989 or the
> latest revision of the subject agreement.\"

Implementation of this PSP is not automatic. The customer must direct 45
RANS in writing to implement the plan.

5.2.2. When 45 SW requires support from another range, a PRD Extract
will be prepared as described above. When the response is received, ER
will ensure the input is incorporated into the consolidated PSP along
with appropriate cost estimates provided by the supporting Range. If 45
SW receives a PRD Extract from another range or test agency, 45 RANS
instructs the RTS contractor to prepare a response.

**Chapter 6**

**OPERATIONS REQUIREMENTS DOCUMENT AND OPERATIONS DIRECTIVE**

**6.1. Operations Requirements (OR).** Missile, space, research
programs, range operations, range engineering tests, and special project
tests must have a PRD/OR or an OR, and an OD for each operation or
series of operations for which 45 SW support is required. The PRD/OR may
be used in lieu of the OR only if requirements in the PRD are sufficient
in detail. If the PRD is deficient in describing all the range support
needed, a separate detailed OR must be written to cover each operation
or series of operations. The OR will be prepared in the UDS structure
using the UDS formats in RCC Handbook, Volume 2 and submitted according
to lead times shown in Table 7.2.1. The OR describes in detail an
individual operation and specific requirements for a portion of the
overall program. When there is a published PRD, the OR is not intended
to reflect new requirements or workload not previously stated in the
PRD. The OR may be used instead of a PRD for programs of short duration
requiring few of the range resources. A critical analysis to identify
new requirements not previously covered in the PRD will be made, and any
item in this category will be returned to the customer for appropriate
action.

6.1.1. Draft OR. Customers with new programs or complicated tests which
may require additional information before the OD is prepared should
present a draft OR in advance of the normal OR time line (Table 7.2.).
The 45 SW staff will be able to review the requirements and set up a
conference between the customer and 45 SW to resolve the problem areas.
If a draft OR conference is not needed, 45 RANS instructs the customer
to proceed in preparing the OR.

6.1.2. Operations Requirements Extracts (ORE). The official means for
any range to levy requirements for operational support on another range
or support agency is with an ORE. The ORE contains requirements
extracted by the range from the customer\'s OR with supplementary
requirements added and forwarded to one or more support ranges to
request their support. 45 RANS instructs the RTS contractor to review
the OR and the PRD Extract and prepare the ORE as well as the OD. The
ORE is prepared using the prescribed UDS formats. An ORE will have the
same number as the customer\'s OR and will always have an OD in
response. The ORE will be forwarded to 45 RANS within 15 days of receipt
of the OR with a CSR Form 6-186, **Documentation Coordination Form**,
attached for documentation tracking only. The approved ORE is then
returned to the RTS contractor for printing and distribution.

**6.2. OPERATIONS DIRECTIVE (OD).** The OD is a complete and detailed
operations plan to mobilize range support through coordination of
equipment operation and services needed to support a specific operation
or series of operations. The OD fulfills three basic purposes: It
provides detailed instructions to operating personnel; it serves as the
45 SW response to the customer and support response to the range; and it
becomes the instrument for operations scheduling. It is written in
sufficient detail to furnish complete instructions for a specific
operation or test. Teletype (TTY) ODs are permissible when time does not
permit processing through the normal cycle. ODs will be prepared using
the UDS format. ODs will be produced within the time lines of Table 7.2.

6.2.1. OD Disclaimer. The following disclaimer should be inserted in all
Operations Directives in Section 1010-Approval Authority under Remarks:

> \"This Operations Directive is based on requirements as defined in
> your Operations Requirements Document (OR). You should understand that
> further requirements or refinements arising after the date of this
> directive may result in increased cost and/or the identification of
> requirements which the government is unable to support. Furthermore,
> manpower and scheduling priorities may preclude support as outlined in
> the PSP.\"

6.2.2. If the OD is for a commercial program, the following statement
should be added:

> \"You should also understand that the United States Government
> reserves its right to priority access in accordance with Article XII
> of the Department of the Air Force, Model Expendable Launch Vehicle
> Commercialization Agreement, Revision 2, dated 12 May 1989 or the
> latest revision of the subject agreement.\"

**Chapter 7**

**DOCUMENTATION PROCESS**

**7.1. Purpose.** The 45 SW has a set procedure and process for
submitting and evaluating documents. To facilitate mission/program
execution the customer and the wing should follow these procedures as
closely as possible. However, the 45 SW is flexible and this process is
negotiable at certain steps to meet customer needs. The earlier in the
process that customer concerns are negotiated, the smoother the flow and
the more likely that the mission/program will succeed without delays.

**7.2. Procedures**:

7.2.1. All range customers will initially contact the Plans office (45
SW/XP) with new programs or new mission work loads. When required, a
Program Introduction (PI) document shall be forwarded from the
perspective range customer to 45 SW/XP. In response, 45 SW/XP will
prepare a statement of capability (SC) document to include the most
comprehensive cost estimate possible and return it to the prospective
customer once it is signed by the Wing Commander. All assumptions
developed in the cost estimation process will be included in the
statement of capability and are dependent on the completeness of the PI.
The point of contact for all other UDS documents concerning accepted
programs is the 45th Range Squadron (45 RANS).

7.2.2. The range customer signature on the PI, PRD, and OR signifies
that the document represents valid and necessary program information and
support requirements.

7.2.3. The 45 SW representative\'s signature on the PI, PRD and OR
signifies that the document has been accepted by the 45 SW for printing,
and distribution to facilitate preparation of a response document. This
is not intended to certify requirements, or that 45 SW will provide
support as requested. The requirements will be confirmed and support
determined during upcoming planning conferences. The 45 SW
representative\'s signature on the Statement of Capability (SC), Program
Support Plan (PSP), and Operations Directive (OD) signifies that support
will be provided as stated.

**7.3. Categories of Objectives and Requirements Classes.** Support
agency resources and development plans are based on valid support
requirements submitted by the range customers. The requirements are
those needed to meet customer program, mission, or operations
objectives. To ensure that requirements will be met, the range customer
must determine the category of objectives and the class (accuracy) of
requirements and relate these to basic needs. For a full description of
categories, requirements, and requirement prioritization refer to the
UDS Handbook, Volume 1.

**7.4. Lead Times.** Lead times will vary considerably from program to
program and are negotiable depending on the scope of the support needed.

7.4.1. The Program Introduction lead times will be established by
negotiation between the customer and 45 SW/XP. Nominal lead times are
shown in Table 7.1.

7.4.2. A PRD should be submitted immediately when support requirements
are identified. The customer should not delay submittal of the PRD
because of incomplete knowledge of support requirements. If extensive
programming effort is required, a complete PRD with exact telemetry
format must be in place no later than one and a half years prior to the
first use date (see paragraph 7.4.3.). Table 7.1 shows required lead
times for PRDs.

**Table 7.1. Lead Times Prior To Mission Execution (Pi / Prd) Scope Of
Augmentation.**

+-----------------------+-----------------------+-----------------------+
| **NEEDED**            | **PI**                | **PRD**               |
+-----------------------+-----------------------+-----------------------+
| New Construction of   | 3 1/2 years           | 3 years               |
| Facilities            |                       |                       |
+-----------------------+-----------------------+-----------------------+
| Extensive Additions   | 3 years               | 2 1/2 years           |
+-----------------------+-----------------------+-----------------------+
| Extensive Programming | 2 years               | 1 1/2 years           |
| and/or                |                       |                       |
|                       |                       |                       |
| siting                |                       |                       |
+-----------------------+-----------------------+-----------------------+
| Instrumentation       | 2 years               | 1 1/2 years           |
| Additions             |                       |                       |
+-----------------------+-----------------------+-----------------------+
| Minor Improvements    | 1 year                | 1/2 year              |
+-----------------------+-----------------------+-----------------------+

***NOTE:*** The lead times above are for planning purposes. The actual
time lines for a specific program should be coordinated during the PI/SC
phase of the UDS.

7.4.3. For final OR\'s the minimum lead time prior to first scheduled
launch, countdown rehearsal, launch simulation, or mission execution
shown in Table 7.2., reflects the number of calendar days required from
receipt of the OR by the range from the customer. All operations to be
scheduled must have an OD in place at supporting range resources prior
to the date of the scheduling meeting (first use date), normally at
0900L on Thursdays. Failure to meet these lead times could result in
support delays due to insufficient planning time. The minimum lead times
in Table 7.2., are required for acceptance, publication, and
distribution of the OR and the preparation, review, approval,
publication, and distribution of the OD.

**Table 7.2. Documentation Lead Times (In Calendar Days).**

+-------------+-------------+-------------+-------------+-------------+
| *           | **ER**      | **ARIA**    | **IN        | **REMARKS** |
| *DOCUMENT** |             |             | TER-RANGE** |             |
|             |             | (Note 2)    |             |             |
| (Note I)    |             |             |             |             |
+-------------+-------------+-------------+-------------+-------------+
| PI          |             |             |             | See Table   |
|             |             |             |             | 7.1.        |
+-------------+-------------+-------------+-------------+-------------+
| PRD         |             |             |             | See Table   |
|             |             |             |             | 7.1.        |
+-------------+-------------+-------------+-------------+-------------+
| OR          | 70          | 85          | 100         | Prior to    |
|             |             |             |             | First Use   |
|             |             |             |             | Date        |
+-------------+-------------+-------------+-------------+-------------+
| Customer    | 30          |             |             | Prior to    |
|             |             |             |             | Mission     |
| Countdown   |             |             |             | Execution   |
|             |             |             |             | (Note 7)    |
+-------------+-------------+-------------+-------------+-------------+
| Expedite OR | 5           | 15          | 15          | Prior to    |
|             |             |             |             | Mission     |
|             |             |             |             | Execution   |
|             |             |             |             | (Note 3)    |
+-------------+-------------+-------------+-------------+-------------+

**Table 7.2.1. Documentation Production Times (In Calendar Days)**

  -------------- -------------- -------------- ----------------- --------------
  **DOCUMENT**   **ER**         **ARIA**       **INTER-RANGE**   **REMARKS**

  SC             125            125            125               After receipt
                                                                 of PI (Note 9)

  PRDE                          15             15                After receipt
                                                                 of PRD (Note
                                                                 4)

  PSP            110                                             After receipt
                                                                 of PRD (Note
                                                                 6)

  Draft RSOR     30                                              After receipt
                                                                 of PRD

  Final RSOR     60                                              Prior to
                                                                 mission
                                                                 execution

  ORE                           25             25                After receipt
                                                                 of OR (Note 5)

  OPS Supplement 15                                              Prior to
  to RSOR                                                        Mission
                                                                 Execution

  OD             10             10             10                Prior to First
                                                                 Use Date (Note
                                                                 8).
  -------------- -------------- -------------- ----------------- --------------

***NOTES:***

> 1\. The range will assist with any draft reviews.
>
> 2\. If ARIA support requires foreign approval at a forward location,
> ARIA operations at Edwards AFB CA requires 120 calendar days notice.
> This notice may be provided by the customer in advance of the OR
> submission to the range.
>
> 3\. An Expedite OR should be used for any change in operational
> requirements within 30 days of launch. THIS INCLUDES MANDATORY HOLD
> LETTERS WHICH MUST BE FORMALLY RECEIVED BY L-20 DAYS.
>
> 4\. For PRDEs, five days are included for 45 RANS signature and
> distribution.
>
> 5\. For OREs, ten days are included for 45 RANS signature, printing,
> and distribution.
>
> 6\. For PSPs, 20 days are included for 45 SW review, signature,
> printing, and distribution.
>
> 7\. No countdown changes will be accepted after rehearsal or
> simulation without coordination and approval of the customer, range
> operations, and safety. For countdown changes submitted after the 30
> day time line prior to mission execution, coordinated approval must be
> obtained from the 45 RANS.
>
> 8\. The OD and the OD response to the ORE must be available 10 days
> prior to the First Use Date.
>
> 9***.*** If requirements are not revised and funding is still
> available.

7.4.4. Sometimes a combined PRD/OR is acceptable if sufficient detail is
known early. The PRD/OR must have requirements detailed at the OR level,
but must comply with PRD submittal lead times.

**7.5. Assignment and Numbering of 45 SW Programs.** The RTS contractor
assigns 45 SW program numbers as required. A block of 100 numbers is
assigned to each new program. The first number of each block identifies
the program and is assigned to the PRD and PSP. Numbers within each
block are used to identify separate series or types of tests and are
assigned to the OR and OD by the customer. An ORE should have the same
number as the OR. Because of the 45 SW Job Order numbering system, no
number may be reused in any one fiscal year. A list of assigned numbers
is maintained by the RTS contractor and published in the Operations
Documentation Index on a quarterly basis. Program titles will not be
used when it results in an unclassified document becoming classified. In
such cases, the words \"Title Classified\" will be used in lieu of the
program title. The document numbers are assigned as follows:

7.5.1. Range Operations Tests - Numbers 1-29 and 100-129. These
documents are originated by 45 SW support organizations to conduct
simulated operations and rehearsals to improve instrumentation operator
techniques, develop standard procedures, etc.

7.5.2. Range Engineering Tests - Numbers 30-59 and 130-159. These
documents are originated by 45 SW support organizations to conduct tests
on range instrumentation, improve range instrumen­tation, etc.

7.5.3. Special Project Tests - Numbers 60-99 and 160-199. These
documents are prepared by range customers to evaluate special equipment,
investigate special phenomena, etc. This type of test is usually
conducted concurrently with a missile, space or orbital program
operation.

7.5.4. Missile, Space or Orbital Program Tests - Numbers 200 up to
20000. The requirements documents are originated by range customers to
launch a missile, spacecraft, satellite or to cover a related portion of
a missile, space, or orbital program.

**7.6. Document Covers**. All second and third level UDS documents will
have a front and back cover of the same color and will include the
following: the UDS Logo, the 45 SW shield and, if appropriate, the
contractor or support agency logo. No other graphic designs are
acceptable. Customer requirements document covers will be yellow and
support document covers will be blue for unclassified documents. For the
classified documents, the color of the covers will be orange for
CONFIDENTIAL and red for SECRET. The Range Technical Services (RTS)
contractor will provide all levels 2 and 3 UDS covers for documents
printed by the ER. If a contractor or support agency logo is requested,
this logo must be furnished to the RTS contractor.

**7.7. Distribution of Documents.** The Distribution List Section (UDS
1020) in each support agency document shows the initial distribution
which is monitored by 45 RANS. The RTS contractor maintains a current
Supplementary Distribution List for the following documents: OR\'s,
PRD\'s, PRD/OR\'s, PRD/OR/RD\'s, and RSOR\'s. The RTS contractor
extracts and prepares for distribution the needed documents required by
all support agencies.

**7.8. Document Cancellation.** The range customer or originator will
notify 45 RANS in writing when a PRD or OR is to be canceled, including
the number, title, and date of the document. Cancellation of the
requirements document automatically cancels the support document.
Official cancellation is published in the Quarterly Operations
Documentation Index.

**7.9. Annexes.** These documents are used to describe subsystem or
special operations related to the major operation in the basic document.
Annexes are usually submitted with the basic document but may be
submitted later. Adding an annex is not considered a revision to the
basic document. When annexes are added after publication of the
document, the Revision Control and Classification Section (UDS 1031)
must be updated to include the annex. Annexes are alphabetically
identified (OR XXXA, indicating Annex A to OR XXX). The letters \"I\"
and \"0\" will not be used because of confusion with the initial number.

**7.10. Revisions.** A revision is considered to be any information or
pages replaced, added to, or deleted from an existing document.
Revisions may be made either by preparing a completely new document or
by submitting the revised information. The UDS documents will reflect
the revision number and date of the revision. Revisions shall be
numbered consecutively (for example: 01, 02, etc). When the basic
document becomes unmanageable due to an excessive number of revisions,
the basic document should be reissued, incorporating the revisions. The
Revision Control and Classification Section (UDS 1031) will be used to
identify the scope of the revision and shall be transmitted with any
revised pages. Section 1030 also provides a historical record of
revisions made to the document. The use of the symbol \"R\" in Column 72
to identify revised lines in an automated format is encouraged and
should be used whenever practical.

7.10.1. When a PRD item is referenced in an OR and the PRD is revised,
the customer will simultaneously submit a revision to the applicable OR.
A PRD revision with significant changes may require revisions to
supporting documentation. Additions or deletions of instrumentation,
variations in data processing or data products, and changes in funding
responsibilities are examples. 45 RANS, in conjunction with the RTS
Program Manager, will evaluate such PRD changes. Support documents will
be revised accordingly when requirements documents are revised, changed,
or modified.

7.10.2. Expedite PRD Revision. An Expedite PRD Revision is a tool to
facilitate new requirements of changes and requires immediate staffing
and reply to the customer. Timelines for an expedite PRD Revision must
be met as soon as possible if delays are to be avoided.

7.10.3. 45 RANS maintains current knowledge of all 45 SW instrumentation
capabilities, range configuration, and operating policies as applicable
to their assigned programs. When changes in these areas occur, as in the
\"Support Requirements Which Cannot be Met\" Section (UDS 2060), 45 RANS
will initiate action to revise the PSP wherever applicable.

7.10.4. OR Revision. This is a program OR change prepared when
operations support required by the customer needs to be redefined or
refined. This change is followed by publication of an OD Revision or a
new OD, depending on the extent of the revision.

7.10.5. Expedite OR (EOR). An EOR may be prepared when required for
immediate support or one-time changes to support for a specific mission,
in unusual cases when processing and publication of an OR Revision would
seriously impact program objectives. These requirements are implemented
by the use of Operations Control Instructions (OCI) or other immediate
means as required to meet customer demands. Expedites shall be numbered
consecutively starting with \"01\" and chronologically numbered. If the
expedite becomes a permanent change to the OR, then an OR revision must
be submitted to revise the OR.

7.10.6. The ODs are supplemented through the use of the following
instructions:

7.10.6.1. Range Operating Instructions (ROIs). The appropriate section
in the OD which references the applicable ROI. This is a short statement
of one or two sentences outlining the type of equipment or procedures to
be used.

7.10.6.2. Operations Control Instructions (OCI). These are last-minute
or one-time changes to the OD. The RTS contractor furnishes copies of
all OCIs to the appropriate 45 SW and range customer offices.

7.10.7. Revision Approval. Section UDS 1030 (Revision Approval) shows
approval of the revision by the customer and acceptance by the range.
This is used as a cover sheet for transmission, revised, or added pages
and summarizes the major changes in support requirements included in the
revision. In the case of OR Extract and OD revisions, a separate sheet
is used to transmit the revised or added pages but is not filed in the
document as is a 1030 section.

**7.11. Miscellaneous Documents.**

7.11.1. Range Safety Operations Requirement (RSOR). An RSOR shall be
published for each major operation and is used to document exceptions to
the standard provisions of missile flight operations according to ERR
127-1, *Range Safety*, and to levy requirements peculiar to a launch
vehicle series. The draft RSOR will be prepared by 45 SW/SEO, approved
by the 45 SW Chief of Safety, and forwarded to 45 RANS no later than 30
days after receipt of the PRD. Following resolution of any changes, the
final RSOR will be prepared, approved, and forwarded in the same manner
to 45 RANS no later than 60 days prior to mission execution along with
cost estimates for the safety requirements levied. 45 RANS is
responsible for printing and distribution of the RSOR. 45 SW/SE will
provide the range customer, through 45 RANS, a Range User Handbook of
all required safety documentation, checks, and time lines no later than
40 days after receipt of the PRD. The time lines will include Safety\'s
response turnaround times back to the customer through 45 RANS. The
requirements from the RSOR and the Range User Handbook will be included
in the PSP along with cost estimates for the safety functional area
requirements.

7.11.2. The RSOR Supplement contains additional information or
requirements peculiar to a launch but not contained in the RSOR. This
document is produced by wing Safety and will include cost estimates for
each additional requirement. A copy will be provided to the range
customer through 45 RANS.

7.11.3. If the range customer supplements basic information in the PRD
and OR in separate correspondence or on other appropriate forms, a
comprehensive list of these requirements with appropriate time lines
will be provided with the next UDS document revision or update.

7.11.3.1. Customers must ensure that any communications-electronics
equipment that radiates or receives electromagnetic energy to be used in
support of their operations has an approved frequency allocation.
Submitting a PI or a PRD is not a request by the range customer for
either an allocation or authorization of frequency usage. The Frequency
Management Office (45 CS/SCXF) can verify the frequency allocation
status of equipment approved for use by or in support of the DoD. A DD
Form 1494, **Application for Equipment Frequency Allocation**, must be
submitted to the Military Communications-Electronics Board (MCEB)
through 45 RANS to 45 CS/SCXF for any equipment not having an approved
frequency allocation. Additionally, a DD Form 1494 normally requires 180
days lead time for processing. Therefore, submission of the DD Form 1494
must be made as early as possible to avoid unnecessary program delays.

7.11.3.2. The Radio Frequency Environmental Working Group (RFEWG) is
chaired by 45 CS/SCXF. Its purpose is payload RF sensitivity and
protection and all related issues pertaining to the RF environment. In
addition, 45 SW routinely limits the RF field intensity to 1 V/m at the
payload for launch complexes and processing facilities which have
requested this protection. This limit increases to 10 V/m during launch
operations. ***NOTE:*** This is only applicable to emitters under 45 SW
control.

7.11.3.3. 45 SWI 40-201, *Radiation Protection Program*, defines the
guidelines, procedures, and responsibilities for the protection of
personnel from the biological hazards of ionizing and non-ionizing
radiation on the ER. AFOSH Standards 48-1, *Respiratory Protection
Program*, and 48-9, *Radio Frequency Radiation (RFR) Safety Program*,
further specify personnel protection requirements for radio frequency
and laser radiation biological hazards respectively.

7.11.3.4. A theoretical trajectory package with two printed tabulations
(computer or microfiche) must be furnished in addition to the PRD, if
applicable. The package must provide coverage from lift-off through the
end of 45 SW support requirements and should include the complete
mission requirements. The trajectory data must be formatted per the
Standard Theoretical Magnetic Tape Format provided by 45 SW/XP. See
Table 7.3, for submission of the package to 45 RANS. For programs
requiring ARIA support, a copy of the tapes and tabulations should be
sent directly, concurrent with submission to the ER, to:

452 Test Squadron

75 South Flightline Road

Edwards AFB CA 93524-6435

**Table 7.3. Lead Time For Theoretical Trajectory Tapes For Ballistic
Missile Flights And Space Missions (In Calendar Days)**

  ------------ --------------------------- --------------------------------
               **New System**              **Operational System**

  Initial      550                         260
  Submission                               

  Final        95                          50
  Submission                               
  ------------ --------------------------- --------------------------------

7.11.3.5**.** Information concerning missile antennas must be provided.
The data must be forwarded on a DOS formatted 3 1/2 or 5 1/4 inch low or
high density, double sided, floppy disk to 45 RANS not less than 12
months prior to the first launch of any program. The data must be
re-submitted three months prior to the first use of an antenna that is
different, or in a new configuration, or relocated on the launch vehicle
per IRIG Standard 253-93, *Missile Antenna Pattern Coordinate System and
Data Formats*.

7.11.3.6. Range safety data is required as indicated in Range User
Handbook. Included are such items as a Flight Analysis Data Package,
telemetry information including calibration and sensing data, and
analysis of propellants used and their effects on radio frequency
propagation. Specific program requirements will be provided by 45 SW/SE
to the 45 RANS using the Range User Handbook.

7.11.3.7. Any photographic requirements not defined in the standard UDS
documents will require a 45 SW Form 2135, **Photographic Outline** (45
CS/SCOT). Once completed, submit to 45 RANS for processing.

7.11.3.8. The Customer Countdown lists the sequence of specific
functions and events to occur or to be performed. It is considered a
hazardous procedure by Wing Safety and must be written in accordance
with ERR 127-1 and submitted to 45 SW/SE through 45 RANS for approval.

7.11.3.9. 45 SW Form 2091, **Operation Schedule/Forecast Request**; 45
SW Form 2050, **Launch Operation Schedule Request**; and 45 SW Form
2010, **Launch Forecast**, indicate date and range use time for
scheduling the OD. The forms are submitted to 45 RANS/DS for scheduling
purposes. Procedures are provided in 45 SWI 13-206.

7.11.3.10. 45 SWI 99-103, *Time Division Multiplexed Data Information
Required for Eastern Range Support*, defines format and lead times to be
supplied for use in programming telemetry decommutators used in
providing data to the customer. Telemetry format changes must be
submitted 310 calendar days prior to launch. If this time line or any
requirements in 45 SWI 99-103 cannot be met, a new schedule must be
negotiated during the PI/SC phase.

7.11.4. Any aircraft supporting Eastern Range operations or aircraft
operations with their own ODs must provide written notification as
defined in ERR 127-1 (Chapter 2) of the intended aircraft support to the
applicable range. The Intended Support Plan (ISP) gives Mission Support
Positions (MSP) as well as alternate MSPs, for weather or other
constraints. The ISPs and MSPs are then approved by 45 SW/SEY and
transferred to 45 RANS.

**7.12. Guidelines For Preparing Formats.** Instructions for preparing
formats are found in RCC UDS Document 501-90, Volumes 1, 2, and 3 which
are available from 45 SW/XP and 45 RANS. 45 SW/XP and 45 RANS will
provide whatever assistance is necessary to the customer to support the
UDS process in understanding the customer requirements and the available
support offered by the Range. The UDS Handbook, 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 preparation of the Program Introduction (PI),
Program Requirements Document (PRD), and the Operations Requirements
(OR). Volume 3 includes sample formats and describes procedures for
preparation of the Statement of Capability (SC), Program Support Plan
(PSP), and Operations Directive (OD). The UDS can be implemented using
either the automated or manual methods as described in Volume 1. The 45
SW/XP and 45 RANS will assist and act in a team effort to support the
customer.

RONALD L. LARIVEE

Colonel, USAF

Vice Commander

***Attachment 1***

***GLOSSARY OF Abbreviations, Acronyms, AND TERMS***

***Section A\--Abbreviations and Acronyms***

***Abbreviations and Acronyms Definitions***

**AFSPC** Air Force Space Command

**ARIA** Advanced Range Instrumentation Aircraft

**BMDO** Ballistic Missile Defense Organization

**CCAS** Cape Canaveral Air Station

**CCTV** Closed Circuit Television

**ECP** Engineering Change Proposal

**EOD** Explosive Ordinance Disposal

**EOR** Expedite Operations Requirement

**EPRD** Expedite Program Requirements Document

**ER** Eastern Range

**ERS** Eastern Range System

**ESA** European Space Agency

**DoD** Department of Defense

**IRIG** Inter-Range Instrumentation Group

**ISP** Intended Support Plans

**KSC** Kennedy Space Center

**LBS** Launch Base Services

**LRA** Lead Range Agency

**MCEB** Military Communications-Electronics Board

**MRTFB** Major Range Test Facility Base

**MSP** Mission Support Positions

**NASA** National Aeronautics and Space Administration

**OCI** Operations Control Instructions

**OD** Operations Directive

**OPR** Office of Primary Responsibility

**OPSEC** Operations Security

**OR** Operations Requirements

**ORE** Operations Requirements Extract

**PI** Program Introduction

**PRD** Program Requirements Document

**PRDE** Program Requirements Document Extract

**PSP** Program Support Plan

**RCC** Range Commanders\' Council

**RFA** Radio Frequency Authorization

**RFEWG** Radio Frequency Environmental Working Group

**ROI** Range Operating Instructions

**RSOR** Range Safety Operations Requirement

**RTS** Range Technical Services

**RVB** Requirements Validation Board

**RVITS** Range Visual Information Technical Services

**SBSS** Standard Base Supply System

**SC** Statement of Capability

**SW** Space Wing

**UDS** Universal Documentation System

**UK** United Kingdom

**WRM** War Reserve Materiel

***Section B\--Terms***

**First Use Date \--** This is the date the Operations Directive (OD) is
required for use; normally the date of the scheduling meeting at which
the operational date will be scheduled.

**Lead Range Agency (LRA) \--** The range that is responsible for
coordination of total support planning and operations for a particular
program, mission, or test. After initial program acceptance by 45 SW,
the customer submits detailed needs to the lead range. The lead range
identifies the support required from other agencies and coordinates the
total support effort.

**Mission \--** An operation, research and development project, launch
or other activity requiring 45 SW support and use of range resources
(reference 45 SWI 16-301, *45 SW Planning Guidance Document*).

**New Workload \--** Any activity which has not been previously accepted
by 45 SW which requires support that imposes commitment or expenditure
of 45 SW resources or any activity which changes previously accepted
workloads to require a \$500,000 increase in resources or a significant
reevaluation of the 45 SW support effort (reference 45 SWI 25-202,
*Acceptance of New Workloads*).

**Range Customers or Requesting Agency or Range User \--** Any
Department of Defense (DoD) organization, other U.S. Government agency,
state or local government, civic, private, or commercial organization,
or foreign government with authority to use range resources.

**Support Agency (SA) \--** An agency which commits its resources in
support of LRA program, mission or test requirements. The ARIA program
and Goddard Space Flight Center (Bermuda) are considered to be agencies
in support of lead range requirements.

**Support Range Agency \--** Major Range Test Facility Base (MRTFB) or
operational facility that provides support services to qualified
customers as determined by current directives. The Kennedy Space Center
(KSC) is considered a Support Range for the Lead Range Agency, 45 SW.