HQ NORTH AMERICAN AEROSPACE DEFENSE COMMAND NORAD REGULATION 102-1
HQ UNITED STATES SPACE COMMAND USSPACECOM REGULATION 102-1
Peterson Air Force Base, Colorado 80914 11 March 1992

Command and Control and Communications

The NORAD/USSPACECOM INTEGRATED COMMAND AND CONTROL SYSTEM(NUICCS)
MISSION SYSTEMS INTEGRATION PROCESS

This regulation establishes the policy and procedures for the Commander in
Chief, North American Aerospace Defense Command (CINCNORAD), and the Commander
in Chief, United States Space Command (USCINCSPACE) NUICCS Mission Systems
Integration (MSI) Process. It applies to HQ NORAD and its supporting commands
and responsible agencies; and HQ United States Space Command (USSPACECOM) and
its components.
Paragraph Page
Chapter 1 - Introduction
Background . . . . . . . . . . . . . . . . . . . . . . . . . 3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 3

Chapter 2 - NUICCS MSI Process Description and NUICCS Procedures
NUICCS MSI Process Interaction . . . . . . . . . . . . . . . 2.1 5
NUICCS Impact Criteria . . . . . . . . . . . . . . . . . . . 2.2 7
NUICCS MSI Process Checkpoints . . . . . . . . . . . . . . . 2.3 7

Chapter 3 - Responsibilities
MSIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 12
MSIB Executive Secretariat (HQ USSPACECOM/J6N) . . . . . . . 3.2 12
NUICCS Concept Review Subpanel . . . . . . . . . . . . . . . 3.3 12
NUICCS Technical Review Subpanels . . . . . . . . . . . . . 3.4 12
Directorate of Manpower and Personnel
(HQ NORAD/USSPACECOM/Jl) . . . . . . . . . . . . . . . . . 3.5 12
NORAD Combat Operations Staff (HQ NORAD/J3) . . . . . . . . 3.6 13
NORAD Planning Staff (HQ NORAD/j5) . . . . . . . . . . . . . 3.7 13
Directorate of Intelligence (HQ NORAD USSPACECOM/j2) . . . . 3.8 13
Directorate of Operations (HQ USSPACECOM/j3) . . . . . . . . 3.9 13
Directorate of Command Control Systems and Logistics
(HQ USSPACECOM/ j4-j6) . . . . . . . . . . . . . . . . . . 3.10 13
Deputy Directorate for NUICCS Policy, Architecture,
and Integration (HQ USSPACECOM/J6N) . . . . . . . . . . . . 3.11 14
Deputy Directorate for Logistics (HQ USSPACECOM/J4L) . . . . 3.12 14
Deputy Directorate for System Certification
(HQ USSPACECOM/J6C) . . . . . . . . . . . . . . . . . . . . 3.13 14
Directorate of Plans (HQ USSPACECOM/J5) . . . . . . . . . . 3.14 14
Joint Strategic Defense Planning Staff (JOSDEPS) . . . . . . 3.15 15
Center for Aerospace Analysis (HQ USSPACECOM/AN) . . . . . . 3.16 15
Inspector General (HQ NORAD/USSPACECOM IG) . . . . . . . . . 3.17 15
NORAD Responsible Agencies and USSPACECOM
Component Commands . . . . . . . . . . . . . . . . . . . . 3.18 15

No. of Printed Pages: 29
OPR: HQ USSPACECC)M/J6NI (CDR Lew E. Alleman)
Approved by Maj Gen Carl G. O'Berry
Editor: Kathy L. Kite
Distribution: F;X(joint Staff/J6N, Washington, DC 20318-6000 ............... 1)
Naval Space Command/Nl7, Dahlgren VA 22448-5170 .......... 5)
US Army Space Command/MOSC-OPI, Stop 80 ................... 5)

2 NUR 102-1 11 March 1992

Paragraph Page

Figures
2.1 NUICCS MSI Checkpoint Interaction with Other Processes ....
2.2 NUICCS Impact Criteria .................................... 7
2.3 NUICCS Concept Review Subpanel Membership ................. 8
2.4 The Scope of the MSI Process within NUICCS ................ 9
2.5 NORAD/USSPACECOM Technical Review Subpanel membership ..... 10
2.6 Responsible Agency/Component Technical Review Subpanel
Membership .............................................. 11

Attachments
1. Special Cases .............................................. 16
2. References ................................................. 18
3. Process Overviews .......................................... 19
4. Definitions ................................................ 23
5. The Scope of the NUICCS MSI Process ........................ 26
6. Acronyms ................................................... 28

NUR 102-1 11 March 1992 3

Chapter 1 Introduction

1.1 Background:

1.1.1. Command and control (C2) system integration within NORAD and
USSPACECOM has historically been accomplished as a subsystem activity,
generally as an adjunct to system acquisition. In the early 1980s, the first
attempt at establishing a system level integration activity resulted in the
formation of the System Integration Office (SIO) in U.S. Air Force Space
Command (HQ AFSPACECOM), the function of which was to ensure the technical
integrity of the Integrated Tactical Warning and Attack Assessment (TW/AA)
System. Initially, the SIO was an element of the AFSPACECOM Deputy Chief of
Staff, Systems Integration, Logistics, and Support, and this collective staff
embodied both the Integrated TW/AA System integration and system technical
certification functions. The functions of the SIO have since been transferred
to HQ USSPACECOM and HQ AFSPACECOM. (See attachment 1 for specifics on the
relationship between the NUICCS Mission Systems Integration (MST) Process and
the integrity of the Integrated TW/AA System.)

1.1.2. As NORAD and USSPACECOM command and control requirements grew to
include C2 support for other mission elements (such as counterdrug operations,
space launch, and space surveillance), it became apparent that the Integrate
TW/AA mission, while still of great importance and highest priority among the
CINC's responsibilities, was becoming a subset of a much larger command and
control system of systems. That system of systems has been designated the
NORAD/USSPACECOM Integrated Command and Control System (NUICCS).

1.2. Purpose: This regulation:

1.2.1. Designates the Director of Command Control Systems and Logistics (HQ
USSPACECOM/j4-J6) as the CINCNORAD/USCINCSPACE agent responsible for NORAD and
USSPACECOM command and control system integration. Consistent with that
designation is authority for the USSPACECOM/J4-J6 to establish system
integration policy and procedures, establish system standards and/or ensure
system standards implementation, certify integrity, and establish/enforce
system configuration management policy for NUICCS. (This authority will be
further defined in future regulations).

1.2.2. Defines the NUICCS MST Process, which is designed to ensure that
changes to the NUICCS, whether in the form of new system interfaces, major
NUICCS upgrades, or subsystem modifications/additions, are strictly
controlled, and accomplished in accordance with established NUICCS technical
standards.

1.2.3. Establishes system integration responsibilities for all NORAD/
USSPACECOM elements and NUICCS users. Specifically:

1.2.3.1. The NUICCS mission system integration process applies to:

1.2.3.1.1. The C2 subsystems, elements, and interfaces over which CINCNORAD
has operational control (OPCON) and/or over which USCINCSPACE/Commander, U.S.
Element NORAD (CMDRUSELMNORAD) has combatant command (COCOM).

