HQ NORTH AMERICAN AEROSPACE DEFENSE COMMAND NORAD REGULATION 55-17
Peterson Air Force Base, Colorado 80914-5001 10 August 1987
REQUESTING, SCHEDULING, AND APPROVING
REGION SYSTEM DOWNTIME
This regulation tells how to request, schedule, and approve region operations control centers (ROCC) and sector opera-
tions control centers (SOCC) downtime. Send supplements and recommended changes to HQ NORAD/NCO for ap-
proval. It there is conflict between this regulation and unit, MAJCOM, or contractor instructions, this regulation
applies and takes priority. This regulation applies to HQ NORAD and forces under operational control of CINCNOR
AD. RCS: NORAD-DOOS(AR)8501 applies; emergency status code is D.
1. Explanation of Terms: c. Sends requests for scheduled downtime to HQ
NORAD/NCO by AUTODIN or its equivalent,
a. Downtime. ROCCs and SOCCs are unable to automatic digital data network (ADDN), in Canada.
perform the NORAD mission due to nonavailability Include as a minimum:
or scheduled outage of mission-essential equipment.
(1) Start and stop times in Zulu.
b. Not Mission Capable (NMC). Unable to per-
form the NORAD mission due to scheduled and or (2) Reasons for downtime.
unscheduled outage of mission-essential equipment.
(3) For CONUS NORAD Region SOCCs which
c. Partially Mission Capable (PMC). One com- will expand as backup (if appropriate).
puter string is performing the NORAD mission. No
backup or switchover capability is available. Secon- (4) Estimate of time required to recall system.
dary missions; such as, training, exercises, data reduc-
tion, and so on, are limited or cannot be performed. (5) Primary office of contact.
d. Fully Mission Capable (FMC). All mission- d. Sends information copies to I AF/DOC/LGK
essential equipment, including redundant critical items, and other regions and sectors, as appropriate.
are capable of performing the NORAD mission.
e. Sends proposed downtime schedule to arrive by
e. Critical Maintenance. Maintenance that must be the 15th day of the month before the effective month.
performed within 24 hours of its originally requested Scheduling revisions should arrive 3 duty days before
time to prevent damage or deterioration to equipment time of the proposed change. If there are less than 3
or correct or avoid a condition which is hazardous to duty days before the scheduled downtime or if critical
personnel. maintenance is required and there is not time to for-
mally request downtime or a scheduled revision, the
2. Policy. To minimize degradation of the NORAD NORAD Command Director can approve downtime
mission, all scheduled downtimes which exceed 5 requests.
minutes are to be approved by CINCNORAD.
f. Classifies messages CONFIDENTIAL. Scheduled
3. How to Request Downtime. Region Director of downtimes become unclassified 30 minutes before
Operations (DO): implementation.
a. Ensures all planned downtimes are scheduled. 4. How to Schedule Downtime. HQ NORAD, Deputy
Director for Air Defense Operations (NCO):
b. Resolves conflicts in adjacent SOCC downtime
requests within the region. a. Consolidates the downtime requirements.
Supersedes NORAD Regulation 55-160, 14 January 1985. (For summary of changes see page 2,)
No. of Printed Pages: 2
OPR: NCOOG (Maj F. H. Fraser)
Approved by: Col J. T. Talley
Editor: W. A. McGarvey
Distribution: F;X(HQ Air Command/SSOGE, CFB Winnipeg, Manitoba CN R2J OTO..................................................1
HQ TAC/DO, Langley AFB VA 23665-5001........................................................................................1
HQ I AF/DO, Langley AFB VA 23665-5009.......................................................................................3)
2 NR 55-17 10 August 1987
b. Coordinates times and revisions with the NORAD 5. Procedures for Downtime Approval:
Command Director and the Air Defense Operations
Center (ADOC). a. NORAD Regions:
c. Resolves conflicts of adjacent region downtime (1) Call the NORAD Command Director for final
requests. approval 30 minutes before scheduled start time.
d. Notifies the following of any revisions: (2) Monitor expansion procedures between
SOCCS, if appropriate, and advise ADOC when ex-
(1) Vice Director NORAD Combat Operations pansion is complete.
b. Command Directors. Base their approval on:
(2) Command Director (CD).
(3) Chief Systems Control Division (LKR). (1) Threat.
(4) Chief Air Defense Operations Center Division (2) Adverse affects on the region requesting
(NCOA). downtime, if it is not allowed.
(5) Chief Command Post Operations Division (3) Adjacent region status.
(6) 1 AF Command and Control Systems (DOY). 6. Unscheduled Outage. In the event of an unscheduled
outage of mission-essential equipment, immediately
(7) 1 AF Communications and Electronics notify the ADOC and adjacent region. The ADOC
Maintenance (LGK). notifies the NORAD Command Director and Systems
Center. If applicable, SOCCs with scheduled
e. At least 3 days before the first day of the effec- downtime, adjacent to the unscheduled outage, comply
live month, sends tentative approval or disapproval to with provision in NR 55-150 as appropriate. Notify
the affected region. Note: The approval or disap- ADOC and adjacent region as soon as the unscheduled
proval is based on adjacent region planned downtimes, outage has returned to a PMC or FMC condition.
DEFCON status, and reason for the request.
OFFICIAL JOHN L. PIOTROWSKI
Commander in Chief
G. A. STANSELL
Director of Administration
SUMMARY OF CHANGES
The terms NOPLEX, SIMPLEX, and DUPLEX have been eliminated and replaced by the terms not mission capable
(NMC), partially mission capable (PMC), and fully mission capable (FMC) (para 1). Reflects modifications required
due to the formation of CONUS NORAD region and Sector Operations Control Centers.