Communications and Information Systems · ground task force (MAGTF) command and control. ... Communications and Information Systems 1001 Command and Control Environment 1-1 ... 2103

Communicationsand

Information Systems

MCWP 6-22

U.S. Marine Corps

PCN: 143 00042 00

Unless otherwise stated, whenever the masculine or feminine gender is used,both men and women are included.

To Our Readers

Changes: Readers of this publication are encouraged to submit suggestions andchanges that will improve it. Recommendations may be sent directly to CommandingGeneral, Marine Corps Combat Development Command, Doctrine Division (C 42),3300 Russell Road, Suite 318A, Quantico, VA 22134-5021 or by fax to 703-784-2917(DSN 278-2917) or by E-mail to smb@doctrine div@mccdc. Recommendationsshould include the following information:

• Location of changePublication number and titleCurrent page numberParagraph number (if applicable)Line numberFigure or table number (if applicable)

• Nature of changeAdd, deleteProposed new text, preferably double-spaced and typewritten

• Justification and/or source of change

Additional copies: A printed copy of this publication may be obtained from MarineCorps Logistics Base, Albany, GA 31704-5001, by following the instructions in MCBul5600, Marine Corps Doctrinal Publications Status. An electronic copy may be obtainedfrom the Doctrine Division, MCCDC, world wide web home page which is found at the fol-lowing universal reference locator: http://www.doctrine.quantico.usmc.mil.

DEPARTMENT OF THE NAVYHeadquarters United States Marine Corps

Washington, DC 20380-1775

16 November 1998

FOREWORD

Marine Corps Warfighting Publication (MCWP) 6-22, Communications and Infor-mation Systems, presents doctrine, tactics, techniques, and procedures (TTP) for theemployment of communications and information systems to support Marine air-ground task force (MAGTF) command and control. It builds on the underlyingapproach to command and control described in Marine Corps Doctrinal Publica-tion (MCDP) 6, Command and Control, and supports the basic warfighting philoso-phy of the Marine Corps as presented in MCDP 1, Warfighting. MCWP 6-22emphasizes the relationship between effective employment of communications andinformation systems and effective command and control, which leads ultimately tosuccess on the modern battlefield.

MCWP 6-22 provides guidance to communications and information systems (CIS)personnel (officer and enlisted) in planning, installing, operating, and maintainingcommunications networks and interfacing information systems to those networks.It also provides guidance for commanders and their staffs, who are the users ofMAGTF communications and information systems. MCWP 6-22 does not providedetailed instructions on the use of any single item of equipment or system, butrather provides a broad understanding of how communications and informationsystems are used to support command and control.

MCWP 6-22 addresses the planning and employment of information systems aswell as communications systems. This publication describes the integration of thepreviously separate functional areas of communications and data processing andemphasizes the rapidly changing nature of information technology and the com-mand and control environment. In this regard, it addresses the impact on the MarineCorps of both the Global Command and Control System (GCCS) and the DefenseInformation Systems Network (DISN). MCWP 6-22 is intended to be read by allMarines involved in the command and control process, whether as users of infor-mation or as operators of communications and information systems.

Substantial developmental efforts are underway throughout the Marine Corps com-mand and control doctrinal hierarchy. The target date for completion of all new andrevised command and control series doctrinal publications is the summer of 1999.Pending completion of this task, in the event of terminology, conceptual, opera-tional, or other conflicts between MCWP 6-22 and other FMFM’s, MCWP 6-22takes precedence.

This publication supersedes Fleet Marine Force Manual (FMFM) 3-30, Communi-cations, dated 3 April 1989.

Reviewed and approved this date.

BY DIRECTION OF THE COMMANDANT OF THE MARINE CORPS

J. E. RHODESLieutenant General, U.S. Marine Corps

Commanding GeneralMarine Corps Combat Development Command

DISTRIBUTION: 143 000042 00

iii

Communications and Information Systems

Table of Contents

Page

Chapter 1 Command and Control andCommunications and Information Systems

1001 Command and Control Environment 1-11002 Information Management 1-21003 CIS Characteristics 1-61004 CIS Responsibilities 1-7

Chapter 2 Organizations

Section I USMC Organizations

2101 Operating Forces 2-12102 Marine Corps Forces 2-12103 Marine Air-Ground Task Forces 2-22104 Marine Corps Forces Reserves 2-42105 The Supporting Establishment 2-4

Section II CIS Organizations

2201 Communication Battalion 2-52202 Marine Wing Communication Squadron 2-72203 Communications Company, HQ Battalion, Marine Division 2-82204 Communications Company, HQ and Service Battalion, FSSG 2-82205 Communications Platoons, Branches, and Sections 2-92206 Special Security Communications Elements and Teams 2-92207 Amphibious Squadron Deployment Teams 2-10

Section III C2 Organizations

2301 MEF CE 2-112302 Ground Combat Element 2-122303 Aviation Combat Element 2-132304 CSSE 2-152305 Intelligence Command and Control 2-162306 Fire Support Centers 2-172307 Rear Area Operations Centers 2-172308 CIS Control 2-182309 Amphibious C2 Facilities 2-202310 Mobile CPs 2-21

____________________________________________________________________________________________________ MCWP 6-22

iv

Chapter 3 Information Systems and Services

Section I Defense Information Infrastructure Common Operating Environment

3101 Mission Applications 3-13102 Services 3-1

Section II Global Command and Control System

3201 Background 3-33202 Description 3-43203 Joint Operation Planning and Execution System 3-43204 Global Reconnaissance Information System 3-43205 Evacuation System 3-53206 Fuel Resources Analysis System 3-53207 Global Status of Resources and Training System 3-53208 Theater Analysis and Replanning Graphical Execution Toolkit 3-53209 Joint Deployable Intelligence Support System (JDISS) 3-53210 ATO 3-63211 JMCIS 3-6

Section III MAGTF C4I

3301 Migration Strategy 3-73302 MAGTF C4I Software Baseline Capabilities 3-73303 Hardware/Operating System Requirements 3-73304 Maneuver 3-103305 Intelligence 3-103306 Air Operations 3-123307 Fire Support 3-133308 Logistics 3-143309 Force Deployment Planning 3-15

Section IV The Defense Message System

3401 AUTODIN 3-173402 Upgrades 3-17

Section V Information Services

3501 Directory Services 3-183502 Terminal Emulation Services 3-183503 Message Handling Services 3-183504 Network Management Services 3-183505 Security Services 3-193506 Facsimile Services 3-203507 Communications Services 3-20

Communications and Information Systems __________________________________________________________________

v

Section VI Shipboard Information Systems

3601 Key Resources 3-213602 JMCIS-Afloat 3-21

Chapter 4 Defense Information Systems Network

4001 Tactical Entry Points 4-14002 DISN STEP Services 4-24003 STEP Access 4-34004 Changes to DISN STEP Sites 4-44005 USMC Network Operations Center 4-4

Chapter 5 MAGTF Tactical Communications Network

Section I Overview

5101 Architecture 5-15102 Challenges 5-1

Section II Single Channel Radio

5201 HF Radio 5-45202 VHF Radio 5-45203 UHF Radio 5-55204 EPLRS 5-65205 UHF-TACSAT 5-65206 Commercial International Maritime Satellite 5-85207 Data Communications 5-8

Section III Local Area Networks

5301 LAN Media 5-105302 LAN Topologies 5-115303 Access Methods 5-14

Section IV Switched Backbone

5401 Tri-Services Tactical System 5-165402 Switches 5-175403 Global Block Numbering Plan 5-215404 IP Routers 5-215405 Multichannel Radios 5-24

Section V Special Purpose Systems

5501 PLRS 5-355502 Precision Lightweight GPS Receiver (PLGR) 5-355503 JTIDS 5-355504 Integrated Broadcast Services 5-365505 Commander’s Tactical Terminal 5-36

____________________________________________________________________________________________________ MCWP 6-22

vi

5506 The Joint Tactical Terminal 5-365507 TROJAN SPIRIT II 5-365508 Global Broadcast System 5-375509 JTF Enabler Module 5-37

Chapter 6 Planning and Execution

Section I Overview

6101 Planning Information 6-26102 Coordination 6-26103 Security 6-26104 Estimates 6-36105 Recommendations 6-36106 Preparing Plans 6-36107 Implementing Plans 6-3

Section II CIS Requirements

6201 Mission 6-46202 Courses of Action 6-46203 Concept of Operations 6-46204 Task Organization 6-46205 Available Resources 6-56206 Enemy Situation 6-56207 Environment 6-66208 Information Management Plan 6-6

Section III Pre-Deployment Preparation

6301 Review Existing Plans and Orders 6-86302 Prepare Troop and Equipment Lists 6-86303 Request Augmentation 6-86304 Coordinate Frequencies 6-86305 Request Satellite Access 6-86306 Compile a Publications Library 6-86307 Initiate Telecommunications Service Requests 6-96308 Conduct Communications/Command Post Exercises 6-96309 Provide CIS Support for Embarkation 6-96310 Submit Communications Guard Shifts 6-96311 Request COMSEC Material 6-96312 Coordinate Logistics 6-96313 Effect Liaison/Coordination 6-10

Section IV CIS Plans, Orders, and Directives

6401 Standing Operating Procedure 6-116402 CEOI 6-136403 CIS Plan 6-146404 CIS Estimate 6-146405 CIS Concept 6-14

Communications and Information Systems __________________________________________________________________

vii

6406 Paragraph 5 of the OPLAN/OPORD 6-156407 Annex K (CIS Annex) 6-16

Section V Communications Control

6501 Phases 6-176502 Responsibilities 6-186503 Functional Areas 6-18

Section VI System Planning and Engineering

6601 Functions 6-206602 Responsibilities 6-206603 Automated Tools 6-26

Section VII SYSCON

6701 Functions 6-296702 Staff Responsibilities 6-296703 OSCC Responsibilities 6-31

Section VIII TECHCON

6801 Functions 6-326802 Responsibilities 6-32

Chapter 7 Information Systems Security

Section I Communications Security

7101 Responsibilities 7-27102 Cryptosecurity 7-37103 Transmission Security 7-37104 Emission Security 7-47105 Physical Security 7-4

Section II Computer Security

7201 The Threat 7-67202 Protection 7-7

Section III Incident Response

7301 The Fleet Information Warfare Center 7-97302 Naval INFOSEC Help Desk 7-97303 The Air Force Information Warfare Center 7-107304 Points of Contact 7-10

____________________________________________________________________________________________________ MCWP 6-22

viii

Chapter 8 Future Directions

8001 Operational Maneuver From the Sea 8-18002 CIS Requirements 8-2

Appendices:

A Defense Information Infrastructure Common Operating Environment Compliance A-1B Common Hardware and Standard Commercial Software Applications B-1C Ship Visit Checklist C-1D MAGTF Radio Nets D-1E Information Systems Directory E-1F CIS Planning Checklist F-1G Unit Planning Checklist G-1H Data Communications Network and Information Systems Planning Checklist H-1I Communications and Information Systems Estimate I-1J Sample CIS Annex (Annex K) J-1K CIS Threat Assessment Planning Checklist K-1L Emission Classification and Designation L-1M Sample Guard Charts M-1N Points of Contact N-1O Glossary O-1P References and Related Publications P-1

Chapter 1

Command and Controland

Communications and Information Systems

MCWP 6-22 outlines the responsibilities of CISpersonnel and CIS users to ensure that those sys-tems provide effective command and control (C2)support. MCWP 6-22 is written, to the extent pos-sible, in nontechnical language. However,chapters 3, 4, and 5 contain many computer net-working and communications terms that may beunfamiliar to most Marines. These terms are de-fined in appendix O.

MCWP 6-22 focuses on the CIS used to supportthe MAGTF in the operational environment. It ad-dresses CIS employment in support of the MarineCorps component headquarters and how theMarine Corps organizes to provide CIS support tothe MAGTF. It describes the information systemsand services that support MAGTF C2 and the em-ployment of communications systems andnetworks to link these information systems.

This publication emphasizes the impact of therapidly evolving joint C2 environment on MarineCorps CIS. Key planning considerations, guide-lines, and procedures are presented. CIS operationis then discussed in terms of system planning andengineering, operational systems control (SY-SCON), and technical control (TECHCON)followed by information security (INFOSEC) andcommunications security (COMSEC). MCWP 6-22 concludes with a discussion of future CISconcepts.

1001. Command and Control Environment

The C2 environment is characterized by rapidchange and continuous challenge. Implementationof maneuver warfare doctrine, with its emphasis

on speed and tempo, demands compressed plan-ning, decision, execution and assessment cycles.At the same time, the volume of information thatneeds to be processed and analyzed to support de-cisionmaking is exploding, and this informationoverload threatens to overwhelm the commanderand his staff. The MAGTF must employ limitedCIS resources to meet these challenges. To helpsatisfy the operational requirement, the MarineCorps is changing its manpower structure and itseducation and training processes as well as itsdoctrine through the combat development pro-cess. Changes are based on integrating thepreviously separate functional areas of communi-cations and data processing into a singlefunctional area with responsibilities for both in-formation processing and information exchange.This merger will position the Marine Corps totake full advantage of advances in informationtechnology to meet C2 requirements.

Developments in the joint C2 arena are anothersignificant factor in the C2 environment. The De-partment of Defense (DOD) is significantlyenhancing the C2 capabilities of the armed forcesby rapid exploitation of advanced informationtechnologies and significant improvements in in-teroperability. These accomplishments are largelythe result of the implementation of the Defense In-formation Systems Network (DISN) and theGCCS and the associated Joint Technical Archi-tecture standards. The DISN is an integration ofDOD communications systems and networks un-der the management control of the DefenseInformation Systems Agency (DISA). The ulti-mate goal of DISN is to provide a single,integrated, common-user, global communicationsnetwork that supports all echelons, strategicthrough tactical. Similarly, the GCCS is designedto replace incompatible Service-unique C2

1-2 ________________________________________________________________________________________________ MCWP 6-22

systems with a single, integrated C2 system. Im-plementation of GCCS will ensure interoperabilityamong forces and provide a common operationalpicture and a common set of decision support toolsfor all components of the joint task force (JTF).Through communications connectivity providedby the DISN, GCCS will support the planning, de-ployment, employment, sustainment , andredeployment of joint forces worldwide. It will besome years before the DISN and GCCS are fullyimplemented. However, GCCS and DISN, as dis-cussed in chapters 3 and 4, are already having amajor impact on the employment of Marine CorpsCIS.

One of the most difficult C2 issues currently fac-ing the Marine Corps is the requirement tosupport a deployable Marine component HQ withCIS personnel and equipment. The primarysource of support is the communications battal-ion. The requirement to provide support to adeployed Marine component HQ can have a sig-nificant effect on the availability of CIS resourcesto support the MAGTF. Resources required tosupport a component HQ is the subject of ongoingstudy and will be addressed by the next ForceStructure Planning Group.

CIS must be able to satisfy the C2 requirements ofthe expeditionary battlefield. CIS must provideMAGTF commanders and their staffs with thetools necessary to rapidly collect, process, ana-lyze, and exchange information in support ofoperations planning and execution. These systemsmust make available the information needed,when it is needed, wherever it is needed on thebattlefield. Employment of these systems mustnot adversely affect the freedom of action andmobility of the MAGTF. They must be reliable,flexible, and responsive. The success of theMAGTF on the modern battlefield depends on de-signing, planning, and employing CIS that satisfythe information needs of the MAGTF C2 process.

1002. Information Management

Much of the information obtained for any endeav-or or purpose is contradictory. This is especially

true in a battle of wills between opposing forcesin military or political conflicts in which each sideseeks to deceive the other with false information.The commander cannot, therefore, be certain thatthe information obtained depicts the situationwith absolute certainty, only that it provides anapproximation of reality. Generally, the com-mander’s approximation of reality can beincreased with more time to collect and analyzeadditional information. However, reality alsochanges with time because of enemy and friendlyactions and the environment. These changes thenintroduce additional information that requires pro-cessing and analysis . At some point , thecommander must make decisions based on thebest information available. Although CIS provideuseful tools, the application of sound informationmanagement principles is required to satisfy thecommander’s information requirements.

a. Information Quality

Information quality and availability have a directeffect on the commander’s capability to effective-ly C2 forces. Good information reduces confusionand contributes to situational awareness. Good in-formation is essential for effectively planning,monitoring, and influencing operations. Informa-tion quality cannot be taken for granted and mustbe assessed with care.

The following criteria are by no means all-inclu-sive, nor are they independent or all of equalimportance. It is counterproductive to seek com-plete information if the search for completenessmakes the information untimely. Irrelevant infor-mation is worse than no information, and falseinformation can be disastrous, especially if it ispart of an enemy deception.

(1) Relevance. Information must apply to themission, task, or situation. Exhaustive informa-tion provided without filtering often detracts fromrather than enhances the commander’s ability tomake timely, effective decisions. Furthermore thetransmission and processing of exhaustive infor-mation ties up CIS.

Communications and Information Systems _______________________________________________________________ 1-3

(2) Timeliness. Information must be available atthe appropriate place and time to be useful. Infor-mation management procedures and techniquesmust ensure the timely, unimpeded flow of rele-vant information. Well-planned and implementedCIS; clearly identified information requirements;effective collection, reporting, and dissemination;and decisiveness by commanders and staff allcontribute to timely information.

(3) Accuracy. Information must be as accurateas possible. Although information systems cancollect, transport, process, disseminate, and dis-play information, Marines must still evaluate theinformation and make decisions as to its accuracy,timeliness, and relevance.

(4) Completeness. Information may be usefulonly when it is complete. However, by the timecomplete information is obtained, it may no long-er be timely. If subordinates are aware of thecommander’s intent and critical information re-quirements , they can provide only thoseinformation fragments needed for situationalawareness.

(5) Objectivity. Information must be provided inthe most undistorted, factual, and unbiased waypossible. Any interpretation should be highlighted.

(6) Usability. The display or presentation of in-formation to the user must be understandable anduseful. Standard, clearly understandable informa-tion formats, symbols, and terms should be usedto exchange information and present it to users.Information exchanged and presented in non-standard form causes delays in interpretation andis more easily misunderstood, thereby leading tolonger decision and execution cycles and, ulti-mately, to less reliable decisions.

b. Information Defined

In this publication, the term information refers toall information that is needed to support the deci-sionmaking process on the battlefieldCthatinformation required to execute the planning, de-cision, and execution cycle in combat. Joint Pub0-2, Unified Action Armed Forces (UNAAF), pro-

vides two definitions for information: (1) facts,data, or instructions in any medium or form, and(2) the meaning that a human assigns to data bymeans of the known conventions used in theirrepresentation. It is important to understand thatthe term information, in its broadest sense, in-cludes everything from raw data, perhaps a radarsignal or a suspected enemy sighting by an obser-vation post, to data that has been extensivelyprocessed into useful information for a decisionmaker. Ultimately, study and analysis of informa-tion leads to an understanding of the situation,that is, situational awareness. Navy doctrinal pub-lication (NDP) 6, Naval Command and Control,and MCDP 6, Command and Control, describe afour-step cognitive process by which the transfor-mation from raw data to situational awarenesstakes place. (See fig. 1-1 on page 1-4.) These foursteps may be viewed as defining an informationhierarchy.

(1) Data. The first step in the cognitive process isto collect raw data. The raw data can take manyforms: radar signals, intercepted radio signals,meteorological data from a weather balloon, oreven bar-coded logistic data scanned from theside of a container. This data may be transmittedin either analog or digital formats by telephone,radio, or facsimile; transferred between comput-ers over local area networks (LANs); or sent bymessenger as rolls of undeveloped film or perhapscomputer diskettes. In any event, to be useful, thisraw data must be processed into a form that canbe understood by the ultimate user.

(2) Processed Data. Processing data involves awide range of functionsCCfrom decoding andtranslating intercepted communications to filter-ing and correlating sensor returns to developingfilm. Processing includes placing information intoa form, such as a graphical display or a formattedmessage, that can be readily interpreted. Someinformation will come to the MAGTF in pro-cessed form and wil l not require fur therprocessing. Once data has been processed, it is re-ferred to as information in the cognitive process.At this point some information may have immedi-ate value for Marines in close contact with theenemy. Such information is known as combat

1-4 ________________________________________________________________________________________________ MCWP 6-22

information. It is usually extremely perishableand should be disseminated to using units as rap-idly as possible.

(3) Knowledge. In the next step, information isanalyzed and evaluated. Through this process ofanalysis and evaluation comes knowledge. Forexample, the analysis of intelligence informationhelps build a picture of the enemy situation.

(4) Understanding. The last step in the process isthe development of an understanding of the situa-t ion based on the informat ion avai lable .Understanding is the result of applying humanjudgment based on individual experience, exper-tise, and intuition to gain a full appreciation of thebattlefield. This understanding is situationalawareness and provides a sound basis for opera-tional decisions. It allows the commander toanticipate events and to uncover critical vulnera-bilities for exploitation. As we strive to gain anunderstanding of the situation, however, we mustrecognize that time is working against us. Wemay not be able to gain complete situationalawareness before acting. Developing situational

awareness with limited and uncertain informationunder severe time constraints is the fundamentalC2 challenge.

c. Types of Information andCommander’s Critical InformationRequirements (CCIRs)

The information required for situational aware-ness fa l l s in to three genera l ca tegor ies :information about the enemy, information aboutthe environment, and information about friendlyforces. The identification of CCIRs is a means tofocus and direct the collection and processing ofinformation in those categories. CCIRs are theinformation regarding the enemy and friendly ac-tivities and the environment identified by thecommander as critical to maintaining situationalawareness, planning future activities, and facili-tating timely decisionmaking. Designation ofCCIRs reduces the volume of information to amanageable level and helps to ensure the accura-cy, relevance, and timeliness of that information.CCIRs comprise priority intelligence require-ments (PIRs), fr iendly force information

Figure 1-1. Information Hierarchy.


requirements (FFIRs), and essential elements offriendly information (EEFIs). Clearly definingthese information requirements is one of the mostdifficult and important tasks of command. CCIRswill not only govern the quantity and quality ofthe information available to support decisionmak-ing, but also have a direct effect on the workloadof the staff and subordinate units.

(1) PIRs. PIRs are intelligence requirements as-sociated with a decision that will affect the overallsuccess of the command’s mission. PIRs includeboth information about the enemy and informa-tion about the environment. Information aboutboth enemy capabilities and intentions is criticalto allow commanders to anticipate and analyzepossible enemy courses of action (COAs). Infor-mation on the environment includes informationon the weather, the terrain, the local population,the local communications and transportation in-frastructures, and a host of other factors that mayaffect the conduct of military operations. Throughidentification of PIRs, commanders ensure thatlimited intelligence resources are directed to ob-taining intelligence information that is essentialfor decisionmaking.

(2) FFIRs. To complete the picture of the situa-tion, the commander requires information onfriendly forces. FFIRs are the information thecommander needs about friendly forces to be ableto develop plans and make effective decisions.Depending on the circumstances, information onunit location, composition, readiness, personnelstatus, and logistic status could become an FFIR.Just as it is essential for the commander to usePIRs to identify the most important requirementsfor information on the enemy, it is also essentialfor the commander to specify what critical friend-ly information is required to support planning andexecution. The commander must have real-timeor near real-time information on the location, sta-tus, and capabilities of friendly forces. However,FFIRs must be prioritized to limit and focus thecollection and processing effort. It is easy to over-burden subordinate units, as well as to overloadcommunications networks, with requests for non-essential information. FFIRs help commanders,staffs, and subordinate units understand precisely

what information is needed to support the plan-ning, decision, execution and assessment cycle.

(3) EEFIs. EEFIs are specific facts about friendlyintentions, capabilities, and activities needed byadversaries to plan and execute effective opera-tions against our forces. These EEFIs may beviewed as representing the opposing command-er’s PIRs. Identification of the EEFIs is key toplanning effective INFOSEC, operations security,and other force protection operations.

d. Flow of Information

The goal of information management is to facili-tate a rapid, unconstrained flow of informationthroughout an organization from its sourcethrough intermediate collection and processingnodes to its delivery to the ultimate user. CCIRsserve as a necessary filter to ensure that only rele-vant information is delivered, thereby preventinginformation overload. Information must flow inall directions to support a common picture of thebattlefield among all unitsCsenior, subordinate,adjacent, supporting, and supported alike. A flexi-ble, responsive MAGTF C2 architecture isrequired that pushes relevant, time-sensitive in-formation to the user while allowing the user topull additional detail as required. This C2 archi-tecture consists of the C2 facilities, informationsystems, and communications networks that aredescribed in chapters 2, 3, 4, and 5.

A number of networking techniques are widelyused to improve the flow of information both with-in and between Marine Corps organizations. Thesetechniques support improved situational aware-ness and collaborative planning. Networking alsooffers tremendous opportunities for “electronicreachback.” The concept of electronic reachbackmay reduce the size of deployed staffs through theuse of specialistsCmilitary, government civilian,or consultantCwho never deploy. The MarineCorps Chemical/Biological Incident ResponseForce (CBIRF) provides an excellent example ofthis approach.

The most widely used networking technique is e-mail. E-mail provides a convenient means for

1-6 ________________________________________________________________________________________________ MCWP 6-22

exchanging information between both organiza-tions and individuals and is a highly effectivemeans of communication. E-mail supports rapiddissemination of time-critical information be-tween a HQ and subordinate organizations andacross staff sections. Organizational e-mail hasreplaced much of the information traffic that waspreviously sent over the Automatic Digital Net-work (AUTODIN). E-mail permits a single userto disseminate information to one or several userssimultaneously. However, in a deployed environ-men t , t he po t en t i a l t o ove r load t hecommunications system requires a disciplined ap-proach to the establishment and use of e-mailaccounts.

Other networking techniques support the conceptof information pull and have the potential to re-duce the load on the communications network andthereby improve the information flow. Thesetechniques include using home pages and news-groups as well as shared network drives on aLAN. However, posting information to a news-group or a home page, or updating a file on aLAN server, is no guarantee of receipt by the in-tended audience.

Pull techniques are generally unacceptable for thepromulgation of time-sensitive critical informa-tion such as fragmentary orders or warningorders. Although brief messages could be sent in-dicating that the order had been posted andrequiring addressees to acknowledge and comply,the order itself normally would not have beenlengthy enough to make this an efficient ap-proach. On the other hand, when selective accessto information in large databases is required tosupport an analysis, pull techniques are more effi-cient than push techniques.

1003. CIS Characteristics

It would be impossible to provide adequate C2support on the modern battlefield without CIS.This publication defines CIS as any system whoseprimary functions are to collect, process, or ex-change information. CIS should be reliable,

secure, timely, flexible, interoperable, andsurvivable.

a. Reliability

CIS should be available when needed and per-form as intended, with low failure rates and fewerrors. Reliability is also attained by standardizingequipment and procedures, building necessary re-dundancy, establishing effective logistic support,and protecting against computer viruses, electron-ic jamming, and deception. Systems shouldperform reliably aboard ships and aircraft, in gar-rison, and in austere field environments.

b. Security

CIS should provide security commensurate withthe user’s requirements and with the vulnerabilityof the transmission media to interception and ex-ploi ta t ion . Secur i ty i s achieved by us ingappropriate protection and cryptographic systems,using transmission security techniques, and edu-cat ing and t ra in ing personnel in secur i typrocedures.

c. Timeliness

CIS should process and transfer information be-tween decision makers rapidly enough tomaintain a high tempo of operations and ensurethat our decision and execution cycle remainsahead of any potential adversary’s.

d. Flexibility

CIS should be capable of being reconfiguredquickly to respond to a rapidly changing environ-ment. Flexibility can be obtained through systemdesign or by using commercial facilities, mobileor transportable systems, or prepositionedfacilities.

e. Interoperability

CIS should enable information to be exchangedamong all of the commanders and forces involved


in an operation. MAGTF CIS also should possessthe interoperability required to ensure informationexchange in joint and multinational operationsand in operations with other Governmentagencies.

f. Survivability

Survivability is all measures taken to prevent dis-ruption of CIS by enemy interference or naturaldisaster. Survivability can be enhanced by the dis-persal and protection of key nodes, physical andelectromagnetic hardening, and redundancy ofcommunications paths and information process-ing nodes.

1004. CIS Responsibilities

The officer military occupational specialties of2502, communications officer, and 4002, data pro-cessing officer, have been merged into a singlemilitary occupational specialty, 0602, CIS officer(CISO). Responsibility for this functional area hasbeen assigned to the G-6/S-6. To reflect this as-signment of responsibility, this publication refersto the G-6/S-6 as the CISO, rather than communi-cations officer or communications-electronicsofficer. Since the technology associated with suchsystems and networks continue to evolve, specificresponsibilities continue to evolve as well. Al-ready it is clear that responsibilities for installingand operating information systems will be sharedbetween CIS specialists and functional area users.For example, the tactical combat operations(TCO) system will be operated by personnel fromthe G-3/S-3. However, they will be assisted in in-stalling the system and interfacing the system toLANs and wide area networks (WANs) by CISpersonnel.

Just as important as the responsibility for install-ing, operating, and maintaining CIS is theresponsibility for the management of the informa-tion processed and exchanged by those systems.Each staff section will be responsible for the qual-ity of the information in the databases of thesystems that support that particular staff section.

However, overall information management policyand procedures will be under the staff cognizanceof the chief of staff (C/S) or the executive officer(XO).

a. Commander

The commander is responsible for the employ-ment of CIS within the command. Although theauthority to plan and employ communications andinformation systems may be delegated, ultimateresponsibility for CIS planning and employmentremains with the commander. The commandermust provide adequate guidance, including neces-sary assumptions and constraints, to support thedevelopment of CIS estimates, plans, and orders.The commander is also responsible for providingthe focus for information management throughoutthe organization and participates directly in theinformation management process by establishingthe CCIRs discussed in paragraph 1002c.

b. Communications and Information Systems Officer

The CISO is responsible to the commander for allmatters concerning the planning and employmentof CIS within the command. As a general or exec-utive staff officer, the CISO serves as an advisor,planner, supervisor, and coordinator. Specific re-sponsibilities include—

(1) Providing the commander and other staff of-ficers with—

● Advice on information management policiesand procedures.

● Estimates of the supportability of courses of ac-tion (COAs).

● Estimates of requirements for CIS re-sourcesCpersonnel, equipment, supplies, andfacilities.

● Recommendations for the allocation and use ofCIS resources.

● Recommendations for CIS training for thecommand.

1-8 ________________________________________________________________________________________________ MCWP 6-22

● Recommendations on the location, echelon-ment, and displacement of the command post(CP) and C2 facilities.

● Advice on operational aspects of informationsystems security (INFOSEC). See chap. 7 fordetailed G-6/S-6 responsibilities.

(2) Preparing CIS plans, orders, and standingoperating procedures (SOPs) to implement thecommander’s policies and decisions on CISemployment.

(3) Assisting the staff in the area of CIS for thepreparation of studies, estimates, plans, orders, in-structions, and reports.

(4) Ensuring compliance with the commander’sorders and instructions by supervising—

● Employment of CIS personnel.

● Installation, operation, and maintenance ofcommunications networks.

● LAN and WAN management, including Inter-net Protocol (IP) address and routing manage-ment.

● Technical support for functional users in the in-stallation, operation, and maintenance of infor-mation systems hardware and common usersoftware.

● Communications systems training and, in coor-dination with functional users, information sys-tems training.

● Supply and maintenance of CIS.

● Compliance with SOPs and interoperabilitystandards.

● CIS security in coordination with the other staffsections.

(5) Coordinating CIS matters with cognizantstaff sections and with staffs of other units, asrequired.

(6) Establishing CIS liaison with senior, subor-dinate, adjacent, supported, and supporting units.

c. Unit Information ManagementOfficer

The unit information management officer is a spe-cial staff officer operating under the staffcognizance of the C/S or XO. If an informationmanagement officer is not designated, then thisduty is the responsibility of the C/S or XO. Theinformation management officer is responsible forestablishing the policy and procedures for infor-mation management within the command.Responsibilities include:

(1) Coordination, with the assistance of the in-formation management officers of each staffsection and subordinate units, of informationmanagement efforts throughout the organization.

(2) Development and publication of the infor-mation management plan. The informationmanagement plan establishes policies and proce-dures for ensuring the quality and flow ofinformation within the organization.

(3) Coordination of the CCIR process: the nomi-nation of CCIRs; approval of CCIRs by thecommander and collection and reporting ofCCIRs by the staff; dissemination of CCIRs tohigher, adjacent and subordinate commands; andmaintenance of CCIRs.

(4) Development and implementation, in closecoordination with the CISO and other staff princi-pa ls and subord ina te un i t s ’ in format ionmanagement officers, of effective informationdissemination techniques.

(5) Development of training programs on infor-mation management procedures.

(6) Coordination with the unit security managerin the development and implementation of infor-mation security procedures.

(7) Coordination with the CISO on LAN man-agement and networking issues, communicationschannels prioritization, and traffic management.


d. Staff Section InformationManagement Officer

Each staff section should appoint an informationmanagement officer. The staff section informa-tion management officer is responsible for—

(1) Coordinating the internal and external infor-mat ion f low for the s taff sect ion and i tsintegration with the information flow of otherstaff sections, including identifying and prioritiz-ing information management requirements.

(2) Providing the unit information managementofficer with input to the information managementplan.

(3) Coordinating information management train-ing fo r s ec t ion pe r sonne l w i th t he un i tinformation officer.

(4) Coordinating the identification and process-ing of all CCIRs within the staff section’s area ofresponsibility (AOR).

e. Functional User Responsibilities

On the modern battlefield, it is essential that func-tional users of information be able to configureand operate the information systems supportingtheir functional area. Such an ability facilitatesincreased speed and operator knowledge in estab-lishing a distributed network. It also ensures thatfunctional area users are able to best exploit andcontrol the capabilities of systems that supporttheir needs. Functional users include every staffsection that is supported by CIS. Consequently,all staff principals have functional user responsi-bilities for the functional areas over which theyhave staff cognizance. For example, the G-3/S-3has functional user responsibilities for TCO.Functional user responsibilities include—

(1) Serving as the primary point of contact, bothinternal and external to the command, for issuesaffecting information systems supporting thefunctional area.

(2) Serving as the configuration manager for in-formation systems supporting the functional area.

(3) Conducting routine information system ad-ministration (assigning user identification,passwords, and privileges; performing data/filestorage and management; conducting systembackups).

(4) Coordinating with the G-6/S-6 to ensure thatadequate hardware, software, trained personnel,and procedures are in place before implementinga new system or system modification.

(5) Coordinating with the G-6/S-6 to developand maintain user training programs for CIS.

(6) Identifying to the G-6/S-6 information sys-tem support requirements.

(7) Identifying to the G-6/S-6 specific commu-nications requirements, including requirements tointerface with other information systems and po-tential interface problems.

(8) Complying with applicable CIS securitymeasures.

(9) Reporting malfunctions and outages and co-ordinating with the G-6/S-6 to restore service.

(10) Designating an information management of-ficer for the staff section.

f. Communications BetweenCommands

The responsibility for establishing communica-tions between units must be clearly delineated.These responsibilities are a cornerstone of com-munications doctrine. However, when supportingcombat operations, unit communications capabili-ties may be destroyed, and responsibility maybecome unclear or irrelevant. Flexibility, commonsense, initiative, cooperation, and mutual assis-tance must prevail in these instances.

1-10 _______________________________________________________________________________________________ MCWP 6-22

Communications between a senior and subordi-nate unit are the responsibility of the seniorcommander.

Communications between adjacent units are theresponsibi l i ty of the f irs t common seniorcommander.

Communications between a supporting and sup-ported unit are the responsibility of the supportingunit commander.

Communications between a reinforcing and rein-forced unit are the responsibility of the reinforcingunit commander.

Communications between a unit and an attachedunit are the responsibility of the commander of theunit to which the attachment is made.

g. G-6/S-6 Staff Cognizance

Communications units and detachments operateunder the staff cognizance of the supported unit’sG-6/S-6. The Marines assigned to these units, inconcert with personnel assigned to G-6/S-6 sec-tions and functional area users, are responsible foremploying CIS to support C2. Communicationsunits and the detachments they deploy are the keyelements in planning, installing, operating, andmaintaining an effective CIS network. See chap-ter 2 for responsibilities.

Chapter 2

Organizations

Section I

USMC Organizations

Marine Corps CIS are employed to support thecommand and control of Marine forces. To under-stand the requirements for CIS support, it is nec-essary to understand the organization and missionof those forces. Marine forces are organized,trained, and equipped under a total force conceptto conduct a wide range of expeditionary opera-tions. The Marine Corps total force consists ofthree components—the operating forces, the Re-serves, and the supporting establishment. Theoperating forces are an expeditionary “force-in-readiness,” providing forward presence, crisis re-sponse, and rapid power projection capabilities towarfighting commanders in chief (CINCs). TheMarine Corps Reserve is an integral part of the to-tal force team, is continuously training and oper-ating with the active forces, and is fully preparedto augment or reinforce in times of crisis. Thesupporting establishment is responsible for re-cruiting, training, equipping, and sustaining theforce—Active and Reserve.

2101. Operating Forces

The two major components of the operating forc-es are the Marine Corps Forces, Atlantic (MAR-FORLANT), and Marine Corps Forces, Pacific(MARFORPAC). These two forces constitute theexpeditionary combat power of the Marine Corps.The other two elements of the operating forces arethe Marine Corps Security Forces at naval instal-lations and the Marine Security Guard Battalionwith detachments at embassies and consulates.Consistent with the Goldwater-Nichols DefenseReorganization Act and Joint Pub 0-2, each com-batant CINC is assigned a Marine Service compo-nent for planning and execution of various

operational plans. MARFORLANT, headquar-tered in Norfolk, VA, is assigned as the MarineService component for the U.S. Atlantic Com-mand, the U.S. Southern Command, and the U.S.European Command. MARFORPAC, headquar-tered at Camp Smith, HI is assigned as the MarineService component for the U.S. Pacific Commandand the CINC United Nations Command/Com-bined Forces Command.

2102. Marine Corps Forces

Marine Corps forces (MARFOR) is the designa-tion given all Marine component commands. AMarine component command is a command con-sisting of all MARFOR assigned to a joint force.There are two levels of Marine components. AMarine Service component is assigned to a com-batant commander or a subordinate unified com-mander. (The two standing Marine Servicecomponents are described in paragraph 2101.)The other level of componency is the Marinecomponent assigned to a JTF. A Marine Servicecomponent may consist of one or more MAGTFs,as well as other required theater-level organiza-tions such as a Marine logistic command. Nor-mally, a JTF Marine component will include onlyone MAGTF and no additional Marine organiza-tions. A MAGTF commander may be dual-desig-nated as the Marine Service or JTF Marinecomponent commander. Unless higher authorityestablishes otherwise, the Marine componentcommander commands all assigned MARFORand exercises operational or tactical control(TACON) of other assigned or attached forces.The Marine component commander deals directlywith the joint force commander (JFC) in matters

2-2 ________________________________________________________________________________________________ MCWP 6-22

affecting assigned MARFOR. The Marine com-ponent commander commands, trains, equips, andsustains all Marine forces. Combat operations areexecuted by assigned MAGTFs. When designatedby the joint commander, a Marine componentcommander (at either the Service or JTF level)may also serve as a functional component com-mander. A functional component command is acommand that is normally composed of forces oftwo or more Military Departments and that maybe established to perform particular operationalmissions. Functional component commanders arenormally selected from Service component com-manders. Normally the Service component com-mander providing the preponderance of thefunctional capability in question is designated thefunctional component commander. A Servicecomponent commander designated as a functionalcomponent commander retains Service compo-nent responsibilities. A Marine component com-mander is more l ikely to be designated afunctional component commander in smallerscale contingencies where MARFOR constitute alarge portion of the joint force. The Marine com-ponent commander could be designated as thejoint force maritime component commander, jointforce land component commander, or joint forceair component commander.

MCWP 0-1.1, Componency, describes three pos-sible staff organizations for the component HQ:

● One commander and one staff—A single com-mander is designated as both the Marine com-ponent and MAGTF commander. Likewise asingle staff executes both component andMAGTF functions.

● One commander and two staffs—Again a sin-gle commander serves as both component andMAGTF commander; however, the command-er is supported by two separate staffs.

● Two commanders and two staffs—This organi-zation provides for two separate commanders,each with a dedicated staff. Although this is themost effective arrangement, it is also the mostcostly in terms of personnel, equipment, and fa-cilities.

2103. Marine Air-Ground Task Forces

Marine operating forces are further organized intoMAGTFs. MAGTFs are organized, equipped, andtrained to conduct forward-presence and crisis-re-sponse missions anywhere in the littoral areas ofthe world. The MAGTF is capable of conductingexpeditionary operations across the full spectrumof conflict, including forcible entry by amphibi-ous assault. The MAGTF is also capable of abroad range of noncombat operations rangingfrom noncombatant evacuations to disaster relief.Because MAGTFs are task-organized, they differin organization. However, all MAGTFs share thesame basic structure.

a. Core ElementsEach MAGTF has four core elements: a com-mand element (CE), a ground combat element(GCE), an aviation combat element (ACE), and acombat service support element (CSSE). Thisstructure is carefully designed to provide opera-tional flexibility and coordinated execution, thusmaximizing the contribution of each element tothe overall mission.

(1) CE. The CE is the MAGTF HQ. It is task-or-ganized to provide the command and control ca-pability necessary for effective planning andexecution of operations. In addition to the HQstaff, it includes units and detachments that pro-vide communications, information systems, andintelligence support for the MAGTF.

(2) GCE. The GCE is task-organized to conductground operations to support the MAGTF mis-sion. It is formed around an infantry organizationreinforced with artillery, reconnaissance, armor,engineer, and other forces as needed. The GCEcan vary in size and composition from a rein-forced infantry battalion to one or more Marinedivisions. During amphibious operations, itprojects ground combat power ashore by usingtransport helicopters from the ACE, organic as-sault amphibious vehicles, and Navy landingcraft.


(3) ACE. The ACE is task-organized to performall or part of the six functions of Marine aviationin support of MAGTF operations. During am-phibious operations, it can vary in size and com-position, from a reinforced aviation squadron ordetachment, with appropriate air command andcontrol and combat service support (CSS), to oneor more Marine aircraft wings (MAWs).

(4) CSSE. The CSSE is task-organized to providethe full range of CSS capabilities necessary tosupport and sustain MAGTF operations. Duringamphibious operations, it may vary in size andcomposition from a task-organized CSS detach-ment to one or more force service support groups(FSSGs).

b. Types of MAGTFsAll MAGTFs are expeditionary forces that aretask-organized for a specific mission. MAGTFsvary greatly in size and composition according tothe assigned mission. To provide a frame of refer-ence, Marine Corps doctr ine categorizesMAGTFs into Marine expeditionary forces(MEFs), Marine expeditionary units (MEUs), andspecial purpose MAGTFs (SPMAGTF).

(1) MEFs. Most of the Marine Corps operatingforces are assigned to the three standing MEFs:

These standing MEFs can deploy as a MEF (nor-mally in echelon) or can deploy subordinate units(task-organized for assigned missions). All threeMEFs provide MEUs for service afloat.

The MEF is the principal Marine Corps warfight-ing organization, particularly for larger crises orcontingencies. Normally commanded by a lieu-tenant general, it is capable of operations across

the full spectrum of conflict, including amphibi-ous assault and sustained combat operationsashore. A MEF can range in size from less thanone to multiple divisions and aircraft wings, to-gether with one or more FSSGs. As describedabove, there are three standing MEFs. Each ofthese MEFs consists of a permanent CE and oneMarine division, MAW, and FSSG. Each forwarddeploys MEUs on a continuous basis.

The size and composition of a deployed MEF canvary greatly depending on the mission, from ele-ments consisting of less than a full division, wing,or service support group to elements consisting ofmore than one. A MEF can deploy with forces at-tached from the other standing MEFs as well asfrom the Reserves. With accompanying suppliesfor 60 days, MEFs are capable of both amphibi-ous operations and sustained operations ashore.With appropriate augmentation, especially in thearea of C2 capability, the CE is capable of per-forming the mission of a JTF HQ, and the MEFcan serve as the nucleus of the JTF. The CIS re-quirements associated with such taskings are sig-nificant.

A MEF normally deploys in echelon and desig-nates its lead element as the MEF (forward) (MEF[Fwd]). The deployment of the MEF (Fwd) doesnot automatically trigger the deployment of theentire force. This would occur only if the crisis islarge enough to require the entire MEF.

(2) MEUs. The MEU is normally composed of areinforced infantry battalion, a reinforced helicop-ter squadron (which may include vertical/shorttakeoff and landing (V/STOL) attack aircraft), aMEU service support group, and a CE. The MEUis commanded by a colonel and deploys with 15days’ worth of accompanying supplies. MAR-FORLANT and MARFORPAC routinely forwarddeploy MEUs aboard amphibious shipping in theMediterranean Sea, Indian Ocean, Persian Gulf,and Western Pacific. Deployed as part of an am-phibious ready group, the MEU provides a com-batant or operational commander with a seabasedrapid-reaction force for a wide variety ofmissions. The MEU has a limited forcible entrycapability and can facilitate the employment of

MARFORPAC MARFORLANT

I MEF III MEF II MEF

Based in California

Forward based in Okinawa, mainland Japan, and Hawaii

Based in North and South Carolina

2-4 ________________________________________________________________________________________________ MCWP 6-22

follow-on forces, including joint and combinedforces as well as a MEF. Before deployment, theMEU undergoes a 6-month training program fo-cusing on selected maritime special operationsand culminating in the designation of the unit as“special operations capable” (MEU[SOC]).

(3) SPMAGTFs. A SPMAGTF may be formed toconduct a specific mission that is limited in scopeand focus and often in duration. A special purposeMAGTF may be any size, but normally it is a rel-atively small force—the size of a Marine expedi-tionary unit or smaller—with narrowly focusedcapabilities chosen to accomplish a limited mis-sion. Common missions of a special purposeMAGTF include raids, peacekeeping, noncombat-ant evacuation, disaster relief, and humanitarianassistance.

2104. Marine Corps Forces Reserves

Rapid force expansion is possible through the ac-tivation of the Marine Corps Forces Reserve(MARFORRES). The Reserve, like the activeforces, consists of a balanced combined-armsteam with ground, aviation, and CSS units. Orga-nized under the Commander, Marine Corps Forc-es Reserve, units are located at 191 trainingcenters in 46 states, Puerto Rico, and the Districtof Columbia. The Marine Corps Forces Reserve isclosely integrated with the active component un-der the Marine Corps total force concept. The Re-serves provide individuals and specific units toaugment and reinforce active capabilities.

2105. The Supporting Establishment

The supporting establishment consists of 16 ma-jor bases, training activities, formal schools, the

Marine Corps Recruiting Command, the MarineCorps Combat Development Command, theMarine Corps Systems Command, and Headquar-ters, U.S. Marine Corps. The supporting estab-lishment’s contributions are vital to the overallcombat readiness of the Marine Corps. Further-more, because of the interconnected nature of theCIS support infrastructure, the supporting estab-lishment plays a direct role in supporting the com-mand and control of all MAGTFs. This support isnecessary to effectively deploy and implementmodern information technology in support of theMAGTF both in garrison and when deployed. Inparticular, the Marine Corps Network OperationsCenter and the Marine Corps Tactical SystemsSupport Activity (MCTSSA) provide essentialsupport to the operating forces in the employmentand operation of CIS.

The Marine Corps Network Operations Center,located in Quantico, VA, acts as the focal pointfor technical support of Marine Corps data com-munications networks. This activity provides as-sistance in planning for and maintaining datacommunications networks for the MAGTF by co-ordinating with external agencies such as DISA;advising operational planners; providing softwaresupport, including contact teams; and providingMarine Corps-wide network operations manage-ment.

MCTSSA, located at Camp Pendleton, CA, pro-vides support to the operating forces for the oper-ation and maintenance of fielded CIS. As thedesignated post-deployment software support ac-tivity for most Marine Corps CIS, MCTSSA re-ceives trouble reports, analyzes problems, andtakes corrective action. The Fleet Marine Force(FMF) Support Division of MCTSSA providesdirect continuous liaison with the operating forcesto identify and resolve problems and providestraining and operational support for exercises andactual contingencies.


Section II

CIS Organizations

Marines dedicated to using CIS are organized bytable of organization (T/O) into the units de-scribed in the following subparagraphs. The T/Ounits may deploy and be employed as a completeunit or they may provide task-organized detach-ments to support elements of a MAGTF. Theseunits and detachments operate under the staff cog-nizance of the G-6/S-6 of the supported unit. Sep-arate units and detachments will be found only athigher echelons. At regiments and below, thecommunications unit will be an integral part ofthe HQ, and the communications unit commandermay also serve as the S-6. The Marines assignedto these units, in concert with personnel assignedto G-6/S-6 sections and functional area users, en-sure that an effective CIS network is planned, in-s t a l l ed , ope ra t ed , and ma in t a ined .Communications units and the detachments theydeploy are the key element in providing CIS capa-bility for the MAGTF elements that they support.Missions, tasks, and concepts of organization andemployment of these units are identified in theirT/Os and synopsized in this section.

2201. Communication Battalion

The mission of the comm battalion is to providecommunications support to a MARFOR compo-nent HQ; a MEF CE or a MEF(Fwd) CE; a com-ponent HQ deployed simultaneously with a MEFCE and a MEF(Fwd) CE; or two MEF(Fwd) CEs.A further mission is to provide support to threeMEU CEs. The battalion provides—

● CE communications for the supported CE:MEU, MEF(Fwd), MEF, and component HQ.

● Communications connectivity between the sup-ported CE and senior, adjacent, and subordi-nate HQs.

● The supported CE with a Naval Telecommuni-cations Systems entry and/or, as appropriate,entry into the Defense Communications Sys-tem.

C2 functions are exercised through the battalioncommander and the executive staff. The commbattalion consists of the HQ company, a servicecompany, three direct support comm companies,and a general support company. Elements of thecomm battalion may be employed separately astask-organized detachments to support organiza-tions smaller than a MEF CE, or the entire battal-ion may be employed to support larger MAGTFCEs. The HQ company includes the structure nec-essary to provide detachments to support twoMEU CEs.

The comm battalion will normally deploy as atask-organized unit or will deploy task-organizeddetachments in support of MAGTF CEs. Uponnotification, and before deployment of a MEFCE, the battalion will task organize to support thedeployment. Upon notification, and before de-ployment of a MEF(Fwd) CE or a componentHQ, a direct support comm company will be taskorganized to support the deployment. TheMAGTF CE G-6/S-6 exercises staff cognizanceover MAGTF communications; to facilitate sys-tem planning and engineering, the battalion con-ducts concurrent planning with the ComponentMAGTF G-6/S-6.

a. HQ CompanyThe mission of the HQ company is to provide or-ganic command, administration, logistic, and oth-er required support for a comm battalion as wellas to support system planning and engineering forand operational control of MAGTF communica-tions networks as required. The company—

● Plans and engineers CIS for the MAGTF CEs,as required.

● Installs, operates, and maintains network con-trol facilities and system control facilities forthe component HQ and MAGTF CEs ofMEF(Fwd) size and larger.

2-6 ________________________________________________________________________________________________ MCWP 6-22

● Installs, operates, and maintains field messagecenters, radio links, and tactical switchboard/telephone systems for two MEU CEs.

The company is organized into functional group-ings to provide for a battalion and company HQand support of the primary mission and tasks.The company normally collocates with the battal-ion HQ and operates in support of the battalion.As required, the various sections can be assignedto task-organized comm battalion detachments insupport of deployed MAGTFs.

b. Direct Support CompanyThe mission of the direct support company is toinstall, operate, and maintain the communicationssystem for a MEF CE, MEF(Fwd) CE, or compo-nent HQ. The company—

● Installs, operates, and maintains communica-tions center facilities for the supported CE/HQ.

● Maintains radio stations on CIS, administra-tive, logistic, and other radio nets as required.

● Installs, operates, and maintains switchboardand telephone services for the supported CE/HQ.

The direct support comm company is organizedinto a company HQ and three platoons organizedalong functional lines, tailored to support the pri-mary mission and tasks listed above. The directsupport comm company operates under the directcontrol of the comm battalion. When operating insupport of a MEF CE, the company deploys andcollocates with the comm battalion. When in sup-port of a MEF(Fwd) CE or component HQ, thecompany, with reinforcements, is capable of de-ploying as a separate unit.

c. General Support Communications Company The mission of the general support comm compa-ny is to install, operate, and maintain the compo-nent HQ, MEF CE, and MEF(Fwd) CE messageand voice switches and links to JTF HQ, majorsubordinate commands (MSCs), adjacent units,the Naval Telecommunications System, and the

Defense Communications System as required.The company—

● Installs, operates, and maintains the MEF digi-tal transmission backbone by using cable andmultichannel radio (MCR) equipment.

● Installs, operates, and maintains digital switch-es to provide secure and nonsecure voice, fac-simile, message, and data service to the MEFCE CPs.

● Interfaces the component and MEF CE CISwith national systems, the Naval Telecommu-nications System, commercial telecommunica-t ions systems, and senior (CINC/JTF),adjacent, and subordinate systems and net-works as required.

● Installs, operates, and maintains tactical widearea networks (WANs)/local area networks(LANs) for MAGTF CEs of MEF(Fwd) size orlarger.

The company is organized into a company HQ, aswitching platoon, a satellite comm platoon, and aterrestrial comm platoon and operates under thedirect control of the comm battalion. When oper-ating in support of the MEF CE, the company de-ploys and collocates with the comm battalion.When in support of a MEF(Fwd) CE or compo-nent HQ, detachments from the company willaugment a task-organized direct support commcompany to provide a switched communicationshub for an area communications network. Simul-taneously, ground mobile forces (GMF) satellitecommunications teams and terrestrial transmis-sion teams, as required, deploy as attachments toMSCs to connect the MEF CE with subordinatecommands.

d. Service CompanyThe mission of the service company is to providetransportation, maintenance, communications-electronics maintenance, materiel handling equip-ment, materiel handling equipment maintenance,and electrical power distribution services for acomm battalion. The company—

● Provides heavy transportation support to oper-ating companies as required.


● Provides communications-electronics equip-ment maintenance support to operating compa-nies as required.

● Provides primary electrical power distributionand service for the battalion.

● Provides materiel handling support to the bat-talion.

● Executes combat trains in support of the battal-ion.

The service company is organized into a companyHQ and three platoons: a motor transport platoonto provide the operation and maintenance ofheavy motor transportation equipment organic tothe battalion; a communications-electronics main-tenance platoon capable of performing third-eche-lon maintenance on digital switches, telephones,cables, computers, cryptographic equipment, andradio equipment, including high frequency (HF),very high frequency (VHF), ultra high frequency(UHF), super high frequency (SHF), and extreme-ly high frequency (EHF) single and multichannelassets organic to the operating companies of thecomm battalion; and an engineer platoon that in-stalls, operates, and maintains power distribution,air conditioning, refrigeration systems, and mate-riel handling equipment organic to the comm bat-talion.

When the comm battalion is deployed as a unit,the service company normally collocates with thebattalion HQ and provides support. As required,personnel and equipment from the service compa-ny can be assigned as part of task-organizedcomm battalion detachments.

2202. Marine Wing Communication Squadron

The mission of the Marine wing communicationsquadron (MWCS) is to provide expeditionarycommunications for the ACE of a MEF, includingcommunications support for the deployment oftask-organized elements of a MAW. The squad-ron—

● Assists in the system planning and engineeringof ACE communications and install, operate,and maintain expeditionary communications tosupport the command and control of the MEFACE.

● Provides operational systems control centers,as required, to coordinate communicationsfunctions internally and externally to the ACE.

● Provides maintenance support for ground-com-mon communications equipment in the MAW.

● Provides the digital backbone communicationssupport for the ACE HQ, forward operatingbases, and Marine air command and controlsystem (MACCS) agencies for up to two air-fields per detachment. The MACCS agenciesinclude the tactical air command center(TACC), tactical air operations center (TAOC),direct air support center (DASC), early warn-ing/control (EW/C) sites, low altitude air de-fense (LAAD) teams, and Marine air trafficcontrol detachments (MATCD).

● Provides tactical, automated switching andtelephone services for the ACE HQ and TACC.

● Provides electronic message distribution for theACE HQ, primary MACCS agencies, and ten-ant units.

● Provides external, single-channel radio (SCR),MCR, and radio retransmission communica-tions support for ACE operations as required.

● Provides deployed WAN and deployed LANserver support for the ACE HQ and primaryMACCS agencies.

● Provides the support cryptographic site for allground-common and MACCS-assigned com-munications security equipment within theACE.

The squadron consists of a HQ element and oneor two detachments. The squadron provides com-munications support for the ACE HQ and TACC.Each detachment may be independently deployedto provide external communications for up to twoairfields and four forward bases.

2-8 ________________________________________________________________________________________________ MCWP 6-22

2203. Communications Company, HQ Battalion,Marine Division

The mission of the comm company is to install,operate, and maintain the communications systemfor a Marine division HQ. The company—

● Installs, operates, and maintains communica-tions center facilities for the division HQ.

● Maintains radio stations on CIS, administra-tive, logistic, and other radio nets as required.

● Installs, operates, and maintains switchboardand telephone services for the division HQ.

● Installs, operates, and maintains MCR termi-nals for support of internal division communi-cations links as required.

● Provides, in coordination with the artillery regi-ment, communications support for the divisionnaval gunfire officer, division air officer, anddivision fire support coordination center(FSCC).

● Installs, operates, and maintains enhanced posi-tion location reporting system (EPLRS) masterstations and reference community in support ofMAGTF operations. The division comm com-pany is organized into a company HQ and sixplatoons organized by function to support themission and tasks listed above.

The division comm company will furnish com-munications for the division main, the divisionrear, and the alternate CP.

The division comm company will provide multi-channel communications to the three infantry reg-iments, the artillery regiment (which may act asthe alternate division CP), and to the DASC.MCR will be the primary means of communica-tion with major subordinate units. Wire communi-cations will not normally be installed to majorsubordinate units, but may be installed to separatebattalions if located within approximately onemile of the division HQ. Otherwise, wire servicewill be restricted to internal HQ installations for

local telephone and multichannel lines. Multi-channel communications service will be disruptedduring displacement of the division HQ.

2204. Communications Company, HQ and Service Battalion, FSSG

The mission of the comm company is to providecommunications support to the HQs of the FSSG,subordinate battalions, and CSSEs. The compa-ny—

● Provides communications support to the FSSGHQ/force CSS area and other CSSEs estab-lished to support MAGTF operations.

● Provides communications support for head-quarters and service (H&S), maintenance, sup-ply, and dental battalions and augmentation tothe organic capabilities of motor transport, en-gineer support, and medical battalions.

● Installs, operates, and maintains communica-tions control facilities.

● Installs, operates, and maintains tactical auto-matic switching and wire communications forthe FSSG HQ/force CSS area, CSS areas, and,when required, provides small-scale automatedswitching within maintenance, supply, medical,and dental battalions; the explosive ordnancedisposal platoon and bulk fuel company; theengineer support battalion; and the FSSG.

The company is structured to provide communi-cations support to the FSSG HQ in MEF opera-tions and task-organized detachments to the HQsof CSSEs deployed with MAGTFs smaller than aMEF. Augmentation from the MEF comm battal-ion is required if a dedicated naval telecommuni-cations system/defense communications systementry is required.

The company provides the primary communica-tions support for the FSSG HQ and other CSSEHQs.


2205. Communications Platoons, Branches, and Sections

Comm platoons, branches, and sections providecommunications support at the regimental/group,battalion/squadron, and, in some instances, com-pany/battery levels of the MAGTF. These com-munications units are organized to support the CPsand the communication networks of their parentorganization. The artillery unit comm platoons arefurther required to provide support for establish-ing the communications links to the units receiv-ing their artillery support. The radio battalioncomm platoon provides SI communications sup-port for the MAGTF CE as described further inparagraph 2206. Comm platoons, branches, andsections are found in the following organizations:

a. MEF CE● H&S company, radio battalion.● HQ, force reconnaissance company.

b. Marine Division● HQ company, infantry regiment.● H&S company, infantry battalion.● HQ battery, artillery regiment.● HQ platoon, artillery battery.● HQ battery, artillery battalion.● H&S company, tank battalion.● H&S company, assault amphibian battalion.● H&S company, combat engineer battalion.● H&S company, light armored reconnaissance

(LAR) battalion.

c. FSSG● H&S company, engineer support battalion.● H&S company, landing support battalion.● H&S company, motor transport battalion.● H&S company, medical battalion.

d. MAW● Marine air support squadron (MASS), Marine

air control group (MACG).

● H&S battery, LAAD battalion, MACG.● Marine air control squadron (MACS), MACG.● Airfield operations division, Marine wing sup-

por t squadron (MWSS) , Mar ine WingSupport Group (MWSG).

e. MEU● MEU CE comm platoon.● H&S company, BLT.● Comm detachment, MSSG.● Comm section, MACG, ACE.

2206. Special Security Communications Elements and Teams

The mission of the special security communica-tions elements and teams is to provide SI commu-n i ca t i ons suppo r t t o t he MAGTF. S Icommunications support for the MAGTF CE isprovided by the special security communicationselement of the radio battalion. SI communicationssupport for the division and MAW HQ is provid-ed by special security communications teams (SS-CT)—small force units organic to each divisionand MAW. These teams operate under the staffcognizance of the assistant chief of staff (AC/S),G-2/special security officer. The special securityelement or team provides the personnel andequipment to install, operate, and maintain SIcommunications terminals. The communicationscircuits are provided by the communications unitsupporting the HQ—the comm battalion for theMAGTF CE, the comm company for the divisionHQ, and the comm squadron for the MAW HQ.Close coordination is maintained with the sup-porting SYSCON and TECHCON to ensure ade-quate support and circuit priority. The specialsecurity elements/teams provide personnel aug-mentation to man ship’s signals exploitation spac-es (SSES) communications facilities as necessaryto support landing force requirements.

2-10 _______________________________________________________________________________________________ MCWP 6-22

2207. Amphibious Squadron Deployment Teams

In 1998, Marine communications detachments(MARCOMMDET) and Marine tactical C2 sec-tions (MTACCS) were reorganized into amphibi-ous squadron (PHIBRON) deployment teams toprovide support for landing force CIS on board allamphibious ships. As both the Navy and CISarchitecture migrates towards a more standard-ized, digital-based information network, it has be-come necessary to look at all amphibiousplatforms as CIS recipients, and couple these CISrequirements with support personnel.

PHIBRON deployment teams provide the re-quired expertise and leadership to maintainMarine Corps current and future CIS networks.The Marine staffing billets as part of the com-mander amphibious group (COMPHIBGRU) andFleet staffs will facilitate essential amphibiousCIS planning, coordination, installation, andmaintenance. In addition, the PHIBRON deploy-ment teams provide appropriate manpower to ad-dress critical deficiencies in amphibious CISrequirements determination and programming atFlag and staff levels, as well as necessary opera-tional support.

Communications and Information Systems _____________________________________________________________ 2-11

Section III

C2 Organizations

To exercise command and control in combat, allMAGTF units establish CPs, which serve as theHQ from which the commander and his staff op-erate. Units of battalion size or larger may dividethe HQ into echelons—main, rear, and tactical.The CP then becomes the echelon at which thecommander is physically located. The main eche-lon (main) is where the commander is normallylocated with those elements of the staff requiredto plan and direct operations and control forces. Ina large geographic area, a unit may establish arear echelon (rear) to serve principally as an ad-ministrative and logistical support base. To be inclose proximity to subordinate units and more di-rectly influence tactical actions, the commandermay create a tactical echelon (tactical CP). Thetactical echelon is mobile and contains a mini-mum number of personnel and equipment, includ-ing the commander, CIS operator(s), the G-2/S-2,the G-3/S-3, and the fire support coordinator.

2301. MEF CE

The MEF staff and supporting CE units are taskorganized to exercise command and control andto support the MEF’s assigned mission. The MEFincludes standard components as well as compo-nents that are used only for certain missions.Standard components include the principal staffsections and, within the operations section, a fu-ture operations cell and a current operations cell.Additional components may be added, based onthe mission, to support functions needed in a par-ticular operation. For example, in a humanitarianoperation, the MEF commander may organize anagency or section to coordinate with other gov-ernment (foreign or domestic), nongovernment,and private voluntary agencies and organizations.Another example, establish a consolidated mili-tary engineering group to provide centralizedplanning and manage engineering assets of theMarine Corps, Army, and Navy that are assignedto the MEF.

a. Future PlansThe MEF G-5 establishes a future plans cell toconduct long-range planning. Future plans worksclosely with the JTF HQ to ensure that the MEF isprepared for its next major mission. Productsfrom future plans provide the basis on which fu-ture operations will develop the operations order(OPORD).

b. Future OperationsThe MEF G-3 establishes a future operations cellthat is responsible for planning operations in sup-port of the current mission. Future operations re-ceives an initial plan and related material fromfuture plans and begins detailed planning. Futureoperations consists of several full-time personnelfrom the G-3 who form the core of an operationalplanning team. When the operational planningteam is formed, it includes members of the G-1,G-2, G-4, G-5, and G-6 sections. Other appropri-ate staff sections join the planning team as need-ed. Representatives from subordinate units alsojoin the team. Designated functional experts com-plete this group. The operational planning teamremains together through mission analysis andCOA development, analysis, and comparison/de-cision. These personnel then return to their re-spective work sections, complete annexes andappendices to the OPORD as required, and re-sume normal duties.

c. Current OperationsThe MEF G-3 establishes a current operations cellthat is responsible for executing operations. Cur-rent operations personnel receive the plan fromfuture operations and execute it. Current opera-tions personnel man the MEF combat operationscenter (COC) from which they monitor MEF op-erations and respond to situations as needed. TheCOC consists of a G-3 watch officer, a G-2 watchofficer, a senior watch officer, and a situation re-port watch officer. A number of enlisted Marinesassist in operating tactical information systems

2-12 _______________________________________________________________________________________________ MCWP 6-22

and maintaining situation displays. The G-2 andG-3 watch officers receive information from col-located MAGTF all-source fusion center (MAFC)personnel and force fires coordination center(FFCC) representatives (ground and air), the sur-veillance and reconnaissance center (SARC), aswell as subordinate and adjacent units. The G-2and G-3 watch officers filter this information andforward important pieces to the senior watch of-ficer. The senior watch officer also receives infor-mation that affects current operations from otherprincipal staff sections (G-1, G-4, and G-6). Thesenior watch officer evaluates information in thecontext of current operations and determineswhether action is required. Depending on the situ-ation, the senior watch officer may be assisted inthis process by other officers from current opera-tions. On the basis of authority delegated by theMEF commander, the senior watch officer acts byeither issuing orders or briefing the MEF com-mander and recommending action.

d. C2 FacilitiesWatch officers and supporting personnel from thestaff sections and supporting units establish andoperate centers within the HQ from which theday-to-day activities of the MEF are coordinated,controlled, and supported. These C2 centerssometimes, especially when dealing with air com-mand and control, are referred to as C2 agencies.In this publication, these centers and agencies,both at the MEF level and at the subordinate unitlevel, are referred to as C2 facilities. These facili-ties include the personnel, software, hardware,shelters, and ancillary equipment needed to sup-port command and control. The key C2 facility inthe MEF is the COC described above. In mostcases, the COC is collocated with the FFCC andthe MAFC. These three C2 facilities work togeth-er closely, focusing on current operations and re-sponding to the immediate needs of the MEFcommander. In all cases, information system sup-port and LAN connectivity within and amongthese three facilities are essential for efficient exe-cution of MEF operations. The FFCC, the MAFC,and other MEF C2 facilities are discussed underthe functional area they support.

e. MEF RearThe MEF rear may perform several functionswithin the MEF area of operations (AO). A MEFrear may be established to coordinate administra-tive and logistical activities while the MEF ma-neuvers forward. The MEF rear may also beassigned responsibility for rear area operations.Rear area operations are extremely complex at theMEF level. Joint doctrine currently defines eightrear area functions that must be coordinated: areamanagement, movements, infrastructure develop-ment, host nation support, security, communica-tions, intelligence, and sustainment. The MEFcommander may assign some or all of these func-tions to the MEF rear and others to the wing andthe FSSG. If assigned overall responsibility, theMEF rear would require the capability to plan andconduct rear area operations. In this instance, theMEF rear would establish a rear area operationscenter to facilitate command and control of opera-tions within the rear area. In situations where themain HQ does not move forward and the MEF re-tains responsibility for rear area operations, therear area operations center becomes another ele-ment of the MEF.

2302. Ground Combat Element

a. Division MainThe division main serves as the division com-mander’s primary HQ. Both current and futureoperations planning are accomplished in the divi-sion main. Division personnel monitor current op-erations from the division main, and if thecommander is aboard, current operations are alsodirected from the division main. Although smallerthan the MEF, the division main is organized forcommand and control in a similar manner, includ-ing a future operations cell within the G-3 section.Current operations are directed from the divisionCOC, which is typically manned with G-3 person-nel; G-2 personnel; the division engineer; the di-vision air officer; and nuclear, biological, andchemical (NBC) personnel. The FSCC is usuallyphysically collocated with the COC, and theDASC is either physically or electronically collo-cated with the FSCC.


b. Division RearIf the division is spread over a large geographicarea, the division commander may establish a di-vision rear. The division rear may serve principal-ly as an administrative and logistical support basefor the division. In this arrangement, the divisionmain may consist of the COC and FSCC with thecollocated DASC. The division rear would theninclude principal staff elements not required toplan and execute current operations (G-1, G-4,staff judge advocate, etc.). This arrangement al-lows the division main to maneuver rapidly inhigh-tempo operations.

c. Division Tactical EchelonThe division commander may establish a small,highly mobile tactical echelon to remain in closeproximity to the battle, gain first-hand situationalawareness, and more directly influence tacticaloperations at critical times. Depending on the sit-uation, either surface or air platforms, appropri-a t e ly con f igu red , p rov ide mob i l i t y andcommunications for the tactical echelon. The di-vision commander prescribes which staff mem-bers constitute the tactical echelon. A nominaltactical echelon would include the division com-mander, CIS operator(s), G-2, G-3, and fire sup-port coordinator.

d. Regiment/BattalionRegiments and battalions also use the main, rear,and tactical echelon structure and establish a COCto coordinate and direct operations. These opera-tions centers and echelons are much smaller thanthose at the division level because regiments andbattalions have fewer subordinate units and fewerfunctions to support.

e. Tactical Air Control PartyTactical air control parties (TACPs) provide coor-dination between GCE units and supporting avia-tion assets. TACPs exist at the infantry division,regiment, and battalion levels. Depending on thecommand level, a TACP contains a combinationof air officers, forward air controllers, and enlist-ed radio operators. Air officers serve at the divi-sion, regiment, and battalion levels. Theseofficers serve as special staff officers to their re-

spective commanders. Additionally, they mayserve within the FSCC to assist with planning anddeconfliction functions related to air support forthe assigned unit. Forward air controllers provideterminal control of close air support aircraft thatare passed to them by the DASC. These officersalso advise GCE commanders on aviation capa-bilities and limitations and prepare requests for airsupport.

2303. Aviation Combat Element

a. Wing MainThe wing main serves as the principal HQ for thewing commander. Like the MEF and divisionmain, most principal staff members are located inthe wing main, and future planning is done in thewing main. The wing rear area operations centeris often collocated with the wing main. Unlike theMEF and division main, however, the wing mainmay be located outside the MEF AO. The wingcommander often locates the wing main at a largeairfield, especially if this airfield houses most ofthe wing’s fixed-wing aircraft. Wing future andcurrent operations functions occur within theTACC, which may or may not be collocated withthe wing main.

b. TACCThe wing commander conducts future operationsplanning and current operations monitoring fromthe TACC. The TACC consists of three mutuallysupporting cross-function operational cells sup-ported by a centralized intelligence center. Theorganizations that comprise the TACC are—

● Future plans ● Future operations (future ops) ● Current operations (current ops)● Air combat intelligence (ACI)

Future plans conducts aviation and aviation sup-port planning for the next MAGTF missionchange. Future ops develops future air tasking or-ders (ATOs), and prepares OPORDs/fragmentaryorders for the next ACE mission change. Current

2-14 _______________________________________________________________________________________________ MCWP 6-22

ops executes the daily ATO and assesses its effec-tiveness.

ACI is imbedded within the TACC. Timely, tai-lored, and fused intelligence is integral to thefunctioning of future plans, future ops, and cur-rent ops. ACI is the focus of all aviation intelli-gence activities supporting the ACE. It producesand disseminates aviation specific all-source in-telligence, including assessments of adversary ca-pabilities and vulnerabilities, target analysis,battle damage assessment (BDA), and the currentstatus and priority of assigned targets to assist inexecution day changes. The TACC uses special-ized information systems and equipment to dis-play a common picture of the aviation situationreceived from tactical digital information links.Each Marine aviation function (antiair warfare,assault support, electronic warfare (EW), air re-connaissance, offensive air support, and controlof aircraft and missiles) provides representation tothe TACC.

c. TAOCThe TAOC performs air surveillance and controlof aircraft and missiles for the wing commander.Air control personnel assigned to this facility usespecialized information systems, sensors, anddedicated communications links to search theMEF’s airspace and provide air defense servicesfor those areas designated as vital. The TAOCcontrols friendly aircraft in the intercept of hostileaircraft and assists Marine missile units in locat-ing and destroying hostile aircraft. Informationgained through radar assets and tactical digital in-formation links is transmitted to the TACC andprovides situational awareness for the wing com-mander. The TAOC is movable, but not mobile,and is located in the rear of the MEF AO. Often,the TAOC is collocated at a fixed-wing airfield.

d. MATCDsMATCDs provide air control services in andaround airfields. Additionally, detachment radarcontributes to air surveillance efforts, and infor-mation is forwarded to other agencies via tacticaldigital information links. Detachment personnel

coordinate with Stinger teams to construct andoperate base defense zones.

e. LAAD Battery Command CenterThe LAAD battalion, usually collocated with theTAOC, establishes a COC for the exercise of bat-talion operations. The LAAD battalion command-er exercises overall command and control ofLAAD battalion operations from the COC. TheLAAD battalion commander obtains and relaysintelligence and combat information on friendlyand enemy operations to the two subordinateLAAD battery COCs. The LAAD battery COCsmaintain situational awareness of MAGTF andother air operations and plan and control employ-ment of LAAD teams.

f. DASCThe DASC controls aircraft supporting the GCE.Air support personnel control aircraft en route tothe forward air controllers serving with infantryunits. DASC controllers also monitor helicoptermissions within the MEF battlespace. These per-sonnel assist GCE units to obtain additional airsupport, either fixed-wing aircraft or helicopters,beyond those preplanned missions scheduled tofly. Because of their proximity to the seniorFSCC, DASC personnel often help the wing com-mander maintain awareness of the ground combatsituation. Several configurations exist for theDASC, with varying degrees of size, capability,and mobility. One configuration may be em-ployed in a C-130 aircraft.

g. Airborne CoordinatorsMarine pilots and aircrew often serve as airborneextensions of MACCS. The tactical air coordina-tor (airborne) serves as an extension of the DASCand coordinates aircraft en route to close air sup-port missions. The tactical air coordinator (air-borne) receives aircraft “hand-offs” from theDASC, briefs those aircrew, then turns these mis-sions over to ground or airborne forward air con-trollers for terminal control. The assault supportcoordinator (airborne) also serves as an extensionof the DASC and coordinates complex helicoptermissions. The assault support coordinator decon-


flicts transport packages, escort packages, and firesupport efforts throughout the mission.

Airborne strike coordination and reconnaissanceis a means to efficiently focus aviation fires in thedeep battlespace. This function, usually per-formed by an F/A-18 aircrew, allows real-time re-connaissance to locate the MEF commander’shigh-priority targets. Once located, the strike co-ordination and reconnaissance aircrew control at-tack aircraft in much the same manner as atactical air coordinator, cycling and deconflictingmultiple strike packages as they ingress to the tar-get area. Using aircrew to extend the commandand control system offers several benefits. Thesepersonnel can position themselves to effectivelycontrol multiple aircraft missions and maintaincommunications with both the aircraft they con-trol and ground-based C2 facilities.

2304. CSSE

a. FSSG MainThe FSSG main is task organized by the FSSGcommander to enable him to control and coordi-nate logistic support of the MEF. An FSSG mainincludes the principal staff sections, a future plansand deployment section, and the CSS operationscenter (CSSOC). The future plans and deploy-ment section ensures that the FSSG is prepared tosupport the next major mission of the MEF. Of-ten, this new mission involves a deployment or re-deployment. The CSSOC monitors currentoperations and plans near-term future operations.The FSSG main will typically be located near seaor aerial ports of debarkation in the MEF’s AO.Subordinate battalions establish their own HQ inproximity to the FSSG main.

b. CSSOCThe CSSOC serves as the hub for future and cur-rent operations planning within the FSSG main.Each CSS functional area (supply, maintenance,transportation, engineering, health services, andservices) provides representation to the CSSOC.Under the supervision of a G-3 watch officer,these personnel monitor current operations and

maintain status displays of friendly and enemysituations. Additionally, CSSOC personnel han-dle requests from subordinate units and keep theMEF informed of the CSS situation. FSSG com-manders may choose either a centralized or de-centralized configuration for their CSSOCs.

c. Combat Service SupportDetachmentsDepending on the situation, the FSSG commanderestablishes forward detachments to provide directsupport to the GCE. Detachment commandersmay establish small facilities to coordinate sup-port and monitor logistics communications nets.A mobile CSS detachment possesses the least ca-pability to establish an operations center. In thisinstance, the CSSOC could resemble a mobile,tactical echelon. Communications connectivitywould be predominantly through SCR.

d. Movement Control CenterMovement control centers support the deploy-ment of the MEF from the home station, throughintermediate bases, to the destination. The com-mander, MARFOR (COMMARFOR) establishesa HQ movement control center, which providesconnectivity to United States TransportationCommand (USTRANSCOM) and keeps the MEFforce movement control center apprised of strate-gic movement issues. The force movement con-trol center controls and coordinates all movementsupport and conducts liaison with the Air Mobili-ty Command, the Military Sealift Command, andthe Military Traffic Management Command. Theforce movement control center supervises effortsof unit movement control centers of the division,wing, and FSSG. These latter units provide trans-portation and communication assets in support ofdeployment activities. Bases and air stations fromwhich Marine units deploy establish base or sta-tion operations support groups to coordinate theirefforts with those of deploying units. These basesalso provide their transportation and communica-tion assets in support of deploying units. Theseunits augment unit movement control centers toensure that all personnel and materiel arrive at seaand aerial ports of embarkation.

2-16 _______________________________________________________________________________________________ MCWP 6-22

e. Marine Logistic CommandThe COMMARFOR may establish a Marine Lo-gistic Command (MLC) and assign it responsibil-ity for establishing the theater general supportstructure to facilitate reception (arrival/assembly)and reception, staging, onward movement, and in-tegration operations, and, on order, for providingoperational logistic support to Marine forces asthe Marine component operational-level logisticagency in theater. MLC is a task organization op-tion, not a standing organization. COMMARFORmay choose to assign a specific FSSG responsi-bility for MLC functions. Then, on the basis ofthe operational situation, theater geography, oper-ations and logistic command and control, and in-frastructure requirements, COMMARFOR willassign Marine component resources to the FSSGfor detailed task organizing and conducting MLCtheater-support operations.

2305. Intelligence Command and Control

The combat intelligence center (CIC) is estab-lished under the G-2/S-2 within the MAGTF HQto provide centralized direction for the overallMAGTF intelligence effort. This organizationserves the entire force by consolidating, validat-ing, and prioritizing intelligence requirementsfrom all MAGTF elements. The CIC links theMAGTF to JTF, theater, national, and allied intel-ligence assets. The CIC includes as key internalnodes the MAFC and the SARC. It also providessmall G-2/S-2 elements to support both the currentand future ops cells. The CIC is supported by thereconnaissance operations center and the opera-tions control and analysis center (OCAC).

a. MAFCThe MAFC provides intelligence analysis, pro-duction, and targeting information to the MEF.An integral part of the MAGTF main CP, theMAFC is usually collocated with the MEF COC.All surveillance, reconnaissance, and intelligencegathering results flow into the MAFC, where theyare fused with previous collections and intelli-gence products are updated and disseminated.

b. SARCThe SARC is the primary intelligence C2 nodeused to direct, coordinate, monitor, and superviseMAGTF collection operations (including intelli-gence collection operations conducted by organicattached and direct support assets). The SARC islocated close to the MEF COC. The SARC coordi-nates collection and operations tasks to variousMEF assets, including force reconnaissance, thesensor control and management platoon, the un-manned aerial vehicle squadron, the radio battal-i on , coun t e r i n t e l l i gence de t achmen t s ,interrogator-translator teams, the force imageryinterpretation unit, and the topographic platoon.Collection results are forwarded to the MAFC toincorporate into current intelligence products, and,when appropriate, to the COC.

c. Reconnaissance Operations CenterThe reconnaissance operations center serves as afocal point for monitoring and supervising forcereconnaissance operations. Located near theSARC, this facility gathers information from dis-persed teams, decrypts reports, and forwards in-formation for fusion into the overall MEFintelligence situation display. Personnel manningthe reconnaissance operations center assist recon-naissance teams with movement and other activi-ties as needed.

d. OCACThe OCAC provides centralized direction, man-agement, and control of signals intelligence (SIG-INT) and EW activities within the MEF andcoordinates with external theater and national as-sets. Assigned personnel process, analyze, anddisseminate collected information. The OCAC islocated within the MEF HQ compound, near otherintelligence C2 facilities.

e. Intelligence Centers The G-2/S-2 will establish intelligence centers atall echelons of the MAGTF down to the battalionlevel. Personnel assigned to the intelligence cen-ter will collect, process, integrate, analyze, evalu-ate, and interpret intelligence and continuouslyupdate the enemy situation. This information willbe rapidly provided to current and future ops.


These centers will be collocated with the COCwhenever possible.

2306. Fire Support Centers

C2 facilities are established to coordinate theoverall fire support effort and to exercise tacticaland technical fire support direction.

a. FFCCThe FFCC is established at the MEF level to as-sist the MEF commander in planning and coordi-nating deep fires. The FFCC performs threeprimary functions for the MEF: planning, acquir-ing, and maintaining target information; coordi-nating and integrating MAGTF-level fires withfuture operations; and coordinating and integrat-ing MAGTF-level fires into current ops. Locatedwithin the MEF, this facility assists both futureops and current ops in their targeting functions.Additionally, the FFCC provides coordination be-tween the MEF and JTF targeting boards and cen-ters. Watch standers may be collocated with theCOC to facilitate rapid deep fires coordination.

b. FSCCEach Marine ground combat organization from di-vision to battalion employs a FSCC as an advisoryand coordination agency. The FSCC is collocatedwith the COC. The senior FSCC coordinates anddeconflicts fire support efforts among subordinateunits and centers. The FSCC includes the fire sup-port coordinator, artillery liaison, TACP person-nel, mortar unit liaison when appropriate, and anaval surface fires liaison. At the division level,the division artillery officer or artillery regimentcommanding officer serves as the fire support co-ordinator. At lower levels, each commander ap-points a fire support coordinator from his staff(usually the weapons company commander).

c. Fire Direction CenterFire direction centers (FDCs) exist at artillery reg-iments, battalions, and batteries. These organiza-tions permit respective commanders to plan andcontrol fires. Fire direction activities may be cen-tralized or decentralized. At regimental and bat-

talion levels, the FDC exercises tactical firedirection, and battalion FDC personnel supervise,advise, and augment battery personnel as re-quired. Battalion personnel also assist by trouble-shooting gunnery problems, which enablesbattery FDC personnel to focus on delivering ar-tillery fires. The battery FDC provides technicalfire direction by evaluating information receivedby forward observers and determining firing data.This firing data is issued to artillery sectionsthrough fire commands. Battery FDCs are also ca-pable of tactical fire direction and would performthis function in cases, such as MEU deployments,when the battery operates independently.

d. EW Coordination CenterThe EW coordination center (EWCC) facilitatescoordination of EW operations with other firesand CIS. This center coordinates efforts by the G-2, G-3, and G-6 to eliminate conflicts betweenthese overlapping battlespace functions. TheEWCC is under the staff G-3’s cognizance. As-signed personnel identify potential conflicts inplanned operations and work to resolve these is-sues. The EWCC includes an EW officer, a CISrepresentative, and other liaison officers as need-ed. Liaison could include radio battalion represen-tation, EA-6B electronic countermeasuresofficers, a MACG radar officer, and other Servicerepresentatives.

2307. Rear Area Operations Centers

Responsibility for rear area operations may betasked to the MEF rear. It may also be shared withor assigned to the FSSG and the wing, especiallywhen the MSCs are widely dispersed geographi-cally. In any case, a rear area operations center fa-cilitates C2 operations within the rear area(s). Therear area operations center contains personnel tomonitor and coordinate the vast array of activitiesoccurring in the MEF rear area. For MSCs, thesize and scope of a rear area operations centerwould be driven by the unit’s mission and rear ar-ea activities. At a minimum, the wing and FSSGwould use one or more rear area operations cen-ters to coordinate security for the bases they occu-py. Personnel serving in these facilities must be

2-18 _______________________________________________________________________________________________ MCWP 6-22

knowledgeable in all functions performed by thefacility. To support the security function, a firesupport coordinator must be assigned to plan andcoordinate fires in the rear area. All rear area op-erations centers should be linked and should coor-dinate activities across the entire MEF rear area.

2308. CIS Control

At the MAGTF CE level, the CISO (G-6/S-6) ex-ercises overall operational systems control ofMAGTF communications networks and informa-tion systems. The G-6/S-6 also coordinates withthe controlling authorities of external networks.The G-6/S-6 is assisted by personnel from thecommunications battalion to exercise operationalsystems control. Operational systems control isexercised at levels lower than the MAGTF downto the battalion/squadron level by the G-6/S-6 ofthat organization. The G-6/S-6 is supported by or-ganic communications units or detachments.

a. Operational Systems Control CenterThe functions of an operational systems controlcenter (OSCC) exist at all levels of CIS control.At higher echelons (MSC and above), specificagencies are established to conduct these func-tions. At lower echelons (bn/sqdn), the functionsare still performed, but at the S-6/comm unit lev-el. Figure 2-1 details a typical Joint operationalsystems control model. The OSCC functions con-sist of the following:

(1) Systems Planning and Engineering. Thesystems planning and engineering (SPE) performsfuture ops functions for communications opera-tions. The SPE at any echelon consists of CIS net-work design. These networks are designed andsubsequently engineered to meet the operationalrequirements as determined by the CISO. Circuitsare determined by type and number to meet bothinternal and external command communicationsrequirements. SPE personnel normally performtheir duties in a suitable facility as part of the G-6/S-6 staff in the main CP. The MAGTF G-6/S-6 isthe senior Marine CISO who directs the overall

SPE effort at the MAGTF level. The G-6/S-6 atlower echelons, with the assistance of their sup-porting communications unit/detachment, per-forms appropriate level SPE functions inaccordance with the overall MAGTF communica-tions plan.

(2) Systems Control. The systems control (SY-SCON) performs current operations functions forcommunications operations. The SYSCON is es-tablished by the operations officer of each com-munications unit to maintain current informationon availability and operational readiness of CIS,set priorities and resolve conflicts. SYSCON per-sonnel perform their duties in an appropriate fa-cility in the vicinity of the supported commandpost. The SYSCON receives direction from theSPE. The SYSCON coordinates directly with se-nior, subordinate, and adjacent SYSCONs as re-quired. SYSCON personnel must have thetechnical expertise and experience to coordinateresolution of complex communications problems.

(3) Technical Control. TECHCON provides cen-tralized technical supervision over the installa-tion, operation and maintenance of single channelradio, wire, multichannel and data communica-tions systems. TECHCON functions are per-formed from specially designed TECHCONfacility(ies), the network operations center, main-tenance facilities, and communications centers,when established. The TECHCON facility(ies)provides a means to conduct and coordinate cir-cuit troubleshooting and restoration. The size andscope of the TECHCON facility(ies) are drivenby the size of the communications organizationand types of services being provided. TECHCONpersonnel must have the technical expertise andexperience to resolve complex communicationsproblems.

b. Joint Communications Control CenterThe joint communications control center (JCCC)is the operational systems control agency of theJTF or CINC J-6. Per Chairman, Joint Chiefs of


Staff Manual (CJCSM) 6231.07A, Joint NetworkManagement and Control, the JCCC providestheater or JTF planning level and supervision ofcomponent communications control centers. Nor-mally, liaison officers from each service compo-nent command are provided to the JCCC assubject matter experts and participate in JCCCfunctions as watch members.

c. MAGTF Communications Control CenterThe MAGTF G-6 employs the MAGTF commu-nications control center as the MAGTF operation-al systems control center. The subordinatecommunications battalion(s)/company(ies) staffaugments the MAGTF communications controlcenter. The MAGTF communications control cen-ter coordinates external communications controlwith the JTF or CINC J-6 through the JCCC. The

MAGTF communications control center may alsobe required to support to a Marine component HQ.

d. Component CommunicationsControl CentersEach component of the Joint Force or TheaterCommand (USA, USAF, USN, USMC) establishsomes form of an operational systems controlcenter to perform component level operationalsystems control functions. The components of thedesignated army Theater Signal Command willnormally support the Army Component Com-mand and augment JTF/Theater-level operationalsystems control agency. The MAGTF communi-cations control center will coordinate OSCCfunctions with joint and service component com-munications control centers to maintain the jointnetwork.

Figure 2-1. Joint Operational Systems Control Model.

2-20 _______________________________________________________________________________________________ MCWP 6-22

2309. Amphibious C2 Facilities

When the MAGTF is embarked aboard amphibi-ous shipping, the MAGTF commander servesconcurrently as the commander of the landingforce. While embarked, the MAGTF commanderand his staff direct the actions of the MAGTFfrom C2 facilities aboard the amphibious ships.Under the OMFTS concept, MAGTF commandand control may remain afloat throughout the am-phibious operation. Many of the shipboard C2 fa-cilities also support the commander, amphibioustask force (CATF), who normally is located, withhis staff, in the flag plot located aboard the flag-ship.

a. Landing Force Operations CenterThe landing force operations center (LFOC) is theshipboard space allocated to the commander,landing force (CLF), and staff to plan and executelanding force operations. The LFOC is normallylocated on the amphibious task force (ATF) flag-ship. The LFOC staff are the same personnel whoman the MAGTF COC when and if it is phasedashore in an amphibious operation. The functionsof the LFOC mirror those of the COC. This centercontrols and monitors the activities of the landingforce until the CLF establishes command ashore.

b. Amphibious Task ForceIntelligence CenterThe amphibious task force intelligence center(ATFIC) is a single Naval intelligence facilityformed during a preassault phase of amphibiousoperations. It supports the requirements of theCATF and the CLF. The ATFIC is usually locatedaboard the amphibious flagship and is manned byNavy and Marine intelligence personnel. Intelli-gence resources available to the ATFIC includenational, joint, combined, and internal naval forceassets. Some of these assets may already be for-ward deployed in advance or assault operations.Landing force intelligence personnel and their or-ganic information systems such as the Intelli-gence Analysis System (IAS) and the technicalcontrol and analysis center (TCAC) workstationsare integrated in the ATFIC operations whileafloat. Additionally, the ship’s signals exploita-tion space (SSES) is within the AFTIC and con-

tains ATF special security communicationsterminals and processing facilities.

c. Supporting Arms CoordinationCenter The CATF exercises overall coordination of sup-porting fires within the amphibious objective areathrough the supporting arms coordination center(SACC). This center, located aboard the amphibi-ous flagship, consists of a supporting arms coordi-nator, naval gunfire, air support, and targetinformation sections. ATF operations, intelli-gence and communications personnel, and land-ing force fire support personnel perform thefunctions of the SACC. These functions are simi-lar to those performed by the FFCC and FSCCthat may be subsequently established ashore. Alanding force liaison is established in the SACC ifthe responsibility for coordination of supportingarms is passed ashore.

SACC provides the commanders of the ATF andthe landing force with information concerning therequirements and developments that affect coordi-nation of fire delivery by naval gunfire units, sup-port aircraft, and artillery units. Fire supportrequests received from the landing force are coor-dinated from this center to ensure that all fires areintegrated to achieve the maximum effect againsttargets. Current fire support information is contin-ually updated and displayed while direction forthe execution of restrictive fire plans and instruc-tions concerning troop safety are promulgated.Naval gunfire plans are prepared and their execu-tion is supervised by the SACC staff. This centeralso coordinates air support operations with ap-propriate ATF and landing force air control agen-cies. Records of targets in the objective area aremaintained, and appropriate fire support activitiesin the amphibious objective area are monitoredwhen responsibility for the coordination of fires ispassed to the CLF ashore.

d. Tactical Air Control Center (Afloat)The tactical air control center (afloat) (TACC[A])is organized and located in the flagship of theCATF. The TACC(A) provides the means to di-rect and coordinate all tactical air operations in anobjective area, including antiair warfare, until this


responsibility is transferred to Marine air controlagencies ashore. The TACC(A) consists of a tacti-cal air controller; air support controller; antiairwarfare coordinator; and appropriate operations,intelligence, and communications personnel andequipment. These personnel and their equipmentare provided by the flagship, the staff of theCATF, and a designated tactical air control squad-ron.

e. Helicopter Direction CenterThe helicopter direction center (HDC) is orga-nized aboard the flagship of the helicopter trans-port group to provide the means to direct andcontrol helicopters during the ship-to-shore move-ment. It consists of a helicopter director, who isresponsible to the tactical air commander for di-rection of all helicopters and supporting aircraft; ahelicopter direction net officer; a helicopter aircontroller; and other appropriate air operationsand communications personnel and equipment.These personnel and their equipment are normallyprovided by the flagship on which the HDC is es-tablished.

To effect the direction and control of helicoptermovement in an objective area, the HDC must op-erate under the overall direction of the TACC(A)for coordinating air operations with other agen-cies and under the operational control (OPCON)of the helicopter transport group commander. TheHDC advises the TACC(A) on all matters pertain-ing to helicopter movement that require coordina-tion with supporting arms. The HDC providesinformation as directed by the TACC(A) and thehelicopter transport group commander and main-tains availability and location status of assignedhelicopters. The HDC also receives requests forhelicopter support, designates units to provide thehelicopters for specific missions, and directs theiremployment. The HDC further controls the move-ment of helicopters, both transport and escort,from wave rendezvous to initial point and fromtakeoff at the landing zone to breakup point. TheHDC also controls movement of helicopters be-tween platforms and assists the DASC in control-ling helicopters between ship and shore after thecontrol of helicopters has been passed ashore.

f. Tactical-Logistical GroupTactical-logistical groups (TACLOGs) are tempo-rary agencies organized as required by groundcombat organizations of a landing force to assistthe naval control organization in the ship-to-shoremovement of troops, equipment, and supplies.They are normally established aboard controlships at each echelon of the MAGTF, along withthe naval control agency exercising control overthe ship-to-shore movement of that echelon dur-ing a waterborne landing. They are also estab-lished aboard each helicopter transport carrierduring vertical assaults. A TACLOG consists ofoperations, CSS, embarkation, and communica-tions personnel provided by the parent groundcombat organization.

TACLOG assists the corresponding naval controlagency in handling landing force requirementsduring the ship-to-shore movement. It is task-or-ganized to advise the naval control agency as tothe location of units, equipment, and supplies andto monitor their regulated movement ashore. TheTACLOG maintains a detailed record of the un-loading and landing status, provides informationto appropriate commanders concerning theprogress of the ship-to-shore movement, and re-sponds to routine requests received from units bycoordinating with the naval control agency. It fur-ther advises the naval control agency when thetactical situation ashore dictates an adjustment tothe prescribed landing sequence.

2310. Mobile CPs

Mobile CPs provide means for commanders at alllevels to keep pace with rapidly maneuvering ele-ments. They are essential for the conducting ma-neuver warfare. These mobile CPs are usuallymounted in vehicles, but may be situationally air-borne or footmobile. Various configurations existdepending on the availability of C2 platforms. C2variants of the assault amphibious vehicle (AAV)and light armored vehicle (LAV) are specificallydesigned for this purpose, and it is also one of theroles of the utility helicopter. Units also use or-ganic vehicles in various arrangements to formmobile CPs. Mobile CPs normally consist of the

2-22 _______________________________________________________________________________________________ MCWP 6-22

commander accompanied by a few key personnelfrom the tactical echelon. At the small unit level(rifle company and rifle platoon), the CP is oftenfootmobile. In some situations, the tactical eche-lon of a larger unit may be footmobile; for exam-

ple, when operating in terrain that precludes usingvehicles. However, given restrictions on theamount of equipment that can be carried, a foot-mobile CP is usually impractical above battalionlevel.

Chapter 3

Information Systems and Services

Information systems and services provide themanagement and decision support tools that arerequired to support command and control func-tions, including operations planning and execu-tion. To improve interoperability, increaseefficiency, and reduce costs, the DOD has mandat-ed that the Services move to a common set of in-formation systems and services. This migration istaking place rapidly with the fielding of the GCCSand the implementation of the defense informationinfrastructure (DII) common operating environ-ment (COE). These developments are having a

profound effect on Marine Corps CIS policy andwill ultimately have an impact on all MAGTF CISdoctrine, organization, training, and equipment.The Marine Corps is migrating its tactical infor-mation systems to the DII COE beginning withTCO and IAS. DII COE compliance will providecomplete interoperability with GCCS and otherDII COE-compliant systems. To understand theinformation systems and services provided by theMAGTF CIS environment, it is necessary to de-scribe that environment in the context of theGCCS and the DII COE.

Section I

Defense Information InfrastructureCommon Operating Environment

The DII COE provides a standard environment,off-the-shelf software, and a set of programmingstandards that describe in detail how mission ap-plications will operate in the standard environ-ment. The COE contains common supportapplications and platform services required bymission applications.

3101. Mission Applications

Each mission application that is migrated to thecommon environment must comply with guid-ance published in the DII COE standards (see app.A). Although there may be some need for“workarounds” as mission applications migrate tothe COE, these are necessary as mission applica-tions. As the COE matures, workarounds will nolonger be needed and will be stripped from themission application.

3102. Services

As the user selects the mission applications need-ed to perform a set of tasks, the integration tool au-tomatically loads all the COE modules needed bythose applications. These selected modules makeup a subset of the DII COE superset: this subset iscalled a COE-variant (COE-V). The original COEsoftware components are used without modifica-tion. System managers must ensure that COE-Vsdo not include nonstandard software that dupli-cates services provided by software under theCOE. Figure 3-1 (on page 3-2) shows the servicesavailable under the DII COE. This figure depictsmission applications (e.g., Joint Maritime Com-mand Information System [JMCIS]) accessing theservices in the DII COE through a standard appli-cation interface. It also reflects both the missionapplications and the DII COE services hosted oncommon computer platforms using COTS operat-ing systems.

3-2 ________________________________________________________________________________________________ MCWP 6-22

Figure 3-1. DII COE Services.


Section II

Global Command and Control System

The GCCS implements the joint C4I for the war-rior concept. This concept calls for the capabilityto move a joint force anywhere on the globe atany time and to provide that force with the infor-mation necessary to accomplish its mission. TheGCCS is a revolutionary approach designed to re-solve joint C2 interoperability issues and evolveincompatible, Service-specific C2 programs into asingle integrated C2 system. Figure 3-2 depictsGCCS.

3201. Background

The Assistant Secretary of Defense (C3I) and theJoint Staff are exercising oversight of GCCS im-plementation. The Assistant Secretary of Defense

(C3I) established the GCCS as the principal mi-gration path for defense-wide C2 systems, direct-ing that GCCS rapidly and efficiently delivermission-essential C2 capabilities to combatantcommanders through maximum use of commer-cial off-the-shelf (COTS) and government off-the-shelf (GOTS) components. Further, he speci-fied that the program evolve through a continuousrequirements-refinement process to meet the goalof providing responsive C2 support to combatantcommanders.

GCCS provides a fused and shared picture of thebattlespace together with the essential planningand assessment tools required by combatant com-manders and their subordinate commanders.

Figure 3-2. GCCS

3-4 ________________________________________________________________________________________________ MCWP 6-22

GCCS also supports readiness assessment and re-porting by the Services. GCCS employs a modernclient-server architecture using commercial, opensystems standards and will, through the ongoingDOD migration strategy, reduce the large numberof information systems in use today.

GCCS is evolving from a baseline of existing C2systems. This baseline has served as the corner-stone for the rapid implementation of an initialsystem capable of fulfilling the most critical userrequirements. As new GCCS versions are subse-quently fielded, existing legacy systems will bereplaced. The common functional, physical, andoperational characteristics of GCCS are based ona single COE described below. All future jointand Service/CINC-specific C2 systems must becompatible with this COE. The goal is to achievea fully integrated, single GCCS in which all C2functions are provided through GCCS applicationprograms that have a common look and feel.

3202. Description

GCCS is composed of several mission applicationprograms built within a single COE. GCCS alsoincludes the network that supports sharing, dis-playing, and exchanging information. The GCCSinfrastructure consists of a client-server environ-ment incorporating UNIX-based servers and cli-en t t e rmina l s as wel l as microcomputerworkstations operating on a standardized LAN.(Although GCCS currently employs a UNIX-cen-tric architecture there is movement toward an ar-chitecture that exploits the capabilities ofWindows NT. This is discussed in paragraph3003.)

The GCCS infrastructure supports data transferamong workstations and servers. Connectivity be-tween GCCS sites is provided by the secret inter-net protocol router network (SIPRNET), thesecret layer of the DISN that is discussed in thenext chapter. Remote user access is also support-ed by using dial-in communications and the tele-communication network (TELNET) protocol.Ultimately, GCCS will be able to operate in amultilevel security mode. See chapter 7 for moreinformation on multilevel security initiatives.

The baseline GCCS architecture consists of asuite of relational database servers and applica-tion servers. At most GCCS sites, the relationaldatabase server acts as a typical file server byhosting user accounts, user-specific data, and site-specific files that are not part of GCCS. The appli-cation servers host the automated message han-dling system, applications not loaded on thedatabase server, and other databases. At eachGCCS site, one application server is configured asthe executive manager. This server acts as the us-er interface and provides access to GCCS applica-tion programs through user identification anddiscrete passwords. GCCS software applicationprograms are categorized into two groups: COEapplications and mission applications.

Several key GCCS mission applications are de-scribed in paragraphs 3203 through 3211. GCCSis an evolutionary program with mission applica-tions being added or improved in each new soft-wa re r e l ea se . The GCCS con f igu ra t i onmanagement website (http://spider.osfl.disa.mil/new_home/cnfgmgmt/cnfgmgmt.html) containsdetailed information on the current status ofGCCS mission applications.

3203. Joint Operation Planning and Execution System

JOPES is the integrated C2 system used to planand execute joint military operations. It is a com-bination of joint policies, procedures, personnel,and training and a reporting structure supportedby automated data processing on GCCS. The ca-pabilities of the JOPES mission applications sup-port translation of the National CommandAuthorities’ policy decisions into planning andexecution of joint military operations. These ap-plications are used by MAGTF planners for de-ployment and employment planning.

3204. Global Reconnaissance Information System

The Global Reconnaissance Information Systemsupports the planning and scheduling of monthly


sensitive reconnaissance operations (SRO) theaterrequests. The Joint Staff staffs these requeststhrough the Office of the Secretary of Defense,the Central Intelligence Agency, and the State De-partment for National Security Council approval.Incoming reconnaissance 1/2/3/4 formatted mes-sages are received by an automated message han-dling system, validated, and passed to the GlobalReconnaissance Information System applicationfor automated processing and database update.The Global Reconnaissance Information Systemgenerates all reconnaissance messages and alsomonitors the monthly execution of theater recon-naissance missions approved in the previousmonth. The Global Reconnaissance InformationSystem is used by the Joint Staff and theater com-mands exercising OPCON over airborne recon-naissance assets.

3205. Evacuation System

The Evacuation System collects and displays in-formation about U.S. citizens located outside theUnited States as collected by U.S. State Depart-ment embassies and consulates. It accesses the da-tabase server via TELNET from a GCCS-compatible client.

3206. Fuel Resources Analysis System

The Fuel Resources Analysis System provides fu-el planners with an automated capability for de-termining supportability of a deliberate or crisisaction plan and for generating the time-phasedbulk petroleum, oil, and lubricants required tosupport an operation plan (OPLAN). The FuelResources Analysis System facilitates review ofthe fuel requirements of a proposed, new, or re-vised OPLAN and assesses adequacy of availableresources to support crisis action planning. Re-quirements can be generated and analysis per-formed either for the overall OPLAN, or byService, or by region within the AO. Two or moreOPLANs can be combined into a single OPLANfor analysis. The requirements generated can bevaried through the use of intensity tables and con-sumption data extracted from the Logistics Fac-

tors File or with the Service-provided datasystem.

3207. Global Status of Resources and Training System

The Global Status of Resources and Training Sys-tem provides information on the status of unitswith respect to personnel, equipment, and train-ing. Query and display capabilities include cate-gories of units (ships, fighter aircraft, groundforces, etc.), specific types of units (frigates, ar-mor battalions, F-15 squadrons, etc.), and a spe-cific unit (displays detailed status information).

3208. Theater Analysis and Replanning Graphical Execution Toolkit

TARGET contains a set of planning tools de-signed to support the operational planner duringcrisis action procedures. These tools allow plan-ners and operators to accomplish tasks throughrapid access to required documents; informationsources; and analysis, multimedia, and teleconfer-encing tools.

3209. Joint Deployable Intelligence Support System (JDISS)

JDISS applications provide access to national,theater, and tactical intelligence sources throughthe joint architecture for intelligence. It providesprotocols for connectivity and interoperabilitywith intelligence systems required to supportforces during peacetime, crisis, and war.

JDISS includes the protocols to access intelli-gence link (INTELINK) at the secret classificationlevel (INTELINK-S). INTELINK-S is an intelli-gence dissemination service that enhances thesharing of intelligence information electronicallyover the SIPRNET. INTELINK provides intelli-gence dissemination by using networked informa-

3-6 ________________________________________________________________________________________________ MCWP 6-22

tion discovery, retrieval, and browsing services.Its “point and click” technology makes intelli-gence products widely available to both users andproducers of intelligence. JDISS applications areable to exchange sensitive compartmented infor-mation (SCI)—video and data—using the JointWorldwide Intelligence Communications System(JWICS). The JWICS communications network isdiscussed in chapter 4.

3210. ATO

The ATO application provides the capability toview and print selected portions of ATOs. A que-ry function allows the user to tailor requests forinformation in a specified order for viewing. Thequery function also supports the display of color-

coded ground tracks for selected portions of theorder. ATO interfaces with the contingency the-ater automated planning system (CTAPS) and itsfollow-on theater battle management core systems(TBMCS).

3211. JMCIS

JMCIS is the foundation for the GCCS fused op-erational battlespace picture. It displays near real-time ground, sea, and air tracks. JMCIS uses acore service known as unified build to providegeographic display, contact correlation, and trackdatabase management. JMCIS Unified Buildserved as the basis for the original GCCS COE,which has evolved into the DII COE.


Section III

MAGTF C4I

MAGTF C4I is the concept for the integration ofMarine Corps tactical information systems andthe migration of selected systems to the DII COE.The MAGTF C4I concept is consistent with DODmandates for DII compliance and designation ofstandard migration systems. MAGTF C4I pro-vides commanders and their staffs at all levels ofthe MAGTF with the capability to send, receive,process, filter, and display data to aid them intheir decisionmaking process. MAGTF C4I alsoprovides a shared situational awareness through acommon picture of the battlespace.

3301. Migration Strategy

The MAGTF C4I migration strategy focuses onincorporating the software functionality ofMAGTF tactical information systems into aMAGTF C4I Software Baseline. Standard soft-ware mission applications and the capabilities tosupport MAGTF C2 functions are described anddeveloped under the MAGTF C4I Software Base-line Program. The MAGTF C4I Software Base-line relies on the DII COE to provide its commonsoftware environment. The MAGTF C4I Soft-ware Baseline is developed using the DII COEsoftware as its foundation. The MAGTF C4I Soft-ware Baseline configuration is coordinated withand controlled under the JMCIS Unified Buildand DII COE programs. This strategy is based onthe following:

● Integration with the DOD GCCS. No function-ality offered by GCCS will be duplicated by theMAGTF C4I Software Baseline. All MAGTFC4I Software Baseline functionality that hasjoint applicability will be nominated for use byGCCS.

● Commitment to the DII COE and the evolutionto open systems, including Windows NT®,Windows 95®, and Java®.

● Pursuit of a naval architecture that integratesUSMC, Coast Guard, and Navy requirements.

● Focus on support of naval expeditionary forcesin a joint environment.

● Pursuit of nondevelopmental items (NDI),COTS and GOTS solutions.

● Exploitation of Windows NT® to avoid thetechnical complexity and high costs associatedwith developing, integrating, operating, andmaintaining UNIX-based systems.

3302. MAGTF C4I Software Baseline Capabilities

Table 3-1 (on pages 3-8 and 3-9) describes thecurrent capabilities of the MAGTF C4I SoftwareBaseline. Capabilities are added as new segmentsare approved and incorporated into the MAGTFC4I Software Baseline. As more capable seg-ments are added, many older segments will beeliminated. These upgrades will occur continuallyas new releases of the MAGTF C4I SoftwareBaseline are fielded to the FMF.

3303. Hardware/Operating System Requirements

MAGTF C4I Software Baseline uses Marinecommon hardware suite (MCHS) equipment, in-cluding the Hewlett-Packard TAC-4, CHS-2 SunSPARC 20, and Intel PC platforms running theDII COE. The MAGTF C4I Software Baseline iscompletely transportable across the GCCS hard-ware platforms. These systems are certifiedthrough the security accreditation process in ac-cordance with current DISA requirements. Vari-ous SECNAVINSTs provide guidance on securitycertification and accreditation procedures withinthe Department of the Navy (DON).

3-8 ________________________________________________________________________________________________ MCWP 6-22

Table 3-1. MAGTF C4I Software Baseline Capabilities .

Segment

COE

Description/Purpose

Universal Applications

Windows NT Application programming interfaces for mapping, communications, track database, and alerts from command and control PC and UNIX DII COE code. It is the minimum set of application program interfaces required for NT DII COE development.

Plotter Ability to plot a tactical map overlay of a user-specified area on an acetate sheet.

Symbols This COE improvement provides the capability to display MIL STD 2525 symbols and overlays to the common operational picture/common tactical picture display.

Tactical Digital Information Link (TADIL) A/B

This COE improvement provides the capability to receive, parse, and display TADIL A and B tracks.

Tactical Communications Interface Module (TCIM)

Capability to exchange over-the-horizon (OTH)-Gold tactical messages over SCR via the TCIM modem using the Marine tactical systems protocol.

Command and Control PC MS Windows NT client program that provides the capability to participate in the common opera-tional picture and common tactical picture using an Intel PC.

Netscape COTS World Wide Web (WWW) browser and e-mail. It will also provide Web page production and shared whiteboard collaboration tools. May replace the functionality of Internet News, Intel-ligence Relay Chatter, and JDISS.

MS Office COTS package that provides advanced word processing, graphics, spreadsheet, presentation graphics, and scheduling capabilities.

WABI Capability to run a subset of MS Windows 3.11 applications, including MS Office, on a UNIX workstation. It is also required to run MS Office.

Maneuver

Position Location Information Sys-tem (PLIS) and JPI

Capability to receive, parse, and inject tracks into the track database from global positioning sys-tem (GPS) and other position location information (PLI) systems.

Routes Graphical route planning tool with an overlay builder and trafficability analysis.

Intelligence

MIG Centralized database server for intelligence databases. Provides access to the National Informa-tion Database. Tactical data can be accessed, output, and updated by analysts at local and remote locations. Naval Intelligence Processing System (NIPS) applications are resident in MIG. NIPS also provides capabilities to process and store message traffic from various sources, generate and transmit messages, and create briefings with mapping and imagery tools.

Communications

System Planning, Engineering, and Evaluation Device (SPEED)

SPEED applications will be available in the MAGTF C4I Software Baseline when converted to operate in Windows NT.

Strategic and Operational

Air Field Worldwide database of airfield capabilities by individual location.

TARGET Timeline-based, time-phased force deployment data (TPFDD) editing and analysis tool.

.


Evacuation System Database of potential evacuees at foreign service posts.

Force Augmentation Planning and Execution System (FAPES)

OPLAN mobilization planning, analysis, and execution tool.

Fuel Resources Analysis System OPLAN fuel capacity, requirement, and expenditure tool.

GCCS ATO Review (GARC) ATO confirmation message browser. Data is parsed from messages sent by CTAPS. May dupli-cate the NIPS functionality for Sun SPARCs.

Global Status of Resources and Training System

Tool to enter status of unit locations, deployment readiness, and training.

Global Transportation Network (GTN)

Visibility into USTRANSCOM transportation data for the global transportation network.

Individual Manpower Requirements and Availability System (IMRAS)

Individual mobilization planning and execution tool.

Imagery Product Archive (IPA) Imagery files and products database.

Internet News SIPRNET bulletin board tool.

Intelligence Relay Chatter SIPRNET chat tool.

JDISS Multimedia applications used to access intelligence information databases over INTELINK and other networks.

Joint Engineer Planning and Execu-tion System (JEPES)

OPLAN civil engineering tool.

JOPES: Ad Hoc Query Ad hoc querying capability to the JOPES using data fields and Boolean operators from a pick list. May duplicate the NIPS ad hoc functionality.

JOPES: Information Resource Man-ager (IRM)

Generic database manipulation tool for compositing OPLANs.

JOPES: JOPES Navigation (JNAV) JOPES front-end tool.

JOPES: Predefined Reports (PDR) JOPES OPLAN report tool.

JOPES: Requirement Development Analysis (RDA)

JOPES TPFDD force module generator.

JOPES: Scheduling and Movement (S&M)

JOPES TPFDD scheduling and movement tool.

Logistics Sustainment Analysis and Feasibility Estimator (LOGSAFE)

Logistics sustainment, feasibility, resupply requirements, contingency plans, and “black-bottom” cargo transportation tool.

Medical Planning and Execution System (MEPES)

OPLAN medical requirements tool.

Oracle COTS relational database management system that provides access to the various databases within the system. It allows the users to access, query, and update information in the databases. May duplicate the NIPS Sybase functionality.

Table 3-1. MAGTF C4I Software Baseline Capabilities (continued).

Segment

COE

Description/Purpose

3-10 _______________________________________________________________________________________________ MCWP 6-22

Although the MAGTF C4I Software Baselinemaintains UNIX operating system segments, newdevelopment is based on Windows NT. TheUNIX-based TAC-4 and CHS-2 platforms are in-terim application and data servers. However, bothIAS and TCO workstations are transitioning to acommon PC-based Windows NT® environment.

All systems will be DII COE/MAGTF C4I com-pliant. All systems will operate on the standardMCHS of equipment and will be distinguishedonly by the set of applications or functional seg-ments resident on the computer. The Marines thatuse each of the functional area tactical data sys-tems (TDS) in this section are responsible for set-ting up, operating, and maintaining those systems(e.g., Marines from the G-3/S-3 will be responsi-ble for setting up, operating and maintaining TCOand Marines from the G-2/S-2 will have those re-sponsibilities for IAS). CIS personnel will assistthese functional users in the operation and main-tenance of their systems and provide external net-work connectivity and IP addresses. This divisionof responsibilities requires close cooperation andcoordination between the functional system userand CIS personnel and applies to all of the infor-mation systems described in this section. Systemdescriptions in paragraphs 3304–3309 are orga-nized by the functional area that they support.

3304. Maneuver

Maneuver systems support operations planningand execution by providing commanders andstaffs with shared situational awareness throughan integrated representation of the battlespace.Maneuver systems pull and fuse information fromall functional areas. These systems provide themeans for mission receipt and rapid developmentand dissemination of the commander’s intent andOPLANs and OPORDs.

The tactical combat operations (TCO) systemprovides an automated capability to process bat-tlefield information. TCO provides timely infor-mation to help commanders and their staffsconduct operations planning and make critical C2decisions. TCO processes and fuses tactical infor-mation to form a common picture of the battle-

field. TCO supports the development of COAsand the preparation and dissemination ofOPLANs and OPORDs, including overlays thatare geographically referenced to an electronicmap.

TCO supports the operations sections of all FMFunits of battalion/squadron size and larger as wellas planning sections at higher echelons. TCO con-sists of computer workstations operating at the se-cret level on multiple LANs interconnected on theSIPRNET through MAGTF communications net-works. TCO components include the MCHS ter-minals, the tactical communications interfacemodule (TCIM) for radio interface, and LANequipment. The functional manager for TCO isthe G-3/S-3, and COC personnel are responsiblefor setting up the TCO equipment in their opera-tions centers. Communications and informationsystems personnel are responsible for connectingTCO terminals to the SIPRNET, providing themwith IP network host addresses, and assisting op-erations COC personnel in installing and main-taining the TCO.

JMCIS-Afloat and TCO are both built around theJMCIS Unified Build core software. This permitsMarine forces embarked aboard Navy ships to“plug in” to the JMCIS-Afloat. Furthermore, be-cause the JMCIS Unified Build served as thebaseline for the DII COE, migration of TCO tothe DII COE is occurring rapidly. DII COE com-pliance will provide complete interoperabilitywith GCCS and other DII COE compliant sys-tems.

3305. Intelligence

Intelligence systems support the timely planning,collection, processing, production, and dissemina-tion of all-source intelligence. In addition, thesesystems support the effective employment of re-connaissance, surveillance, and target acquisitionresources.

a. IASIntelligence analysis system (IAS) providesMAGTF intelligence personnel with intellopera-


tions planning and direction, all-source process-ing and fusion, and dissemination capabilities.IAS is the principal Marine Corps intelligence in-formation system. The G-2/S-2 is the functionalmanager for IAS, and intelligence personnel areresponsible for setting up IAS equipment in theirintelligence centers. MEF IAS is a sheltered, mo-bile system with multiple (scalable) analyst work-stations in a client-server LAN configuration. IASsuites for intermediate commands are configuredin a four-workstation LAN. Single IAS worksta-tions support battalions and squadrons. IAS usesMCHS equipment and will transition to the DIICOE. IAS hosts the secondary imagery dissemi-nation system (SIDS), and links are planned withother intelligence systems at the national (DODIntelligence Information Systems [DODIIS]), the-ater, and tactical (including TCAC, Tactical Elec-tronic Reconnaissance Processing and EvaluationSystem (TERPES), and Joint Services ImageryProcessing System [JSIPS]) levels.

b. MAGTF SIDSThe manpack SIDS device provides the capabilityto electronically collect, transmit, and receive im-agery products throughout the MAGTF, as well asthrough adjacent, higher, and external commands.MAGTF manpack SIDS uses MAGTF communi-cations networks and complies fully with the na-tional imagery transmission format (NITF)Version 2.0 and the Tactical CommunicationsProtocol (TACO II). MAGTF SIDS is fielded intwo configurations. One configuration is hostedon the IAS; the other is a standalone manpackedconfiguration. Both configurations allow the userto display, manipulate, annotate, print, transmit,and receive images on a multipurpose worksta-tion.

c. TCAC Product Improvement ProgramTactical control and analysis center product im-provement program (TCAC PIP) provides the ra-dio battalions with a fully capable SIGINTprocessing, production, and dissemination sys-tem (and other C2 information systems) that isshelter-mounted on a heavy variant, high-mobili-ty, multipurpose wheeled vehicle (heavy HM-MWV). The TCAC PIP includes three SUN

workstations, two SUN servers, and five radios(one HF, two VHF, one UHF, and one UHF satel-lite communications [SATCOM]). Through itsautomated processing, analysis, and reporting ca-pability, TCAC PIP enhances the overall controland management of SIGINT assets as well as thedevelopment and dissemination of SIGINT prod-ucts. Timely, fused, and filtered SIGINT productsare provided to MAGTF commanders, usuallythrough the MAFC.

d. Joint Surveillance Target Attack Radar System The JSTARS aircraft is a U.S. Air Force asset thatcan provide the MAGTF commander with a near-real-time depiction of the surveillance area for in-telligence and battlespace situational awareness.JSTARS detects and tracks moving and stationaryground targets in the AO, including data on ene-my forces and position location of friendly forces.Access to this theater asset also enhances targetacquisition and identification, postattack combatassessment, indications and warning, cueing/cross-cueing among intelligence collectors, oper-ations planning and execution, and pattern analy-sis/intelligence fusion.

JSTARS consists of two major components: theU.S. E-8C aircraft and the common ground sta-tion (CGS), which provides connectivity to theaircraft. The sensor suite provides target detectionand tracking through moving target indicator,fixed target indicator, and synthetic aperture radardata. The aircraft transmits data sets to the CGSvia a surveillance control data link. The CGS ter-minates the surveillance control data link and pro-cesses and manipulates the sensor data sets. Mapdata are registered and topographical features en-tered on the two operator workstations and digi-tized plotting boards within the CGS. TheJSTARS picture will be fed simultaneously fromup to four CGS remote workstations, which maybe located in the MAFC, the current operationscell, the FFCC, the future operations cell, or otherC2 nodes. The MAFC serves as the principal C2node for correlating, analyzing, and interpretingJSTARS information and for its dissemination toMAGTF subordinate units.

3-12 _______________________________________________________________________________________________ MCWP 6-22

In the future, full JSTARS data sets (moving tar-get indicator, fixed target indicator, and syntheticaperture radar imagery), fused intelligence, trackdatabase information, and contact and track datainformation will be available throughout theMAGTF down to regimental/MAG levels viaIAS, TCO, and/or the Advanced Field ArtilleryTactical Data System (AFATDS) by using theTDN backbone.

e. Mobile Electronic Warfare Support System Product Improvement ProgramThe MEWSS, mounted in an LAV, provides SIG-INT/EW support to a wide variety of missions, in-cluding LAR operations. The MEWSS PIPprovides the radio battalions with an upgradedSIGINT/EW suite. The MEWSS PIP is a wide-band intercept system that provides a completepicture of the enemy electronic order of battle andstate of the art electronic warfare support mea-sures (ESM). The system contains three primarymission subsystems that are also part of the Ar-my’s Intelligence/EW Common Sensor program.

The primary mission subsystems consist of acommunications intelligence (COMINT) systemthat provides intercept, collection, and geoloca-tion across a broad frequency range and a capabil-i t y aga in s t a va r i e ty o f mode rn t h r ea tcommunications emitters; an electronic intelli-gence (ELINT) system that provides interception,identification, and geolocation of noncommunica-tions emitters, including counterbattery and bat-tlefield radar; and a precision location system tolocate communications emitters to within target-ing accuracy. The MEWSS PIP system includesan electronic attack (EA) module that is capableof “smart” and conventional jamming. TheMEWSS PIP is completely interoperable with Ar-my Intelligence/EW Common Sensor platforms,thereby allowing cooperative engagement and da-ta sharing.

f. TERPESTactical Electronic Reconnaissance Processingand Evaluation System (TERPES) is a system thatsupports the reception, processing, evaluation,

and dissemination of electronic reconnaissanceinformation. Data is received from EA-6B aircraftby data links, magnetic tape, and crew logs. TER-PES also supports EA-6B mission planning, brief-ing, and debriefing and generates intelligence forstrike mission planning. TERPES fuses data fromEA-6B missions with information from other na-tional and theater sources to update the electronicorder of battle and passes intelligence to the IASfor further processing and dissemination. TERP-ES is housed in one 8-foot by 8-foot by 20-footshelters dedicated to mission analysis, missionplanning, and mission support.

3306. Air Operations

Air operations systems support the planning, co-ordination, and control of MAGTF air combat op-erations and interface with Navy, joint, andcombined forces air operations systems. Thesesystems also interface directly with fire supportsystems.

The MACCS provides the tactical air commanderwith the automated support required to exercisecontrol over MAGTF air operations. MACCSsupports tactical air command, tactical air opera-tions, air defense, and direct air support. Person-nel dedicated to these systems provide support fortheir installation, operation, and maintenance. TheMWCS provides the multichannel communica-tions connectivity that links the airfields and for-ward sites, as well as the long haul single channelradio support between higher and adjacent com-mands and the wing headquarters and TACC.

a. Tactical Air Command SystemsTactical air command systems provide the tacticalair commander with support for planning, control-ling, and coordinating overall MAGTF air opera-tions. Functions supported include determinationof operational requirements, allocation of aircraft,publication of ATOs, planning of air operations,coordination and supervision of execution, andcoordination with naval and joint agencies.CTAPS, one of the mission applications support-ing tactical air command, is used to create anddisseminate the ATO. The Joint Chiefs of Staff


have mandated the use of CTAPS for joint ATOdissemination. CTAPS runs at the secret level onUNIX-based MCHS servers on the TACC LAN.The MWCS provides each CTAPS workstationwith an IP host address and connects the TACCLAN to remote airfields, DASC, TAOC, and oth-er Service command centers over SIPRNET byusing IP routers and organic transmission assets.Tactical air command systems are evolving toprovide improvements in a number of areas, in-cluding migration to common hardware and DIICOE compliance, mobility, and Joint Tactical In-formation Distribution System (JTIDS) integra-tion. Through such enhancements, tactical aircommand systems will provide the automatedtools needed to effectively plan, coordinate, anddirect all MAGTF tactical air operations.

b. Air Defense SystemsThe Tactical Air Operations Center (TAOC) isthe C2 agency that controls tactical air operationsand coordinates the air defense of the MAGTF.The TAOC consists of the AN/TYQ-23(V)1 Tac-tical Air Operations Module (TAOM) and associ-ated sensors, the AN/TPS-59, AN/TPS-63, and itsreplacement, the AN/MPO-62 radars, and the sec-tor antiair warfare facility. The TAOM providesautomated support for surveillance, weapons con-trol, air traffic control, and training. The operatorconsole of the TAOM is being upgraded to pro-vide GCCS functionality and a Windows inter-face. The Sector Antiair Warfare Facility providesthe tactical air picture from the TAOM to the sec-tor antiair warfare coordinator and enables an au-tomated interface between CTAPS and TAOMfor passing the ATO. JTIDS implementation isongoing and will provide greatly enhanced, se-cure, high-capacity, jam-resistant information dis-tribution capabilities as well as improvedinteroperability for the conduct of joint air de-fense and theater missile defense operations.

c. Direct Air Support SystemsThe high-mobility downsized DASC provides au-tomated support to the DASC for the conduct ofair operations directly supporting ground forces.It provides support for the coordination of closeair strikes, assault support, and air reconnaissancemissions. The high-mobility downsized DASC is

an integrated system that consists of five light-weight multipurpose shelter Type-1 systemsmounted on M-1097 heavy HMMWVs. Eachoperations shelter contains five operator worksta-tions capable of conducting integrated aviationC2 functions. Each high-mobility downsizedDASC vehicle tows an M-116 trailer that carries agenerator and external cables. The trailers associ-ated with the operations suites also carry onequick-erect shelter. The system design allows formaximum employment flexibility to support anylevel of MAGTF operations, providing the FMFwith a lightweight, highly mobile system that iscapable of responsive direct air support C2.

3307. Fire Support

Fire support systems support the planning, coordi-nation, and control of artillery, air, and naval gun-fire.

a. Fire Support Command and Control System (FSC2S)The FSC2S is designed to meet the basic require-ments for a fully automated fire support system. Itprovides initial semiautomated tactical fire sup-port and technical artillery fire control functionsfor MAGTF operations. The follow-on AFATDScompletes the transition to fully automated firesupport C2. There are two components to theFSC2S: the fire control system and the batterycomputer terminal.

The FSC2S is employed at FDCs down throughthe firing battery level, at FSCCs down throughthe battalion level, at the SACC, and by theMAGTF CE to support fire planning and tacticalfire direction. The FSC2S is supported by digitalfire support communications nets.

b. Advanced Field Artillery Tactical Data System (AFATDS)The AFATDS is a joint Army/Marine Corps sys-tem which will replace the initial fire support au-tomated system (IFSAS). It is a multi-service,integrated, battlefield management and decisionsupport system which incorporates automation in-to the fire support warfighting function to assist

3-14 _______________________________________________________________________________________________ MCWP 6-22

the commander in the planning, delivery, and co-ordination of supporting arms. These terminalswill be located in FSCCs, DASC, TACC, and ar-tillery battalion and regimental FDCs. AFATDSwill provide the MAGTF commander with the ca-pability to rapidly integrate ground, air, and navalsurface fire support with the scheme of maneuver.The AFATDS software architecture is interopera-ble with Marine Corps CIS, GCCS COE, andMAGTF C4I baseline systems.

3308. Logistics

LOG systems support logistic planning and oper-ations. These include all logistic functions sup-po r t i ng dep loymen t , emp loymen t , andreconstitution of forces.

There are two basic uses for information: to pro-mote situational awareness as the basis for a deci-sion and to direct and to coordinate actions in theexecution of that decision. There are currentlyover one hundred logistic information systemsutilized within the Marine Corps to support ForceDeployment Planning and Execution, sustainmentand distribution. Biannually, the Installations andLogistics Department, Headquarters MarineCorps publishes a comprehensive listing of thesesystems in a Logistics Information ResourcesPlan (Log IR Plan). The Log IR Plan provides aroadmap for how logistics information systemswill utilize information technology methods. It al-so provides a migration strategy that tailors thenumber of systems by eliminating redundanciesand leveraging joint systems where appropriate.While by no means a complete listing, the follow-ing provides a top down view of the significant ofinformation systems currently in use to supportforce structure, movement, sustainment, materielreadiness, and fiscal management.

a. Systems in Support of Operations

(1) Standard Accounting, Budgeting, and Re-porting System (SABRS). SABRS is a DODautomated system used by Marine Corps fiscalplanners to account for and report expenditures ofappropriated funds and for use in submissions tothe DOD budget cycle.

(2) MAGTF II/Logistics Automated InformationSystem (LOGAIS). This family of systems sup-ports Marine Corps ground logistic data require-ments. The MAGTF II system is the primaryplanning tool for selecting and tailoring aMAGTF and for providing updates to JOPES tosupport FDP&E. It includes TC-AIMS andMDSS II. TC-AIMS II, a joint system, will even-tually replace TC-AIMS and MDSS II. TC-AIMSand ATLASS will be the primary systems thatprovide functional logistics management for sus-tainment and distribution.

(3) Transportation Coordinators’ AutomatedInformation for Movement System (TC-AIMS). TC-AIMS provides automated support for motortransport control, planning of support, and coordi-nation of overland movement and convoys. Itmanages use and movement of day-to-day motortransport and heavy equipment. Its resource-man-agement module provides inventory, support re-quests, and task and dispatch management. Itsupports convoy management with an embarka-tion and marshaling module. It tracks criticalevents, including user time statistics. TC-AIMSinterfaces with the MAGTF Deployment SupportSystem II (MDSS II). This system, along withTC-AIMS, assists in deployment planning and ex-ecution and unit movement at the MEF level andbelow. The integrated MAGTF/LOGAIS soft-ware will enable an improved degree of integra-tion between MDSS II and TC-AIMS.

(4) Theater Medical Information Program(TMIP). TMIP provides a global capability thatlinks medical information databases to integrationcenters; these integration centers are accessible toNavy medical personnel while engaged in supportof Marine forces. The goal for TMIP is to providetheater medical integrated automated informationusing Global Command and Control System(GCCS) and Global Combat Support System(GCSS) that links all echelons of medical care insupport of Marine forces.

(8) MDL. MAGTF Data Library is the datadictionary tool used to facilitate gathering of validsource data for use by all of the MAGTF/LOG-AIS family of systems.


(5) MDL. MAGTF Data Library is the datadictionary tool used to facilitate gathering of validsource data for use by all of the MAGTF/LOG-AIS family of systems.

b. Systems in Support of Materiel Readiness

(1) Global Status of Resources and TrainingSystem (GSORTS). GSORTS provides informa-tion on the readiness status of units with respect topersonnel, equipment, and training.

(2) Asset Tracking Logistics and SupplySystem (ATLASS). ATLASS provides automat-ed support for supply and maintenance. It replacestwo mainframe-based systems developed in theearly 1970s—the Marine Integrated MaintenanceManagement System (MIMMS) and the Support-ed Activities Supply System (SASSY)—with aclient-server system based on an open systems ar-chitecture. ATLASS is being implementedthrough phased development, with the currentphase focusing on integrating user-unit supplyand shop-level maintenance functions.

(3) Naval Tactical Command Support System. NTCSS is a fleet tactical command support sys-tem used by the ACE. NTCSS replaces 1970s vin-tage fleet equipment with modern minicomputers,personal computers, and local area networks. Itprovides status and ad hoc reports to the BattleGroup Logistics Coordinated Support System(BGLCSS). The system is formulated aroundSNAP III, which began the process of integratingshipboard computers by adopting the commandand control systems architecture for commandsupport applications.

(4) Shipboard Nontactical ADP Program III(SNAP III). The Marine wing support group(MWSG) and MALS use SNAP III hardware toprovide automated information processing sup-port for supply, finance, and organizational main-tenance management.

(5) Naval Aviation Logistics Command Man-agement Information System (NALCOMIS). MWSG and MALS use the NALCOMIS softwareapplication to provide automated information pro-

cessing support for maintenance of all aviationequipment and spares to aviation units and select-ed base and garrison activities throughout theMarine Corps.

(6) Shipboard Uniform Automated Data Pro-cessing System (SUADPS). This is the supplysoftware application used by MALS to provide fi-nancial, inventory, and logistic management ofaviation supply support for Marine aircraft.

(7) Conventional Ammunition Integrated Man-agement System (CAIMS). CAIMS provideson-line inventory management data such as am-munition location, quantity, material condition,purpose code, and requisition status.

3309. Force Deployment Planning

Force deployment planning systems support plan-ning for the movement of forces and their sustain-ment from original locat ions to specif iedoperational areas. The MAGTF II system supportsdeployment planning. It enables Marine deploy-ment planners to conduct both deliberate and time-sensitive (crisis action) planning. By usingMAGTF II , planners can select and tai lorMAGTFs and estimate sustainment and lift re-quirements. MAGTF II is a PC-based system thatsupports TPFDD development and maintenance,with the results uploaded to JOPES. MAGTF IIcan operate on a LAN, although system users andadministrators must be mindful of security con-cerns. Because of its usability, versatility, andportability, MAGTF II has been nominated as amigration system that will, with specific modifica-tions, serve all Services and the Joint Staff as anautomated tool to support deployment planningand execution. For detailed information on forcedeployment planning, see Joint Pub 5-03.1, JointOperation Planning and Execution System, Vol-ume I.

The MAGTF C4I systems described above nor-mally operate on LANs in various C2 facilities ofthe MAGTF. A notional layout of the systems thatsupport COCs is in figure 3-3 (on page 3-16).

3-16 _______________________________________________________________________________________________ MCWP 6-22

Figure 3-3. Supporting Systems.


Section IV

The Defense Message System

DMS is an evolving system that consists of allhardware, software, procedures, standards, facili-ties, and personnel used to exchange messageselectronically between organizations and individ-uals in the DOD. The current subsystems of theDMS are the automated digital network (AUTO-DIN) (which includes base-level support systems)and e-mail. DMS will have a store and forwardcapability. The DMS must support interfaces tosystems of other government agencies, allies, tac-tical systems, and defense contractors. System us-ers may be deployed or in garrison, fixed ormobile. The planned or objective system will re-place the current subsystems, based on DODstandards, with a single system based on interna-tional standards established by the InternationalOrganization for Standardization (ISO). Securityservices, including authentication, integrity, con-fidentiality, and registration, are provided throughthe Fortezza Personal Computer Memory CardInternational Association (PCMCIA) card, whichis discussed later in this chapter. The primary ob-jective of the DMS is to maintain existing serviceand security while reducing cost and staffing.

3401. AUTODIN

The transition to the objective system involves re-placing AUTODIN delivery systems and existinge-mail capabilities based on the simple mail trans-fer protocol (SMTP) with e-mail based on the ISOX.400 message handling protocol and the sup-porting X.500 ISO standard for directory services.The transition also involves transitioning the se-curity and service management infrastructure. Fi-nal AUTODIN closeout is scheduled for 31December 1999. Remaining non-DMS message

systems will be phased out and DMS capabilitieswill be upgraded by the end of calendar year2008. Services and agencies have been tasked todevelop transition plans for implementation of thenew system and have been asked to include sup-ported CINCs in their plans. DMS has been desig-nated the single DOD message system and will beintegrated with all applications that have embed-ded messaging functions, such as GCCS.

3402. Upgrades

Joint requirements, policy, doctrine, and architec-ture and a transition plan for interfacing and in-corporating tactical users into the DMS are stillunder development. At present, tactical messagetraffic enters the long-haul network primarilythrough AUTODIN switching centers and auto-matic message processing exchanges. The AU-TODIN interface into the DMS is scheduled to bephased out by 31 December 1999; therefore, theimpact on tactical users, including the need to in-teroperate with legacy tactical message switches,will be felt over several years. The primaryMAGTF message handling system replaced byDMS is the AN/MSC-63A message switch. DMSalso replaces VINES mail, a proprietary messag-ing system used throughout the Marine Corps.DMS will improve tactical messaging by provid-ing a seamless system across the strategic and de-ployed environments. It provides a secure, timely,reliable writer-to-reader messaging service. TheDMS program helps to integrate the tactical andstrategic environments and is a key component ofthe DII. CJCSM 6231.03A, Joint Data Systems,provides additional detailed information about theDMS.

3-18 _______________________________________________________________________________________________ MCWP 6-22

Section V

Information Services

Information management and exchange are sup-ported not only by the information systems de-sc r ibed p rev ious ly , bu t a l so by commoninformation services hosted on servers throughoutthe MAGTF. Many of these information serviceshave already been mentioned as part of the DIICOE and the MAGTF C4I Software Baseline. Fig-ure 3-4 shows these services, which are describedin the following paragraphs. These services en-able the flow of information over the communica-tions networks supporting the MAGTF.

3501. Directory Services

Directory services consist of Marine Corps stand-ard network directory service application, the do-main name system (DNS), and X.500. The MarineCorps standard network directory service applica-tion is Banyan Street Talk Directory Assistance.As mentioned above, X.500 is the ISO standardfor directory services that supports X.400 messag-ing and will be part of DMS. DNS is a directoryservice that links Internet domain names to the IPaddresses specified by network administrators.The DNS organizes the names of hosts in a hierar-

chical fashion, much like a file system. The re-mainder of the domain name is administered bythe network administrator of the subnetwork, andthe subnetwork is often broken up into additionalzones to ease administration. The network admin-istrator is responsible for setting up name serversto handle requests for domain name-to-addressresolution for the network administrator’s zones.

3502. Terminal Emulation Services

Terminal emulation services provide the capabili-ty for remote users to access logistic and person-nel applications hosted at DISA megacenters.Remote logins are supported through a synchro-nous terminal emulation using the TELNET pro-tocol.

3503. Message Handling Services

Message handling services provide message stor-age, transfer, forwarding, routing, translation, andformat conversion. Services include SMTP, mul-tipurpose Internet mail extension (MIME), andACP 123 message handling capability.

3504. Network Management Services

Network management services link a NetworkManagement System and networked devices (e.g.,servers) being managed. Network management isprovided through the simple network manage-ment protocol (SNMP) Through SNMP the sys-tem administrator is alerted when traffic patternsand conditions indicate that a networked device isfailing or has failed. A network manager can setthresholds for devices and receive an alarm whenthe threshold is reached.

Communications Mission Application

Fax File

Message Database

Security/Firewall Network OperatingSystem

Defense MessageSystem

Network Management

World Wide Web Directory

Print Domain Name

Network Administration TELENET 3270

Figure 3-4. Information Services.


a. Configuration ManagementConfiguration management includes resource ser-vicing, testing, and reporting; software distribu-tion and licensing; planning; and management.Configuration management also includes the plan-ning and use of directories. Configuration man-agement requires maintenance of completerecords of users, assignments, equipment, and oth-er information needed to administer the network.Planning support consists of development, dis-semination, and coordination of letters of instruc-tion, Annex K for OPLANs\OPORDs, routingtables, address assignments, and message han-dling instructions.

b. Fault ManagementFault management consists of fault determination,correction, prevention, reporting, and archiving.File server backup and recovery functions consistof providing backup and recovery services locallyand from one server to another in the network.

c. Performance ManagementPerformance management consists of perfor-mance and traffic characterization, performancetesting, performance timing and correction, con-trol of performance management, reporting, andarchiving.

d. Security ManagementSecurity management consists of configurationmanagement of security components, securitymechanism management (including identificationand authentication, discretionary access control,object reuse, and the use of audit trails), systemvulnerability reduction, and other methods to pre-vent security breaches. Figure 3-5 (on page 3-20)is an outline of the interactions and relationshipsbetween the various MAGTF C4I services andprotocols.

3505. Security Services

Information systems security is discussed in depthin chapter 7.

a. Fortezza CardsThe Fortezza card is a security component thatprovides user privileges for sending and receivingDMS messages. The Fortezza cards include pri-vate security keys and user messaging privileges.User messaging privileges include individual mes-saging and organizational message release, in-cluding organizational level, precedence, andclassification authorized. Directory queries forDMS directory services are authenticated by thedigital signature function of the Fortezza PC cardto allow access to the X.500 directory. The Fortez-za PC cards are programmed by using the certifi-cation authority workstation.

b. Certification Authority WorkstationThe certification authority workstation is a PC-based application used to program and maintainFortezza PCMCIA cards for users. These Fortez-za cards (one per person) include not only privatesecurity keys, but also the user messaging privi-leges. Local authorities use the DMS agent soft-ware applications resident in the certificationauthority workstation to perform distributed di-rectory and security management tasks. Thistrusted workstation supports functions that in-clude decentralized assignment of directorynames and creation of X.509 certificates. As partof this process, the applications initialize each us-er’s Fortezza card with a personal identificationnumber (PIN), X.509 certificate(s), and selectedDMS information.

c. In-line Network EncryptorsIn-line network encryptors use the Secure DataNetwork System standards from the National Se-curity Agency and interface to the National Elec-tronic Key Management System. In-line networkencryptors provide end-to-end security betweenhosts and workstations running on secure LANs.In-line network encryptors allow secure commu-nications over public, packet-switched, and un-classified backbone networks. In-line networkencryptors incorporate an open architecture.

3-20 _______________________________________________________________________________________________ MCWP 6-22

3506. Facsimile Services

Facsimile services allow the sending and receiv-ing of electronic text, graphics, and imagesthrough the switched telephone network. The fac-simile server provides storage, routing, and trans-lation of data.

3507. Communications Services

Communications services provide communica-tions management between LANs and WANs.

This server provides dynamic addressing and rout-ing services that allow automated selection of thepooled communications resources at a central lo-cation. It interfaces with the message handler andthe TCIM to provide automated radio networkmessage addressing and routing. This server sup-ports Marine tactical systems, Transmission Con-trol Protocol (TCP)/IP, e-mail, file transfer,SNMP, and SMTP.

Figure 3-5. MAGTF C4I Services and Protocols.


Section VI

Shipboard Information Systems

Naval amphibious ships provide CIS support toembarked Marine forces as well as spaces fromwhich to exercise command and control. Avail-able shipboard information system support willseldom fully satisfy the requirements of the em-barked Marine force and, consequently, will re-qu i re augmenta t ion by o rgan ic MAGTFinformations systems support resources.

3601. Key Resources

Appendix I is an overview of the various CIS re-sources available on amphibious ships. However,the actual CIS support available on amphibiousships varies, even between ships of the sameclass, based on system installation and upgradeschedules. Specific configurations, includingidentification of software release versions, mustbe determined during pre-deployment and embar-kation planning. Figure 3-6 (on page 3-22) depictsthe information systems and equipment typicallyavailable on amphibious ships, focusing on com-munications resources and LANs that are key toshipboard command and control.

3602. JMCIS-Afloat

JMCIS-Afloat (formerly known as Navy TacticalCommand System-Afloat [NTCS-A]) providesthe tactical commander with timely, accurate, and

complete all-source information management,display, and dissemination capabilities. These in-clude multisource data fusion and distribution ofcommand, surveillance, and intelligence data andimagery to support warfare mission assessment,planning, and execution. JMCIS-Afloat is DIICOE compliant and shares the JMCIS UnifiedBuild software with TCO. This commonality per-mits the MAGTF to operate TCO in the LFOCand the IAS in the JIC.

JMCIS-Afloat includes the NIPS database inter-face and the national, regional, and organic sensorintelligence and environmental databases. TheJDISS and other services described in the GCCSsection are also included in JMCIS-Afloat. Em-barked MAGTF commanders can access and usethe JMCIS-Afloat services by using MAGTF and/or shipboard computers (with prior coordination)on ships’ LANs. Flagships such as CV, CVN,LHA, LHD, and LCC have been upgraded to thelatest version of JMCIS, while most of the unit-level platforms such as CG, DD, DDG, LPD,LPH, and LSD ships are using older software ver-sions that have incompatibilities with theMAGTF C4I Software Baseline. Upgrades arecontinual; until the Navy can achieve a coordinat-ed simultaneous software update with the MarineCorps, this condition requires that MAGTF CISpersonnel adapt and find ways to make the net-works provide the required services.

3-22 _______________________________________________________________________________________________ MCWP 6-22

Figure 3-6. Amphibious Ship Information Systems.

Chapter 4

Defense Information Systems Network

The goal of DOD communications architects is asingle, integrated, common-user, global commu-nications network. This network, the DISN, willprovide support for exchange of voice, data, im-agery, and video from strategic to tactical levels,at all echelons, in garrison or when deployed.DOD and the Services are implementing DISN inan evolutionary manner by interfacing and inte-grating existing communications networks andmaximizing commercial services and standards.

Just as GCCS and the DII COE are shaping thefuture of MAGTF C4I systems, DISN implemen-tation is shaping the Marine Corps tactical com-munications architecture. For the near term, thecommunications networks supporting theMAGTF will include the current MAGTF tacticalcommunications networks, the Tri-Services Tacti-cal Communications System (TRI-TAC) switchedbackbone, SCR, LANs, and special-purpose net-works with an interface to DISN for long-haulcommunications (see chap. 5). However, changeis occurring rapidly with the introduction of rout-er-based data communications systems augment-ing the switched backbone and providingenhanced connectivity among tactical networksand between tactical networks and DISN.

DISN is the information-transfer segment of theDII. The objective of DISN is the creation of a sin-gle, integrated telecommunications infrastructurethat can provide end-to-end communications con-nectivity in support of military operations world-wide. DISN is evolving toward that objectivethrough continuous upgrades to switching andtransmission centers around the world and throughconsolidation and integration of satellite and ter-restrial communications networks. DISN currentlyprovides long-haul, common-user, dedicated, se-cure and nonsecure, voice, data, and video servicethrough a mix of both DOD-dedicated and stand-ard commercial communications services. DISN

provides the communications backbone for otherDOD-wide systems including the Secure VoiceSystem, DMS, Defense Data Transport Networknonsecure internet protocol router network (NIPR-NET) and SIPRNET, video teleconferencing, andJWICS, as well as separate systems and networksserving the CINCs, Services, and agencies.

4001. Tactical Entry Points

As a first step in DISN implementation, DISA es-tablished the Integrated Tactical-Strategic DataNetwork (ITSDN) to provide an IP router-baseddata network to support deployed forces. IP routernetworks are described later in this chapter. Ac-cess to ITSDN was provided through SIPRNETand NIPRNET gateways consisting of IP routersand appropriate encryption devices. ITSDN entrypoints were established at the following locations:

● Ft. Belvoir, VA.● Wahiawa, HI.● Northwest, VA.● Ft. Buckner, Japan.● Ft. Meade, MD.● Riyadh, Saudi Arabia.● Ft. Detrick, MD.● Landstuhl, Germany.● Camp Roberts, CA.● Croughton, United Kingdom.

These ten sites have been upgraded. The four siteslisted below have been established to provide 14DISA standard tactical entry points (STEPs).

● Ft. Bragg, NC.● Bahrain.● MacDill AFB, FL.● Lago Patria, Italy.

4-2 ________________________________________________________________________________________________ MCWP 6-22

Upgrades include installation of the Defense Sat-ellite Communications System (DSCS), the inte-grated digital network exchange (IDNX), and aninterface to the Navy Tactical Network. TheSTEP sites are also called Defense Communica-tions System entry points, GMF gateways, orDISN gateways. MAGTFs and forward-deployedforces use these STEP sites to access DISN toconduct training, exercises, and operations. Whenashore, the MAGTF’s primary means to accessthe STEP sites is through GMF tactical satellite(TACSAT) communications over the DSCS.Shipboard access is provided through the NavyTactical Network. Five entry points with Navy-unique configurations are located at naval com-puter and telecommunications area masterstations (NCTAMS) to provide both ship-to-shoreand ship-to-ship communications. Figure 4-1 de-picts a JTF notional architecture with a STEP siteand NCTAMS providing the DISN entry.

4002. DISN STEP Services

The services provided to the deployed MAGTFthrough the DISN STEP include voice, data, andvideo. Voice services consist of the DefenseSwitched Network (DSN) and, for secure voice,the Defense Red Switch Network. Data and videoservices are provided through NIPRNET, SIPR-NET, JWICS, and video teleconferencing.

a. DSNSTEP provides one T1 (1.544 Mbps) circuittranscoded to support 48 interswitch trunks to aDSN multifunction switch. These 32 kbps inter-switch trunks allow tactical users to place eithernonsecure or secure telephone unit-type III (STU-III) calls to a DSN subscriber.

b. Defense Red Switch NetworkA single STEP accommodates up to four 56 kbpscircuits to the Defense Red Switch Networkswitch. Each circuit provides two interswitchtrunks between the tactical and Defense RedSwitch Network switches. These eight interswitch

trunks allow tactical users to place secure redswitch calls from the field.

c. NIPRNETNIPRNET is an information network that is basedon IP routers and IDNX smart multiplexers. NI-PRNET is designed for sensitive but unclassifiedinformation transfer. It supports unclassified net-works such as the Marine Corps Data Networkand the Tactical Automated Weather DistributionSystem. Under the ITSDN program, 10 of the 14STEP sites were configured with NIPRNET rout-ers. MAGTFs use the NIPRNET both aboard shipand ashore to transfer administrative data.

d. SIPRNETSIPRNET is an information network based on IProuters and IDNX smart multiplexers and de-signed for exchanging classified information upto and including the secret level. It supports ex-changing classified data among GCCS, DMS,CTAPS, TCO, IAS, and other tactical informationsystems. SIPRNET routers are collocated withNIPRNET routers at 10 STEP sites. MAGTFs usethe SIPRNET both aboard ship and ashore totransfer operational data.

e. JWICSJWICS is an information network based on bothIDNX smart multiplexers and IP routers. It is de-signed for exchange of SCI-level video and datainformation. It supports the MAGTF’s use of IN-TELINK and other services such as those access-ed by using JDISS and TCAC. MAGTFs accessJWICS while aboard ship and in operationsashore.

f. Video TeleconferencingHigher echelons use video teleconferencing withincreasing frequency. Within the operating forc-es, it is used primarily for MAGTF-to-JTF/CINCcoordination. Currently, video teleconferencingsupports only point-to-point conferencing. In thefuture, multipoint conferencing will also be sup-ported.


4003. STEP Access

The STEP access process is different for theMAGTAF GMF/TRI-TAC terminals than it is forNavy shipboard terminals. The STEP accessequipment at the entry points is assigned to eitherGMF/TRI-TAC or Navy. The GMF/TRI-TAC ac-cess equipment is managed by DISA, and the Na-vy-unique access equipment is managed by theNavy. DISA manages the satellite power andbandwidth for DSCS. DISA also assigns MAGTF(i.e., GMF/TRI-TAC) users particular STEP sitesaccording to priority and equipment/service capa-bilities.

The various DISA monitoring centers that controlNIPRNET and SIPRNET router configurationsand programming are listed below. When a circuitis activated and a router-to-router connection ismade or attempted, the DISA monitoring center

must be contacted. A previously issued missiondirective (described below) references the DISAmonitoring center supporting an operation or ex-ercise. The DISA analyst ensures that all routersare configured properly to support the operation/exercise. DISA has the capability to modify rout-ing tables and configurations as required:

● Columbus, OH (NIPRNET Regional ControlCenter).

● Washington, DC (SIPRNET Regional ControlCenter).

● Oahu, HI (Pacific).● Vaihingen, Germany (Europe).

Procedures for GMF/TRI-TAC access to an entrypoint and satellite are described in the CJCSM6231 series. Theater-specific access proceduresare described in DISA contingency exercise plans.

Figure 4-1. JTF Notional Architecture.

4-4 ________________________________________________________________________________________________ MCWP 6-22

Theater access procedures for the western hemi-sphere (including the continental United States[CONUS]) are governed by Contingency Exer-cise Plan 10-95, for the European theater by Con-tingency Exercise Plan 1-96, and for the Pacifictheater by Contingency Exercise Plan 203-92. Ac-cess is initiated with the MAGTF G-6/S-6 requestto the theater DISA Contingency OperationsBranch and a satellite access request to the Re-gional Space Support Center, either directly orthrough the JTF J-6. The request specifies the ser-vices required. DISA responds with an SHF/GMFmission directive and a satellite access authoriza-tion. The mission directive is a message that iden-tifies entry points and points of contact to establishthe access. The priority and purpose of the request,based on the MAGTF mission, should determinethe speed at which entry point access is granted.

The mission directive also provides IP addressing,router information, port and channel assignment,and coordination points of contact for each datanetwork. For additional information on ITSDN,see the IP Addressing Plan and the CJCSM 6231series documents. The communication battalion’sdata network officer and system planning and en-gineering officer maintain copies of these andother DISA documents.

4004. Changes to DISN STEP Sites

Change is continuous in the DISN evolution.DISN sites and the tactical users must remainadaptable to obtain the more robust and flexibleservices provided by the upgraded IDNX back-bone. The joint communications support element(JCSE) that provides CINC/JTF support commit-ted funding for IDNX upgrades to meet the goalcommunications architecture. IDNX provides linkbandwidth management that allocates circuits asneeded. It allows for a virtual network with auto-matic routing and rerouting. It also sets the stagefor an evolutionary transition to the use of asyn-chronous transfer mode (ATM). As these changestake place, MAGTFs will require similar equip-ment to take advantage of the more robust global

network structure. For additional information, seeCJCSM 6231.07A.

4005. USMC Network Operations Center

Assistance from outside the MAGTF is availablefrom the USMC Network Operations Center. TheUSMC Network Operations Center provides tech-nical support for MAGTF and supporting estab-lishment WAN managers and acts as the primarypoint of contact for all Marine Corps operationalissues in the area of communications networking.The USMC Network Operations Center acts asthe Marine Corps Service-level representative toDISA, other DOD agencies, and commercial ven-dors concerning network operational issues andproducts.

The USMC Network Operations Center operates24 hours a day, 7 days a week supporting theMarine Corps communications infrastructure as awhole. It performs the following tasks:

● Reports/resolves problems.● Distributes networking software.● Provides network infrastructure components in-

ventory.● Serves as the Marine Corps network registra-

tion authority as assigned by the DISA networkinformation center.

● Provides centralized management and fundingof Marine Corps telecommunications servicesthat traverse DISN, NIPRNET, SIPRNET,LAN-WAN exchange, and IBM Systems Net-work Architecture networks.

● Serves as Service representative to DISA.● Coordinates Marine Corps and other Service/

agency telecommunications requirements.● Provides technical assistance teams to request-

ing units.● Maintains 16 permanently assigned NIPRNET

and 16 permanently assigned SIPRNET Class Caddresses for deployed MEU(SOC)s.

Chapter 5

MAGTF Tactical Communications Network

The MAGTF tactical communications networksupports information exchange requirements—voice, data, video, and imagery—both internal andexternal to the MAGTF. For external long-haulcommunications, the tactical communications net-

work interfaces to DISN. The MAGTF tacticalcommunications network must also interface withthe tactical communications networks of the otherServices.

Section I

Overview

This overview is designed to give all Marineswho use tactical communications an understand-ing of the capabilities and limitations of these net-works. This understanding, in turn, will assist inthe effective employment of these networks toconduct operations and accomplish assigned mis-sions.

5101. Architecture

The tactical communications network is com-posed of numerous subnetworks that interfacewith one another in varying degrees. These sub-networks themselves are usually referred to asnetworks. Figure 5-1 depicts the four types ofsubnetworks—SCR, local area networks, SBB,and special purpose systems. Each is described insections II–V.

The Marine Corps tactical communications archi-tecture is rapidly evolving to meet the informationtransfer requirements of the MAGTF and to takeadvantage of new technology. Changes in the ar-chitecture are also driven by the requirement tointerface with DISN and to be interoperable withthe other Services.

5102. Challenges

The rapid pace of change provides the CIS com-munity with both challenges and opportunities.Perhaps the most critical challenge is to providemaneuver battalions with adequate data commu-nications capability. The ability to provide the

Figure 5-1. MAGTF TacticalCommunications Network.

5-2 ________________________________________________________________________________________________ MCWP 6-22

shared situational awareness so critical to the suc-cessful execution of any operation depends onmeeting this challenge and others. The fundamen-tal requirement remains unchanged—to providethe MAGTF with a reliable, secure, fast, and flex-ible communications network.

The design of the actual communications archi-tecture to support a MAGTF is based on the na-ture of the operation, the commander’s (JTF,ATF, MAGTF) intent, the concept of operations,and the composition and task-organization of theMAGTF as well as that of attached and support-

ing forces. In the early stages of an operation,SCR usually provides the principal means ofcommunications. As the operation evolves, LANsand SBB networks are established to meet the in-formation transfer requirements of command andcontrol at higher echelons. Maneuver battalionscontinue to depend on SCR throughout the opera-tion with limited radio interface extensions to theSBB. Special-purpose systems provide dedicatedcommunications support for certain functions,such as position location and navigation and airdefense.


Section II

Single Channel Radio

SCR is the principal means of communicationssupport for maneuver units. SCR communicationsequipment is easy to operate, and networks areeasily established, rapidly reconfigured, and, mostimportantly, easily maintained on the move. SCRprovides secure voice communication and sup-ports limited data information exchange. SCR inthe VHF and UHF bands is normally limited toline of sight. In the HF band, SCR can supportlong-range communications, albeit at the expenseof mobility. SCR SATCOM provide mobility,flexibility, and ease of operation with unlimitedrange. Limitations of SCR include susceptibilityto enemy electronic warfare; cosite, footprint, ter-rain, and atmospheric interference; the require-ment for close coordinat ion and detai ledplanning; a need for common timing, frequency,and equipment; and limited spectrum availability.The latter is particularly critical in the case ofSATCOM.

MAGTF SCR equipment is fielded in many con-figurations and includes hand-held, manpack, ve-hicle-mounted, ground-mounted, and shelteredradios. These radios operate in simplex and half-duplex modes. The most widely employed tacticalradios provide integrated COMSEC and jam re-sistance through frequency hopping. TacticalSCRs operate in the three military radio frequen-cy bands shown in table 5-1. Characteristics ofeach category are discussed in paragraphs 5201through 5203.

SCR is used primarily for secure voice communi-cations. However, SCR can also transmit and re-ceive data by using terminal devices such as theDigital Message System (previously called andmore commonly known as the Digital Communi-cations Terminal [DCT]) and the TCIM. TheDCT and the TCIM are described in this sectionbecause of their critical role in enabling data com-munications at the tactical level over SCRs. (Seeapp. A.)

Table 5-1. Ground SCRs.

Frequency Band

MAGTF SCR Equipment Used

Operating Frequency

Range Typical Application

HF AN/PRC-104AN/GRC-193AN/MRC-138

2–29.999 MHz Radio line of sight and beyond/long range

VHF AN/PRC-68AN/PRC-77VRC-12 familySINCGARS family

30–88 MHz Radio line of sight and relay/retransmission

AN/PRC-113AN/VRC-83

116–150 MHz Critical line of sight (ground to air)

UHF AN/PRC-113AN/VRC-83AN/GRC-171

225–400 MHz Critical line of sight (ground to air)

AN/PSC-3AN/PSC-5

SATCOM footprint

5-4 ________________________________________________________________________________________________ MCWP 6-22

5201. HF Radio

HF radio equipment is capable of both long- andshort-range secure voice and data communica-tions. Data communications capability is typicallylimited to rates of 2.4 kbps. Data transmission re-quires modems specifically designed for opera-tion in this band of the radio spectrum. MAGTFHF radio equipment includes the AN/PRC-104manpack, the vehicle-mounted AN/MRC-138, theAN/GRC-193, and the AN/TSC-120 with auto-matic link establishment capability.

The primary advantage of using HF radio is its ca-pability to provide long-range, OTH communica-tion. Successful data communication over the HFrange depends on several factors: equipment sit-ing, proper equipment grounding, types of anten-nas used , t ac t ica l employment of rad ioequipment, path assessment and analysis, and fre-quency planning and assignment. When commer-cial data terminal equipment (DTE) is used, usersemploying HF radio equipment need to be awareof radio interference and potential shock hazardsthat can easily affect unprotected DTE. Wheneverpossible, HF radio equipment should be remotedfrom DTE.

The primary limiting factors when using HF radi-os are frequency allocation/management andbandwidth availability. Frequency allocation/management is concerned with frequency, time ofday, time of year, and location. The ability to re-flect HF radio waves off the ionosphere to a dis-tant location is in a constant state of flux becauseof activity in the ionosphere.

The sun’s radiation causes disturbances in theionosphere, with most changes taking place inwhat is known as the F-layer. Sunrise and sunsetcan be the most difficult times for HF communi-cations. The F-layer splits into two separate layersaround sunrise and recombines into one layeraround sunset. These splits affect transmissiondistances as the area “skipped over” increases anddecreases. At times, solar storms can completelyeliminate all HF communications.

HF transmission paths must be constantly moni-tored to achieve a dependable HF link. HF radiodata communications capabilities are limited bythe bandwidth that is imposed by legal constraintsand the physics of the spectrum. The bandwidthavailable in the HF spectrum limits the channelbandwidth, which in turn limits data throughput.

5202. VHF Radio

The primary MAGTF VHF radio is the singlechannel ground and airborne radio system (SINC-GARS). SINCGARS is a family of lightweightcombat radios that serves as the primary means ofcommunications for command and control andfire support on the battlefield. SINCGARS is thestandard VHF-frequency modulated (FM) tacticalradio for the Marine Corps, replacing the AN/PRC-77 and the AN/VRC-12 family. The systemprovides high security against threat EW by usingfrequency hopping with integrated COMSEC. Itis capable of voice and data transmission (up to16 kbps under optimum conditions and over limit-ed distances) over the VHF-FM frequency rangeof 30–87.975 MHz.

There are seven different SINCGARS configura-tions available, depending on the requirements ofthe user. These configurations include the man-pack, typically used in infantry operations, and ve-hicle-mounted variants. The radio provides voicecommunications ranges of up to 8 km for the man-pack and 35 km for vehicular configurations. SIN-CGARS is capable of remote operation by usingthe analog AN/GRA-39B radio remote control,the digital HYX-57 wire-line adapter, or the digi-tal C-11561(C)/U remote control unit (RCU).

a. Systems Improvement ProgramThe SINCGARS radio has undergone a systemsimprovement program (SIP). This radio is re-ferred to as the SINCGARS SIP. The primary im-provements relate to the data transmissioncapabilities of the system. A forward error correc-tion appliqué‚ was implemented in the receiver/transmitter and a new packet data mode wascreated to better support packet networks. An im-proved channel access protocol was added which


optimizes data throughput performance whileminimizing impact on voice communications onthe same SINCGARS channel.

The SINCGARS SIP radio is also available in adownsized version, the result of an advanced sys-tems improvement program (ASIP). This radio isreferred to as the SINCGARS ASIP. This radiowill retain all the functionality of the full size SIPradio in half the size at a total weight of 7.6pounds (including the battery). The radio is inter-changeable with previous SINCGARS versions,including the capability to be mounted in oldervehicular adapter assemblies. A new feature ofthe SINCGARS ASIP provides a retransmissioncapability while operating in the packet datamode and will also employ a new fast channel ac-cess protocol for improved operations in sharedvoice/data nets.

The AN/ARC-210 multipurpose radio supportssingle-channel air-to-air, air-to-ground, andground-to-air communications in tactical Navy/Marine Corps fixed- and rotary-wing aircraft. Ithas the capability to transmit and receive VHF-FM, VHF-amplitude modulation (AM), and UHF.It is compatible with SINCGARS in the frequen-cy hopping mode, as well as with HAVE QUICKand HAVE QUICK II frequency hopping UHFradios, and it can accept 25 preset single-channelfrequencies. The AN/ARC-210 requires a TSEC/KY-58 encryption device to encrypt transmissionsand decrypt received signals.

b. Employment ConsiderationsAttention to operator maintenance of the radioequipment, antennas, cable assemblies, andequipment grounding, as well as site planning andselection, is essential to reliable communications.Frequency separation, radio antenna separation,remote keying when using COMSEC, and poweroutput are significant employment factors.

When operating with some Navy ships, SINC-GARS may be limited to the single-channelmode. When SINCGARS is employed in the fre-quency hopping mode, the following operatingfactors need to be taken into account: hopset (fre-quency segment allocation), time of day (system

clock), antenna placement (cosite interference ismore of a concern than in the single-channel oper-ating mode), and power setting. SINCGARS radi-os configured for different hopsets that dial intothe same numbered net will not be able to com-municate. MCRP 6-22A, TALK II-SINCGARS:MSCP for the Single Channel Ground and Air-borne Radio System, provides detailed informa-tion on the employment of SINCGARS.

VHF SCR is the primary communications systemfor combat and combat support units while on themove. The predominant mode of operation is se-cure voice. However, use of VHF radio for datacommunication will increase with the fielding oftactical information systems at the battalion leveland below.

Small, handheld VHF radios are used at the small-unit level in the MAGTF. These radios are oftencommercial items that lack compatibility withSINCGARS and do not have integrated COM-SEC. Their use should be governed accordingly.

c. Environmental LimitationsThe primary limiting factors when using VHF ra-dios are range and frequency availability. VHF ra-dios can provide reliable communication forranges of up to 10 miles, depending on the equip-ment operating constraints and the operating envi-ronment. When employing radios that operate inthe VHF spectrum, consideration must be given tounit location. Most circuits are limited to radioline of sight, known as 4/3 earth curvature. VHFradio signals essentially follow the curvature ofthe earth to a distance that is approximately 1/3greater than the distance to the horizon. Foliageinterferes with VHF signals and may reduce nor-mal operating ranges to significantly less than 10miles.

5203. UHF Radio

Military UHF radio equipment operates in the116-150 MHz upper VHF frequency range and the225-400 MHz military UHF radio spectrum.MAGTF UHF radio sets (AN/PRC-113, AN/VRC-83, and AN/GRC-171) are capable of data

5-6 ________________________________________________________________________________________________ MCWP 6-22

communication at 16 kbps under optimal condi-tions. MAGTF ground and airborne UHF radiosincorporate the HAVE QUICK electronic counter-counter measures capability and operate in single-channel and frequency hopping modes. TheHAVE QUICK UHF radio is capable of remoteoperation by using the AN/GRA-39B or HYX-57.

The UHF radios are used for forward air controlground-to-air communication. Line of sight be-tween radios is critical for reliable communica-tion. Significant range differences are encounteredbetween UHF radios employed for ground-to-airand ground-to-ground communications. Greaterrange is achieved when employed from ground toair because of the increased line of sight. Whenemployed in the frequency hopping mode, the fol-lowing operating factors must be understood forproper operation: hopset, time of day, antennaplacement, and power setting.

The primary limiting factor when using UHF radi-os is range (critical line of sight). Critical line ofsight can be described as “what you see is whatyou get.” As long as the radio’s antenna has opti-cal line of sight to another radio’s antenna, the twowill be able to transmit and receive. For this rea-son, UHF radios are primarily used in air-to-ground communications.

5204. EPLRS

EPLRS shares many characteristics with PLRS,but provides a significant increase in data com-munications capability over PLRS. Various datarates supporting a variety of broadcast and point-to-point modes are currently available. Thus,EPLRS will provide a dedicated data communica-tions capability between regiment and battaliontactical data networks (TDNs) within the groundcombat element, when fielded in FY-00. This net-work will also be extended to lower echelonsthroughout the MAGTF. EPLRS can also serve asa source for automated friendly position locationinformation (PLI) and navigation information in ahybrid community with PLRS, though datathroughput is reduced. A NCS-E(D) is currentlyrequired to establish an EPLRS communicationsnetwork, however, efforts are underway to contin-

ue to reduce its size. Ultimately a “laptop” com-munications network initialization capability isenvisioned, concurrent with increased functional-ity within the radio set itself. (See fig. 5-2.)

5205. UHF-TACSAT

The AN/PSC-5 Enhanced Manpack UHF terminalemploys both narrowband (5 kHz) and wideband(25 kHz) channels supporting 2.4 and 16 kbps da-ta transfer rates, respectively. UHF-TACSAT ra-dios are employed for long-range communication.Multiple-access schemes can operate either withfixed channel assignments to the various users orwith channels being assigned in varying fashionaccording to demand. The latter is called demandassigned multiple access (DAMA). With demandassignment the user makes a channel request, and,after a brief time lag, a channel is allocated. TheDAMA scheme of operation is employed onUHF-TACSAT to share available channels moreefficiently. The radio systems are compatible withthe KY-57 (wideband mode only), the KY-99 andANDVT (narrowband mode only), and the KG-84C (wideband or narrowband) COMSEC equip-ment. This radio equipment is also capable ofremote operations by using the AN/GRA-39B(narrowband mode) or HYX-57 (widebandmode).

a. Employment ConsiderationsBecause of its limited availability, the MAGTFemploys TACSAT primarily to support critical,long-range communications requirements (e.g.,communications support for deep reconnaissanceoperations or connectivity to the tactical echelonof a MEU(SOC) when deployed ashore). The AN/PSC-5 is the primary DAMA-capable TACSATradio available to the MAGTF.

TACSAT limitations include the competition foravailable frequency resources and channel timeon the satellite. If only narrowband channels areavailable, channel data rates are limited to 2,400bps. Channel congestion, noise, and network satu-ration will affect the information flow on satellitechannels and will require a significant reductionin the data transmission rates to sustain data com-munication. Transmit power selection can be


critical. Sometimes increasing the transmit powercan decrease net effectiveness. Larger directionalantennas provide increased signal gain, which in-creases the transmitted signal power. Antennasfor these systems are lightweight and fragile and,therefore, require constant maintenance and in-spection for proper operation.

b. Environmental LimitationsThe primary environmental limitations on TAC-SAT radios are signal propagation delay, locationon the earth, terrain masking, and weather effects.Timing between DTE can be a critical factor inSATCOM because the satellite, acting as a relaybetween radios, is about 25,000 miles away.There is approximately a one-fourth second prop-agation delay between sending and receiving sta-

tions. This delay can interfere with systems thatautomatically retransmit if an acknowledgment isnot received after a very short timeout period.

As unit location changes, the “look angle” (angleabove the horizon) to the satellite can affect netreliability. The orbit of a satellite allows it to cov-er a certain footprint on the earth. Satellites inequatorial orbit can cover large portions of theearth both north and south of the equator, but asthe user moves closer to the earth’s poles, theTACSAT terminal may exceed the satellite foot-print. This will cause intermittent or lost commu-nications. Terrain can also have this effect byinterfering with the satellite and TACSAT termi-nal line of sight. Thunderstorms, heavy snow-storms, and hail also affect satellite transmissions

Figure 5-2. EPLRS COE.

5-8 ________________________________________________________________________________________________ MCWP 6-22

both by damage to antennas and effect on theelectromagnetic environment.

5206. Commercial International Maritime Satellite

INMARSAT is a commercial L-band UHF sys-tem originally designed to support merchant ves-s e l s and c ru i s e sh ip s w i th t e l ephon i ccommunications. It is used by the military on asurge basis to satisfy demands that military satel-lites cannot meet. Significant restrictions on theuse of INMARSAT are its cost and lack of securi-ty. It is a pay-as-you-go service that costs $5–$8per minute. Because of these high usage costs,INMARSAT should be used only when other tac-tical communications cannot support the opera-tion effectively. The advantage to INMARSAT isits availability with minimum advance coordina-tion, although it could potentially become saturat-ed during a major crisis. Planning for use ofINMARSAT requires coordination and approvalfrom the MAGTF G-6/S-6 and arrangements forconnection and payment of bills.

To access the INMARSAT satellite constellation,the Marine Corps can employ any one of a varietyof manpack and mobile systems. These terminalscommunicate via satellite with a shore station thatprovides the connection to the global terrestrialnetwork. INMARSAT radio employment consid-erations and environmental limitations are muchthe same as those for military TACSAT.

5207. Data Communications

Although data communications will never com-pletely replace voice communications on the bat-tlefield, for certain functions it is essential.Examples are functions such as reconnaissance,where transmit time must be minimized, and firesupport, where rapid, accurate fire support requestprocessing is critical. Furthermore, as tactical in-formation systems such as TCO are fielded tolower echelons, the requirement for data commu-nications will expand dramatically.

a. DCT (AN/PSC-2)The DCT is a rugged, lightweight, microproces-sor-controlled, handheld message processor. Itprovides Marine users at all echelons with point-to-point and netted data communications and iscompatible with most MAGTF radio, wire, andencryption equipment. It supports data transfer upto 2.4 kbps in the analog frequency shift keying(FSK) mode and, depending on the transmissionmedia, up to 16 kbps in the digital basebandmode. The DCT allows the operator to enter andread data in both free text and fixed or variablemessage formats (VMFs). VMF is the tacticalmessage standard adopted by DOD for groundforces. All of the Services have agreed to use thisstandard.

DCT communications protocols and modulationtechniques are interoperable with those of theTCIM used at MAGTF CPs. DCTs are used bythe Army for both fire support and intelligenceapplications, and a DCT interface is available on-board the LHD-1 class of amphibious ships.

Forward air controllers, forward observers, Sting-er teams, and reconnaissance teams are the pri-mary users of the DCT. Employment of thisdevice enables one-time entry of the data, incorpo-rating burst transmission for reduced on-air time.The DCT supports standard message formats foraccurate, consistent, and machine-readable infor-mation exchange. Effective DCT employment re-quires training and a commander’s willingness totake the time required to set up data communica-tions nets rather than relying strictly on voicecommunications. Proper DCT operation results ina key command and control capability—the abili-ty to exchange data at the tactical level.

b. Data Automated Communications TerminalThe DACT is a small, tactical computer and com-munications terminal which gives users the capa-bility to receive, process, and transmit variousmessages, to include text and symbology, used bytactical data systems. The DACT will effectivelyreplace the DCT when it achieves full operationalcapability in FY 03, but will provide much greaterfunctionality below battalion levels. This will


include an embedded GPS receiver, the ability toshare a common picture of the battlespace, auto-mated data exchange, and MAGTF C4I networkconnectivity. The DACT will be transportable byfoot mobile Marines and mounted in tactical or ar-mored vehicles.

c. TCIMTCIM provides interfaces between MAGTF in-formation systems and communications systems.It is used to connect standalone terminals withSCR nets and to pool radio resources at operationcenters for more efficient use of equipment andfrequencies. TCIM provides operations centerswith the ability to receive and transmit a set ofstandard tactical netted messages processed bythe DCT and other tactical information systems.As an MCHS communications processor forMAGTF information systems, TCIM provides thedata network interface for MAGTF command,control, communications, computers, and intelli-gence information systems at various facilities,agencies, centers, and individual locations. It sup-ports data exchange over radio, wire, and TRI-TAC SBB networks.

Three types of TCIMs are available with varioussoftware versions that support a wide variety ofcommunications protocols. The three types in-clude an internal PC card, an external set of cardsmounted in a small metal box, and a PC card vari-ant that requires a compatible PCMCIA card slotin the computer. TCIM interfaces to the computerby using the open systems standard small comput-er system interface (SCSI) and the serial RS-232C(7-wire) interface. Programmable wire-line, mul-tipurpose, and radio port interfaces are providedon the network side of TCIM.

Communications protocols supported includeTACFIRE, combat net radio, battery computersystem, gun direction unit, Marine tactical sys-tems (MTS), MIL-STD-188-220A variable mes-sage format (VMF), commercial, Army mobilesubscriber equipment (MSE) tactical packetswitch network, and EPLRS X.25 packet switchprotocols. This network interface device allowsdata exchange with Marine and other Service ele-ments using compatible protocols. The DCT canexchange data with information systems that useTCIM.

5-10 _______________________________________________________________________________________________ MCWP 6-22

Section III

Local Area Networks

MAGTF LANs are data communications net-works designed to support information exchange,collaboration, and resource sharing in a particularagency, facility, center, cell, or geographic loca-tion. Because of the limited distances involved,network signal protocols can be designed to sup-port high data throughput—up to 100 Mbps, al-though 10 Mbps is more common. These LANsinclude terminal equipment connected to a trans-mission medium such as wire or fiber-optic cable.The terminal equipment exchanges data by usinga protocol that is compatible with the medium.MAGTF LANs use both copper wire and fiber-optic cable of various types configured to meetthe tactical information exchange requirements ofthe command. Specific LAN access methods,technologies, protocols, and equipment are em-ployed in a topology that connects the commands’information systems and services. This sectionaddresses the basic types of LAN media, topolo-gies (physical and logical layout or design), andaccess methods in use by the MAGTF.

This section describes the LAN environment andsome of its many implementations. MAGTF LANimplementations will change with time because ofcontinuous change in the technology and resultingcommercial products. DOD acquisition directivesrequire the Services to implement COTS andGOTS products where they are feasible and cost-effective. As these very products compete in thecommercial marketplace, it is incumbent on CISpersonnel to remain aware of these changes to beable to employ the most effective LAN cables, to-pologies, and access media in coordination withMarine Corps- and DII-specified standards.

5301. LAN Media

LAN media include copper-based coaxial andtwisted-pair cable used within local facilities,such as a regimental-level COC and fiber-opticcable used for higher-speed backbone connections

connecting multiple facilities in a large HQ com-plex. Fiber-optic backbone LANs are also usedaboard Navy ships in conjunction with copper-based coaxial and twisted-pair LANs within anoperational workspace such as the LFOC.

a. Unshielded Twisted-Pair CableUnshielded twisted-pair cable is increasingly thecommercial LAN cable of choice. Unshieldedtwisted-pair cable is economically priced, widelyavailable, and relatively easy to install, operate,and maintain, making it particularly attractive forMAGTF employment. The MAGTF requires thatLANs be easily and quickly set up and dismantledto support rapid and frequent displacements onthe battlefield. Less specialized installation equip-ment and training are major considerations driv-ing Marine Corps use of unshielded twisted-paircable. Twisted-pair cable comes in several gauges(more commonly referred to as categories in LANterminology), based on the number of twists perfoot, with categories 3, 4, and 5 being the mostdesirable for LAN connectivity. Smaller gauges,used for subscriber telephone line installations,should not be used for data transmission. Localnetworking using unshielded twisted-pair cablesrequires hubs or concentrators to provide retrans-mission of signals and assist in maintenance. Un-shielded twisted-pair LANs are not reliable inenvironments with high electromagnetic interfer-ence (EMI). In these environments, wire cablesmust be shielded, routed around interferencesources, or replaced with fiber-optic cable.

b. Shielded CableShielded LAN cable options include shieldedtwisted-pair and coaxial cable. Shielded twisted-pair cable has many of the advantages of un-shielded twisted-pair cable, but costs more inreturn for supporting greater segment lengths anda relatively limited shielding capability. Coaxialcable is available in both thick and thin diameters.Thick coaxial cable allows greater noise immuni-ty and longer cable runs than does thin coaxial


cable. Shielded LAN cables are used by MAGTFsonly when necessary to achieve greater distancewithout repeaters and as a lower-cost alternativeto fiber-optic cable.

c. Fiber-Optic CableFiber-optic cable provides high speed over longdistances with immunity to electromagnetic inter-ference. Greater levels of security are possiblewith this cable because it is very difficult to tap.Glass fiber-optic cable is many times more trans-parent than its plastic counterpart, and, therefore,it is the primary type used for LAN applications.This cable is available in single- and multimodefiber based on its light conducting or propagationcharacteristics. Single-mode fiber is much thinnerthan multimode fiber and provides higher trans-mission throughput at distances much greater thana few miles.

Single-mode fiber uses lasers as an intense lightsource and is the most expensive to install. Multi-mode fiber uses dispersed light signals; this re-duces its transmission throughput and its effectivecable length to distances of less than a mile. Mul-timode fiber uses the much more cost-effectiveand weaker light source provided by light-emit-ting diodes. Therefore, if a MAGTF fiber-opticLAN backbone capability made of interconnect-ing, 1-km or less segments is suitable, the cheapermultimode fiber capability would be acceptable.The MAGTF Fiber-Optic Cable System currentlyin the supply inventory can be used for the tacticaldata network (TDN) backbone, with appropriateconnector modifications.

Fiber-optic cables require two fibers to allow two-way (full duplex) communications. MAGTFfiber-optic cable is bundled with two fibers in asingle cable, but commercial fiber-optic cable isalso available as single-fiber cable. The glass fi-bers are surrounded by a reflecting wrap, a plasticcoating, a layer of tough material such as Kevlar,and an outermost jacket for protection. Two disad-vantages of fiber-optic cable are its low tolerancefor bends in the cable and poorly constructed ormaintained connectors. Light transmission toler-ances are critical for these cables to operate prop-erly.

d. Shipboard MediaIn an effort to improve information access and re-source sharing, upgrades to shipboard LANs areconstantly underway. As ships are cycled throughservice life extension, they receive the latest net-working technology. However, it may be severalyears between overhauls, leaving much of thefleet with older, less responsive networkingequipment. Many older shipboard LANs were in-stalled with thick coaxial cable, while newer ship-board LANs use both fiber-optic backbones andtwisted-pair or thin-wire coaxial cable extensionsfrom hubs to workstation terminals. EmbarkedMAGTFs do not use the older thick-cable LANsbecause they cannot adequately support multipleadditional users. In these cases, embarkedMAGTFs are often authorized to install their owntemporary, unshielded twisted-pair or thin-wirecoaxial LANs.

e. Media SelectionThe higher cost and increased complexity of in-stallation and maintenance of coaxial cable and fi-ber-optic LANs is sometimes outweighed by theircapability to span greater distances without re-peaters and, in the case of fiber-optic cable, muchgreater throughput capacity. This is particularlytrue in the choice of a backbone media to supporta larger HQ such as the MEF or an MSC. On theother hand, at the cells and centers of the largerHQ and at tactical echelons, regiment and below,media selection will be driven by ease of installa-tion and operation, and data throughput require-ments will not be as great. In most cases, this willlead to a choice of unshielded twisted-pair cable.

5302. LAN Topologies

LAN topologies are described by both their physi-cal configuration (bus, star, or ring) and their log-ical implementation. The most common physicaltopologies in use by the MAGTF are the bus andstar, with the star becoming more prevalent. Ship-board physical topologies include bus, star, andring. The fiber-optic backbone on most ships isarranged as a ring, with star-configured LANsconnected to the ring. Logical topologies describethe way the LAN is viewed by the media access

5-12 _______________________________________________________________________________________________ MCWP 6-22

method used. For example, Ethernet uses both thebus and star physical topologies while implement-ing a bus-type logical topology.

a. Bus TopologyThe bus physical topology requires the leastamount of cable and is the simplest of the three.Terminal devices are attached using drop lines topoints along the cable where a tap is used to pene-trate the cable, or, alternatively, quick disconnecthardware is used at planned breaks in the cable.Signals transmitted on the bus propagate to everypoint on the bus in a broadcast fashion. Any de-vice connected to the bus can communicate withany and all other devices on the bus over thisbroadcast medium. The ends of the bus requireterminating devices with an impedance thatmatches that of the cable (typically 50 ohms forbaseband coaxial cable). Without this matchedtermination, reflected signals would interfere withintended transmissions. (See fig. 5-3.)

The bus topology is usually used with contention-based media access methods such as Ethernet.This topology is also frequently used as a back-bone transmission path for other topologies,which allows multiple specifications and accessmethods in a more complex network. Buses usespecifications that restrict overall cable length.Length restrictions are necessary to ensure thattiming measurements associated with signal prop-agation and collisions on the cable can be used tomanage the network.

The bus topology may be desirable for smallerLANs at tactical echelons where its simplicity andease of installation may outweigh its disadvantag-

es. Installation and reconfigurations tend to besimpler with a single cable. Less equipment, wir-ing, and infrastructure are required for the buscompared to other topologies; therefore, installa-tion and operating costs are likely to be lower.Multiport transceivers, bus attachment devicesthat allow multiple terminal drops from one con-nection to the bus, transform the bus topology to astar. The flexibility of being able to reroute theterminal drops without moving the bus is a furtheradvantage of this topology.

The shared nature of the bus topology is the causeof its disadvantages. Any disconnected or brokencable will disable the entire LAN. Minimum dis-tances between connected terminal devices areimposed to reduce adjacent terminal signal reflec-tions and to allow sufficient time for collision de-tection schemes to operate properly. Bus cablesare restricted in length through imposed specifica-tions to ensure that signal propagation delay neverexceeds the time needed to send the shortest al-lowable message over the LAN. The thin-wireLAN cable specification 10Base2, for example,indicates with the number “2” that the maximumcable length is 200 meters. Actual cable lengthsare somewhat less than the approximate numbersused in the abbreviated specifications.

b. Star TopologyThe star topology is characterized by multiple ter-minal devices homed or connected to a centralhub or server. Unlike the bus, the star topologycontinues to operate for all other connected devic-es if one of its terminals or a cable to one of itsterminals malfunctions. This topology, althoughmore complex than the bus, can be more efficient

Figure 5-3. Bus Topology.


and is the most widely used LAN topology incommercial and MAGTF applications. (See fig.5-4.)

Advantages of the star topology include excellentdiagnostic, control, and management capabilities.Priority schemes can be employed as a way ofmanaging the various workstations and other ter-minal devices on the LAN. Because all terminaldevices connect to the hub, all lines are easilymonitored and controlled. Reconfiguration is alsomuch easier to manage at this centralized loca-tion. (See fig. 5-5.)

The star topology’s disadvantages center aroundits centralized hub, also called a concentrator. Thehub is a common point of failure for all of the

connected terminals. If the hub loses power or hasa failure in its circuitry, the entire LAN may beshut down. If the failed hub is attached to a back-bone bus when it fails, the entire bus could also bedisrupted. The additional wiring for terminal con-nections and the hubs themselves adds to the costof this type of topology. Despite the higher cost,the added flexibility and convenience of the startopology make it the topology most often used inthe MAGTF.

c. Ring TopologyIn the ring topology, all terminals are connectedto one another to form a circular ring with com-munications possible in either direction. Typical-ly, one of the terminals acts as the manager ormonitor in the network. The monitor is responsi-ble for generating and passing the token that con-trols other terminal users’ access to the ring. Onlythe holder of the token is allowed to transmit onthe LAN. Once completed, that user sends the to-ken to the next user on the ring. The ring is gener-ally associated with token-passing access methodssuch as token ring or fiber distributed data inter-face (FDDI). (See fig. 5-6.)

The implementation of this topology is most oftencombined with the star topology using hubs onthe ring as multiple access units for terminal con-nections. This access method reduces failures andinterruptions that would occur if terminals wereconnected in a series of point-to-point connec-tions to form the ring. (See fig. 5-7 on page 5-14.)

The hubs are left in place, reducing the chance offailure introduced by constant interruption caused

Figure 5-4. Star Topology.

Figure 5-5. Combined Bus/Star Topology.

Figure 5-6. Ring Topology.

5-14 _______________________________________________________________________________________________ MCWP 6-22

by user connections and disconnections. One badconnection on any part of the ring, however, canbring the entire LAN down. The hubs are part ofthe ring, and their failure to maintain the ring con-nection can cause the backbone LAN to fail. Dualrings are used to overcome this single point offailure. Usually, one ring is the primary ring,while the other (secondary ring) is a backup thatis used if the primary ring fails. As with the startopology, the ring topology includes excellent di-agnostic, control, and management capabilities.This topology is prevalent aboard ship.

5303. Access Methods

LAN access methods define the processes, proce-dures, and standards for the various types of me-dia and topologies. The Institute of Electrical andElectronic Engineers (IEEE) 802 series specifiesstandards for LAN media access methods. TheIEEE 802 series includes Carrier Sense MultipleAccess with Collision Detection (CSMA/CD or802.3), token bus (802.4), and token ring (802.5)access methods. These access methods, originallyused with copper wire at data rates of 1 - 16 Mbpsare now also used with fiber-optic cable and canbe used at 100-Mbps data rates. The FDDI andcorresponding copper distributed data interface

access methods are specifically developed for 100Mbps fiber-optic and copper LANs. Ethernet, aspecific implementation of the 802.3 access meth-od, is the most widely used LAN standard in theworld. It is also, not surprisingly, the most widelyused LAN access method in the MAGTF andaboard ship. Ethernet is used with multiple mediatypes and topologies Ethernet standards are speci-fied for twisted-pair, coaxial, and fiber-optic LANmedia. Table 5-2 shows approximate maximumdata rates, cable types, approximate maximum ca-ble segment lengths, topologies, and the numberof segments and nodes per segment for eachEthernet specification.

The FDDI access method specifies a 100 Mbps,token-passing, dual-ring LAN that uses the fiber-optic transmission medium. It defines the physicallayer and media-access portion of the link layer.FDDI access is similar in many ways to TokenRing access. Both use the ring topology, tokenpassing, and redundant features such as dualrings.

FDDI is defined by specifications for media ac-cess control, physical layer protocols and medi-um, and station management. FDDI, however,uses the same upper sublayer of the datalink layerthat Ethernet uses, making it compatible with

Figure 5-7. Combined Ring/Star Topology.


Ethernet at its higher throughput. Media accesscontrol defines the medium access method, whichincludes frame format, token handling, address-ing, the algorithm for calculating a cyclic redun-dancy check value for error detection, and errorrecovery mechanisms. The physical layer proto-col defines data coding procedures, clocking,framing, and other requirements. The physicallayer medium defines the transmission medium,which includes the fiber-optic link, power levels,bit-error rates, optical components, and connec-tors. Station management involves the FDDI sta-tion and ring configurations and ring controlfeatures such as station insertion and removal, ini-tialization, fault isolation and recovery, schedul-ing, and statistics collection.

FDDI employs two traffic types, synchronous andasynchronous, to provide real-time allocation ofnetwork bandwidth. A portion of the total 100Mbps bandwidth can be allocated solely for syn-chronous traffic, while asynchronous traffic usesthe remainder. Stations with the need for continu-ous transmission capability, such as simultaneousvoice, data, and video information applications,use synchronous traffic. The remaining band-width is used by asynchronous traffic users whohave much lower throughput requirements. Sta-tion management functions of FDDI include adistributed bidding scheme to allocate FDDIbandwidth based on an eight-level priorityscheme. These capabilities for flexible bandwidthallocation are useful in the larger MEF HQ to en-sure effective use of limited bandwidth.

.

Table 5-2. Ethernet Standards and Specifications.

Specification Name 1

Maximum Data Rate Cable Type

Maximum Length of One Cable Segment (meters)

Bus Type Topology

Number of Segments/Nodes

per Segment

10BaseT 10 Mbps Twisted-pairCategory: 3, 4, 5

100 Star Depends on hub ports

10Base2 10 Mbps Coaxial (thin) 200.00 Linear 2 3/30

10Base5 10 Mbps Coaxial (thick) 500 Linear 2 5/250

10BaseFL 10 Mbps Fiber-optic 4000.00 Star

100BaseFX/TX 10 Mbps 100 Mbps

Twisted-pair(Category 5)

150 Star Depends on hub ports

1Specifications are all baseband, with the first number indicating the maximum data rate in Mbps and the last letter/number indicat-ing the cable type or the unrepeated cable length. 2 Impedance matching terminations at ends of cables required.

5-16 _______________________________________________________________________________________________ MCWP 6-22

Section IV

Switched Backbone

The MAGTF switched backbone (SBB) compris-es the switching, routing, and wideband transmis-sion systems that provide the high-capacitycommunications backbone for the MAGTF tacti-cal communications network as well as connec-tivity with the DISN. It is the tactical equivalentof commercial local and long-distance networksand, in some situations, interfaces with and usesthose commercial networks. The SBB uses anevolution of older and newer equipment and tech-nology. The evolution drives changes in systemsand organizations, revisions in procedures, andrequirements for additional training.

The SBB, like the MAGTF itself, is tailored andhas the flexibility to adapt to support the unfold-ing tactical situation and overall scheme of ma-neuver. The SBB is planned, designed, installed,operated, and maintained by CIS personnel underthe cognizance of the G-6/S-6 and leadership ofcommunications unit commanders. Planning, re-design, and adaptation are continuous as SBBequipment and personnel arrive in theater and theMAGTF transitions to operations ashore. LargerHQ, rear areas, expeditionary airfields, and C2 fa-cilities are the principal subscribers to the SBB.Maneuver battalions cannot afford the restrictionson mobility imposed by the SBB and normallylink to it through an SCR interface.

The switches, IP routers, and wideband MCR sys-tems that form the MAGTF SBB are described inthis chapter. Computers play a key role in the op-eration, maintenance, and control of this SBB.Computer-controlled communication links andswitching enable efficient, flexible use of limitedresources. Computerized switches and routers areused to route voice, data, and video information atvarious points or nodes in the network. They in-clude devices such as circuit switches to routetelephone calls and data, message switches toroute organizational message traffic, packetswitches for efficient data transmission, and rout-ers to interface with IP router networks for data

communications. Wideband MCRs, both satelliteand terrestrial, provide the internodal communica-tions for the MAGTF communications networkand the connectivity to the DISN entry points.(See app. E.)

5401. Tri-Services Tactical System

The TRI-TAC family of equipment, developed inthe 1970s under a joint program of the MarineCorps, Air Force, and Army and fielded in themid-1980s, provides the major components of theMAGTF SBB. This equipment was developed toprovide interoperable, secure, and deployablevoice and data digital switching and transmissionsystems for tactical forces operating in a joint en-vironment. The design took into consideration therealities of tactical communications in remote lo-cations. Tactical transmission links are con-strained by high bit-error rates and limitedbandwidth, and TRI-TAC systems are designed tooperate in this environment.

TRI-TAC systems provide a high degree of secu-rity but are complicated, expensive, difficult tooperate, and use a very different set of communi-cations standards than the commercial networksand the DSN. For voice digitization, TRI-TACsystems employ continuously variable slope delta(CVSD) modulation to conserve transmissionbandwidth, while the DSN and commercial net-works use pulse-code modulation and adaptivedifferential pulse-code modulation. These differ-ences require modulation conversions at interfacepoints between the TRI-TAC and DSN or com-mercial networks. Multiple modulation signalconversions eventually lead to errors that disruptcircuits.

TRI-TAC systems use conditioned diphase sig-naling, which allows longer wire-line transmis-sion without repeaters than commercial baseband


signaling techniques and permits timing to be em-bedded in every circuit. This type of signal alsoprovides a much more efficient use of bandwidththan commercial baseband signaling. Again, how-ever, the different signaling techniques drive a re-quirement for conversion to interface with DSNand commercial networks.

The TRI-TAC family of TACSAT and terrestrialmicrowave MCR communications and switchingsystems equipment is currently in use by threeServices and the joint community—the Army atechelons above corps level, the Marine Corps atregiment/group and higher echelons, the AirForce when deployed, and the JCSE to supportJTFs. The employment of TRI-TAC systems be-gan before Desert Shield/Desert Storm and pro-v ided , w i th some g rowing pa in s , anunprecedented degree of communications interop-erability between the Army, Marine Corps, andAir Force.

GMF tactical SATCOM systems include DSCSsatellites that provide the required relay and com-patible ground terminal systems. Terminal sys-tems include the AN/TSC-85 and AN/TSC-93,which are fielded in the MAGTF in limited num-bers. The Army also uses these terminals, whilethe Air Force uses interoperable versions—theAN/TSC-100 and AN/TSC-94 terminals. Marinecomponent and MEF HQ are routinely augmentedwith Air Force and Army GMF SATCOM termi-nals for training and contingencies under memo-randums of understanding (MOUs) with theArmy and Air Force.

There are five different TRI-TAC circuit switchesand two versions of the TRI-TAC messageswitch. Each switch has its own software thatmust be frequently tested and certified to ensurethat it will interoperate with the other switches inthe network. The Marine Corps and the Air Forceemploy the TRI-TAC-developed AN/TTC-42 andSB-3865 unit-level circuit switches (ULCSs). Thelarge, high-capacity AN/TTC-39 circuit switchand AN/TYC-39 message switch are also TRI-TAC switches but are not part of the MarineCorps inventory. However, these two switches areavailable, with support personnel, under the same

Army and Air Force MOUs used to obtain GMFSATCOM augmentation. TRI-TAC switches usedeterministic routing like the DSN and commer-cial networks, while the Army’s AN/TTC-39Dand MSE switches use an incompatible flood-search routing scheme.

5402. Switches

Switches provide the means to route trafficthrough a network of transmission media support-ing many commands, units, and individualMarines. Switching may be manual (operator as-sisted) or automatic, and it may connect local sub-scribers, such as those in a MEF main COC, orperform WAN functions, such as sending trafficover satellite links. There are basically three typesof switches: circuit, message, and packet.

Circuit switches generally support telephone traf-fic; message switches process formatted messagesfor storage and delivery; and packet switches pro-cess data into packets for transmission over multi-ple links and then reassemble the packets at theother end. Although the Marine Corps developeda packet switch under the TRI-TAC program, itwas never fielded, and the Marine Corps achievesa packet switching capability through the use ofIP routers as discussed below. The Army, in con-trast, employs an X.25 packet switching protocolin conjunction with their MSE equipment to es-tablish a tactical packet network. Exchanging databetween the MAGTF SBB and the Army tacticalpacket network will be a requirement in mostjoint operations and will be discussed later.

a. Circuit SwitchesCircuit switches provide an electrical circuit ondemand between calling and called parties. Thecircuit is reserved for exclusive use of the partiesuntil the connection is terminated. The tacticaltelephone system operates by means of circuitswitching. Circuit switches are used to switchvoice, data, and multimedia traffic. Traffic mayoriginate from either data capable terminal devic-es, secure telephones, nonsecure telephones, or IProuters used to route LAN traffic within theMAGTF and over WANs.

5-18 _______________________________________________________________________________________________ MCWP 6-22

(1) AN/TTC-42 and SB-3865. The MAGTF usestwo ULCSs: the AN/TTC-42 and the SB-3865.AN/TTC-42 switches can provide service to 280combined digital/analog loops/trunks. An SB-3865 switch can provide service to 64 combineddigital/analog loops/trunks in a single configura-tion, and two or three SB-3865s may be stacked toserve 90 combined digital/analog loops/trunks at asingle site. Because routing of calls is determinis-tic, a tactical telephone directory must be main-tained.

(2) Digital Transmission Groups. DTGs a r eused to interconnect switches and are usually en-crypted to provide traffic flow security. DTGsmay be transported by using GMF SATCOM, lineof sight microwave radio, tropospheric-scatter(troposcatter) microwave radio, coaxial cable, andfiber-optic cable.

(3) Interface to the DSN. TRI-TAC switches in-terface to the DSN through STEPs. STEPs areconfigured to provide the interface between thetactical and DSN systems. Because a direct digitalCVSD-to-pulse-code modulation conversion hasnot yet been implemented in the STEPs, the inter-face between the tactical communications systemand the DSN consists of converting tacticalCVSD-modulated circuits to analog form, inter-facing the analog signal with the DSN, then digi-t izing the signal into 64 kbps pulse-codemodulation or 32 kbps adaptive differential pulse-code modulation format for further transmissionwithin the DSN.

(4) Interface to MSE. TRI-TAC switches inter-face to MSE switches via designated area codesknown as “area code gateways.” These area codesare used within MSE as the means of interfacingbetween the MSE flood-search network and exter-nal deterministic networks such as DSN and TRI-TAC.

(5) North Atlantic Treaty Organization andCommercial Interfaces. TRI-TAC AN/TTC-39family switches contain hardware and softwarefeatures that allow them to interface with NATOmembers’ switches in accordance with Standard-ization Agreement (STANAG) 5040. STANAGs4206 through 4213 provide specifications for

standard digital interfaces between NATO tacticalcommunications systems. The AN/TTC-42 andSB-3865 switches do not implement NATO inter-faces and rely on AN/TTC-39 family switches toprovide NATO access if it is required.

(6) Security. The TRI-TAC system employsdigital subscriber voice terminals (DSVTs) toprovide end-to-end encryption for classified con-versations and uses link encryption of interswitchdigital transmission groups to conceal the numberof calls made over the link and the telephonenumbers called (i.e., traffic flow security). Al-though not designed as part of the TRI-TAC sys-tem, STU-III terminals are used to provide secureaccess to subscribers in the DSN. DSVT, digitalnonsecure voice terminal (DNVT), and analogtelephones cannot be used to place secure calls in-to the DSN because they are cryptographically in-compatible with the STU-III terminals. DSVT,DNVT, and analog telephones can place nonse-cure calls to STU-III terminals connected to theDSN or commercial networks. A STU-III multi-media terminal can be used for interfaces withDNVT devices for interface to the TRI-TACcommunications network.

(7) Access. Telephones (DSVT, DNVT, andmultimedia terminal), TCIMs, radio-wire integra-tion devices, remote multiplexer combiners(RMCs), and electrical/optical converters are usedto gain access to circuit switches (see table 5-3).Telephone lines may be multiplexed/combined byRMC devices before entering the circuit switch.Many of the tactical telephones are both data andvoice capable. The TCIM provides a computer-to-radio or computer-to-circuit switch interface ca-pability. Radio-wire integration devices providemanual, remote access to the SBB from SCR sys-tems. RMCs extend the service area of a local cir-cuit switch by providing wire-line access to alimited number of subscribers who do not possessor have direct access to a switch. Electrical/opti-cal converters allow for connection of fiber-opticcable between switches and other parts of thecommunications network

(8) Analog Equipment. Some older analog cir-cuit switches and telephones remain in the inven-tory. These devices can interface to the SBB, but


not in a secure digital mode. Consequently, theirprimary utility lies in providing local telephoneservice within a single CP or HQ. These analogdevices are described in TM-2000-15/2B, Princi-pal Technical Characteristics of U.S. MarineCorps Communication-Electronic Equipment.

More information on circuit switching can be ob-tained from TRI-TAC manuals and in CJCSM6231.02, Joint Voice Communications Systemsand CJCSM 6231.03A. The older tactical tele-phones are described in TM 2000-15/2B.

b. Message SwitchesMessage switches ensure delivery of completemessages to a distant location or multiple loca-tions when circuits to that location become avail-able. If all circuits are busy, the originatingmessage center or intermediate message switchesstore the message and automatically transmit it tothe proper addressee as soon as a circuit is free.This form of switching is referred to as “store andforward.”

Message switches are primarily used by theMAGTF at the MEF CE and MSC levels. TheAN/MSC-63A is used to support both general ser-vice (GENSER) and SCI message switching. Thedesignations for these two message switch usesare the Tactical Communications Center (TCC)for the GENSER message switch and the SpecialSecurity Communications Central (SSCC) for

SCI. As mentioned earlier, the AN/TYC-39 mes-sage switch is available from the Army to aug-ment the message switching capability of theMEF.

c. Packet SwitchesTransmission of complete messages is an ineffi-cient use of data communications networks. Pack-et switches break messages into data packets thatare individually addressed and entered into thenetwork. The packets are forwarded to the ad-dressee over a number of different links or circuitpaths between packet switches based on circuitavailability. At the receiving end of the circuit,the packets are reassembled into the original mes-sage, which is then passed to the receiving termi-nal. The MAGTF does not use packet switches.However, the MAGTF circuit switches may haveto interface with the Army’s MSE. MSE employsa tactical packet network overlay to accomplishpacket switching over its circuit switches. MSEsupports division units in the Army. Special inter-face equipment and protocols are required to ac-complish this interface.

d. Switch NetworkMAGTF switches are used primarily at the regi-ment level and higher echelons at the main andrear area operations centers. MAGTF switchesand associated subscriber devices are listed in ta-ble 5-4 on page 5-20.

Switches are now available in increasingly smallpackages such as circuit cards. This enables theuse of these switches within or as embedded com-ponents of other systems such as digital TECH-CON equipment and TDN servers and gateways.Routers, described next, are also migrating to en-closures such as those described above and per-form similar functions to those of switches.Figure 5-8 (on page 5-20) shows circuit switchconnectivity for a MEF in a JTF. CJCSM 6231.02and CJCSM 6231.03A provide more detailed in-formation about tactical circuit and messageswitch descriptions and use.

.

Table 5-3. MAGTF Telephones.

Analog TA-312TA-838TA-938

STU-III1

Digital TA-954 DNVT

TA-1042 DNVT1

TSEC/KY-68/78 DSVT1

Multimedia terminal (STU-III)1

1Data capable

5-20 _______________________________________________________________________________________________ MCWP 6-22

Table 5-4. MAGTF Switches.

Switch Location UsedInterface Devices

Terminal Devices Type

AN-TTC-42 MEF/MSC TCIMIP routers

STU-III Circuit

SB-3865 MEF/MSCRegiment/groupArtillery regiment/ battalion

DNVTDSVT

AN/MSC-63AAN/TYC-39

MEF/ACE/divisionMEF/MARFOR

Message servers Message

Figure 5-8. Circuit Switch Network.


5403. Global Block Numbering Plan

Effective 1 June 1995 the Global Block Number-ing Plan (GBNP) was implemented by all tacticalcircuit switches and switchboards in the Depart-ment of Defense. The GBNP does not violate thedeterministic use of 3/4 or 4/3 numbering plans.The plan was designed to be compatible withnumbering plans previously used for joint opera-tions and the Military Services. Incorporation ofthe plan should be done during the normal cyclewhen contingency, exercise, and operations plansare updated.

The basis for the GBNP is fourfold: (1) to incor-porate all Services into a joint network, (2) toidentify a unique, Service-managed block of unitand subscriber numbers, (3) to simplify networkmanagement (DISN/Commercial) routing into aglobal network, and (4) to identify data bases andsubnetworks within the block of numbers. TheGBNP must be implemented with the circuitswitch routing - task execution plan (CSR-TEP)to preclude NNXX contention between floodsearch and deterministic subscribers and to allowdeterministic switches to route into the floodsearch network.

HQMC (C4I) is the policy and oversight authorityfor the USMC’s GBNP and Preafilliation List(PAL) management. PAL management will becentralized at the USMC and major command lev-el (COMMARFORPAC, COMMARFORLANT,and COMMARFORRES). As of June 1998,MARCORSYSCOM is designated the USMCPAL Manager; MCTSSA will be the action orga-nization. The USMC PAL Manager will—

● Coordinate, distribute and maintain the USMCPAL assignments as delineated by the GlobalPAL Manager (U.S. Army).

● Serve as the Marine Corps’ primary Point ofContact for the Global PAL Manager (U.S.Army).

● Coordinate and assist the major commands inestablishing PAL and PAL sublists and main-tain this information in a centralized database.

● Recommend any policy requirements that facil-itate the management and assignment of PALsTo HQMC (C4I) on an as needed basis.

● Coordinate with COMMARLOGBASES onequipment related issues.

● Coordinate with MCCDC to ensure that USMCPAL assignments are incorporated into the ap-propriate doctrinal publications.

5404. IP Routers

The modern battlefield demands that the SBBprovide efficient support for data communica-tions. Although circuit switches and messageswitches can support data communications, pack-et switching is far more efficient. The MarineCorps initially planned to establish a packetswitching network using a packet switch devel-oped under the TRI-TAC program. However, theArmy chose to implement an X.25-based packetswitching network as an overlay on its MSEnetwork. This Army decision and other factors ledthe Marine Corps to abandon the TRI-TACpacket switch, known as the unit-level messageswitch. Instead, the Marine Corps has developed apacket switching capability through the use ofcommercial IP routers. This placed the MarineCorps in an excellent position in terms of connec-tivity to DISN because DISA has transitioned thestrategic DISN Defense Data Network (DDN)from a network based on X.25 packet switching toone based on IP routers.

The Marine Corps uses commercially available IProuters to automatically route traffic to and fromlocal or remote subscriber LANs, over the SBB,and to and from the DISN. These IP routers forma data communications overlay on the SBB andserve as gateways to the IP router networks of theother Services, the JTF, and DISN. MAGTF com-puters are configured to operate by using theirunique IP address(es). These computers imple-ment the TCP to handle end-to-end delivery ofmessages on IP router networks.

IP routers route data packets containing data inmultiple formats throughout the DISN IP routernetworks: JWICS, SIPRNET and NIPRNET.

5-22 _______________________________________________________________________________________________ MCWP 6-22

Inline network encryptors and COMSEC encryp-tion equipment are used to provide packet-leveland transmission security of the IP router net-works. IP routers provide the gateways betweenthe LAN and the SBB. IP routers use exterior pro-tocols along with interior protocols to handle IP-addressed packets, determine paths to destinationsor other routers, and manage the IP packet flowthrough their nodes. CJCSM 6231.07A, chapterVIII, provides information about router protocolsand IP addressing used by the DISN.

a. Notional Air-Deployable DataCommunications PackageA typical air-deployable, router-based data com-munications package to support the MAGTF CEincludes the equipment in table 5-5.

This equipment, with appropriate CIS personneland transmission equipment, provides the follow-ing capabilities:

● NIPRNET, SIPRNET, and JWICS WAN ac-cess to a gateway/higher HQ.

● NIPRNET, SIPRNET, and JWICS WAN ac-cess for one MSC.

● NIPRNET, SIPRNET, and JWICS LAN accessfor 35–50 end users.

● TDS network management.● IP router network management.

b. Notional MEF Data Communica-tions PackageA typical router-based data communicationspackage to support the MEF CE includes theequipment in table 5-6.

This equipment, with appropriate CIS personneland transmission equipment, provides the follow-ing capabilities:

● NIPRNET, SIPRNET, and JWICS WAN ac-cess to a gateway/higher HQ.

● NIPRNET, SIPRNET, and JWICS WAN ac-cess for seven MSCs/adjacent units.

● NIPRNET, SIPRNET, and JWICS LAN accessfor 50–200 end users.

● TDS network management.● IP router network management.

Table 5-5. Notional Air-Deployable Data Communications Package.

Nomenclature Quantity

Heavy HMMWV with shelter 2

Banyan server suite 4

Laptop (router) 2

Desktop suite (net management) 3

CISCO 4000 router 3

LAN repeater 3

Uninterruptible power supply (UPS) 7

Channel service unit (CSU)/data service unit (DSU) modems

4

Asynchronous modems 2

KG-84C 8

KYK-13/data transfer device (DTD) 2

KOI-18 2

Table 5-6. MEF CE Data Communications Package.

Nomenclature Quantity

5-ton truck with shelter 1

Banyan server suite 8

Laptop (router) 2

Desktop suite (net management) 5

CISCO 7000 router 3

CSU/DSU modems 4

Asynchronous modems 2

LAN repeater 8

UPS 11

KG-84C 20

KYK-13/DTD 2

KOI-18 2


● JTF enabler module.

c. Contingency Data Network SuitesMCTSSA has available, on request, contingencydata network suites capable of supporting NIPR-NET and SIPRNET WAN access. The contingen-cy data network suite is a standard data networkpackage for MAGTF use until the TDN gatewayis fielded. Each contingency data network suitehas been designed to support encrypted WANconnectivity to distant CPs and a LAN of up to 48hosts operating at the same classification level.The contingency data network suite is composedof two CE packages and six remote site packagesthat differ in size and the number of serial dataconnections available. Table 5-7 lists the contin-gency data network suite equipment. The KIV-7is compatible with the KG-84A/C, but is capableof much higher data rates when interfaced withanother KIV-7. The UNIX workstation is capableof supporting a DNS and network managementsoftware. The contingency data network suite canbe requested from MCTSSA via the MEF G-6.

d. TDNAlthough the TDN had not been fielded as of thewriting of this publication, the operating forcesare already using COTS hardware and software toestablish tactical data communications networks

and to interface with DISN. TDN will have an ini-tial operational capability in FY 00.

The TDN system augments the existing MAGTFcommunications infrastructure. It provides thecommander with an integrated data network andforms the data communications backbone forMAGTF TDSs. It will replace the interim datacommunications package with an expeditionary,highly mobile suite of equipment that uses the lat-est router technology.

The TDN system has two configurations: theTDN gateway and the TDN server. The TDNgateway is deployed at the MEF and MSC levelsand provides access to the NIPRNET, the SIPR-NET, and other Services’ tactical packet switchnetworks. The TDN gateway consists of an air-conditioned/heated, heavy HMMWV-mountedshelter equipped with the major components list-ed in table 5-8.

Table 5-7. Contingency Data Network Suite Equipment.

Item Quantity

CE Package (x 2)

CISCO 4500 router 1

KIV-7 encryption device 4

LAN hubs 2

2000VA UPS 1

UNIX workstation 1

Printer (LaserJet) 1

Remote Site Package (x 6)

CISCO 2514 router 1


Table 5-8. TDN Gateway Components.

Item Quantity

MCHS processors 4

Monitors 2

Smart multiplexer IDNX-20 1

Router-multiprotocolMinimum: 8 serial ports 2 802.3 ports 1 asynchronous port

2

Repeater (7-port) 6

TCIM and TCIM power supply 4


Wire-line adapters 16

UPS 6

SNMP adapter 4

Fiber-optic modems 2

KY-68 DSVT 6

MMT with DNVT appliqué 4

Patch panelsEIA 530Loop

42

In-line network encryptor 1

5-24 _______________________________________________________________________________________________ MCWP 6-22

The TDN server is deployed at the MEF, MSCs,and units down to the battalion/squadron level.The TDN server is transported in three transit cas-es. It includes the equipment shown in figure 5-9.TDN gateways and servers provide the capabilityto share files, perform electronic message han-dling, and provide transparent routing of messagesthrough the LAN, circuit switch, MCR, and SCRsubnetworks.

e. Future DirectionFor more efficient MAGTF interfaces to theDISN, IP routers and smart multiplexers are in-creasingly replacing the older and less expedition-ary switching system equipment. For example,IDNX smart multiplexers are being included atSIPRNET and NIPRNET (DISN) entry points,and the implementation of similar equipment bythe MAGTF will enable more efficient and flexi-ble use of available bandwidth. Figure 5-10 showsthe many connectivity options available withsmart multiplexers.

CJCSM 6231.02 and 6231.03A provide more de-tailed information about switches, routers, andjoint communications networks.

5405. Multichannel Radios

MCR provides the communications links for theSBB. It permits multiple users to access a singlecommunications path. MCR equipment includesterrestrial line of sight, troposcatter, TACSAT,and HF radios, all with associated multiplexers,modems, cabling, and antennas. MCR providesworldwide connectivity through links to the NI-PRNET, SIPRNET, and JWICS networks of theDISN as well as the links for long-distance com-munications within the theater and within theMAGTF. MCR provides reliable, flexible, andhigh-capacity links for both voice and data com-munications. Its primary disadvantages are com-plexity and a lack of mobility. An MCR networkrequires more time to set up and more expertise tooperate and maintain than an SCR network, and it

Figure 5-9. TDN Server Components.


cannot operate on the move. Consequently, ma-neuvering elements will rely on SCR in most situ-

ations. Table 5-9 lists the MCRs employed by theMAGTF.

Figure 5-10. Smart Multiplexer Connectivity.

Table 5-9. MCRs

Category MAGTF Radio Type or Use

SHF terrestrial AN/TRC-170(V)5 Troposcatter radio terminal

SHF SATCOM AN/TSC-85BAN/TSC-93B

GMF satellite terminals

UHF terrestrial AN/MRC-142 Line of sight radio

UHF SATCOM AN/TSC-96A(V) Satellite communications central

HF multichannel AN/TSC-120 Communications central

5-26 _______________________________________________________________________________________________ MCWP 6-22

a. SHF TerrestrialThe AN/TRC-170 is a microwave radio terminaldeveloped under the TRI-TAC program. The AN/TRC-170 provides secure digital trunking be-tween major nodes of the MAGTF communica-tions network and limited dedicated circuitsbetween individual subscribers. The AN/TRC-170includes antennas, radio transmitting and receiv-ing equipment, digital transmission group multi-plexing equipment, digital and analog voice anddata orderwires, and built-in test equipment forfault isolation. Although longer links have beensuccessfully installed, the AN/TRC-170 nominal-ly supports a 100-mile communications link. Linkdistance depends on the transmission techniqueused (mode of operation), data rate, terrain and ho-rizon angles, and atmospheric conditions. Com-mun ica t ion ba t t a l i ons and Mar ine w ingcommunication squadrons operate the AN/TRC-170.

(1) Low Data Rate Multiplexer (FCC-100). Themost important feature of the FCC-100 is its capa-bility to conserve the conditioned diphase band-width and digital trunk group interfaces to theTRI-TAC system while providing a compatibleinterface to a commercial T1 multiplexer digitaltrunk group. Commercial and TRI-TAC interfacecapabilities are available on both the loop andtrunk group sides of the FCC-100. It interfaceswith a single group of the digital group modemand provides up to 16 loop ports. These loop portscan be a mix of synchronous, asynchronous, iso-chronous, conditioned diphase data, and CVSDand pulse-code modulation voice frequency (ana-log-to-digital and digital- to-analog) signals. Withthe appropriate interface card, two-wire foreignexchange systems and four-wire voice compres-sion coder-decoder (CODEC) modules, STU-III,facsimile, and modem interfaces are supported.Characteristics of the AN/TRC-170 are listed intable 5-10.

.

(2) Modes of Operation. The AN/TRC-170 canbe operated in one of three modes with variousranges achievable in each mode. The modes areline of sight, troposcatter, and obstacle gain dif-fraction. Each mode is useful under certain cir-cumstances and in various environmentalconditions. The extensive capabilities and flexi-bility of this system make it an invaluable trans-mission system and workhorse that provides theconnectivity between the MSCs and the CE of theMEF.

Line-of-sight mode requires minimal power out-put (down to 0.25 W) and requires straight-lineclearance between sites. Normally, line of sight isused for links up to 10 miles. Figure 5-11 depictsthis mode of operation.

Table 5-10. AN/TRC-170 Characteristics.

Characteristic AN/TRC-170 (V) 5

Frequency range 4.4 - 5.0 GHz (tunable in100-kHz increments)

Bandwidth 3.5 or 7.0 MHz

Transmitter power l kW

Diversity Dual

Data rates Up to 4,608 kbps

Channel capacity(at 32 kbps)

Up to 144 (includes overhead)

Figure 5-11. Line-of-Sight Mode.


Troposcatter mode is used for link distances of 40to 100 miles. Ranges of up to 150 miles are possi-ble with troposcatter, and ranges of under 75miles, while possible, are difficult to achieve. Asmall portion of the transmitted radio waves is re-fracted off the troposphere toward the distant-endAN/TRC-170. (See fig. 5-12.)

Obstacle gain diffraction mode is used for linkdistances of 10 - 40 miles with an obstacle (e.g., amountain) located between the sites. Radio wavesare diffracted off the obstacle toward the distant-end AN/TRC-170. (See fig. 5-13.)

(3) Subscriber Channels. By using two loopgroup multiplexers (LGMs), up to 32 individualchannels (any combination of digital and analog,depending on availability of circuit card assem-blies) can be accommodated. These interface withthe AN/TRC-170 through four-wire WF-16 orCX-4566 cable.

(4) Group Trunks. Up to four groups interfacewith the AN/TRC-170 through CX-11230 or fi-ber-optic cable.

(5) Potential TRC-170 Configurations. TheTRC-170 has a variety of potential configura-tions, including:

Multitrunking Terminal. The multitrunking termi-nal is used to provide connectivity between multi-ple sites.

Through Relay. The through relay is used to ex-tend the distance of a link or provide connectivitywhen terrain prevents a single line of sight, obsta-cle gain diffraction, or troposcatter link.

Terminal Site. The terminal site is the terminatedend of a link.

Dedicated Subscriber. The dedicated subscriber isused for point-to-point telephone and/or data cir-cuits.

LGM Used as an RMC. As an RMC, the LGM isused to provide tactical telephone service to dis-tant sites. The LGM is programmed the same astwo stacked RMCs off the switchboard (TTC-42or SB-3865).

Figure 5-14 on page 5-28 shows how these con-figurations could be used to form part of aMAGTF network.

b. SHF SATCOMSHF SATCOM is employed in the MAGTF byusing GMF TACSAT terminals and preplannedDISN satellite and STEP access. These systemsare deployed by the communication battalion insupport of the MEF. The MEF uses two types ofGMF TACSAT systems: the AN/TSC-85B andthe AN/TSC-93B.

(1) AN/TSC-85B. The AN/TSC-85B is a full du-plex nodal satellite communications terminal thatis capable of interfacing with a single satellite. Ittransmits a single carrier and receives betweenone and four carriers.

Figure 5-12. Troposcatter Mode.

Figure 5-13. Obstacle Gain Diffraction Mode.

5-28 _______________________________________________________________________________________________ MCWP 6-22

(2) AN/TSC-93B. The AN/TSC-93B is a full du-plex satellite nonnodal communications terminal.The TSC-93B simultaneously transmits and re-ceives a single carrier.

(3) GMF TACSAT Capabilities. Table 5-11 liststhe capabilities and characteristics of the SHFSATCOM terminal systems. Characteristics ofthe AN/TSC-85B terminal are the same as thoseof the AN/TSC-93B unless otherwise noted.

(4) Potential Configurations. A GMF network iscomposed of nonnodal and nodal terminals con-nected through a satellite to provide the user datacommunications links. System configurations

available with MAGTF GMF assets are point-to-point, nodal, mesh, or hybrid mesh/nodal.

In the point-to-point configuration, each terminalcommunicates with the other terminal only. AllGMF terminals are capable of operating in thisconfiguration. Associated cut sheets and terminalassignment sheets must be coordinated withdetailed planning to ensure systems interoperabil-ity and minimize troubleshooting efforts. (See fig.5-15.)

In the nodal configuration, the central or nodalterminal is able to communicate directly with allof the peripheral or nonnodal terminals. The AN/TSC-93B is a nonnodal terminal, and the AN/

Figure 5-14. Notional TRC-170 Network.


TSC-85B is a nodal terminal. The nodal terminalscan communicate with up to four nonnodal termi-nals. (See fig. 5-16.)

(5) Mesh Operations. In this configuration, thenodal units communicate with each other. TheAN/TSC-85B can simultaneously communicatewith four other AN/TSC-100As or AN/TSC-85Bswith all terminals operated in a nodal mode. Forcommunications to be possible, the basebandequipment must be compatible. (See fig. 5-17.)

Table 5-11. SHF SATCOM Terminal Systems Capabilities.

Transmit frequency range 7900 - 8400 MHz

Transmit bandwidth 40 MHz

Power output 500 W (nominal)

Receive frequency range 7,225 - 7,725 MHz

Receive bandwidth 500 MHz

AN/TSC-85B AN/TSC-93B

Group data rate

Balanced nonreturn to zero (NRZ) 8 - 1,152 kbps 8 - 1,152 kbps

Conditioned diphase 72 - 1,152 kbps 8 - 1,152 kbps

Unbalanced NRZ 288; 576; 1,152 kbps 288; 576; 1,152 kbps

Low-rate multiplexer: (12 channels/low-rate multiplexer)

8 low-rate multiplexers 3 low-rate multiplexers

Maximum data rate 256 kbps

Minimum/maximum per channel 1,256 kbps

TRI-TAC: (digital trunk group) 4 ports via group modem 1 port

Figure 5-15. Point-to-Point Configuration. Figure 5-16. Nodal Configuration.

Figure 5-17. Mesh Configuration.

5-30 _______________________________________________________________________________________________ MCWP 6-22

(6) Hybrid Mesh/Nodal. In configuration, nodalunits communicate with both nodal terminals andnonnodal terminals simultaneously. The AN/TSC-85B can communicate with any combinationof up to four AN/TSC-100As, AN/TSC-85Bs,AN/TSC-94As, and/or AN/TSC-93Bs. The TSC-100A and TSC-94A are GMF terminals that theAir Force operates and provides for MEF and/orMarine component support under a formal MOU.(See fig. 5-18.)

c. UHF TerrestrialThe AN/MRC-142 is the UHF terrestrial MCRterminal used by the MEF and its MSCs. A TRI-TAC-developed transmission system, the AN/MRC-142 is configured with two line-of-sight ra-dio subsystem terminals. The line-of-sight radiosubsystems can be set up to function as indepen-dent line-of-sight radio subsystem terminals orcan be configured together to function as athrough repeater or drop-and-insert repeater. Eachline-of-sight radio subsystem terminal interfaceswith another AN/MRC-142 line-of-sight radiosubsystem terminal over a UHF radio link usingparabolic grid antennas mounted on telescoping50-foot masts. The characteristics of the AN/MRC-142 are provided in table 5-12.

The AN/MRC-142 has four operational configu-rations that provide the flexibility required of thissystem in MEF operations. It is capable of beingconfigured as a single- or dual-link terminal, athrough repeater, or a drop-and-insert repeater.

One of the two line-of-sight radio subsystem ter-minals in each AN/MRC-142 is used to configurea single UHF radio link. In this operational con-figuration, the radio terminal equipment designat-ed “number 1" is used because it provides the bestequipment access and communicates with justone other AN/MRC-142.

Two line-of-sight radio subsystem terminals ineach AN/MRC-142 are used when two separateUHF radio links are required. In this configura-tion, the two independent radio terminalscommunicate with single line-of-sight radio sub-system terminals in two other separate AN/MRC-142s.

The through repeater configuration is used when aparticular radio path between two AN/MRC-142sis longer than 20 - 30 miles or does not have aline-of-sight path. The through repeater configu-ration uses a third AN/MRC-142 to extend orcomplete the radio link between two communicat-ing AN/MRC-142s.

The drop-and-insert repeater configuration is usedwhen a particular mission requires access to traf-fic at a repeater site. The drop-and-insert functionis accomplished by connecting a TD-1234 RMCbetween the cable side interface of the two line-

Table 5-12. AN/MRC-142 Characteristics.

Frequency range 1,350 - 1,850 MHz

Bandwidth 100 (125 optional) kHz

Channel rate 144, 288, and 576 kbps

Output power Low: 300 mW (25 dBm)High: 3 W (35 dBm)

Frequency stability 10 ppm

Orderwire channel Analog: 300 - 3,400 HzDigital: 16 kbps

Figure 5-18. Hybrid Mesh/NodalConfiguration.


of-sight radio subsystem terminals. In this mode,a digital transmission group from one end is putinto the high group side of the RMC. The RMCdemultiplexes eight individual traffic channelsfrom the group and passes on a low group, whichis still combined. This combined low group isconnected from the RMC to the second line-of-sight radio subsystem terminal and passed on tothe distant end. The result is that eight channelsfrom the source are “dropped off” at the repeatersite and an additional eight channels (combinedlow group) are passed on to the distant-end termi-nal.

d. UHF SATCOMThe AN/TSC-96A(V) is a UHF SATCOM centralterminal that provides the capability to receiveand transmit GENSER message traffic. This sys-tem accesses AUTODIN through the Naval Com-mon User Digi ta l Informat ion ExchangeSubsystem (CUDIXS) and provides access to se-cure voice communications and fleet broadcastvia UHF satellites. It can be employed anywherein the world within the coverage of any fleet satel-lite (FLTSAT), UHF follow-on satellites, leasedsatellite, or GAP FILLER satellites.

The AN/TSC-96A(V) is a UNIX-based systemhosted on two processors and workstations withNaval Modular Automated CommunicationsSubsystem II (NAVMACS II) software. It inter-faces with the AN/MSC-63A, Banyan VINESservers, and PC-client software loaded on com-puter terminals for message distribution. The sys-tem has the capability to receive four high-speedfleet broadcast channels. It was designed with in-ternal backup and the capability to remote DAMAsecure voice up to 100 feet. The AN/TSC-96A(V)can use four DAMA ports and monitor four fleetbroadcast channels. A daily communication statusreport lists the available channels on the satellitefor fleet DAMA and fleet broadcast.

There are 16 total channels on the fleet broadcastnetwork. One channel is used for timing and over-head, leaving 15 operational channels. Eleven ofthe fleet broadcast channels are secure and can beprocessed by the AN/TSC-96A(V). These arecalled common and overload channels. The com-

mon channel is the primary channel for fleetbroadcast traffic. The overload channel willbroadcast messages that could not be broadcast onthe common channel because of overload. It willalso rerun messages transmitted on the commonchannel.

SCI channels are automatically routed/forwardedto the SCI facility, to the AN/MSC-63A, or di-rectly to the user. Two weather channels can betransmitted over fleet broadcast and processed inthe AN/TSC-96A(V). A tactical intelligence (TA-CINTEL) channel can be received in the AN/TSC-96A(V) but not processed. United Press In-ternational and Associated Press Internationalnews are sometimes transmitted and can be pro-cessed.

The AN/TSC-96A(V) has several configurationsavailable to the supported unit. The subsystemsand capabilities/limitations listed above are avail-able in any configuration. The AN/TSC-96A(V)can be configured as—

● A stand-alone communications message center● Networked into an AN/MSC-63A message

switch ● Networked into the LAN.

The AN/TSC-96A(V) can be configured to sup-port a unit with all of the capabilities of a commu-nicat ions center except the reproduct ioncapabilities. In this configuration, the AN/TSC-96A(V) provides primary AUTODIN entry viathe associated NCTAMS. In addition to theGENSER message traffic capability, the AN/TSC-96A(V) can provide the using unit with a se-cure voice capability.

The AN/TSC-96A(V) can be connected to theAN/MSC-63A message switch for increased ca-pabilities. In this configuration, the AN/TSC-96A(V) can provide the primary or secondaryAUTODIN access for units connected to the AN/MSC-63A.

The AN/TSC-96A(V) can be linked into the LANthrough several options. If the network users are

5-32 _______________________________________________________________________________________________ MCWP 6-22

using PC-client software, the LAN can be admin-istered through the AN/TSC-96A(V). If the net-work is using Banyan VINES software, a thirdcomputer terminal is needed between the servers.This terminal is the gateway between the BanyanVINES server and the TAC-3 server. This termi-nal requires Super TCP/IP and NAVMACS IIsoftware for the system to be compatible withBanyan VINES networks.

The AN/TSC-96A(V) uses the Navy UHF SAT-COM system, which consists of information ex-change and quality monitoring subsystems.Satellites relay communications and control infor-mation as well as data to manage satellite resourc-es.

The subsystems are designed to address specificnaval communications requirements. These sub-systems provide various communications net-works with specific services and capabilities.

(1) Fleet Satellite Broadcast Subsystem. Thisis an expansion of the fleet broadcast, which his-torically has been the central communicationsmedium for operating naval units. Fleet broadcastis a receive-only function that allows the sub-scriber the ability to monitor 4 channels at 75 bpsper channel. In addition, fleet broadcast can beused as an alternate route for receiving messagetraffic if the CUDIXS link is not available. High-speed fleet broadcast is available from NCTAMS.High-speed fleet broadcast gives the subscriberthe ability to receive the four channels of fleetbroadcast at 2,400 bps per channel.

(2) CUDIXS/NAVMACS II. These two systemscombine to form a communications network fortransmitting GENSER message traffic betweenships and shore installations. CUDIXS is ashore,and NAVMACS II is aboard ship and in the AN/TSC-96A(V).

Secure Voice. This is a narrowband UHF sub-system that provides voice communications be-

tween ships and with wide-area voice networksashore.

TACINTEL. This subsystem is specifically de-signed for special intelligence communications.

DAMA. This subsystem is designed to multiplexseveral subsystems, or users, on one satellitechannel. This multiplexing has the effect of al-lowing more satellite circuits to use a single UHFsatellite channel.

Satellite Monitoring. This subsystem provides us-ers of the UHF satellite communications systemwith means to analyze and resolve system andequipment-related problems. The SATCOM sig-nal analyzer is operational at NCTAMS.

e. Super High Frequency (SHF)Tri-Band Advanced Range Extension Terminal (STAR-T)The STAR-T (AN/TSC-156) is a HMMWV-mounted, multichannel, tri-band SATCOM termi-nal that will be fielded in FY 99. The STAR-Tsupports the equivalent of four 1.544 Mbps cir-cuits. It can communicate with the DSCS andcommercial satellite systems. It is capable ofwideband satellite transmission and receptionover the DSCS. It is also capable of commercialsatellite communications in the Ku and C bandsof the electromagnetic spectrum. The AN/TSC-156 will replace the current inventory of AN/TSC-93(B)’s and AN/TSC-85(B)’s in the FMF.The STAR-T brings increased mobility, reducedset-up/tear-down times, and commercial accesscapability to the Marine Corps. The STAR-T willbe organic to the Communication Battalion of theMarine Expeditionary Force. In addition to sup-porting the doctrinal MEF to Major SubordinateCommand wideband links, STAR-T will providesmaller MAGTF’s like MEU’s the bandwidththey need to conduct a range of missions in the lit-torals. Maximum aggregate bandwidth on thedownlink is equivalent to four 1.544 Mbps (T-1).It will have an increased channel bandwidth andgreater operational capability.


f. Secure Mobile Anti-Jam Reliable Tactical-Terminal (SMART-T)The SMART-T, a HMMWV-mounted, tacticalSATCOM terminal, Nomenclature: AN/TSC-154. Scheduled for fielding in FY 99, this Ex-tremely High Frequency (EHF) terminal ismounted on a HMMWV. It is capable of Low Da-ta Rate (LDR) and Medium Data Rate (MDR)transmission and reception over the Milstar satel-lite constellation. The SMART-T brings a new ca-pability to the Fleet- protected, survivablecommunications. It will be organic to the Com-munication Battalion of the Marine ExpeditionaryForce, and will also reside at the CommunicationsCompany of the Marine Division and theCommunications Platoon of the Marine InfantryRegiment. SMART-T will also provide the meansby which Marines participate in CINC and JTFmandated EHF communications circuits. Maxi-mum aggregate bandwidth on the downlink is1.544 Mbps.

g. HF Communications CentralThe MAGTF uses the AN/TSC-120 for its HF in-terface to AUTODIN. It is a self-contained, stand-alone communications central used primarily forlong-haul Defense Communications System entryand point-to-point, beyond line of sight communi-cations. It provides connectivity for the majorCEs of a MAGTF.

The AN/TSC-120 is shelter mounted on a heavyHMMWV. It may also include one AN/PSC-5DAMA-capable UHF TACSAT radio per system.Each communication battalion maintains fiveAN/TSC-120s, which are operated in the 2–29.9999 MHz frequency range, with automatictuning for 280,000 possible frequencies in 0.1-kHz increments. The AN/TSC-120 is capable ofeither single or double sideband operation. Its in-ternal modems are capable of emulating severalmodems currently used in the DOD inventory,

making the AN/TSC-120 a highly interoperableand flexible system. Each modem is limited toemulating one modem-mode at a time, and onlyone modem can be patched per sideband.

AUTODIN interface is provided by using a laptopcomputer that provides Modes I, II, and V AU-TODIN access. It can transmit and receive JointArmy, Navy, and Air Force Publication (JAN-AP)-128 messages at data rates of up to 2,400 bps(Modes I and II) and 1,200 bps (Mode V). AlliedCommunications Publication (ACP)-126 andmessage text format editor messages stored on3.5-inch floppy disks can be modified, stored, andthen transmitted.

Automatic link establishment automatically se-lects an optimum HF communications channelfrom an available list of approved, prepro-grammed channels. It then executes a handshak-ing protocol to connect two or more HF radiosystems in a half-duplex link with minimal opera-tor involvement. Automatic link quality analysiscalculates the quality of available channels anddisplays the results in a numeric format. On thebasis of the automatic link quality analysis results,the operator can establish the link on the bestoverall channel or allow automatic link establish-ment to establish the link on the first channel thatallows for communications. Once the link is es-tablished, the operator must choose the best chan-nels for transmitting and receiving in order toestablish the full-duplex link.

h. MEF UseThrough task-organization, the MCR equipmentcan be used at any location and with any unit inthe MAGTF. However, the most common use ofthis equipment within a MEF is as shown in fig-ure 5-19 on page 5-34. CJCSM 6231.04, JointTransmission Systems, provides detailed informa-tion about the operation of MCR equipment.

5-34 _______________________________________________________________________________________________ MCWP 6-22

Figure 5-19. MEF Notional MCR Connectivity.


Section V

Special Purpose Systems

The MAGTF special-purpose system assets aresystems designed to provide specific position lo-cation, navigation, information distribution, andcooperative identification services. These systemsserve all MAGTF elements, often through exter-nally managed satellite and aircraft relay systems.These systems provide real-time information totactical users at the point of need.

5501. PLRS

PLRS provides MAGTF commanders with nearreal-time, accurate, three-dimensional position lo-cation and navigation information. It is a time-or-dered, spread-spectrum radio system operating inthe Ultra-High Frequency (UHF) band between420 and 450 megahertz. Integral error detectionand correction, cryptographic security, and fre-quency hopping features provide resistance toelectronic countermeasures.

The PLRS radio set can be employed in the fol-lowing configurations: manpack, surface vehicle,or aircraft. The five-ton truck configuration of thecurrent PLRS Master Station is being replaced bythe Net Control Station-EPLRS (Downsized)(NCS-E[D]). The NCS-E(D) improves mobility,flexibility, and reliability. It can accommodate upto 460 radio sets in a single PLRS “community.”Key planning considerations are the number andlocation of “reference” radio sets and the locationof relays, as necessary. (Each radio set in the net-work is capable of automatically relaying data tothe NCS-E(D) without operator action.) Refer-ence sites can be surveyed, in which case they arefixed, or established by using a Global Position-ing System interface, which provides additionalmobility and versatility.

PLRS is employed by PLRS Platoon, Communi-cations Company, Marine Division. The U.S. Ar-my (Enhanced PLRS [EPLRS]), U.S. Navy (AN/KSQ-1), and U.S. Air Force (Situational Aware-

ness Data Link [SADL]) also have PLRS-relatedrequirements.

5502. Precision Lightweight GPS Receiver (PLGR)

The AN/PSN-11 PLGR is a small, handheld, GPSreceiver that weighs approximately 3 lb. It pro-vides precise positioning and timing solutionsbased on signals received from the GPS satelliteconstellation. Position can be displayed in virtual-ly any format, including latitude/longitude, mili-tary grid reference system, and UniversalTransverse Mercator. It contains 49 map datums,and users can program way-points for navigationwith back azimuths and distances to the next way-point available with the push of a button. ThePLGR is compatible with night vision goggles. Itis important, however, to understand the differ-ence in capabilities between the PLGR and PLRS.While the PLGR provides a dramatic improve-ment in land navigation capability, it cannot pro-vide the location of another unit and has nocommunications capability beyond the passive re-ceipt of location and time. It should be viewed asa complement for, not a replacement of, PLRS.

5503. JTIDS

JTIDS is an advanced radio system that providesinformation distribution, position location, andcooperative identification capabilities in an inte-grated form. The primary JTIDS mission is to co-ordinate tactical resources for air defense of theMAGTF. JTIDS is a spread spectrum, fast fre-quency hopping, cryptographically secure, digital(data and voice) communications system. Thesystem operates in the 960–1,215 MHz frequencyband and provides jam-resistant, line-of-sightcommunications using a time division multipleaccess (TDMA) architecture. The system has amaximum range of 500 miles. The Marine Corps

5-36 _______________________________________________________________________________________________ MCWP 6-22

will implement the JTIDS terminal in the TAOMto enhance coordination of antiair warfare. Theother services are fielding JTIDS in aircraft aswell as in air defense command and control sys-tems. JTIDS is also an integral component ofNATO air defense systems.

5504. Integrated Broadcast Services

IBS is a worldwide, DOD standard network fortransmitting tactical and strategic intelligence in-formation and targeting data. IBS will integrateintelligence broadcast using the DII for bothbroadcast and interactive dissemination. IBS willmigrate tactical terminals/receivers to a single, re-lated Joint Tactical Terminal (JTT) family. TheJTT Common IBS modules will enable seamlessinformation displays on GCCS. The goal of IBS isto resolve the proliferation of stovepipe intelli-gence broadcast formats by providing the tacticalcommander with an integrated means of deliver-ing intelligence information to the warfighter.

5505. Commander’s Tactical Terminal

CTT (AN/USC-55) is a multi-service developedspecial application UHF satellite communicationsreceiver that can be dedicated to receiving criti-cal, time-sensitive intelligence to commandersand intelligence centers at all echelons, in near-re-al-time, at GENSER or SCI levels. Its receiverprovides one full duplex and two receive-onlychannels. Planned concept of employment forCTT is similar to that of the tactical receiveequipment (TRE); i.e., fielded widely within theMAGTF to allow access to intelligence broad-casts and intelligence collectors. Full operationalcapability for CTT is expected by the fourth quar-ter of fiscal year 1998.

5506. The Joint Tactical Terminal

JTT, with its common IBS modules, is capable ofreceiving diverse broadcasts into terminals with

common capabilities. These terminals use multi-ple communications transmission paths and soundinformation management to provide the ability foreach user in the battlespace to view a common op-erational picture/common tactical picture. Themodular feature of these terminals allows produc-ers and users in the MAGTF to incorporate IBSinto their existing CIS. Hardware and softwareexisting in the MAGTF (IAS, TCO, ACE sys-tems, etc.) can integrate the common IBS mod-u l e s t ha t add t he r equ i r ed capab i l i t y .Alternatively, users may also obtain completelyconfigured tactical terminals. Employment ofJTT/common IBS modules facilitates a seamlesstransition from current dissemination systems tothe IBS without degrading the capabilities provid-ed by the current systems.

5507. TROJAN SPIRIT II

TROJAN SPIRIT II consists of two heavy HM-MWVs with lightweight multipurpose shelters,trailer-mounted power generation units, and atowed 2.4-meter (C, Ku band) or 6.1-meter tri-band (C, Ku, and X band) antenna. The 6.1-meterantenna is not used by the Marine Corps. The sec-ond heavy HMMWV is used as a maintenanceshelter. TROJAN SPIRIT II is a mobile, SHFSATCOM system that is capable of receiving,transmitting, and processing multimedia products,including imagery and secure dial-up voice, data,facsimile, and video.

TROJAN SPIRIT II will be deployed to provideGENSER and SCI communications for intelli-gence operations. TROJAN SPIRIT II provides16 channels of digital voice or data when used ex-clusively for SCI or collateral secret traffic. Thismode of operation allows a maximum T1 aggre-gate data rate. If both SCI and collateral secrettraffic are handled, a 2-channel separation be-tween SCI and collateral secret traffic results in alower aggregate data rate. TROJAN SPIRIT IIprovides LAN communications supported by twoseparate Ethernet LANs (SCI and collateral se-cret) and entry to the SIPRNET and the JWICS.


5508. Global Broadcast System

The GBS will augment and interface with otherCIS and provide a continuous, high-speed, one-way flow of high volume information to deployedor garrisoned Marine units. GBS will support rou-tine operations, training and military exercises,crisis, situational awareness, weapons targeting,intelligence, and the transition to and conduct ofopposed operations short of nuclear war. GBSwill provide the capability to quickly disseminatelarge information products to various joint andsmall user platforms. GBS coverage will beworldwide.

5509. JTF Enabler Module

The JTF enabler provides the JTF, Marine com-ponent, or MEF commander an initial, in-theater,immediate, reliable command and control capa-bility. Detailed guidance for the employment ofCIS in support of joint operations is found in JCSPub 6-0, Doctrine for Command, Control, Com-munications, and Computer Support to Joint Op-erations; JCS Pub 6-02, Joint Doctrine for theEmployment of Operational/Tactical Command,Control, Computer, and Communications Sys-tems; and the CJSM 6231 Series, Manual for Em-ploying Joint Tactical Communications.

The module includes the personnel and equip-ment needed to establish high-capacity, long-haulcommunications links and provide informationsystems services. This capability would be usedby the JTF, Marine component, or MEF com-

mander to support preparations for the introduc-tion of follow-on forces. The Marine Corpscurrently augments MEU(SOC)s with this capa-bility. In coordination with the commander of theamphibious squadron, the organic CIS of the am-phib ious ready group and the embarkedMEU(SOC), augmented with an enabler module,can support initial command and control of fol-low-on forces from either afloat or ashore.

The JTF enabler includes the GCCS deploymentand operations modules, such as the JMCIS/TCOmodule; the CTAPS; the JDISS; and secure elec-tronic messaging. Currently, an AN/TSC93B(V)1 is used to provide high-capacity, long-haul connectivity. The personnel and equipmentfor the enabler are currently provided from the or-ganic assets of the supporting comm battalion.

The JTF or follow-on forces enabler allows a JTF,Marine component, or MEF commander to fall inon assets carr ied by a forward-deployedMEU(SOC) and commence operations withoutdelay. The MEU(SOC) can provide limited com-mand and control systems support ashore for ashort period of time. The responsibility for CISsupport for the JTF HQ shifts to the JCSE and theJTF HQ organic information systems support up-on their arrival in theater. The JTF enabler mod-ule will usually backload with the MEU(SOC)upon arrival of sufficient JTF HQ assets and capa-bilities in order to be ready for employment as anenabler for additional follow-on forces. The en-abler module, however, may also remain as partof the MEF CE or Marine component HQ.

(reverse blank)

Chapter 6

Planning and Execution

Effective C2 depends on the effective and efficient operation of CIS. These systemsprovide the means to develop a common operational picture (COP); to prepare andrapidly disseminate OPLANs and OPORDs; and to monitor, direct, and coordinatemaneuver, fires, and logistics. In turn, the effective, efficient operation of these CISdepends on detailed planning that is thoroughly integrated with the operation plan-ning process. Coordination and integration are key to ensuring development ofOPLANs that are supportable from a CIS perspective and CIS plans that are respon-sive to the needs of the operation. Normally, the commander assigns the responsibili-ty for detailed preparation of CIS plans and orders to the G-6/S-6, who is the CISO.

The CISO should be thoroughly familiar with the form, content, and techniques forpreparing these documents. This chapter describes the planning process as it pertainsto the CISO, establishes basic planning guidance, discusses planning considerations,and describes CIS planning documents. This information is provided to assist the CISplanner in participating in the overall operation planning process and in preparingCIS plans that are complete and effective and that support the mission of the MAGTFand the Marine component.

Section I

Overview

Preliminary planning is conducted before the re-ceipt of a mission. It is based on the analysis offacts and trends to predict probable commitmentsand to anticipate what action will be required toaccomplish future tasks. Preliminary planningmakes use of available information and logical as-sumptions to prepare studies, estimates, and plans.The depth of these studies, estimates, and plans isbased on the time available. They are refined asmore information becomes available and are thebasis for subsequent planning. Other measuresthat may be taken to reduce planning time includethe use of existing SOPs, concept plans (CON-PLANs) and OPLANs that can be tailored and re-fined. Once a mission is received, operationplanning involves six steps:

● Mission analysis.● COA development.● COA analysis.● COA comparison/decision.● Orders development.● Transition to execution.

MCWP 5-1 (draft) provides the details of theMarine Corps planning process.

All planning is time constrained. To maintain op-erational tempo, an organization must employtechniques that reduce the overall time required toplan. Effective employment of information sys-tems and information management procedures

6-2 ________________________________________________________________________________________________ MCWP 6-22

permits concurrent, collaborative planning amongstaff sections and between echelons. This speedsup the planning process and, at the same time, re-sults in better coordinated plans.

6101. Planning Information

The CISO collects and analyzes all available in-formation relative to the impending operation andthe resources available to support the operation toprovide the commander and other staff memberswith sound advice for the employment of CIS.The CISO uses this information as the basis forestimating the situation, making recommenda-tions, and preparing CIS plans.

a. CommanderThe commander briefs the staff and subordinatecommanders on the mission as part of the missionanalysis. This briefing includes the action to be ac-complished as well as the commander’s intent,which describes the desired end state. At the endof the mission analysis, the commander providesinitial planning guidance: the results of the mis-sion analysis, necessary assumptions and con-straints, COAs to be considered, and any otherconsiderations that may influence planning. Afterissuing this guidance, the commander keeps thestaff and subordinate commanders informed on acontinuing basis as mission-related information isreceived and decisions are made.

b. StaffThe CISO is the G-6/S-6 and, in this capacity, hasstaff cognizance for the overall CIS effort. TheCISO must have continual interaction both withother staff officers and with supporting and subor-dinate CIS unit commanders. CISOs must obtainessential information from other staff members tounderstand and support the developing situation.Information that affects the employment of CISmust be aggressively pursued. Close coordinationis critical to the establishment of effective C2.

c. Other HQsThe CISO must obtain information from otherHQs during planning. Higher HQs may provideCIS support, impose special communications re-quirements, or issue special communications in-structions for the operation. Subordinate HQsmay require additional personnel, equipment, orother assistance to accomplish their mission.

6102. Coordination

Planning must be coordinated not only within thelocal command, but with the HQs of senior, sub-ordinate, adjacent, supported, and supportingunits. The proper coordination of planning effortsinvolves the prompt, continual exchange of infor-mation, decisions, plans, orders, and instructionsamong all interested parties. Coordination meansinclude—

● Liaison with all personnel responsible for theexchange of planning information and coordi-nation of planning activities.

● Interaction among G-6s/S-6s and communica-tions units and detachments.

● Appropriate coordination and dissemination ofinformation by staff sections.

● Coordination of planning documents.● Staff conferences for the exchange of informa-

tion between HQs and development of mutual-ly-agreed-upon COAs.

● Timely briefings to keep the commander andstaff informed of the current situation.

6103. Security

Operational security, COMSEC and COMPUSECare important considerations during the planningof any operation. To maintain surprise, it is neces-sary to deny the enemy prior knowledge of detailspertaining to an operation. Measures must also beinstituted to control access to information andprotect information systems and communicationsnetworks.


6104. Estimates

The CIS officer prepares estimates to assist thecommander in the analysis of alternative COAs.On the basis of factors such as terrain, weather,distance, scheme of maneuver, and availability ofpersonnel and equipment, the CISO predicts thesupportability of COAs from a CIS perspective.The CISO also provides the commander with rec-ommendations on how the available means canbest support the selected COA. Formal, detailed,written estimates are usually prepared only duringpreemployment. Once execution begins, writtenestimates are seldom used. Whenever the situa-tion warrants, a revised estimate is briefed to thecommander and/or other staff officers for theirconsideration in the planning process. In eithercase, the CISO’s estimate should derive from alogical sequence of thought that considers all crit-ical elements of CIS planning. A suitable form fora formal CIS estimate is included in appendix I.

6105. Recommendations

The CISO makes recommendations to the com-mander, as required, to assist in establishing poli-cies and making decisions. The CISO should alsooffer recommendations to other staff officers andsubordinate commanders on CIS matters. Al-though the CISO may follow formal or informalprocedures in arriving at and making recommen-dations, many of the recommendations are basedon observations or mental estimates. Recommen-dations based on other written studies or formalestimates are usually submitted in writing. What-ever the procedure, recommendations are theproduct of careful analysis and comparison con-strained by the time available. They are candidand objective, are based on the best information

available, and, when appropriate, are coordinatedwith other staff sections. Recommendations areconcise and presented in a form that requires onlythe commander’s approval or disapproval.

6106. Preparing Plans

CIS planning is simplified when it is considered inreverse order (e.g., when developing a C3 SystemsAnnex for an amphibious operation, first addressthe assault phase and move in reverse order backto the planning and embarkation phases). A widerange of planning considerations is covered in thenext paragraph. The maintenance and use of astanding CIS Annex, Annex K, which can be tai-lored for specific operations, greatly facilitates thetimely preparation of OPLANs. (See app. J.) TheCIS procedures that remain constant, such as theMAGTF internal telephone numbering scheme,should not have to be re-planned regardless of thetime, location, or type of operation. The CIS plan-ner may then concentrate on specific require-ments for a particular operation, with only a quickreview of the other items that may have changedover time.

6107. Implementing Plans

Once a CIS plan or annex is completed and ap-proved, it must be implemented effectively. Closesupervision and frequent examination of the statusof information systems and communications net-works by the CISO and staff are essential. Planswill inevitably be modified as the operational situ-ation develops. The CISO and staff must keepabreast of developments and be prepared to adaptthe CIS plan to the changing situation to supportand maintain MAGTF operational tempo.

6-4 ________________________________________________________________________________________________ MCWP 6-22

Section II

CIS Requirements

The CISO must determine the resources requiredto support the operation and request augmentationif needed. To do this, the CISO must first deter-mine the information processing and informationtransfer requirements to be supported. This in-volves extensive coordination with CISOs ofhigher, subordinate, adjacent, supporting, andsupported units. All aspects of the operation mustbe considered to accurately determine the require-ments for information processing and informationexchange.

6201. Mission

The mission statement describes, in conciseterms, the location of the operation, the time itwill occur, and the tasks to be accomplished. Themission includes the commander’s intent—thepurpose of the action. Careful review of the mis-sion gives the CISO a general idea of what overallCIS resources will be required to support the op-eration. At the component level, the possible des-ignation of the Marine component commander asa functional component commander or the possi-ble requirement to provide the nucleus of a JTFHQ would drive a significant increase in CIS re-quirements.

6202. Courses of Action

A COA is an approach to accomplish the mission.The CISO develops estimates of supportabilityfor each COA considered while at the same timeinfluencing COA development on the basis ofCIS capabilities and limitations.

6203. Concept of Operations

The concept of operations generally depicts thescheme of maneuver, the employment of support-

ing fires, and in an amphibious operation, thelanding plan. Analysis of the concept of opera-tions gives the CISO an understanding of whenevents will occur, projected locations and move-ment of units and C2 facilities, and the distancesthe communications network must span.

6204. Task Organization

The task organization lists all tactical, administra-tive, and service groupings with the commandersof each. It depicts the organization for combat andindicates the command relationships of the as-signed forces. Review of the task organizationhelps the CISO determine the requirements for in-ternal and external information flow to be sup-ported by the communications network. Reviewof the task organization also enables the CISO toidentify the C2 facilities and their associated re-quirements for information systems support. Amajor consideration is whether the componentand the MAGTF commanders are supported byseparate staffs and, if by separate staffs, whetheror not those staffs are collocated. The requirementto support separate, geographically separated,component and MAGTF CE HQs will severelystress the capabilities of a communication battal-ion.

After the CISO has determined the requirementsto be supported, the factors that may affect theemploymen of information systems and commu-nications networks are analyzed. These include:

● Available resources.● Enemy situation.● Environment.● Information management plan.


6205. Available Resources

The CISO must consider all available resources todetermine the extent of support that can be pro-vided and to determine shortfalls in the capabilityto support the mission. This includes resourcesboth organic and external to the MAGTF.

a. PersonnelThe number, military occupational specialties,state of training, and availability of replacementsare of primary concern. Individual mobilizationaugmentee billets must be filled, contractor sup-port requirements must be identified and, whenappropriate, agreements for other-Service aug-mentation must be exercised.

b. Equipment and ServicesThe availability, condition, and operational char-acteristics of equipment must be identified, asmust the availability of external telecommunica-tions services. This includes identifying equip-ment available through joint or other-Serviceaugmentation and telecommunications servicesavailable through commercial sources, and, insome cases, host nation support. Points of contactfor information concerning the employment andmaintenance of equipment should be researchedin advance of operations. The Marine Corps Sys-tems Command, the Marine Corps Network Oper-ations Center (NOC), the Command and ControlSystems School, and the Marine Corps Communi-cations-Electronics School are excellent sourcesof information, as are equipment manufacturersand suppliers. Information on interfaces to joint,other-Service, allied, commercial, and host nationequipment should be researched.

c. SoftwareThe compatibility and interoperability of CIS aremajor concerns. Even in a single information orcommunications system, different versions or re-leases of software may be incompatible. For ex-ample, various versions of the GCCS (JMCISUnified Build and MAGTF C4I Software Base-line) are not compatible and can preclude infor-mation sharing between the embarked MAGTFand shipboard systems. In Operation Desert

Storm, newly fielded TRI-TAC equipment re-quired extensive software modifications toachieve interoperability between Services andwith joint HQs. The CISO must ensure that usersof CIS are aware of the potential for incompatibil-ity and take appropriate action to ensure that sys-tems are interoperable and compatible. MCTSSAis responsible for software support of fielded sys-tems, and MEF CISOs should coordinate withMCTSSA to implement new releases of softwareand to identify and resolve software problems.

d. SuppliesThe quantity and condition of available suppliessuch as wire, batteries, and repair parts, and theavailability of resupply in the objective area needto be coordinated.

e. MaintenanceMaintenance requirements must be anticipatedand support planned for each phase of the opera-tion. Particular attention to the availability of testequipment is necessary to support maintenanceefforts in the objective area. Planning must takeinto consideration the availability of maintenancesupport through inter-Service agreements andhost nations.

6206. Enemy Situation

Enemy intelligence, reconnaissance, and EW ca-pabilities can significantly degrade and in somecases exploit our CIS. The potential for disruptionof MAGTF command and control must be under-stood and countered. The CISO should always as-sume that the enemy has the capabilities tointercept, locate, exploit, deceive, and/or other-wise degrade MAGTF CIS. The enemy threatscan be countered through—

● Threat awareness.● Sound COMSEC and COMPUSEC proce-

dures.● Restricted RF emissions.● Employment of secure, jam-resistant, low-

probability-of-intercept transmission equip-ment.

6-6 ________________________________________________________________________________________________ MCWP 6-22

● Use of wire and messengers.

Chapter 7, sections I and II, address COMSECand COMPUSEC.

The CISO must take into consideration the threatcapability to employ NBC weapons. Given thecontinued proliferation of weapons of mass de-struction to both outlaw nations and non state ac-tors, even military operations on the lower end ofthe conflict spectrum may include their use. Con-sequently, the CISO must plan for CIS support ina contaminated environment and be prepared toprovide rapid decontamination of CIS equipmentand facilities. (See app. K.)

6207. Environment

The CISO must consider those physical character-istics such as terrain, weather, and the electro-magnetic environment of the objective area thatmay affect the employment of CIS.

a. TerrainThe CISO should be aware of the topography,vegetation, road networks, soil conditions, andother terrain features in the objective area. Theterrain has a major bearing on the location of fa-cilities, sitting of antennas and relays, effectiverange of line-of-sight transmission systems, in-stallation of wire lines, and effectiveness of mes-senger service.

b. WeatherThe climatic conditions in the objective area de-termine the requirements for special equipment orsupplies such as heaters, air conditioners, shelters,or cold weather batteries. Many CIS do not oper-ate effectively under conditions of extreme heator cold, and heavy precipitation can adversely af-fect radio transmissions. The CISO must plan tooperate under all weather conditions that will beencountered during the operation.

c. Electromagnetic InterferenceThe CISO must take into account the electromag-netic environment in the AO. Electromagnetic in-

terference, both natural and manmade, canseverely degrade the performance of communica-tions systems. An effective training program foroperator and maintenance personnel is the key tobeing able to communicate effectively in an ad-verse electromagnetic environment. Informationon the electromagnetic environment may be ob-tained from the Joint Spectrum Center and inMCRP 6-22B, MSP for Spectrum Management ina Joint Environment.

d. FacilitiesThe CISO should take into account the infrastruc-ture in the AO, especially telecommunicationsand electric power generation and distribution fa-cilities, and its potential availability eitherthrough host nation support or capture.

6208. Information Management Plan

The information management plan describes theprocesses by which information will be created,processed, maintained, and disseminated withinthe organization. Normally, the information man-agement plan will consist of a set of SOPs thatare updated as necessary to fit the circumstancesof a particular exercise or operation and promul-gated as an annex to the OPLAN or OPORD. Theunit information management officer, with theguidance of the C/S or XO, and in coordinationwith the information management officers of eachstaff section and subordinate units, develops theinformation management plan. The CISO mustensure that the employment of CIS support the in-formation management plan. The informationmanagement plan will include the following:

● Procedures by which information requirementsare identified, developed and prioritized, in-cluding how CCIRs are nominated, approved,collected, reported, maintained, and dissemi-nated. The information management plan willidentify and assign responsibility for standingCCIRs (key items of information that will berequired in almost any situation). StandingCCIRs must be reviewed for relevancy andmodified, expanded, or deleted as necessary.


The CCIR procedures will include guidance onfiltering and fusing raw data before submissionand dissemination.

● Procedures by which the COP is maintainedand shared. This will include guidance on thelevel of detail (e.g., a division COP might dis-play friendly units down to the battalion level,and a battalion COP might display friendlyunits down to the platoon level); assignment ofresponsibility for the quality and integrity ofthe COP database, including the managementof air, ground, and sea tracks/unit locations;and assignment of responsibility for maintain-ing the status of friendly and enemy units. Eachstaff section will be assigned responsibility forproviding status information for the functionalareas over which they have cognizance.

● Designation of data standards, including stand-ards for symbology, report/message formatsand data element standards.

● Procedures supporting the effective flow ofboth routine and time-sensitive information:• Automated networking techniques such as

news groups, home pages, and other Inter-net-like methodologies.

• Policy governing the use of e-mail. • Supply-push and demand-pull approaches to

information dissemination, as well as eche-lon skipping where appropriate (e.g., re-sup-ply reques ts bypass ing in termedia teechelons).

• Manual as well as automated procedures forhandling information dissemination. Tacticalechelons must avoid overloading communi-cation circuits. Particular attention should begiven to the best approach for transferringhigh-volume data formats such as imagery,video, maps, and overlays. Messengers andhard copy OPORDs remain a reliable meansof information dissemination.

• Procedures for the design, maintenance, ac-cess, use, synchronization, and integration ofdatabases supporting command and control.

• Procedures and schedules for daily briefings,meetings, and reporting. This daily opera-tions cycle is developed in coordination withall staff sections and subordinate units. Uponcommencement of operations, the C/S or XOmay modify the operations cycle as neces-sary to maintain tempo or to adjust to the un-folding situation.

6-8 ________________________________________________________________________________________________ MCWP 6-22

Section III

Pre-Deployment Preparation

Mission accomplishment often depends on pre-deployment planning and preparation. Numerousactions must be accomplished by the G-6/S-6 be-fore deployment. Appendices C, F, G, H, and K ofthis publication and CJCSM 6231.07A (app. G),contain pre-deployment checklists that should beconsidered for incorporation into unit SOPs.

6301. Review Existing Plans and Orders

OPLAN and OPORD communications-electron-ics/CIS annexes, time phased force deploymentdata (TPFDD) files, planning guidance, and anyother appropriate documentation, including after-action reports and CIS annexes from previous op-erations of a similar nature and unit SOPs, shouldbe reviewed. Items not covered adequately in ex-isting OPLANs or OPORDs should be identified.The CISO should prepare and submit updated in-formation for the TPFDD file.

6302. Prepare Troop and Equipment Lists

Personnel requirements must be determined andthe troop list prepared. The troop list should in-clude rank, military occupational specialty, linenumber, and billet description. The CISO shoulddetermine equipment requirements and prepare anequipment list summarizing all Class VII items tobe deployed.

6303. Request Augmentation

Augmentation of personnel and/or equipmentshould be requested if shortfalls exist in either ar-ea. The CISO must be familiar with any existing

memorandums of agreement for support fromother Services and the procedures for exercisingthose agreements, as well as procedures for ob-taining support from the Reserve. At the presenttime, both the Army and the Air National Guardhave memorandums of agreement in effect withthe Marine Corps to provide a portion of the com-munications equipment and personnel required tosupport two Marine component HQs.

6304. Coordinate Frequencies

The type and number of frequencies requiredshould be identified in sufficient time and for-warded to the frequency manager who is found at,but not limited to, the joint, CINC, Force, MEF,and Base levels. Liaison should be made with thefrequency coordinator so that required frequen-cies can be obtained, assigned, and distributed insufficient time. The frequency coordinator pro-vides guidance on frequencies used in garrison,during embarkation, in transit, and in the AO.

6305. Request Satellite Access

The CISO should identify requirements and coor-dinate requests for UHF and SHF satellite accessthrough the frequency manager.

6306. Compile a Publications Library

General and technical publications need to be em-barked to ensure that deployed units have accessto the information they need. It may be advanta-geous to maintain some publications on massstorage media. However, essential publicationsshould be available in hard copy.


6307. Initiate Telecommunications Service Requests

To request U.S. or host nation commercial re-sources, a telecommunications service requestmust be submitted. The telecommunications ser-vice request format is found in various DISA Cir-culars and should also be included in the unit CISSOP. Telecommunications service requests arenormally submitted via the chain of commandwell in advance of the operation.

6308. Conduct Communications/Command Post Exercises

These exercises are designed to test personnel andequipment readiness. In a communications exer-cise, the viability of the communications networkis tested. In a CP exercise, unit staff functioningand information systems support are exercised toprepare for an operation. The optimal way to testboth the staff and the adequacy of CIS support isby combining these two exercises. The staff be-come familiar with the information systems theywill employ in the operation, and the CISO is ableto test the adequacy of the communications net-work as well as the information systems supportbefore operational employment.

6309. Provide CIS Support for Embarkation

Support is required throughout the embarkationphase. Movement to sea and aerial ports of em-barkation requires communications nets for con-voy control and coordination, and the actualembarkation of troops, equipment, and supplies ismost efficient when supported with informationsystems. The preferred means of providing thissupport is through the use of equipment and per-sonnel who are not deploying with the MAGTF.

6310. Submit Communications Guard Shifts

Upon deployment, a unit must submit a communi-cations guard shift message to ensure continuedreceipt of its record traffic. Guard shift messagesare used to update the Common Source RouteFile. Guard shift procedures are contained in na-val tactical publication (NTP) 4, Fleet Communi-cations. Deployed organizational and individuale-mail systems must also be established and re-designated for the deployment period.

6311. Request COMSEC Material

Requests for appropriate cryptographic material(equipment keys, etc.) must be expeditiously sub-mitted through the appropriate chain of commandto the controlling authority for each key required.The controlling authority validates the requestand forwards it to the director of the Communica-tions Security Material System for processing.The requisitioning process can be lengthy.

6312. Coordinate Logistics

The G-6/S-6, in close coordination with the G-4/S-4, must plan for logistic matters. The followingareas require special attention.

a. EquipmentTo ensure equipment readiness, limited technicalinspections should be conducted on all equipmentscheduled for embarkation. These inspectionsmust be conducted as early as possible to allowtime for correction of deficiencies before embar-kation. Waterproofing and weatherproofing ofequipment before deployment are essential to pro-tect the equipment while in transit.

b. Power RequirementsThe G-6/S-6 officer must identify to the G-4/S-4the electrical power requirements.

6-10 _______________________________________________________________________________________________ MCWP 6-22

c. Embarkation MaterialUnits should maintain materials required for con-struction of embarkation boxes to meet missionrequirements.

d. Technical Representative SupportBecause of technical sophistication, contract tech-nical representatives from the manufacturer arerequired to maintain some critical low-densityequipment. Technical representative support isavailable for exercises and operations but requiresconsiderable lead time. Requests for such supportshould be submitted in accordance with currentdirectives.

e. Hazardous CargoHazardous cargo is any material that is prone tofire, explosion, or toxic seepage, thereby present-ing an inherent danger to personnel and equip-ment as well as to ships and aircraft. This type ofmaterial must be identified, packaged accordingto existing transportation regulations, and certi-fied by a competent authority. Many restrictionsapply. It is critical that these matters be addressedbefore embarkation so that vital equipment andsupplies are not rejected by loadmasters or com-bat cargo officers during embarkation.

f. Repair and MaintenanceSustained operations result in the need to main-tain and repair equipment. Required repair parts,

based on the equipment density list, must eitheraccompany the deploying unit or be staged in theAO. In addition to repair parts, appropriate testequipment and maintenance personnel must beavailable. Regardless of the operational readinessof equipment at embarkation, it will deteriorate ifnot properly maintained during sustained opera-tions. Required items are often held in a contin-gency block that is identified by need and heldready for issue on demand. It is the responsibilityof the CISO to request this block through the sup-ply officer.

g. SuppliesIn addition to repair parts, the G-6/S-6 must en-sure that adequate provision is made for re-supplyof other critical, high-volume consumables suchas batteries and petroleum, oil, and lubricants.

6313. Effect Liaison/Coordination

For the CISO to accurately assess requirementsand plan the necessary CIS support, close liaisonand coordination with senior, adjacent, support-ing, and subordinate CISOs as well as other staffofficers are essential. Appendix P and CJCSM6231.07A, appendix A, identify liaison/coordina-tion points of contact.


Section IV

CIS Plans, Orders, and Directives

CIS plans and orders describe how CIS will beemployed to support the commander in the exer-cise of C2. The G-6/S-6 is responsible to the com-mander for preparing the following plans, orders,and directives:

● CIS SOPs.● Communications-electronics operating instruc-

tions (CEOI).● CIS plan.● CIS estimate● CIS concept.● Paragraph 5 of the OPORD or OPLAN● CIS Annex (Annex K).

The G-6/S-6 is often required to provide CISguidance for inclusion in other annexes of anOPLAN or OPORD. This may include the air an-nex and the naval gunfire annex. Planners mustensure that all necessary CIS guidance and in-structions are covered in Annex K, other designat-ed annexes where certain CIS instructions areappropriate, or both. The practice of cross-refer-encing annexes without adequate harmonizationcan result in gross omissions of required CISguidance. Plans and orders follow standard for-mats. For a detailed discussion of standard for-mats for OPLANs and OPORDs, see MCWP 5-1(draft).

6401. Standing Operating Procedure

The SOP is one of several types of orders that thecommander develops and uses to accomplish themission. It is a set of instructions covering thosefeatures of operations that lend themselves to adefinite or standardized set of procedures without

loss of effectiveness. The procedures are applica-ble unless ordered otherwise. The SOP reflectsapproved doctrine as published in current doctri-nal publications, directives, and regulations, mod-ified to satisfy local operating conditions and thepolicies of the command. The SOP is normallyfollowed, but may be modified, tailored, or evencompletely discarded depending on the situation.In no way should the SOP be allowed to reduceflexibility and adaptability or to limit creativityand initiative. The SOP is usually referred to inthe OPORD with exceptions identified. Theamount and type of information to be included inan SOP must be carefully determined. Proceduresmust be clear and concise. In the absence of spe-cific orders to the contrary, the instructions con-tained in the SOP are guiding. The SOP—

● Reduces the need for other types of orders andsimplifies the preparation and transmission oforders.

● Simplifies training by establishing uniformpractices for the unit.

● Promotes understanding and teamworkthroughout the command.

● Facilitates and expedites execution of routineprocedures.

● Minimizes confusion and error.

The scope of the SOP varies with the echelon ofthe preparing command. An SOP prepared by adivision is broad in scope and provides essentialinstructions for all major elements of the division.The SOP of a subordinate unit applies only to thatindividual unit and its subordinate elements. Asthe scope of the SOP narrows, the amount of de-tail increases. For example, an SOP for a sectionis detailed, describing what each individual doesand in what sequence with respect to the actionsof other individuals in the section.

6-12 _______________________________________________________________________________________________ MCWP 6-22

a. FormatAlthough there is no established format for anSOP, one of the two following formats is general-ly used. An SOP may be formatted as an all-inclu-sive document containing in the main bodysections and paragraphs detailing the duties andresponsibilities of subordinate units and, whereapplicable, of personnel. This format does nothave annexes or enclosures. The other approach isto publish the main body of the SOP as a basicdocument containing instructions of a general na-ture with annexes for technical details and specif-ic instructions for individual units and/orpersonnel. For example, the basic document couldcontain information for the communications bat-talion as a whole with annexes for different func-tional areas such as TECHCON and systemsplanning and engineering. SOPs prepared by sub-ordinate units must comply with and be coordi-nated with pertinent parts of the SOP of the highercommand. SOPs should not repeat practices orprocedures governed by other directives or docu-ments that are readily available to all elements ofthe command unless such repetition is required toclarify local operating practices.

b. Suggested Content● References such as MCWPs, field manuals,

technical manuals, regulations, and the SOPsand CEOI of higher commands.

● Planning checklists.● Training instructions outlining general training

standards. Detailed instructions are normallycontained in quarterly training schedules.

● Information systems security instructions thataddress both COMSEC and COMPUSEC. In-structions should be limited to those that areapplicable to all elements of the command andare not contained in the command CEOI, as thepurpose of this section should be to developand maintain CIS security awareness through-out the unit.

● Physical security instructions designed to de-velop an awareness for physical security and topromulgate and standardize physical securityprocedures throughout the unit.

● Instructions for the operation of communica-tions centers, including location and procedures

for transmittal, receipt, and processing ofrecord traffic.

● Procedures covering the exchange of organiza-tional and individual e-mail. The authorizationfor use and the records to be maintained shouldbe prescribed.

● Procedures for wire communications, includingwire and cable installation practices; priority ofinstallation; tagging procedures; general guid-ance pertaining to locations of switching, rout-ing, and patching facilities; LANs and terminalequipment; and instructions governing theplacement of calls. Also, inclusion of directoryservice information, guidance for obtaining ser-vice, and instructions for maintenance of equip-ment and lines should be considered.

● Instructions pertaining to the planning, installa-tion, operation, and maintenance of SCR equip-ment and guidance for the composition andoperation of radio nets, including those re-quired for data communications. Informationabout data interface modules used with the ra-dios and the advance planning required for fre-quency hopp ing r ad io s and TACSATcommunications should be included. Actions tobe taken in the event of imitative communica-tions deception or jamming should be defined.

● Instructions pertaining to the planning, installa-tion, operation, and maintenance of theswitched backbone that apply to all elements ofthe command. Detailed instructions on opera-tions should be published in the SOP of the unitthat owns the equipment. Joint and other-Ser-vice interfaces, means of entry into the DISN,and planning for TACSAT communicationsshould be addressed.

● Instructions pertaining to the planning, installa-tion, operation, and maintenance of LANs, in-cluding switch, router, and/or server planning,installation, operation, and maintenance.

● General procedures to be employed by all usersfor the planning, installation, operation, andmaintenance of radio-wire integration facilities.

● Instructions pertaining to the general use anddistribution of visual and sound signal devices(flags, lights, pyrotechnics, panels, arm-and-hand signals, whistles, sirens, bells, voice am-plifiers, explosive devices, etc.).


● Procedures to be followed to obtain frequen-cies, restrictions on the use of frequencies, pro-cedures for report ing interference, andconditions under which radio silence is re-quired.

● Instructions covering the identification of cir-cuits and systems for installation and controlpurposes.

● Special communications support procedures(e.g., R and Y routers) that may be required forintelligence systems in the command.

● Identification of the various command, control,and coordination agencies, centers, and cells(this manual refers to these entities genericallyas command and control facilities, for example,COC, DASC, FSCC, TACC, and TAOC) with-in the command and their requirements forinformation systems support and communica-tions connectivity.

● General procedures to be employed by all usersfor the planning, installation, operation, andmaintenance of general-purpose computers andgeneral guidance for interfacing all tactical in-formation systems into the communicationsnetwork. Detailed instructions on the operationof individual tactical information systemsshould be published separately.

● General instructions pertaining to communica-tions control not covered elsewhere in the SOP.More detailed instructions on communicationscontrol will be promulgated in the CIS SOPs ofcommunications units.

● Information pertaining to the location of theCISO and C2 facilities, selection of CPs, in-structions governing the preparation of theCEOI, subordinate unit SOPs, and instructionspertaining to CIS planning for future opera-tions.

c. Communications UnitsThe CIS SOP for a communications unit is uniquein that it addresses the operation of the unit in theexecution of its primary missions. Its scope is de-termined by the type of unit, the amount of detailthe unit commander desires, and the echelon ofcommand to which the unit is assigned. As a min-imum, the SOP should include—

● Specific responsibilities of each major subordi-nate element.

● Instructions on routine operations of such im-portance that continuing instructions are desir-able.

● Instructions governing the execution of all re-sponsibilities for CIS support.

● Instructions pertaining to routine administra-tive and logistic support, including personnelpolicies and procedures, supply and mainte-nance procedures, inspection procedures, phys-ical security, and other areas as directed by theunit commander.

Additional subjects to consider include specificresponsibilities for sections and/or individuals aswell as for subordinate units, guidance for inclu-sion in the SOPs of subordinate units, CIS poli-cies, key references, exercise guidelines, safetyinstructions, and displacement procedures.

6402. CEOI

The CEOI contains the technical guidance re-quired to establish and maintain communicationssupport of operations. The CEOI amplifies theCIS SOP by providing detailed guidance for thecoordination and control of communicationsmeans and functions. SPEED includes the RevisedBattlefield Electronic CEOI System (RBECS), amodule to support generation of the CEOI. Inputis normally requested from subordinate com-mands by higher HQ. Sufficient copies of theCEOI should be maintained by the issuing HQ toallow issue to other units that may be attached foran operation. The following information and in-structions can usually be included in the CEOI:

● Call sign assignments.● Frequency assignments.● Radio guard charts (app. M).● Radio net identifiers.● Telephone directory names and numbers.● Identification and marking panel codes.● Signal panel message instructions.● Pyrotechnic and smoke codes.

6-14 _______________________________________________________________________________________________ MCWP 6-22

● Ground-to-air signals.● Sound warning signals.

6403. CIS Plan

A CIS plan is normally created by combining theCIS SOP and the CEOI. This combined documentthen becomes a basic CIS plan. The tactical andadministrative instructions of the SOP form thebody of this plan. The operating instructions ofthe CEOI are normally issued as a supplement.During the discussion of the tactical and adminis-trative instructions in the body, reference shouldbe made as necessary to the supplement that con-tains related technical operating instructions. Thepreparation of the operating instructions as a sep-arate supplement facilitates revision or extractionas the need arises.

6404. CIS Estimate

As discussed earlier, the CIS estimate is a tool orprocedure the G-6/S-6 uses to assist the com-mander in determining the best COA to accom-plish a mission. On the basis of CIS estimates, theG-6/S-6 provides the commander with insights in-to the supportability of alternative COAs and rec-ommendations on how available means can bestsupport the selected COA. Appendix I provides asuggested format for the CIS estimate. The pro-cess of developing a CIS estimate is analogous toand completely integrated with the process of de-veloping a preferred COA for the operation. De-pending on the time available, several iterationsmay be performed as COAs are refined and modi-fied, and the CIS estimate is updated accordingly.The following five steps are useful for preparingthe estimate:

● Develop an understanding of the mission, thecommander’s intent, and the situation.

● Consider all factors that affect employing CIS,and develop alternative approaches to satisfyCIS requirements.

● Analyze each alternative to determine its ad-vantages and disadvantages.

● Compare the alternatives and select the bestone.

● Translate the selected solution into a decision(if the commander’s estimate) or recommenda-tion (if the G-6/S-6 estimate).

6405. CIS Concept

After developing the CIS estimate and gaining thecommander’s approval, the CISO prepares theCIS concept. The concept outlines how CIS are tobe employed to support command and controlthroughout the operation. The CIS concept in-cludes information such as—

● Numbers, types, classification levels, and loca-tions of C2 facilities.

● Numbers, types, classification levels, locations,and mode of operation of SCR nets.

● Numbers, types, classification levels, locations,and channelization of MCR circuits, includinglocation of transmission equipment.

● Numbers, types, classification levels, and loca-tions of wire circuits, including location of ter-minal equipment.

● Numbers, types, classification levels, and loca-tions of radio-wire integration facilities.

● Numbers, types, classification levels, and loca-tions of LANs.

● Numbers, types, classification levels, and loca-tions of switching centers, routers, and gate-ways.

● Numbers, types, classification levels, locations,and channelization of satellite links, includinglocation of terminal equipment.

● Numbers, types, classification levels, and loca-tions of terminal devices (computer, facsimile,etc.).

● Frequency requirements.● Call sign requirements.● Visual, sound, and messenger communications.● Communications control procedures, including

number, types, and location of communicationscontrol facilities.


The above list is not all-inclusive. It provides gen-eral guidance for preparing the CIS concept.Concept development should be closely coordi-nated with OPLAN/OPORD development. Theconcept is modified and refined as necessary andthen promulgated as Annex K to the OPLAN/OPORD.

6406. Paragraph 5 of the OPLAN/OPORD

The culmination of all operational planning is thepreparation and issuance of an OPLAN orOPORD. Information and instructions necessaryto employ CIS and effect command and controlare detailed in paragraph 5, Command and Signal,of the plan/order. As the member of the command-er’s general or executive staff with cognizance foremployment of CIS in support of command andcontrol, the G-6/S-6 is responsible for preparingparagraph 5. The G-6/S-6, with input from the G-3/S-3, will provide the draft paragraph 5 to thestaff section with overall staff cognizance for theplan (G-5 at MEF level and above and G-3/S-3 atdivision/wing/FSSG level and below) or the order(G-3/S-3). See MCWP 5-1 (draft) for discussionon development of OPLANs/OPORD.

The command and signal paragraph covers sever-al subjects: CIS establishment and maintenanceinstructions; CP location instructions; probable lo-cations of future CPs; and command relationships.CP locations and command relationships informa-tion is provided by the G-3/S-3. Sections of para-graph 5 pertaining to the employment of CIS mayconsist simply of the notation “no change” if theexisting CIS plan (CIS SOP and CEOI) is adequatefor the operation. It may contain only changes oradditions to an existing CIS plan/order if these arefew. In either case, the existing CIS plan must beclearly referenced and available to all. Paragraph 5will always include as subparagraphs commandrelationships, signal, and CPs.

a. Command RelationshipsThis subparagraph shows changes in or unusualcommand relationships. If there are none, theterm “omitted” is used. For example—

● Command Relationships. Control of RLT-7passes from 1st Marine Division to 2d MarineDivision on order of CG, I MEF, on or aboutD+2.

● Command Relationships. Omitted.

b. SignalThis subparagraph references Annex K, the CISAnnex and other publications that are in effect,such as the CIS plan. It also includes instructionsor restrictions pertaining to radio, visual, or soundsignals. For example—

● Reference (b) (CIS plan) and Annex K (CISAnnex).

● Radio silence until lifted by this HQ.● Signal for “assault waves have landed” will be

green star cluster.

c. Command PostsThis subparagraph states the locations of the issu-ing unit’s CP, subordinate unit CPs, and CP of thenext higher unit. If an Annex K is not prepared, theCP locations of adjacent and supported units mayalso be shown to facilitate communication by mes-senger. In an amphibious operation, this subpara-graph may also show CPs both afloat and ashore.This subparagraph should be considerably short-ened by referencing CP locations on the operationoverlay or, if one is prepared, in Annex K. Thissubparagraph may also direct subordinate units toreport the location and opening/closing times ofCPs. For example—

Command Posts

Afloat Ashore Unit (Ship Designation) (Grid Coordinates)

RLT 4 LHA 10268381BLT 1/4 LPD 10254387Co A LSD To be reportedCo B LPD 10264391Co C LHA 18466832

Report initial location ashore and changes in loca-tion by priority message.

6-16 _______________________________________________________________________________________________ MCWP 6-22

Additional subparagraphs may or may not be in-cluded. If used, they are lettered consecutivelyand may include the following information, as ap-propriate:

● Locations and times of opening/closing of C2facilities.

● Use of CIS and equipment.● Code words and names.● Liaison procedures.● Brevity List.

6407. Annex K (CIS Annex)

Annex K is an amplification of the instructionscontained in paragraph 5 of the OPLAN orOPORD. It is a tool to coordinate the establish-ment, operation, and maintenance of CIS to sup-port command and control. It delineates:

● The primary CIS missions to be accomplishedby the organization.

● The CIS missions to be accomplished at the or-ganizational HQ.

● The CIS missions assigned to subordinate unitsand (internal unit staff) principle staff officers

● Detailed technical plans for employment ofCIS.

● Administrative and logistics details related toCIS.

In formulating an OPLAN or OPORD, MEFs, di-visions, aircraft wings, FSSGs, and other majorHQs normally find it necessary to issue a volumi-nous and detailed CIS Annex. However, the an-nexes developed by subordinate organizations areusually less detailed. The maintenance of a stand-ing Annex K that can be tailored as necessary willgreatly reduce the preparation time to develop acomprehensive Annex K for a specific operation.Furthermore, the Annex K should reference (or

modify) existing CIS SOPs and CEOI and notpromulgate redundant information. Finally, byreference to the Annex K and/or the communica-tions plan of a senior HQ, a subordinate organiza-tion may be able to place all necessary CISinstructions in paragraph 5 of its OPLAN, obviat-ing the need to prepare a separate Annex K. How-ever, there are still instances when the plan ororder developed by a lower echelon should con-tain both paragraph 5 and a CIS Annex. For ex-ample, when a unit is involved in a highlycomplex operation requiring detailed CIS instruc-tions to ensure that no salient points are omittedor misunderstood, such detailed instructionsshould be contained in a CIS Annex.

Annexes to an OPLAN or OPORD are preparedto—

● Promote clarity, brevity, and simplicity withinthe body of an order.

● Amplify parts of an order with data that is tech-nical and/or limited in application to the com-mand as a whole.

● Furnish guidance for development of a plan ororder by a subordinate unit.

Annex K serves all three purposes. It amplifiesparagraph 5 with data that is technical and, for themost part, limited in applicability, and at the sametime eliminates the need for detailed CIS instruc-tions in the main body. The CIS Annex also pro-vides guidance to communications units for thedevelopment of their OPLANs and OPORDs. TheG-6/S-6 should begin preparation of Annex K onthe basis of the conclusions reached in the CIS es-timate developed in support of the preferred COAand in close coordination with the overall devel-opment of the OPLAN or OPORD. Detailed in-structions on the preparation of Annex K and arecommended format are contained in appendix Jof this manual.


Section V

Communications Control

Communications control is the method used bythe CISO to manage and provide positive controlover the communications network and the em-ployment of information systems. It involves or-ganizing CIS personnel to plan, direct, andcoordinate CIS support and controlling, engineer-ing, installing, operating, and maintaining theMAGTF communications network. Communica-tions control provides centralized control of limit-ed CIS resources while allowing decentralizedexecution for greater flexibility and responsive-ness. Communications control is the responsibili-ty of the commander. The commander delegatesthis responsibility to the CISO, the G-6/S-6. Theoverall MAGTF communications control effort isthe responsibility of the MAGTF G-6/S-6 officer.CISOs of subordinate organizations and units areresponsible for providing communications controlof the CIS resources of their respective organiza-tions and units in accordance with the overallMAGTF communications control effort.

At the MEF, the G-6 exercises communicationscontrol with the assistance of a staff that is aug-mented by the supporting communications battal-ion. An MCCC is organized under the direction ofthe G-6. The MCCC directs both internal and ex-ternal communications control functions. Externalcommunications control is coordinated with theJTF or CINC J-6 through the joint communica-tions control center (JCCC). The functions and re-sponsibilities of the JCCC are described inCJCSM 6231.01A, Joint Tactical Systems Man-agement, and CJCSM 6231.07A. The MCCC alsoprovides communications control support to theMarine component HQ.

Although communications control responsibili-ties, functions, and organization are more com-plex a t h igher eche lons of the MAGTF,communications control is exercised throughoutthe MAGTF down to battalion/squadron level.

Many of the communications control functionssupported by the communications battalions forthe MEF and the Marine component are per-formed by the MWCS, the division and FSSGcommunications companies, and, at lower eche-lons, communications platoons and detachments.Likewise, many of these functions associated withSCI communications are performed by the radiobattalions (for the MAGTF CE) or division andwing special security communications teams.

6501. Phases

Communications control begins with planning foran operation/exercise and continues throughoutthe deployment, installation, maintenance, and re-deployment phases.

a. PlanningThis phase consists of both operational and tech-nical planning. It culminates in the issue of a com-mand e lement OPORD and a suppor t ingcommunications unit OPORD. This phase is char-acterized by extensive coordination meetings be-tween the supporting communications unit(s) andsupported staff.

b. DeploymentDuring this phase, OPCON of the communica-tions units and/or detachments is transferred tothe supported CE. The CIS plan is refined throughcoordination among the supporting communica-tions unit(s) and the supported G-6/S-6 staffs andkey staff officers (e.g., the G-2/S-2 for intelli-gence CIS requirements, the fire support coordi-nator for fires CIS requirements, etc.). Limitedexecution is performed during this phase, includ-ing tracking message traffic and operating in-tran-sit radio circuits, as required.

6-18 _______________________________________________________________________________________________ MCWP 6-22

c. InstallationThis phase begins with the ship-to-shore move-ment and reoccurs with subsequent CP and orga-nizational displacements. Central coordination ofmultiple tasks is characteristic of this phase. Par-ticular attention is paid to maintaining communi-cations links external to the command element.SCR links are of highest priority.

d. MaintenanceThis phase occurs as terminal systems and net-work circuits become operational. It is highlight-ed by a shift from SCR to SBB-based systems,including installation and operation of LANs andsupport of voice traffic and router and switch-based message and data traffic over MCR links. Itis important to keep the SCR installation, opera-tion, and maintenance efforts separate from ef-forts to install backbone systems. Otherwise thecriticality of maintaining the SCR network can in-terfere with efforts to install the SBB. During thisphase, communications planning is continual tomodify and adapt communications networks asnecessary to support maneuver and displacement.

e. RedeploymentThis phase is highlighted by coordinated efforts todeactivate and pack up systems and equipmentand by a transition to a simpler, less capable com-munications network while maintaining the re-quired level of communications connectivity andinformation transfer capability. Communicationssupport must remain effective and responsivethroughout this phase.

6502. Responsibilities

Communications control is the method of orga-nizing communications personnel and facilities toprovide positive control of communications. It in-cludes planning, organizing, directing, coordinat-ing, controlling, and evaluating circuitry andequipment to ensure effective support of commu-nications requirements. As the level of commandincreases, so does the complexity of communica-tions control. Communications control responsi-bilities include—

● Planning, engineering, managing, coordinating,and controlling the MAGTF communicationsnetworks, both GENSER and SCI, includingSCR, local area, and SBB networks, as well asmaintaining connectivity to external networks.

● Identifying problems with the communicationsnetworks and coordinating and controlling ef-forts to restore, reconstruct, or reroute circuitsto resolve problems.

● Frequency planning, allocation, management,and deconfliction.

● Managing COMSEC assets and monitoringcompliance with COMSEC procedures.

● Managing, coordinating, and supervising tacti-cal information systems employment in concertwith principal staff officers representing func-tional area users.

6503. Functional Areas

Communications control is divided into the func-tional areas of system planning and engineering,SYSCON, and TECHCON.

System planning and engineering consists of de-termining the CIS requirements of the organiza-tion; designing the communications networks tosupport those requirements; and promulgatingCIS plans, orders, and directives.

SYSCON consists of supervising, coordinating,and controlling the overall, day-to-day operationof MAGTF communications networks.

TECHCON consists of centralized technical su-pervision of the installation, operation, and main-tenance of MAGTF communications networks.At the MEF and MSC level, a SYSCON staff andan OSCC support the SYSCON function, and aTECHCON operations staff and facility supportthe TECHCON function. Figure 6-1 is an over-view of MEF communications control. SectionsVI through VIII discuss these three functional ar-eas and the specific responsibilities and tasks as-sociated with performing them in support ofMAGTF tactical communications networks.


Figure 6-1. MEF Communications Control.

6-20 _______________________________________________________________________________________________ MCWP 6-22

Section VI

System Planning and Engineering

System planning and engineering involves thetechnical aspects of designing the MAGTF tacti-cal communications networks. These networksare planned, designed, and engineered to meet theoperational requirements set by the CISO. Thetype and number of circuits required, circuitroutes, frequency management, and other consid-erations are evaluated to establish requirementsfor both internal and external communications.System planning and engineering is performed byeach CISO in the MAGTF. The MEF G-6 is thesenior CISO and directs the overall system plan-ning and engineering of CIS networks. The com-munication battalion provides personnel tosupport system planning and engineering at theMEF level. The CISOs at lower echelons plancommunications support for their respective orga-nizations in accordance with the overall MEFcommunications plan.

6601. Functions

System planning and engineering is conducted atall echelons and includes the following functions:

● Prepare and disseminate general command pol-icies for the use of CIS within the command.

● Prepare and issue communications and infor-mation orders, records, and reports for the useof CIS and equipment within the commandsubordinate elements.

● Maintain continual contact with other staff ele-ments to ensure awareness of the operationalenvironment and evolving CIS requirementsand coordination with the CIS staffs of otherunits in the AO.

● Specification of system interfaces to other-Ser-vice and joint networks and the DISN.

● Planning and engineering of the overall config-uration of the command’s communications net-works, including the general locations ofmultichannel terminals, switches, gateways, ca-ble routes, and LANs and the use of host nation

facilities, radio net structure, relay/retransmis-sion sites, frequency requirements/allocations,and alternate means of communications.

● Analyzing the need for system reconfigurationand priority restructuring.

● Prepare and issue directives on implementingchanges in network configuration, connectivi-ty, or routing resulting from unit displacements,modifications of missions, unsatisfactory sys-tem performance, or other reasons.

● Continual review of system status and perfor-mance of communications equipment and per-sonnel.

● Planning system expansion, extension, com-pression, or reconfiguration.

● Prepare and update contingency plans.● Establishing network priorities.● Monitoring progress of work implementation

and quality assurance testing.● Coordinating frequency requests and develop-

ing a frequency management plan that includesfrequency allocation for both communicationsand noncommunications emitters such as radar.

● Maintenance of the system planning and engi-neering database.

● Prepare communications operations reports andmaintain historical data and files.

● Inform the commander and staff of the commu-nications situation.

● Prepare and plan COMSEC requirements (keys,codes, equipment, etc.) for the communicationsnetworks.

● Coordinate the development of automated toolsto enhance system planning and engineering ca-pabilities.


The MAGTF CISO is responsible for planning theSCR, local area, SBB, and special purpose systemnetworks. Subparagraphs a–c address specific


system planning and engineering responsibilitieswith respect to each of the communications net-works. Responsibilities for LANs are included un-der the SBB.

a. SCRPlanning SCR operations is the responsibility ofCISOs at all MAGTF levels. Each level can em-ploy a specific radio differently; however, interop-erability and interference require consideration offactors such as frequency selection, cryptographicequipment, communications protocols, and fre-quency separation. SCR nets used by the MAGTFare described in appendix D.

(1) VHF and UHF Frequency Hopping RadioNetworks. These networks include the SINC-GARS and HAVE QUICK radio systems. Both ofthese systems employ frequency hopping tech-niques. The set of frequencies, or hopset, to beused is planned and allocated by the MAGTF fre-quency manager. The MAGTF CISO assigns aunique net identifier to each net within theMAGTF. Current policy is for the net identifier tobe permanently assigned in the MAGTF masternet l ist . The MAGTF CISO identifies theMAGTF COMSEC keys for each net.

(2) Satellite Systems. The AN/PSC-5 is a sin-gle-channel UHF satellite radio system used forcommunication both within and external to theMAGTF. The area NCTAMS performs the linkperformance calculations, plans the uplink anddownlink frequencies, and provides the satellitelocation information for antenna pointing calcula-tions. When the radio is employed within theMAGTF, the MAGTF CISO identifies the COM-SEC key to be used. If the radio is employed tocommunicate outside the MAGTF (JTF, otherServices, and agencies), the higher HQ is respon-sible for security planning.

(3) HF Systems. Factors for HF communica-tions interface planning include terminal selec-tion, data rate selection, and operational mode.These are the responsibility of the MAGTF CISO.The MAGTF frequency manager is responsiblefor the propagation prediction. This includes cal-culating the maximum usable frequency, the low-

est usable frequency, and the frequency ofoptimum transmission for skywave propagation.The MAGTF frequency manager must then re-quest frequency assignments from the area fre-quency coordinator. The power requirement andrange for groundwave propagation are also re-sponsibilities of the frequency manager. Addi-tionally, the MAGTF CISO is responsible foridentifying required COMSEC keys.

b. Switched Backbone

(1) Switching Systems. The MAGTF CISO isresponsible for the detailed planning of theMAGTF SBB on the basis of user requirements.Each MSC CISO determines user requirementsfrom within the command and forwards this infor-mation to the MAGTF CISO. On the basis of thisinformation, the MAGTF CISO designs the net-work by establishing the trunking requirementsfrom the MAGTF CE to each MSC and betweenthe MSCs. From this design, each MSC CISOcompletes the detailed planning for the MSCswitching system, including trunking to subordi-nate units, trunking between subordinate units,and loop termination assignments. The MAGTFCISO prepares and distributes the network timingplan to the subordinate units, indicating the mas-ter timing source for the network. From this over-all plan, the unit CISO develops the internal sitetiming plans. The MAGTF CISO identifies theCOMSEC keys for the MAGTF switched net-work and identifies the COMSEC and alternateCOMSEC parent circuit switches.

(a) AN/TTC-42. The MEF employs AN/TTC-42circuit switches at the MEF CE and at each MSCHQ. The MAGTF CISO, after consulting with theGBNP, determines the numbering scheme to beused and develops the circuit switch numberingplan. The MAGTF CISO also assigns telephonenumbers and publishes the information systemsdirectory (app. E). The interswitch trunking as-signments and interoffice and interarea routingschemes are also the responsibility of theMAGTF CISO. Unit CISOs are responsible forconfiguring their switches to meet network designrequirements and for providing subscriber ser-vice. Unit CISOs are also responsible for report-ing their local plans and operational problems to

the MAGTF CISO. The MAGTF CISO deter-mines the priority for restoration of service.

(b) SB-3865. The SB-3865 circuit switch is usedthroughout the MAGTF, within each MSC, and atsubordinate units. It has operating characteristicssimilar to the AN/TTC-42. Therefore, the plan-ning requirements, with minor exceptions, are thesame as for the AN/TTC-42. The MAGTF CISOdetermines the priority for restoration of service.No planning is involved in selecting the numberformat because the SB-3865 accepts only the tac-tical numbering format (4/3).

(c) AN/MSC-63A. The AN/MSC-63A communica-tions central is employed as a message switch atthe MAGTF’s CE and major subordinate ele-ments. Connectivity for the AN/MSC-63A isplanned at two levels: the MAGTF CE level andthe MSC level. When employing the AN/MSC-63A, users must plan for communications connec-tivity because the AN/MSC-63A does not haveorganic communications equipment. If GENSERand/or SCI communities are to be served, the us-ers, inter-Service requirements, and security re-quirements must be identified.

(d) IP Routers. The Marine Corps employs IProuters to provide a data communications capabil-ity over the SBB and to interface with the SIPR-NET, NIPRNET, and JWICS. The MAGTF CISOalso has overall responsibility for network securi-ty on the SIPRNET. The MAGTF CISOcoordinates with MSC CISOs to ensure routerconnectivity throughout the MAGTF. Communi-cations and special communications units at theMAGTF CE and MSCs are responsible for the in-stallation, operation, and maintenance of theMAGTF secure and nonsecure data networks. Af-ter the networks are operational, the communica-tions unit monitors the network for activity,reliability, and security. Any detected security vi-olations are reported immediately to the unit CI-SO and the unit security manager. See appendixM for an example of an IP network diagram.

(2) Transmission Systems. The MAGTF CISOis responsible for planning the systems for trans-mission from the CE to the MSCs and between

MSCs. Circuits that run from each MSC HQ to itssubordinate units are the responsibility of theMSC CISO. If the MAGTF uses external meansto communicate outside of the MAGTF (JTF, oth-er Services, and agencies), the planning require-ments are coordinated with the higher HQ. Thefollowing transmission systems employment con-siderations provide some understanding of the CI-SO’s responsibilities.

(a) CX-4566, 26-Pair Cable. CX-4566 is used toextend the distance of subscriber terminal equip-ment from assemblages and switches and to per-form the function of a link concentrator when usedwith a J-1077 junction box.

(b) CX-11230, Coaxial Cable. The CX-11230 pro-vides the connectivity between switches, switchesand transmission systems, and data terminals.

(c) Fiber-Optic Cable System. The fiber-optic ca-ble system provides the connectivity from theswitch equipment to the transmission equipmentor between switches.

(d) AN/MRC-142. The AN/MRC-142 is a UHFtransmission system employed by each MSCwithin the MAGTF. This system provides criticalline-of-sight communications from the MAGTFCE to the HQs of subordinate commands, betweenMSC HQs, and within each MSC. The AN/MRC-142 baseband configuration is planned by theMAGTF CISO with input from the MSC CISO.Profiling and frequency planning between the CEand MSCs and between MSCs are accomplishedby the MAGTF CISO. Systems internal to anMSC are profiled by the MSC CISO. Site selec-tion and antenna elevation are the responsibility ofthe CISO employing the equipment and are basedon the profile of the system.

(e) AN/TRC-170. The AN/TRC-170 radio terminalset is used for line-of-sight or troposcatter com-munications by the MEF CE, each MSC withinthe MEF, and between elements of the ACE. TheMAGTF CISO, with input from the MSC CISOs,coordinates baseband configuration and profilingof the AN/TRC-170s between the CE and MSCsand between MSCs. The MAGTF CISO is


responsible for the frequency planning for theAN/TRC-170 systems.

(f) AN/TSC-85B and AN/TSC-93B. These t e rmi -nals provide entry into the GMF satellite systemand the DISN gateway. The MAGTF CISO plansfor employing the AN/TSC-85B satellite terminalat the CE. At the MSC locations, the MSC CISOplans for employing the AN/TSC-93B. The base-band configurations of the AN/TSC-85B and AN/TSC-93B are planned by the MAGTF CISO in co-ordination with the MSC CISOs. The MAGTF CI-SO submits a satellite access request to theRegional Space Support Center in CONUS, Eu-rope, or the Pacific for entry to the GMF satellitesystem. The Regional Space Support Center willproduce and provide a satellite engineering planthat includes the path, link analysis, uplink anddownlink frequencies, azimuth and elevation forthe antenna, and satellite assignments. The resultsare sent to the MAGTF CISO and then to theMSCs for employment of the GMF equipment.

(g) AN/TSC-96A. The AN/TSC-96A is a UHF sat-ellite communications system designed to workwith the Fleet Satellite Communications (FLT-SATCOM) network. It is employed down to theMSC level within the MEF. The baseband config-uration of the AN/TSC-96A is planned by CISOsof the MSC. Because this is a satellite system, thelink performance calculations, uplink and down-link frequencies, and the antenna pointing calcula-tions are planned by the NCTAMS servicing theAO. A communications information bulletin ispublished by the area NCTAMS. The communica-tions information bulletin provides the satellitecoverage of the area, base frequencies for reestab-lishment of links, and the types of informationtransmitted over each satellite channel. There is acommunications information bulletin publishedfor each operational area of the world. MEF andMSC CISOs should request copies of the commu-nications information bulletin before they deploy.The COMSEC keys to be used with this systemare planned by the parent agency of the system.

(h) AN/TSC-120. The AN/TSC-120 is employed atthe MEF and MSC HQs and provides internal andexternal communications. It can operate with bothU.S. and NATO conventional and special opera-

tions forces. The CISOs at each echelon plan forthe employment of the AN/TSC-120 and are re-sponsible for the proper employment of the sys-tem, including terminal equipment selection, datarate selection, and mode of operation. The CISOsalso submit communication guard shifts to ensuresystem entry into the Naval TelecommunicationsSystem and DISN.

When employing this system, the MAGTF CISOand frequency manager must confirm the avail-ability and allocation of multiple frequencies nec-essary for effect ive operat ion and circui treliability. Calculation of skywave propagationparameters is also required. In addition, power re-quirements and range for groundwave propagationemployment must be considered. The areaNCTAMS performs the link performance calcula-tions for the AN/PSC-5 employed with the TSC-120, plans the uplink and downlink frequencies,and provides the satellite location information forantenna pointing calculations. The MAGTF CISOis responsible for planning power requirements,range, and message throughput and wait times forVHF-AM meteor burst employment. When theAN/TSC-120 is employed within the MAGTF, theMAGTF CISO identifies the COMSEC key to beused. If it is employed to communicate outside theMAGTF (JTF, other Services, and agencies), thehigher HQ is responsible for security planning.

(3) Special-Purpose Systems

(a) PLRS. The PLRS is a ground-based radio-navi-gation system. Employment of PLRS is the jointresponsibility of the GCE operations and CIS of-ficers and the MAGTF CISO. The GCE opera-tions officer is responsible for operationalplanning, including basic user unit equipment dis-tribution, group access, message set access, andnavigational aids (zone, corridor, and line bound-aries and predetermined items). The MAGTF CI-SO is responsible for planning the initial locationsof the PLRS master station and alternate masterstation. The GCE operations officer determinesthe organizations that will provide the necessary6–10 reference units and coordinates with the CI-SO for their initial locations. The MAGTF CISOis responsible for planning reference units andcoordinates with the GCE CISO for their initial

6-24 _______________________________________________________________________________________________ MCWP 6-22

locations. The MAGTF CISO is responsible forplanning reference and relay unit locations to en-sure complete PLRS coverage. The MAGTF fre-quency manager provides the net frequencyallocation and a single-channel VHF frequencyfor the PLRS engineering net. In the event thatmore than one PLRS network is operated, theMAGTF frequency manager plans for additionalfrequency allocations for the additional networks.

(b) EPLRS. EPLRS employment requires detailedplanning so that it can support the operationalscheme of maneuver. All predetermined EPLRSdata communications needlines must be plannedand established prior to mission execution. Con-tinuous coordination between the operations offi-cer and communication-electronics officer of op-erational headquarters throughout the MAGTF isnecessary for effective employment of EPLRS.EPLRS network planning with consideration forTDN, DACT, TCO, AFATDS, and SINCGARS,and the cryptological key management plan arekey mission planning factors. Additionally, forjoint operations, coordination with Army EPLRSplanners, Air Force Situation Awareness DataLink (SADL) planners, and Navy AN/KSQ-1planners may be necessary.

During operations ashore, EPLRS will serve asthe primary data radio set for TDN connectivitybelow the regimental level, as well as providingdata communications requirements for task orga-nizations below the battalion level. The networkcan be generated and established by an NCS-E(D)or a PC, dependent upon the particular mission.(The PC-based capability, currently under devel-opment, will be used for rapid communicationsnetwork initialization, and generation of initial-ization and cryptographic keys to support garrisonand field exercises, EPLRS radio set training, andhost system training. This precludes deploymentof an NCS-E(D) to support limited training envi-ronments and small operational deploymentswhich do not require an automated PLI capability,but do require EPLRS data communications capa-bilities.)

If EPLRS and PLRS are also employed for PLI,the NCS-E(D) is required and will be located inthe vicinity of the senior headquarters of the oper-

ating force. The tactical situation will determineits exact location. However, in making this deter-mination, the commander should consider thescheme of maneuver, security requirements, EPL-RS network requirements, and electromagnetic in-terference. The reference community can be basedon a mix of fixed reference sites and radio setswith Global Positioning System Interface Units(GPSIUs). The GPSIU allows the employment ofa mobile, more versatile reference community,vice fixed reference units which must be surveyed,by connecting an organic AN/PSN-11 PLGR to ei-ther an EPLRS radio set or PLRS BUU. A singleEPLRS/PLRS community will be deployed withone NCS-E(D) and up to 460 active radio sets.

During ship-to-shore movements, the MarineCorps EPLRS network can be integrated with theU.S. Navy’s Amphibious Assault Direction Sys-tem (AN/KSQ-1). (Net Control Stations are beinginstalled on all LHAs and LHDs as part of this sys-tem.) The AN/KSQ-1 is designed to monitor andcontrol naval surface landing craft—LCUs andLCACs—as well as “inject” PLI generated bythese craft into the Joint Maritime Command In-formation System (JMCIS) Track Database Man-age r (TDBM) fo r bu i l d ing t he commonoperational picture. Airborne or terrestrial plat-forms equipped with EPLRS can provide “over-the-horizon” communications, dependent uponthe mission and platform availability. In order tocapitalize on EPLRS communication and PLI ca-pabilities, extensive coordination and planningmust be done in order to establish and manage thedata needlines for Marine and Navy use.

(c) JTIDS. JTIDS is an airspace C2 support sys-tem. The TAOC and the TACC are the onlyMarine Corps C2 facilities to be equipped withJTIDS. The ACE CISO is responsible for plan-ning implementation of the JTIDS terminals lo-cated within the ACE. The ACE CISO requeststhe required frequencies and time slots from theMAGTF CISO, who forwards the request to theJTF J-6. The MAGTF CISO is also responsiblefor identifying COMSEC key requirements. TheJTF J-6 assigns the frequencies to be included inthe frequency allocation and the time slots for op-eration in the network. The ACE CISO coordi-nates with the ACE operat ions officer to


determine the locations of the JTIDS modules as-sociated with the TAOC and TACC.

(d) GPS. The GPS is a passive system, and thereare no communications networks for the MAGTFCISO to coordinate. However, the MAGTF CISOmust ensure that satellite coverage is available inthe AO. This information is found in the satellitealmanac published by the U.S. Air Force SpaceCommand. The data in the almanac includes thenumber of satellites covering the AO, the actualnumber of satellites operating, and the times thesatellites are overhead. The GPS satellite almanacdata is also transmitted automatically to GPS re-ceivers from the GPS satellite constellation.

(e) Trojan Spirit II. Each day, a portion of the radioelectronic spectrum is captured by selected SIG-INT collection facilities overseas and relayed viathe Trojan Spirit intelligence support system toCONUS-based analysts for further exploitation.Trojan Spirit (fig. 6-2) is a unique transmission ca-pability designed to forward tactical SIGINT toCONUS-based elements for analysis. Operatingat the SCI/TK level, the Trojan Spirit system isfielded and operational in the MEFs. Operators atthe Intelligence Company of the MEF, in conjunc-

tion with analysts from Radio Battalion, can re-ceive live SIGINT information being collected inthe forward area. This capability enables analyststo train and maintain their readiness in collectionmanagement, technical control, and system super-vision, as well as SIGINT production and database maintenance.

The executive authority for Trojan Spirit is theU.S. Army Intelligence and Security Command(INSCOM) at Fort Belvoir, VA; management isprovided by the U.S. Army Technical Control andAnalysis Element (TCAE) at Fort Meade, MD.Use and management of the Trojan Spirit systemis exercised at Fort McPherson, GA. Trojan Spiritservices are extended to the I, II, and III MEFs.

In addition to supporting the counter-drug mis-sion, language training, an essential element ofthe intelligence training program, is a secondarypurpose of the system. The command provides se-cure facilities and communications with intelli-gence staff oversight and INSCOM technicalcontrol for the training of SIGINT skills, tasks,and processing of assigned units under TCAE op-erational control.

Figure 6-2. Trojan Spirit.

6-26 _______________________________________________________________________________________________ MCWP 6-22

The Trojan Spirit system consists of four major el-ements: the remote collection equipment in theforward area, transmission systems that carry theactual transmission to CONUS, central switchingfacilities at Fort Belvoir that route traffic to specif-ic processing sites, and the garrison central operat-ing facility.

A basic Trojan Spirit system consists of four col-lection positions, four listening posts, a system su-pervisor’s console, and system-associatedcommunications equipment. An upgraded capa-bility includes enhanced signal distribution inter-connecting control and digital data switching. Thetactical field monitor sub-component of the TrojanSpirit system is designated the AN/TSQ-144(V)2.This equipment can remotely control receivers atunmanned collection sites. From the collectionsite, secure communications links are establishedusing tactical military equipment such as SHF/GMF terminals employing the DSCS, most often acombination of U.S. military-owned/-leased com-mercial connectivity using satellite and terrestrialsystems.

Although Trojan Spirit is oriented toward CONUSgarrison operations, the system has tactical appli-cations, as was proven during Operations DesertShield/Desert Storm. The Army realized that ithad a robust wide-band communications asset thatcould be used to support tactical operations. Dur-ing Operation Restore Hope, using Trojan Spirit tosupport split-based operations reduced the numberof intelligence personnel required to deploy.

Future TS IIs will provide MEFs with both C- andKu-band satellite communications; planned field-ing will remain at two systems per MEF. The HM-MWVs are currently configured with a primaryTrojan shelter on one vehicle and a spare equip-ment shelter on the other. Both vehicles have un-der-the-hood and tunnel-mounted electrical powergenerating capabilities. The space between theHMMWV cab and the shelter contains the tunnel-mounted generator. The system also has a mobileantenna platform trailer.

6603. Automated Tools

Several automated planning and engineering toolsare available to support system planning and engi-neering.

a. SPEEDSPEED is a team-transportable, fully integrated,microcomputer-based system that supportsMAGTF tactical communications planning to theregimental/group level. SPEED is used in con-junction with a random data generator and a datatransfer device. SPEED should have other pro-grams which provide the following capabilities:

● Point-to-point analysis.● High-frequency analysis.● Guard chart application.● Signal/noise and signal/interference analysis.● Area coverage analysis.● Topographic database.● Database of basic equipment characteristics.● RBECS software programs for CEOI/signal

operating instructions generation.● Tactical Network Analysis and Planning Sys-

tem Plus (TNAPS+) software.● Switched Network Automated Planner soft-

ware.

b. Revised Battlefield Electronic CEOI SystemRBECS application software was designed to pro-vide the user with an enhanced CEOI and frequen-cy hopping data generation capability. RBECS isone of the applications resident on SPEED termi-nals. There are two application modules withinRBECS: Signal operating instructions/CEOI andRevised SINCGARS Integrated CommunicationsSecurity Module, Nonintegrated Communica-tions Security Module Support Software (RSI-NISS). Signal operating instructions/CEOIprovide the user with the capability to build, gen-erate, edit, and print CEOI locally for training oroperations. CEOI generation requires an AN/CSZ-9 random data generator and is conducted atthe MEF, MSC, and MEU CE levels.


c. Revised SINCGARS Integrated Communications Security Module, Nonintegrated CommunicationsSecurity Module Support SoftwareThis application of the RBECS was designed togenerate, store, edit, and transfer SINCGARS fre-quency hopping data. RSINISS can download fre-quency hopping data from a PC into a DTD byusing RS-232 cable or to a floppy disk for dissem-ination to subordinate, adjacent, or supportingunits. RSINISS requires a random data generatorto generate unique transmission security keys.Transmission security keys are generated at theMEF, MSC, and MEU CE levels.

d. AN/CSZ-9 Random Data GeneratorThe random data generator performs two basicfunctions. It randomizes the allocated frequenciesinto daily changing frequencies and assigns dailychanging call signs for the CEOI application. Itgenerates a unique pseudo random transmissionsecurity key for RSINISS use when creating load-sets.

e. AN/CYZ-10 DTDThe DTD is a weather-resistant, electronic datastorage and transfer device procured by the Na-tional Security Agency loaded with RBECS DTDSoftware. The DTD is cargo-pocket size, weighs1.5 pounds, and requires three 3-volt batteries orone 9-volt battery. DTD’s primary function is toserve as a common fill device to load COMSECkeys into any Marine Corps cryptographic equip-ment. It is the planned replacement for the TSEC/KYK-13 and the TSEC/KYX-15. The DTD canreceive, store, and transfer frequency hopping da-ta between DTDs or PCs. The DTD can also re-ceive, store, display, and edit CEOI informationand transfer one time period of CEOI informationover the air by using a SINCGARS radio. TheDTD is also referred to as the Automated NetControl Device (ANCD) in many U.S. Armytechnical and operation manuals.

f. Revised Battlefield Electronic CEOI System DTD SoftwareThis is the software application used by the Armyand Marine Corps in the DTD. RBECS DTD

Software has two application modules: signal op-erating instructions and radio. Signal operating in-structions can receive, store, find, display, andtransfer CEOI data. Radio can receive, store, edit,and transfer frequency hopping data. Radio canalso generate, receive, store, and transfer COM-SEC keys.

g. ARC-210 Fill Program The ARC-210 Fill Program is a software applica-tion located on the SPEED platform. The ARC-210 Fill Program is used to enter and organize thevarious types of data required to fill an AN/ARC-210 radio: single-channel frequencies and relateddata and HAVE QUICK and SINCGARS fre-quency hopping data. This data allows the radio tooperate in either single-frequency or frequencyhopping modes with compatible radios.

h. Consolidated SCR EP PackageThe Consolidated SCR EP Package is a softwareapplication that may be loaded into the DTD. TheConsolidated SCR EP Package allows the DTD toreceive frequency hopping data from RSINISSand COMSEC keys from common fill devices.The Consolidated SCR EP Package applicationconsists of two functions: detailed managementand quick fill. The detailed management functionoffers transmit, receive, database, and setup func-tions. The quick fill function transfers frequencyhopping data from the DTD to a SINCGARS orAN/ARC-210.

i. TNAPSTNAPS is a computer-based desktop system plan-ning and SYSCON tool that assists the planner inbuilding an exercise or operation database and inproducing a series of output reports describing theresulting networks and equipment configurations.The system controller can use this database withprogram support to monitor and manage in-placecommunications. TNAPS allows tactical commu-nications planning and control at two levels: thenetwork level and nodal/equipment level. Net-work planners and controllers are responsible forplanning and managing the overall network. Nod-al planners and controllers plan and manage acomplete database for equipment within the node

6-28 _______________________________________________________________________________________________ MCWP 6-22

and generate all necessary worksheets and crewassignment sheets. Some of the functions ofTNAPS are—

● Exercise of database control.● Site configuration and inventory control.● Circuit/message switch graphics and network

development.● Transmission graphics and network develop-

ment.● COMSEC database control.● Report generation.

● Subscriber database control.● SYSCON.

j. Switched Network AutomatedPlannerThe Switched Network Automated Planner isused to plan and engineer switched communica-tions networks. Through a series of user selec-tions and inputs and software routines, theSwitched Network Automated Planner assists inplanning and engineering a network and providesphysical and database configuration data forULCS equipment.


Section VII

SYSCON

The primary purpose of SYSCON is to ensure op-timum use of all available circuits to meet the re-quirements of the commander. SYSCON is theresponsibility of the supporting communicationsunit. The SYSCON function includes two types ofactivity: staff direction of MAGTF communica-tions network configurations and day-to-day man-agement of the operating communicationsnetworks. These functions are accomplished bythe SYSCON staff and the OSCC watchstanders,respectively. The SYSCON staff supervises OS-CC activities and compiles statistics and reportsfor use in long-range planning. The OSCC mean-while directs day-to-day operations of the commu-nica t ions ne tworks wi th in the MEF. Thecommunications battalion provides the SYSCONstaff and mans the MEF OSCC. At the MSC level,the supporting communications unit(s) provide thesame functions. At lower echelons, SYSCONfunctions are less complex and are performed bypersonnel of the communications unit without es-tablishment of an OSCC.

6701. Functions

The SYSCON functions performed by the SY-SCON staff and the OSCC are—

● Prepare and issue detailed directives and in-structions to subordinate communications unitsfor implementaion of CIS plans and supervis-ing the execution of the plans.

● Monitor system performance and coordinateactions required for restoration of system out-ages, including coordinatoin with senior, sub-ordinate, and adjacent OSCCs.

● Generate and disseminate frequency assign-ments and monitor and control frequency usage.

● Maintain the transmission quality on all trans-mission links.

● Adjust communications resources to compen-sate for disruptions or destruction of the com-munications system by the enemy.

● Achieve speed and grade-of-service goals in thenetwork under normal and stress conditions.

● Determine satellite/transponder usage and mon-itor the channels for occupancy to determinewhether a reallocation of channels is necessary.

● Provide circuit switch, message switch, androuter programming needed to establish andupdate subscribers and route traffic.

● Develop, monitor, and load key variables intoencryption devices.

● Collect and analyze traffic data, service com-plaints, and outage reports to identify and correctsystem inadequacies, procedural deficiencies,and other problems and provide the analyses tosystem planning and engineering. Make recom-mendations to system planning and engineeringfor corrective actions when the resources avail-able to SYSCON are insufficient to provide sat-isfactory communications service.

● Prepare and distribute information essential tousing and operating the system, such as tele-phone directories, network addresses, and callsigns.

● Maintain system records and historical data andsubmit reports as required.

● Direct and receive circuit information from thelocal TECHCON operations center.

6702. Staff Responsibilities

Communications, as a function of the command,are the ultimate responsibility of the commander.The CISO and the supporting communicationsunit operations officer act as agents of the com-mander. For example, the MEF communicationsbattalion operations officer may provide directionto the division communications company opera-tions officer. However, the division communica-tions company operations officer is ultimatelyresponsible to the division commander and servesas the agent of the division commander to express

6-30 _______________________________________________________________________________________________ MCWP 6-22

the division communications requirements to theMEF.

At each echelon, the communications unit opera-tions officer has been delegated the managementand control responsibility necessary to direct theoperation of the communications systems and net-works. At the MAGTF CE, the communicationsunit operations officer is responsible for the com-munications links connecting the CE to the subor-dinate HQ. Directives from the MAGTF CISO aredistributed down to each subordinate communica-tions unit operations officer. The MAGTF com-munications unit operations officer periodicallymonitors the status of each link of the MAGTFcommunications networks, including equipmentstatus. Reports from subordinate communicationsunit operations officers are consolidated by theMAGTF communications unit operations officer.Each subordinate communications unit operationsofficer monitors the equipment and network statuswithin the command and reports the status to theMAGTF communications unit operations officer.For systems between adjacent subordinate HQs(e.g., GCE to ACE), the MAGTF CISO designatesone of the subordinate communications unit oper-ations officers to control the link.

a. SCREach subordinate communications unit operationsofficer or commander monitors the status of SCRnets and provides periodic status reports to thenext higher command communications unit oper-ations officer. If an MSC communications unitoperations officer is notified of a COMSEC orTRANSEC compromise, the MAGTF CISO is in-formed. Each subordinate communications unitoperations officer informs the next higher com-munications unit operations officer of any inter-ference problems that require addi t ionalfrequency planning for HF, VHF, UHF, andUHF-SATCOM nets.

b. Switched BackboneEach subordinate communications unit operationsofficer is responsible for directing the implemen-tation of the SBB network according to plans de-veloped or approved by the MAGTF CISO. Thesubordinate communications unit operations of-

ficers coordinate with adjacent units to resolveproblems. Subordinate communications unit oper-ations officers are responsible for providing peri-odic status reports to the next higher echelon. TheMAGTF CISO is kept informed of the MAGTFcommunications network status by the MAGTFcommunications unit operations officer. Subordi-nate communications unit operations officers areresponsible for reporting problems that cannot besolved at their level to the next higher communi-cations unit operations officer.

c. Special Purpose SystemsDirection, management, and control responsibili-ties for special purpose systems consist primarilyof reporting equipment status and outages. Statusreporting for these systems is the same as de-scribed above for the switched backbone. Outagereports are sent to the external supporting organi-zations for these networks through the MAGTFCISO. Planning to circumvent outages is coordi-nated with the communications unit operationsofficer. The communications unit operations of-ficer coordinates with the appropriate network or-ganizations for access according to local SOPguidelines.

The MAGTF communications unit operations of-ficer is responsible for directing, managing, andcontroling the PLRS (EPLRS). The MAGTFcommunications unit operations officer directs theactivities of the PLRS (EPLRS) master station op-erators in implementing OPLANs and planchanges. The PLRS (EPLRS) master station oper-ators are responsible for the PLRS TECHCONfunctions. The MAGTF communications unit op-erations officer monitors the PLRS (EPLRS) net-work to check for full area coverage. If the areacoverage is insufficient, the MAGTF communica-tions unit operations officer notifies the MAGTFCISO. PLRS (EPLRS) employment must be inte-grated into the commander’s scheme of maneuverand support execution. This means that the net-work must be flexible and able to adapt to changeas it occurs during all phases of planning and op-erations.

The MWCS operations officer is responsible forthe SYSCON of the JTIDS. The MWCS


operations officer receives system status reportsfrom the wing OSCC and reports system failures,frequency interference problems, and ground sta-tion movements to the wing CISO.

The MAGTF communications unit operations of-ficer needs to ensure that the appropriate COM-SEC variables are distributed so that encryptedpositioning signals can be properly received. TheMAGTF CISO monitors almanac conditions, co-ordinates appropriate adjustments, and forwardsinformation messages to GPS users. System out-ages are reported to U.S. Air Force Space Com-mand.

6703. OSCC Responsibilities

The OSCC directs the day-to-day operation ofcommunications networks.

a. SCRThe OSCC directs the implementation of the SCRnets, including coordination with the unit opera-tions section for the operation of the net controlstation. The OSCC also maintains the COMSECand TRANSEC keys, the word of the day, and thenet frequency allocation for each net. The TECH-CON of the tactical radio nets, including trouble-shooting, is directed by the OSCC. To combatinterference or to limit the amount of traffic on anet, the OSCC and the operations officer may de-cide in favor of time sharing of nets or directednet operations. The OSCC periodically reports thetactical radio net status to the communicationsunit operations officer.

b. Switched BackboneThe OSCC maintains the equipment status of eachsystem. The OSCC also monitors the circuitswitched network statistics to insure that systemavailability, call blocking, and the switch trafficload are within acceptable tolerances. The OSCCdirects the installation of the switch network to in-clude fault isolation, restoration, and reconfigura-t ion , as necessa ry . The OSCC ins t i tu tespreauthorized changes in the switched networksuch as routing table changes, zone restrictions, al-ternate routing, database changes, or traffic load

control procedures. The OSCC reports problemsthat cannot be resolved at that level to the respec-tive communications unit operations officer. TheOSCC is also responsible for directing the loadingof the proper COMSEC keys into the equipmentand ensuring proper operation. The OSCC com-piles the statistics of the switched network and re-ports them to the communications unit operationsofficer.

c. Special Purpose SystemsThe primary functions of each OSCC are to directthe installation of the systems, maintain the equip-ment status, and report equipment outages to thecommunications unit operations officer. Securitymanagement is also the responsibility of the OS-CC. The OSCC provides COMSEC keys and en-sures proper operation.

The majority of PLRS (EPLRS) OSCC duties,such as monitoring reference units and coordinat-ing with multiple network PLRS (EPLRS) masterstation operators, must be done at the master sta-tion location. The PLRS (EPLRS) master stationoperator is responsible for fulfilling the duties ofthe OSCC. The master station operators are re-sponsible for reporting the status of the networkto the MAGTF communications unit operationsofficer. They also provide the COMSEC keys tothe necessary personnel. The master station oper-ators continually monitor the units that are activeusers of the PLRS (EPLRS). Units moving out ofthe area of coverage are reported to the communi-cations unit operations officer for action. Masterstation operators are also responsible for verifyingthe map, control, and coordination data that ap-pears on the monitors.

The ACE OSCC directs the JTIDS installation,operation, and maintenance; provides the COM-SEC key to the JTIDS operators; and coordinatesthe movement of the JTIDS ground stations. TheOSCC provides system status, frequency interfer-ence, and ground station movement reports to thecommunications unit operations officer.

The MEF OSCC distributes COMSEC keys andinformation messages to GPS users.

6-32 _______________________________________________________________________________________________ MCWP 6-22

Section VIII

TECHCON

TECHCON is the means of exercising centralizedtechnical supervision over the installation, opera-tion, and maintenance of the circuits and systemsemployed by the MAGTF. The installation of eachsystem is controlled by a TECHCON facility. Thisincludes both the systems that interface directlywith the facility and those that do not. The OSCCwatch officer directs the activities of the TECH-CON operations staff. The TECHCON operationsstaff supervises the installation, operation, andmaintenance activities of the direct support, gener-al support, and service companies and/or their de-tachments. The capabilities of these units areorganized around platoons and sections into cen-ters such as radio, wire, multichannel, and datacommunications central; the TECHCON facility;the communications center; and the maintenancefacilities. TECHCON operations staff overseesand directs the activities of all these centers.

6801. Functions

TECHCON functions are—

● Exercise technical coordination between ele-ments of the MAGTF tactical communicationsnetwork.

● Exercise technical supervision over subordinatetechnical control facilities

● Restore disrupted service.● Perform quality checks and exercise technical

direction, coordination, and supervision on sys-tem testing.

● Coordinate system activation, deactivation,and/or reconfiguration.

● Report system and circuit status to the appro-priate control facility.

● Record status of transmission links, trunks,channels, and circuits as required by local SOP.


The current generation of digital switching andtransmission equipment has been designed withinherent TECHCON capability. Because many ofthe component systems that make up the commu-nications networks are physically isolated fromone another, responsibility for the TECHCON ofthe communications networks involves the com-bined and coordinated effort of each operator, su-pervisor, and maintainer in each part of thesystem.

a. SCRThe responsibility for TECHCON of MAGTFtactical radio nets lies with the net control stationequipment operators and the local communica-tions organization. For frequency hopping radionets to operate properly, each radio in the netmust maintain an accurate time-of-day clock. Thenet control station maintains time of day and pro-vides it to the users of the net. The equipment op-e ra to r s a re r e spons ib le fo r ma in ta in ingsynchronization within the network and correct-ing as necessary. Troubleshooting tactical radionets is the responsibility of the local communica-tions organization. The local communications or-ganization also determines the separation andplacement of antennas to minimize electromag-netic interference. The OSCCs direct equipmentoperators on the power setting that will allowthem to operate in the net without using an excessamount of power.

b. Switched BackboneThe TECHCON for the SBB is accomplished bythe operators and supervisors of the switch andtransmission equipment, as well as by dedicatedTECHCON personnel. The switch and transmis-sion equipment operators are responsible forinstalling the individual circuits in the switchednetwork and for monitoring the equipment


alarms. It is also the responsibility of the equip-ment operators to monitor the synchronization ofthe switched network. When circuit or systemoutages occur, the operators are responsible fornotifying the OSCC and implementing proce-dures for fault isolation and restoring the lost ser-vice. If necessary, they reconfigure the circuits orsystems under the direction of the OSCC. Equip-ment and circuit outages are reported to OSCC bythe operators. Equipment operators are also re-sponsible for monitoring and adjusting circuitsthat require alignment, such as analog voice anddata circuits. The operators are also responsiblefor monitoring the status of each circuit and sys-tem and periodically reporting this status to theOSCC. In addition, there may be dedicated cir-cuits installed that use the transmission systemsbut do not access the switched network. TheTECHCON for these circuits may be accom-plished by using portable TECHCON facilitiesthat do not interface with other systems.

The current TECHCON facility is the AN/TSQ-84, an analog facility with limited capabilities.The digital technical control (DTC) is replacingthe AN/TSQ-84. The DTC provides the FMF witha deployable, digital technical control capabilityto replace the AN/TSQ-84. The DTC facilitatesthe installation, operation, restoration, and man-agement of individual circuits and digital linksconsisting of many multiplexed circuits. It pro-vides the primary interface between subscribersystems/networks within a local area and longhaul multi-channel transmission systems to trans-port voice, message, data, and imagery traffic. Itcan add, drop, and insert digital circuits into mul-tiplexed groups; provide a source of stable timing

to connected equipment; condition circuits; andperform analog/digital, 2-wire/4-wire, and signal-ing conversions. It contains the monitoring, test-ing, and patching equipment required by technicalcontrollers to troubleshoot and restore faulty cir-cuits and links. Equipment is contained in an S-280 shelter and will be transported by a dedicated5-ton truck. A total of 31 systems are planned forfielding to the FMF.

c. Special Purpose SystemsBecause the special purpose systems are separatefrom the other systems within the MAGTF, theTECHCON is accomplished by the equipment op-erators. The operators monitor the status of thetransmission and subscriber equipment. Reportsof system status and outages are sent to the OSCC.

The PLRS (EPLRS) master station operators areresponsible for the TECHCON duties. These re-sponsibilities have been discussed in the day-to-day OSCC responsibilities.

The JTIDS operators at the TAOC and TACCperform the TECHCON functions for the JTIDSsystem. The JTIDS operators install and restorethe JTIDS system under the direction of the ACEOSCC and report equipment outages and periodicsystem status to the ACE OSCC.

The MAGTF G-6 staff monitors almanac condi-tions and coordinates appropriate adjustments andinformation messages to GPS users. System out-ages are reported to U.S. Air Force Space Com-mand.

(reverse blank)

Chapter 7

Information Systems Security

MAGTF command and control relies on the confi-dentiality, availability, and integrity of tacticalcommunications networks and information sys-tems. Protecting these systems from exploitation,disruption, or destruction is of highest priority.

The threat to MAGTF CIS comes from a varietyof sources and continues to evolve. This threatranges from conventional EW/SIGINT tech-niques to newer forms such as computer intrusionsby hackers; drug traffickers; foreign intelligenceagencies; disaffected, disgruntled, or disloyal per-sonnel; and, potentially, battlefield adversaries.Intruders have repeatedly demonstrated their abili-ty to penetrate military information systems. Withthe increasing interconnection of information sys-tems, such attacks threaten the entire DII as wellas the tactical communications networks and in-formation systems that interface with and use thatinfrastructure.

INFOSEC is the protection of information sys-tems against unauthorized access to or modifica-t ion of informat ion, whether in s torage ,processing, or transit, and against denial of ser-vice to authorized users or the provision of ser-

vice to unauthorized users, including thosemeasures necessary to detect, document, andcounter such threats.

As with other forms of security, the first step inproviding effective INFOSEC is understandingthe threat. This includes identifying threat objec-tives, capabilities, and techniques as well asfriendly vulnerabilities.

The threat’s overall capability to conduct C2 war-fare on the battlefield and information warfare inthe strategic arena affects the way the MAGTFmust defend its information systems.

At the strategic level, DISA is responding to thethreat with a defensive information warfare strate-gy based on protecting the infrastructure and data,detecting attacks, reacting promptly to attacks,and maintaining service. On the battlefield, theMAGTF is responding to the threat through asimilar C2 protection strategy.

This chapter focuses on two key security disci-plines: COMSEC and computer security (COM-PUSEC).

Section I

Communications Security

COMSEC is the protection resulting from allmeasures designed to deny unauthorized personsinformation of value that might be derived fromthe possession and study of telecommunicationsor to mislead unauthorized persons in their inter-pretation of the results of such possession andstudy. COMSEC includes physical, cryptograph-ic, transmission, and emission security. The goalof COMSEC is to protect friendly communica-

tions from enemy exploitation while ensuring un-impeded use of the electromagnetic spectrum.The organization must be able to employ commu-nications equipment effectively in the face of ene-my efforts. COMSEC is an integral part ofelectronic protection—the element of EW that fo-cuses on protection of our capabilities. COMSECrequirements must be integrated into communica-tions systems planning and must focus on provid-

7-2 ________________________________________________________________________________________________ MCWP 6-22

ing secure communications without impairingreliability or responsiveness. Modern communi-cations equipment includes features such as inte-grated encryption capability and frequencyhopping capability, which contribute to communi-cations protection. However, the security of ourcommunications depends on the proper operationof communications equipment and adherence toproper procedures.


COMSEC is a command responsibility. It is alsothe responsibility of each individual user of com-munications. The G-6/S-6 is responsible to thecommander for the overall planning, supervision,and coordination of COMSEC matters, includingthe administrative, day-to-day management ofCOMSEC material. Specific staff responsibilitiesinclude:

a. G-6/S-6● Incorporating COMSEC requirements into the

communications plan.● Supervising communications to ensure proper

equipment operation and use of COMSEC pro-cedures.

● Training communications personnel in COM-SEC and electronic protection techniques.

● Promoting awareness of the enemy EW threatamong all members of the command.

● Advising and assisting the unit security manag-er, G-2/S-2, and G-3/S-3 in matters regardingCIS and electronic security and protection.

● Preparing an emission control (EMCON) planto include employment of alternate communi-cations means.

● Advising and assisting the G-3/S-3 in mattersregarding the command’s operations securityand deception plan.

● Instructing all users on proper operation ofcommunications systems and equipment andproper communications procedures.

● Coordinating with the G-2/S-2 and G-3/S-3 forconducting COMSEC monitoring and analysisoperations.

● Supervising the COMSEC Material System(CMS) custodian in the execution of his dutiesand responsibilities for control and account-ability over classified CMS material and equip-ment, including distribution and destruction ofCOMSEC material in accordance with currentdirectives.

● Ordering COMSEC material and equipment foroperations and exercises.

● Developing, in coordination with the unit secu-rity manager, emergency destruction plans forCOMSEC materials and equipment.

b. G-2/S-2● Advising and assisting the communications in-

formation systems officer on electronic protec-tion techniques based on analysis of enemySIGINT and EW capabilities and other threatsto unit CIS and operations.

c. G-3/S-3● Integrating communications information sys-

tems protection, including COMSEC and elec-tronic protection, into the concept of operationin accordance with the commander’s guidance.

● Planning and supervising the physical protec-tion of essential communications nodes.

● Planning and supervising the overall EW effortin coordination with the G-2/S-2 and the G-6/S-6.

d. MEF COMSEC Management Office● Providing and sourcing MEF units with mis-

sion essential contingency COMSEC material.● Establishing CMS policy within the MEF.● Deploying as a MEF COMSEC Management

Office (MCMO) in support of the MEF or de-ploys and/or supports a Joint COMSEC Man-agement Office for a Joint Headquarters.

e. Command Security Manager● Serving as the commanding officer’s advisor

and direct representative in matters pertainingto the security of classified information andpersonnel security.


● Developing written command information andpersonnel security procedures, including anemergency plan which integrates emergencydestruction bills where required.

● Ensuring that threats to security, compromisesand other security violations are reported, re-corded and, when necessary, investigated vig-orously. Ensures incidents falling under theinvestigative jurisdiction of the NCIS are im-mediately referred to the nearest NCIS office.

For a complete list of all Security Manager duties/requirements refer to OPNAVINST 5510.1H.

7102. Cryptosecurity

Cryptosecurity is the COMSEC component thatresults from the provision of technically soundcryptosystems and their proper use. With thebuilt-in encryption feature of SINCGARS and thewidespread availability of encryption equipmentfor other SCRs and the SBB, it should be possibleto cover all tactical communications. Accom-plishing COMSEC requires detailed planning thatis conducted as an integral part of the overallcommunications planning effort. The require-ments for encryption must be determined and theappropriate equipment and material must be ob-tained to support those requirements. CJCSM6231.05 provides detailed COMSEC informationfor TRI-TAC equipment and is a key reference inplanning the SBB. Units must act immediatelyupon receipt of a COMSEC callout message toobtain the required cryptographic material to beemployed in a particular exercise or operation toinclude, when designated, the intertheater COM-SEC package. In the future, the joint key manage-ment system, which is under development, willenable the electronic distribution of keys through-out the JTF.

Modern cryptographic systems use random num-ber generators to accomplish encryption. By ini-tializing the random number generator with a seednumber, a deterministic sequence of pseudoran-dom numbers is generated. Each time the sameseed is used, the same sequence of numbers isgenerated. The pseudorandom numbers may then

be used, for example, to modify a bit stream tosend over a communications network. If the re-ceiver of the bit stream has access to the seed usedby the sender, the modified bit stream can be de-coded. The bit stream may consist of data, or itmay be digitized voice. With this approach to en-cryption, it is not necessary for the equipment it-self to be highly classified as was the case withWorld War II era encryption equipment. It is onlylosing the seed number, or key, that will compro-mise the encrypted information. Therefore, themanagement and control of keying material is ofutmost concern. Commanders should limit theholdings of keying material to the minimum re-quired for operations. This material must be trans-ported, stored, safeguarded, destroyed, andaccounted for in strict accordance with existingregulations.

7103. Transmission Security

Transmission security (TRANSEC) is that com-ponent of COMSEC that results from all mea-sures designed to protect transmissions frominterception and exploitation by means other thancryptoanalysis. The Marine Corps’ goal is to se-cure all tactical communications circuits and SCRnets. However, even encrypted communicationsmay be targeted, exploited, and disrupted by anenemy’s intelligence and EW organizations viatraffic analysis, direction finding, and jamming.TRANSEC is an important component of the unitelectronic protection effort.

a. SCRStrict radio discipline and adherence to authorizedprocedures are key to ensuring TRANSEC overSCR networks. Operating SINCGARS radios in afrequency hopping mode provides maximum pro-tection against enemy EW capabilities. OtherTRANSEC measures include:

● Training operators thoroughly on proper com-munications procedures and equipment opera-tion. (This includes all Marines that mayoperate SCR, not just CIS personnel.)

● Avoiding unauthorized transmission and test-ing and maximizing use of data networks to

7-4 ________________________________________________________________________________________________ MCWP 6-22

minimize transmission time and opportunityfor enemy direction finding.

● Using transmitter, antenna, and power combi-nations that produce minimum wave propaga-tion and emission intensity consistent withreliable communications.

● Strictly adhering strictly to authorized frequen-cies.

● Using authentication systems to protect againstimitative deception on nonsecure nets.

● Using changing call signs and frequencies onnonsecure nets.

● Promptly responding to and reporting enemyjamming. (Operators should continue to oper-ate on assigned frequencies in a secure mode,unless otherwise directed by a competent au-thority, and should attempt to work through theinterference.)

● Strictly adhering to all EMCON restrictionsand observance of radio silence.

● Using communications means that do not radi-ate in the electromagnetic spectrum such asmessengers, visual and sound signaling, and lo-cal wire loops.

● Using terrain masking to shield transmissionsystems from enemy EW systems.

● Remoting transmitters and avoiding the cluster-ing of antennas.

b. Multichannel Radio and WireInformation is often compromised by the assump-tion that wire is secure. While wire is inherentlymore secure than radio, the SBB normally usesMCR to move traffic beyond the local geographicarea. Furthermore, when a wire infrastructure isused over an extended area, the line can betapped. Sensitive traffic, voice or data, should beeither sent over covered circuits or encrypted pri-or to transmission over nonsecure circuits. MCRoperation in close proximity to the enemy is ofconcern because the high power of transmissionequipment and continuous mode of operation areeasily detectable and could potentially reveal thelocation of units and CPs. Use of terrain maskingand, where possible, limiting forward and backlobe emission into enemy territory are measures

that can reduce the vulnerability of MCR to ene-my EW.

In addition to encryption and measures to reducethe probability of interception, traffic flow securi-ty is required. Traffic flow security conceals thepresence of messages on communications cir-cuits. Traffic flow security is normally achievedon the SBB by using trunk encryption devices togenerate a continuous stream of bits, making thecircuit appear busy at all times.

7104. Emission Security

Emission security (TEMPEST) is the componentof COMSEC that results from all measures takento deny unauthorized persons information of val-ue that might be derived from interception andanalysis of compromising emanations fromcrypto equipment and telecommunications sys-tems. The operation of communications and infor-mation systems may result in unintentionalelectromagnetic emissions. Although tacticalequipment is designed to reduce the possibility ofsuch emissions, COTS equipment is not. Uninten-tional emissions are extremely susceptible to in-terception and analysis and may discloseclassified information. Commanders must followapplicable regulations providing guidance on con-trol and suppression of such emissions.

7105. Physical Security

Physical security is the COMSEC component thatresults from all physical measures necessary tosafeguard classified equipment, material, and doc-uments from access or observation by unautho-r i zed pe r sons . The acces s t o c l a s s i f i edcryptographic information must be tightly con-trolled. When a commander or designated repre-sentative has determined that an individual has aneed to know and is eligible for access, then ac-cess to classified cryptographic information willbe formally authorized. The authorization processmust include an introduction to the unique natureof cryptographic information, its unusual sensitiv-ity, the special security regulations governing its


handling and protection, and the penalties pre-scribed for its disclosure. In the event of a viola-tion of physical security, a report is required.Reportable violations include:

● Loss of material.● Unauthorized viewing.● Capture of individuals having access to COM-

SEC information.

Currently fielded COMSEC equipment is unclas-sified for external viewing when appropriate cov-ers are in place and no keying material is visible.Consequently, the exposure of such equipment to

casual viewing by uncleared personnel, whetherby accident or as the result of operational necessi-ty, does not constitute a reportable violation.

Personnel planning for and setting up the SBBmust be aware of the requirement for red/blackisolation. This refers to the separation of circuits,systems, equipment, and areas that handle classi-fied plain text (red) information in electronic sig-nal form from those that handle unclassified(black) information in electronic signal form.(Black signals include encrypted signals becausethese signals would not divulge national securityinformation if recovered and analyzed.)

7-6 ________________________________________________________________________________________________ MCWP 6-22

Section II

Computer Security

Command and control on the modern battlefielddepends increasingly on information systems. Theamount of data that is processed and the tempo ofoperations combine to make manual proceduresinadequate except at the small unit level. Even atthe small unit level, automated systems are prolif-erating, particularly in the fire support area. Theincreasing dependence on tactical informationsystems drives the requirement to protect thesesystems from disruption or exploitation by hostileforces. In much the same way that COMSEC pro-vides the security for information transferredthrough communications systems, COMPUSECprovides the security for information that is col-lected, stored, processed, and displayed by com-puters and peripheral equipment at user locations.

7201. The Threat

With the openess of the Internet, intruders can in-flict damage on information systems from virtual-ly any location with little fear of detection.Today’s information systems are connected intoworldwide communications networks that areonly as secure as the weakest link. The enemy caneasily gain access to much of the same informa-tion infrastructure used by the MAGTF. Intrudersdo not require sophisticated technology. A non-technical means, such as a compromised pass-word, can bypass LAN security features. Onceaccess is gained, the attacker can employ mali-cious logic to inflict tremendous damage on ourinformation systems. (Malicious logic is comput-er code designed to deny, destroy, modify, or im-pede system configurations, programs, data files,or routines. Types of malicious logic include vi-ruses, Trojan horses, logic or time bombs, andworms.) The enemy will have several objectivesin attacking MAGTF information systems.

a. Information CompromiseA major goal of threat attacks on MAGTF infor-mation systems is to gain access to classified or

sensitive information. Access to this informationprovides the enemy insight into MAGTF, joint,and national capabilities; force and resource loca-tions; plans and intentions; readiness status; andknowledge of what is known about the enemy.This type of information, when discovered andused to advantage, has often been the deciding fac-tor in the outcome of battle. In today’s environ-ment, this type of information is surprisingly easyto obtain. For example, careless e-mail exchangeswith family and friends can reveal plannedMAGTF movements and operations. E-mail iseasily and readily collected by enemy agents.

b. Information ModificationAnother objective of attacks on our informationsystems is information modification. Such infor-mation corruption can be used to create an elec-tronic deception. Undetected, it can lead toincorrect assumptions and subsequent faulty deci-sions. In other instances, the attack may be de-signed to destroy information required to executethe MAGTF planning and decision cycles. In ei-ther case, detection of the attack can severely re-duce confidence in the MAGTF’s informationsystems. The MAGTF’s ability to observe, orient,decide, and act more quickly than the enemy de-pends greatly on the information provided by theinformation systems used. Reduced confidence,induced time delays, and undetected, faulty infor-mation can all severely degrade the commander’sability to make sound and timely decisions.

c. Denial of ServiceStill another objective of enemy attacks on our in-formation systems is either total or partial restric-tion of our ability to process, retrieve, anddisseminate information. Data corruption resultsin lost confidence and service self-denial. Suc-cessful enemy attacks on stored data, applica-t i ons , o r ope ra t i ng sy s t ems may r ende rinformation systems unusable. Damage or physi-cal destruction to equipment, facilities, and per-


sonnel will be a high priority for the enemybecause our communications information systemscapabilities are viewed as critical vulnerabilitiesand key targets. Such attacks may range from ter-rorist truck bombings to more technologically ad-vanced enemies using directed energy weapons.The environment is also a potential disruptiveforce. Information systems, particularly COTSsystems, are very susceptible to power surges;temperature extremes; and dusty, dirty, and sandyconditions encountered in the austere littoral areasin which the MAGTF operates.

7202. Protection

Protection of MAGTF information systems is es-sential. COMPUSEC is the means of providingthat protection. This includes knowledge of thethreat and employment of operating procedures,equipment, and personnel training to counter thatthreat. COMPUSEC also includes putting intoplace measures to detect intrusion early and plan-ning for immediate action to counter attacks, and,if necessary restore lost data and service.

a. ResponsibilitiesCOMPUSEC is a command responsibility andmust be understood and practiced by all MAGTFinformations systems users. However, overall net-work and information systems security responsi-bi l i ty belongs to the CISO. This includesestablishing policy and procedures for LAN,WAN, and information systems management.Procedures are required to manage user identifica-tion and passwords assignment, to provide authen-tication, and to maintain visibility and control ofthe operation and use of network services. The CI-SO coordinates network management functions,including security, with the individual LAN man-agers and information systems coordinators.Training and education in threat capabilities andCOMPUSEC procedures are CISO’s responsibili-ty, supported by the unit security manager, G-2/S-2, G-3/S-3, and in coordination with all LAN man-agers and functional information systems coordi-nators.

b. ManagementThe CISO provides overall COMPUSEC manage-ment through policies, directives, plans, and train-i ng . The CISO gu ides LAN manage r s ,information systems coordinators, and informa-tion systems users in implementing proceduresnecessary to maintain reliable and secure informa-tion systems. Much of the security for informa-tion systems is provided at the individualworkstation through operating systems and appli-cation-specific access mechanisms. However, fornetworked applications and services, a well-de-vised network security plan is necessary to man-age the various accesses and privileges thatcontrol read and write access to files and data.Monitoring the network is required to documentactivity and detect intruders. COMPUSEC proce-dures must be integrated with and complement theoverall communications information systems planto ensure responsive service to authorized userswhile protecting against unauthorized access.

c. ImplementationDOD Directive 5200.28 establishes mandatory,minimum standards for automated informationsystems. It promotes using computer-based secu-rity features that emphasize the personal responsi-bility of system users. Current procedures rely onstandalone workstations and system high net-works, which require dedicated routers andswitches, making system security managementdifficult. There are many ongoing programs toprovide improved security services for individualworkstations, LANs, and the overall DII. Multi-level Information Systems Security Initiativeproducts and services are being fielded incremen-tally as technology matures. They include—

(1) Cryptographic Cards. PC-configured cryp-tographic cards are gradually being introduced toprovide different levels of personal security pro-tection, including confidentiality, data integrity,identification/authentication, and nonrepudiation.

(2) Firewalls. Firewalls protect MAGTF net-works from outside networks such as the Internet.Firewalls with Fortezza identification and authen-tication allow Fortezza card-holders controlled ac-cess to the NIPRNET from outside networks. This

7-8 ________________________________________________________________________________________________ MCWP 6-22

capability prevents unauthorized access to the sen-sitive but unclassified information on the NIPR-NET while providing convenient access forauthorized users.

(3) High Assurance Guards. High assuranceguards, such as the secure network server withstandard mail guard, are used to protect againstunauthorized release of classified informationfrom a classified facility while allowing the re-lease of unclassified information. High assurancemeans that the guard has been verified by the Na-tional Security Agency to be highly resistant topenetration based on the application of rigoroussecurity software engineering methods, extensivepenetration testing, and security analysis duringits development, production, and fielding. Theguard is required for information processing andexchange between facilities or systems operatingat different levels. The guard also ensures that ex-ternal requests for access to the “guarded” highersecurity level locations are approved before al-lowing that access.

(4) In-Line Network Encryptor. In-line networkencryptors provide data confidentiality and integ-rity across LANs and WANs. They employ en-cryption and access control through cryptographickey management. Some in-line network encryp-tors can also provide traffic flow security services.In-line network encryptors operate with IP routers,packet switches, synchronous optical networks,and asynchronous transfer mode networks. Someof the in-line network encryptors offer combina-tions of these capabilities to allow for the futuregrowth of networks based on synchronous opticalnetwork and asynchronous transfer mode technol-ogies. A key feature of in-line network encryptorsis that they encrypt only the data, not the address

information. This allows the transmission of clas-sified data on unclassified networks or SCI data onsecret networks. In-line network encryptors,through software configuration and appropriatekeying material, are used to link multiple sites.

(5) Security Management Services. Secu r i t ymanagement services include security measuressuch as cryptographic keying, access control, au-thentication, and the use of passwords. These ser-v ices a re needed to implement e f fec t iveinformation systems security programs within theMAGTF. Key security management services in-clude—

● Local authority workstations that reside on theLAN and provide security capabilities such asdigital signatures, cryptographic keys, and ac-cess control permissions.

● Rekey managers that work in conjunction withelectronic key management systems to providecryptographic rekey support for Multilevel In-formation Systems Security Initiative products.

● Audit managers that provide support for thecollection and analysis of security-relevantevents that can be audited and are associatedwith Multilevel Information Systems SecurityInitiative products. Repeated failed user loginis an example of a security-relevant event thatcan be audited.

● Directories that provide a repository for publicsecurity information essential for effective glo-bal message addressing. The public part of auser’s digital signature is an example of thistype of public security information.

● Mail list agents that are used by messaging sys-tems to add security for messages that are sentto many recipients.


Section III

Incident Response

Effective response to attacks on MAGTF infor-mation systems requires that all users and supportpersonnel be aware of attack indicators and theprocedures to be followed in the event of an at-tack. The Marine Corps Command Center (MC-CC) and the Network Operations Center (NOC)will exchange information in the event of an IN-FOSEC incident. The MCCC will act as the com-munica t ions l ink be tween the NOC andHeadquarters Marine Corps throughout the inci-dent. The NOC has the overall responsibility ofmanaging any computer intrusion incidents in theMarine Corps.

7301. The Fleet Information Warfare Center

The Fleet Information Warfare Center is the Na-vy’s principal agent for development of informa-tion warfare and command and control warfaretactics, procedures, and training. The center de-ploys personnel trained in command and controlprotection and is equipped with appropriate infor-mation systems security equipment to supportbattle group and JTF operations. It is responsiblefor providing computer incident response teamsand is the single point of contact for monitoringthe security of information systems. All computerincidents (break-in attempts and malicious logic)are reported to the center. The center publishesadvisories containing the latest information onsystem vulnerabilities and effective countermea-sures. These advisories are received from the cen-ter’s computer incident response team by theMarine Corps Network Operations Center anddisseminated to all Marine Corps commands.

7302. Naval INFOSEC Help Desk

The information systems security help desk at Na-val In-Service Engineering Activity on the EastCoast provides expert assistance with all informa-

tion systems security and computer security prob-lems. This help desk receives calls 24 hours dailyand is manned a minimum of 8 hours per day,Monday through Friday. Emergency calls are re-ceived via cellular phone when the help desk isnot manned. Services include—

● Security policy interpretation.● Installation, configuration, support, and train-

ing for implementation of network securityproducts:

• Internet firewalls.• Standard mail guard.• Secure network server.• Fortezza cards.• Packet filters and routers.• UNIX host security.

● Additional guidance is provided on—• The Multilevel Information Systems Securi-

ty Initiative.• Protected distribution systems.• Secure systems and Tempest certifications.• Cryptographic/COMSEC equipment.• Secure voice systems.• The Navy Key Management System.• Secure telemetry and communications.• Computer and network security tools.• Risk assessment and vulnerability surveys.• Destruction, purging, or recovery of sensi-

tive data.• Computer systems accreditation and certifi-

cation.• Controlled access.• Distribution of naval computer security pub-

lications.• Training courses.• Other naval INFOSEC resources.

7-10 _______________________________________________________________________________________________ MCWP 6-22

7303. The Air Force Information Warfare Center

The Air Force Information Warfare Center devel-ops, maintains, and deploys command and controlwarfare capabilities in support of operations, cam-paign planning, acquisition, and testing. The cen-ter acts as the single focal point for command andcontrol warfare services and provides technicalexpertise for computer security and COMSEC.The Air Force computer emergency responseteam is part of the center and is responsible for re-porting and handling computer security incidentsand vulnerabilities. The center publishes adviso-ries containing the latest information on system

vulnerabilities and effective countermeasures.These advisories are received by the MarineCorps Network Operations Center and dissemi-nated to all Marine Corps commands.

7304. Points of Contact

Appendix N provides points of contact, includingtelephone numbers, WWW uniform resource lo-cators (URLs), and e-mail addresses, for INFOS-EC and other key organizations. Appendix Pincludes a list of reference documents. This infor-mation should be verified and incorporated intocommand and control plans and SOPs.

Chapter 8

Future Directions

The Marine Corps implementation of commandand control is based on a maneuver warfare phi-losophy. Effective support of maneuver warfaredemands a flexible command and control systemthat can support rapid decisionmaking and execu-tion to create and maintain a high tempo of opera-tions. CIS and equipment are the means throughwhich effective command and control support isprovided. These systems must be as robust, flexi-ble, and expeditionary as the MAGTF they sup-port. They are employed across the full spectrumof operations, from humanitarian assistance oper-ations to general war. They support the MAGTFwhether forward deployed or in garrison.

Most importantly, MAGTF CIS must be equallycapable of supporting all expeditionary operationsconducted by the Marine Corps—operational ma-neuver from the sea (OMFTS), sustained opera-tions ashore, and military operations other thanwar (MOOTW). This chapter focuses on OMFTS,the concept by which naval forces will projectpower ashore in the 21st century. As the com-mand and control doctrine and organizationsevolve to meet the requirements of OMFTS,MAGTF CIS and equipment must evolve as well.This chapter provides a framework for under-standing the unique considerations in the employ-ment of CIS to support OMFTS.

8001. Operational Maneuver from the Sea

The underlying operational concept for allMAGTF operations is OMFTS. This concept isthe application of the principles of maneuver war-fare to naval forces at the operational level. Whilenot every MAGTF operation is an OMFTS, themaneuver warfare principles associated with itprovide the basis for all Marine Corps operations.

In OMFTS, the MAGTF operates as part of a na-val expeditionary force in the conduct of a jointcampaign.The primary focus of OMFTS is to al-low a sea-based MAGTF to decisively engage en-emy forces and accomplish naval and jointobjectives. New technologies and capabilities inamphibious operations will allow the MAGTF toengage the enemy from positions of advantageand to penetrate to the heart of an enemy system,destroying his ability and will to resist effectively.

OMFTS may allow the MAGTF to act as an en-abling force, allowing the introduction of largerland-based forces to commence sustained opera-tions ashore; as a decisive force, where theMAGTF operates to achieve the decisive cam-paign objectives of a joint force commander; or asan exploitation force that takes advantage of op-portunities created by other elements of the jointforce. The transition to sustained operationsashore (SOA) or other expeditionary operations(OEO), and the decision to base all or some of theMAGTF ashore for long periods will depend onthe situation and assigned missions. OMFTS isbased on two key implementing concepts—ship-to-objective maneuver (STOM) and seabasing.

a. Ship-to-Objective Maneuver

The implementing concept of STOM combinesthe ship-to-shore movement with subsequent op-erations ashore into a single, decisive maneuverdirectly from the ship. STOM generates operatingtempo by avoiding a pause to build up combatpower ashore. Full exploitation of this concepthinges on fielding the advanced amphibious as-sault vehicle (AAAV) and the MV-22 to transportthe surface assault and the vertical assault, re-spectively. However, through skillful use ofavailable platforms, STOM is possible today, al-though on a somewhat restricted scale. Figure 8-1(on page 8-2) depicts the STOM concept.

8-2 ________________________________________________________________________________________________ MCWP 6-22

b. SeabasingSeabasing is another important implementingconcept for executing OMFTS. Seabasing envi-sions bringing ashore only those MAGTF ele-ments that must be ashore to accomplish theirmission. Most fire support, command and control,and logistic functions remain at sea throughoutthe operation. Most aviation support remains sea-based. While some or all GCE C2 transitionsashore, the overall command and control of theMAGTF, centralized in the MAGTF CE, normal-ly stays afloat. Seabasing offers tremendous oper-ational freedom of action to the MAGTF.Retaining command and control, aviation, fires,and logistics afloat reduces the need to establishand then protect shore-based facilities while si-multaneously enhancing the MAGTF’s force pro-tection posture. This translates into increasedoperating tempo and reduced requirements forrear area security. The reduced infrastructureashore also facilitates the rapid reembarkation andredeployment of the landing force.

8002. CIS Requirements

OMFTS provides a means of projecting naval ex-peditionary power directly against an exposed en-emy center of gravi ty (COG) or c r i t ica lvulnerability. However, the execution of OMFTSposes a number of C2 challenges, particularlywith respect to CIS support. Perhaps the most ob-vious challenge is how to provide secure, reliable,high-capacity communications links over extend-ed distances, perhaps as much as 200 miles, fromthe ships of the ATF to rapidly maneuvering sur-face and vertical assault elements ashore. Forlonger distances, innovative solutions and new us-es for existing equipment must be pursued. Satel-lite communications (SATCOM) offers the bestnear term solution. Airborne/ground-based highcapability, multichannel relay sites; long range,high capacity single channel systems; and secureglobal cellular and phone networks are just someof the intriguing possibilities to provide ship-to-objective communications.

Figure 8-1. The STOM Concept.

Communications and Information Systems __________________________________________________ 8-3

In the near-term, several interim fixes are beingpursued, including the possible employment ofthe MRC-142 with appropriately modified anten-nas to enable shipboard operation providing con-nectivity at ranges of up to 40 miles. For longerdistances, SATCOM appears to be the only cur-rently available option. Although the numbers ofSATCOM terminals currently available are rela-tively limited, this situation is improving with thefielding of the AN/PSC 5. However, obtaining theSATCOM access required to provide the commu-nications connectivity needed for command andcontrol of a MEF is problematic because of com-petition with other elements of the ATF, the navalexpeditionary force, and the JTF. Before and dur-ing the early phases of the ship-to-shore move-ment, ultrahigh frequency (UHF) tacticalsatellites (TACSATs) with high frequency (HF)single channel radios (SCR) as backup is the pre-dominant means of long-haul communications.

Once established ashore, MAGTF forward ele-ments may use ground mobile forces (GMF)TACSAT. As previously discussed, employmentof high-capacity, multichannel transmission sys-tems and establishment of the switched backbonecome at some expense in terms of maneuverabili-ty. Tradeoffs will demand careful analysis. Futuresystems should seek to overcome these limita-tions.

Another key ingredient for successful OMFTS isthe provision of real-time COP throughout theATF and the landing force. OMFTS depends onfree maneuver of both the surface assault and thevertical assault elements to exploit the developingsituation and to avoid obstacles and strongpoints.The only way that we can maneuver freely whilesimultaneously providing responsive supportingfires is through continuous, real-time knowledgeof friendly and enemy locations. Presently, thisposition location information (PLI) is availablethrough the PLRS system installed aboard theLHD class of amphibious ships and can be dis-seminated throughout the ATF by JMCIS. Ship-board coverage of landing force maneuverelements must be maintained until the landingforce brings a master station ashore. Dependingon the distances involved, relay units, either sur-

face or airborne, may be required for effectivePLRS operation. Future systems will exploit PL-RS, GPS and other navigation systems, linked tocommunication and information systems, to pro-vide an accurate, real time COP throughout theMAGTF and Navy force.

To conduct OMFTS, the MAGTF must have theability to employ its information systems effec-tively while at sea. This is an area in which signif-icant improvements are rapidly occurring. Bothtactical combat operations (TCO) and intelligenceanalysis system (IAS) are routinely deployedaboard amphibious ships, and connectivity is be-ing provided to the JMCIS LAN. However, pres-ently these installations are occurring on an adhoc basis, and the installation varies from ship toship even within the same class. It is thereforecritical that the command and control officer be-gin planning early to ensure not only adequatenumbers of workstations, but also, just as impor-tantly, adequate LAN connectivity. Workstationsdedicated to MAGTF LAN connectivity are re-quired in all landing force command and controland administrative work spaces in all ships of theamphibious ready group, not just in the LFOCaboard the flagship. Future seabased MAGTF fa-cilities will require CIS connectivity that is as ef-fective throughout the battle space as that forshore based facilities. In other words, whetherseabased or shore-based, CIS capabilities andavailability should be transparent to users in fu-ture command naval control and administrativefacilities.

Full implementation of OMFTS will place strin-gent demands on the command and control capa-bilities of the MAGTF. The MAGTF will exercisecommand and control both ashore and afloat overgreatly extended distances. Furthermore, theMAGTF will depend on increasing amounts of in-formation to plan operations, deploy and sustainits forces, and execute its missions. Effective in-formation management will be critical for fo-cused , e f f i c i en t command and con t ro l .Information systems must provide a common pic-ture of the battlefield and shared situationalawareness throughout the battlespace. Communi-cations systems must provide a robust voice and

8-4 ________________________________________________________________________________________________ MCWP 6-22

data communications capability throughout thebattlespace and connectivity to information re-sources throughout the world.

The CIS discussed in chapters 3, 4, and 5 will pro-vide many of these capabilities in the near future.This includes the migration of tactical informa-tion systems to the GCCS and the fielding of in-ternet protocol (IP) router and IDNX-basedgateways and servers. Continual improvements inthe packaging of tactical information systems willresult in smaller, more maneuverable operationscenters and CPs. Another significant develop-ment is the JTF enabler, which will allow aMEU(SOC) to provide initial communications

and information systems support to a follow-onforces commander.

As a final note, MAGTF operational concepts areundergoing rapid and dramatic change, not unlikethe field of information technology. MAGTFcommunications and information systems person-nel must adapt the command and control systemto support these evolving concepts. This will bedone through exploitation of information technol-ogy and the continued refinement of proven com-mand and control doctrine. The ultimate goal is toenhance the commander’s command and controlcapabilities—providing the necessary informa-tion at the right place and time for effective plan-ning, decisionmaking, and execution.

Communications and Information Systems __________________________________________________ 8-5

Appendix A

Defense Information InfrastructureCommon Operating Environment Compliance

The concept of a common operating environment(COE) is the most significant part of the GlobalCommand and Control System (GCCS) develop-ment effort. The DII COE encompasses the archi-tecture, standards, and reusable software modulesthat provide a cohesive framework for systemsdevelopment. Even more importantly, the DIICOE guarantees the interoperability of all sys-tems that achieve full COE compliance. This ap-pendix addresses what i s meant by COEcompliance. As with any standard, compliance isrequired to ensure interoperability. More detailedinformation on the DII COE and COE compliancemay be found on the Defense Information Sys-tems Agency (DISA) COE configuration manage-ment web site—http://spider.osfl.disa.mil/cm/1097_cm_page.html. The information in this ap-pendix is extracted from DII COE Version 3.0 of5 February 1997.

Compliance Categories

The DII COE defines four areas of compliancecalled compliance categories. Within a specificcategory, a segment is assigned a numerical val-ue, called the compliance level, which is a mea-sure of the degree to which a segment iscompliant within the category. This approach fa-cilitates the development of migration strategiesfor legacy systems as well as the evaluation ofCOE compliance by both legacy systems and newdevelopments.

Category 1, Runtime EnvironmentCategory 1 measures how well the proposed soft-ware fits within the COE executing environmentand the degree to which the software reuses COEcomponents. It is an assessment of whether the

software will run when loaded on a COE platformand whether it will interfere with other segments.

Category 2, Style GuideCategory 2 measures how well the proposed soft-ware operates from a look and feel perspective. Itis an assessment of how consistent the overallsystem will appear to the end user. It is importantthat the resulting COE-based system appearseamless and consistent to minimize training andmaintenance costs.

Category 3, Architectural CompatibilityCategory 3 measures how well the proposed soft-ware fits within the COE architecture (client/serv-e r a r ch i t e c tu r e , d i s t r i bu t ed compu t ingenvironment (DCE) infrastructure, CDE desktop,etc.). It is an assessment of the software's poten-tial longevity as the COE evolves. It does not im-ply that all software must be client/server andremote procedure call (RPC)-based. It simplymeans that a reasonable design choice has beenmade given that the COE is client/server basedand is built on top of a DCE infrastructure.

Category 4, Software QualityCategory 4 measures traditional software metrics(lines of code, McCabe complexity metric, etc.).It is an assessment of program risk and softwarematurity.

Category 1 Levels

Version 3.0 of the COE defines compliance levelsfor category 1 only. The COE defines eight pro-gressively deeper levels of integration for thiscategory. Levels 1 through 3 are considered to be

A-2 ________________________________________________________________________________________________ MCWP 6-22

interfacing with the COE and not integrated withthe COE. Integration begins at level 4.

Bootstrap compliance (level 4) is required beforea segment may be submitted to DISA for evalua-tion as a prototype. Such segments will not befielded or accepted into the online library. AtDISA's discretion, segments that meet the criteriafor minimal COE compliance (level 5) may be ac-cepted into the online library and installed at se-lected sites as prototypes for user evaluation andfeedback. However, such segments will not be ac-cepted as fieldable products. Acceptance as an of-f i c i a l DISA f i e ldab l e p roduc t r equ i r e sdemonstration of interoperable compliance (level7) and a migration strategy to full COE compli-ance (level 8), unless the proposed segment is aninterim product that is targeted to be phased out inthe near term.

As previously noted, the compliance categoriesand levels are designed to support the migrationof legacy systems into the COE. The first step ofcategory 1, covered by levels 1 through 4, is toensure that systems do not destructively interferewith each other when located at the same opera-tional site. Level 5 is sometimes called a federa-tion of systems in that while systems are stillmaintained as stovepipes, they can safely sharecommon hardware platform resources. Levels 6through 8 complete the migration by reducingfunctional duplication, promoting true data shar-ing, and making the system appear to the user as ifit were developed as a single system. The lastthree levels represent varying degrees of integra-tion from marginally acceptable (level 6) to a tru-ly integrated system (level 8).

Level 1, Standards Compliance

Level 1 is a superficial level in which the pro-posed capabilities share only a common set ofCOTS standards. Sharing of data is undisciplined,and minimal software reuse exists beyond theCOTS. Level 1 may allow simultaneous execu-tion of the two systems.

Level 2, Network Compliance

Two capabilities coexist on the same LAN but ondifferent central processing units (CPUs). Limiteddata sharing is possible. If common user interfacestandards are used, applications on the LAN mayhave a common appearance to the user.

Level 3, Workstation Compliance

Environmental conflicts have been resolved sothat two applications may reside on the sameLAN, share data, and coexist on the same work-station as COE based software. The kernel COE,or its equivalent, must reside on the workstation.Segmenting may not have been performed, butsome COE components may be reused. Applica-tions do not use the COE services and are not nec-essarily inter operable.

Level 4, Bootstrap Compliance

At level 4, all applications are in segment formatand share the bootstrap COE. Segment formattingallows automatic checking for certain types of ap-plication conflicts. Use of COE services is notachieved and users may require separate login ac-counts to switch between applications.

Level 5, Minimal COE Compliance

At this level, all segments share the same kernelCOE, and functionality is available via the execu-tive manager. Boot, background, and local pro-cesses are specified through the appropriatesegment descriptor files. Segments are registeredand available through the online library. Applica-tions appear integrated to the user, but there maybe duplication of functionality and inter operabili-ty is not guaranteed. Segments may be successful-ly installed and removed through the COEinstallation tools.

Level 6, Intermediate COE Compliance

Segments use existing account groups and reuseone or more COE component segments. Minordocumented differences may exist between thestyle guide and the segment's graphical user inter-face (GUI) implementation.

Communications and Information Systems ______________________________________________________________ A-3

Level 7, Interoperable ComplianceSegments reuse COE component segments to en-sure inter operability. These include COE provid-ed communications interfaces, message parsers,database tables, track data elements, and logisticservices. All access is through published applica-tion program interfaces with documented use offew, if any, private application program interfaces.Segments do not duplicate any functionality con-tained in COE component segments.

Level 8, Full COE ComplianceProposed new functionality is completely integrat-ed into the system (e.g., makes maximum possibleuse of COE services) and is available via the exec-utive manager. The segment is fully compliantwith the style guide and uses only published publicapplication program interfaces. The segment doesnot duplicate any functionality contained else-where in the system whether as part of the COE oras part of another mission application segment.

(reverse blank)

Appendix B

Common Hardware andStandard Commercial Software Applications

MAGTF units employ a wide and varied array ofcomputers and peripheral equipment. Althoughsome of this computer hardware represents the lat-est technology in the commercial market, in manyinstances, constrained budgets force units to con-tinue to use some outdated, yet still functioning,equipment. This situation is a fact of life in theFMF and is manageable through proper trainingand effective maintenance practices. However,such equipment will ultimately become more ex-pensive to maintain than to replace.

Standard commercial software is identified by Re-quirements Division, Marine Corps Combat De-velopment Command. These standards arepromulgated to improve interoperability and re-duce training requirements.

Computers are used throughout the MAGTF bothas integral components of tactical information sys-tems and for administrative and logistic supportfunctions. Several fielded tactical information sys-tems including TAOM and PLRS use embeddedNavy standard AYK and UYK computers, whichwill not be addressed here. As new MAGTF C4Isystems are developed and fielded systems mi-

grate to the DII COE, they are hosted on a stand-ard suite of computersCthe Marine commonhardware suite (MCHS).

The Marine Common HardwareSuite

The Common Computer Resources (CCR) Pro-gram Office, Marine Corps Systems Command,continuously evaluates computers and peripheralequipment for inclusion in the MCHS and identi-fies DOD contract vehicles (currently Navy- andArmy-common hardware programs) to use forprocurement by the MCHS. This office maintainsa Computer Buyer’s Guide that is updated on aquarterly basis and posted on the Marine CorpsSystems Command web site (www.marcorsy-scom.usmc.mil). Procurement of common com-puter resources through the MCHS program willhelp ensure commonality, interoperability, sup-portability, and redundancy between the comput-ers and peripherals that support the manyfunctional users. Figure B-1 depicts the categoriesof MCHS equipment currently available throughthe CCR contracts.

Figure B-1. The MCHS.

B-2 ________________________________________________________________________________________________ MCWP 6-22

MCHS High-Performance ServerThe high-performance server (HPS) is intended tofunction as a network server, database server, andcommunications server, or as a central facilityprocessor with rapid processing and display capa-bilities. It is intended for medium-to-large-sizedworkgroups that use processor-intensive applica-tions. HPS computers are available in both UNIX-compatible, reduced instruction set computing(RISC) and PC-compatible, complex instructionset computing (CISC) architectures. The HPSRISC and CISC computers are also available inboth nonrugged (V1) and rugged (V2) variants.Variant 2 is configured to fit into a 19-inch rack.Peripherals available for the HPS include CD-ROM, erasable optical disks, digital audio tape(DAT) drives, high-capacity internal storagedisks, an expansion chassis, enhanced graphics ca-pability, and various video monitors.

MCHS High-Performance Workstation/Application ServerThe high-performance workstation (HPW) has thecapability to function as a server for smallerworkgroups and as a network or standalone work-station. The HPW is available in the same com-puting architectures and variants as the HPS.Variant 1 is available in desktop/deskside andportable configurations. Variant 2 is available in aportable configuration.

MCHS Standard ApplicationWorkstationThe MCHS standard application workstation(SAW) provides network and standalone, high-and low-end, desktop or laptop computers for useat all echelons of the MAGTF. The SAW comput-ers are available in the same computing architec-tures and var ian ts as the HPS and HPWcomputers. Peripherals available for the SAW in-clude CD-ROM, a tape drive, a high-capacity re-movable disk drive, external video monitors,Ethernet LAN interface cards, a ruggedized mag-neto-optical drive, and others.

PeripheralsPeripheral equipment includes items purchasedseparately, such as printers, facsimile modems

and machines, data storage devices, UPSs, andvarious types of displays. Some of these devicesare purchased as standard equipment through thesupply system, and others are obtained as COTSproducts. Additionally, many peripheral compo-nents are provided as part of the MCHS equip-ment fielded for various command posts andcenters. Proper operation of this equipment in-volves using quality cables and ensuring thatproper connections are maintained to computingand LAN equipment. Most peripherals also re-quire software drivers that must be installed withthe appropriate user preferences and settings. Ta-ble B-1 lists some typical peripheral equipmentused with MAGTF information systems.

Data StorageThe MCHS provides a separate four-bay SCSI pe-ripheral device enclosure, commonly referred toas the TAC-4 Data Silo. This enclosure accom-modates two 2.5 GB (4 GB optional) removabledisks, a CD-ROM drive, and a 4-mm DAT drive.The TAC-4 Data Silo is connected to the worksta-tion via an SCSI port. This item is a part of theMCHS suite of equipment.

I/OThe SCSI provides a commercial standard com-puter interface for peripheral devices. The SCSIterminal server is a separate SCSI peripheral de-vice that provides eight RS-232 serial ports andone parallel port as a means of connectivity toother devices. This item is a part of the MCHSsuite of equipment.

PrinterThe MAGTF MCHS printers include both Paint-Jet and DeskJet printers. These printers are avail-able in both color and black and white for hard-copy text and graphics output.

PlotterThe recommended MCHS plotter is a DesignJetmodel.

ScannerThe recommended MCHS scanner is a ScanJetmodel.

Communications and Information Systems ______________________________________________________________ B-3

DisplayThe large group display is composed of a flat-panel video display that rests on top of a high-in-tensity overhead projector to project the worksta-tion screen displays. This item is a part of theMCHS suite of equipment.

Power Supply/ProtectionUPSs protect computers from the power surges offield-generated power. The UPS also provides abackup power source.

End-User Computing Equipment

The End-User Computing Equipment (EUCE)Program fields microcomputer systems through-out the FMF for general-purpose administrativeinformation processing and for information sys-tem workstations. The EUCE, AN/UYK-83, andthe downsized version, DEUCE, AN/UYK-85,are ruggedized, Tempest-certified 286, 386, and486 IBM-compatible computers. These comput-ers are being replaced by more capable computerspurchased through the MCHS program.

Table B-1. MCHS Peripheral Equipment.

Category Peripheral Equipment

Storage Z-Micro single, dual plus, three-bay, four-bay, and seven-across expansion chassis with removable hard drives and media canisters

Input/Output (I/O) SCSI Terminal Server

Printer Hewlett-Packard DeskJet and LaserJet Models

Plotter Hewlett-Packard DesignJet Models

Scanner Hewlett-Packard ScanJet Models

Display Large Group Display Flat-Panel Video Display

Power Supply UPSRuggedCOTS

(reverse blank)

B-4 ________________________________________________________________________________________________ MCWP 6-22

Appendix C

Ship Visit Checklist

Action Items

Ship visits are conducted by the CIS officer be-fore embarkation. CIS representatives embarkedaboard the same ship should coordinate a jointmeeting. CIS requirements have to be completelycoordinated with the ship’s information officer sothat an exchange of information, decisions, plans,orders, and instructions may be properly execut-ed. Every attempt should be made to get a writtenagreement by all concerned. Key considerationsduring ship visits follow.

In Preparation● Determine communications center require-

ments (number of augmentees).● Determine circuit requirements.● Determine TECHCON capabilities.● Identify classified material and CMS storage

needs.● Identify HAZMAT storage needs.

During Ship Visit● Determine space available for landing force:

• Communications control• Message reproduction and distribution• CIS officer and staff office• Cryptographic material and equipment stor-

age• Battery storage• CIS equipment repair benches• Radio central• Troop training spaces.

● Locate joint spaces (joint intelligence center,SACC, etc.).

● Provide prioritized list of landing force circuitrequirements (by type operation).

● Discuss ship’s ability to meet landing forceneeds.

● Discuss equipment type, operational condition,and interoperability.

● Identify shortfalls.● Discuss deck mounting policy (i.e., location,

type of equipment, security, and safeguardingof ship’s watertight integrity).

● Provide guard list and summary of anticipatedarrivals and departures.

● Discuss communications center and other ship-board personnel augmentation requirements.

● Discuss message quantities and distributionprocedures for landing force message traffic.

● Obtain copy of Ship’s Loading and Character-istics Pamphlet (SLCP).

● Review SLCP for accuracy.● Review Marine tactical CIS systems and/or

communications detachment SOP(s).● Identify shipboard CIS available for landing

force use. (See list at end of this checklist.)● Coordinate EMCON notification-of-change

procedures.● Discuss joint circuits and facilities to be used

during each phase of the operation.● Resolve location, quantity, and restoration pri-

orities of landing force circuits. Get a copy ofthe phone directory for the ship’s spaces to pre-pare a phone directory for all landing forcespaces (including berthing and state rooms) andother critical spaces aboard the ship.

Also Discuss:● Antenna locations● Frequency separation requirements● Shipboard interference problems● Joint intelligence center communications

C-2 __________________________________________________________________________________________________________________________________________________________ MCWP 6-22

● How to handle high-precedence and special-category landing force message traffic

● SCI communications● Access lists● Remote locations● Use of signal communications during EMCON● Supplies and communications center operating

stocks to be provided by landing force● Fleet secure voice communications (FLTSE-

VOCOM) channelization● Competing requirements/potential problem ar-

eas● Lost communications procedures● Window versus carrier frequencies● Telephone locations● Multichannel channelization● Clearance and message-release needs● Use of brevity codes, authentication, and so on● Types of information systems available● Availability of Navy and Marine Corps CIS op-

erators, maintainers, and supply support per-sonnel

● Operational checkout of shipboard equipmentdesignated for landing force use

● LAN connectivity to “green spaces”● FCC-100 (SHF) channelization (satellite access

request coordination)● DSN trunks● JDISS● GCCS● TCO, IAS, AFATDS, Logistic AIS (LOGAIS),

etc.● IP addresses● Use of copiers/printers/scanners● INMARSAT● NIPRNET● SIPRNET● JWICS● Unique systems (PLRS/KSQ-1, situational

awareness beacon with reply (SABER), en-hanced PLRS)

● Plain old telephone system (POTS)● KY-68 (connection to Pentagon red switch)● EHF capabilities

Shipboard CIS

The following CIS represent the types of systemsfound aboard amphibious ships in the fleet. Thislist is not all inclusive; it is meant to stimulatethought and lead to a constructive dialog amongembarking Marine and ship’s company CIS per-sonnel. Systems will vary widely among ships ofthe same type and among different types of ships.This is because all ships are rotated periodicallythrough service life extension program overhaulswhere they receive new systems and system up-grades that are planned through the combat devel-opment process.

C2● JMCIS Unified Build 1.X, 2.X, 3.X, etc.● CTAPS host/remote● CTAPS 5.2 (TAC n)● Joint Maritime Tactical Communications

Switching System (JMTCSS) (formerly TRI-TAC and smart multiplexing unit (SMU))

● Integrated Video System (23TV) closed-circuittelevision video switch

● Radiant Mercury A rules-driven multilevel se-curity automatic sanitizer

● AN/USQ-119D, NTCS-A IV● GCCS phase 2 or 3● 9TV (SXQ-8)

Satellite Communications● INMARSAT A/B● W-band commercial SATCOM● EHF SATCOM USC-38 ● Navy EHF communications controller (NECC)● EHF medium data rate (MDR) MILSTAR● High-speed fleet broadcast● WSC-3 UHF SATCOM/line of sight

Communications and Information Systems ____________________________________________________________________________________________________ C-3

● WSC-6 SHF SATCOM/7’ antenna● Global Broadcast Service (GBS)/Joint Broad-

cast Service (JBS)● UHF DAMA● 5 kHz DAMA AN/USC-54

Logistics● Naval Tactical Command Support System

(NTCSS) includes the following:• Shipboard Nontactical Automated Data Pro-

cessing (ADP) Program (SNAP): includesautomated supply, financial, organizationalmaintenance management, administration,and medical functions

• Naval Aviation Logistics Command Man-agement Information System (NALCOMIS):includes intermediate and organizational-level maintenance management

● Maintenance Resource Management System(MRMS): automates shipboard intermediatemaintenance management.

Communications● Joint Maritime Communications Strategy (JM-

COMS) includes—• Automated Digital Network System

(ADNS): network management, switching,routing, and control

• Digital Modular Radio (DMR) System: mul-tifunction radio (2 kHz - 2 GHz)

• Integrated Terminal Program (ITP): militaryand commercial radio at frequencies above 2GHz.

● Link 4A air intercept control and fighter-to-fighter data link

● Link 11 AN/USQ-125 common shipboard dataterminal set (CSDTS)

● Link 16 (JTIDS)/command and control proces-sor rehost

● Officer in Tactical Command Information Ex-change System (OTCIXS)

● TACINTEL (UHF Fleet SATCOMSubsystem)/TACINTEL II Plus

● Tactical Data Information Exchange System-Subsystem A (TADIXS-A)

● TADIXS-B tactical receive equipment ● JTT/commander’s tactical terminal (CTT)● Battle Group Information Exchange System

(BGIXS)

Tactical Communications● Mission Display System● Battlegroup cellular telephone system● Maritime Cellular Information Exchange Sys-

tem (MCIXS)● High-frequency radio group (HFRG)● R-2368A HF/low frequency-medium frequen-

cy receiver● SINCGARS (3 channel)● UHF Digital Wideband Transmission System

(DWTS) ● UHF antijam HAVE QUICK● Video Information Exchange System (VIXS)

Intelligence-IW Sensors● JWICS● JDISS● Battle Group Passive Horizon Extension Sys-

tem (BGPHES)● Common high-bandwidth data link (CHBDL)● Outboard/combat direction finding● Ship’s signals exploitation equipment● JSIPS-Navy (JSIPS-N)● DSSCS● TACINTEL● Tactical Remote Sensor System (TRSS)

Message Processing● NAVMACS I/II● AN/SSQ-33A Shipboard Automated Commu-

nications Control System● UGC-143A(V) Navy standard terminal (NST)● Navy orderwire

C-4 __________________________________________________________________________________________________________________________________________________________ MCWP 6-22

Miscellaneous CIS Equipment● Red analog switch● Black analog switch● Battlegroup HF e-mail● Information transfer for the 21st century (IT-

21)● IT-21 DNS-GENSER

● IT-21 DNS-SCI● Red/black baseband switch● SSQ-88C Quality Monitoring System● Electronic Key Management System Phase 2● Navy Key Management System local manage-

ment device

Appendix D

MAGTF Radio Nets

This appendix provides the basic description andparticipants for each radio net. It is a planningguide for radio nets that may be established to sat-isfy MAGTF CIS requirements. CIS officers mustemphasize to users of this appendix that not all ofthe listed radio nets will be used in a given opera-tion or exercise. As few as two or three nets maysuffice to meet mission requirements.

The kinds of services (voice, video, facsimile,etc.) that are required should be determined andadjusted to conform to available resources (per-sonnel, equipment, and frequency/channel avail-ability) and environmental characteristics. Therequired service will be governed primarily by thetactical situation, terrain features, and distancesbetween stations on the net (with due consider-ation to equipment inventories and available per-sonnel). Multiple nets of the same type may beestablished to handle excess traffic volume. Thesenets would have a number suffix such as 1, 2, and3 for the primary, secondary, and tertiary circuitsof the same type. The primary net descriptions aregiven in this appendix.

Within each net composition, units in italics nor-mally participate in the specified net as required.There is no absolute requirement for each unitnoted to participate in net composition. CIS offic-ers can use the net composition in this appendixfor planning and compiling radio guard charts(which SPEED provides) for operations.

Where multiple frequency bands are listed in pa-rentheses following radio net titles, the frequencyband that is normally assigned is listed first.

Marine Expeditionary Force Master Net Lists

The MEF Master Net List is a database that facili-tates the MEF’s Revised Battlefield ElectronicCEOI System CEOI generation. These files areunclassified and consist of every circuit within theMEF and each circuit’s emission requirements, aswell as grouping, call sign, and call word infor-mation. The list is important to SINCGARS net-work planners because it is the sole source for netassignments and net identifiers. Characteristics ofthe Master Net List are presented in table D-1 (onpage D-2).

The MEF Master Net List is controlled by theMEF G-6 and is managed by the MEF frequencymanager. The MEF Master Net List will be re-viewed annually for proposed modifications onthe basis of input from operating force command-ers. Requests for modification of the Master NetList will be submitted to higher HQ for consolida-tion and review. The Master Net List, and therebyCEOI net assignments, should not be modifiedwithout the review and approval of the MEF G-6.

The need to maintain consistent, standard radionetwork terminology demands that MEF radiocircuit assignments be regulated. With the intro-duction of the Revised Battlefield ElectronicCEOI System Master Net List, electronic CEOIinformation can be matched to the task organiza-tion, edited, generated, and printed for an entireMEF within hours. Unit participation in MasterNet List revisions and compliance are essential tomaintaining the currency of this information.

D-2 ________________________________________________________________________________________________ MCWP 6-22

Marine Air-Ground Task Force Command Element Nets

MAGTF CE nets are established to support theexercise of command and control during combatoperations. The type operation, commander’s in-tent, concept of operations, environment, enemycapabilities, and MAGTF task organization willinfluence which nets are required and established.During amphibious operations the term MAGTFis synonymous with the term landing force.MAGTF CE nets follow:

MAGTF Command Net 1 (UHF-SAT-COM/HF)Used to exercise command and coordinate admin-istrative and logistic functions with the majorcomponents of the MAGTF.

● CE● GCE(s)● ACE(s)● CSSE● Other OPCON units

MAGTF Tactical 1 (UHF-SATCOM/VHF/HF)Used to carry operational traffic between thecommander and major CEs of the MAGTF.

● CE● GCE(s)● ACE(s)● Other OPCON units● Landing force TACLOG

MAGTF Ground ReconnaissanceCommand (UHF-SATCOM/HF)Used for C2 of landing force ground reconnais-sance operations and transmission of collected re-connaissance directly to the MAGTF commanderor the MAGTF CE combat intelligence center(CIC).

● CE● OPCON reconnaissance units ● Unmanned aerial vehicle (UAV) squadron/de-

tachment● GCE(s)

Item Purpose Comment

Net number Reference Used to provide task organization requirements to higher HQ

Net name Description Standard net description

Net ID SINCGARS 000 - 999

Call sign Call-sign assignment Yes or no, assigned randomly

Organizational code Echelon separation Allows for duplicate net IDs within separate units

Restrictions Subband separation Allows for restrictive frequency assignments (such as HF day and night)

Frequency Band assignment N-None, H-HF, F=VHF, A=VHF-AM, U=UHF, S=SHF, E=EHF

Power Output power 1-High through 4-Low

Reuse class Geographic separation Tactical

Call word Call-word assignment Fixed or random

Table D-1. Special Characteristics of the Master Net List.

Communications and Information Systems ______________________________________________________________ D-3

● Other units, as required (e.g., radio battalionradio reconnaissance team (RRT), Navy spe-cial warfare teams, etc.)

MAGTF Alert/Broadcast (HF)

Used for alert warning traffic or general trafficpertaining to all (or the majority) of the units onthis net. Messages not of an alert warning type willbe consecutively numbered upon transmission.

● CE

● Designated units within the MAGTF ground el-ement(s)

MAGTF Intelligence (UHF-SATCOM/HF/VHF).

Used for rapid reporting and dissemination of in-telligence, collaborative planning of futureMAGTF intelligence operations, and commandand control of ongoing MAGTF intelligence andreconnaissance operations.

● CE

● GCE(s)

● ACE(s)

● CSSE

● OPCON intelligence and reconnaissance units

● UAV squadron/detachment

MAGTF Air Observation (UHF/VHF)

Used to coordinate air observation and transmitinformation from air observers to MAGTF ele-ments. May be used to adjust artillery or navalgunfire (NGF) on an emergency basis.

● CE

● Aerial observer

● GCE

● FSCCs

● Artillery battery FDC

● Supporting arms special staff (SASS)

MAGTF NGF Support 1 (HF)Used to request NGF support and coordinate theemployment of NGF support ships in general sup-port of the landing force.

● SACC

● GCE(s)

● Landing force general support ships

● CE

MAGTF Fire Support Coordination (UHF-SATCOM/VHF/HF)Used to coordinate all MAGTF fires. Activated atthe CE when a FFCC or FSCC is established.

● SACC

● FFCC and senior FSCC(s)

● Senior artillery FDC


● SASS

NGF Control (HF)Used to request, assign, and relieve fire supportships. Also used to request general support mis-sions and report reliefs, emergencies, and orderspertinent to the execution of scheduled fires. TheCATF may establish an NGF control overload netto handle excess traffic.

● CATF/SACC

● Fire support group and unit commanders

● Fire support ships

● Screen commanders

● GCE NGF officer

NGF Ground Spot 1 (HF)Used to control individual ship gunfire support.Its primary use is to call and adjust fire, and itssecondary use is to exchange vital information be-tween stations on the network, such as frontlinepositions. Activated at the MAGTF CE levelwhen a MAGTF FFCC or FSCC is established.

D-4 ________________________________________________________________________________________________ MCWP 6-22

● Battalion FSCC(s) (NGF liaison officer(s))

● NGF spot team(s)

● FFCC and/or FSCC(s)

● Direct support ship(s)

● General support ship(s)


Shore Fire Control Party Local 1 (VHF)Used to coordinate shore fire control party activi-ties.

● NGF spot team

● NGF liaison officer

MAGTF Artillery Command/FireDirection (HF)Used to direct the fires of artillery units when es-tablished ashore. Established only when two ormore independent artillery units are providing firesupport for the MAGTF.

● FFCC/FSCC/SASS

● SACC (MAGTF artillery officer afloat)

● MAGTF artillery units

MAGTF Artillery Air Spot (UHF/VHF)Used to conduct air spot for force artillery fires ondeep and difficult targets. Activated at MAGTFlevel only when artillery units are under the directcontrol of the MAGTF commander.

● Force artillery air spotters

● CE

● GCE artillery air spotters

● Artillery units

MAGTF Convoy Control 1 (VHF/HF)Used to control the various elements within a con-voy. Artillery units and aerial observers may enterto ensure security of motor march routes. Multipleconvoy control nets may be required dependingon the extent of motor march activity within theforce.

● Convoy commander

● Designated convoy elements

● Artillery units and aerial observers

● HQ of unit conducting convoy

MAGTF Landing Zone (LZ) Control 1 (UHF/VHF)Used to control and coordinate helicopters enroute between the initial point and the LZ.

● MAGTF CE

● Support helicopters

● LZ control team

● MAGTF support party

● Helicopter support teams

Helicopter Support Team Control 1 (HF)Used to control and coordinate helicopter supportteam activities.

● MAGTF CE TACLOG group

● TACLOG support helicopters


● Helicopter support teams

Helicopter LZ (HLZ) Local 1 (VHF)Used to coordinate helicopter support team activi-ties within an LZ.

● Helicopter support team

MAGTF CSS (UHF-SATCOM/HF/VHF)Used to coordinate CSS within the MAGTF.

● CE

● GCE(s)

● ACE(s)

● CSSE

● TACLOG element


MAGTF Damage Control (HF)Used to exchange damage assessment informa-tion subsequent to an enemy attack with mass de-s t ruc t ion means . Also used to d i rec t andcoordinate evacuation and casualty assistance fora stricken unit.

● CE

● All MAGTF units of battalion/squadron sizeand larger

● Damage control parties/ monitor teams

● Mass evacuation units

● Designated medical units

MAGTF Damage Control Local 1 (VHF)Used to coordinate damage control efforts withina local area.

● Damage control parties

MAGTF Support Party Control (HF)Used for combat units to request support from thelanding force support party (LFSP) and for theLFSP to coordinate with TACLOGs for landingof equipment and supplies.

● Landing force TACLOG

● GCE TACLOG


● LFSP liaison teams

● FSSG/brigade service support group/MEU ser-vice support group

Shore Party Net (VHF)Used to coordinate shore party activities on alanding beach or on multiple beaches.

● Shore party

● Beach party team

MAGTF Local Security (VHF)Used to coordinate CE security.

● HQ commandant● Security elements as directed

MAGTF Medical Regulating (HF)Used to coordinate casualty distribution amongmedical treatment facilities.

● Landing force casualty evacuation agency● Medical battalion/unit● Hospital ships● Designated medical facilities

MAGTF Communications Information Systems Coordination 1 (UHF- SAT-COM/HF/VHF)Used to coordinate, install, and restore MAGTFcommunications-information systems operations.

● CE (G-6/S-6)● GCE (G-6/S-6)● ACE (G-6/S-6)● CSSE (G-6/S-6)● Communications unit (S-3/detachments)

MAGTF EW Coordination (HF)Used to coordinate electronic attack (EA) andSIGINT activities.

● CE (G-3/S-3 EWCC)● OCAC● GCE● TACC● TAOC

MAGTF Defense Special Security Communications System Entry (UHF-SATCOM/HF/Multiplex (MUX))Used to provide the MAGTF commander with anSCI data communication capability with externalagencies. The communication path is provided bythe supported commander, and the terminalequipment and personnel are provided by theradio battalion/special security communicationsteam (SSCT).

D-6 ________________________________________________________________________________________________ MCWP 6-22

● MAGTF CE via the radio battalion/detachmentspecial security communication element

MAGTF Special Intelligence Communi-cations Net External (HF)Used to provide the MAGTF commander with asecure data communications channel for the ex-change of SCI. The communications path is pro-vided by the supported commander, and theterminal equipment and personnel are providedby the radio battalion/SSCT.

● MAGTF CE via the radio battalion detachmentspecial security communication element

● CJTF

● CATF

MAGTF Critical Communications (CRITICOMM) Net (UHF-SATCOM/VHF)Used to provide the supported commander with achannel to adjacent Service cryptologic agenciesor cryptologic support group. The communica-tions path is provided by the supported command-er, and the terminal equipment and personnel areprovided by the radio battalion/SSCT.

● MAGTF CE via the radio battalion/ SIGINTsupport unit (SSU) special security communi-cations element

● Higher HQ, adjacent HQ, and theater and na-tional intelligence/SIGINT agencies

MAGTF Internal Special Intelligence Communications Handling System Net (VHF/UHF/SHF)Used to provide the MAGTF commander with asecure SCI communications capability with sub-ordinate division/wing commanders through theirorganic SSCT. The communications path is pro-vided by the supported commander, and the ter-minal equipment and personnel are provided bythe radio battalion/SSCT.

● MAGTF CE via radio battalion/SSU special se-curity communications element

● Division SSCT

● MAW SSCT

Radio Battalion/SSU Command and Control Net (HF/VHF)Used to provide the battalion commander/detach-ment officer in charge with command and controlof subordinate elements. The communicationspath, equipment, and personnel are provided bythe radio battalion.

● Radio battalion

● Radio battalion direct support unit

Theater Cryptologic Support Net(HF/UHF-SATCOM)Used to provide rapid exchange of cryptologic in-formation with the cryptologic elements of otherorganizations. The communications path is pro-vided by the supported commander, and the ter-minal equipment is provided by the radiobattalion direct support unit.

● MAGTF (radio battalion direct support unit)

● Adjacent Service cryptologic elements

● National cryptologic agencies

● Joint/ATF cryptologic agencies

Radio Battalion CRITICOMM Net(UHF-SATCOM/HF/VHF)Used to provide CRITICOMM facilities to battal-ion elements that are physically removed from theCP in support of MAGTF units. The communica-tions path is provided by the supported command-er, and the equipment and personnel are providedby the radio battalion.

● Radio battalion

● Radio battalion direct support unit (at leasttwo)

Radio Battalion/SSU Collection and Reporting Net (UHF-SATCOM/HF/VHF)Used to provide command and control and SIG-INT reporting capabilities for battalion/SSU col-lection operations.


● Radio battalion/SSU (OCAC)

● Deployed collection/direction funding (DF)teams

Radio Battalion/SSU EA Control Net (VHF)

Used to provide the direction and control of radiobattalion electronic countermeasures assets. Thecommunications path, equipment, and personnelare provided by the radio battalion.


● Deployed EA teams

Radio Battalion/SSU DF Flash Net (VHF)

Used to provide the DF control station with ameans of broadcasting DF flashes to the DF out-stations. The communications path, equipment,and personnel are provided by the radio battalion.


● Deployed DF teams

Radio Battalion/SSU DF Report Net (VHF)

Used for DF reporting from DF outstations to DFcontrol. The communications path, equipment,and personnel are provided by the radio battalion.


● Deployed DF teams

DF Data Net (VHF)

Used to exchange DF information between out-stations and DF control. The communicationspath, equipment, and personnel are provided bythe radio battalion.

● DF outstations

● DF control

Tactical Receive Equipment andRelated Applications Program Data Dissemination SystemUsed to provide global surveillance informationin time for sensor cueing and to provide indica-tions and warning. Data is forwarded from sensorto communications gateways/relays for dissemi-nation to worldwide military users via geosyn-chronous UHF satellite links. TDDS data sourcesinclude national and tactical sensor systems.

● Intelligence agencies● CIC● OCAC● SSES● ATFIC

On-Board Processor/Direct DownlinkUsed to distribute nationally generated data to op-erational forces and commanders worldwide. Theinformation delivered directly to tactical users canbe used to support indications and warning, sur-veillance, targeting (including OTH targeting),maneuver, execution, and battle damage assess-ment.

● Intelligence agencies● CIC● OCAC● SSES● Joint intelligence center

TACINTEL Broadcast ServiceUsed to provide near-real-time intelligence froman open network of interactive participants by us-ing multiple sensors and sources. The TIBSbroadcast uses UHF SATCOM assets for networkoperation and for the relay of out-of-theater spe-cific information into the tactical users’ AOs.TIBS participants include a wide variety of na-tional and Service airborne, surface, and subsur-face intelligence platforms.

● JTF, theater, and national intelligence organiza-tions

● MAGTF CE (CIC)

D-8 ________________________________________________________________________________________________ MCWP 6-22

● ATFIC (SSES)

Tactical Reconnaissance Intelligence Exchange SystemUsed to provide high-accuracy targeting data tomulti-Service/joint Services command, control,and intelligence users. The TRIXS network sup-ports full-duplex data and half-duplex voice con-nectivity between user terminals. It is designed toprovide in-time intelligence reports that are fo-cused on high-payoff ground threat targets. It iscapable of providing maneuver, threat avoidance,targeting, mission planning, and sensor cueingsupport to commanders at all echelons. TheTRIXS network can accept input from up to fiveintelligence producers such as the Army GuardrailCommon Sensor and Airborne ReconnaissanceLow, the Air Force Contingency Airborne Recon-naissance System, and the Navy Story Teller Sys-tem.


● MAGTF CE (CIC)● ATFIC (SSES)

TACINTEL NetUsed for transmission and reception of sensitiveinformation sensor data and voice among collec-tion and reporting units and detachments of theradio battalion, the MAGTF, and shipboard facili-ties, TACINTEL is an automated, high-speed datalink.


● MAGTF CE (CIC)● ATFIC (SSES)

Radio Battalion/SSU MissionEquipment Control Data LinkNet (UHF)Used to control, coordinate, and monitor the mis-sion equipment of the MEWSS. This net is usedfor internal MEWSS operations and for interfaceand cooperative operation with the Army intelli-gence and EW common sensor systems.

● MEWSS internal

● Army Guardrail Common Sensor

● Army Ground-Based Common Sensor

● Army Advanced Quickfix

Radio Battalion/SSU DF Net (UHF)Used to control, coordinate, and report DF data.

● MEWSS

● OCAC

● Army Technical Control and Analysis Element

Radio Battalion/SSU Tasking andReporting Net (VHF)Used to issue taskings/report results

● Team Portable Collection System

● Analyst Subsystem

● Collection outstations

Radio Reconnaissance Command (UHF-TACSAT)Used for command and control of deployedRRTs; reporting of SIGINT collection and DF re-ports.

● MAGTF CE (CIC)

● ATFIC (SSES)

TROJAN SPIRIT II Net (C and Ku Band SATCOM)Used to receive, report, and disseminate intelli-gence information over a special-purpose satellitesystem.

● MAGTF CE (CIC/OCAC)

● ATFIC (SSES)

● External intelligence agencies and organiza-tions

Maritime Prepositioning Ships (MPS) Offload 1 (HF/VHF/UHF SATCOM)Used to control and coordinate the MPS offload.


● Surveillance, liaison, and reconnaissance party(SLRP)

Force Reconnaissance Company Command (HF)Used to exercise command and coordinate admin-istrative and logistic requests of subordinate units.

● Unit HQ● Subordinate units● Liaison personnel

Surveillance and Control Data Link (UHF)The surveillance and control data link is used totransmit moving target indicator, synthetic aper-ture radar, and fixed target indicator data acquiredby Joint STARS to the MAGTF CE to supporttarget acquisition, situation development, bat-tlespace management, and targeting functions.

● JSTARS● MAGTF CE G-2 section's CGS

Air/Naval Gunfire Liaison Company/Marine Liaison Group Command(VHF/UHF)Used to exercise command and coordinate admin-istrative and logistic requests of subordinate units.

● ANGLICO HQ/MLG HQ● Senior liaison team/Marine liaison companies● Subordinate liaison teams

Sensor Control and ManagementPlatoon (SCAMP) Command (VHF)Used for command and control of SCAMP opera-tions and for the coordination of SCAMP admin-istrative and logistic support.

● MAGTF CE CIC (SARC/SCAMP liaison andcontrol element)

● SCAMP/detachment HQ● Monitoring sites/deployed sensor employment

squad (SES)/sensor employment team liaisonteams

● Others, as required

Sensor Reporting Net (VHF)Used as a means for rapid reporting of sensor datato supported units.

● MAGTF CE CIC (SARC [net control])

● SCAMP monitoring sites

● Supported units


SCAMP Data Transmission (VHF)Used for transmission of sensor data collected byremote sensor sites.

● SCAMP liaison and control element monitor-ing sites

● MAGTF CE CIC (SARC)

● Remote sensor and sensor relay sites

CI/HUMINT Team(s) Command(HF/VHF)Used for command and control of CI teams andsubteams, interrogator-translator teams and sub-teams, and HUMINT exploitation teams opera-tions and the coordination of CI/HUMINTadministrative and logistic support.

● MAGTF CE CIC (SARC HUMINT liaison andcontrol element)

● CI/HUMINT company/detachment HQ

● Deployed CI/HUMINT teams and subteams


CI/HUMINT Reporting Net (VHF)Used as a means for the rapid reporting of CI/HU-MINT data to supported units.

● MAGTF CE CIC (SARC [net control])

● Deployed CI/HUMINT teams and subteams

● Supported units


D-10 _______________________________________________________________________________________________ MCWP 6-22

Ground Combat Element Nets

Division/GCE Command 1 (HF)Used by the division/RLT/BLT commander to ex-ercise command and coordinate administrativeand logistic functions.

● GCE HQ (forward, main, and alternate CPs)● Artillery regiment/battalion/battery● Infantry regiment/battalion/company● Reconnaissance battalion/company/platoon● LAR battalion/company● Tank battalion/company/platoon● Assault amphibian battalion/company platoon● Combat engineer battalion/company/platoon● GCE TACLOG group● Attached combat and CSS units

Division/GCE Tactical 1(UHF-SATCOM/HF/VHF)Used by commanders to exercise TACON of ma-jor combat units of the GCE.

● GCE HQ (forward, main, and alternate CPs)● Infantry regiment/battalion/company● Artillery regiment/battalion/battery● Reconnaissance company/platoon● LAR battalion/company● Tank battalion/company/platoon● Assault amphibian battalion/company/platoon ● Combat engineer battalion/company/platoon● UAV squadron/detachment● Attached combat units● GCE TACLOG● MAGTF TACLOG

Division/GCE Ground Reconnaissance Company Command (HF/VHF)Used for command and control of ground recon-naissance operations and for reporting reconnais-sance information for deployed reconnaissanceelements/teams to the GCE G-2/S-2 (SARC).

● GCE HQ (G-2/S-2/SARC)

● Reconnaissance units

● LAR units


Division/GCE Intelligence (HF/VHF)Used to provide rapid reporting and disseminationof intelligence, collaborative planning of futureintelligence operations, and command and controlof ongoing intelligence and reconnaissance opera-tions.

● GCE HQ (G-2/S-2/MAFC)

● Infantry units

● Artillery units

● Reconnaissance units

● LAR units

● Tank units

● Assault amphibian units

● Combat engineer units

● Attached/direct support intelligence units(RadBn SIGINT support unit [SSU], CI team)


● Attached combat and combat support units

Marine Division Defense SpecialSecurity Communications SystemEntry (UHF-SATCOM/HF/MUX)Used to provide the division commander with anSCI data communication capability with externalagencies. The communications path is providedby the communications company, and the termi-nal equipment and personnel are provided by thedivision SSCT.

● SSCT

Division/GCE Fire SupportCoordination (HF/VHF)Used to provide division/GCE-level fire supportcoordination.

● GCE FSCC

Communications and Information Systems _____________________________________________________________ D-11

● Artillery regiment● Subordinate regiment FSCC(s)● UAV squadron/detachment● DASC

Division/GCE CommunicationsInformation Systems Coordination 1 (HF/VHF)Used to coordinate, install, maintain, and restoreGCE communications information systems opera-tions.

● GCE HQ (G-6/S-6)● Infantry S-6s and communications information

systems units● Artillery S-6s and communications information

systems units● Separate battalions (S-6)● Attached combat and combat support units

Division/GCE Convoy Control 1 (VHF)Used to control elements within a convoy and toensure security (threat and fratricide) of motormarch routes.

● Convoy commander● Convoy elements● Artillery units● Aerial observers● Division HQ

Military Police (MP) CompanyCommand (VHF)Used to exercise command and to coordinate ad-ministrative and logistic functions.

● MP company HQ● MP units● GCE provost marshal● Traffic control/mobile units

MP Company Tactical 1 (VHF)Used by MP commander to tactically control andcoordinate MP activities.

● MP company HQ● MP units● Traffic control/mobile units

Combat Engineer Battalion Command (HF)Used for administrative control and OPCON ofsubordinate units.

● Combat engineer battalion HQ● Engineer units● Supporting and attached units● Liaison personnel at higher HQ

Engineer Company Command (VHF)Used for administrative control and OPCON ofsubordinate units.

● Engineer company HQ● Engineer units● Liaison personnel at higher HQ

Engineer Local (VHF)Used to coordinate engineer efforts within a localarea.

● Engineer units/detachments

Tank Battalion/Company/Platoon Command 1 (VHF)Used to exercise command and coordinate admin-istrative and logistic requests. Separate commandnets are set up for each echelon in the battalion.Separate tube-launched, optically tracked, wirecommand link guided missile (TOW) company,platoon, and section command nets are also in-cluded.

● Tank battalion/company/platoon HQ● Tank companies/platoons/tanks● Tank recovery on tank company command● TOW companies, platoons, sections, squads

● Liaison personnel● Supporting and attached units

D-12 _______________________________________________________________________________________________ MCWP 6-22

LAR Battalion/Company/PlatoonTactical 1 (VHF/HF)

Used to exercise TACON of subordinate units.Each echelon has its own tactical command(TAC) net.

● Unit HQ

● Subordinate units and vehicles

● Recovery vehicles (company net)

● Liaison personnel

● Attached units

LAR Battalion Command (HF/VHF)

Used to exercise command and coordinate admin-istrative and logistic support.

● Battalion HQ

● Companies


● Supporting/attached units

LAR Battalion Mortar (VHF)

Used to request and control the fires of the mortarplatoon.

● Forward observer teams

● Mortar platoon FDC

● Mortar representative at the battalion HQ

Assault Amphibian Battalion/Company/ Platoon Command(VHF).

Used to exercise command and coordinate admin-istrative and logistic support. Each echelon has itsown command net.

● Unit HQ

● Subordinate units/vehicles

● Recovery vehicles (company net)


Reconnaissance Company/Platoon Command (HF/VHF)Used to exercise command and coordinate admin-istrative and logistic support.

● Unit HQ

● Subordinate units

● Patrols/support aircraft/vehicles

● Supporting units● Liaison teams at supported units

Infantry Regiment Command (HF)Used to exercise command and coordinate admin-istrative and logistic support.

● Infantry regiment HQ

● Infantry battalions

● CSS area HQ

● Landing support company● Attached units

Infantry Regiment Tactical 1 (VHF)Used to exercise TACON of subordinate units.



● Regimental TACLOG● Supporting and attached units

Infantry Regiment Intelligence (VHF)Used for rapid reporting and dissemination of in-telligence, collaborative planning of future intelli-gence operations, and command and control ofongoing intelligence and reconnaissance opera-tions.



● Intelligence units (radio battalion SSU, coun-terintelligence team)

● Supporting and attached units● Regimental observation post


Infantry Regiment Fire SupportCoordination (VHF)Used for regimental-level fire support coordina-tion.

● Infantry regiment FSCC

● Infantry battalion FSCC(s)

● Artillery battalion(s)

● Other supporting HQ

Infantry Regiment CommunicationsInformation Systems Coordination (VHF)Used to coordinate, install, maintain, and restoreregimental communications-information systemsoperations.



● Supporting and attached units

TACP Local (VHF)Used to coordinate activities of the air liaison of-ficer and forward air controllers.

● Air liaison officer

● Forward air controllers

Infantry Regiment Local Security (VHF)Used to coordinate HQ main area, rear area, andCP security elements. Multiple security nets willbe required.

● HQ commander

● Security elements

Infantry Battalion Tactical 1 (VHF)Used to exercise tactical control and fire directionof subordinate units.

● Infantry battalion HQ

● Rifle companies

● Weapons company● Battalion TACLOG group ● Landing support or helicopter support teams● Battalion liaison officer(s)● Supporting and attached units

Infantry Battalion Mortar (VHF)Used to request and control the fires of the 81-mmmortar platoon.

● Forward observer teams● 81-mm mortar platoon FDC● 81-mm mortar representative at battalion HQ

Scout-Sniper Command (VHF)Used to exercise command and control of battal-ion scout-sniper operations and to report recon-naissance information collected by deployedscout-sniper teams.

● Battalion S-2 and S-3 (fires)● Scout-sniper teams

Rifle Company/Platoon Tactical (VHF)Used to exercise TACON of subordinate units.

● Rifle company or platoon HQ● Rifle platoons or squads/fire teams● Weapons platoon or sections● Company or platoon observation posts● Supporting and attached units

Artillery Regiment/Battalion/Battery Command 1 (HF, Regiment; VHF,Battalion/Battery)Used to exercise command and coordinate admin-istrative and logistic requests. May be used as analternate fire direction net.

● Artillery unit HQ

● Subordinate artillery units● Attached/reinforcing artillery units● Division HQ

D-14 _______________________________________________________________________________________________ MCWP 6-22

Artillery Regiment Tactical 1/2(VHF/HF)Used as a supplemental means for the commanderto exercise command and control of subordinateunits when the command and fire direction netsbecome overloaded. This net may also be used bythe artillery battalion liaison officers for the rapidexchange of fire planning data, counterfire infor-mation, and other artillery liaison activities.

● Artillery regiment HQ

● Division HQ (forward, main, alternate CP)

● Artillery battalions

● Attached artillery units

● Supporting artillery units

● Artillery battalion liaison officers

Artillery Regiment/Battalion/FireDirection 1/2 (VHF/HF, Regiment;VHF, Battalion)Used to exercise tactical fire direction of subordi-nate units by the assignment of fire missions, des-ignation of units of fire, and conduct of time-on-target missions. Subordinate units may use thisnet to request additional fires from organic and at-tached artillery units. This net may also be usedfor the exchange of infantry fire planning data andfire support coordination information when noother means is available.

● Artillery unit HQ

● Division FSCC

● Subordinate artillery units

● Attached/reinforcing artillery units

● Supporting artillery units

● Artillery liaison officers

Artillery Regiment Communications Information Systems Coordination (VHF/HF)Used to coordinate installation and restoration ofcommunications-information systems capabilities.


● Artillery battalions

Artillery Regiment Radar Telling (VHF)Used to exchange radar intelligence informationand for requests for surveillance of enemy coun-terfire weapons. May also be used for registrationand adjustment of artillery fire.


● Countermortar radar sites

● Artillery battalions and batteries

Artillery Regiment Survey/Metro (VHF)Used to exchange survey, meteorological, andballistic information and data between surveyteams and artillery units.


● Artillery battalions/batteries

● Survey officers and teams

● Division HQ

Artillery Battalion/Battery Conduct of Fire (VHF)Used by forward observers to request and adjustartillery fire. Established when fire direction iscentralized; when fire direction is decentralized,each battery in the battalion has a separate con-duct-of-fire net that terminates at the battery HQ.There may be as many as four conduct-of-firenets in each direct-support artillery battalion.

● Artillery battalion or battery HQ

● Battery forward observers

● Battery liaison officers


● Artillery battalion liaison officers

● Attached/reinforcing artillery units

Aviation Combat Element Nets

Wing radio nets that are replaced by static MUXcircuits will remain available as backups.


ACE Command Net 1 (HF)Used to exercise command and coordinate admin-istrative and logistic support.

● ACE HQ● MAGs● Marine wing support group/squadron● Marine air control group/detachment● Independent squadrons/battalions● Attached units

Tactical Air Command 1(UHF-SATCOM/HF)Used by the tactical air commander to task subor-dinate elements to provide aircraft for missions.

● TACC/tactical air direction center (TADC)● TAOC(s)● DASC● Marine aircraft groups/squadrons (as required)● MATCDs● Early warning/control (EW/C)

Command Action (HF/VHF/MUX)Used for command-level coordination of antiairwarfare (AAW) through the exchange of informa-tion pertaining to missile battery employment, as-signment of air targets, and the interceptor/missilecoordination. Net functions may be performedover the air operations control net when an MCRcircuit is not established.

● TACC/TADC● TAOC(s)● EW/C

Antiaircraft Control (HF/VHF/MUX)Used to control surface-to-air missile (SAM) bat-teries. Types of information passed on this net in-clude: target assignments, fire direction orders,weapons status commands, battery status reports,and progress-of-engagement reports.

● TAOC(s)

● EW/C● LAAD Battery CP/ADCP

Air Operations Control (HF/MUX)Used by TAOC to request interceptor aircraft andreport friendly air defense situation information tothe TACC/TADC. Used to exchange informationpertaining to combat air patrol availability, sta-tioning and assignment, assignment and disposi-tion of targets, intercept progress, SAM unitstatus and employment, and aircraft/missile weap-ons coordination. Multiple air operations controlnets are normally required; one or more for eachTAOC in operation.

● TACC/TADC● TAOCs● LAAD Battery CP/ADCP● Early warning/control activities

Antiaircraft Intelligence (HF/MUX)Used by SAM batteries to report targets acquiredby the battery surveillance radar. TAOC passesselected early warning contacts to missile firingunits. Combined with the antiaircraft control netwhen MUX is not available.

● TAOC(s)● Air defense fire units● EW/C● LAAD Battery CP/ADCP

Combat Information/Detection(HF/MUX)Used to report unidentified or hostile aircraft, in-cluding initial contact reports, tracking, amplify-ing, and final disposition. Multiple combatinformation/detection nets may be established formultiple TAOCs.

● TAOC(s)● Early warning/control activities● LAAD Battery CP/ADCP● Air defense fire units● DASC (as required)

D-16 _______________________________________________________________________________________________ MCWP 6-22

● MATCD (as required)● TACC/TADC● Other reporting agencies

Handover/Cross Tell (HF/MUX)Used to transfer aircraft control between air con-trol agencies. Multiple nets can be established forthe TAOC-early warning/control handover orground control intercept-ground control approachhandover. Functions may be combined on one netif traffic permits.

● TAOC● Early warning/control● ATC Detachment, MACS● MATCD● Other-Service control agencies

LAAD Battalion Command (HF)Used to exercise command and coordinate admin-istrative and logistic support.

● LAAD battalion HQ● LAAD battery● Command Posts/ADCP

LAAD Weapons Control (HF)Used for air defense warnings, weapons controlconditions, and pertinent information concerningfriendly, enemy, or unknown aircraft.

● Command Posts/ADCP● LAAD battery ● LAAD platoon commanders/section leaders

LAAD Team Control (VHF)Provides air defense warnings, weapons controlcondition and pertinent information concerningfriendly, enemy, or unknown aircraft to LAADteams. Multiple LAAD team control nets are nor-mally employed.

● LAAD section leaders● LAAD teams

Interface Coordination (HF/UHF VHF/MUX)Provides a means for command level coordinationin the employment of certain tactical weapons andfor interface command, control, and coordination.

● TACC

● Other-Service agencies

● TAOC

TADIL A (HF/UHF)Used to exchange digital data between variousTDSs. Types of data passed include air and sur-face tracks, weapons status, and selected ordersand functions. TADIL A operates as a star-netteddata link.

● TACC

● TAOC(s)

● EW/C

● Other-Service air control agencies

TADIL B (MUX)Used in a point-to-point mode by using a full-du-plex wire/multichannel path (a functional equiva-lent to TADIL A). NATO designation: Link 11 B.

● TACC

● TAOC(s)

● EW/C

● MATCD


TADIL C (UHF)Used as a one- or two-way unsecure digital datalink between air control agencies and interceptoraircraft. NATO designation: Link 4A.

● TAOC

● EW/C

● Interceptor aircraft

● Other-Service air control agencies (E-3/E-2Caircraft, ship AAW facilities)


Army Tactical Data Link (ATDL)-1 (MUX)Used for secure, point-to-point exchange of airbreathing track data. Data passed includes refer-ence tracks, missile status, and missile engage-ments.

● TAOC

● Early warning/control

● Army Air Defense units

Ground-Based Data Link (VHF)Used for air defense CP downlink of surveillanceinformation to short-range firing units.

● ADCP

● Short-range air defense

● Remote sensors

Point-to-Point Data Link (MUX)Used for one-way transmission of TBM nonairbreathing track data.

● ADCP

● TPS-59 radar

Track Supervision Net (TSN)(HF/UHF/MUX)Used by surveillance personnel to exchange infor-mation in order to maintain a clear picture. Maybe combined with Data-Link Coordination Net(DCN) for SCR operations.

● TACC/TADC

● TAOC(s)

● Antiaircraft operations center

● Early warning/control activities

Data-Link Coordination Net(HF/UHF/MUX)Used for maint/coord of data-link operation. Maybe combined with TSN for SCR operations. Gen-erally one DCN per TADIL-B/ATDL-1.

● TACC

● TAOC


Radar Remote Coordination (VHF/HF)Used to exchange early warning/control track andcontrol data.

● TAOC

● TAOMs

● Early warning/control sites

Voice Product Net (HF/UHF/MUX)Used to report/forward hostile target SIGINT in-formation that is not reportable in a standard dataformat.

● TACC

● TAOC

● Other interfacing agencies

ACE Communications Information Systems Coordination (HF/VHF)Used to coordinate installation and restoration ofcommunication capabilities.

● Wing HQ

● Marine aircraft groups

● MACGs

● Marine wing support group/squadron

● Independent squadrons/battalions

● Attached units

Direct Air Support (HF/MUX)Used by DASC to request direct air support air-craft from the TACC. Information pertaining toaircraft stationing, fuel and ordnance status, andprogress of direct air support missions may bepassed over this net.

● TACC/TADC

● DASC

D-18 _______________________________________________________________________________________________ MCWP 6-22

Tactical Air Request/HelicopterRequest (TAR/HR) (UHF-SATCOM/HF/VHF)Used by forward ground combat units to requestimmediate air support from the DASC. Intermedi-ate ground combat echelons (FSCCs) monitor thisnet and may modify or disapprove a specific re-quest. The DASC uses the net to brief the request-ing unit on the details of the mission. Targetdamage assessments and HRs may be passed overthis net. Multiple TAR/HR nets may be required,depending on the scope of close air support opera-tions.

● DASC

● TACPs

● HDC

● TAOC

● Tactical air coordinator (airborne)

● Forward air controller (airborne)

Tactical Air Traffic Control (TATC) (UHF/VHF)Used by the TACC/TADC, TAOC, and DASC toexercise control of all tactical and itinerant air-craft in the objective area. Used to pass aircraft re-ports of launches by mission number, to clearaircraft to their assigned control agencies, to di-vert aircraft as necessary, and to report missionscompleted before landing. Multiple TATC netsare required for each control agency.

● TACC/TADC

● TAOC(s)

● DASC

● EW/C

● Fixed-wing aircraft

● Helicopters

● UAV ground control station (GCS)

Fighter Air Direction (FAD) (UHF/VHF)Control aircraft in the conduct of intercepts. Mul-tiple FAD nets are required and assigned to majorcontrol agencies.

● TAOC

● Early warning/control

● Interceptor aircraft

● Other-Service AAW agencies

Tactical Air Direction (TAD) (UHF/VHF)

Used to direct aircraft in the conduct of offensiveair support missions and to brief support aircrafton target information or assignment. MultipleTAD nets are required and are assigned to majorair control agencies by the DASC. This net is pri-marily UHF with a secondary VHF capabilityavailable in some cases.

● DASC

● UAV GCS

● TACP

● Forward air controller (airborne)

● Offensive air support aircraft

Helicopter Direction (HD)(UHF/VHF/HF)

(Navy: inbound and outbound; USMC: control ofhelicopters in the objective area) Used by theHDC for positive control of inbound and out-bound helicopters in the amphibious objective ar-ea. The radar controller in the HDC uses thesenets to direct flight course and altitude of helicop-ters and holdings, let-downs, and climbout whenrequired. Both UHF/VHF and HF HD nets areemployed. Multiple HD nets are required and areallocated by the DASC.

● DASC

● HDC

● UAV GCS

● Assault support coordinator (airborne)

● Helicopters

● Helicopter LZ Control Team (LZCT)

● Tactical air controller (airborne)

● TACP


Tanker (UHF)Used by in-flight refueling aircraft to communi-cate with the tanker. Used by TAOC to exchangeinformation with the tanker.

● Tanker

● In-flight refueling aircraft

● EW/C

● TAOC

Squadron Common (UHF/VHF)Used for in-flight group or squadron aircraft, andgroup or squadron HQ, communications. Eachaircraft squadron has its own common net.

● Group or squadron HQ

● In-flight group or squadron aircraft

Guard (UHF/VHF/HF)Used by aircraft to declare an emergency. Usedby air control agencies to advise aircraft of emer-gency conditions or serious hazards to aircraftsafety.

● TACC/TADC

● TAOC(s)

● DASC

● MATCD

● EW/C

● Fixed-wing and helicopter aircraft

Crash, Fire, and Rescue (VHF)Used to coordinate crash recoveries on or aroundan airfield.

● Crash crew

● ATC facility

● Airfield operations

● Explosive ordnance disposal

● Medical facility

● MP

Search and Rescue (SAR) (UHF/VHF)Used to control and coordinate air rescue mis-sions. Multiple SAR nets may be required de-pending on the number of concurrent SARmissions.

● All elements within the command and controlsystem

● Aircraft involved in SAR missions

ATC Common (HF/MUX)Used to coordinate airspace management betweenairfields.

● Air traffic controller(s)

Approach Control (UHF/VHF)Used to control air traffic approaching the termi-nal airspace.

● Approach controller

● Approaching aircraft

Departure Control (UHF/VHF)Used to control air traffic departing the terminalairspace.

● Air Traffic Control Facility

● Departing aircraft

Ground Control Approach (GCA) (UHF/VHF)Used to provide bearing and altitude to approach-ing aircraft.

● TATC

● Aircraft

Ground Control (UHF/VHF)Used to control ground movement of vehicles,aircraft, and personnel on the taxiways and run-ways.

D-20 _______________________________________________________________________________________________ MCWP 6-22

● Ground control● Aircraft

● Vehicles

● Personnel

LZ Control (VHF/UHF)Used to control aircraft en route between the ini-tial point and the LZ.

● LZCT● Aircraft en route between the initial point and

the LZ

● DASC● Aircraft coordinator (airborne)

LZCT Local (VHF)Used to direct the activities of aircraft control per-sonnel in each of the landing sites.

● LZCT commander

● Landing site controllers

Air Base Security (VHF)Used to coordinate security operations of expedi-tionary airfields (EAFs).

● MPs at the EAFs

Air Defense Alert (UHF)Used to direct coordination and exchange of criti-cal threat information and verbal warning to air-craft t ransi t ing minimum risk routes andoperating near missile engagement zones.

● Ground-based air defense units

● Combat air patrol aircraft

● Transiting to friendly aircraft

Convoy Control (VHF)Used to control the various elements within a con-voy.

● Convoy commander

● Convoy elements● Aerial observers● ACE HQ

Defense Meteorological SatelliteProgram Satellite Imagery(SATCOM)Used as an encrypted receive-only circuit to pro-vide a direct readout of real-time satellite imageryfrom polar orbiting satellites of the Defense Mete-orological Satellite Program.

● Deployed Marine wing support squadron(MWSS)

Fire Support Safety (HF)Used to exchange information concerning the em-ployment of artillery, NGF, surface-to-surfacemissiles, and close air support aircraft to ensuresafety of all aircraft in the objective area.

● Air control agencies and elements

Fleet Facsimile (HF)Used as a broadcast receive-only circuit to pro-vide weather graphics produced by Navy regionalcenters.

● Broadcast from NCTAMS● Deployed MWSS

Fleet Multichannel Broadcast(UHF SATCOM)Used as a receive-only circuit on channels 8 or 15(environmental channels) of the satellite to pro-vide weather bulletins produced by Navy regionalcenters.

● Broadcast from NCTAMS● Deployed MWSS

Goldwing Communications (HF)Used as a secure, in-theater, joint net that may beused for voice traffic but is primarily for transmit-ting and receiving alphanumeric weather data.


● Other-Service meteorological and oceano-graphic agencies

● Deployed MWSS

Landing Signal Officer (UHF)Used to coordinate control of the landing patternwith the control tower and to control aircraft inthe landing pattern. A tower secondary frequencyis normally used for this requirement.

● ATC Facility

● Aircraft in pattern

● Landing signal officer

Medical Evacuation (MEDEVAC)Coordination Net (VHF)Used to coordinate MEDEVACs.

● Requesting unit

● Evacuation helicopters

● Medical facilities

Pilot to Metro (UHF)Used for exchange of meteorological information.

● Flying aircraft

● Weather detachment at EAF

Rear Area Security (VHF)Used to coordinate security operations of groups/squadrons/attached units at EAFs and air controlagency locations.

● Security element task organized by the units atthe EAFs and air control agency locations

Strip Alert (HF/VHF)Used to coordinate fixed-wing aircraft and heli-copter operations at the EAF.

● Air boss

● Tactical air watch officer

● Assault support watch officer

Tactical Alert (HF)Used for rapid dissemination of air-raid warnings.

● MAGTF HQ

● GCE/ACE/CSSE HQ

● Air control agencies

Television Infrared ObservationSatellites Imagery (SHF)Used as an unencrypted receive-only circuit toprovide a direct readout of real-time satellite im-agery from the National Oceanographic Atmo-spheric Administration.

● Deployed MWSS

Tower Hot (HF/VHF)Used by ATC to inform the TACC of launchedaircraft.

Tower Primary (UHF/VHF)Used by controller to issue traffic advisories andaircraft clearances within the EAF.

Tower Secondary (UHF/VHF)Overflow traffic from the tower primary.

Weather Radar Net (AN/FPS-106)Used as a single-site radar that provides a visualdepiction of precipitation and storm structurewithin a 200-nautical-mile radius of its location.

● Deployed MWSS at the EAF

Wing Intelligence (HF)Used for rapid reporting and dissemination of in-telligence information.

● ACE G-2

● Group S-2

● Squadron S-2

D-22 _______________________________________________________________________________________________ MCWP 6-22

MAW Defense Special Security Com-munications System Entry (UHF-SAT-COM/HF/MUX)Used to provides the wing commander with anSCI data communication capability with externalagencies. The communications path is providedby the communications company, and the termi-nal equipment and personnel are provided by theMAW SSCT.

● SSCT

Wing Logistic Net (HF)Used to request logistic support.

● ACE G-4

● Group S-4

● Squadron S-4

Link-1 (NATO) (MUX)Used for point-to-point interface with NATO AirDefense Ground Environment (NADGE) agen-cies in a full-duplex data link to exchange air de-fense information.

● TACC/TADC

● TAOC

● NADGE agencies

UAV Command Net (HF/VHF/UHF)Used to coordinate UAV activities.

● UAV squadron/detachment HQ

● GCS

● Launch and recovery site

● Remote video terminal teams

UAV Primary Uplink Control (G-Band)Used to control air vehicle and payload.

● Ground data terminal

● Launch and recovery

● Air vehicle

UAV Secondary Uplink Control(G-Band)Used to control air vehicle and payload if primarylink control is lost.

● Ground data terminal

● Launch and recovery

● Air vehicle

UAV Telemetry Downlink (G-Band)Used to provide real-time video display of targetarea and downlink flight control data.

● GCS

● Launch and recovery site

● Remote video terminal teams

● Air vehicle

Combat Service Support Element Nets

CSS Command 1/2 (UHF-SATCOM HF/VHF)Used to exercise command and coordinate admin-istrative and logistic support.

● Unit HQ

● General support group

● Direct support group

● CSS detachments

CSS Alert/Broadcast (HF)Used for alert warning or general traffic pertain-ing to all (or a majority) of the units. Messagesnot of an alert warning type will be consecutivelynumbered at the time of transmission.

● Unit HQ

● General support group

● Direct support group

● CSS detachments


CSS Damage Control (HF)Used for damage assessment information that isexchanged subsequent to an enemy attack withmass-destruction means. Evacuation and casualtyassistance for stricken units may also be directedover this net.

● Unit HQ● General support group● Direct support group● CSS detachments

CSS Communications Information Systems Coordination (HF/VHF)Used to coordinate, install, maintain, and restoreCSSE communications and information systemsoperations.


CSS Local (VHF)Used to coordinate activities within CSS local area.


CSS Security (VHF)Used to coordinate security elements in the CSSoperating areas.

● CSS HQ commandant● Security elements as directed by HQ comman-

dant

CSS Request (UHF-SATCOM/VHF)Used to receive requests from supported units andprovide status.

● CSSOCs

● CSS detachments● Supported unit(s)

LFSP Command (HF/VHFUsed to exercise command and coordinate admin-istrative and logistic support of own units. Thisnet is also used to coordinate the movement ofsupplies being landed over multiple coloredbeaches.

● LFSP HQ● Shore party/helicopter support groups● Shore party/helicopter support team

Shore Party Control (VHF/HF)Used to coordinate the flow of supplies and per-sonnel. A separate net is established for each col-or of beach.

● Shore party group (operating the beach)● Shore party teams● TACLOG group of supported units using indi-

cated beach● Shore party liaison teams with supported units● LFSP HQ ● MAGTF TACLOG

Engineer Support BattalionSubordinate Unit Command(HF)Used to exercise command and coordinate admin-istrative and logistic requests of subordinate units.

● Unit HQ ● Subordinate units

Motor Transport Battalion Company Command/Convoy Control (VHF/HF)Used to exercise command and coordinate admin-istrative and logistic requests of subordinate units.Used to control and coordinate convoys.

● Unit HQ● Convoy commander

D-24 _______________________________________________________________________________________________ MCWP 6-22

● Convoy front

● Convoy rear

Medical Battalion Command (VHF)Used to exercise command and coordinate admin-istrative and logistic requests of subordinate units.

● Medical battalion HQ

● Medical companies

● Hospital companies

Medical Battalion EvacuationCoordination (Ground) (VHF)Used to coordinate ground MEDEVAC.

● Medical unit HQ● MEDEVAC ambulances/vehicles● Evacuation/treatment facilities ● Requesting units

Medical Battalion EvacuationCoordination (Air) (VHF)Used to coordinate air MEDEVAC.

● Medical unit HQ● MEDEVAC aircraft● DASC● Evacuation/treatment facilities ● Requesting units

Appendix E

Information Systems Directory

Section I

Overview

An information systems directory is one of themos t c r i t i c a l documen t s pe r t a in ing t oCIS planning. It shows a subscriber how to usethe system to the maximum extent possible with-out assistance from communications or data sys-tems personnel. The principal function of thisdirectory is to provide guidelines from which CISofficers and telephone systems officers may pro-duce a directory for their commands/organiza-tions. Section II of this appendix is a sampledirectory for II MEF. It supports the design char-acteristics of the MAGTF tactical communica-tions network.

Security of Information

The information systems directory for a given or-ganization, even one as large as the MEF, neednot be classified if the directory contains informa-tion derived from unclassified sources. For exam-ple, a listing of organizations with subscribernumbers that are consistent with this appendixand are unchanging from operation to operationneed not be classified. However, an informationsystems directory could be used as a source of in-formation for enemy intelligence collection.Therefore, an information systems directoryshould be handled as For Official Use Only if itcontains CIS architecture diagrams or if it will beused in an operation outside of CONUS.

Cover

A cover can specify which organization createdthe directory, for what community of users the di-rectory is intended, and the effective period forthe directory.

Emergency Numbers

Emergency numbers provide the subscriber rapidaccess to the numbers of certain critical agencies(e.g., aid station, combat operations center, forceprotection platoon). These numbers should alsobe listed in the organizational listing.

Index

An index is an optional feature that serves as a ta-ble of contents. The size of the directory deter-mine the need for an index.

General Instructions

These instructions discuss the differences in thetypes of telephone equipment that may be used bya unit during an operation. The telephone equip-ment should include tactical equipment such as theKY-68, TA-954, and TA-1042, STU-III’s, com-mercial equipment, and cellular telephones. Eachhas its own special operating instructions.

Operating Instructions

These instructions tell subscribers how to effec-tively use the tactical automated switching system(TASS) and commercial systems. They should listthe unique operating characteristics of each tele-phone system.

Dialing Instructions

These instructions will aid subscribers in usingthe different telephone systems found in a MEF-level exercise. Instructions should give enough

E-2 ________________________________________________________________________________________________ MCWP 6-22

detail to allow unfamiliar subscribers to effective-ly use the system. Instructions should not changetoo much from unit-to-unit or from operation-to-operation, as the equipment characteristics do notchange. Instructions do not describe every avail-able subscriber feature of the switching system.This technical information may be found in TMsor the CJCSM 6231 series for the specific equip-ment.

Precedence Subscribers

Circuit switched calls within a network are pro-cessed according to five levels of precedence. Theprecedence levels follow in ascending order.

Routine (R)

Routine has no precedence over any other call andis handled sequentially as placed by the callingparty. There is no preemption of any lines. Rou-tine precedence designation applies to normal of-ficial government communications.

Priority (P)

Priority has precedence over any other telephoniccall of lower precedence (routine calls). Priorityprecedence is reserved generally for telephonecalls by parties requiring expeditious action orrequiring essential information for conductinggovernment operations.

Immediate (I)

Immediate has precedence over and will preemptroutine and priority calls. Immediate precedenceis reserved generally for telephone calls pertain-ing to—

● Situations that gravely affect the security of na-tional and allied forces.

● Reconstitution of forces in a post attack period.

● Intelligence essential to national security.

● Diplomatic negotiations to reduce or limit thethreat of war.

● Implementation of Federal Government actionsessential to national survival.

● Situations which gravely affect the internal se-curity of the United States.

● Civil Defense actions concerning direction ofour population and their survival.

● Disasters or events of extensive seriousnesshaving an immediate and detrimental effect onthe welfare of the population.

● Vital information having an immediate effecton aircraft, spacecraft, or missile operations.

Flash (F)

Flash has precedence over and preempts immedi-ate, priority, and routine calls. Flash precedenceis reserved generally for telephone calls pertain-ing to—

● Command and control of military force essen-tial to defense and retaliation.

● Critical intelligence essential to national sur-vival.

● Conduct of diplomatic negotiations critical tothe arresting or limiting of hostilities.

● Dissemination of critical civil alert informationessential to national survival.

● Continuity of Federal Government functionsessential to national survival.

● Fulfillment of critical United States internal se-curity functions essential to national survival.

● Catastrophic events of national or internationalsignificance.

Flash Override (FO)

Flash override has precedence and preempts allother types of telephone calls. The application ofthe FO capability is available to—

● The President of the United States, Secretary ofDefense, and Joint Chiefs of Staff.

● Commanders of unified and specified com-mands when declaring either Defense Condi-tion One or Defense Emergency.

● CINCNORAD when declaring either DefenseCondition One or Air Defense Emergency andother national authorities as the President mayauthorize.

Communications and Information Systems ______________________________________________________________ E-3

Dialing Precedence Calls

The precedence indicator (P, I, F, or FO) is dialedfrom the subscriber’s telephone terminal keypad,and is dialed first in any dialing sequence. If noprecedence is dialed, the call is processed as rou-tine. The unit CIS officer (in accordance withstandard operating procedures) determines whichtelephones will have precedence capability. Theprecedence capability is programmed into the cir-cuit switch memory. If a subscriber has a prece-dent capability, any precedence indicator can bechosen in a dialing sequence, up to the level thathas been authorized. A subscriber attempting touse precedence levels higher than that authorizedwill have the call processed at the maximum au-thorized level. Both loops and trunks are preempt-able. A call cannot preempt a loop or trunk in theswitch that is handling a call of equal or higherprecedence.

Numbering Plan

The tactical telephone numbering plan is based ona 13-digit numbering scheme and is structured in-to four parts:

NATO Code (9YX)

NATO members have reached a standardizationagreement (STANAG) to use a unique three-digitnational identification (NI) number. The NI codefor tactical U.S. forces is 914. Calls to NATOsubscribers can only be made from the mediumunit level switch (AN/TTC-42) when it is con-nected to the AN/TTC-39 large circuit switch.

Area Code (MYX)An area code is a number that identifies an area orregion of switches. Area codes are only assignedduring very large military operations in whichseveral Services are working together in a jointoperation. DISA DSN area codes are assigned bygeographical areas as follows:

312 - CONUS313 - Caribbean314 - Europe315 - Pacific317 - Alaska318 - CENTCOM

Unique Area CodesIf a very large military operation is conducted, allof the forces in a theater might be assigned theirown unique area code (300 for example). Depend-ing on which part of the world they are deployedto, if a military operation becomes extremelylarge, the MARFORs have several area codes re-served for their use.

MARFOR ACOM 204MARFOR CENTCOM 304MARFOR PACOM 804MARFOR SOCOM 408

Inter-Area DialingWhen calling a subscriber who is serviced by adifferent area code (MYX), the full ten-digit num-ber must be dialed (MYXPRSLGXX). As with di-aling another PRSL, the same 9 or 91 escape codemust be used. The number dialed will be either—

9 MYX PRSL GXX or91 MYX PRSL GXX

Switch Code (PRSL)A switch code is a unique number that identifiesone particular circuit switch. It is composed oftwo parts; the first two digits are the primary zone(PR) and the last two digits are the switch locator(SL). The switch code is also called the “PRSL”.All circuit switches must be assigned a switchcode, whether operating independently or as part

9YX MYX PRSL GXX ||

||

||

||

NATOCode

AreaCode

SwitchCode

SubscriberNumber

G = 1–8M = 2–8X = 0–9Y = 0–1

PR = 32–39SL = 00–99

E-4 ________________________________________________________________________________________________ MCWP 6-22

of a circuit switched network. A four-digit PRSLswitch code within a network is also called a 4/3numbering plan, since the switch code is four dig-its and the subscriber number is three digits. The4/3 numbering plan is preferred in military circuitswitched systems since it allows for more circuitswitches with fewer subscribers as compared to acommercial switching system which uses a 3/4numbering plan. A commercial switching systemhas fewer switches with more subscribers, hencethe 3/4 code.

Interswitch DialingWhen calling a subscriber who is serviced by adifferent circuit switch (PRSL), the full seven-digit number must be dialed (PRSL-GXX). Butfirst, the circuit switch must be told that the num-bers dialed are PRSL numbers and not subscribernumbers. This is done with a one or two digit spe-cial “long-distance” or escape code. Some circuitswitches require a “9” or a “91” code prior to theseven digit subscriber number. This is analogousto dialing a “1” for long distance on a telephone athome or in the office. The number dialed will beeither—

9 - PRSL - GXX or

91 - PRSL - GXX

PRs will be assigned by the higher headquartersJ6/G-6, according to the Global Block NumberingPlan (GBNP) matrix found in CJCSM 6231.02.Some higher level switches in the military can usea 3/4 numbering plan, which uses a three-digitswitch code (NNX) called a local exchange code,vice a PRSL code. The full subscriber numberthen takes on the form NNXGXXX.

Subscriber Number (GXX)The subscriber number is a three-digit number be-tween 100 and 899. Every telephone instrumentthat is connected to a circuit switch, whether auto-matic or manual, must be assigned a number. All

subscriber numbers are listed together in the in-formation systems directory, which is publishedby the unit CIS officer prior to an operation.When one subscriber wishes to call another sub-scriber who is on the same circuit switch, he onlyneeds to dial the subscriber number (GXX).

Global Block Numbering Plan

The Marine Corps will begin using the GBNP inFY 99 to incorporate all of its switches into a jointnetwork. The GBNP will identify all of the ser-vices with a unique, service-managed block ofnumbers, simplify network management into aglobal network, ensure nonduplication of num-bers within an area of responsibility, and identifydatabases and subnetworks within the assignedblock of numbers. After implementing the GBNP,it is expected that a block of numbers (PRSLnumbers between 3200–3900) will be associatedwith each major subordinate command (MSC)and switch type. MSCs should coordinate withtheir respective preaffilation managers to deter-mine their subscriber numbers.

LAN Instructions

These instructions address how to use the secured(SIPRNET) and unsecured (NIPRNET) LAN. In-structions should describe all LAN services avail-able, including electronic mail, Internet access,message dissemination, and COMPUSEC.

Information Systems Listing

This listing provides tactical, commercial, DSN,host nation, pager, and cellular telephone num-bers for subscribers at every organizational loca-tion. It also provides subscriber’s SIPRNET andNIPRNET LAN addresses and any operationalwebpage addresses. The listing should include ad-jacent major organizations of other services in ajoint operation.


Section II

Sample II MEF Information Systems Directory

This section contains a representative information systems directory designed according to the prin-ciples outlined in section 1. This sample directory used II MEF as the notional unit. The directory,however, may not accurately reflect the actual composition of the present II MEF, nor does it list allof the potential subscribers to the system. CISOs should consult with the GBNP and their unit’s T/Osand SOPs before preparing a directory to ensure that subscriber numbers are accurate.

CLASSIFICATION

II MEF EXERCISE

INFORMATION SYSTEMS DIRECTORY Effective Date 210800Z October XXXX

EMERGENCY NUMBERS

TELEPHONE SECURITY IS EVERYONE’S RESPONSIBILITY. DO NOTDISCUSS CLASSIFIED INFORMATION ON NONSECURE TELEPHONES!OFFICIAL DOD TELEPHONES ARE SUBJECT TO MONITORING AT ALLTIMES FOR COMMUNICATION SECURITY PURPOSES.

CLASSIFICATION

Operator 000Combat Operations Center 3420-300Headquarters Commandant 3420-807Force Protection Platoon 3420-160

Telephone Help Desk 3421-613

LANHelp Desk 3420-605

E-6 ________________________________________________________________________________________________ MCWP 6-22

INDEX

EMERGENCY NUMBERS ..................................................................................................................GENERAL INSTRUCTIONS...............................................................................................................OPERATING INSTRUCTIONS...........................................................................................................DIALING INSTRUCTIONS.................................................................................................................PRECEDENCE SUBSCRIBERS ..........................................................................................................NUMBERING PLAN............................................................................................................................LAN INSTRUCTIONS .........................................................................................................................INFORMATION SYSTEMS LISTING................................................................................................

GENERAL INSTRUCTIONS

TASS allows most subscribers to place local and long distance telephone calls without operator as-sistance. By using the following instructions telephone service will be quicker and more responsiveto your needs. Use the following telephones with digital switching equipment:

TA-1042 Digital Non Secure Voice Terminal (DNVT). This is the ruggedized green push but-ton telephone. The LED will blink and a ring will be sounded when the phone receives a ring. Aknob located on the phone will adjust ringer volume. Ensure that the ear-piece is properly reinsertedinto the body of the phone after the call is completed. DO NOT use the push-to-talk switch on thehandset at anytime. This will disrupt your conversation.

KY-68 Digital Secure Voice Terminal (DSVT). This is the ruggedized green push button tele-phone. Once filled, the KY-68 holds the highest classification because of the COMSEC key loadedinside and must be handled accordingly. After the phone has received its crypto fill it requires no us-er adjustments other than adjusting the ring volume. ANY OTHER ADJUSTMENTS TO THE RE-MAINING CONTROLS MAY ZEROIZE THE TELEPHONE RENDERING IT INOPERATIVE.If this occurs notify the TELEPHONE TROUBLE DESK at 411.

SECTEL MMT 1500. This is the Motorola 1500 STU III in that it can be operated from a garrisontelephone or the tactical phone system. The MMT can talk unsecured to any type of phone on thetactical system (the MMT can only be connected to the tactical switch digital line termination unit(DLTU) with the DNVT adapter). The MMT can only go secure with another STU-III. The dialinginstructions for the MMT are the same as any tactical instrument on the network unless dialingthrough an IWF.

INTER-WORKING FUNCTION (IWF). This device allows tactical SECTEL MMT 1500 STU-IIIsubscribers to place secure calls to commercial STU-III subscribers. The IWF is programmed as aDNVT within the ULCS network and is direct access service (DAS) to the TTC-42 switch and con-nected to a single Dial Central Office (DCO) line. Access the IWF by dialing its tactical number froma SECTEL MMT 1500 STU-III within the tactical network, receiving a second dial tone (from DCO)and then dialing the commercial telephone number. Once this connection is made, both subscribersmay go secure.

The only way that commercial subscribers are able to go secure with tactical STU-III subscribers isby dialing through the IWF.


OPERATING INSTRUCTIONS

The KY-68 and the TA-1042 may receive and initiate calls with any telephone installed within the TASS.The KY-68 has some unique operation characteristics that are as follows:

● Under the handset of the phone is a 3 position pole type plunger which automatically sets itself in thesecure mode when the phone is hung up.

● All calls will be initiated in the secure mode; pick up the handset and dial the required number you de-sire.

● If the party you are calling does not have a secure voice telephone (KY-68), you will hear a continuousheartbeat sound in the receiver and the NSW (Nonsecure Warning) will flash. Simply pull up on theplunger and your phone will go to the unsecured mode. Note: The NSW light will remain until youterminate the call.

● The KY-68 will automatically reset itself to the secure mode when you hang up.

DSVT’s cannot talk secure with STU-III telephones. They are not compatible in the secure mode.

Access Through Defense Switched Network (DSN)

The II MEF TASS will have six DSN trunks available through the AN/TTC-42 switchboard. DSN use bysubscribers will be on “A FIRST COME, FIRST SERVED” basis. Precedence subscribers will have theability to preempt other subscribers when a precedence call is initiated.

DIALING INSTRUCTIONS

● To dial a tactical telephone number from your tactical phone, dial the following:

• AN/TTC-42 subscribers: Dial 9 and the seven digit extension (9-XXXX-XXX).

● To dial DSN telephone numbers aboard Camp Lejeune from your tactical phone, dial the following:

• AN/TTC-42 subscribers: Dial 5C (wait for tone)-451-XXXX-C. (XXXX = the four digit DSN num-ber) or dial for the operator at 000.

• SB-3865 subscribers: Dial 91 (wait for the tone)-5C (wait for the tone)-451-XXXX-C or dial the op-erator at 000.

● To dial a tactical telephone number from a DSN number or to dial a TASS Operator from a DSN num-ber, take the following steps:

• Dial the tactical switch operator at one of the following numbers: 6131 or 6174.

• Give the operator the seven digit number (PRSL-XXX) for the subscriber you wish to reach. Exam-ple: 3469-633.

Note: TASS subscribers with an assigned higher precedence may start the dialing sequence with theappropriate level precedence.

• If any problem occurs during the dialing process, call the operator by dialing 000 or for telephonetrouble calls within your switching network, dial the unit’s corresponding telephone trouble desknumber.

E-8 ________________________________________________________________________________________________ MCWP 6-22

PRECEDENCE SUBSCRIBERS

The tactical circuit switch (AN/TTC-42) is capable of processing five levels of precedence. The prece-dence levels in ascending order are—

ROUTINE (R)PRIORITY (P)IMMEDIATE (I)FLASH (F)FLASH OVERRIDE (FO)

The maximum precedence level authorized to a particular terminal is assigned by a classmark. The prece-dence indicator (P,I,F,FO) is dialed first in any dialing sequence. If no precedence is dialed, the call isprocessed as routine. Subscribers can initiate calls at a precedence level lower than the maximum autho-rized. Once a call is established, the originator’s precedence level is maintained, regardless of the levelauthorized to other participating parties. Preemption is employed to calls of higher priority are given pref-erence over lower precedence calls. Initiate the call with the assigned precedence, and the call will becompleted on a priority basis. Example: P600, F300, etc.

Note: When a priority is used it will disconnect any subscriber who has lower precedence. PLEASEUSE THEM WITH DISCRETION.

WARNING

Remember that the telephone network is NOT SECURE. Do not discuss classified material on anytelephone UNLESS YOU ARE USING A KY-68 OR A STU-III TELEPHONE IN THE SECUREMODE. Even calls made within the command post are susceptible to interception. Practice goodcommunications security!


NUMBERING PLAN

The Primary Zone (PR) is the primary identification number that identifies subscribers in the geographicarea.

Switch Location (SL) assignments are listed for all commands and organizations within II MEF and eastcoast units. Spare SL numbers are provided at different echelons and for task organization assignments.

The following PR and SL are assigned to II MEF units participating in the MEF Exercise:

PR SL

II MEF CE 34 20

EIGHTH COMM BN 34 21

2D FSSG 35 77

MED BN 35 80

8TH ESB 35 82

2D LSB 35 84

8TH MT BN 35 86

2D MAW/MWCS-28 DET B (CHRY PT) 35 27

2D MAW/MWCS-28 DET A (BOGUE FLD) 35 30

2D MAW (NEW RIVER) 35 32

2D MAW/MWSS-274 35 42

2D MAW/MWSG-27 35 36

2D MAW/MWSS-271 35 40

2D MAW/MASS-1 35 33

2D MAW/MWSS-272 35 41

2D MARDIV 34 69

2D MAR REGT 34 76

6TH MAR REGT 34 77

8TH MAR REGT 34 78

10 MAR REGT 34 79

2D TANK BN 34 88

2D AMPHIBIOUS ASSAULT BN 34 89

2D LAR BN 34 90

2D COMBAT ENG BN 34 91

E-10 _______________________________________________________________________________________________ MCWP 6-22

LAN INSTRUCTIONS

Disclaimer. The United States Marine Corps, while recognizing certain commercial products in this di-rectory, does not endorse any of the products listed here. Technology and the marketplace drive the prod-ucts that are available. The USMC will use the best technology or tool for the job at any given time.

LAN Overview

II MEF personnel will have access to both the nonsecure internet protocol router network (NIRPNET) andthe secure internet protocol router network (SIPRNET) during this exercise. NIPRNET and SIPRNET ad-dresses are located on the information systems listing at the end of this directory.

The overall LAN coordinator for the exercise will be the II MEF Assistant Chief of Staff G-6 InformationSystems Management Officer (ISMO), under the cognizance of the II MEF AC/S G-6. The ISMO will beassisted by communications and information systems officers and personnel at each of the Major Subor-dinate Commands (MSCs). LAN questions and problems should be addressed to the LAN help desk at3420-605.

II MEF personnel will be using a variety of computers loaded with Microsoft WindowsNT® networkand Exchange® software applications during this exercise. WindowsNT® is a multipurpose operatingsystem that integrates a variety of network services. The network services it provides are designed to ad-dress requirements in many categories. Windows NT® will be used to connect all of the units within theMEF.

Software Applications

II MEF computers have been installed with several software application packages, which includeMicrosoft Outlook® and Internet Explorer®, and Message Dissemination System (MDS).

Microsoft Outlook®. This application is used for all electronic mail applications, including calendar andscheduling features, and is accessed via the desktop icon.

Microsoft Outlook® is a desktop information management program that helps the user organize andshare information on your desktop and communicate with others. Use Outlook® to manage your messag-es, appointments, contacts, and tasks, as well as track activities, view and open files, and share informa-tion with others.

In Outlook®, information is organized in folders. When the user first starts Outlook®, the Inbox folderopens. Use the Inbox to read and send mail messages, meeting requests, and task requests.

To create a message, point to New on the file menu, and then click Mail Message. Enter recipient namesin the To and Cc boxes. Type the subject of the message in the subject box, and then type the message inthe text box. When you are ready to send the message, click Send.

To quickly go to another part of Outlook®, click a Shortcut on the Outlook® Bar to the left of the Inbox.For example, click Calendar to open your Calendar folder. The Folder Banner (horizontal bar above the

Communications and Information Systems _____________________________________________________________ E-11

information viewer) shows the name of the folder you have open. To see a complete list of your folders,click the folder name in the Folder Banner.

The user can use Outlook® as a substitute for Windows Explorer®. To view the files on the hard disk,click Other on the Outlook® Bar, and then click My Computer, My Documents, or Favorites.

Outlook® uses views to sort and organize items in a folder. To switch to a different view, click a view inthe Current View box on the Standard toolbar.

If Microsoft Word® is installed on a computer, use Word® and Outlook® together to create powerful e-mail messages. To turn Word® as your editor on or off, close this message and click Options on theTools menu. On the E-mail tab, select or clear Use Microsoft Word® as the e-mail editor. With MicrosoftWord® as your e-mail editor, you can use features such as autocorrect, spell it, bullets and numbering,document map, and highlighter to create your e-mail messages.

The Internet (MS Internet Explorer®). This application is used for all Web access and is accessed viathe desktop icon.

The Internet is a collection of computer networks that connects millions of computers across the UnitedStates and around the world. Explorer® enables the user to connect to the internet to gain access to vaststores of information on these computers. Double click on the Explorer® icon to access the internet.When a frequently used URL is typed into the Address bar, Explorer® will complete the address. In addi-tion, Explorer® can search through incorrectly typed addresses in order to find a match.

Users can search for web sites using the Explorer® bar. Click on the search button on the toolbar: the Ex-plorer® bar appears in the left side of the browser window. Then click on a link to view that page on theright side of the screen while viewing the list of search documents on the left. It is also possible tobrowse through favorite sites and history folders, channels, or documents.

Users can find information on the web in a variety of ways. When the search button is clicked on thetoolbar, the Explorer® bar appears to the left of the window. It provides access to a number of search ser-vices that offer different kinds of searching capabilities. To find information quickly, type GO, Find, or?, followed by a word or phrase right in the address bar. Explorer® immediately starts a search for thetopic. Then, after the user goes to a specific web page, the user can search for the specific text on thatpage.

Message Dissemination System (MDS). MDS has been installed on II MEF computers for this exercise.The primary function of MDS is the automatic dissemination of Organizational Automatic Digital Net-work (AUTODIN) messages to various organizational users as MD Users or E-Mail Addressees. This au-tomatic dissemination is based on the Office Code Distribution provided by the Originator of the messagein the form of Office Codes assigned to Plain Language Addresses (PLAs) in the heading of a message,and/or Profiles. Messages are made available to MD for processing either electronically via a GateGuardSystem or on diskette produced by a GateGuard, Personal Computer Message Terminal (PCMT), or othersystems using the standard message diskette format.

E-12 _______________________________________________________________________________________________ MCWP 6-22

LAN Security

The internet works by sending information from computer to computer until the information reaches itsdestination. When information is sent from one point to another, every computer in between has an op-portunity to look at what’s being sent. This can pose a security problem. Users must understand that clas-sified information must not be sent on unsecured networks. Users should practice good computer security(COMPUSEC) procedures while using the Internet.


II MEF Information Systems Listing

Effective Date: 210800Z October XXXX

Note: The tactical PRSL numbers listed below are based on a draft GBNP switch block proposaldated 26 Aug 98. CISOs are highly encouraged to check with their unit PAL managers before as-signing tactical numbers.

Subscriber Tactical Commercial DSN

E-MAIL ADDRESS

NIPRNETDomain:

SIPRNETDomain:

II MEFCMD ELEMENT3420 (TTC-42)

fwd.iimef.usmc.mil

fwd.iimef.usmc.smil.mil

CG 3420-106 (DSVT) 751-9475 cg@domain cg@domain

CELLULAR (910) 340-8230

C/S 3420-103 (DSVT)

HQ CMDT 3420-807 (DNVT)

SJA 3420-104 (DNVT)

PAO 3420-105 (DSVT)

SGT MAJ 3420-109 (DNVT)

G-1

AC/S G-1 3420-114 (DSVT) g1@domain g1@domain

PERSONNEL OFFICER 3420-110 (DSVT)

ADJUTANT 3420-112 (DSVT)

G-2


G-2 CHIEF 3420-209 (DSVT)

CIC WATCH OFFICER 3420-225 (DSVT)

COLLECTIONS OFFICER 3420-211 (DSVT)

TARGET OFFICER 3420-245 (DSVT)

RAD BN 3420-201 (DSVT)

CI 3420-211 (DSVT)

METOC 3420-240 (DSVT)

SARC 3420-242 (DSVT)

RECON OPS CENTER 3420-244 (DSVT)

G-3



COMBAT OPERATIONS CENTER (COC)

SENIOR WATCH OFFICER 3420-300 (DSVT)

FUTURE OPS OFFICER 3420-327 (DSVT)

AIR OPS OFFICER 3420-308 (DSVT)

E-14 _______________________________________________________________________________________________ MCWP 6-22

CSS OPS OFFICER 3420-405 (DSVT)

FFCC OFFICER 3420-340 (DSVT)

FIRES 3420-340 (DSVT)

TARGETING 3420-319 (DSVT)

EW PLANS OFFICER 3420-225 (DSVT)

CIVIL AFFAIRS 3420-105 (DSVT)

G-4



G-4 OPERATIONS 3420-403 (DSVT)

EMBARK 3420-404 (DSVT)

ENGINEER OFFICER 3420-405 (DSVT)

MEF SURGEON 3420-430 (DSVT)

G-5


DEP G-5 3420-501 (DSVT)


G-6


G-6 OPS OFFICER 3420-601 (DSVT)

G-6 OPS CHIEF 3420-602 (DSVT)

G-6 DATA OFFICER 3420-603 (DSVT)

G-6 COMM CHIEF 3420-603 (DSVT)

LAN/WAN TROUBLE DESK 3420-605 (DNVT)

MISCELLANEOUS

AID STATION 3420-155 (DNVT)

FORCE PROTECTION 3420-160 (DNVT)

8TH COMM BN3421 (SB-3865)

CO 3421-806 (DSVT)

XO 3421-807 (DSVT)

SGT MAJ 3421-808 (DNVT)

OPS OFFICER 3421-830 (DSVT)

OPS CHIEF 3421-931 (DSVT)

PERSONNEL OFFICER 3421-801 (DNVT)

BAS 3421-867 (DNVT)

BN OOD 3421-802 (DNVT)

SYSCON 3421-613 (DSVT) syscon@domain syscon@domain

TECHON 3421-623 (DSVT) techcon@domain techcon@domain

DATA COM 3421-633 (DSVT) datacom@domain datacom@domain


E-MAIL ADDRESS

NIPRNETDomain:

SIPRNETDomain:


2D MARINE DIVISION3469 (TTC-42)

fwd.2dmardiv.iimef.usmc.mil

fwd.2dmardiv.iimef.usmc.smil.mil

CG 3469-106 (DSVT) cg@domain cg@domain

G-1 3469-114 (DSVT) g1@domain g1@domain



G-4 3469-400 (DSVT) g-4@domain g4@domain

CELLULAR (910) 340-8235

TCO DIAL-IN 3469-675 (DNVT)


CELLULAR (910) 340-1014

DIVISION COMM COMPANY

CO COMM CO 3469-610 (DSVT)

TECHCON 3469-113 (DSVT)

OPS OFFICER 3469-149 (DSVT)

SYSCON (STU-III) 3469-669 (DSVT) 751-9265

SIPRNET to MEF 3469-330 (DSVT)

TSC-93 (GMF) (910) 451-9271

DASC (STU-III) (910) 451-9272

LONG LOCAL - MEF 3469-701 (DNVT)

LONG LOCAL - WING 3469-702 (DNVT)

TTC-42 (SWBD) 751-9470

2ND MAR REGT3476 (SB-3865)

CO 3476-106 (DSVT)

S-1 3476-114 (DNVT)

S-2 3476-200 (DSVT) 751-1014

S-3 (STU-III) 3476-300 (DSVT) 751-5263

S-4 3476-400 (DNVT)

S-6 3476-600 (DSVT)

6TH MAR REGT3477 (SB-3865)

CO 3477-675 (DSVT)

S-1 3477-200 (DNVT)

S-2 3477-300 (DSVT)

S-3 3477-662 (DSVT)

S-4 (FAX) 3477-400 (DNVT) 751-3977

S-6 (STU-III) 3477-600 (DSVT) 751-2822


E-MAIL ADDRESS

NIPRNETDomain:

SIPRNETDomain:

E-16 _______________________________________________________________________________________________ MCWP 6-22


CO 3478-106 (DSVT)

S-1 3478-114 (DNVT)

S-2 3478-200 (DSVT)

S-3 3478-300 (DSVT)

S-4 3478-400 (DNVT)

S-6 (STU-III) 3478-600 (DSVT) 751-2551


CO 3479-106 (DSVT)

S-2 3479-200 (DNVT)

S-3 3479-300 (DSVT)

S-4 3479-400 (DNVT)

S-6 3479-600 (DSVT)

2D TANK BN3488 (SB-3865)

CO 3488-106 (DSVT)

S-3 3488-300 (DSVT)

2D AMPH ASSAULT BN3489 (SB-3865)

CO 3489-106 (DSVT)

S-3 3489-300 (DSVT)

2D LAR BN3490 (SB-3865)

CO 3490-106 (DSVT)

S-3 3490-300 (DSVT)

2D COMBAT ENG BN3491 (SB-3865)

CO 3491-106 (DSVT)

S-3 3491-300 (DSVT)

2D FFSG3577 (TTC-42)

fwd.2dfssg.iimef.usmc.mil

fwd.2dfssg.iimef.usmc.smil.mil

CG (STU-III) 3577-106 (DSVT) cg@domain cg@domain







E-MAIL ADDRESS

NIPRNETDomain:

SIPRNETDomain:


H&S BN

CO 3577-706 (DSVT)

S-3 3577-703 (DSVT)

S-4 3577-704 (DNVT)

FSSG COMM CO

CO 3577-610 (DSVT)

OPSO 3577-149 (DSVT)

SYSCON 3577-633 (DSVT)

COMMERCIAL (STU-III) (910) 451-9609


SUPPLY 3577-720 (DNVT)

MAINT 3577-779 (DNVT)

COMMERCIAL (STU-III) (910) 451-9610

MD BN3580 (SB-3865)

CO 3580-706 (DSVT)

S-3 3580-703 (DSVT)

S-4 3580-704 (DNVT)

S-6 3580-600 (DSVT)

DENTAL BN 3580-604 (DNVT)

ENG BN3582 (SB-3865)

CO 3582-706 (DSVT)

S-3 3582-703 (DSVT)

S-4 3582-704 (DNVT)

S-6 3582-600 (DSVT)

LSB3584 (SB-3865)

CO 3584-706 (DSVT)

S-3 3584-703 (DSVT)

S-4 3584-704 (DNVT)

S-6 3584-600 (DSVT)

MT BN3586 (SB-3865)

CO 3586-706 (DSVT)

S-3 3586-703 (DSVT)

S-4 3586-704 (DNVT)

S-6 3586-600 (DSVT)


E-MAIL ADDRESS

NIPRNETDomain:

SIPRNETDomain:

E-18 _______________________________________________________________________________________________ MCWP 6-22

2D MAWCHERRY POINT3527 (TTC-42)

fwd.2dmaw.iimef.usmc.mil

fwd.2dmaw.iimef.usmc.smil.mil

CG 3527-106 (DSVT) cg@domain cg@domain






TACC “DET B”CHERRY POINT

SYSCON OFFICER 3527-113 (DSVT)


TSC-85 3527-185 (DNVT)

TSC-120 3527-120 (DNVT)

TSC-96 3527-196 (DNVT)

TRC-170 (MEF) 3527-170 (DNVT)

Long Local - MEF 3527-613 (DNVT)

MCWS 28 CO 3527-106 (DSVT)

MCWS 28 S-3 3527-103 (DSVT)

MCWS 28 S-4 3527-104 (DSVT)

MCWS 28 Maint 3527-115 (DNVT)

DET B OFFICE 3527-206 (DNVT)

DATA COMM 3527-230 (DSVT)

COMM CENTER 3527-111 (DSVT)

MSC-63 3527-211 (DNVT)

MTACS 28

SAC 3527-333 (DSVT)

CTAPS SYS ADMIN 3527-380 (DNVT)

SWO/SAC 3527-334 (DNVT)

DCN 3527-382 (DSVT)

ICO 3527-393 (DSVT)

TACC 3527-381 (DSVT)

2D MAWBOGUE FIELD DET “A”

3530 (TTC-42)


TTC-42 VAN 3530-555 (DNVT)

TECHON 3530-150 (DSVT)

CO 3530-106 (DSVT)

RADIO 3530-132 (DNVT)

WIRE 3530-131 (DNVT)


E-MAIL ADDRESS

NIPRNETDomain:

SIPRNETDomain:


DATA COMM 3530-129 (DSVT)

COMM CTR 3530-111 (DSVT)

MAINT 3530-115 (DNVT)

MACS-6 ATC SITE

ATC COMMON 3530-350 (DNVT)

FACILITY WATCH O 3530-351 (DSVT)

RADAR SUPERV 3530-352 (DNVT)

MACS-6 EW/C SITE

SAD 3527-330 (DSVT)

SID 3527-332 (DSVT)



NEW RIVERDET “A”

3532 (SB-3865)


SYSCON (SWO) 3532-213 (DSVT)

TTC-42 VAN 3532-150 (DNVT)

TECHON 3532-150 (DSVT)

CO 3532-106 (DSVT)

MASS-1 SUBSCRIBERS3533 (SB-3865)

SAC 3533-101 (DSVT)


SEC WAN 3533-103 (DSVT)

COMM USER 3533-104 (DNVT)

MAG-26NEW RIVER

3535 (SB-3865)

CO 3535-106 (DSVT)

S-1 3535-114 (DSVT)

S-3 3535-300 (DSVT)

S-4 3535-400 (DSVT)

S-6 3535-600 (DSVT)

HMLA-167

CO 3535-806 (DSVT)

S-3 3535-330 (DSVT)

MWSG 273536 (SB-3865)

CO 3536-806 (DSVT)

S-3 3536-803 (DSVT)

S-6 3536-800 (DSVT)


E-MAIL ADDRESS

NIPRNETDomain:

SIPRNETDomain:

E-20 _______________________________________________________________________________________________ MCWP 6-22

S-6 CHIEF 3536-801 (DNVT)



DATA 3536-804 (DSVT)

WXO 3536-805 (DNVT)

MWSS 2713540 (SB-3865)

CO 3540-506 (DSVT)

S-3 3540-503 (DSVT)

S-6 3540-500 (DSVT)

SYSCON 3540-501 (DNVT)

TECHON 3540-502 (DNVT)

WXO 3540-505 (DNVT)

MWSS 2723541 (SB-3865)

CO 3541-506 (DSVT)

S-3 3541-503 (DSVT)

S-6 3541-500 (DSVT)



WXO 3541-505 (DNVT)

MWSS 2743542 (SB-3865)

CO 3542-306 (DSVT)

S-3 3542-303 (DSVT)

S-6 3542-300 (DSVT)



WXO 3542-305 (DNVT)


E-MAIL ADDRESS

NIPRNETDomain:

SIPRNETDomain:

Appendix F

CIS Planning Checklist

The purpose of this checklist is to guide CIS plan-ning for joint operations. This checklist is derivedfrom Joint Pub 6-02, Joint Doctrine for Employ-ment of Operational/Tactical Command, Con-trol, Communications, and Computer Systems.This checklist is not all-inclusive. Questionsshould be revisited as CIS planners adapt to thechanging operational situation. The checklist pro-vides a framework for supporting CIS planningfor each phase of an operation, focusing CIS plan-ners on the mission and how the commander in-tends to accomplish it. CIS planners should alsobe familiar with relevant joint and naval TTP andhave access to pertinent publications and techni-cal manuals as well as CIS support organizations,including those listed at appendix P.

Reference Material

● Existing OPLANs and OPORDs

● Commander’s planning guidance, estimate, in-tent, and concept of operations

● Area studies

● Unit SOPs

● Joint Pub 6-0, Doctrine for Command, Control,Communications, and Computer (C4) SystemsSupport for Joint Operations

● Joint Pub 6-02, Joint Doctrine for Employmentof Operational/Tactical Command, Control,and Computer Systems

● Joint Pub 6-02.1, Joint Connectivity Handbook

● CJCSM 6230.03, Communications-ElectronicsOperations Instructions—Signal OperationsInstruction

● CJCSM 6231.01–6231.07A series, Manual forEmploying Joint Tactical Communications

● DISA Contingency Plan 10-95

● Joint Communications Support Element Plan-ning Guide

● Lessons-learned databases from previous oper-ations and exercises

● TPFDD and time-phased force deployment list

Planning Considerations

General● What is the MAGTF or unit mission?● What is the geographic operational area?● What are the commander’s intent, concept of

operations, planning guidance, and CCIRs?● What are the commander’s communications

and information systems requirements?● What are the JTF, naval expeditionary force,

MAGTF, and supporting elements’ task organi-zations? What are the command relationships?

● How will the forces deploy (means of transpor-tation), and what is the deployment timeline?

● Are there any transport and/or lift restrictions(availability of assets, departure and arrival lo-cations)?

● Are there any satellite landing rights?● When are the operations planning meetings

scheduled? How will CIS planning meetings fitinto this schedule? Has DISA been involved re-garding coordination of technical require-ments?

● Are there any planning constraints?● Are there any special CIS requirements? Who

has them?● What national space-based assets are required

and/or available to support the operation? Has aU.S. Space Command Joint Space SupportTeam been contacted?

● What communications capabilities are avail-able to the MAGTF: SHF and/or UHF com-mercial satellite, DSCS, and FLTSATCOM;

F-2 ________________________________________________________________________________________________ MCWP 6-22

military strategic and tactical relay system(Milstar) satellite terminals; JWICS and Mil-star; HF, VHF, and UHF radio; troposphericand line-of-sight microwave systems; local ar-ea, switched backbone, and router networks;DMS; DISN; and personal communicationssystems?

● What frequencies are available for the MAGTFin the operations area?

● What are the general INFOSEC requirements?Who will draft the callout message?

● Who is the potential adversary? What are theircapabilities to conduct offensive informationwarfare (IW)? Does a joint force plan exist tocounter the threat?

● What are the releasability requirements formultinational operations?

Subordinate Units● Where will their C2 nodes be located?

● What are their communications requirements(identify by function, C2 node/agency, andoverall unit priority)?

● What are their communications capabilities(identify by function, command and controlnode/agency, and overall unit priority)?

● What type of communications systems do theyhave (power, frequency bands, interoperableand compatible with other subordinate compo-nents’ equipment, mobility)?

● Who is the unit CIS officer (G-6 or S-6) staffpoint of contact for planning and technicalmanagement and direction?

● Are there any special CIS requirements result-ing from the mission and the commander’s esti-mate, intent, and concept of operations?

● Are subordinate and supporting CIS plans con-sistent with the supported commander’s CISplan?

Supporting Units● What is the mission of the supporting units and/

or activities (this includes other Services, agen-cies, allies, and coalitions)?

● What are their communications capabilities?

● What information does the supported MAGTFor unit need from the supporting units and/ oractivities (intelligence, weather, imagery, map-ping, deployment), and how will it be access-ed?

Nonorganic Support

DISA

● Does the operational area have a DISA Region-al Control Center or field office?

● Who is the DISA point of contact?● What is the DISN infrastructure in the opera-

tional area?● Are sufficient gateways available? What are the

interface requirements to access the gateways?Is the equipment available?

● Is the Telecommunications Service Provision-ing and/or National Security Emergency Pre-paredness authority provided and current?

● What are the anticipated DSCS and commer-cial satellite requirements?

● Has modeling of space networks been initiatedby DISA?

Commercial Networks

● Are commercial networks available for use?Who can approve access to them? Are fundsavailable? Has DISA been contacted to ensurerequired lead times for normal allocations? (1)Satellite (2) Data (3) Voice?

● What special interfaces are required to accessthe commercial network, and where are the ac-cess points?

● What are the locations and types of switches inthe commercial network? What are their tech-nical parameters?

● Where are the locations and types of systemsproviding the backbone transmission network?

● What type of power is used—voltage, current,commercial grid, or generator?

● Does the operational area have a cellular net-work? What are the transmission media, fre-quency band, and interface requirements? Whatare the system standards? Is the system avail-able for use?

Communications and Information Systems ______________________________________________________________ F-3

Chairman of the Joint Chiefs of Staff (CJCS)-Controlled Assets

● What CJCS-controlled assets are available?

● What capabilities are available?

● Will JCSE support be required in the operation-al area, or will other defense and commercialassets be sufficient?

● Will JCSE support be needed for en route com-munications?

● Has a Chairman of the Joint Chiefs of Staff In-struction (CJCSI) 6110.01, CJCS-ControlledTactical Communications Assets, support re-quest for CJCS-controlled C4 systems assetsbeen submitted?

● What are the JCSE’s logistics support and elec-trical power requirements?

● What are the JCSE airlift considerations, allo-cations, and/or priority?

Other Support

● Is support needed from specialized communi-cations units?

● Who are the points of contact, and what are therequest procedures?

● What are the unit’s communications capabili-ties and limitations?

Planning Activities

General Planning● What nodes will provide entry into the global

C4 systems network, and where will they be lo-cated?

● What transmission media will be used to con-nect the nodes?

● What types of CIS equipment will be located ateach node (equipment strings, interoperabilityof the equipment)?

● What are the frequency requirements for eachnode? How will the frequencies be allotted(joint, multinational, components, the MAGTF,and MSCs)? Are there potential frequency con-flicts?

● What are the call signs and/or words for eachnode?

● What units will provide, install, operate, andmaintain the equipment for each node?

● What lift assets are available to deploy theseunits? When will the units deploy and activatethe nodes or network?

● Is the deployment schedule of CIS assets con-sistent with the phases of the plan? Will it per-mit the provision of CIS support when andwhere needed?

● What is the phased buildup of CIS in the opera-tional area?

● Has CIS scheduling information been added tothe TPFDD and/or time-phased force deploy-ment list?

● Have the commander and principal staff offic-ers affected been informed of potential CISshortfalls and recommended solutions?

● How will keying material be managed (order-ing, generation, storing, distribution, transfer,and destruction)? What are the procedures forhandling compromises? Is a COMSEC logis-tics management activity needed in the opera-tions area? What access will allies have to U.S.COMSEC?

● Are network and node diagrams available?● Have special communications requirements

been addressed (MPF, shipboard, SAR, enroute communications, and embarkation anddebarkation connectivity)?

● Have SCI communications requirements beenidentified and satisfied?

● How will the joint, component, supportingforces, and MAGTF networks interface withnonorganic networks (DISN, commercial, andJCSE)?

● When and where will the joint, Marine Forces,or MAGTF communications control centers beestablished?

● Are the subordinate elements/units and sup-porting CIS plans consistent with the MAGTFCIS plan?

Detailed Planning

Circuit Switches

F-4 ________________________________________________________________________________________________ MCWP 6-22

● Does a circuit switch network diagram existthat shows information about the switch andcircuit switch network connectivity (switchtype, area code, trunk groups, and capacity)?

● How does the switch route calls: flood, deter-ministic, or circuit switch routing task execu-tion plan?

● Where do circuit switches need to be located?How will they be connected?

● What special features or restrictions will be im-posed on subscribers? Who will authorize andenforce these restrictions?

● Where are the DSN interfaces? Are precedenc-es authorized? By whom?

● How will subscriber assistance be handled?

● Where is the greatest anticipated traffic load:for GENSER? for SCI? Does sufficient capaci-ty exist to handle these?

● What types of status reports are required, andwhen will they be submitted?

● How will traffic metering and network loadingbe measured, modeled, and managed?

● Who will publish telephone directories, andhow will they be distributed?

Data Networking

● What are the anticipated MAGTF or unit datarequirements?

● Has automation been planned and/or engi-neered into the network (x.25, IEEE 802.3,TCP/IP)?

● What and/or where are the network identifica-tions and gateways?

● Will data of various classifications “ride” a se-cure tactical backbone? How will traffic of var-ious classifications be controlled and managed?Are multilevel information systems securityinitiative devices needed, and are resourcesavailable?

● What is the data network architecture?

● Who are the data network managers?

● What are the NIPRNET, SIPRNET, andJWICS connectivity requirements?

● What STEP sites will be used? Has a gatewayaccess request been submitted in accordancewith DISA contingency and/or exercise plans?

● What is the addressing scheme?

● Where do the IP addresses come from?

● Will the IP addresses have to be changed whenelements of the MAGTF go ashore?

● What is the scheme for sorting out routerloops?

Message Switches

● Where are the message switches required?

● What is the trunking plan?

● What is the network connectivity of all mes-sage switches?

● Have routing indicators been developed androuting tables established?

● Is this an R and/or Y network?

● Has a plain language address directory beencreated?

● How will special category traffic be handled?Who will be authorized to have access?

● What are the intranodal and internodal termi-nals?


● What AUTODIN switching centers are con-nected to the message switch?

● Who is the automated message processing sys-tem security officer?

● Who will act as the AUTODIN controller?

Transmission Systems

● Are the circuit requirements, routing, channel-ization, and other parameters that were identi-fied in high-level planning valid? Have satelliteaccess requests been submitted? Have frequen-cy requests been approved and published?

● What are the characteristics and connectivity ofmultiplexers in the network? Are they compati-ble?

Communications and Information Systems ______________________________________________________________ F-5

● What are the timing requirements for the net-work components? How will timing be accom-plished?


Technical Management and Direction

Joint, Marine Forces, and/or MAGTF Communications Control Centers● What are the operational procedures for the

control centers?● Where are the joint, Marine Forces, and/or

MAGTF control centers located?● How will the control centers be manned?● What reports will be required, how often will

they be required, and when will they be submit-ted?

● How will network reconfiguration be accom-plished?

● Who are the points of contact at the subordinatecontrol centers?

● Who will submit the telecommunications ser-vice request (TSR) and telecommunicationsservice order (TSO)? Have TSRs/TSOs for SCIcommunications requirements been incorporat-ed?

● Who will coordinate changes to connectivitywith the DISN? With the commercial net-works?

● What kind of statistics will be kept? Who willanalyze them? What will be done with them?

● How will changes caused by the evolving tacti-cal situation be handled?

● Can the JCCC direct changes within MAGTFnetworks to optimize C4 systems within thejoint operations area?

● Where is the boundary between technical direc-tion and operational direction?

● How will frequency deconfliction be managed?How can potential conflicts be anticipated?

● Who will control frequency spares and autho-rize their use?

● Who manages the allocated satellite bandwidthused by the geographic joint forces?

JCSE● Is JCSE support required?● Who is the JCSE point of contact?● How is support requested?● How will JCSE participate in the technical

management process?● Are there any special reporting requirements

for systems provided by the JCSE?

Spectrum Management

● What are the provisions and procedures for fre-quency planning and use for opposed and/orunopposed entry operations into an operationalarea?

● What frequency allotments and assignments areavailable for the operational area?

● Can the allotted and assigned frequencies sup-port the equipment deployed to the operationalarea (communications, LANs and/or WANs,sensors, surveillance radars, GPS, and airspacecontrol radars)?

● Will the frequencies work (propagation and to-pographic analyses)?

● Does the allocation and assignment of frequen-cies to subordinate commands contribute tomission accomplishment?

● What are the enemy capabilities to intercept,radio direction find, jam, or otherwise exploitor degrade MAGTF allotted and assigned fre-quencies? Does a joint and MAGTF plan existto counter the threat?

● Will the JCCC resolve electromagnetic inter-ference issues? Will Joint Spectrum Centersupport be required to resolve interference is-sues?

● Who will issue the Joint Restricted FrequencyList?

F-6 ________________________________________________________________________________________________ MCWP 6-22

● Are sufficient spare frequencies available?

● What EMCON measures will be applied?

● Will the MAGTF implement an electronic de-ception plan? Are sufficient frequencies avail-able to support this plan?

Security

● Will the cryptographic equipment interoperate?

● What are the keying material requirements?

● Does a key management plan exist?

● How will cryptographic compromises be de-tected and corrected?

● What INFOSEC measures will be employed onthe LANs and WANs in the operational area?

● How will access to the various networks becontrolled (electronic and physical)?

● Have COMSEC and INFOSEC emergency de-struction procedures been established?

● What is the logistics plan for the cryptographicequipment?

● Are equipment and keymat sufficient to sup-port planned and unplanned operations?

● Have key change times been established andpromulgated?

● Have provisions been made for over-the-air re-keying where applicable?

● Is an intertheater communications plan avail-able? Is it needed?

● What will we transition to and when?● What is the IW threat?● Are virus-detection software applications in-

stalled and operational? Are passwords issuedand in use? Has a contingency plan been devel-oped to guide recovery actions should data bemodified or destroyed by unauthorized intru-sions?

● Do remotely accessed computer systems pos-sess features to identify users and substantiatetheir identification before allowing informationto be processed?

Appendix G

Unit Planning Checklist

The following checklist is provided to assist CIS planners in conducting operationalplanning. It is oriented toward detailed unit planning from a CIS perspective. Thischecklist is based on the 6-Step Marine Corps Planning Process (MCPP) published inMCWP 5-1 (draft). Rather than reiterate the specific subcomponents of the 6-StepMCPP, the reader should refer to MCWP 5-1 and comparatively analyze thought pro-cesses which may assist in the design of the overall CIS architecture(s) which supportone or more courses of action (COAs).

The recommendations which follow may not be complete, depending on the level ofplanning, the time allocated for planning, and most importantly, the commander’s in-tent. As with any collaborative planning, the MCPP may not always appear sequen-tial (e.g., 1, 2...6) when actually being executed. With these thoughts in mind, theconsiderations provided below apply to each step, but are not necessarily limited toany specific step. This is because the operational planning team (OPT) must remainfocused on the commander’s intent—and supporting it—throughout all levels ofplanning.

Step 1, Mission Analysis

During this step, it is essential that the CIS plan-ner develop a thorough understanding of the mis-sion and the commander’s intent, as well as thesituation. Included in this step are—

● Commander’s initial orientation.

● Staff analysis—the CIS planner may begin toconsider some of the following:

• Connectivity.

■ JTF HQ? MARFOR HQ? What is theMAGTF composition?

■ Links to MSCs; again, MAGTF composi-tion?

■ Strategic high-capacity links—are theserequired?

■ What special capabilities may be re-quired to support special circuits?

■ Is bandwidth adequate?

■ MUX, SCR, what is the operationalstate—transitional (mobile) or consolidat-ed (more static), and how may we supportthis?

■ Interoperability—like all CIS planning thekey planning considerations (flexibility,survivability, etc.); the CISO should con-sult the CJCSM 6231.07A to determine ifequipages involved in the operation are in-teroperable.

• Coordination—as soon as feasible, plan andconduct an initial planning conference forCIS personnel (to include adjacent and sub-ordinate unit G-6/S-6s) in order to begin ef-fective, concurrent planning. Coordinate allissues as they can be developed. Determinemid-term planning conference as applicableto update all personnel involved in the plan-ning with the latest revisions and command-er’s intent.

• Intelligence preparation of the battlespace(IPB). As with all members of the staff, IPBshould be constant throughout the planning

G-2 ________________________________________________________________________________________________ MCWP 6-22

process. Some initial considerations in-clude—

■ Location/distances with respect to the ene-my; what terrain studies are available?

■ Begin analysis of the topography and en-vironment in which CIS systems must op-erate. Consider also time of year (TNAPS+ databases can begin to be built, notionalat this point, and/or SPEED can be used toassist in this initial analysis of the area ofoperation).

■ Electronic emissions, communications se-curity (COMSEC), computer security(COMPUSEC) and physical security is-sues must be formulated from the initialplanning. What are enemy and friendlyelectronic warfare (EW) capabilities?

■ Ensure a thorough understanding of theenemy’s location and situation. Possiblenode and retransmission sites must beconsidered in light of the enemy situation.

● Warning order.

Step 2, COA Development

The CIS planner should consider all factors thataffect the exercise of C2. These factors includemission, allocated forces, supporting communica-tions units and equipment employment sites, andjoint/MAGTF user requirements. Finally, developalternative approaches to satisfy C2 requirements.

● Determine desired end state; some specific CISconsiderations may include—

• Asset availability; what units are available tosupport the current COA?

• Personnel availability; what personnel canbest provide mission support to the COA?

• Tempo of the operation; in addition to mo-bility factors, how do all of the battlespacefunctions factor in which must be supportedby CIS systems?

• Synchronization of C2 with maneuver andall warfighting functions mobility of the CISassets and personnel?

• Provision for link or circuit activation—speed of support vs. reliability of the link orcircuit must be weighed; priority ALWAYSrests with the commander.

• Force protection; how do CIS units and per-sonnel support force protection?

• Logistics considerations; provision of sup-port must be matched by effective consider-ation of the logistics plan.

• IPB results; IPB is continuous, and the ene-my situation as it develops must be in theCIS planner’s mind.

● Develop measures of effectiveness (MOEs).

● Develop COAs to achieve end state.

● Present COA brief.

● Obtain approval of COAs for further analysis.

Step 3, COA Analysis

The CIS planner must analyze all alternatives todetermine advantages and limitations of each.

● Commander provides guidance.

● Staff wargames each COA.

● Staff briefs each COA.

• Wargame results.

• Staff estimates of supportability.

■ Feasibility of all alternatives to supportthe COA?

■ Adequacy of all means to support theCOA?

■ Acceptability of mediums and capacities(links, circuits, etc.) to the commander?

■ Supportability of the CIS plan for theCOA; does it best enable the commander toexercise C2? What are the commander’scritical information requirements (CCIRs),

Communications and Information Systems ______________________________________________________________ G-3

and how may each link/circuit providethem?

■ Assumptions with regard to availability ofassets and personnel; identify and recon-cile all of these with the commander.

■ Limitations; the estimate of supportabilityshould identify for the commander andstaff what these may be.

■ Constraints/restraints; how do they affectthe design and implementation of the CISplan?

Step 4, COA Comparison and Decision

Selecting the best COA relies heavily on the de-velopment of the COA by staff elements; it is atthis point that the CIS planner assists the com-mander and staff in COA comparison by recom-mending the best option.

● Commander evaluates and compares COAs.

● Commander decides on the COA to be used.

● New warning order issued.

• Commander’s concept of operation.

• Updated commander’s intent.

• Complete description of the chosen COA.

■ Supporting concepts; the CIS plannermust begin immediately to resolve anyshortfalls anticipated. At this point, thelimitations which have already been iden-tified by the CIS planner must be reducedor overcome in order to support the com-mander’s ability to exercise C2.

■ Task organization.

■ Refined CCIRs.

■ Staff estimates.

■ Coordination—the CIS planner should en-sure that final coordination with all re-spec t ive G-6s /S-6s (or des ignatedrepresentatives) is completed prior toorders development. During the planning

phase, coordination of a final planningconference and a technical control confer-ence will enable key coordination effortsto take place, and a more detailed plan forsupport can be prepared by all supportingunits/agencies.

Step 5, Orders Development

Prepare the Annex K, refine the plan continuous-ly, and continue liaison with the staff and thecommander. In this step, the staff will refine theselected COA into an OPORD together with sup-porting documentation. Much of the required in-formation will have already been developed in theprevious steps of the planning process. Thechecklists below identify specific areas to be ad-dressed in the OPORD.

The first list should be checked as soon as youknow your mission, while the second containsitems to be addressed after receipt of a warningorder. Many of these areas will need to be ad-dressed several times throughout the planning andduring execution. Bear in mind that planning foran operation/exercise is different from planningfor a contingency. The checklists on the followingpages are to help guide you.

Items to be Initiated Well in Advance of Warning Order Receipt

*These items require continuous action beforeand during the operation.

Communications

● Review senior HQ operation plan/letter of in-struction.

● Identify command relationships and relatedconnectivity requirements (both GENSER andSCI).*

● Request maps of area of operation.

● Determine equipment requirements.*

● Conduct map, weather, terrain analysis.*

● Conduct C2 threat assessment. (See app. K.)

G-4 ________________________________________________________________________________________________ MCWP 6-22

● Conduct site or map reconnaissance and IDpossible CP locations.*

● Conduct SPEED/sight analysis tools/JointSpectrum Center studies.

● Request frequencies/net IDs/call signs.

● Submit UHF satellite request (CUDIXS).

● Submit SHF/GMF satellite access request.

● Identify AUTODIN requirements.

● Submit telecommunications service requests(both GENSER and SCI).

● Recommend/coordinate w/S-3 on CP layout.

● Identify retransmission/relay/remote locations.*

● Determine security requirements for communi-cations assets (both GENSER and SCI).

● Coordinate messenger communications opera-tions and procedures with the unit G-1/S-1.

● Review SYSCON procedures.

● Identify communications reporting procedures.

● Prepare and distribute radio guard chart.

● Prepare and distribute IP address chart.

● Prepare circuit switch traffic diagram.

● Provide senior HQ with CEOI/automatedCEOI/telephone directory.

● Conduct ship visit (see app. C) as soon as pos-sible.

● Present predeployment briefing to staff/subor-dinates.

● Publish communications-related safety remind-ers.

● Prepare for special operations if required.

● Conduct predeployment training.

● Assess environmental impact on communica-tions.

● Review appropriate publications.

● Ensure that subordinate units understand com-munications guard shift procedures.

● Prepare/submit communications guard shift inaccordance with NTP 4, Naval Telecommuni-cations Procedures—Fleet Communications.

Maintenance

● Verify an equipment repair order matrix.

● Determine repair parts requirements (preex-pended bin, class IX block, stocks).

● Review/establish maintenance procedures.

● Check force activity designator status.

● Determine technicians required.

● Update the equipment repair order priorities onmission-essential equipment (Marine CorpsBulletin 3000).

● Update priorities on modifications and calibra-tions.

● Determine availability/need for mobile mainte-nance teams.

● Prepare necessary publications for embarka-tion.

● Conduct liaison visits with support agencies.

● Update temporary loan paperwork.

● Determine status of type I, II, and III items.

● Determine MPF asset availability.

● Prepare tools/equipment (test, maintenance, anddiagnostic equipment).

● Conduct limited technical inspections.

● Update preventive maintenance actions.

● Determine availability of maintenance facilities.

CMS/Classified Materials Control Center/Security

● Establish list of authorized users.

● Determine keying material requirements.

● Acknowledge satellite access authorization.

● Determine CMS start and changeover times.

● Determine requirement for safes.

● Determine requirement for cables.

● Issue security reminder to all users/staff (two-person integrity).

● Prepare input for C2 protection and deceptionplan.

● Establish message handling procedures.


● Determine hardware requirements.

Items to be Initiated After Receipt of a Warning Order

Communications

● Issue fragmentary/warning order to subordinateunits and issue initial CIS guidance to support-ed principal staff officers.

● Assemble staff to begin detailed planning.

● Submit equipment augmentation request.

● Weatherproof equipment.

Maintenance

● Conduct operational checks.

CMS.

● Issue CMS callout message.

● Ensure that CMS equipment is distributed.

Administration

Personnel Equipment Requirements

● Helmet.

● Flak jacket.

● H-harness.

● Cartridge belt.

● Two canteens with covers.

● Two magazine pouches.

● Six M-16 pouches.

● Weapon (with cleaning gear).

● Chemical protective gear.

● Gas mask.

● E-tool.

● ALICE pack (with frame).

● Flashlight (red lens).

● Bayonet/K-bar.

● Ear plugs.

● Shelter half (with five pins, three poles, andguy line).

● ISO mat.

● Waterproof bag.

● Sleeping bag.

● Poncho and poncho liner.

Uniform Requirements

● Cammies.

● Cammie cover.

● Physical training gear (green/green, gray/gray,running shoes, white socks).

● Field jacket with liner.

● Watch cap.

● Gloves with inserts.

● Rank insignia.

● Combat boots.

● Boot bands.

● Web belt with buckle.

● Cold-weather underwear (top and bottom).

● Wet-weather top.

● Wet-weather bottom.

● Skivvie bottoms.

● T-shirt.

● Socks.

● Civilian clothes.

● Towel (green).

● Washcloth (green).

● Shaving kit.

● Foot powder.

● Boot polish and brush.

● Sewing kit.

Personnel Administrative Requirements

● Determine personnel requirements.

● Ensure that security clearances are complete.

● Identify advance, main, and rear parties.

● Make advance party assignments.

G-6 ________________________________________________________________________________________________ MCWP 6-22

● Submit request for personnel augmentation.

● Determine billeting requirements.

● Duplicate records (service record book, health,dental,).

● Ensure that visas/passports/drivers licenses(Status-of-Forces Agreement) are current.

● Ensure that basic clothing is servicable/marked.

● Ensure that direct deposit is established.

● Ensure that powers of attorney are completed.

● Ensure that wills are completed/updated.

● Check dental (class I or II) status.

● Check dependent care arrangements.

● Obtain key volunteers phone list.

● Ensure that mail (forwarding address) form iscomplete/submitted.

● Ensure that Marines understand the followingprocedures/programs:

• Family assistance.

• Red Cross.

• Casualty assistance.

• Legal assistance.

• The Soldiers and Sailors Relief Act.

● Ensure that TRICARE/DEERS information isupdated and correct.

● Ensure that allotment to spouses/split pay is ar-ranged.

● Ensure that dependent ID cards are currentthrough date of return from deployment.

● Ensure that custody of children for single par-ents is legally established.

● Establish personnel database:

• Name, rank, SSN, MOS.

• Security clearance.

• Meal card.

• Weapon number.

• Section.

• Blood type.

• ID tags/cards.

• Next of kin.

• CPOG, gas mask size.

• Uniform, boot size.

• Updated record of emergency data (RED).

• Messman requirements.

• Corpsman request.

• Armory draw.

• Recall roster.

• Security for personal effects (supply).

• Banks/credit unions.

• Mortgage/deed of trust/financial obligations.

• Leases.

• Outstanding bills (address of creditors).

• Insurance coverage.

• Safe deposit box.

• Automobile storage.

• Storage of household goods.

• Right to vote.

• Memberships and subscriptions.

Logistics

Embarkation

● Determine equipment requirements.

● Determine logistical support requirements.

● Identify hazardous materials (HAZMAT) andstorage/disposal procedures.

● Prepare personnel and equipment for embarka-tion.

● Obtain shipping lists.

● Identify and label embarkation boxes.

● Submit equipment density list (broken down byship or transport relay).

● Determine transportation requirements (person-nel).

● Waterproof materials.


● Prepare embarkation list for each box.

● Provide air and surface transport support equip-ment (height, length, weight, cube).

● Determine material handling equipment re-quirements (forklift/crane).

● Inspect vehicles, generators, HAZMAT.

● Prepare staging schedule (TPFDD).

● Prepare 463L pallet request/inventory (checkfor proper straps).

● Submit MilVan/ConEx/QuadCon requests.

● Determine requirement and understand proce-dures for HAZMAT, packaging, handling, stor-age, transportation, etc.

Supply

● Block of materials request.

● Camouflage netting requirements.

● Tentage.

● Cots.

● Field desks/tables/chairs.

● Meals, ready to eat (MREs).

● Training allowance pool gear.

● Batteries.

● Wire.

● Sandbags.

● Plastic.

● Flooring.

● Heaters.

● Schedule.

Utilities

● Determine power requirements.

● Submit generator (and operator) requests.

● Conduct generator operator license training.

● Provide light bulbs.

● Provide drip pans/fuel drums.

● Determine mobile electric power distributionsystem cabling/harness requirements.

Motor Transport

● Conduct HMMWV/five-ton license training.

● Determine convoy route.

● Submit vehicle and driver assignments (consid-eration: command group drivers).

● Determine convoy composition.

● Establish convoy communications/control pro-cedures.

● Determine requirement for vehicle placards.

● Determine fuel requirements (petroleum, oils,and lubricants).

● Determine requirement for trip tickets.

Step 6. Transition

The last step in the MCPP is transition of theOPORD from the planners to the executors (at theMEF level, from future operations to current op-erations). The planning, decision, and executioncycle continues with planners responding to thedeveloping situation and with new or revised mis-sions.

(reverse blank)

G-8 ________________________________________________________________________________________________ MCWP 6-22


Appendix H

Data Communications Networkand

Information Systems Planning Checklist

Gateway Access Coordination

● Determine bandwidth requirements (over 32kbps will require special coordination).

● Incorporate request for NIPRNET/SIPRNET/JWICS into satellite access request.

• MEF IP networks to be used.

• Router type.

• Encryption device.

• Data rate.

• Exterior routing and encapsulation protocol(i.e., BGP4/EGP and PPP/HDLC).

● Ensure standard gateway COMSEC (ICPUSKAT: C5573).

● Coordinate/confirm KG-84A/C front-panel set-tings with gateway.

● Contact DISA, per mission directive, 7–10 daysbefore scheduled activation to confirm IP ad-dressing and routing information.

● Coordinate with the local information office, inconjunction with MEF G-6, to establish a NI-PRNET server-to-server connection.

MEF WAN Requirements

● Determine the number of subordinate/adjacentcommands/units requiring serial port router ac-cess.

● Determine appropriate router type.

• CISCO 4000 (two serial/four Ethernet)

• CISCO 7010 (eight serial/six Ethernet)

● Identify transmission system links to be used insupport of data networks, in conjunction withcommunications battalion/squadron systemsplanning and engineering staff and the G-6.

● Identify data rates to subordinates.● Determine the interior routing and encapsula-

tion protocol to be used with subordinates (i.e.,IGRP/OSPF and HDLC/PPP).

● Determine autoroute tables and related require-ments for all JMCIS workstations.

● Determine CSU/DSU unit leased-line require-ments.

● Determine the number of hosts (MEF CE) thatrequire an IP address (UNIX TDS workstationsand PCs configured as IP clients).

● Determine the appropriate IP subnet mask to beused.

● Design a detailed IP data network for NIPR-NET, SIPRNET, and JWICS (MEF CE will pro-vide IP addresses for MEF/subordinate IPinterface).

● Determine the COMSEC keymat to be used(generally will use same as gateway).

● Coordinate DNS access/use, if required.

LAN Requirements

● Determine the number of PCs to be connected toeach network.

● Determine the number of services required.● Determine the number of TDSs to be connected

to SIPRNET (e.g., GCCS, IAS, TCO, CTAPS,etc.).

● Identify the geographical area that the MEF CEwill use (tents, buildings, or trailers) and thephysical separation/distance between sections.

H-2 __________________________________________________________________________________________________________________________________________________________ MCWP 6-22

● Determine cabling and connector requirements(RG-58, fiber optic, thick Ethernet, BNC con-nectors, terminators, T connectors).

• RG-58: maximum distance, 185 m.

• Thick Ethernet: maximum distance, 500 m.

• Fiber optic: maximum distance, 2.5 milesmulti-fiber, 10 miles single fiber.

● Determine the number of repeaters required.(The number depends on the physical layout ofthe CE and number of PCs/laptops/TDSs.)

● Determine the number of servers required. (Thenumber depends on applications: Plan for 1server per 35 users when message distributionsystem (MDS) is being used.)

● Design a detailed LAN diagram with appropri-ate cable segments, repeater, routers, servers,TDSs, and IP clients identified.

● Determine server application requirements(e.g., MDS, e-mail, etc.).

● Determine the number of LAN dial-ins requiredand the type of interface (i.e., KY-68, STU-III,Hayes Modem).

● Determine the concept of operations for INFOS-EC monitoring and analysis, and initiate neces-sary support requests.

Logistic and Personnel Planning

● Determine block of materials requirements onthe basis of requirements and preliminary plan-ning, and submit 45–60 days before deploy-ment.

● Determine embarkation requirements, includ-ing shelters to be used (height, weight, width,length), on the basis of equipment requirementsand geographical location.

● Submit appropriate log requests for lifting andtransporting shelters or pallets (if required).

● Determine power distribution and grounding re-quirements.

● Determine power requirements (generally, 15kW, 120 V, 60 Hz).

● Determine the number of personnel required tosupport the exercise/operation. Keep in mind:

• WAN monitoring/maintenance will general-ly require two Marines per shift.

• The help desk will generally require one Ma-rine per shift.

• LAN troubleshooting will generally require1 Marine per 35 computers per shift.

• 24-hour operations require 12-hour shifts.

• Duration of exercise/operation will affectpersonnel requirements.

● Submit COMSEC request to CMS.

● Coordinate priority DSN/INMARSAT accessfor initial SIPRNET/NIPRNET/JWICS installa-tion.

● Coordinate one AN/GRA-39 per shelter. (Whenusing HMMWV-mounted shelters, arrange fortwo.)

● Coordinate separate J1077 (J-box)/26-pair ca-ble for data serial connections for each shelter(reduces conflicts with wire/telephone connec-tions—recommended when supporting multi-ple serial line connections).

Network Management

● Coordinate IP address management in conjunc-tion with principal staff officers and higher/ ad-jacent/subordinate unit communications andinformation systems officers.

● Create appropriate user accounts in accordancewith Marine Corps and MEF standards, per G-6input.

● Implement a virus management plan in conjunc-tion with the G-6.

● Implement an automatic data processing securi-ty plan in conjunction with the G-6.

● Implement an internet access policy in conjunc-tion with the G-6.

Communications and Information Systems_____________________________________________________________________________________________________ H-3

Preexercise Equipment Preparation

● Identify the equipment required to support theexercise/operation.

● Configure and test servers (see Server Checkliston page H-4).

● Configure and test routers and repeaters (seeRouter/Repeater Checklist on page H-5).

● Confirm proper crypto strappings.● Inspect and test all KG-84 red and black side ca-

bles.● Configure and test all CSU/DSU modems and

cables.

● Preconfigure and bench test equipment string.

● Coordinate a data communications pretest/con-figuration exercise with subordinate units, iffeasible.

● Ensure that all application, diagnostic, and serv-er software is loaded on each server and on dis-kette (two copies), tape, or compact disk (CD).

● Ensure that all UPSs are tested.

● Ensure that all network and router managementPCs/laptops are configured and tested properly.

● Ensure that all equipment is embarked in a man-ner that will minimize equipment damage.

● Ensure that appropriate backup equipment istested and embarked.

H-4 __________________________________________________________________________________________________________________________________________________________ MCWP 6-22

SERVER CHECKLIST Date______________

Server serial no._________________ Server key no._____________________ Server name____________________

Server console password________________ Sys admin account name: SysAdmin*___________________________

Password_______________ Processor (min. 486)_____________________ RAM (min. 16 Mb)________________

Hard disk size (min. 500 Mb): No. 1_____ No. 2_____ No. 3_____ Tape backup unit__________________________

Network interface cards andintelligence communication adapter: Services created:

Slot Type/Maker IRQ I/O Address RAM Address Init. Started Type Name

____ ___________ ____ ___________ ___________ ____ Started File SHARED FILES*

____ ___________ ____ ___________ ___________ ____ Started File DATACOMM SHARED FILES*

____ ___________ ____ ___________ ___________ ____ Started ISMTP ISMTP*

____ ___________ ____ ___________ ___________ ____ Stopped STDA SATELLITE STDA*

____ ___________ ____ ___________ ___________ ____ Stopped Print SHARED PRINTER*

Server options: Software installation (each program loaded and tested):

Init. Version No. On SHARED FILES*

____ VINES operating system Init. Version No. License No.

____ Server-to-server LAN ____ Lotus SmartSuite (LAN user)

____ Server-to-server WAN (HDLC) ____ MTF Editor

____ PC print ____ MDS

____ Asychronous dial-in ____ VDS

____ Asynchronous terminal emulation ____ MCLLS

____ Mail service ____ JULLS

____ Network management On DATACOMM SHARED FILES*

____ VINES assistant toolbox ____ MS-DOS

____ TCP/IP routing ____ Windows

____ TCP/IP server to server ____ ProComm Plus

____ Incognito simple mail transfer protocol(ISMTP) (software only)

________

3 Com Etherlink II Diag3 Com Etherlink III Diag

____ Incognito domain name server(software only)

________

PCtoolsSuperTCP for Windows

Server accessories: Hardware test verification:

Init. Init.

____ Power cable (CPU, monitor, printer, router) ____ Each network interface card tested with a client PC

____ UPS ____ Intelligence communication adapter tested (each port)

____ ICA cables ____ Floppy drive tested

____ Surge protectors (2) ____ Tape backup tested and verified

____ Extension cord (15 ft. or more) ____ Platform diagnostics run

____ Printer ____ Last second echelon preventive maintenance ______________

____ Printer cable Next scheduled second echelon preventive maintenance_______________

____ Printer ribbons/toner cartridge *@servername@servers____ Blank option key

____ Server software/CD-ROM

Communications and Information Systems_____________________________________________________________________________________________________ H-5

ROUTER/REPEATER CHECKLIST

Router CISCO 4000/7010

Serial no.__________________ Router name/no.____________________ Router password________________

Software version no._______________ Router configuration printed and attached___________________(initials)

Router hardware verification(each port must be tested)

Ethernet transceivers and AUI cables(test each)

Init. Init. Serial no.

____ Serial 0 ____ Ethernet 0 ____ One transceiver per router/repeater port ____________

____ Serial 1 ____ Ethernet 1 ____ One AUI cable per router/repeater port ____________

____ Serial 2 ____ Ethernet 2 ____ Five backup transceivers/AUI cables ____________

____ Serial 3 ____ Ethernet 3




____ Serial 7 Ethernet 7

Repeater Serial no.__________

Quantity Init.

____ AUI ports ____ All ports tested

____ Ethernet ports ____ One transceiver/AUI cable per AUI port, serial nos.:______________________________

UPS (two)

Init.

___ Tested good

Additional items

Init. Quantity Item

____ ____ Blank, option keys (five)

____ ____ Cable, AUI (five: one per router/repeater port)

____ ____ Cable, CISCO 4000 to RS-449

____ ____ Cable, CISCO 7010 to KG-84C

____ ____ Cable, power (CPU, monitor, router, repeater)

____ ____ Cable, RS-232 to KG-84 red (six per ICA)

____ ____ Cable, RS-449 to KG-84 red (four)

____ _____ ICA cable (one per ICA)

____ ____ Surge supresser (two)

____ ____ Transceiver, thinnet

(reverse blank)

Appendix I

Communications and Information Systems Estimate

COMMUNICATIONS AND INFORMATION SYSTEMS ESTIMATE

(Local variations and modifications as necessary to meet requirements.)

------------------------------------------------------------------------------------------------

CLASSIFICATION

Copy no. ___ of ___ copiesIssuing headquarters

PLACE OF ISSUE

Date/time of issue

COMMUNICATIONS AND INFORMATION SYSTEMS ESTIMATE

Ref:

1. ( ) MISSION. (This subparagraph contains a brief restatement of the basicmission of the command as a whole as previously announced by the commander.Deduced missions necessary for the accomplishment of the basic mission, alongwith previous decisions of the commander regarding either deduced or basicmissions should be listed in appropriate subparagraphs.)

2. ( ) SITUATION AND CONSIDERATIONS.

a. ( ) Intelligence Situation. (Information known or obtained from theG2. Where appropriate, reference may be made to the Intelligence Estimateor other intelligence documents.)

(1) ( ) Characteristics of the Area. (Those affecting C2.)

(a) ( ) Weather.

(b) ( ) Terrain.

(c) ( ) Transportation networks/communication routes.

(d) ( ) Other area characteristics that affect C2.

(Page number)

CLASSIFICATION

I-2 _________________________________________________________________________________________________ MCWP 6-22

CLASSIFICATION

(2) ( ) Enemy Strengths and Disposition of Major Units

(a) ( ) Tactical units.

(b) ( ) Signals intelligence/electronics warfare.

1. ( ) Jamming.

2. ( ) Wire tapping.

3. ( ) Imitative deception.

b. ( ) Friendly Forces. (Information obtained from the commander’s planningguidance and from the G-3.)

(1) ( ) Present Disposition of Major Units

(a) ( ) Tactical units.

(b) ( ) CIS elements.

(2) ( ) Courses of Action to be Considered

(a) ( ) Course of action #1.

(b) ( ) Course of action #2, etc.

(3) ( ) Projected Operations. (If known, and which will affect the CIS situ-ation.)

(a) ( ) Rates of advance.

(b) ( ) Command post location and displacement.

(c) ( ) Uncovering of major communication routes.

(d) ( ) Other projected operations that affect the CIS situation.

c. ( ) Personnel Situation. (Information known or obtained from the G-1 re-garding personnel matters affecting the CIS situation. Where appropriate, makereference to the personnel estimate or other personnel documents.)

(1) ( ) Strengths.

(2) ( ) Replacements.

(Page number)

CLASSIFICATION

Communications and Information Systems _______________________________________________________________ I-3

CLASSIFICATION

(3) ( ) Command post organization and operation.

(4) ( ) Other personnel matters affecting the CIS situation.

d. ( ) Logistics Situation. (Information known or obtained from the G-4regarding logistics matters affecting the CIS situation. Where appropriate,reference may be made to the logistics estimate or other logistics docu-ments.)

(1) ( ) Availability of equipment.

(2) ( ) Condition of equipment.

(3) ( ) Availability of repair parts and consumable items.

(4) ( ) Other logistic matters affecting the CIS situation.

e. ( ) Assumptions. (Any assumptions required as a basis for initiatingplanning or for the preparation of the estimate.)

f. ( ) CIS Situation.

(1) ( ) General. (Information regarding current communication in-stallations, the status of the overall communications system, and the lo-cation and mission of communication and control agencies. Referencemay be made to the CIS SOP and COI or to the command, control andcommunications systems annexes contained in current operation plansor orders.)

(2) ( ) Special. (Items not covered elsewhere which affect the CISsituation.)

(a) ( ) Availability and assignment of radio frequencies.

(b) ( ) Assignment of call signs.

(c) ( ) Availability of shipboard communication equipment fortroop use.

(d) ( ) Arrangements for communications guard.

(e) ( ) Anticipated traffic volumes.

(f) ( ) Cryptographic matters.

(g) ( ) Other special items affecting the CIS situation.

(Page number)CLASSIFICATION

I-4 _________________________________________________________________________________________________ MCWP 6-22

CLASSIFICATION

3. ( ) ANALYSIS. (Each course of action under consideration is analyzed in thelight of significant factors to determine problems which will be encountered, measuresrequired to solve such problems, and any limiting features which will exist.)

a. ( ) Course of Action #1.

(1) ( ) Support Requirements,

(a) ( ) Terrain and Distance Factors. (A discussion of terrain and dis-tance factors that may affect the location of command posts, installations,and the employment of communications means.)

(b) ( ) Installations. (A discussion of known or deduced communica-tions requirements for each communications and control agency and otherunits. These requirements may be expressed as need lines or may be de-tailed to include types of circuits and terminal service, or other forms ofcommunications, required by these activities.)

(2) ( ) Support Capability. (A discussion of the capability to employ allavailable means of communications to satisfy the foregoing support require-ments.)

(a) ( ) Radio and Wire. (Discussed in conjunction with the capabilityto provide various types of circuits and attendant terminal service; e.g.,telephone, facsimile, and data.)

(b) ( ) Network Systems.

(c) ( ) Messenger.

(d) ( ) Visual and Sound.

b. ( ) Course of Action # 2. (Same for each COA #1.)

4. ( ) EVALUATION. (Based on the foregoing analysis, the advantages and disad-vantages of each course of action are summarized and compared from a CIS view-point.)

a. ( ) Course of Action #1.

(1) ( ) Advantages.

(2) ( ) Disadvantages.


Communications and Information Systems _______________________________________________________________ I-5

CLASSIFICATION

b. ( ) Course of Action #2.

(1) ( ) Advantages.

(2) ( ) Disadvantages.

c. ( ) Other Courses of Action.

5. ( ) CONCLUSIONS.

a. ( ) COA Statement. (A statement as to which course of action under con-sideration can best be supported from a CIS viewpoint.)

b. ( ) Salient Disadvantages Statement. (A statement of the salient disad-vantages which render the other courses of action less desirable from a CISviewpoint.)

c. ( ) Significant Problems Statement. (A statement of significant CIS prob-lems to be solved and limitations which may exist.)

d. ( ) Resolution Statement. (A statement of measures required to resolvethe foregoing CIS problems and offset any limitations which may exist.)

/s/____________________

_____________________

Appendixes: (As appropriate)

(Page number)CLASSIFICATION (reverse blank)

Appendix J

Sample CIS Annex (Annex K)

The CIS annex generally follows the basicOPLAN or OPORD format. General instructionsfor preparation are provided below. A sampleAnnex K appears on pages J-4 through J-14.

Heading

The heading is the same as the heading of theOPLAN or OPORD and gives the following in-formation:

Issuing HQThis consists of the official designation of thecommand.

Place of IssueThis shows the physical location of the issuingHQ. All letters are capitalized.

Date-Time GroupThis indicates the date and time the plan or orderis signed and, unless otherwise specified in theplan or order, the date and time the annex be-comes effective. It is expressed in standard mili-tary sequence: day, hour, minutes, time zonesuffix, month, and year (e.g., 151200Z Jan 2000).The time zone used will be that of the operationsarea or universal coordinated time.

Designation and Title of the AnnexThe title of an annex consists of a capital letterfollowed by an indication of the subject matter inparentheses and by the number of the OPLAN orOPORD to which it is attached.

ReferencesIncluded in the heading and listed as referencesare other sources of information (CIS SOPs,CEOI, maps, charts, or overlays) needed to under-

stand the annex. The caption Ref:____ is alwaysincluded. When there are no references, the cap-tion will be followed by the word “none.” Eachitem cited as a reference is preceded by a letter inparentheses and is in alphabetical sequence (e.g.,(a), (b), etc.). Information regarding maps andcharts should include the country, scale, name andsheet number, and year of edition, or the appropri-ate information required to locate them on com-pact disc.

Time Zone

The time zone normally used in the plan or orderis that of the objective area. When the plan or or-der applies to units in different time zones, uni-versal coordinated time or the time specified byhigher HQ is used.

Body

The body of the annex contains information con-sistent with that contained in the main body butfocused on information relevant to CIS.

General

This subparagraph contains a brief, general state-ment of the purpose of the annex with respect tothe basic plan objectives. It provides guidance forCIS support of the operation.

Situation

This paragraph provides an overview of the envi-ronment in which the CIS support described inthe annex will be provided. This includes the rea-son for the annex, the friendly and enemy situa-tion, and assumptions that are necessary toplanning. This subparagraph summarizes the situ-ation consistent with that of the main body, butfocusing on those factors that affect CIS.

J-2 ________________________________________________________________________________________________ MCWP 6-22

General. This subparagraph will make reference tothe concept of operations.

Enemy Forces. This subparagraph contains enemyforces information that will affect CIS employ-ment. This subparagraph usually references the in-telligence annex or provides specific informationon the enemy’s intelligence, EW, or deception (orother) capabilities; C2 facilities; CIS capabilities;and the possible exploitation of enemy assets.

Friendly Forces. This subparagraph contains infor-mation on the higher, adjacent, supported, and/orsupporting units or facilities involved in the C2support of the operation. This subparagraph identi-fies communications elements attached or de-tached for the operation. Reference may also bemade to the task organization annex.

Assumptions. This subparagraph establishes es-sential criteria for developing the CIS annex. If, asthe planning phase progresses and the situationdevelops, the assumptions prove mistaken, thenthe plan must be modified accordingly. Assump-tions define the anticipated conditions that willdrive CIS requirements and affect CIS capabili-ties; they are major considerations for planningCIS support. The number of assumptions shouldbe held to a minimum and worded carefully to de-scribe concisely and accurately the conditions onwhich the plan is based. Assumptions are applica-ble to plans only.

MissionThis paragraph is a concise statement of the mis-sion of the command. It should include the com-mander’s intent and identify actions necessary tosupport this intent, the concept of operations, andthe commander’s planning guidance. Normally,this paragraph states the time that the C2 facilitieswill commence and terminate operations.

Execution

Guiding PrinciplesThis subparagraph outlines the principles neces-sary for the coordination and guidance of all com-mands and units. Selected policies, doctrine, or

procedures that are contained in the references butthat need emphasis are called out. New proceduresare included in a separate subparagraph.

Operational ConceptThis subparagraph describes briefly how the en-tire operation is visualized from the CIS view-point. Particular emphasis is placed on aspects ofthe basic plan that establish CIS support require-ments, capabilities, and limitations.

Tasks and ResponsibilitiesThis subparagraph assigns specific CIS supportmissions or tasks for both issuing and subordinateunits. The tasks for each unit are addressed in sep-arate subparagraphs. In addition, instructions forfunctional areas such as intelligence, fires, and lo-gistics are in specific subparagraphs and often ex-panded on in appendices to Annex K. It should benoted that CIS support for functional areas is alsoroutinely incorporated into CIS appendices, tabs,or enclosures that are a part of the OPLAN/OPORD annexes covering those functional areas.

Coordinating InstructionsThis subparagraph provides instructions for CISsupport tasks that apply to two or more units.

Special Measures. This paragraph is separated intosubparagraphs and provides information regard-ing each special measure or procedure necessary tosupport the mission that is not addressed above orin paragraph 4 of the OPLAN or OPORD. Thisparagraph includes specific information pertain-ing to measures such as routing indicators, elec-tronic identification procedures, and liaison teams.

Information Management. This paragraph providesinstructions for ensuring that the communicationsand information management systems supports theunit information management plan. Usually, thisparagraph references the annex that addresses CISsupport for information management.

Administration and Logistics

AdministrationThis paragraph contains administrative proceduresconcerning CIS support in the areas of personnel,

Communications and Information Systems _______________________________________________________________ J-3

records, reports, and other administrative matters.It will include identification of CPs ashore andafloat.

LogisticsThis paragraph contains logistics information re-lating to CIS employment, and usually referencesthe logistic/CSS annex.

Command and Control

Command RelationshipsThis paragraph contains information relating tocommand relationships and usually refers to theappropriate appendices in the OPORD.

Communications and Information SystemsPlansThis paragraph refers to the appropriate appendi-ces in the OPORD.

Ending

The ending of the CIS annex consists of the fol-lowing:

● Acknowledgment instructions.

● Signature of either the commander or the com-mander’s authorized representative. (Authenti-cation by the authorized representative is alsoacceptable.)

● List of the appendices attached to the annex.

● Distribution.

Appendices

Appendices amplify information contained in thebasic CIS annex and are used to promote accura-cy, brevity, and clarity. The material contained inthe appendices is usually technical, detailed, andcomplex in nature. The information often lends it-self to presentation in tabular, schematic, or over-lay form. MCWP 5-1 (draft) provides amplifyinginformation. Typical appendices that may be pre-pared to support the basic CIS annex include com-munications security, call signs, visual and soundcommunications, and frequency management, toname but a few possibilities. The sample format(pages J-4 through J-14) contains a more exten-sive listing of possible appendices, but the listingprovided is not meant to be either exhaustive ormandatory. The number and type of appendicesrequired will vary with the situation and the needsof the preparing organization.

J-4 ________________________________________________________________________________________________ MCWP 6-22

CLASSIFICATION

Copy no. _____ of _____ copiesIssuing headquartersPLACE OF ISSUEDate/time of issueMessage reference number

ANNEX K TO (UNIT) OPORD (NUMBER) (U)

COMMUNICATIONS AND INFORMATION SYSTEMS (U)

(U) Ref: (a) MCWP 6-22 (Communications and Information Systems) (U)(b) CJCSM 6231 (Series) (Manual for Employing Tactical Communications) (U)(c) ACP 121 (Communications Instructions—General) (U)(d) ACP 122 (Series) (Communications Instructions—Security) (C)(e) ACP 167 (Series) (Glossary of Communications-Electronics Terms) (U)(f) NWP 4 (Series) (Basic Operational Communications Doctrine) (U)(g) NTP-3 (Series) (Telecommunications—Users Manual) (U)(h) NTP-4 (Series) (Naval Telecommunications Procedures—Fleet Communications) (C)(i) NTP-5 (Voice Communications) (U)(j) JANAP 128 (Series) (Automated Digital Network (AUTODIN) Operating Procedures) (U)(k) (Higher Headquarters) (Communication and Information Systems Plan) ( )(l) (Higher Headquarters) (OPORD) ( )(m) (Unit) Order (Communication and Information Systems SOP) ( )(n) (Unit) Order (Information Management SOP) ( )

(U) Time Zone: Z

1. ( ) GENERAL. This annex provides guidance for employing CIS architecture to support (unit) op-erations.

2. ( ) SITUATION.

a. ( ) General. (See Concept of Operations, Annex C (Operations))

b. ( ) Enemy.

(1) ( ) See Annex B (Intelligence)

(2) ( ) The enemy has the capability to—



CLASSIFICATION

(a) ( ) Conduct satellite-based EA, including imitative commu-nications deception, jamming (both communications and radar), ra-dar deception, and electromagnetic virus insertion operations.

(b) ( ) Intercept, analyze, and report timely intelligence informa-tion derived from friendly emitters to appropriate enemy command-ers.

(c) ( ) Accurately locate and target friendly forces communica-tions and electronic emitters by DF.

(d) ( ) Conduct meaconing operations against both TACAN andlow-frequency automatic direction finding (ADF) navigation re-ceivers.

(e) ( ) Access and gain temporary control of commercial digitaltelecommunications switches and deny access to satellite communi-cations switches in geosynchronous orbit.

(f). ( ) Employ malicious logic techniques against our informationsystems.

c. ( ) Friendly. See Annex A (Task Organization).

(1) ( ) Higher headquarters or other specific organizations that willprovide CIS to (unit) in a specific operation.

(2) ( ) The command relationship between friendly forces is shown inAnnex J (Command Relationships) to this OPORD.

(3) ( ) Attachments and Detachments

(a) ( ) (See Annex A (Task Organization) to this OPORD.

(b) ( ) When OPCON is taken of MAGTF units as (unit) formsduring compositing, MARFOR CIS assets will be listed separately.

d. ( ) Assumptions. (State the assumptions that establish essential criteriafor development of the annex.)

3. ( ) MISSION. Commencing and terminating on order, (unit) communica-tions organizations provide, install, operate, and maintain the internal and exter-nal communications and support the installation, operation, and maintenance ofinformation systems for reliable C2.

(Page number)

CLASSIFICATION

J-6 ________________________________________________________________________________________________ MCWP 6-22

CLASSIFICATION

4. ( ) EXECUTION

a. ( ) Commander’s Intent. Synopsis of the commander’s intent that bears onemploying CIS.

b. ( ) Guiding Principles

(1) ( ) The procedures contained in references (a) through (n) will be used.

(2) ( ) (Unit) operations will be conducted in a hostile EW environment.The following degradations are to be expected.

(a) ( ) Loss of DCS entry due to equipment damage or circuit path loss.

(b) ( ) Isolation of a headquarters due to loss of wideband systems.

(c) ( ) Hostile interference on all terrestrial/satellite MCR and SCRsystems (jamming).

(d) ( ) Loss of a switchboard due to component failure or hostile ac-tion.

(e) ( ) Loss of a satellite asset due to EW or destruction of the satellite.

(f) ( ) Disruption or loss of information systems due to componentfailure or hostile action.

(3) ( ) Frequency changes, radio transmission brevity, and, on occasion,complete EMCON will be employed in order to facilitate control and reduceanticipated interference with communications.

(4) ( ) Backup CIS equipment and alternate communications paths will beplanned and installed to enhance reliability, flexibility, and responsiveness ofCIS networks.

(5) ( ) Based on coordination with affected commanders and principalstaff officers, radio nets will be combined/pooled at the COCs and other C2facilities to conserve the frequency spectrum and reduce communications re-quirements.

(6) ( ) Information systems security and COMSEC measures will be em-ployed to deny information of value to the enemy and to prevent loss or dis-rupt ion of service through host i le act ion. Refer to Appendix 1(Communications and Information Systems Security) to this annex for de-tails.



(CLASSIFICATION)

(7) ( ) The (unit) G-6/S-6 will be the single point of contact at thisheadquarters for obtaining CIS services, support, or interface with high-er headquarters, NTS, DISA, or other external agencies.

c. ( ) Operational Concept

(1) ( ) Every means available will be used to provide the commanderwith the ability to exercise C2 and to accomplish the assigned mission.It is the responsibility of the G-6/S-6 to make the commander fullyaware of the capabilities and limitations of available CIS.

(2) ( ) Subordinate unit CIS officers must advise the G-6 of situa-tions, actual or potential, that could adversely affect MAGTF CIS sup-port.

(3) ( ) The major limitation of the CIS network is the EW threat. Theenemy has the full capability to disrupt, intercept, and confuse friendlyforces CIS operations. Line-of-sight communications will be adverselyaffected because of extremely rugged terrain throughout the AO.

(4) ( ) The critical vulnerability of CIS network is the degradation ofthe common tactical picture during extended COC and CP displace-ments.

(5) ( ) The COG of the CIS network is the capability to adapt andscale the network through extensive retransmission and backup systemsconfigurations. This provides full support of maneuver, intelligence,fires, CSS, and force protection throughout the AO.

(6) ( ) Appendix 1 (Communications and Information Systems Se-curity) to this annex lists measures designed to deny information to un-authorized persons.

(7) ( ) Appendix 2 (Command and Control Protection) to this annexdescribes measures to ensure continuous availability of friendly CIS.

d. ( ) Tasks and Responsibilities. Appendix 3 (Communications and In-formation Systems Planning) to this annex highlights CIS planning consider-ations for effective execution of the assigned mission.

(1) ( ) (Communications Unit)

(a) ( ) Provide the net control station(s) for all (unit) controlledradio circuits. See Appendix 4 (Radio Circuit Plan) to this annex.

(Page number)

CLASSIFICATION

J-8 ________________________________________________________________________________________________ MCWP 6-22

CLASSIFICATION

(b) ( ) Ensure that information on call signs and routing indicators ispromulgated to using staff sections/functional agencies. See Appendix 5(Call Signs and Routing Indicators) to this annex.

c) ( ) Install, operate, and maintain wire and MCR communicationsas described in Appendix 6 (Wire and Multichannel Radio Plan) to thisannex.

(d) ( ) Install, operate, and maintain the data communications networkas described in Appendix 7 (Data Communications Network Plan) to thisannex.

(e) ( ) Promulgate visual and sound signals for the operation. See Ap-pendix 8 (Visual and Sound Communications) to this annex.

(f) ( ) Install, operate, and maintain a SYSCON and TECHCON fa-cility in support of the (unit) communications networks. See Appendix 9(Communications Control) to this annex.

1. ( ) Ensure that a liaison representative is at higher and adja-cent headquarters to facilitate the direct handling of questions and/or problems relating to CIS.

2. ( ) Ensure that the G-6/S-6 and appropriate watch officersare informed of the communications circuit status.

3. ( ) Ensure strict compliance with G-6/S-6 assigned frequen-cies. See Appendix 10 (Frequency Management) to this annex.

4. ( ) Ensure that the established power distribution system isproperly grounded and that backup mobile power is available asnecessary. See Appendix 11 (Power Requirements) to this annex.

5. ( ) Ensure that CP displacements are hastily executed withthe requisite communications network scaled to retain essential in-formation flow. See Appendix 12 (Command Post DisplacementCommunications) to this annex.

6. ( ) Ensure that the TACSAT communications are installed,operated, and maintained as depicted in Appendix 13 (TacticalSatellite Communications) to this annex.

7. ( ) Ensure that communications restoration is handled expe-ditiously. See Appendix 14 (Communications Restoration) to thisannex.



CLASSIFICATION

8. ( ) Ensure that the G-6/S-6 and the command are keptinformed about the status of the commercial (local civilian)telecommunications systems.

(g) ( ) Install, operate, and maintain a communications and elec-tronics maintenance facility to inspect, repair, and/or replace faultycommunications and electronics equipment. See Appendix 15 (Spe-cial Maintenance Procedures) to this annex.

(h) ( ) Establish and maintain messenger service, includingtruck, helicopter, and motorcycle couriers, as directed in Appendix16 (Messenger Service) to this annex.

(i) ( ) Install, operate, and maintain a communications center tosupport (unit) with over-the-counter service for all Marine units/agencies at the (unit) headquarters. See Appendix 17 (Communica-tions Center) to this annex.

(j) ( ) Establish emergency action procedures for use in thecommunications center and any other area containing classifiedand/or cryptographic material. See Appendix 18 (Emergency Ac-tion) to this annex.

(2) ( ) Radio battalion/SSU: Install, operate, and maintain MAGTFCE special security communications terminal facilities.

(3) ( ) Ground Combat Element

(a) ( ) Install, operate, and maintain internal and external com-munication circuits and information systems as directed in unitSOPs and this annex.

(b) ( ) Be prepared to assume communications and crypto-guardfor (unit(s)) and to assume net control of (unit) circuits in the event(unit) headquarters becomes a casualty.

(c) ( ) Install, operate, and maintain a SYSCON/TECHCON fa-cility to ensure the rapid restoration/rerouting of communicationscircuits.

(4) ( ) Aviation Combat Element

(a) ( ) Install, operate, and maintain internal and external com-munications circuits and information systems as directed in unitSOPs and this annex.

(Page number)

CLASSIFICATION

J-10 _______________________________________________________________________________________________ MCWP 6-22

CLASSIFICATION

(b) ( ) Install, operate, and maintain a SYSCON/TECHCON facilityto ensure the rapid restoration/rerouting of communications circuits.

(c) ( ) Be prepared to maintain TADIL A, TADIL B, TADIL J, AT-DL-1, GBDL, and Link 1 connectivity with (fleet), (joint Service), andNATO agencies.

(d) ( ) Ensure the necessary liaison to establish and maintain the nec-essary MACCS interface with joint, other-Service, national, and interna-tional agencies, as required.

(5) ( ) Combat Service Support Element. Install, operate, and maintain aSYSCON/TECHCON facility to ensure the rapid restoration/rerouting ofcommunications circuits.

e. ( ) Intelligence and Reconnaissance. State intelligence and reconnaissancesupport required even though they have been covered in Annexes B and C becauseAnnex K may be distributed separately. If the information is very detailed, pre-pare an appendix to the CIS systems annex. If MILSATCOM is a requirement, en-sure it’s covered in Appendix 13.

f. ( ) Coordinating Instructions

(1) ( ) Special Measures

(a) ( ) The G-6/S-6 will make special efforts to indoctrinate staff/command personnel in alternate routes/means of communications to pre-clude the confusion or delay of information due to outages in the high-threat EW environment.

b) ( ) The communications support for linkup operations is found inAppendix 19 (Communications for Linkup Operations) to this annex.

((c) ( ) Specific communications procedures relative to air assets arefound in Appendix __ (Air Communications) to Annex __ (Air Opera-tions) to this OPORD.

(d) ( ) Safety is paramount in working with CIS. Appendix 20 (Safe-ty) to this annex identifies major safety measures and concerns.

e) ( ) Emergency evacuation operations require unique communica-tions capabilities. See Appendix 21 (Noncombatant Evacuation Opera-tions Communications) to this annex.


Communications and Information Systems _____________________________________________________________ J-11

CLASSIFICATION

(f) ( ) Detailed instructions for the ITSDN/DISN/DCS STEPprocedures are found in Appendix 22 (ITSDN/DISN/DCS) to thisannex.

(g) ( ) Detailed instruction designed to alleviate confusion in therapid task organization of (unit), with its necessary command com-munications support shifts, is found in Appendix 23 (Task Organi-zation/Communications Guard Shifts) to this annex.

(h) ( ) The description for handling emergency action communi-cations is found in Appendix 24 (Emergency Action Communica-tions) to this annex.

(i) ( ) To alleviate confusion and to aid in the organized assign-ment of resources while embarked, Appendix 25 (Communicationsand Information Systems Support for Embarked Units) to this annexdetails assets available for (unit) use.

(j) ( ) Details for radio battalion/special security officer (SSO)communications support are found in Appendix 26 (RadBn/SSOCommunications Support) to this annex.

(k) ( ) Procedures for effecting a reliable communications net-work in geographic areas in which climatic conditions require spe-cial consideration are found in Appendix 27 (Special Climatic/Geographic Considerations) to this annex.

(l) ( ) Special considerations for establishing and coordinatingjoint Service communications support are found in Appendix 28(Joint Service Communications Coordination) to this annex.

(m) ( ) Instructions for establishing and coordinating communi-cations connectivity with and in the host nation are found in Appen-dix 29 (Host Nation Communications) to this annex.

(n) ( ) Special communications considerations necessary to sup-port hardback (information pull) and connectivity to global infor-ma t ion sy s t ems a r e f ound i n Append ix 30 (G loba lCommunications) to this Annex.

(o) ( ) Special instructions for establishing and coordinatingcommunications support for intelligence activities are found in Ap-pendix 31 (Communications Support for Intelligence) to this annex.

(Page number)

CLASSIFICATION

J-12 _______________________________________________________________________________________________ MCWP 6-22

CLASSIFICATION

(p) ( ) Specific communications support relative to intelligence opera-tions is addressed in Appendix 31 (Communications Support for Intelli-gence) to this annex.

(q) ( ) Instructions for the establishment of Internet Protocol (IP) ad-dresses are found in Appendix 34 (IP Address Assignments) to this annex.

(2) ( ) Information Management. This paragraph contains instructions toensure that employing CIS is coordinated with and supports the unit informa-tion management plan. Detailed instructions will be addressed in Appendix35 to this annex.

5. ( ) ADMINISTRATION AND LOGISTICS.

a. Administration.

(1) ( ) Required CIS status and other reports are listed in Appendix 32(Reports) to this annex.

(2) ( ) Security violations will be reported in accordance with Appendix 1(Communications and Information Systems Security) to this annex.

(3) ( ) Procedures to support the administrative formation of a unit at seaare found in Appendix 33 (Compositing) to this annex.

(4) ( ) CPs

MEF main: Vicinity (location). See reference (n) and Annex C (Op-erations).

*List remaining MEF and other subordinate elements’ tactical,main, and rear echelons.

b. ( ) Logistics

(1) ( ) See Annex D (Logistics/Combat Service Support).

(2) ( ) Units will deploy with the capability to perform basic organization-al and field maintenance.

(3) ( ) The service support unit will provide intermediate maintenance (di-rect support and general support) of all ground-common communications andelectronics equipment.


Communications and Information Systems _____________________________________________________________ J-13

CLASSIFICATION

(4) ( ) Water, billeting, messing, and generator fuel will be providedby the unit that hosts multichannel teams.

(5) ( ) Communications units deploy with sufficient maintenanceequipment; repair parts (class IX); petroleum, oils, and lubricants (ClassIII); batteries; and cable for ( ) days/weeks of sustained operations.

(6) ( ) Report maintenance problems for critical low-density items tothe G-6/S-6 immediately.

6. ( ) COMMAND AND CONTROL

a. ( ) Command Relationships. Refer to Annex J for command relation-ships.

b. ( ) CIS Plans. All subordinate commands down to battalion level sub-mit unit CIS plans to this headquarters (Attn: AC/S G-6) NLT (date).

T.U. STARRMajor General, U.S. Marine Corps

Commanding

Appendices:1 Communications and Information Systems Security2 Command and Control Protection3 Communications and Information Systems Planning4 Radio Circuit Plan5 Call Signs and Routing Indicators6 Wire and Multichannel Radio Plan7 Data Communications Network Plan8 Visual and Sound Communications9 Communications Control10 Frequency Management11 Power Requirements12 Command Post Displacement Communications13 Tactical Satellite Communications14 Communications Restoration15 Special Maintenance Procedures16 Messenger Service17 Communications Center


J-14 _______________________________________________________________________________________________ MCWP 6-22

CLASSIFICATION

18 Emergency Action19 Communications for Linkup Operations20 Safety21 Noncombatant Evacuation Operations Communications22 ITSDN/DISN/DCS23 Task Organization/Communications Guard Shifts24 Emergency Action Communications25 CIS Support for Embarked Units26 RadBn/SSO Communications Support27 Special Climatic/Geographic Considerations 28 Joint Service Communications Coordination 29 Host Nation Communications30 Global Communications31 Communications Support for Intelligence32 Reports33 Compositing34 IP Address Assignments35 CIS Support for Information Management

OFFICIAL:

O.N.E. EAGLEColonel, USMCAC/S G-6

DISTRIBUTION:

Appendix K

CIS Threat Assessment Planning Checklist

This checklist is designed to assist C2 planners inevaluating any threat capability to exploit and/ordisrupt our CIS. Planners must understand thethreat to develop a C2 architecture that performseffectively with minimum disruption.

Physical Destruction

● What type of weapons of mass destruction doesthe enemy have?

● Do they have antiradiation munitions? How ac-curate are they?

● What means of delivery of munitions are avail-able?

● Do they have trained saboteurs? Infiltrators?

● What other means of physical destruction dothey possess?

● Where are we most vulnerable to ground at-tack?

● Does the enemy possess and train to use chemi-cal and biological agents? What are theirmeans of delivery?

● Are lasers used against CIS targets?

Collection Systems

● Is the threat capable of—

● Visible light, infrared imagery?

● Electronic surveillance, direction finding?

● Interception of radio signals, wiretapping?

● Gathering HUMINT and placing agents inthe area?

● What means of collection are used?● Satellite? What is the footprint? When are

we most vulnerable?

● Overflights? What platforms are used? Whatcapability do they have?

● Ground collection units? Where? Capabil-ity? Range of their equipment? What fre-quencies? Is it a part of a worldwidecollection and reporting network?

● How is information used and distributed?● Direct targeting?

● Tracking?

● Intelligence analysis?

Jamming

● What type of jamming do they use? Barrage?Spot?

● What frequencies are vulnerable?● What geographic area is likely to be affected?● What equipment do they use? How is it de-

ployed?● What techniques are most likely to be used?● What circuits are most vulnerable?

Imitative Deception

● Level of sophistication?● Do they have trained imitative communications

deception operators?● How do they deploy?● What techniques have they used in the past?

(reverse blank)

Appendix L

Emission Classification and Designation

The International Telecommunication Union(ITU) at its World Administrative Radio Confer-ence in 1979 in Geneva, Switzerland, adopted aninternational standard method of forming radioemission designators. Emissions shall be desig-nated according to their necessary bandwidth andtheir classification character as prescribed by theITU. Information about the character codes in thisappendix is derived from the Manual of Regula-tions and Procedures for Federal Radio Frequen-cy Management (also referred to as the Redbookor NTIA Manual), pages 9-16 through 9-18. Thecurrent version of this manual is available on theNational Telecommunications and InformationAdministration (NTIA), Department of Com-merce, Web page: www.ntia.doc.gov or with thefrequency manager.

Necessary Bandwidth

For a given class of emission, the width of the fre-quency band is just sufficient to ensure the trans-mission of information at the rate and with thequality required under specified conditions. Thenecessary bandwidth shall be added just beforethe classification symbols and shall be expressedby three numerals and one letter. The letter occu-pies the position of the decimal point and repre-sents the unit of bandwidth. The first charactershall be neither zero nor K, M, or G. Necessarybandwidths are expressed as follows:

Between 0.001 and 999 Hz shall be expressed inHz (letter H). Examples:

0.002 Hz = H002 25.3 Hz = 25H3

0.1 Hz = H100 400.0Hz = 400H

Between 1.00 and 999 kHz shall be expressed inkHz (letter K). Examples:

2.4 kHz = 2K40 180.4 kHz = 180K

6.0 kHz = 6K00 180.5 kHz = 181K

12.5 kHz = 12K5 180.7 kHz = 181K

Between 1.00 and 999 MHz shall be expressed inMHz (letter M). Examples:

1.25 MHz = 1M25 10.0 MHz = 10M0

2.0 MHz = 2M00 202 MHz = 202M

Between 1.00 and 999 GHz shall be expressed inGHz (letter G). Example:

5.65 GHz = 5G65

Classification

Emissions shall be classified and symbolized ac-cording to their basic characteristics. Optionalcharacteristics may be used. Normally, only thebasic characteristics are required.

Basic Characteristics

● First character—type of modulation of themain carrier.

● Second character—nature of signal(s) modulat-ing the main carrier.

● Third character—type of information to betransmitted.

L-2 ________________________________________________________________________________________________ MCWP 6-22

Modulation that is used only for short periods andfor incidental purposes (such as, in many cases,for identification or calling) may be ignored pro-vided the necessary bandwidth as indicated is notthereby eased.

First Character

Unmodulated

Emission of an unmodulated carrier

Amplitude Modulated

Emission in which the main carrier is AM (includ-ing cases where subcarriers are angle modulated).

Angle Modulated

Emission in which the main carrier is angle modu-lated.

Amplitude and Angle ModulatedCE mission in which the main carrier is amplitudeand angle modulated, either simultaneously or in apreestablished sequence.

PulseEmission of pulses (emissions for which the maincarrier is directly modulated by a signal that hasbeen coded into quantized form (e.g., pulse-codemodulation)), should be designated using thecharacters listed above in amplitude modulated, orangle modulated.

Character Description

N Unmodulated carrier


A Double sideband

H Single sideband, full carrier

R Single sideband, reduced or vari-able-level carrier

J Single sideband, suppressed car-rier

B Independent sidebands

C Vestigial sideband


F FM

G Phase modulation


D Amplitude and angle modulation


P Sequence of unmodulated pulses

K Modulated in amplitude

L Modulated in width/duration

M Modulated in position/phase

Q In which the carrier is angle modu-lated during the period of the pulse

V That is a combination of the forego-ing or is produced by other means

W Of cases not covered above, in which an emission consists of the main car-rier modulated either simultaneously or in a combination of two or more of the following modes: amplitude, angle, pulse

X In cases not otherwise covered (A fully explanation for this selection must be provided in supplementary details)

Communications and Information Systems ______________________________________________________________ L-3

Second Character

Third Character

Optional Characteristics

The optional additional characteristics not nor-mally required are—

● Fourth character—details of signal(s)

● Fifth character—nature of multiplexing

Character Description0 No modulating signal

1 A single channel* containing quan-tized or digital signal information without the use of a modulating sub-carrier (this excludes time-division multiplex)

2 A single channel* containing quan-tized or digital signals with the use of a modulating subcarrier (this excludes time-division multiplex)

3 A single channel* containing analog signals

7 Two or more channels* containing quantized or digital signals

8 Two or more channels* containing analog signals

9 Composite system with one or more channels containing quantized or digital signals together with one or more channels containing analog sig-nals

X In cases not otherwise covered (a full explanation for this selection must be provided in supplementary details)

*In this context, the word “channel(s)” refers to the radio frequency channel.

Character DescriptionN No information transmitted

A Telegraphy for aural reception

B Telegraphy for automatic reception

Character DescriptionC Facsimile

D Data transmission, telemetry, and telecommand (The character D indi-cates that data, telemetry, or telecom-mand information* is being transmitted individually or that any combination of the three is being transmitted simultaneously. If any combination is being transmitted simultaneously, one of the multichan-nel symbols 7, 8, or 9 must be used for the second character.)

E Telephony (including sound broad-casting)

F Television (video)

W Combination of the above (Use only for multichannel systems that have the capability to transmit all informa-tion* simultaneously.)

X Cases not otherwise covered (A full explanation is required in supplemen-tary details.)

*In this context, the word “information” does not include information of a constant, unvarying nature such as is provided by standard frequency emissions, continuous wave, and pulse radars

L-4 ________________________________________________________________________________________________ MCWP 6-22

Fourth Character

Fifth Character

Character DescriptionA Two-condition code with elements of

differing numbers and/or durations

B Two-condition code with elements of the same number and duration with-out error correction

C Two-condition code with elements of the same number and duration with error correction

D Four-condition code in which each condition represents a signal element (of one or more bits)

E Multicondition code in which each condition represents a signal element (of one or more bits)

F Multicondition code in which each condition or combination of condi-tions represents a character

G Sound of broadcasting quality (monophonic))

H Sound of broadcasting quality (ste-reophonic or quadraphonic)

J Sound of commercial quality (excluding categories of sound given under characters K and L, below)

Character DescriptionK Sound of commercial quality with

the use of frequency inversion or band splitting

L Sound of commercial quality with separate FM signals to control the level of demodulated signal

N Monochrome

O Color

P Combination of the above

Q Cases not otherwise covered

Character DescriptionN None

C Code-division multiplex (this includes bandwidth-expansion tech-nique

F Frequency-division multiplex

T Time-division multiplex

W Combination of frequency-division multiplex and time-division multi-plex

X Other types of multiplexing

Appendix M

Sample Guard Charts

LEGEND:X = GUARDW = WHEN DIRECTEDA = AS REQUIREDM = MONITORC = NET CONTROL

JOIN

T A

IR C

OO

RD

INA

TIO

N N

ET

JOIN

T A

IR C

OO

RD

INA

TIO

N N

ET

TA

CT

ICA

L A

IR D

IRE

CT

ION

NE

T

JOIN

T A

IR S

UP

PO

RT

C

OO

RD

INA

TIO

N N

ET

TA

DIL

A (

LIN

K 1

1)

JOIN

T A

IR S

UP

PO

RT

CO

OR

DIN

AT

ION

NE

T

TA

DIL

B (

LIN

K 1

1B)

JOIN

T IC

N

JOIN

T T

SN

JOIN

T D

CN

JOIN

T V

PN

JOIN

T T

AC

TIC

AL

AIR

RE

QU

ES

T

AIR

TR

AF

FIC

CO

NT

RO

L

JOIN

T S

AR

NE

T

TA

DIL

C (

LIN

K 4

A)

JMS

AT

DL-

1

NA

DG

E (

NA

TO

LIN

K 1

)

AC

-1

AC

-1A

AC

-4

AC

-10A

AC

-10B

AC

-11

AC

-13

AC

-14

AC

-15

AC

-16

AC

-17

AC

-18

AC

-22

JTF

-17

NO

NE

NO

NE

NO

NE

NO

NESOP CIRCUIT

DESIGNATIONS

TRANSMISSION TYPE:1=HF 3=UHF2=VHF 4=UHFSATCOM

4 1 1 1OR 3

1 1 1 1 1 3 3 3 2 2OR 3

CJTF/JFACC C C C C C C C C C C X

X X X X X X X X X X X W M

X

X X X X X X X

X X M

M

M

M

M

X

X X X X X X X

X X X X X X X

X

X X X X X X X X X X

X X

X X X X X

X

X

A

RO

UT

ED

TH

RO

UG

H T

HE

MU

LTIC

HA

NN

EL

NE

TW

OR

K

RO

UT

ED

TH

RO

UG

H T

HE

MU

LTIC

HA

NN

EL

NE

TW

OR

K

RO

UT

ED

TH

RO

UG

H T

HE

MU

LTIC

HA

NN

EL

NE

TW

OR

K

USMC TACC

USMC TAOC

USMC DASC

USN NTDS SHIPS

USN ATDS SHIPS

USAF CRC

USAF AOC

USAF AWACS

USAF FACP

USA FDC

USMC VMFA SQUADRONS

USN FIGHTER/ATTACK SQDNS

Figure M-1. Sample Radio Guard Chart.

M-2 ________________________________________________________________________________________________ MCWP 6-22

LEGEND:X = GUARDW = WHEN DIRECTEDA = AS REQUIREDM = MONITORC = NET CONTROL

MA

RF

OR

CM

D N

ET

MA

RF

OR

TA

C N

ET

MA

RF

OR

INT

EL

NE

T

MA

RF

OR

CO

MM

CO

OR

D

ME

F C

MD

NE

T 2

ME

F C

MD

NE

T 1

ME

F T

AC

1

ME

F T

AC

2

ME

F A

LER

T B

RD

CA

ST

ME

F IN

TE

L 1

ME

F IN

TE

L 2

ME

F C

SS

ME

F C

OM

M C

OO

RD

1

ME

F C

OM

M C

OO

RD

2

TA

R/H

R 1

TA

R/H

R 2

712A

712B

713A

713B

715

717A

717B

721

751A

751B

NO

NE

NO

NESOP CIRCUIT

DESIGNATIONS

TRANSMISSION TYPE:1=HF 3=UHF2=VHF 4=UHFSATCOM

1OR 4

1 2 1 1 1 2 2 2

MARFOR HQ C C C C

X X X X X X

X X X X X X

X X A

A

X X X X X

X C

X

X X X X

MEF HQ

MAW TACC

MAR DIV HQ

DASC

FSSG HQ

NO

NE

NO

NE

NO

NE

NO

NE

AS

DIR

AS

DIR

AS

DIR

AS

DIR

1 1 1

C C C C C C C C C X

W W W W W A

W W W

W W W W W

C C

Figure M-1. Sample Radio Guard Chart (continued).

Communications and Information Systems ______________________________________________________________ M-3

(reverse blank)

Figure M-2. Sample IP Network Diagram.

Appendix N

Points of Contact

Headquarters, United States Marine Corps (C4I)http://www.usmc.milDSN 327-5561Commercial (703) 607-5538

Marine Corps Network Operations CenterHelp Deskhttp://www.noc.usmc.milDSN 278-5300Commercial (703) 784-5300

Architecture BranchRequirements DivisionMarine Corps Combat Development Commandhttp://www.archvision.quantico.usmc.milDSN 278-6049Commercial (703) 784-6049

Marine Corps Systems CommandC4I Directorate, Code CCR, MCHShttp://www.marcorsyscom.usmc.milDSN 278-5610Commercial (703) 784-5610

(This WWW site has links to the following:Marine Corps Computer Buyer’s GuideDII COEMARCORSYSCOMDefenseLINKMarineLINK)

Doctrine Division, MCCDChttp://www.doctrine.quantico.usmc.milDSN 278-6229/33 (Unclassified)fax x-2917Commercial (703) 784-xxxx

Command and Control Systems SchoolMarine Corps Universityhttp://www.ccss.quantico.usmc.milDSN 278-2438Commercial (703) 784-2438

Marine Corps Communications Electronics SchoolMCAGCCDSN 957-3707 (Ops)

Marine Corps Tactical Systems Support Activityhttp://www.mctssa.usmc.milDSN 365-2167Commercial (760) 725-2167

National Telecommunications and Information AdministrationDepartment of Commerce(Frequency Management-Emission DesignatorCodes)http://www.ntia.doc.gov

Naval In-Service Engineering Activity-East(INFOSEC)E-mail [email protected]://infosec.nosc.milDSN 563-8878/8879Commercial 800-304-4636/800-974-5426

Naval Computer Incident Response Team(NAVCIRT) HotlineNAVCIRT NIPRNETE-mail [email protected] 888-NAVCIRT/800-628-8893

(reverse blank)

Appendix O

Glossary

Section I. Acronyms and Abbreviations

AAAV........ advanced amphibious assault vehicleAAV........................... assault amphibious vehicleAAW.............................................. antiair warfareACE ............................... aviation combat elementACI....................................air combat intelligenceACOM ....................................Atlantic CommandACP..............Allied Communications PublicationAC/S....................................assistant chief of staffADCP.........air defense communications platformADF ........................... automatic direction findingADNS...........Automated Digital Network SystemADP ............................ automated data processingAFATDS......... Advanced Field Artillery Tactical Data SystemAFFOR....................................... Air Force ForcesAIS ........................automated information systemALICE............. all-purpose lightweight individual

carrying equipmentAM ..................................... amplitude modulationANCD ..................... automated net control deviceANGLICO .......air/naval gunfire liaison companyAO.............................................area of operationsAOC ........................ air operations center (USAF)AOI ................................................area of interestAOR .....................................area of responsibilityARFOR .............................................Army ForcesASIP.....advanced systems improvement programATC ........................................... air traffic controlATDL................................Army tactical data linkATF.................................... amphibious task forceATFIC..............................ATF intelligence centerATLASS .... Asset Tracking Logistics and Supply

SystemATM......................... asynchronous transfer modeATO ............................................ air tasking orderAUI ..............................autonomous unit interfaceAUTODIN .................Automatic Digital NetworkAWACS ......airborne warning and control system

BDA............................. battle damage assessmentBGLCSS ...... Battle Group Logistics Coordinated

Support SystemBGIXS .........Battle Group Information Exchange

SystemBGP.................................border gateway protocolBGPHES ................Battle Group Passive Horizon

Extension SystemBLT....................................battalion landing teamBn.............................................................battalionbps..................................................bits per secondBUU............................................... basic user unit

C2........................................command and controlC3........... command, control and communicationsC3I ....... command, control, communications, and

intelligenceC4......... command, control, communications, and

computersC4I .............. command, control, communications,

computers and intelligenceCAIMS...... Conventional Ammunition Integrated

Management SystemCATF ............ commander, amphibious task forceCBIRF.................... Chemical/Biological Incident

Response ForceCCIR ................commander’s critical information

requirementsCCR ........................ common computer resourcesCDE ...................... common desktop environmentCD.................................................... compact diskCD-ROM .......... compact disk–read only memoryCE ............................................ command elementCENTCOM.............................. Central CommandCEOI ........ communications-electronics operating

instructionsCFC..........................Combined Forces CommandCG.......................................commanding general;

O-2 ________________________________________________________________________________________________ MCWP 6-22

guided missile cruiserCGS..................................common ground stationCHBDL.......... common high-bandwidth data linkCI ............................................counterintelligenceCIC.............................. combat intelligence centerCINC......................................commander in chiefCINCNORAD.......... Commander in Chief, North

American Aerospace Defense CommandCIS ......communications and information systemsCISC............... complex instruction set computingCISCO.......Cisco Systems (a computer company)CISO ..........communications information systems

officerCJCS .......... Chairman of the Joint Chiefs of StaffCJCSI ......... Chairman of the Joint Chiefs of Staff

instructionCJCSM....... Chairman of the Joint Chiefs of Staff

manualCJTF..........................commander, joint task forceCLF ............................. commander, landing forceCMD ......................................................commandCMS .... communications security material systemCOA ............................................. course of actionCOC .............................. combat operations centerCODEC...........................................coder-decoderCOE ................... common operating environmentCOE-V ...common operating environment-variantCOG ............................................ center of gravityCOMINT................. communications intelligencecomm .......................................... communicationsCOMMARFOR ..........commander, Marine Corps

forcesCOMMARFORLANT......... Commander, Marine

Corps Forces, AtlanticCOMMARFORPAC............ Commander, Marine

Corps Forces, PacificCOMMARFORRES ............ Commander, Marine

Corps Forces ReserveCOMMARLOGBASES....... Commander, Marine

Corps Logistics BasesCOMM BN .................. communications battalionCOMM COORD......communications coordinatorCOMNAVFOR........... Commander, Navy ForcesCOMPHIBGRU...commander, amphibious groupCOMPUSEC.............................computer securityCOMSEC ...................... communications security

ConEx ...................................... Container ExpressCONPLAN........................................ concept planCONUS......................... continental United StatesCOP.......................... common operational pictureCOTS ............................. commercial off the shelfCP................................................... command postCPOG................ chemical protective overgarmentCPU................................... central processing unitCRC .......................... control and reporting centerCRITICOMM ................. critical communicationsC/S .................................................... chief of staffCSDTS........ common shipboard data terminal setCSMA/CD .......carrier sense multiple access with

collision detectionCSR-TEP .... circuit switch routing-task execution

planCSS .................................. combat service supportCSSE...................combat service support elementCSSOC............combat service support operations

centerCSU........................................channel service unitCTAPS..................contingency theater automated

planning systemCTT....................... commander’s tactical terminalCUDIXS............common user digital information

exchange systemCV...................................................aircraft carrierCVN..................................aircraft carrier, nuclearCVSD................continuously variable slope delta

DACT............................................ data automatedcommunications terminal

DAMA ..............demand assigned multiple accessDARPA................... Defense Advanced Research

Projects AgencyDAS ......................................direct access serviceDASC...............................direct air support centerDASC(A) ........direct air support center (airborne)DAT ...........................................digital audio tapeDATACOMM..................... data communicationsdBm.........decibels referred to 1 milliwatt; decibel

millivoltsDCE .............. distributed computing environmentDCN..........................Data Link Coordination NetDCO.......................................... dial central officeDCS................. Defense Communications System

Communications and Information Systems ______________________________________________________________ O-3

DCT ...................digital communications terminalDD...........................................................destroyerDDG........................................................destroyerDDN..................................Defense Data NetworkDEERS................. Defense Eligibility Enrollment

Reporting SystemDEUCE ..................................downsized end-user

computing equipmentDF ...............................................direction findingDII ...................defense information infrastructureDISA .........Defense Information Systems AgencyDISN .......Defense Information Systems NetworkDLTU.........................digital line termination unitDMR ....................................digital modular radioDMS..............................Defense Message SystemDNS .................................. Domain Name SystemDNVT ................ digital nonsecure voice terminalDOD................................. Department of DefenseDODD............................................DOD directiveDODIIS.... DOD Intelligence Information SystemDON ...............................Department of the NavyDSCS .............Defense Satellite Communications

SystemDSN ...........................Defense Switched NetworkDSSCS ........ Defense Special Security Communi-

cations SystemDSU ............................................ data service unitDSVT .................digital subscriber voice terminalDTC .................................digital technical controlDTD ...................................... data transfer deviceDTE.................................data terminal equipmentDTG .............................digital transmission groupDWTS ....Digital Wideband Transmission System

EA ............................................... electronic attackEAF..................................... expeditionary airfieldEEFI ....essential elements of friendly informatione.g....................................................... for exampleEGP.............................. exterior gateway protocolEHF.............................. extremely high frequencyELINT................................ electronic intelligenceEMCON ...................................... emission controlEMI ..........................electromagnetic interferenceEP..........................................electronic protectionEPLRS ........ enhanced position location reporting

system

ESM .............electronic warfare support measuresEUCE..................... end user computer equipmentEW ................... electronic warfare; early warningEW/C .................................. early warning/controlEWCC.......electronic warfare coordination center

F ..................................................................... flashFACP ...............................forward air control postFAD ....................................... fighter air directionFAPES ............Force Augmentation Planning and

Execution Systemfax ........................................................... facsimileFDC........................................ fire direction centerFDDI ..................... fiber distributed data interfaceFFCC..................... force fires coordination centerFFIR .........friendly force information requirementFIWC ...............Fleet Information Warfare CenterFLTSAT............................................ fleet satelliteFLTSATCOM........fleet satellite communicationsFLTSEVOCOM.........................fleet secure voice

communicationsFM...................................... frequency modulationFMF ........................................Fleet Marine ForceFMFM........................ Fleet Marine Force manualFO ..................................................Flash OverrideFSC2S ..........Fire Support Command and Control

SystemFSCC................... fire support coordination centerFSK .................................. frequency shiftkey(ing)FSSG..........................force service support groupft. ............................................................. foot; feet

GARC .................................... GCCS ATO reviewGB.............................................................gigabiteGBDL................................ground-based data linkGBNP....................Global Block Numbering PlanGBS...............................Global Broadcast SystemGCA ......................... ground controlled approachGCCS ...... Global Command and Control SystemGCE .................................ground combat elementGCS.................................... ground control stationGCSS .................Global Combat Support SystemGENSER...................... general service (message)GHz.........................................................gigahertzGMF.................................... ground mobile forcesGOTS............................. government off the shelf

O-4 ________________________________________________________________________________________________ MCWP 6-22

GPS .............................. global positioning systemGPSIU........... global positioning system interface

unitsGSORTS ............. Global Status of Resources and

Training SystemGTN .................... Global Transportation NetworkGUI .................................. graphical user interface

H&S ............................... headquarters and serviceHAVE QUICK................jam-resistant UHF radioHAZMAT ..............................hazardous materialsHD.......................................... helicopter directionHDC .............................helicopter direction centerHDLC......................... high-level data link controlHF ................................................. high frequencyHFRG.........................high frequency radio groupHLZ.................................. helicopter landing zoneheavy HMMWV .....heavy variant, high-mobility,

multipurpose wheeled vehicleHMMWV... high mobility multipurpose wheeled

vehicleHPS ................................ high-performance serverHPW... high-performance workstation/application

serverHQ..................................................... headquartersHQMC ..................... Headquarters, Marine CorpsHR............................................. helicopter requestHUMINT ................................ human intelligenceHz...................................................................hertz

I .............................................................immediateIAS ............................ intelligence analysis systemIBS ............................ integrated broadcast serviceICN............................................idle channel noiseID ..................................................... identificationIDNX ........... integrated digital network exchangei.e.................................................................. that isIEEE.............................. Institute of Electrical and

Electronic EngineersIFF............................. identification, friend or foeIFSAS........interim fire support automated systemIGRP ...................................... interior routing and

encapsulation protocolIMRAS.........Individual Manpower Requirements

and Availability System

INFOSEC.............................. information securityINMARSAT......... international maritime satelliteINSCOM................... U.S. Army Intelligence and

Security CommandINTELINK...................................intelligence linkINTELINK-S ................... intelligence link-SecretI/O ...................................................... input/outputIP................................................. internet protocolIPA..................................imagery product archiveIPB ......intelligence preparation of the battlespaceIRM....................... information resource managerISC .....................information systems coordinatorISMO ...............information systems management

officerISO.........................International Organization for

StandardizationIT-21 .............information technology for the 21st

centuryITP ............................integrated terminal programITSDN............. Integrated Tactical-Strategic Data

NetworkITU.......International Telecommunications UnionIW ..........................................information warfareIWF ................................... inter-working function

JANAP.................... Joint Army, Navy, Air Forcepublication

JBS...................................Joint Broadcast ServiceJCCC............joint communications control centerJCSE......... joint communications support elementJDISS ........Joint Deployable Intelligence Support

SystemJEPES...... Joint Engineer Planning and Execution

SystemJFACC ...... joint force air component commanderJFC.................................... joint force commanderJFLCC.....joint force land component commanderJFMCC ............... joint force maritime component

commanderJIEO ................ Joint Interoperability Engineering

OrganizationJMCIS ...... Joint Maritime Command Information

SystemJMCOMS....................................... Joint Maritime

Communications System


JMTCSS........................... Joint Maritime TacticalCommunications Switching System

JNAV ...................................... JOPES NavigationJOPES .....................Joint Operation Planning and

Execution SystemJSIPS.................................Joint Services Imagery

Processing SystemJSIPS-N.............................................. JSIPS-NavyJSOTF ..............joint special operations task forceJSTARS ................ joint surveillance target attack

radar systemJTF .................................................joint task forceJTIDS ...... Joint Tactical Information Distribution

SystemJTT ...................................... joint tactical terminalJULLES .......................... Joint Universal Lessons

Learned SystemJWICS..................... Joint Worldwide Intelligence

Communications System

kbps ......................................... kilobits per secondkHz.......................................................... kilohertzkm .......................................................... kilometer

LAAD .............................. low altitude air defenseLAAM ............................ light antiaircraft missileLAN ......................................... local area networkLAR .......................light armored reconnaissanceLAV .................................... light armored vehicleLCAC..............................landing craft air cushionLCC............................ amphibious command shipLCU .......................................landing craft, utilityLDR .................................................. low data rateLFOC ................... landing force operations centerLFSP .......................... landing force support partyLGM..................................loop group multiplexerLHA ..............general purpose amphibious assault

shipLHD ..............general purpose amphibious assault

ship (with internal dock)LOGAIS..............logistics automated information

systemLOG IR Plan ..... Logistics Information Resources

PlanLOGSAFE ............. logistics sustainment analysis

and feasibility estimator

LPD............................. amphibious transport dockLPH................................. amphibious assault shipLSB ......................................logistic support base;

landing support battalionLSD........................................... dock landing shipLZ...................................................... landing zoneLZCT ........................... landing zone control team

m .................................................................. meterMACCS ............Marine air command and control

systemMACG ........................... Marine air control groupMACS .......................Marine air control squadronMAFC ............... MAGTF all-source fusion centerMAG ................................... Marine aircraft groupMAGTF ...................Marine air-ground task forceMAGTF II............Marine air-ground task force IIMALS ......... Marine Aviation Logistics SquadronMARCOMMDET...........Marine communications

detachmentsMARCORMATCOM .......Marine Corps Material

CommandMARCORSYSCOM......... Marine Corps Systems

CommandMARDIV .................................... Marine DivisionMARFOR..............................Marine Corps forcesMARFORLANT...Marine Corps Forces, AtlanticMARFORPAC........Marine Corps Forces, PacificMARFORRES .......Marine Corps Forces ReserveMASS....................... Marine air support squadronMATCD..... Marine air traffic control detachmentMAW ....................................Marine aircraft wingMb...........................................................megabiteMbps ................................... megabites per secondMCAGCC ....................Marine Corps Air-Ground

Combat CenterMCCC................ Marine Corps Command CenterMCCDC...... Marine Corps Combat Development

CommandMCDP ........... Marine Corps doctrinal publicationMCHS .................Marine common hardware suiteMCIXS... maritime cellular information exchange

systemMCMO........MEF COMSEC Management OfficeMCO ...................................... Marine Corps orderMCPP.................. Marine Corps Planning Process

O-6 ________________________________________________________________________________________________ MCWP 6-22

MCR........................................ multichannel radioMCRP ...........Marine Corps reference publicationMCTSSA ............ Marine Corps Tactical Systems

Support ActivityMCWP ......Marine Corps warfighting publicationMD ............................................................medicalMDL...................................MAGTF Data LibraryMDR ..........................................medium data rateMDS....................Message Dissemination SystemMDSS II ................ MAGTF Deployment Support

System IIMECDL .......mission equipment control data linkMED BN ....................................medical battalionMEDEVAC.............................medical evacuationMEF ...........................Marine expeditionary forceMEF (Fwd) ................Marine expeditionary force

(forward)MEPES.............. Medical Planning and Execution

SystemMETOC ......... meteorological and oceanographicMEU.............................Marine expeditionary unitMEU(SOC) .... Marine expeditionary unit (special

operations capable)MEWSS ........Mobile Electronic Warfare Support

SystemmHz.......................................................megahertzMILSATCOM ........................... Military Satellite

CommunicationsMilstar .....................military strategic and tactical

relay systemMilVan ..............................................Military VanMIME..........multipurpose internet mail extensionMIMMS ............. Marine Integrated Maintenance

Management SystemMLC..........................Marine Logistics CommandMLG...................................Marine Liaison GroupMOE............................. measures of effectivenessMOU ................... memorandum of understandingMOOTW......... military operations other than warMOS..................... military occupational specialtyMP ................................................. military policeMPF .......................maritime prepositioning forceMPS .......................maritime prepositioning shipsMRE.......................................... meal, ready to eatMRMS ........ Maintenance Resource Management

System

MS...............................message switch; MicrosoftMSC.........................major subordinate commandMS-DOS ...........MicroSoft-disk operating systemMSE ........................ mobile subscriber equipmentMTACCS...............Marine tactical command and

control sectionsMT Bn............................motor transport battalionMTF ...................................... message text formatMTS .................................Marine tactical systemsMUX ...................................................... multiplexMWCS ...Marine wing communications squadronMWSG.......................Marine wing support groupMWSS.................. Marine wing support squadron

NADGE ......................NATO air defense groundenvironment

NALCOMIS........ Naval Aviation Logistics Com-mand Management Information

SystemNATO ........... North Atlantic Treaty OrganizationNAVCIRT.....................Naval Computer Incident

Response TeamNAVFOR.......................................... Navy ForcesNAVMACS II............ Naval Modular Automated

Communications Subsystem IINBC ..................nuclear, biological, and chemicalNCIS .......... Naval Criminal Investigative ServiceNCS-E(D) .................Net Control Station-EPLRS

(Downsized)NCTAMS.........naval computer and telecommun-

ications area master stationNDI ..................................nondevelopmental itemNDP .............................naval doctrine publicationNECC....... Navy EHF communications controllerNGF ................................................. naval gunfireNIPRNET........ nonsecure internet protocol router

networkNIPS.......... Naval Intelligence Processing SystemNIST...............National Institute of Standards and

TechnologyNITF...........national imagery transmission formatNLT.................................................. not later thanNOC............................. network operations centernos. ...........................................................numbersNRZ ........................................... nonreturn to zeroNST.................................. Navy standard terminal


NSTISSI............National Security Telecommuni-cations and Information Systems

Security InstructionNSW........................................ nonsecure warningNTCS-A .......... Navy Tactical Command System-

AfloatNTCSS ............Naval Tactical Command Support

SystemNT DII COE...................... nodal terminal defense

information infrastructurecommon operating environment

NTIA.............. National Telecommunications andInformation Administration

NTP............................... naval tactical publicationNTS..................naval telecommunications system

OCAC ....... operations control and analysis centerOEO ......................other expeditionary operationsOMFTS .......... operational maneuver from the seaOPCON................................... operational controlOPLAN ...........................................operation planOPNAVINST.............. Chief of Naval Operations

InstructionOPORD ........................................ operation orderops .........................................................operationsOPSEC ................................... operations securityOPT..............................operational planning teamOSCC ..............operational systems control centerOSPF................................. open shortest path firstOTCIXS ................. Officer in Tactical Command

Information Exchange SystemOTH ............................................ over the horizon

P .................................................................priorityPACOM ....................................Pacific CommandPAL.............................................preaffiliation listPAO ........................... public affairs officer/officePC.............................................personal computerPCMCIA ......... Personal Computer Memory Card

International AssociationPCMT.......... personal computer message terminalPDR.......................................... predefined reportsPHIBRON........................... amphibious squadronPIN ....................... personal identification numberPIP........................ product improvement programPIR .....................priority intelligence requirement

PLA................................... plain language addressPLAD.................plain language address directoryPLGR ................precise lightweight GPS receiverPLI ..........................position location informationPLIS ......... Position Location Information SystemPLRS .......... Position Location Reporting SystemPOTS...........................plain old telephone systemppm .............................. pulse position modulationPPP.................................... point-to-point protocolPR..................................................... primary zone

QuadCon ..............................Quadruple Container

R................................................................. routineRadBn ............................................ radio battalionRAM ................................random access memoryRBECS.................. Revised Battlefield Electronic

CEOI SystemRCU ........................................ remote control unitRDA............ Requirement Development AnalysisRECON OPS................reconnaissance operationsRED .............................. record of emergency dataregt .......................................................... regimentRF................................................. radio frequencyRISC................ reduced instruction set computingRLT.................................regimental landing teamRMC........................ remote multiplexer combinerRPC.....................................remote procedure callRRT............................. radio reconnaissance teamRSINISS..............Revised SINCGARS integrated

COMSEC module, nonintegratedCOMSEC module support software

SABER...situational awareness beacon with replySABRS...... Standard Accounting, Budgeting, and

Reporting SystemSACC...........supporting arms coordination centerSADL................Situational Awareness Data LinkSAM.....................................surface-to-air missileSAR........................................... search and rescueSARC.......surveillance and reconnaissance centerSASS....................... supporting arms special staffSASSY........ Supported Activities Supply SystemSATCOM.......................satellite communicationsSAW.................. standard application workstationSBB......................................... switched backbone

O-8 ________________________________________________________________________________________________ MCWP 6-22

SCAMP...............sensor control and managementplatoon

SCI .............sensitive compartmented informationSCR....................................... single-channel radioSCSI ...................small computer system interfaceSECNAVINST. Secretary of the Navy instructionSECTEL......................................secure telephoneSES............................... sensor employment squadSGT MAJ....................................... sergeant majorSHF ......................................super high frequencySI .............................................special intelligenceSIDS.....secondary imagery dissemination systemSIGINT ...................................signals intelligenceSINCGARS................. single-channel ground and

airborne radio systemSIP........................ systems improvement programSIPRNET ............... secret internet protocol router

networkSJA........................................ staff judge advocateSL.................................................... switch locatorSLCP............. Ship’s Loading and Characteristics

PamphletSLRP.... survey, liaison, and reconnaissance partyS&M.............................scheduling and movementSMART-T........Secure Mobile Anti-Jam Reliable

Tactical TerminalSMTP ...................... simple mail transfer protocolSMU................................. smart multiplexing unitSNAP .........Shipboard Nontactical ADP ProgramSNAPIII ....................Shipboard Nontactical ADP

Program IIISNMP........ simple network management protocolSOA ...........................sustained operations ashoreSOCOM ................................ Southern CommandSOP .........................standing operating procedureSPE.................. systems planning and engineeringSPEED ............system planning, engineering, and

evaluation deviceSPMAGTF .....................special purpose MAGTFSqdn ........................................................squadronSRO...............sensitive reconnaissance operationsSSCC..... special security communications centralSSCT.........special security communications teamSSES ..................ship’s signals exploitation spaceSSN ................................... social security numberSSO ................................... special security officer

SSU ...................................... SIGINT support unitSTANAG .....................standardization agreementSTAR-T .............Super High Frequency Tri-Band

Advanced Range Extension TerminalSTEP ......................... standard tactical entry pointSTOM ........................ship-to-objective maneuverSTU-III................... secure telephone unit-type IIISUADPS ..............Shipboard Uniform Automated

Data Processing SystemSYSCON.......................................systems control

TAC ........................................................... tacticalTACAN............................... tactical air navigationTACC........................ tactical air command centerTACC(A) .......... tactical air control center (afloat)TACFIRE............................................ tactical fireTACINTEL............................ tactical intelligenceTACLOG .........................tactical-logistical groupTACO II .........Tactical Communications ProtocolTACON..........................................tactical controlTACP .............................. tactical air control partyTACSAT.......................................tactical satelliteTAD .......................................tactical air direction TADC.......................... tactical air direction centerTADIL .................tactical digital information linkTADIXS A/B .............. Tactical Data Information

Exchange System-Subsystem A/BTAOC....................... tactical air operations centerTAOM.................... tactical air operations moduleTAR ......................................... tactical air requestTARGET.......... Theater Analysis and Replanning

Graphical Execution ToolkitTASS............tactical automated switching systemTATC.............................tactical air traffic controlTBM..................................theater ballistic missileTBMCS....................... theater battle management

core systemTCAC.......... technical control and analysis centerTCAC PIP ...... tactical control and analysis center

product improvement programTCAE....... Army Technical Control and Analysis

ElementTC-AIMS................Transportation Coordinators’

Automated Information forMovement System

TCC...................... tactical communications center


TCIM ...............tactical communications interfacemodule

TCO .............................tactical combat operationsTCP .........................transmission control protocolTDBM................. technical database managementTDDS ................ Tactical Receive Equipment and

Related Applications ProgramData Dissemination

TDMA..................... time division multiple accessTDN ..................................... tactical data networkTDS........................................ tactical data systemTECHCON..................................technical controlTELNET ................. telecommunications networkTERPES ........Tactical Electronic Reconnaissance

Processing and Evaluation SystemTIBS...........tactical intelligence broadcast serviceTM ............................................. technical manualTMIP........ Theater Medical Information ProgramTNAPS+...............Tactical Network Analysis and

Planning System PlusT/O ....................................... table of organizationTOW ........tube-launched, optically tracked, wire-

command link guided missileTPFDD... time-phased force and deployment dataTRANSEC ...........................transmission securityTRE..............................tactical receive equipmentTRI-TAC............................... Tri-Service Tactical

Communications SystemTRIXS........ Tactical Reconnaissance Intelligence

ExchangeTRSS.......................tactical remote sensor systemTSCM...... technical surveillance countermeasures

TSN...................................... track supervision netTSO..................telecommunications service orderTSR ...............telecommunications service requestTTP ................ tactics, techniques, and procedures

UAV................................unmanned aerial vehicleUHF ....................................... ultrahigh frequencyULCS ...............................unit-level circuit switchUNC.............................United Nations CommandUNIX ........an open-architecture operating systemUPS ......................... uninterruptible power supplyURL ............................... uniform resource locatorUSA .......................................United States ArmyUSAF ...............................United States Air ForceUSMC ....................... United States Marine CorpsUSN ....................................... United States NavyUSTRANSCOM ....................U.S. Transportation

Command

VHF ...................................... very high frequencyVIXS .......... Video Information Exchange SystemVMF................................variable message formatVMFA.................. Marine fighter attack squadronVPN ...........................................voice product netV/STOL ........... vertical/short takeoff and landing

W................................................................... wattsWAN........................................ wide area networkWWW ..........................................world wide web

XO...............................................executive officer

O-10_______________________________________________________________________________________________ MCWP 6-22

Section II. Definitions

A

Allied Communication Publication 123 (ACP123)—ACP 123 defines a military messagingstandard. Allied nations have agreed to adopt theACP 123 Military messaging standard to replacethe current human-interactive ACP 127 proce-dures. The ACP 123 standard is based on the opensystem X.400 message standard, which providesnot only the format of the message, but the proce-dures and services required in its delivery.

Allied Communication Publication 126 (ACP126)—ACP 126 defines a character-oriented mes-sage standard for use in operations with alliedforces.

application—A system or problem to which acomputer is applied.

asynchronous—Pertaining to an operation thatoccurs without a regular or predictable time rela-tionship to a specified event.

asynchronous transfer mode (ATM)—A meth-od of digitized data transmission based on fixed-length cells. ATM can carry multiple types of da-ta—text, voice, imagery, and video—at highspeeds.

asynchronous transmission—Data transmissionin which the instant that each character, or blockof characters, begins to be transmitted is arbitrary.However, the time of occurrence of each signalrepresenting a bit within the character or block ispredictable.

B

back lobe—Pertaining to a directional antenna,the radiation occurring in a direction 180 degreesfrom that of the main axis of radiation.

backbone—The high traffic density connectivityportion of any communications network.

bandwidth—The difference between the limitingfrequencies of a continuous frequency band ex-pressed in hertz (cycles per second). The termbandwidth is also loosely used to refer to the rateat which data can be transmitted over a givencommunications circuit. In the latter usage, band-width is usually expressed in either kilobits persecond (kbps) or megabites per second (Mbps).

baseband—The original band of frequencies pro-duced by a transducer, such as a microphone, tele-graph key, or other signal-initiating device, beforeinitial modulation. Baseband describes the signalstate before modulation, before multiplexing, fol-lowing demultiplexing, and following demodula-tion.

bit error rate—The number of erroneous bits di-vided by the total number of bits transmitted, re-ceived, or processed over some specified period.

bomb—A computer program, generally mali-cious in nature, hidden within or emulating anoth-er program and designed to execute at a specificfuture time or on the occurrence of a specificevent.

C

client-server architecture—A computer net-working architecture, client-server defines a soft-ware architecture and not a hardware architecture.A client software entity (client) requests a servicefrom a server software entity (server), which inturn fulfills the request. To fulfill the request theserver may provide data, perform processingtasks, control a peripheral, or request the servicesof another server. A client can request servicesfrom multiple servers and a server can service

Communications and Information Systems _____________________________________________________________ O-11

multiple clients. Because clients and servers aresoftware entities, they can reside on the samecomputer or be on different computers in a net-work. Servers are designated according to the ser-vices provided. A server providing access tocommunications services would be called a com-munications server.

collision detection—A method by which a colli-sion is detected on a LAN transmission medium.A collision occurs when more than one simulta-neous transmission is attempted on the LAN.

combat information—Unevaluated data, gath-ered by or provided directly to the tactical com-mander which, due to its highly perishable natureor the criticality of the situation, cannot be pro-cessed into tactical intelligence in time to satisfythe user’s tactical intelligence requirements.

communications—A method or means of con-veying information of any kind from one personor place to another. (Joint Pub 1-02).

conditioned diphase signaling—A robust formof digital baseband signaling employed by TRI-TAC equipment in which bits are encoded in thephase of the signal.

D

data terminal equipment—A networked device,such as a PC, that is capable of transmitting andreceiving digital data signals over a communica-tions circuit.

digital backbone—A term loosely applied to theTRI-TAC-based circuit switched communicationsnetwork employed by the Marine Corps. Usedsynonymously with switched backbone.

digital signature function—A cryptographictechnique for authenticating electronic docu-ments, much as a written signature verifies the au-

thenticity of a paper document. A message isencrypted with the sender’s digital private keyand the recipient decrypts the signature with thesender’s digital public key.

digital switch—A switch that performs time-di-vision multiplexed switching of digitized signals.When used with analog inputs analog-to-digitaland digital-to-analog conversions are necessary.

digital transmission—The transmission of a dig-ital bit stream that may include digitized voice ordata or both. The transmission signal itself may beeither discrete or continuous (analog).

digital transmission group—A group of digi-tized voice and/or data channels that have beencombined (multiplexed) into a single digital bitstream for transmission over communications me-dia.

DISA megacenter—One of several large dataprocessing centers maintained and operated byDISA, such as the Cleveland Center, which sup-ports the Defense Finance and Accounting Ser-vice.

domain name—The symbolic name assigned to ahost on an IP network. Syntactically the domainname consists of a sequence of names separatedby periods. A domain is a logical grouping of IPhosts.

domain name system—The online distributeddatabase system used to relate (map) readable, al-phabetic domain names with numeric IP address-es.

double sideband—The transmission of a modu-lated carrier wave accompanied by both sidebandsresulting from modulation. The upper sidebandcorresponds to the sum of the carrier and modula-tion frequencies, whereas the lower sideband cor-responds to the difference between the carrier andthe modulation frequencies.

O-12_______________________________________________________________________________________________ MCWP 6-22

F

forward lobe—Pertaining to a directional anten-na, the radiation occurring along the main axis ofradiation.

full duplex—Refers to a mode of transmission inwhich communication between two terminalstakes place in both directions simultaneously.

G

gateway—In a communications network, a net-work node that is equipped for interfacing withanother network that uses different protocols. Theterm is loosely applied to a computer or computersoftware configured to perform the tasks of agateway.

H

half-duplex—Refers to a mode of transmission inwhich communication between two terminals oc-curs in either direction, but in only one directionat a time. This is the typical mode of operation fortactical single-channel radios.

host—In a computer network, a computer thatprovides services to end users. Those services areconsidered to be hosted on that computer. Theterm host also refers to the computer on a networkthat performs network control functions.

I

IDNX—Integrated Digital Network Exchange, orIDNX, devices provide automated link bandwidthmanagement that allocates available circuits asneeded. These devices are used at network nodesto allow for a virtual network with automatic rout-ing and rerouting. IDNX devices are easily up-graded to asynchronous transfer mode (ATM)capability.

information system—The organized collection,processing, transmission, and dissemination of in-formation, in accordance with defined procedures,whether automated or manual. In informationwarfare, this includes the entire infrastructure, or-ganization, and components that collect, process,store, transmit, display, disseminate, and act oninformation. (Joint Pub 1-02)

in-line network encryptor—A cryptographic de-vice that permits the transmission of classified da-ta on unclassified networks or SCI data on secretnetworks. A key feature of in-line network en-cryptors is that they only encrypt the data, not theaddress information. In-line network encryptors,through software configuration and appropriatekeying material, may be used to link multipleLANs of one classification level by using a datacommunications network operating at a lowerclassification level.

internet—The worldwide interconnection of in-dividual computer networks operated by govern-ment, industry, academia, and private parties. Theinternet was originally developed by the DefenseAdvanced Research Projects Agency (DARPA) tointerconnect laboratories and academic institu-tions engaged in government-sponsored research.

internet protocol (IP)—A DOD standard proto-col designed for use in interconnected systems(internets) of packet-switched communicationsnetworks. The IP provides for transmitting blocksof data called datagrams from sources to destina-tions, where sources and destinations are identi-fied by fixed length addresses (IP addresses).

IP address—A unique numerical address as-signed to each host on an IP network based on astandard scheme and by a central agency. Used tocommunicate between hosts on the network.

isochronous—Pertaining to data transmissions inwhich the time interval separating two corre-sponding signal state transitions is equal to the


unit interval of that signal state or a multiple ofthe unit interval.

J

Joint Army, Navy, Air Force Publication(JANAP)-128 local area network—A joint stan-dard for AUTODIN message formats and proce-dures. A data communications system that lieswithin a limited geographic area, has a specificuser group, and uses a specific topology. A LANis not part of a public switched telecommunica-tions network although it may be connected tosuch a network.

L

loop—A communication channel from a switch-ing center or an individual message distributionpoint to the user terminal. In a telephone system, apair of wires running from a central office to asubscriber’s telephone.

M

media access method—The method by which aterminal on a LAN accesses the LAN transmis-sion medium.

modem—In computer communications, a deviceused for converting digital signals into, and recov-ering them from, quasi-analog signals that aresuitable for transmission over analog communica-tions channels.

modulation—The process of varying a character-istic (e.g., frequency, phase, amplitude) of a carri-er signal in accordance with an informationbearing signal.

multichannel—Pertaining to communications,usually full duplex, on more than one channel si-

multaneously. Multichannel transmission may beaccomplished by time-, frequency-, code-, andphase-division multiplexing, or space diversity.

multiplexer—A device that combines (multiplex-es) multiple input signals (information channels)into an aggregate signal (common channel) fortransmission.

mult ipurpose in ternet mai l ex tens ion(MIME)— MIME is the internet standard proto-col for sending multipart, multimedia, and binarydata by using e-mail. Typical uses of MIME in-clude sending images, audio, word processingdocuments, programs, or even plain text fileswhen it is important that the mail system does notmodify any part of the file. MIME also allows forlabeling message parts so that a recipient (or mailprogram) may determine what to do with them.The MIME internet standard is described in RFC-1521.

O

open systems—A system with characteristics thatcomply with specific, publicly maintained (ratherthan proprietary), readily available standards.Such a system, by virtue of adherence to the stan-dard, may be connected to other systems thatcomply with those same standards.

order wire—An auxiliary circuit or channel foruse by operating and/or maintenance personnelfor communications incident to establishing, op-erating, maintaining, and controlling communica-tions facilities, systems and equipment.

P

packet switch—A switch that breaks messagesinto data packets for transmission over a networkand reassembles data packets into messages uponreceipt.

O-14_______________________________________________________________________________________________ MCWP 6-22

protocol—A formal set of specifications govern-ing the format and control of interaction amongterminals communicating over a network.

R

radio-wire integration—The combining of wirecircuits with radio functions.

relational database—A database that is based onthe relational model. The relational model relieson the mathematics of set theory, thereby provid-ing a solid theoretical base for the management ofdata. Relational databases are typically easier touse and maintain than nonrelational databases.The relational model provides for improved dataavailability, data integrity, and data security be-cause the model rigorously defines these featuresas part of the database, not as part of the processesthat maintain the database.

repeater—A device that amplifies, reshapes, re-times or performs a combination of these func-tions on an input signal for retransmission. Theinput signal may be either analog or digital. Re-peaters are used to extend the distance that net-work signals can be transmitted.

request for comment (RFC)—A document usedby the Internet Activities Board (the governingbody for internet protocols) to develop and toconfiguration manage internet protocols.

router—A device used to interconnect two ormore data communication networks. The routerreads the network address of all data packets andforwards to the addressee via the best availablecommunications path.

S

simple mail transfer protocol (SMTP)—The in-ternet standard protocol used to facilitate the ex-change of e-mail across an internet. SMTP

establishes a link to a remote host and handles thetranslation of different mail file formats betweenhosts. To arrange for mail delivery, e-mail appli-cations running on a particular host must make acall to SMTP which then handles the delivery.SMTP uses internet domain names to find a con-nection, relying on the DNS to make the transla-tions to IP numeric addresses.

simple network management protocol (SN-MP)—The internet standard protocol used to pro-vide the network management capabilities neededto monitor and control a network.

simplex—Refers to a mode of operation in whichcommunication between two terminals can takeplace in only one direction.

single sideband—A mode of communications inwhich the carrier wave and one sideband are sup-pressed. Single sideband operation requires lesspower at the transmitter for the same effectivesignal at the receiver, a narrower frequency bandcan be used, and the signal is less affected by se-lective fading or interference.

skywave—A radio wave that reaches the receiv-ing location after refraction from the ionosphere.

synchronous—Pertaining to an operation that oc-curs with a regular or predictable time relation-ship to a specified event.

systems network architecture (SNA)—A pro-prietary network architecture developed by IBM.

T

T1 circuit—A communications circuit providing1.544 Mbps capacity.

TELNET—The internet standard virtual terminalprotocol that is used for remote terminal connec-tion service. TELNET allows a remote terminal to


login to and access services from a host computerby using dial-in or other network connections.

timing—The synchronization of communica-tions signals. Of critical importance for digitalcommunications networks and for secure commu-nications.

token—A bit pattern used in the token ring andtoken bus media access methods for controllingaccess to the medium.

topology—In the context of a communicationsnetwork, the term topology refers to the way inwhich the stations or terminals attached to the net-work are interconnected. The common topologiesfor local area networks are the star, ring, and bus.

transponder—1. An automatic device that re-ceives, amplifies, and retransmits a signal on adifferent frequency. 2. An automatic device thattransmits a predetermined message in response toa predefined received signal. (Note: Examples oftransponders are identification, friend or foe (IFF)systems and air-traffic-control secondary radar(beacon radar) systems.) 3. A receiver-transmitterwhich will generate a reply signal upon proper in-terrogation. (Joint Pub 1-02) 4. Device in a com-munications satellite that receives a signal from asending earth station and retransmits the signal toone or more receiving earth stations.

Trojan horse—A computer program containingan apparently or actually useful function that alsocontains hidden functions that allow unauthorizedcollection, falsification, or destruction of data.

trunk—A trunk is a single circuit between twoswitching centers or individual message distribu-tion points. This is in contrast to a loop, which is asingle circuit between the switching center ormessage distribution point and the individual sub-scriber terminal. A trunk group is formed by twoor more trunks between the same two points.

trusted workstation—A workstation that meetsstrict security accreditation standards and is con-sidered secure from exploitation.

V

virus—A self-replicating malici attaches itself toan application program or other executable

system component.

W

wide area network—A term loosely applied toany communications network extending over alarge geographic area.

worm—An independent computer program de-signed to self-replicate from computer to comput-er across computer networks often cloggingnetworks and monopolizing computer system re-sources as it spreads.

X

X.400—Open system standard for e-mail.

X.500—Open system standard for network direc-tory service.

X.509 certificate—Open system standard for se-curity. Many internet protocols and applicationsemploy public-key technology for security pur-poses and require a public-key infrastructure tosecurely manage public keys for widely-distribut-ed users or systems. The X.509 standard providesbasis for such an infrastructure, defining data for-mats and procedures related to distribution ofpublic keys via certificates digitally signed bycertification authorities.

(reverse blank)

Appendix P

References and Related Publications

Standardized Agreements (STANAGs)

4206 The NATO Multi-Channel Tactical Digital Gateway—System Standards4207 The NATO Multi-Channel Tactical Digital Gateway—Multiplex Group Framing

Standards4208 The NATO Multi-Channel Tactical Digital Gateway—Signalling Standards4209 The NATO Multi-Channel Tactical Digital Gateway—Standards for Analogue to Dig-

ital Conversion of Speech Signals4210 The NATO Multi-Channel Tactical Digital Gateway—Cable Link Standards4211 The NATO Multi-Channel Tactical Digital Gateway—System Control Standards4212 The NATO Multi-Channel Tactical Digital Gateway—Radio Relay Link Standards4213 The NATO Multi-Channel Tactical Digital Gateway—Data Transmission Standards5040 NATO Automatic and Semi-Automatic Interfaces Between the National Switched

Telecommunications Systems of the Combat Zone and Between These Systems andthe NATO Integrated Communications System (NCIS)—For the Period 1979 to the1990s

Allied Communications Publications (ACPs)

121 Communications Instructions—General122 Series Communications Instructions—Security123 Common Messaging Strategy and Procedures126 Communications Instructions Teletypewriter Procedures167 Series Glossary of Communications-Electronics Terms

Department of Defense Publications

Directives (DODDs)

5200.1 Information Security Program5200.28 Security Requirements for Automated Information Systems (AISs)8320.1 DOD Data Administration

Instruction (DODI)

4630.8 Procedures for Compatibility, Interoperability, and Integration of Command, Control,Communications and Intelligence (C3I) Systems

P-2 ___________________________________________________________________________________________ MCWP 6-22

Chairman, Joint Chiefs of Staff (CJCS) Publications

Joint Publications (Joint Pubs)

0-2 Unified Action Armed Forces (UNAAF)1-0 DOD Dictionary of Military and Associated Terms3-0 Doctrine for Joint Operations5-0 Doctrine for Planning Joint Operations5-03.1 Joint Operation Planning and Execution System—Volume 16-0 Doctrine for Command, Control, Communications, and Computer (C4) Systems

Support to Joint Operations6-02 Joint Doctrine for Employment of Operational/Tactical Command, Control,

Communications, and Computer Systems6-02.1 Joint Connectivity Handbook

Manuals (CJCSMs)

6231.01A Manual for Employing Joint Tactical Communications—Joint Tactical SystemsManagement

6231.02 Manual for Employing Joint Tactical Communications—Joint Voice Communi-cations Systems

6231.03A Manual for Employing Joint Tactical Communications—Joint Data Systems6231.04 Manual for Employing Joint Tactical Communications—Joint Transmission Sys-

tems6231.05 Manual for Employing Joint Tactical Communications—Joint Communications

Security6231.06 Manual for Employing Joint Tactical Communications—Joint Technical Control

Procedures and Systems6231.07A Manual for Employing Joint Tactical Communications—Joint Network Manage-

ment and Control

Instructions (CJCSIs)

6110.01 CJCS-Controlled Tactical Communications Assets6230.03 Communications-Electronics Operation Instructions/Signal Operation Instruc-

tions

Joint Army, Navy, Air Force Publications (JANAPs)

128 Automatic Digital Network (AUTODIN) Operating Procedures137 Automatic Voice Network (AUTOVON) Operating Procedures

Communications and Information Systems _________________________________________________________ P-3

Army Publications

Field Manuals (FMs)

11-24 Signal Tactical Satellite Company11-25 Signal Troposcatter Company11-30 MSE Communications in the Corps/Division11-32 Combat Net Radio Operations11-41 Signal Support: Echelons Corps and Below (ECB)11-43 Signal Leader’s Guide11-50 Combat Communications within the Division (Heavy and Light)24-2 Spectrum Management24-11 Tactical Satellite Communications24-18 Tactical Single-Channel Radio Communications Techniques24-19 Radio Operator’s Handbook24-26 Tactical Automatic Switching100-6 Information Operations

Technical Manuals (TMs)

Operator’s Manual for SINCGARS Ground Combat Net Radio, ICOM ManpackRadio AN/PRC-119A (NSN 5820-01-267-9482) (EIC: L2Q) Short Range Ve-hicular Radio AN/VRC-87A (5820-01-267-9480) (EIC: L22) Short Range Ve-hicular Radio with Single Radio Mount AN/VRC-87C (5820-01-304-2045)(EIC: GDC) Short Range Vehicular Radio with Dismount AN/VRC-88A (5820-01-267-9481) (EIC:L23) Short Range Vehicular Radio with Dismount and SingleRadio Mount AN/VRC-88C (5820-01-304-2044) (EIC: GDD) Short Range/LongRange Vehicular Radio AN/VRC-89A (5820-01-267-9479) (EIC: L24) LongRange Vehicular Radio AN/VRC-90A (5820-01-268-5105)(EIC:L25) ShortRange/Long Range Vehicular Radio with Dismount AN/VRC-91A (5820-01-267-9478) (EIC: L26) Long Range/Long Range Vehicular Radio AN/VRC-92A(5820-01-267-9477) (EIC: L27)

SINCGARS ICOM Ground Radio Operator’s Pocket Guide for Manpack RadioAN/PRC-119A (NSN 5820-01-267-9482) (EIC: L2Q) Short Range VehicularRadio AN/VRC-87A (5820-01-267-9480) (EIC: L22) Short Range Vehicular Ra-dio with Single Radio Mount AN/VRC-87C (5820-01-304-2045) (EIC: GDC)Short Range Vehicular Radio with Dismount AN/VRC-88A (5820-01-267-9481)(EIC: L23) Short Range Vehicular Radio with Dismount and Single Radio MountAN/VRC-88C (5820-01-304-2044) (EIC: GDD) Short Range/Low Range Vehic-ular Radio AN/VRC-89A (5820-01-267-9479) (EIC: L24) Long Range Vehicu-lar Radio AN/VRC-90A (5820-01-268-5105) (EIC: L25) Short Range/LongRange Vehicular Radio with Dismount AN/VRC-91A (5820-01-267-9478) (EIC:L26) Long Range/Long Range Vehicular Radio AN/ VRC-92A (5820-01-267-9477) (EIC: L27)

SINCGARS ICOM Ground Radios used with Automated Net Control Device(ANCD) AN/CYZ-10 Operator’s Pocket Guide Radio Sets Manpack Radio AN/PRC-119A) (NSN: N/A) (EIC: N/A) Vehicular Radios (AN/VRC-87A-C thruAN/VRC-92A) (NSN: N/A) (EIC: N/A)

11-5820-890-10-2

11-5820-890-10-6

11-5820-890-10-1

P-4 ___________________________________________________________________________________________ MCWP 6-22

Operator’s Manual for SINCGARS Ground Combat Net Radio, ICOM ManpackRadio, AN/PRC-119A (NSN 5820-01-267-9482) (EIC: L2Q), Short Range Ve-hicular Radio AN/VRC-87A (5820-01-267-9480) (EIC: L22), Short Range Ve-hicular Radio with Single Radio Mount AN/VRC-87C (5820-01-304-2045)(EIC: GDC), Short Range Vehicular Radio with Dismount AN/VRC-88A (5820-01-267-9481) (EIC: L23), Short Range/Long Range Vehicular Radio AN/VRC-88C (5820-01-304-2044) (EIC: 6DD), Short Range/Long Range Vehicular Ra-dio AN/VRC-89A (5820-01-267-9479) (EIC: L24), Long Range Vehicular Ra-dio AN/VRC-90A (5820-01-268-5105) (EIC: L25), Short Range/Long RangeVehicular Radio with Dismount AN/VRC-91A (5820-01-267-9478) (EIC: L26),Short Range/Long Range Vehicular Radio AN/BRC-92A (5820-01-267-9477)(EIC: L27) used with Automated Net Control Device (ANCD) (AN/CYZ-10) Precision Lightweight GPS Receiver (PLGR) (AN/PSN-11) Secure Tele-phone Unit (STU) Frequency Hopping Multiplexer (FHMUX)

Navy Publications

Navy Doctrine Publications (NDPs)

5 Naval Planning 6 Naval Command and Control

Navy Warfare Publication (NWP)

4 Basic Operational Communication Doctrine

Navy Technical Publications (NTPs)

3 Telecommunications Users Manual4 Naval Telecommunications Procedures—Fleet Communications5 Naval Telecommunications Procedures—Voice Communications6 Naval Telecommunications Procedures—Spectrum Management Manual

Office of the Chief of Naval Operations Instruction (OPNAVINST)

5510.1H Messages Requiring Special Handling, Information Security Program

Marine Corps Publications

Doctrine Publications (MCDPs)

1 Warfighting1-1 Strategy1-2 Campaigning1-3 Tactics2 Intelligence3 Expeditionary Operations4 Logistics5 Planning6 Command and Control

11-5820-890-10-8


Warfighting Publications (MCWPs)

0-1.1 Componency2-1 Intelligence Operations3-1 Ground Combat Operations (in development)3-2 Aviation Operations (in development)3-25.5 Direct Air Support Center Handbook3-25.7 Tactical Air Operations Center Handbook4-1 Logistics Planning and Operations (in development)5-1 Marine Corps Planning Process (in development)

Reference Publications (MCRPs)

5-2A Operational Terms and Graphics6-22A TALK II-SINCGARS: Multiservice Communications Procedures for the Single-

Channel Ground and Airborne Radio System6-22B Multiservice Procedures for Spectrum Management in a Joint Environment6-22C Radio Operator’s Handbook (in development)6-22D Field Antenna Handbook (in development)6-22E TTP For The AN/TSQ-1

Orders (MCOs)

1510.83A Individual Training Standards (ITS)P3000.18 Marine Corps Planner’s Manual5236.2 ADP Resources Delegation Program Order5271.4 E-Mail Policy and GuidanceP5510.14 AIS Security Program

Bulletin (MCBul)

3000 Table of MARES Reportable Equipment

Technical Manuals (TMs)

Operator’s Manual for Multiplexers/Demultiplexers TD-1389(P)(V)1/G (NSN5895-01-188-8820) (EIC: L2R) TD-1389(P)(V)2/G (5895-01-186-3235) (EIC:L2N)

Operational and Organizational Maintenance Instruction for the AN/PRC-104B(V)1, (V)4 Radio Set

Operator’s and Organizational Maintenance Instruction Amplifier-Converter AM6879/URC

Instruction Manual Antenna, AS-2259/GR (FSN 5895-106-6130) and Adapter,Antenna to Antenna Base MX-9313/GR (FSN 5985-172-6518)

Operator’s Manual for Satellite Communications Terminals, AN/TSC-85B(V)1(NSN 5895-01-284-8305) and AN/TSC-85B(V)2 (5895-01-248-8308)

8B552B-10/1A

07748B-12/1

07749A/07743A-12/2

07508A-14

08347A-10/1

P-6 ___________________________________________________________________________________________ MCWP 6-22

Operator’s and Organizational Maintenance Manual for Satellite Communica-tions Terminals AN/TSC-85B(V)1 (NSN 5895-01-284-8305) and AN/TSC-85B(V)2 (5895-01-284-8308) Operation and Operator Maintenance

Operator’s and Organizational Maintenance Manual for Satellite Communica-tions Terminal AN/TSC-85B(V)1 (NSN 5895-01-284-8305) (EIC: L3F) and AN/TSC-85B(V)2 (5895-01-284-8308) (EIC: N/A)

Operator’s Manual for Satellite Communications Terminals AN/TSC-93B(V)1(NSN 5895-01-284-8306) and AN/TSC-93B(V)2 (5895-01-284-8307)

Operator’s and Organizational Maintenance Manual for Satellite Communica-tions Terminals AN/TSC-93B(V)1 (NSN 5895-01-284-8305) (EIC: L3E) andAN/TSC-93B(V)2 (5895-01-284-8307) (EIC: N/A)

Operator and Organizational Maintenance Switchboard, Telephone, Automatic,SB-3865(P)/TCC

Central Office Telephone, Automatic, AN/TTC-42(V)

Operator’s Manual for Multiplexer, Digital, TD-1337(V)1/G, (NSN 7025-01-112-6311), TD-1337(V)2/G (7025-01-112-6310), TD-1337(V)3/G (7025-01-112-6312), and TD-1337(V)4/G (7025-01-127-7020)

Combined Operation and Maintenance Instructions Organizational and Interme-diate Radio Terminal Set AN/TRC-170(V)3 Part Number 951100-5 (NSN 5820-01-148-3976)

Operator’s and Unit Maintenance Manual for Digital Data Modem MD-1026(P)/G (NSN 5820-01-145-4945)

Microwave Antenna Group OE-468

Operator and Troubleshooting Checklist for the Radio Terminal Set AN/MRC-142

Communications Central, AN/TSC-120

Principal Technical Characteristics of U.S. Marine Corps Communication-Elec-tronic Equipment

Ground Equipment Record Procedures

Operator’s and Organizational Maintenance Manual for Multiplexer, TD-1235(P)/TTC (NSN 5820-01-145-2460)

08347B-12/1-1

08347B-12/1-2

08348A-10/1

08348B-12/1-1

08439A-12/2-1

08440A-12/2-1

08467A-10/1

08658A-14/1

08761A-12/1

09280A-14&P/1

09543A-14

09589A-14&P/1

2000-15/2B

4700-15/1

5805-12/1


Operator’s and Unit Maintenance Manual for Multiplexer, TD-1236/G (NSN5820-01-145-2461)

Tactical Combat Operations (TCO) Technical Manual (NSN 5895-01-392-0294)

Miscellaneous Publications

Joint Manual of Regulations and Procedures for Federal Radio Frequency Management

Manual for Regulations and Procedures for Federal Radio Frequency Management (also referredto as the NTIA Manual or Redbook) (http://www.ntia.doc.gov/osmhome/redbook/redbook.html)

DISA Contingency Plan 10-95

Computer Buyer’s Guide (http://www.marcorsyscom.usmc.mil)

Ship’s Loading and Characteristics Pamphlet

5805-12/2

10149A-13&P/1-1

(reverse blank)