4 NUR 102-1 11 March 1992

1.2.3.1.2. The C2 system interfaces with non-command and control and
intelligence systems/subsystems over which the CINC has OPCON or COCOM.

1.2.3.1.3. The interfaces between NORAD/USSPACECOM C2 systems and other
systems over which the CINC may not exercise OPCON or COCOM.

1.2.3.2. The NUICCS MSI Process will adhere to normal chain of command and
normal staff relationships to the maximum extent possible. oversight of the
NUICCS MSI Process is a responsibility of USSPACECOM/J4-J6. NORAD responsible
agencies and USSPACECOM components, subcommands, and/or support elements will
implement the process and adapt existing support processes to satisfy NUICCS
policy, procedures, and standards.

1.2.3.3. The Mission Systems Integration Board (MSIB) will assist the
USSPACECOM/j4-j6 in the NUICCS MSI Process oversight role. The MSIB is an
advisory body whose membership will include, as a minimum, general officer
level representation from HQ NORAD and HQ USSPACECOM AN, J2, J3, and J5, and
senior officer representation from USARSPACE, NAVSPACECOM, and AFSPACECOM.
Permanent or temporary representation on the MSIB may be requested by the
Chairman from other agencies as required. The MSIB will be chaired by
USSPACECOM J4-J6 and may establish panels/subpanels, as appropriate, to
conduct studies, analyses, system/subsystem reviews, and system integration
related activities, as required.

NUR 102-1 11 March 1992 5

Chapter 2 - NUICCS XSI Process Description and NUICCS Procedures

2.1. BTUICCS MSI Process Interaction:

2.1.1. An overview of existing processes that interact with the NUICCS MSI
Process is contained in attachment 3. Definitions associated with NUICCS,
mission systems integration, and the NUICCS MSI Process are contained in
attachment 4. The full scope of the NUICCS MSI Process is depicted in
attachment 5.

2.1.2. The NUICCS MSI Process is built upon and, to the extent possible,
embodies existing processes employed by NORAD, USSPACECOM, the Canadian NDHQ,
their respective supporting/component commands/elements, and the various
agencies responsible for acquisition, test and evaluation, and support of
NORAD and USSPACECOM C2 systems.

2.1.3. Oversight of the NUICCS MSI Process by USSPACECOM/J4-j6 is a top-level
staff activity. Such oversight is not intended to supplant existing staff
functions, and will conform to the requirements and acquisition policies and
procedures delineated in Defense Acquisitions (DOD Directive 5000.1), Defense
Acquisition Management Policies and Procedures (DOD Instruction 5000.2), NORAD
Mission Need Statement (NORAD regulation 57-1), Operational Requirements
System (USSPACECOM regulation 57-1), Processing Operational Requirements
(USSPACECOM HOI 57-1), and Communications-Computer Systems Requirements
Document Processing (USSPACECOM regulation 700-1). An overview of said
procedures and the NUICCS MSI Process interaction therewith is contained in
attachment 3. Figure 2.1, NUICCS MSI Checkpoint Interaction with Other
Processes, provides a pictorial representation of the relationship between the
NUICCS MSI Process and the regulatory procedures/processes described in the
references above. Canadian participation in the NUICCS MSI Process will be
guided by the Memorandum of Understanding between the Canadian National
Defence Headquarters (NDHQ) and NORAD.

2.1.4. The NUICCS MSI Process implements direction provided in JCS
Publication 0-2, Unified Action Armed Forces (UNAAF), which directs CINCs to
provide direction to assigned subordinate commands to ensure interoperability
of command-wide C2 and intelligence systems essential to assigned operational
functions.

2.1.5. The NUICCS MSI Process identifies key integration responsibilities,
checkpoints, controls, and actions associated with implementation of new
acquisitions, maintenance, evolution and modernization of C2 systems,
subsystems, and system elements for the lifetime of such systems.

2.1.5.1. Elements of the NUICCS MSI Process may be tailored to meet the
specific needs of individual programs or national needs of individual
countries, subject to the approval of the USSPACECOM/J4-j6.

2.1.5.2 The NUICCS MSI Process may be tailored as necessary to accommodate
the requirements of highly sensitive classified programs or system interfaces,
subject to the approval of the USSPACECOM/j4-j6.

NUR 102-1 11 March 1992 7

2.2. NUICCS impact Criteria. The addition of new equipment or software, or
modifications to existing equipment or software must be assessed for impacts
on NUICCS as a whole. NORAD Mission Need Statements (N-MNSs) , Mission Need
Statements (MNSs), Operational Requirement Documents (ORDs), Interface Control
Documentation (ICDs), specifications, and other documentation meeting the
NUICCS impact criteria in Figure 2.2, NUICCS Impact Criteria, are subject to
the NUICCS MSI Process.

Modifications or changes that cross mission boundaries.

Modifications or changes affecting the NUICCS technical framework.

modifications or changes affecting requirements of NUICCS or NUICCS
missions.

modifications or changes affecting architectures or operational
concepts of NUICCS or NUICCS missions.

modifications or changes affecting multiple NUICCS components or
supporting commands/agencies.

FIGURE 2.2 NUICCS IMPACT CRITERIA

2.3. MSI Process Checkpoints:

2.3.1. MSIB Information Brief. This is a briefing to the MSIB, structured to
provide information on the introduction of a new NUICCS concept or
requirement, or a proposed modification to an existing NUICCS subsystem,
system element, or interface. Its purpose is to allow the senior staff to
identify integration issues and assign integration responsibilities at the
earliest possible stage in a proposed NUICCS system change. The MSIB
Information Brief will be presented by the NORAD N-MNS or USSPACECOM MNS
project officer, or supporting/component command project officer during the
NORAD or USSPACECOM formal staffing process required by NORADR 57-1,
USSPACECOMR 57-1, USSPACECOM HOI 57-1, or USSPACECOMR 700-1. Canadian inputs
on unique requirements will be outlined in a Memorandum of Understanding
between NORAD and the Canadian Department of National Defence (DND).

2.3.2. NUICCS Concept Review. This review provides a check for compliance
with the NUICCS First Principles and the NUICCS Architecture. This review is
accomplished during the formal staffing of the N-MNS, MNS, Operational
Requirements Document (ORD), Communications-Computer System Requirement
Document (CSRD), or System Change Form (SCF) forwarded to HQ NORAD or HQ
USSPACECOM. An overview of this staffing process is contained in attachment 3,
paragraphs A3.1 and A3.4.

2.3.2.1. The review is conducted by a subpanel of the MSIB. This subpanel
will be chaired by the Deputy Director for NUICCS Policy, Architecture,
and Integration (HQ USSPACECOM J6N). Membership of the subpanel includes

8 NUR 102-1 11 March 1992

representatives from the organizations listed in Figure 2.3, NUICCS Concept
Review Subpanel Membership.

