SUBJECT: LAUNCH INSTRUMENTATION PERFORMANCE ANALYSIS

PURPOSE: This procedure defines the organizational responsibilities and
procedures for identifying, analyzing, documenting, tracking, and
briefing deviations from expected instrumentation system performance
which occur during launch support. Procedures for reporting
instrumentation system status and status changes are set forth in ROI
03-03-04.

OPR: Systems Analysis

REFERENCES: ROI 03-01-04

ROI 03-03-04

ATTACHMENTS: 1. **(REDACTED) 2-Day Anomaly Report (Representation)**

2\. **(REDACTED) 7-Day Anomaly Report (Representation)**

ANNEXES: None

1.0 GENERAL

A. **Systems Analysis** is responsible for providing the **(REDACTED)**
with an analysis of all deviations from expected instrumentation system
performance during launch support. For the purposes of this instruction,
and other documentation, any instrumentation performance deviation is
termed an \"anomaly\" (see paragraph 2.0 for definitions).

B. **Systems Analysis** is responsible for integrating all available
information on each anomaly into a concise and accurate report
describing the cause of the event, mission impact, and status of efforts
to prevent a recurrence (including, when known, action agency and
expected completion dates).

C. **Systems Analysis** is responsible for tracking the status of all
open anomalies and periodically reporting the status of these anomalies
until final resolution.

D. **Systems Analysis** is responsible for maintaining a database of all
anomalies for trend analysis. **Systems Analysis** will update the
database as new information is received regarding the nature of an
anomaly and resolution status. Historical summaries of anomalies by
system or anomaly type are provided to authorized requestors.

2.0 DEFINITIONS

A. An anomaly occurs whenever there is a total or partial loss,
degradation, or delay of Eastern Range Instrumentation System capability
at any time during an operation.

Anomalies include:

1\. Total or partial loss, degradation, or delay of required data or
services

2\. A system failure or upset which is detected and corrected during the
operation irrespec-tive of impact.

B. Operation

For the purposes of this instruction, an operation is defined as the
period from the start of the Eastern Range countdown until the **end of
Eastern Range instrumentation coverage, as de-fined by the Expected
Coverage Plan (ECP) for the mission. For systems with responsibilities
not defined by the ECP, the operation ends at Range Safety release.
Events that occur before the start of the countdown are classified as
anomalies if the event results in a launch delay or scrub or at the
direction of the 45th Space Wing (45 SW) Range Engineer.**

C. Required Data or Services

Any Range, or Range User, mandatory or required data or services set
forth in the applicable Operations Requirements (OR), Range Safety
Operations Requirement (RSOR), or Operations Control Instruction (OCI),
including allied support (such as power, communications, envi-ronmental
controls, etc.) that is necessary to accomplish required data collection
or services.

D. Instrumentation System

**Any system that provides data or services to meet either Eastern Range
or Eastern Range customer requirements during the operation. These
systems are normally listed in the Launch Book or OCIs for the
mission.**

E. Anomaly Class

Each anomaly will be classified as follows:

1\. [Mission Impact]{.underline} - a class of anomaly **that results in
a failure to meet a Range Safety or Range Customer mandatory
requirement. This led to either a launch delay or scrub or an anomaly
occurred during flight that could reasonably be expected to have caused
a launch delay or scrub had the problem been known or expected prior to
launch.**

2\. [Major **Impact**]{.underline} - a class of anomaly **that results
in a failure to meet a Range Safety or Range Customer non-mandatory
requirement.**

3\. [Minor **Impact**]{.underline} - a class of anomaly **that results
in a failure to meet a non-Range Safety or non-Range Customer
non-mandatory requirement or a failure, outage, or degradation of a
system or capability that was corrected before any requirement was
impacted.**

F. Anomaly Status

Each anomaly will carry a status as follows:

1\. [Open Anomaly]{.underline} - an anomaly is classified as open if it
satisfies either of the following con-ditions:

a\. The cause of the anomaly is not well understood and further
investigation or analysis is required to develop a recommendation for
corrective action.

b\. The cause of the anomaly is well understood but corrective action
has not been completed.

2\. [Closed Anomaly]{.underline} - an anomaly is classified as closed if
it satisfies either of the following conditions:

**a. Investigation has been completed and either the cause of the
problem has been identified and corrective action completed or the cause
has not been identified and further investigation is not warranted and
(REDACTED) approval of closure has been obtained.**

b\. The corrective action required to prevent a recurrence has not been
completed and the anomaly recurs during a subsequent launch. In this
case, the first occurrence of the anomaly is closed and the most recent
occurrence is kept open until the requirements of the preceding
paragraph are satisfied or the anomaly recurs again.

G. Workaround

A workaround is a formally documented temporary measure that is
implemented to avert the total or partial loss, degradation, or delay of
required data or services. Workarounds are normally limited to
procedural changes but may include instrument reconfiguration when
formally approved by **(REDACTED)**.

3.0 PROCEDURES AND RESPONSIBILITIES

A. Manager, **Systems Analysis**

