DTIC ADA260575: U.S. Marine Corps MTACCS/Copernicus Integration

54 Pages·2.9 MB·English

by  Defense Technical Information Center

U *So M R NE--RS
P.-I.NTEGRAEIO
AIM
fI prvdfrpbi ees;dsrbto sulmtd
Technical Document 2359
January 1993
U.S. Marine Corps
MTACCS/COPERNICUS INTEGRATION
I
932 2 (93-01972 93U I1111
I
NAVAL COMMAND, CONTROL AND
OCEAN SURVEILLANCE CENTER
RDT&E DIVISION
San Diego, California 92152-5000
J. D. FONTANA, CAPT, USN R.T. SHEARER m
!
Commanding Officer Executive Director
I
ADMINISTRATIVE INFORMATION
S
This study, performed during fiscal year 1992, was funded by the
Amphibious Warfare Technology Directorate of the Marine Corps Systems
Command to identify architectural/technical issues associated with integrating
components of Marine Corps C4I systems into the Navy's Copernicus architecture.
The work was performed under the direction of Chuck Mirabile (Code 405) of the
Naval Command, Control and Ocean Surveillance Center's RDT&E Division
(NRaD), San Diego, California 92152-5000.
The authors are
"* John Flynn (Code 461)
"* Denny Mattison (Code 742)
"• Roger MerK (Code 827)
Released by Under authority of
Chuck Mirabile, Program Manager V. J. Monteleon, Head
Space and Electronic Space and Electronic
Warfare (SEW) and Warfare (SEW) and
Copernicus Office Copernicus Office
I
I
i
RBT
a
FOREWORD
BACKGROUND
The Naval Command, Control and Ocean Surveillance Center's RDT&E Division
(NRaD) supports the Marine Corps through the Battlefield Electronic Support Technology
Program. The principal objective of this program is to enable the Marine Corps to develop
technology leading to high-performance, portable Command, Control, Communications
and Intelligence (C31) systems.
OVERALL OBJECTIVES
In the 3900/AW/4 Feb 92 letter from the Marine Corps Research, Development and
Acquisition Command (now the Marine Corps Systems Command), tasking was given to
NRaD's Copernicus program office. Subsequent meetings between NRaD and the Sys-
tems Command resulted in the following specific tasks addressed in this report:
Identify architectural/technical issues associated with-and, when possible, provide
solution/options for-
1. The Marine Air-Ground Task Force (MAGTF) Command Element (CE) to
function as a Tactical Command Center (TCC) within the Navy's Copernicus
architecture.
2. A shipboard interface between the Marine Tactical Command and Control Sys-
tem (MTACCS) and the Navy Tactical Command System-Afloat (NTCS-A)
C31 system.
3. Use of "Communications Support System (CSS)-like" architecture and technol-
ogy to support the communications resource-allocation requirements of a
MAGTF CE ashore.
Note that the systems and concepts discussed here (Copernicus, NTCS-A, et al.) will
likely be subject to significant changes over time, particularly in this present environment
of budgetary constraint and changing threats. For this reason, some of the assumptions
made in this document about these programs are "best guesses," and issues/solutions
based on them may have to be modified in the future. Acs.a lo-
GNUI
I LI
DTIC QUALITY INSPECTED 3 !
__
Di
A
SCOPE/DOCUMENT STRUCTURE
As indicated by the task objectives just described, the treatment of the elements cov-
ered in this report varies from considering near-term solution/options to an existing com-
munications problem-to a very much more theoretical identification of issues associated
with treating the MAGTF CE as a TCC in Copernicus.
To accommodate this variation and the differing operational context of each task, this
report addresses the task elements in the following order:
1. MTACCS/NTCS-A Shipboard Interface (Section 1)
1
2. MAGTF CE to Function as a TCC (Section 2)
3. "CSS" to Support MAGTF CE Ashore (Section 3) -
Recommendations and conclusions are provided separately for each task element at 3
the end of each section.
Appendix A provides a succinct description of the Navy-developed C31 systems men-
tioned in this report, Appendix B presents an overview of Copernicus and its relationship
with MTACCS, and Appendix C lists some CSS-related terms and definitions.
I
I
S
I
I
I
I
a
!
ii !1
i
CONTENTS
1. MTACCS/NTCS-A SHIPBOARD INTERFACE TASK ............... 1-1
1.1 ARCHITECTURAL LAYOUT .............................. 1-1
1.1.1 Operational Context ................................ 1-1
1.1.2 NTCS-A Configuration (See Appendix A.) ............. 1-2
1.1.3 Special MTACCS Configuration ...................... 1-3
1.1.4 Other Concerns About Architecture ................... 1-3
1.1.5 Architectural Layout ................................ 1-4
1.2 TASK ANALYSIS/ISSUES IDENTIFIED ..................... 1-6
1.2.1 Information Requirements Between CATF/CLF in
Shipboard Environment .............................. 1-6
1.2.2 Issues Associated With Meeting Requirements .......... 1-6
1.3 CONCLUSIONS AND RECOMMENDATIONS ................ 1-7
2. MARINE AIR-GROUND TASK FORCE COMMAND ELEMENT
AS A TACTICAL COMMAND CENTER ......................... 2-1
2.1 TASK DESCRIPTION ..................................... 2-1
2.1.1 Operational Context of Task ......................... 2-1
2.1.2 Baseline MTACCS Configuration (MCTCA-Midterm) ..... 2-2
2.1.3 Detailed Task Description ............................ 2-2
2.1.4 Copernicus Pillars .................................. 2-2
2.1.5 Comparison of C2MP/MTACCS and Copernicus ......... 2-3
2.2 TASK ANALYSIS/ISSUES IDENTIFIED ..................... 2-6
2.2.1 GLOBIX Sources/Information ......................... 2-6
2.2.2 TADIXS Issues ..................................... 2-7
2.2.3 Afloat Support and Transition to Ashore ............... 2-8
2.2.4 Organic/Nonorganic Bearer Services ................... 2-8
2.2.5 Prioritization of Voice-Media Communications .......... 2-8
2.2.6 Standards ......................................... 2-9
2.3 OPTIONS/RECOMMENDATIONS ........................... 2-9
2.4 DEVELOPMENT OF MAGTF-TCC PROTOTYPE ............. 2-14
3. CSS TO SUPPORT MAGTF-CE ASHORE ........................ 3-1
3.1 TASK DESCRIPTION ..................................... 3-1
3.1.1 Operational Context of Task ......................... 3-1
3.1.1.1 Types of MAGTF ............................ 3-1
3.1.1.2 M EU ....................................... 3-1
1111.
3.1.1.3 ME B ....................................... 3-2
3.1.1.4 M EF ....................................... 3-2
3.1.2 Baseline MAGTF-CE Configuration .................... 3-4
3.1.3 CSS/SCE Specification .............................. 3-5
3.1.4 CSS Functional Description .......................... 3-6
3.2 POTENTIAL ARCHITECTURAL DESIGNS .................. 3-7
3.3 ISSU ES ................................................. 3-8
3.4 RECOMMENDATIONS ................................... 3-8
3.4.1 Copernicus Architecture for the Common Evolution of
Navy and Marine Corps Record-Message Traffic
Delivery System s ................................... 3-9
APPENDICES
A: NAVY-DEVELOPED C31 SYSTEMS ......................... A-1
B: OVERVIEW OF COPERNICUS ARCHITECTURE .............. B-1
C: CSS TERMS AND DEFINITIONS ............................ C-1
FIGURES
1-1 MTACCS/NTCS-A interface .................................... 1-1
1-2 NTCS-A hardware configuration, LHD ........................... 1-2
1-3 NTCS-A hardware configuration, LHA ........................... 1-3
1-4 Elements of MTACCS running as applications on four-layered
structure ..................................................... 1-4
1-5 Gateway concept for interface shipboard ......................... 1-5
1-6 OSI reference model .......................................... 1-8
2-1 Operational context of the task ................................. 2-1
2-2 MAGTF architecture under Copernicus ........................... 2-2
2-3 CINC Command Center and MAGTF-TCC connectivity ............. 2-6
2-4 Existing GLOBIXS B .......................................... 2-15
2-5 LANTFLT USMC to GLOBIXS-WAN connectivity ................. 2-16
2-6 Candidate PACFLT USMC MAGTF-TCC prototype development ..... 2-17
2-7 MAGTF-TCC connectivity ...................................... 2-19
2-8 MAGTF-MTACCS architecture .................................. 2-19
Ii
iv
I
3-1 Communications Support System (CSS)/Standard
Communications Environment (SCE) ............................. 3-7
3-2 CSS MAGTF-CE LAN configuration............................3-8
3-3 Automated Network Control Center (ANCC) at NCTAMS
EASTPAC ................................................... 3-10
TABLES
1-1 MTACCS/NTCS-A interface, issues and recommendations .......... 1-9
V
1
1. MTACCS/NTCS-A
SHIPBOARD INTERFACE TASK
1.1 ARCHITECTURAL LAYOUT
1.1.1 Operational Context
Amphibious operations are acknowledged to be among the most complex and difficult of
military operations. To be successfully accomplished, an ongoing dialogue must exist
between the Marine Air-Ground Task Force (MAGTF) Command Element (CE) and the
Navy's Command Element represented by the Commander, Amphibious Task Force
(CATF) throughout the entire assault operation. The requisite information and data-
exchange requirements and resources will clearly vary during the phases of the operation.
While both the Commander, Landing Force (CLF) and the CATF are embarked, prior to
the start of an assault, the communications and data-exchange requirements between the
Navy and the Marine Corps must be identified. Once identified, many or all of these
requirements could be accommodated by an interface between the Marine Corps'
MTACCS and the Navy's NTCS-A systems. This section addresses this interface (fig-
ure 1-1) and the architectural and/or technical issues associated with it.
C2 FOR OTH ASSAULT
ATF/LF INTERCONNECTIVITY
CATP LAN
(NTCS-A)
CLF LAN
(MTACCS)
Figure 1-1. MTACCS/NTCS-A interface.
1-1
I
3
1.1.2 NTCS-A Configuration (See Appendix A.)
The NTCS-A hardware configurations in figures 1-2 and 1-3, taken from the NTCS-A
j
Program Handbook of 21 October 1991, reflected current planning for amphibious assault
(LHA/LHD) ship equipment locations and are the system architectures considered in this
I
study. (These figures illustrate the density of the hardware in the two configurations.) The
following list comprises the Navy Tactical Command Systems-Afloat (NTCS-A) stan-
dards that are assumed with these architectures and that define the system's "Common
Operating Environment" are
Operating System UNIX (POSIX)
3
Database RDBMS, SQL
Languages C, Ada II
Local Area Network Ethernet 802.3
5
Protocols TCP/IP (GOSIP)
Graph•ics A GKS, PHIGS C. ..
YN
I
Man-Machine Interface X-WINDOWS (MOTIF)
OCIPI
I
1-2
Fiurs12 NTwCS- a rdw r cofiurtin LLSD
gas
FLT Ws op 1-2