HQ NORTH AMERICAN AEROSPACE DEFENSE COMMAND (NORAD)
Directorate of Manpower and Personnel (HQ NORAD USSPACECOM/Jl)
NORAD Combat Operations Staff (J3)
NORAD Planning Staff (J5)
Directorate of Intelligence (HQ NORAD USSPACECOM/j2)
Inspector General (HQ NORAD USSPACECOM IG)

HQ UNITED STATES SPACE COMMAND (USSRACECOM)
Directorate of Operations (J3)
Deputy Directorate for NUICCS Policy, Architecture, and Integration (J6N)
Deputy Directorate for System Certification (J6C)
Deputy Directorate for Logistics (J4L)
Directorate of Plans (JS)
Joint Strategic Defense Planning Staff (JOSDEPS)
Center for Aerospace Analysis (AN)

Canadian National Defence Headquarters/DGADO

HQ Air Force Space Command (AFSPACECOM)

HQ United States Army Space Command (USARSPACE)

HQ Naval Space Command (NAVSPACECOM)

Other organizations as deemed necessary by the subpanel chair.

FIGURE 2.3 NUICCS CONCEPT REVIEW SUBPANEL LEADERSHIP

2.3.2.2. Integration issues that are developed from the review are referred
back to the appropriate agency for resolution. If the issues cannot be
resolved, the appropriate service will present options to the MSIB for
consideration. The MSIB will discuss the options, and decide on a recommended
course of action. The options and recommended course of action will then be
forwarded by the Chairman of the MSIB to the CINC for approval.

2.3.2.3. once the review is completed, and all issues resolved, the
appropriate Command, Control, Communications and Computer Systems Master Plan
(C4SMP), and other affected plans and documentation will be updated as
necessary.

2.3.3. NUICCS Technical Review. This review provides a check for compliance
with NUICCS Standards, and other standards and policy developed and
promulgated by HQ USSPACECOM. Further, it assesses program overlaps,
interfaces, and interoperability issues for new programs and existing systems.
This review is accomplished during the formal staffing of the program/system
Technical Interface specifications, ICDS, CSRDS, and SCFS. The review is
conducted by subpanels of the MSIB. The chair and membership of the subpanel


10 NUR 102-1 11 March 1992

is determined by the system/program involved. Figure 2.4, the Scope of the
MSI Process within NUICCS, shows the systems/programs in which changes would
require review by a NORAD/USSPACECOM Technical Review Subpanel or a
Responsible Agency/Component Technical Review Subpanel.

2.3.3.1. NORAD/USSPACECOM Technical Review Subpanel. This subpanel will be
chaired by the Deputy Director for Logistics (HQ USSPACECOM J4L). Membership
of the subpanel includes representatives from the organizations listed in
Figure 2.5, NORAD/USSPACECOM Technical Review Subpanel Membership.

HO NORTH AMERICAN AEROSPACE DEFENSE COMMAND (NORAD)
NORAD Combat Operations Staff (J3)
NORAD Planning Staff (J5)
Directorate of Intelligence (J2)

HQ UNITED STATES SPACE COMMAND (USSPACECOM)
Directorate of Operations (J3)
Deputy Directorate for NUICCS Policy, Architecture, and Integration (J6N)
Deputy Directorate for System Certification (J6C)
Directorate of Plans (J5)
Center for Aerospace Analysis (AN)

Canadian National Defence Headquarters/DGCEEM

HQ Air Force Space Command (AFSPACECOM)

HQ United States Army Space Command (USARSPACE)

HQ Naval Space Command (NAVSPACECOM)

Other organizations as deemed necessary by the subpanel chair.

FIGURE 2.5 NORAD/USSPACECOM TECHNICAL REVIEW SUBPANEL

2.3.3.1.2. Integration issues that are developed from the review are referred
back to the appropriate service for resolution. If the issues cannot be
resolved, the appropriate service will present options to the MSIB for
consideration. The MSIB will discuss the options, and decide on a recommended
course of action. The options and recommended course of action will then be
forwarded by the Chairman of the MSIB to the CINC for resolution.

2.3.3.1.3. once the review is completed, and all issues resolved, the NUICCS
Architecture, appropriate C4SMP, and other appropriate plans and documentation
will be updated as necessary.

2.3.3.2. Responsible Agency/Component Technical Review Subpanel. This subpanel
will be chaired by the lead responsible agency/component for the
program(3)/system(3) to be reviewed. This subpanel may be merged with other
existing responsible agency/component boards/panels with the representatives
from the organizations listed in Figure 2.6, Responsible Agency/Component

NUR 102-1 11 March 1992 11

Technical Review Subpanel membership. Results of the review will be provided
to HQ USSPACECOM/J6N.

HQ NORTH AMERICAN AEROSPACE DEFENSE COMMAND (NORAD)
NORAD Planning Staff (J5)
Directorate of Intelligence (HQ NORAD/ USSPACECOM/j2)

HQ UNITED STATES SPACE COMMAND (USSPACECOM)
Deputy Directorate for NUICCS Policy, Architecture, and Integration (J6N)
Deputy Directorate for System Certification (J6C)
Deputy Directorate for Logistics (J4L)
Directorate of Plans (J5)

Canadian National Defence Headquarters/DGCEEM

Other organizations as deemed necessary by the subpanel chair.

FIGURE 2.6 RESPONSIBLE AGENCY/COMPONENT TECHNICAL REVIEW SUBPANEL

2.3.3.2.2. If desired, a responsible agency/component can forward its
program(s)/system(s) to the NORAD/USSPACECOM Technical Review Subpanel, rather
than conduct its own technical review.

2.3.3.2.3. Integration issues that are developed from the review that cannot
be resolved will be presented by the Responsible Agency/Components to the MSIB
with options for consideration. The MSIB will discuss the options, and decide
on a recommended course of action. The options and recommended course of
action will then be forwarded by the Chairman of the MSIB to the CINC for
resolution.

2.3.3.2.4. Once the review is completed, and all issues resolved, the NUICCS
Architecture, appropriate C4SMP, and other appropriate plans and documentation
will be updated as necessary.
12 NUR 102-1 11 March 1992

Chapter 3 - Responsibilities

3.1. MSIB, as an advisory body to the Director of Command Control Systems
and Logistics (HQ USSPACECOM/J4-JG):

3.1.1. Provides oversight for the NUICCS MSI Process.

3.1.2. Resolves issues developed by the NUICCS Concept Review and NUICCS
Technical Review subpanels that cannot be resolved by appropriate staff
action.

3.1.3. Provides a forum for the discussion of technical integration issues.

3.1.4. Recommends solutions to the Director of Command Control Systems and
Logistics (HQ USSPACECOM/j4-j6) for technical integration issues that cannot
be resolved through appropriate staff action, through the MSIB or through
other appropriate forums for final resolution by CINCNORAD/USCINCSPACE.

3.2. MSIB Executive Secretariat (HQ USSPACECOM/J6N):

3.2.1. Schedules MSIB Information Briefs as requested by the NORAD staff, its
responsible agencies or supporting commands; or the USSPACECOM staff and its
component commands.

3.2.2. Publishes minutes of MSIB meetings.

3.2.3. Maintains this regulation.