1\. The Manager, **Systems Analysis**, is responsible for establishing,
enforcing, and updat-ing (when required) the policies and procedures
necessary to ensure the successful con-duct of the Launch
Instrumentation Performance Analysis Program.

2\. The Manager, **Systems Analysis**, or his designee, will attend the
Project Manager\'s Mis-sion Readiness Briefing (which is nominally
scheduled for L -**(REDACTED)** to L **-(REDACTED)** days) **and
identify any outstanding Mission Impact Items which were not already
addressed in the briefing by the System Managers** **and** could impact
the successful completion of the **next** launch operation.

**B. Systems Performance Section Manager, Systems Analysis**

**1. The Systems Performance Section Manager will attend the Post
Mission Review.**

**2. The Systems Performance Section Manager will review the 2-Day and
7-Day Re-ports submitted by the Instrumentation Analysis Group
Supervisor and submit fi-nal versions to the Launch Performance Analysis
(LPA) Process Manager by the close of business on the due date.**

**C. Instrumentation Analysis Group Supervisor, Systems Analysis**

**1. The Instrumentation Analysis Group Supervisor will assign Systems
Analysts for each launch operation.**

**2. The Instrumentation Analysis Group Supervisor will review all
reports from the Systems Analysts prior to submittal to the Systems
Performance Section Manager.**

**D. LPA Analyst, Systems Analysis**

1\. The **Systems Analysis LPA Analyst** will monitor selected
instrumentation nets at the **Systems Analysis LPA** console in the
Range **Operations** Control Center (R**O**CC) during the range
countdown and launch phase. The analyst will compile a detailed
chronology of all potential anomalies and associated actions and
instrumentation status changes for later review with the Range Engineer
and Instrumentation Systems Range Officer (ISRO).

**2.** The **Systems Analysis LPA Analyst** will attend, when possible,
the Operations Control Post **Mission** Critique (normally held at the
R**O**CC on L +**(REDACTED)** workday).

**3.** **The Systems Analysis LPA Analyst** will chair the **Systems
Analysis Post Mission Re-view** (normally held at Building
**(REDACTED)** on **L** +**(REDACTED)** workday). Each anomaly
identified will be re-viewed by the **Systems Analysis LPA Analyst** and
the responsible **Systems Analysis Systems Analysts**. Additional
anomalies identified by the Systems Analysts will be added at this time.

**E. Reliability Analysis Group Supervisor, Systems Analysis**

**1. The Reliability Analysis Group Supervisor will assign a qualified
Systems Analysis LPA Analyst for each launch.**

**2. The Reliability Analysis Group Supervisor will schedule and attend
the Post Mission Review, and notify the Range Engineer, the appropriate
Program Manager, MCCJC, and the Systems Analysis Technical Staff via
e-mail.**

**3. The Reliability Analysis Group Supervisor will ensure that all
Single Event Site Status Reports (SESSRs), which pertain to a specific
launch and instrumentation system, received from the Maintenance Control
Center (MCC) are distributed to the appropriate Systems Analysis Systems
Analysts.**

**4. By L +(REDACTED) working day, the Reliability Analysis Group
Supervisor will receive the 2-Day Anomaly Report input approval from the
Systems Performance Section Manager.**

**5. The Reliability Analysis Group Supervisor will prepare the 2-Day
Anomaly Report (Attachment 1) and ensure the report is distributed by L
+(REDACTED) working days. The 2-Day Anomaly Report includes the
following information:**

**a. Anomaly number**

**b. Instrumentation Supersystem affected**

**c. Names of the responsible Systems Analysis Systems Analyst and
Instrumentation Systems contact.**

**d. Condensed description of the nature of the anomaly**

**6. By L +(REDACTED) working days, the Reliability Analysis Group
Supervisor will receive the 7-Day Anomaly Report input approval for each
anomaly from the Systems Performance Section Manager.**

**7. The Reliability Analysis Group Supervisor will prepare the 7-Day
Anomaly Reports, and ensure that the reports are distributed on, or
before, L +(REDACTED) working days. The following information is
included in the 7-Day Anomaly Report (Attachment 2):**

**a. Anomaly number**

**b. Instrumentation Supersystem, System and Subsystem affected**

**c. Potential and actual operational impact of the anomaly**

**d. Recommended status of the anomaly**

**e. Resolution agency and estimated completion date (ECD) (if
recommended status is "Open").**

**f. Number of duplicate occurrences for the Subsystem in past two
years**

**g. Last duplicate anomaly number and date occurred (if a duplicate
anomaly)**

**h. Names of the responsible Systems Analysis Systems Analyst and
Instrumentation Systems contact.**

**i. Description of the anomaly, including the system background,
potential and actual operational impact, diagnostic action, and
recommendations for correc-tive action or further investigation.**

**8. The Reliability Analysis Group Supervisor will receive periodic
input from Systems Analysts when the status of any open anomaly changes
and will ensure that the LPA database is updated when this information
is received.**

**9. The Reliability Analysis Group Supervisor will coordinate any
change in anomaly class or anomaly status with the Range Engineer.**

