SUBJECT: INSTRUMENTATION COVERAGE PLANS

PURPOSE: Define instrumentation coverage intervals

REFERENCES: None

ATTACHMENTS: None

ANNEXES: None

1.0 GENERAL

A. Instrumentation Coverage Plans (instrumentation coverage intervals),
as defined by this ROI, will be provided to **(REDACTED)** by Operations
Control. Two types of coverage plans are generated by Operations
Control.

1\. Committed Coverage Plans provide the official Eastern Range support
commitments given in response to Launch Agency and Range Safety
requirements for Radar, Telemetry, Command, Optics, and FTSS
Instrumentation scheduled for launch, midcourse and orbital support.
Final support commitments are provided by **(REDACTED)** after review of
proposed commitments, issued by **(REDACTED)** Operations Control.

2\. Expected Coverage Plans provide information to alert operators to
potential problems in meeting Launch Agency and Range Safety
requirements. Expected Coverage Plans will be provided for Radar,
Telemetry, Command, Optics, and FTSS Instrumentation scheduled for
launch, midcourse and orbital support.

B. Committed and Expected coverage plans are based on scientific
analysis using the general criteria specified in this ROI and modified
by past experience with like vehicles and similar trajectories.

The development process will use but is not limited to the following
inputs:

1\. EWR 127-1/RSOR/Ops Sup

2\. 45 SWI 99-101/45 SWI 99-102/45 SWI 21-102

3\. PRD/OR

4\. Trajectory Tape (AFSC Manual 80-12)

5\. Missile Antenna Patterns (IRIG Standard 253-93)

6\. General Criteria

7\. Instrumentation Parameters

8\. Masking Profiles (ROI 02-03)

9\. Radiation Restrictions (ROI 10-01-12)

10\. Defined Caveats

11\. Site Specific Look Angles and Predicted Signal to Noise or Power
Levels

12\. Site Specific Aspect Angles and Predicted Flame Attenuation
Intervals

13\. Site Specific Aspect Angles and Predicted Polarization Mismatch
Intervals

14\. Launch Performance Summaries

15\. Recorded Data from Previous Launches

16\. Approval and Revision Cycle

NOTE: Experience criteria will be applied to expected coverage plans as
described in paragraph 1.0 D below.

C. It is estimated at least 95% of the total solid line interval will
meet the associated Range User and Range Safety Quality needs.

D. In situations where committed coverage is less than expected
coverage, the expected coverage chart will reflect the same coverage as
the committed charts. In this case one set of charts will be prepared
and titled \"committed and expected\" coverage.

1.1 Chart Symbols

A. Three levels of support for radar and telemetry will be shown on the
Expected Coverage and Committed Coverage charts as follows:

1\. Radar

a\. Metric data quality requirements will be met - indicated by a wide
solid bar ( ).

b\. RU/RS data quality requirements will be met - indicated by a narrow
solid bar,

( ).

c\. Data available but documented data quality requirements are not
expected to be met - indicated by a broken bar, (- - - - - - -).

2\. Telemetry

a\. RU/RS data quality requirements will be met - indicated by a wide
solid bar\
( ).

b\. RS data quality requirements will be met - indicated by a narrow
solid bar, ( ).

c\. Data available but documented data quality requirements are not
expected to be met -indicated by a broken bar, (- - - - - - -).

B. The minimum performance criteria for the quality levels noted above
are defined in the radar and telemetry tables that follow in paragraph
1.2.1 and 1.2.2. The command criteria, using different symbols, are
described in paragraph 1.2.3. Optics criteria are defined in paragraph
1.2.4.

1.2 General Criteria

1.2.1 Radar

Metric Quality RU/RS Criteria RU/RS Criteria Not Met

\- - - - - - -

NOTES: 1. S/N - Received signal-to-noise ratio

2\. Metric quality data is defined as realtime track data free of
multipath and refraction errors and derived from signal returns adequate
to achieve both error gradient independent of input level and designed
servo loop gain and track bandwidth. Satisfies Range Safety and Range
User requirements.

1.2.2 Telemetry

\- - - - - - -

NOTES: 1. S/N - Received signal-to-noise ratio

2\. RUN - Range User Needs in terms of PRD specified bit error rates

1.2.3 Command

Symbols and criteria for 4 levels of support when RU/RS required signal
margin is 9dB.

Required Required -3dB Required -6dB Required -9dB

\>\>\>\>\>\>\>\> \<\<\<\<\<\<\<\< xxxxxxxx

Symbols and criteria for 5 levels of support when RU/RS required signal
margin is 12dB.

\>\>\>\>\>\>\>\> \<\<\<\<\<\<\<\< xxxxxxxx \-\-\-\-\-\-\-\-\-\-\-\-\-\--

NOTE: Signal Margin (S/M) is equal to 0dB at the specified and/or
verified functional threshold of the command receivers.

1.2.4 Metric Optics

RS Criteria

NOTES: 1. Metric optics sites provide a combined angles only solution
with operator initiated quality bit indicating that the vehicle is
within the telescope reticle (a minimum of 4 sites are required for
Range Safety support).

2\. Launch area radars provide single source optical angle coverage and
auto-range track (skin or beacon gate). An operator initiated quality
bit confirms the vehicle is clearly observed within the boresight TV
reticle. This mode of operation is referred to as DAAR/O (Designate
Angles Auto-Range and Optical quality bit set).