3.3. NTJICCS Concept Review Subpanel:

3.3.1. Conducts concept reviews of N-MNSS, MNSS, ORDS, CSRDS, SCFS, and other
documents specified in this regulation, and in NORADR 57-1, USSPACECOMR 57-1,
USSPACECOM HOI 57-1, USSPACECOMR 700-1, or the Integrated TW/AA System
Configuration Control System Directive (CCSD), Vol I.

3.3.2. Facilitates the briefing of significant issues that arise from
integration reviews to the MSIB by requirements or concept proponent.

3.4. NUICCS Technical Review Subpanels:

3.4.1. Conduct technical reviews of ORDS, CSRDS, SCFS, Technical Interface
specifications, and other documents as specified in this regulation, and in
NORADR 57-1, USSPACECOMR 57-1, USSPACECOM HOI 57-1, USSPACECOMR 700-1, or the
Integrated TW/AA CCSD.

3.4.2. Facilitate the briefing of significant issues that arise from
integration reviews to the MSIB by requirements or concept proponent.

3.5. Directorate of Manpower and Personnel (HQ NORAD/USSPACECOM/Jl) provides a
representative to the NUICCS Concept Review Subpanel.

NUR 102-1 11 March 1992 13

3.6. NORAD Combat Operations Staff (HQ NORAD/j3):

3.6.1. Provides a representative to the NUICCS Concept Review and
NORAD/USSPACECOM Technical Review Subpanels.

3.6.2. Provides MSIB Information Briefs on new operational concepts, and
other issues/documents meeting the NUICCS impact criteria in paragraph 2.2.

3.7. NORAD Planning Staff (HQ NORAD/J5):

3.7.1. Provides a representative to the NUICCS Concept Review, and NORAD/
USSPACECOM and Responsible Agency/Component NUICCS Technical Review Subpanels.

3.7.2. Provides MSIB Information Briefs on new operational concepts,
requirements, and other issues/documents meeting the NUICCS impact criteria in
paragraph 2.2.

3.7.3. Provides N-MNSs to the NUICCS Concept Review Subpanel for review and
incorporate the results of those reviews into N-MNSS. Further, incorporate the
results of the panel review of externally generated N-MNSS, and ORDs into the
NORAD response to these documents.

3.8. Directorate of intelligence (HQ NORAD USSPACECOM/j2):

3.8.1. Provides a representative to the NUICCS Concept Review, and NORAD/
USSPACECOM and Responsible Agency/Component NUICCS Technical Review Subpanels.

3.8.2. Provides MSIB Information Briefs on new operational concepts,
requirements, and other issues/documents meeting the NUICCS impact criteria in
paragraph 2.2.

3.9. Directorate of Operations (HQ USSPACECOM/j3):

3.9.1. Provides a representative to the NUICCS Concept Review and NORAD/
USSPACECOM Technical Review Subpanels.

3.9.2. Provides MSIB Information Briefs on new operational concepts,
requirements, and other issues/documents meeting the NUICCS impact criteria in
paragraph 2.2.

3.10. Directorate of Command Control Systems and Logistics (HQ USSPACECOM/
J4-J6):

3.10.1. Chairs the Mission Systems Integration Board.

3.10.2. Provides MSIB Information Briefs on new operational concepts,
requirements, and other issues/documents meeting the NUICCS impact criteria in
paragraph 2.2.

14 NUR 102-1 11 March 1992

3.11. Deputy Directorate for NUICCS Policy, Architecture, and Integration (HQ
USSPACECOM/J6N):

3.11.1. Chairs the NUICCS Concept Review Subpanel and provide a representative
to the NORAD/USSPACECOM and Responsible Agency/Component NUICCS Technical
Review Subpanels.

3.11.2. Is responsible for, and maintains the NUICCS First Principles of
Operation, and NUICCS Architecture.

3.11.3. Develops, and maintains implementing charters for the NUICCS Concept
Review and Technical Review Subpanels.

3.11.4. Provides the MSIB Executive Secretariat.

3.11.5. Identifies CSRDs meeting the NUICCS impact criteria in paragraph 2.2
for NUICCS Concept Reviews and NUICCS Technical Reviews.

3.12. Deputy Directorate for Logistics (HQ USSPACECOM/J4L):

3.12.1. Chairs the NORAD/USSPACECOM NUICCS Technical Review Subpanel. Provide
a representative to the NUICCS Concept Review and Responsible Agency/Component
NUICCS Technical Review Subpanels.

3.12.2. Is responsible for, and maintains the NUICCS Standards, and directs
the NUICCS configuration management effort.

3.12.3. Identifies SCFs meeting the NUICCS impact criteria in paragraph 2.2
for NUICCS Concept Reviews and NUICCS Technical Reviews.

3.13. Deputy Directorate for System Certification (HQ USSPACECOM/J6C)
provides a representative to the NUICCS Concept Review, NORAD/USSPACECOM
Technical Review, and Responsible Agency/Component Technical Review Subpanels.

3.14. Directorate of Plans (HQ USSPACECOM/j5):

3.14.1. Provides a representative to the NUICCS Concept Review and the
NORAD/USSPACECOM and Responsible Agency/Component NUICCS Technical Review
Subpanels.

3.14.2. Provides MSIB Information Briefs on new operational concepts,
requirements, and other issues/documents meeting the NUICCS impact criteria in
paragraph 2.2.

3.14.3. Provides MNSS, ORDS, ICDS, specifications and other documentation
delineated in USSPACECOMR 57-1 and USSPACECOM HOI 57-1 to the NUICCS Concept
Review and NUICCS Technical Review Subpanels for review and incorporates the
results of those reviews into HQ USSPACECOM developed MNSS, or incorporates
the results of those reviews into the HQ USSPACECOM response for externally
generated MNSS, ORDs and specifications.

NUR 102-1 11 March 1992 15

3.15. Joint Strategic Defense Planning Staff (JOSDEPS):

3.15.1. Provides a representative to the NUICCS Concept Review Subpanel.

3.15.2. Provides MSIB Information Briefs on new strategic defense concepts,
requirements, assessments and other issues/documents meeting the NUICCS impact
criteria in paragraph 2.2.

3.15.3. Coordinates candidate C3 concepts for incorporation in Integrated
Strategic Defense Concept Plan (ISDCP) revisions with appropriate NUICCS
Concept Subpanel members.

3.16. Center for Aerospace Analysis (HQ USSPACECOM/AN) provides a
representative to the NUICCS Concept Review and Technical Review Subpanels.

3.17. Inspector General (HQ NORAD/USSPACECOM IG) provides a representative to
the NUICCS Concept Review Subpanel.

3.18. NORAD Responsible Agencies and USSPACECOM Component Commands:

3.18.1. Publish implementing regulations as appropriate.

3.18.2. Provide representatives to the NUICCS Concept Review and NUICCS
Technical Review Subpanels as delineated in paragraph 2.3.

3.18.3. Chair Responsible Agency/Component NUICCS Technical Review Subpanels
as delineated in paragraph 2.3.