**10. The Reliability Analysis Group Supervisor will conduct the monthly
Range Engi-neer Open Anomaly Review in Building (REDACTED).
Instrumentation Systems Section Managers, a Maintenance Control Center
representative, and appropriate Program Managers should participate in
the review to provide additional information or clarification of the
anomalies.**

**During the Open Anomaly Review, the Systems Analysis Systems Analysts
will present the status of corrective actions needed to prevent a
recurrence of all open anomalies which are not classified as Long Term
Open.**

**11. The Reliability Analysis Group Supervisor will prepare and
distribute the Quarterly Long Term Open Anomaly Report, which provides
corrective action updates on anomalies classified as Long Term Open.**

**12. The Reliability Analysis Group Supervisor will maintain a
consolidated launch folder for each individual launch operation.**

F. Systems Analysts, **Systems Analysis**

1\. Systems Analysts are responsible for maintaining cognizance of
assigned instrumenta-tion systems, to include actual performance during
mission support, system capabilities and limitations, launch support
commitments, and ongoing engineering change or devel-opment activity.

2\. Systems Analysts who monitored launch support as directed by their
respective Group Leaders will attend the **Systems Analysis** Post
**Mission** Review. The Systems Analyst will ensure that the anomaly
description reported by the **Systems Analysis LPA** is accu-rate, given
the information available at the time of the review. Any additional
anomalies identified by the Systems Analysts, and not already accounted
for by the **Systems Analysis LPA**, will be added at this time.

**3. LPA anomaly occurrence times are reported as follows:**

**a. Anomaly times will be recorded using either L or T notation,
depending on the point in the countdown when the anomaly occurred.**

**b. The L or T time will always be followed by wall clock time in
Universal Time Coordinated (UTC) (the Z designation will be used in all
LPA reports).**

**c. For countdowns which cross two different UTC days, the day of the
month number will always precede the UTC time (i.e., 23/1215Z represents
1215 UTC on the 23rd day of the month).**

**d. The reported L or T time will be coincident with the actual L or T
time the anomaly occurred and will not be adjusted if the actual T -0
occurs after the planned T -0.**

**e. If the time the anomaly occurred is not known, then time the
anomaly was de-tected will be used. If the time the anomaly was detected
is not known, then the time the anomaly was reported will be used.**

**f. L times will be used until the L and T times are synchronous, then
only T times will be used for the remainder of the operation. T times
will be used exclu-sively for missions with no built-in holds and for
all anomalies after T -0.**

**g. L times are always expressed in minutes; therefore, the "min"
designation is understood and not required. T plus times may be
expressed in either minutes or seconds; therefore, all T plus times must
be followed by either the "min" or "sec" designations.**

**h. If the clock is holding at the time of an anomaly, the letter "H"
will follow the time (i.e., T -5H indicates T -5 minutes and holding).**

**4. Systems Analysts are responsible for preparing a 2-Day Anomaly
Report input for each anomaly assigned during the Systems Analysis Post
Mission Review.**

**5. Systems Analysts are responsible for preparing a 7-Day Anomaly
Report input for each anomaly assigned during the Systems Analysis Post
Mission Review.**

**6. Systems Analysts are responsible for providing the Reliability
Analysis Group Su-pervisor with updated information on each anomaly, as
that information becomes available.**

**7. Systems Analysts will review post mission data and prepare a new
anomaly report if any one of the following conditions is observed:**

**a. Radar Systems**

**1) Any instance where a committed radar loses track not predicted in
ad-vance by the ECP.**

**2) Any instance where a committed radar drops below the Range
Safety/Range User criteria not predicted in advance by the ECP.**

**3) Any instance where a radar exhibits tracking errors exceeding the
estab-lished system standard.**

**b. Telemetry Systems**

**1) Any instance where a committed telemetry system drops below
receiver threshold not predicted in advance by the ECP.**

**c. Metric Optics Systems**

**1) Any instance where there is no combined (multi-station) solution
during the committed coverage period.**

**d. Command Destruct Systems**

**(REDACTED)**

**(REDACTED)**

**G.** Maintenance Control Center (MCC)

1\. The MCC is responsible for the collection and distribution of all
SESSRs under\
ROI 03-03-04.

2\. The MCC will forward all SESSRs, which apply to launch
instrumentation during the launch support period, to **Systems
Analysis** within one hour of receipt.

3\. The MCC will publish listings of the Mission Impact Items.

**H.** **Instrumentation Systems/Downrange Operations**/Site Managers

1\. The **Instrumentation Systems/Downrange Operations**/Site Managers
will provide additional information regarding specific anomalies (beyond
that reported in the SESSR) when requested by the **Systems Analysis**
Systems Analyst.

2\. The **Instrumentation Systems** Section Managers (or their
representative) and a management representative of **Downrange
Operations** will attend the Range Engineer Open Anomaly Reviews.

**ATTACHMENT 1**

**(REDACTED)**

**ATTACHMENT 2**

**(REDACTED)**