3.18.4. Provide MSIB Information Briefs on new operational concepts,
requirements, and other issues/documents meeting the NUICCS impact criteria in
paragraph 2.2.

3.18.5. Provide MNSS, ORDS, interface control documentation, and
specifications through HQ USSPACECOM/J5 per USSPACECOMR 57-1 or NORAD/j5 in
accordance with NORAD procedures to the NUICCS Concept Review and NUICCS
Technical Review Subpanels for review.

OFFICIAL DONALD J. KUTYNA
General, USAF
Commander in Chief

MICHAEL A. KLICH
Lieutenant Colonel, USAF
Director of Information Management

16 NUR 102-1 Attachment 1 11 March 1992

SPECIAL CASES

Al.l. Integrity. As assigned by MCM-172-91, Integrity of the Integrated
TW/AA System, USCINCSPACE is responsible to manage and control the overall
integrity for the Integrated TW/AA System. Integrity is assured through the
development and application of architectures and standards; through systems
integration; through configuration control; through end-to-end integrity
tests; and through system/element testing and certification.

Al.l.l. Integrity is defined as that condition of a system that guarantees it
will perform its assigned function correctly, reliably, and within the
timeframe required by the operational mission. When more than one system
provides the same or similar results, those results must agree to the extent
that they may be interpreted by the next system(s) in the flow, or the end
user, without any ambiguity in meaning.

Al.1.1.1 Correctly is defined as: the system will produce the same exact
results each and every time the same exact inputs are provided to the system,
and those results are the operationally required and expected results.

Al.1.1.2. Reliably is defined as: the system will continue to function under
all projected loads and processing conditions, and will respond in a
predictable manner to all loads or processing conditions (exception
conditions) not projected to be encountered. All such exception processing
will be in a manner such that the assigned function or mission can be
continued with parameters established by the operational requirements.

Al.1.2. USCINCSPACE will review and approve the addition of new equipment or
software, or modifications to existing equipment or software within or
interfacing with the Integrated TW/AA System to ensure that the integrity and
operational capability of the system are maintained.

Al.1.3. Stringent direction, functions, responsibilities, and procedures
have been developed to ensure that integrity is preserved. Systems, sub-
systems, elements, etc. that are a part of, or interface with the Integrated
TW/AA System must meet the requirements for integrity.

Al.1.4. As stated by USCINCSPACE, concurred on by Chief of Staff, U.S. Air
Force, and approved by the Chairman, Joint Chiefs of Staff, in USSPACECOM
IPLAN 1-91, USCINCSPACE will ensure integrity of the Integrated TW/AA System
through:

Al.1.4.1. mission systems integration oversight (this regulation);

Al.1.4.2. the establishment of direction and guidance in technical standards
and configuration control;

Al.1.4.3. the development and application of architectures;

Al.1.4.4. system/element testing and certification;

Al.1.4.5. and system-wide integrity testing.

NUR 102-1 Attachment 1 11 March 1992 17

Al.2. System Security. With the multi-national, multi-level classification
aspects of NUICCS, the security of data handled within NUICCS must be assured.
During the acquisition phase and changes and modifications phase, equal
emphasis shall be applied across the following disciplines: Computer security
(COMPUSEC); Communications security (COMSEC); Emanations security (TEMPEST);
operations security (OPSEC); Physical security; Personnel security; and
Information security (INFOSEC).

18 NUR 102-1 Attachment 2 11 March 1992

REFERENCES

a. Charter for the Mission Systems Integration Board (MSIB), 18 September
1 9 92 .

h. DOD Directive 5000.1, Defense Acquisition, 23 February 1991.

c. DOD Instruction 5000.2, Defense Acquisition Management Policies and
Procedures, 23 February 1991.

d. NORAD Regulation 57-1, NORAD Mission Need Statement, 28 February 1992.

e. USSPACECOM Regulation 57-1, Operational Requirements System.

f. USSPACECOM HOI 57-1, Processing Operational Requirements.

g. USSPACECOM Regulation 700-1, Communications-Computer Systems Requirements
Document Processing, 20 June 1989.

h. DOD Manual 5000.2-M, Defense Acquisition Management Documentation and
Reports, 23 February 1991.

i. Integrated Tactical Warning and Attack Assessment Configuration Control
System Directive, Vol. 1, 16 Sep 1991.

j. The Memorandum of Agreement between NORAD, USSPACECOM, AFSPACECOM,
NAVSPACECOM, and USARSPACE, Concerning the Formation and Operation of the
Integrated TW/AA System Operational Integration Review Board and The
Operational Integration Working Group, 13 July 1988.

k. Joint Publication 1-02. The DOD Dictionary of Military and Associated
Terms, 1 December 1989.

1. Joint Publication 0-2. Unified Action Armed Forces (UNAAF), 1 December
1986.

M. Chairman, Joint Chiefs of Staff (CJCS) Memorandum of Policy (MOP) No. 50,
Command, Control, Communications, and Computer Systems Master Plans,
Assessments, and Evaluation, 13 December 1990.

n. NORAD Command, Control, and Communications Systems Master Plan (C3SMP),
26 July 1991.

0. USSPACECOM Command, Control, Communications, and Computer Systems Master
Plan (C4SMP), 30 September 1991.

P. MCM-172-91, Integrated TW/AA System Integrity, 01 October 1991.

q. USSPACECOM Implementation Plan for the Restructure of the Integrated TW/AA
System Executive Management and the Transfer of SIO Functions (USSPACECOM
IPLAN 1-91), 16 October 1991.

NUR 102-1 Attachment 3 11 March 1992 19

PROCESS OVERVIEWS

A3.1. Requirements Process Background and Overview:

A3.1.1. The requirements definition process is covered in directives,
instructions, manuals, regulations, and operating instructions (see attachment
2). The purpose of this section in this regulation is to give overall context
to the NUICCS MSI Process briefs and reviews described in paragraph 2.3 of
this regulation, as they relate to a major defense acquisition program
described in DODD 5000.1 and DODI 5000.2. Figure 2.1, NUICCS MSI Checkpoint
Interaction with Other Processes, of this regulation provides a pictorial
representation of the relationship between the NUICCS Integration Checkpoints,
the requirements process, and the acquisition process.

A3.1.2. Mission needs for NORAD and USSPACECOM command and control functions
are identified as a direct result of continuing assessments of current and
projected capabilities in the context of changing military threats, and
national and DOD policy. This mission area analysis can be driven by the
addition of new tasks or responsibilities through a change to the Joint
Strategic Capabilities Plan, the Unified Command Plan, the U.S./Canada Defence
Agreement, the CINCNOP-AD Terms of Reference, new identified threats, or the
development of new technologies. Mission area analysis is conducted by the
Department of Defense (DOD), DOD agencies, the unified and specified commands,
the military departments, NORAD and its supporting commands and responsible
agencies, and the USSPACECOM components.

A3.1.3. These periodic mission area analyses are necessary to identify
deficiencies that may result in a need to:

A3.1.3.1. Change doctrine, tactics, training, or organization.

A3.1.3.2. Fix shortcomings in existing materiel.

A3.1.3.3. Introduce new operational capabilities.

A3.1.3.4. Revise or develop operational concepts.

A3.1.4. Command and control needs that can be satisfied by a nonmaterial
solution are referred to the appropriate OPR for coordination and action.

A3.1.5. Command and control needs that can be satisfied by a major change or
modification to an existing system within NUICCS that does not qualify as a
major defense acquisition program (as defined in DODD 5000.1) will be
documented and coordinated in accordance with NORADR 57-1, USSPACECOMR 57-1 ,
USSPACECOM HOI 57-1, USSPACECOMR 700-1, or other applicable regulations or
instructions as appropriate. Service specific responsibilities and procedures
for performing modifications are covered in service regulations/instructions;
however, modifications which meet the impact criteria in paragraph 2.2 will be
subject to the NUICCS MSI Process described in this regulation.

A3.1.6. NUR 102-1 does not change the current DOD, NORAD, USSPACECOM or
service policies and directives for submitting requirements. The procedures

20 NUR 102-1 Attachment 3 11 March 1992

for processing NORAD N-MNSs and USSPACECOM MNSs for NUICCS or NUICCS-related
systems are contained in NORADR 57-1, USSPACECOMR 57-1 or USSPACECOM HOI 57-1,
as applicable. The interface with the NUICCS MSI Process is summarized as
follows:

A3.1.6.1. A Mission Systems integration Board (MSIB) Information Brief,
described in paragraph 2.3 of this regulation, will be given by the N-MNS or
MNS project officer or cognizant OPR during the beginning phases of the
staffing process.

A3.1.6.2. During the requirements coordination effort, the N-MNSIMNS will
undergo a NUICCS Concept Review, described in paragraph 2.3 of this
regulation.

A3.1.6.3. Upon resolution of issues from the NUICCS Concept Review and the
two letter coordination, the N-MNS or MNS is then sent to:

A3.1.6.3.1. the appropriate validation authority for validation.

A3.1.6.3.2. the Joint Requirements Oversight Council (JROC) and NDHQ for
validation (N-MNSs).

Note: Comments are sent to the originating agency for incorporation as
appropriate.

A3.1.7. As the MNS is developed, the appropriate NORAD or USSPACECOM
directorate develops or revises an Operational Concept that will further
define the operational uses of the new system or change to an existing system.

A3.1.8. After the N-MNS or MNS has been validated and a Milestone 0 decision
reached (as described in DODD 5000.1 and DODI 5000.2), the user or user
representative begins drafting an Operational Requirements Document (ORD) that
will support the most promising system concept developed during Phase 0. ORDs
are written in accordance with DODI 5000.2 using the format contained in
DODM 5000.2-M. The ORD documents objectives and minimum acceptable
requirements for operational performance of the proposed concept or system.
The ORD is the bridge connecting the N-MNS or MNS to the acquisition program
baseline and the specifications for the concept or system. ORDs for NUICCS or
NUICCS-related systems will be processed in accordance with USSPACECOMR 57-1
or USSPACECOM HOI 57-1, as applicable.

A3.1.9. During the NORAD or USSPACECOM staff review process of the ORD for
Milestone I, the ORD will receive a NTJICCS Concept Review.

A3.1.10. At Milestone IT, the ORD is updated and expanded to reflect system
definition and experience from Phase I of the acquisition process. As the ORD
undergoes the NORAD or USSPACECOM staff review process, the revised ORD will
receive a NUICCS Concept Review. These reviews will be tailored to reflect
the changes made to the ORD, and may not be as extensive as previous reviews.

A3.1.11. Upon completion of the staff review process and other reviews, the
N-MNS or MNS, and supporting ORD may require revision. The revised N-MNS, MNS

NUR 102-1 Attachment 3 11 March 1992 21

or ORD is forwarded through the NORAD or USSPACECOM staff review process, and
a NUICCS Concept Review. These reviews will be tailored to reflect the
changes made to the ORD, and may not be as extensive as previous reviews.

A3.2. Acquisition Process Background and Overview:

A3.2.1. The acquisition process is covered in directives, instructions,
manuals, regulations , and operating instructions (see attachment 2). The
purpose of this section is to give overall context to the NUICCS MSI Process
checkpoints described in paragraph 2.3 of this regulation. Figure 2. 1
provides a pictorial representation of the relationship between the NUICCS
Integration Checkpoints, the requirements process, and the acquisition
process. As stated in DoD Instruction 5000.2, user participation during
system acquisition is essential to help synchronize performance objectives in
the ORD with the acquisition program baseline. In parallel with the
acquisition process, NUICCS mission system integration checkpoints will
continue to help ensure that new and modified systems can be effectively
integrated into NUICCS with respect to command and control. The user's or user
representatives participation in each acquisition phase is essential to help
synchronize performance objectives in the ORD and the acquisition program
baseline and to keep these objectives operationally meaningful.

A3.2.2. During the normal review of specifications generated during the
acquisition process, a NUICCS Technical Review will be conducted to ensure the
specification reflects and properly interprets the NUICCS Standards as
required by USSPACECOMR 57-1, and USSPACECOM HOI 57-1.

A3.2.3. During the acquisition phase for a program, the appropriate NORAD or
USSPACECOM directorate revises the Operational Concept and or Operational Plan
(OPLAN) to further define the operational uses of the new system or change to
an existing system.

A3.3. Operational Acceptance Overview:

A3.3.1. Operational Review. This review provides periodic checks for
compliance with identified operational needs to ensure that modifications or
acquisitions are proceeding in an operationally acceptable manner.

A3.3.1.1. The review consists of normal staff actions and a review by the
Operational Integration Working Group (OIWG) for additions and or
modifications. Integration issues that are developed from the review are
referred back to the sponsor for resolution.

A3.3.1.2. If the integration issues cannot be resolved by the sponsor, they
will be presented to the Operational Integration Review Board (OIRB) or other
appropriate forum for consideration. If the issues cannot be resolved at these
forums, they will then be forwarded to the CINC with appropriate
recommendations and alternatives.

A3.3.1.3. Upon completion of the operational test and evaluation, a
Operational Review is conducted to verify the system is ready to enter an
operational verification period.

22 NUR 102-1 Attachment 3 11 March 1992

A3.3.2. At this point, the operating command of the new system or
modification becomes familiar with it, using operational techniques and
procedures to demonstrate that the system can perform its designed operational
mission. System certification (required for systems addition or modification
to the Integrated TW/AA System) is completed at the end of this period. This
period ends with the the operational approval of the modifications or changes,
or the declaration of IOC by the appropriate service.

A3.3.3. A final operational Review and NUICCS Technical Review is conducted
on any waivers or deviations to validated performance requirements to assess
system impacts and compatibility, prior to the system or modification entering
the Operations and Support phase.

A3.4. Changes and Modifications Overview:

A3.4.1. There are several classes of changes and modifications that can be
made to the NUICCS. Major modifications have the potential of re-entering the
formal acquisition process in accordance with DODD 5000.1 and DODI 5000.2.
Major modifications will be handled via the processes outlined in NORADR 57-1,
USSPACECOMR 57-1, and USSPACECOM HOI 57-1. NUICCS changes can also be made
via a Communications-Computer Systems Requirements Document (CSRD) in
accordance with USSPACECOMR 700-1. Upon approval through the Integrated TW/AA
requirements review process described in the Integrated TW/AA System
Configuration Control System Directive (CCSD), changes to the Integrated TW/AA
System can be made via a Standard Change Form (SCF).

A3.4.2. The processing of CSRDs within NORAD is coordinated through the
Deputy Directorate for Air Defense (N/J30) and the Deputy Directorate for
Requirements (N/J5R). The processing of CSRDs within USSPACECOM is managed by
the Deputy Directorate for C2 Systems Operations (J60) . The addition of new
equipment or software, or modifications to equipment or software of NUICCS by
the CSRD process will be assessed by the CSRD originator for impact on NUICCS
and forwarded for a NUICCS Technical Review as deemed necessary.

A3.4.3. The specifics for preparing and processing SCFs are contained in the
Integrated TW/AA System CCSD. SCFs that directly impact other mission areas
within NUICCS will be fully coordinated and will be subject to the review
processes contained in this regulation.

A3.4.3.1. The addition of new equipment or modifications to equipment of the
unified and specified commands, of the National Military Command System, or of
the NUICCS that is directly connected to the Integrated TW/AA System will be
coordinated with USSPACECOM/j4-j6 for review and approval of interface
engineering, technical compatibility, and technical integrity.

A3.4.3.2. Mission systems integration within the Integrated TW/AA System will
be performed in accordance with the governing documents of the Integrated
TW/AA System. modifications to the Integrated TW/AA System that directly
impact other mission areas within NUICCS will be fully coordinated and will be
subject to the review processes contained in this regulation.

NUR 102-1 Attachment 4 11 March 1992 23

DEFINITIONS

A4.1. Command and Control System. The facilities, equipment, communications,
procedures, and personnel essential to a commander for planning, directing,
and controlling operations of assigned forces pursuant to the missions
assigned,

A4.2. NORAD/USSPACECOM Integrated Command and Control System (NUICCS). NUICCS
(pronounced NEW-ICKS) is the facilities, equipment, software, communications,
procedures, and personnel, the integration of which is essential to the
Commander in Chief of NORAD and USSPACECOM for planning, directing and
controlling the operation of assigned forces pursuant to the missions
assigned. It is a worldwide, multinational, multicommand, multimission
integrated command and control system of systems.

A4.3. Integrated Tactical Warning/Attack Assessment (Integrated TW/AA) System.
The Integrated TW/AA System consists of surveillance systems targeted against
ballistic missile, atmospheric, and space threats; processing systems and
correlation nodes; information display systems; and associated communications
links to include the interface between Integrated TW/AA sensors or processors.
The Integrated TW/AA System incorporates strategic and tactical warning
information to provide warning and assessment of ballistic missile, space, and
atmospheric attacks against North America; warning of a ballistic missile or
space attack against United States interests worldwide; and warning and
assessment of attacks against United States and Allied space assets.

A4.4. Mission. A clear, concise statement of the task of the command and its
purpose. For example, NORAD's mission is to provide surveillance and control
of the airspace of Canada and the United States; provide appropriate response
against air attack; and provide warning and assessment of aerospace attack,
utilizing mutual support arrangements with other commands.

A4.5. Mission Area. An established segment of the command's mission. For
example, NORAD's three segments are Tactical Warning and Attack Assessment of
attack against North America; Air Defense of North America; and Air
Sovereignty of North America,

A4.6. Mission Area Element. A subdivision of a Mission area that describes an
operational role. For example, NORAD's mission area of Air Sovereignty of
North America is divided into Counterdrug, detection, surveillance, and
control.

A4.7. System. A composite of equipment, skills, and techniques capable of
performing and/or supporting an operational role. A complete system includes
related facilities, equipment, material, services, software, technical data,
and personnel required for its operation and support to the degree that it can
be considered a self-sufficient unit in its intended operational and/or
support environment. The system is what is employed operationally and
supported logistically.

A4.8. Subsystem. Combination of all elements (components, structures,
materials, energy sources, and interconnections) that perform a complete major

24 NUR 102-1 Attachment 4 11 March 1992

functions) and is an integral member of a system: for example, guidance
subsystem, propulsion subsystem.

A4.9. Element. Equipment, facilities, material (components, structures,
energy sources, and interconnections) that perform a functions) and is an
integral member of a system or subsystem.

A4.10. Technical integration. The process of ensuring the development or
identification of appropriate new or existing integration standards and
employing them in the acquisition, evolution, and maintenance of system
elements and subsystems. The process consists of the matching of requirement
with integration standards and specifications and assuring that system
planning, design, architectures, and development are consistent with such
standards.

A4.11. Operational Integration. The process of assuring that operational
concepts and requirements are properly defined and managed, that system or
subsystem development or modification plans and designs satisfy operational
requirements, and that training, man-machine interfaces, and other operational
factors are properly addressed in system development or modification planning
and prototyping.

A4.12. System-Level Integration. The unified and iterative approach to the
management and technical activities necessary to ensure that all parts of a
system work together. It is the combination of technical, operational '
intraprogram, and facilities integration at the system-level. The elements of
System-Level Integration may be accomplished by different agencies; however, a
single agency should have top-level responsibility for system-level
integration.

A4.13. Mission Systems Integration. The process of assuring that the
systems, subsystems and elements (e.g., Integrated TW/AA, BMD, communications,
sensors, C2 networks, etc.) of a system of systems, when technically
implemented, are cooperative, interoperable, and fully functional parts of the
entire system. Mission systems integration includes vertical integration
within individual mission areas, as well as horizontal integration across
mission areas. This process includes establishment and implementation tracking
of command principles, high-level architectures, and high level standards.

A4.14. Command and Control System Architecture. A conceptual framework
describing the characteristic physical, operational, procedural, or functional
structure of a C2 system or set of interoperating C2 systems. Architectures
are guided in their conceptual framework by mission requirements and approved
standards. A current system description provides documentation for existing
capabilities. A target system describes a capabilities goal to be achieved.
The architecture structures the transition from a current to a target system.

A4.15. Command, Control, Communications, and Computer Systems Master Plan
(C4SNP). Incorporates architectures by documenting the current and target
systems. Additionally, it assesses performance and develops objectives and a
time-phased approach in moving from current to target systems in keeping with

NUR 102-1 Attachment 4 11 March 1992 25

resource constraints. The assessment contained in the plan leads to the
identification and resolution of deficiencies.

A4.17. Major Defense Acquisition Program. An acquisition program that is not
a highly sensitive classified program and that is:

A4.17.1 Designated by the Under Secretary of Defense for Acquisition as a
major defense acquisition program, or that is estimated by the Under Secretary
of Defense for Acquisition to require:

A4.17.1.1. An eventual total expenditure for research, development, test, and
evaluation of more than $200 million in fiscal year 1980 constant dollars
(approximately $300 million in fiscal year 1990 constant dollars), or

A4.17.1.2. An eventual total expenditure for procurement of more than $1
billion in fiscal year 1980 constant dollars (approximately 1.8 billion in
fiscal year 1990 constant dollars).

A4.18. Highly Sensitive Classified Program. An acquisition special access
program established in accordance with DoD 5200.1-R, "Information Security
Program Regulation," and managed in accordance with DoD Directive 520 5 . 7,
"Special Access Program Policy".

A4.19. Nonmajor Defense Acquisition Program. A program other than a major
defense acquisition program or a highly sensitive classified program.

A4.20. Communications-Computer Systems Requirements Document (CSRD) A CSRD
documents communications-computer systems requirements for HQ NORAD and HQ
USSPACECOM expected to cost less than $25 million in one year or less than $75
million total, and does not require research and development funds (3600
funds).

A4.21. Standard Change Form (SCF). An Integrated TW/AA System standard form
for staffing and approving a proposed change to the operational Integrated
TW/AA System.

26 NUR 102-1 Attachment 5 11 March 1992

THE SCOPE OF THE NUICCS MSI Process

A5.1. The scope of the NUICCS MSI Process comprises CINCNORAD's and
USCINCSPACE's command and control system interfaces with non command and
control systems, intelligence system interfaces, the command and control
systems over which the CINC has OPCON/COCOM, and the command and control
interfaces to those facilities, equipment and communications owned and
operated by other military or commercial organizations that support assigned
NORAD and USSPACECOM missions. The NUICCS MSI Process incorporates the
interfaces to the responsible agencies/components command and control centers,
but not the internal workings of those centers.

A5.2. The NUICCS MSI Process will be concerned with those command and control
systems, subsystems, and elements that meet the criteria in paragraph A5.1,
above, necessary for the collection, processing, display, decision, and
dissemination of information to support assigned missions.

A5.3. NUICCS is a worldwide, multinational, multicommand, multimission,
integrated command and control system that supports the missions of NORAD and
USSPACECOM. At present, Canada supports only that portion of NUICCS that
directly supports the NORAD mission. The NUICCS hierarchy of mission areas,
mission area functional tasks, and NUICCS elements are shown in Figure A5-1,
NUICCS Hierarchy.

A5.3.1. Mission Areas supported by NUICCS. The mission of NORAD (and
therefore the mission supported by Canada) is divided into three mission areas
Tactical Warning and Attack Assessment of attack against North America; Air
Defense of North America; and Air Sovereignty of North America. The primary
mission of USSPACECOM is divided into four mission areas: Force Enhancement;
Force Application; Space Control; and Space Support.

A5.3.2. Mission Area Elements supported by NUICCS. The seven mission areas
cited above are subdivided into the following Mission area elements.

A5.3.2.1. Integrated Tactical Warning and Attack Assessment: Missile, air,
and space.

A5.3.2.2. Air Defense: Appropriate response and damage limitation.

A5.3.2.3. Air Sovereignty: Counterdrug, detection, surveillance, and control.

A5.3.2.4. Force Enhancement: Communication, navigation, intelligence and
surveillance, environmental monitoring, warning processing and dissemination,
mapping, charting and geodesy.

A5.3.2.5. Force Application: Ballistic Missile Defense (BMD), aerospace
defense, and power projection from space using space and space related
weapons.

A5.3.2.6. Space Control: Surveillance of space, protection, and negation.

NUR 102-1 Attachment 5 11 March 1992 27

A5.3.2.7. Space Support: Launch, orbit transfer, recovery, and satellite
control.

A5.3. Systems, subsystems, and elements supported by NUICCS. Due to the
binational, multicommand aspects of NORAD; and the multinational, multicommand
aspects of USSPACECOM, many of the systems, subsystems, and elements supported
by NUICCS support several missions and mission areas. These are characterized
by command centers, operations centers, processing centers and systems, data
sources, communications systems, and engagements nodes.

For example, the Space Surveillance Network (SSN) provides information in support of
the Integrated TW/AA and Space Control mission areas as shown in Figure A5-1,
NUICCS Hierarchy.

FIGURE A5.1 NUICCS HIERARCHY

28 NUR 102-1 Attachment 6 11 March 1992

ACRONYMS

ACE Air Control Element
ADOC Air Defense Operations Center
A-ADOC Alternate Air Defense operations Center
AFSCN Air Force Satellite Control Network
AFSPOC Air Force Space Command Center
AMWC Alternate Missile Warning Center
ASEN Alternate Space Engagement Node
ASPADOC Alternate Space Defense Operations Center
ASSC Alternate Space Surveillance Center
ARSPOC Army Space Operations Center
AWACS Airborne Warning and Air Control System

BCC Battery Control Center
BMDOC Ballistic Missile Defense Operations Center
BMEWS Ballistic Missile Early Warning System
BP Brilliant Pebbles
BE Brilliant Eyes

CCC Consolidated Command Center
CCPDS-R Command Center Processing and Display System Replacement
CIC Consolidated Intelligence Center
CINCNORAD Commander in Chief, NORAD
COCOM Combatant Command
CSOC Consolidated Satellite operations Center
CSRD Communications-Computer Systems Requirements
CSTC Consolidated Space Test Center
C4SMP Command, Control, Communications, and Computer Systems Master Plan

DSCS Defense Satellite Communications System
DMSP Defense Meteorological Satellite Program
DSP Defense Support Program

EOC Element Operations Center
E2I Exo/Endo Atmospheric Interceptor

FLTSATCOM Fleet Satellite Communications

GBI Ground Based Interceptor
GBR-T Ground Based Radar - Terminal
GPS Global Positioning System
GSTS Ground Surveillance and Tracking System

IOC Intelligence Operations Center
ISCS Integrated Satellite Control System

JROC Joint Requirements oversight Council

MCCC Mobile Consolidated Command Center
MCC Mobile Control Center
MCE Mission Control Element

NUR 102-1 Attachment 6 11 March 1992 29

MGS Mobile Ground Segment
MNS Mission Need Statement
MSI Mission Systems Integration
MSIB Mission Systems Integration Board
MWC missile Warning Center

NDHQ National Defence Headquarters
NAVSPASUR Naval space Surveillance (System)
NAVSPOC Naval Space Operations Center
NAVSOC Naval Satellite Operations Center
N-MNS NORAD Mission Need Statement
NORTIC NORAD Technical Intelligence Center
NSSOC NAVSPASUR Operations Center
NUICCS NORAD/USSPACECOM Integrated Command and Control System

OPCON Operational Control
ORD Operational Requirements Document
OTH-B over-the-horizon Backscatter (RADAR)

PDS Processing and Display System

RGF Regional Ground Facility
ROCC Regional Operations Control Center
ROC Regional Operations Center
RSSC Regional Space Support Center

SCF Systems Change Form
SCIS Survivable Communications Integration System
SPADOC Space Defense Operations Center
SPACC Space Command Center
SOCC Sector Operations Control Center
SSC Space Surveillance Center
SEN Space Engagement Node
SSN Space Surveillance Network

TSSC Theater Space Support Center
TW/AA Tactical Warning and Attack Assessment