5-1
MARINE CORPS PLANNER'S MANUAL


CHAPTER 5

C4I DURING PLANNING AND EXECUTION


5000. INTRODUCTION. This provides a concise review of the command,
control, communications, computer, and intelligence systems available
to support deliberate planning. It will discuss WWMCCS and JOPES as
command and control medium to support Automatic Digital Network
(AUTODIN), telephone, and SATCOM during development and execution of
plans. It will discuss the use of teleconferences (MCOPSLOG, LANTCAT,
CCTLCF, etc.) as coordination tools. It will summarize the computer
systems designed to support planning and execution (MAGTF II/LOG AIS
family of systems, intelligence resources, etc.). Finally, it will
place all the preceding C4I capabilities in the context of deliberate
planning and execution, providing an overview of how each is used
during the two phases.


5001. COMMUNICATION SYSTEMS

1. Use of WWMCCS as a Communications Medium

a. General. This section describes the functional use of the
WWMCCS Intercomputer Network (WIN) as a communications medium within
the Marine Corps.

b. Background. Joint Staff Pub 0-1, UNAAF, defines WWMCCS as
"the system that provides the means for operational direction and
technical administrative support involved in the function of command
and control of U.S. military forces." The system is designed to
establish effective connectivity among the members of the defense
organization.

c. WWMCCS is not a single system, nor are there plans for it to
become one. It is a system of systems ranging from the national to
the theater level. Component systems are designed, developed, and
used to satisfy command and control requirements of the agencies,
services, or commands that use them.

d. The overarching communications bridge connecting WWMCCS
applications and data bases is called the WWMCCS Intercomputer Network
or WIN. With WIN, users may communicate with other users, review and
update data at other WWMCCS locations, and rapidly transfer data
between computers. The system enables real-time Top Secret high
communications. There are three prominent capabilities:

(1) Telecommunications Network (TELNET). TELNET is the link
between each host computer which allows the user to gain access to any
WIN host computer regardless of geographic location.

(2) Teleconference (TLCF). TLCF allows access to files of
stored electronic messages for up to 1,500 participants who are
granted access by the TLCF chairman on a need-to-know basis.

5-3

Analogous to a radio net, the TLCF may also be used to carry on an
informal (textual) dialogue among participants.

(3) File Transfer Service (FTS). FTS is used to exchange data
files within WWMCCS. Electronic mail is sent instantly to one or
multiple designated users. Unlike TLCF, FTS is user-to-user
communications. Only the individual(s) possessing the userid(s) to
which mail is sent have access to the message.

(4) Time Sharing Subsystem (TSS). TSS is the host data
storage medium. Users can transfer data stored in these files from
host to host; user to user; or between the host computer and the
user's WWMCCS terminal.

2. Use of WIN in the Marine Corps

a. General. Primarily a tool for operators, planners and
logisticians, use of WIN within the Marine Corps will range from
informal action officer communication to formal "command"
correspondence.

b. Each command with WIN access will maintain a joint crisis
action team (JCAT) user ID for access into the system. Use of
personal identification codes should be discouraged. Access to WIN
files and databases is rigidly controlled in accordance with Joint
Pubs 6-03 series. The local WIN Terminal Area Security Officer
(WATASO) is charged to ensure all use of WIN is within the scope of
these Joint Staff publications.

c. The following is policy governing the use of WIN TLCF and
WINMAIL for communications.

(1) Commands having access to WIN will establish a primary
point of contact for WIN related matters.

(2) Establishment of and changes to the JCAT ID "command
mailbox" will be announced by entering a message in the "MCOPSLOG"
TLCF at the NMCC host.

(3) Use of TLCF's and WINMAIL to transmit command originated
or informal message traffic will be governed by the procedures
presented below.

3. Procedures

a. Formal WINMAIL. Use of the WIN as a formal communications
media within the Marine Corps will be governed by the following
guidelines:

(1) All record traffic will be handled in accordance with
established procedures for AUTODIN.

(2) Command messages are formal correspondence. They have the
same import as AUTODIN messages/mailgrams.

5-4

(3) Format will be the same as for AUTODIN traffic.

(4) Drafter and releaser must be annotated on the last line of
each message.

(5) Messages will always be sent to the recipient's JCAT
"command" mailbox at their host site.

(6) Establish procedures for staffing and accountability of
all command originated messages sent/received by WIN.

(7) Use WINMAIL, vice TLCF, to transmit "close hold", limited
distribution, or "Personal For" messages.

b. Informal Messages. Informal messages may be used for rapid
information dissemination, action coordination, informal document
review, etc.

(1) Informal messages will not contain command taskings,
policy, or otherwise be directive in nature. Lack of response to an
informal message will be taken as meaning "no comment."

(2) WINMAIL or the "MCOPSLOG" TLCF will be the normal means of
transmitting informal messages.

(3) Informal messages addressed to individuals but sent to
"command mailboxes" need only be routed to the individual. No file
copy is required.

c. Internal Message Handling Procedures. Each WIN capable
command is authorized latitude to establish procedures for
transmission, receipt, and distribution of WIN messages. However,
adherence to standing classified material control procedures and
policy and procedural guidance is mandatory.

4. Teleconferences. To be written by DC/S Plans, Policies and
Operations.

5. JOPES. To be written by DC/S Plans, Policies and Operations.

6. Computer Hardware

a. WWMCCS. To be written by DC/S Plans, Policies and Operations.

b. MAGTF II/LOG AIS. To be written by DC/S Installations
and Logistics.

c. Aviation Planning Systems Hardware. To be written by DC/S
Aviation.

(1) TAMPS

(2) TAVB Logistics Planning System (TALPS)

5-5

(3) Ordinance Management Inventory System (OMIS)

(4) Standardized Conventional Ammunition Accuracy Inventory
Record (SCAAIR)

(5) Fleet Optical Scanning Ammunition Marking System (FOSAMS)

(6) On-Hands Management System (OHMS)


5002. MARINE CORPS PLANNING SYSTEMS

1. Effective deployment of MAGTF's requires detailed knowledge and
application of appropriate AIS. MAGTF II/Logistics AIS family of
systems, when coupled with other joint and USMC aviation systems,
provides MAGTF's with a powerful array of planning and execution
tools. However, full utility of these automated tools cannot be
realized without uniform standards and procedures for their use.
Accordingly, this section identifies functions associated with
operational planning and force deployment, prescribes standard tool(s)
to be used for each function, and delineates appropriate staff
agencies who will use the tool to perform function.

2. Although currently MAGTF II/LOG AIS and aviation planning systems
do not exchange information, efforts are underway to allow that
information exchange. Included in paragraph 5002.7 is a listing of
aviation support systems will interface with the MAGTF II family of
planning tools. Provided below is the policy for use of the MAGTF
planning tools available today.

3. Planning and Deployment. The Marine Corps has traditionally
excelled in deploying forces quickly and smoothly. However, current
emphasis on regional conflict and crisis response dictates that we
master all facets of deliberate planning and crisis action planning
using joint systems such as the Joint Operations Planning and
Execution System (JOPES). To this end Marines must be familiar with a
range of systems which, when used in coordination with one another,
greatly enhance our ability to plan for and deploy MAGTF's in a joint
environment. Recent history has demonstrated absolute need for
standardization and consistent use of procedures and associated tools.

4. Standard Systems. Marine Corps planning systems are classified as
either 1A (ones that support main frame systems) or 1C (stand alone
AIS that provide Marine Corps wide support on small organic workspace
computers). The following Class 1A and lC systems are Marine Corps
standard tools to support functions indicated:

a. Deployment Planning and Execution

(1) Function: Each FMF and SMCR unit must maintain a unit
database containing all T/E equipment, supplies and table of
organization personnel. Information in this database will be used to


5-6

develop and identify configuration for specific task organizations,
with equipment, supplies, and personnel down to vehicle/package level.
These databases form the basis for movement requirements.

(2) Standard System: MAGTF Deployment Support System II
(MDSS 11) is the Marine Corps Standard Class lC system which provides
unit level automated task organizing ability for deployment and
execution. This is accomplished through use of the unit's database
which is the source of information for other MAGTF II/LOG AIS systems
(CAEMS, CALM, MAGTF IT, TCAIMS). MDSS II replaces Standard
Embarkation Management System (SEMS).

(3) Responsible Office

(a) Functional Manager: HQMC (LPO)

(b) System Sponsor: COMMARCORLOGBASES (815/70)

(c) MEF/MSC Level Functional Sponsor: G-4

(4) Standard Users

(a) MAGTF CE/MSC HQ/G/S-4: Training of subordinate units.

(b) Regiment/Group/Separate Battalion/Separate Squadron
S-4 - For consolidating unit level deployment data prior to export
into MAGTF II/TC AIMS.

(c) Battalion/Sguadron/Separate Company: S-4, Development
of sourced/refined deployment data in support of particular operation;
development of shipping label information for input into LOGMARS
format labels.

b. Operational Planning Including Development of JOPES TPFDD's

(1) Function: Planners need system capability of providing
all functionality of JOPES in garrison and while deployed. This
includes building MAGTF movement requirements, estimating airlift and
sealift, computing sustainment, sourcing sustainment through War
Reserve System (WRS) And generating time phased force and deployment
data (TPFDD). MAGTF'S also require means of uploading a TPFDD to and
downloading a TPFDD from JOPES.

(2) Standard System: MAGTF planning system II (MAGTF II) is
the standard Class IC system which provides MAGTF planners with
automated means of selecting and tailoring MAGTF units/detachments
using either data extracted from MDSS II or JOPES, or data generated
within MAGTF II, assigning unit line numbers (ULN's), calculating
gross sustainment requirements, estimating strategic lift
requirements, transmitting movement data to JOPES, and a means of
manipulating JOPES data off line. MAGTF II replaces MAGTF I Lift
Model.


5-7

(3) Responsible Office

(a) Functional Manager: HQMC (LPO)

(b) System Sponsor: COMMARCORLOGBASES (815/70)

(c) MEF/MSC Level Functional Sponsor: G-5

(4) Standard Users

(a) MAGTF CE: G-5/3/S-3, G/S-4 - Development of force
deployment requirements; consolidation of MAGTF II imports from
subordinate commands; calculation of sustainment requirements/
development of sustainment deployment requirements; gross estimation
of lift requirement, and import/export deployment data to/from JOPES.

(b) MSC HO: G-3/4 - Transmitting force deployment
requirement to subordinate HQ's for detailed sourcing, tailoring and
refinement; consolidation MAGTF II imports prior to providing data
back to MAGTF CE; import/export deployment data to/from JOPES.

(c) Regiment/Group/Separate Battalion/Separate Squadron
S-3/4 - Receive planning data from MSC/MAGTF; consolidation of sourced
and refined deployment data, developed in MDSS II at unit level, prior
to providing to MSC HQ/MAGTF CE (as appropriate).

(d) MARCORLOGBASES/MARRESFOR/MARCORSYSCOM: As means of
uploading/downloading JOPES information.

c. Planning War Reserve Withdrawals

(1) Function: Most materiel necessary to sustain MAGTF's
(excluding T/E and aviation) is normally held (or acquisition managed)
by MARCORLOGBASES. MAGTF'S must plan in advance for movement of
necessary sustainment to POE's to support deployment, and have means
of actually tracking movement of sustainment during execution.

(2) Standard System: War Reserve System (WRS) is the Standard
Class 1A which provides a force planner with a automated tool to
assist in developing war reserve withdrawal plans to support
deliberate planning or crisis action planning. WRS also is means by
which MARCORLOGBASES reviews and executes withdrawal plans. WRS is a
system which has been in use for some time, but which has been
upgraded to interface with MAGTF II.

(3) Responsible Office

(a) Functional Manager: HQMC (LPO)

(b) System Sponsor: COMMARCORLOGBASES (815/70)

(c) MEF/MSC level Functional Sponsor: G-4

(4) Standard Users

5-8

(a) MEF CE: G-4 - to develop War Reserve Withdrawal plans
and source from force-held PWR stocks, based on requirements generated
by MAGTF II.

(b) MARCORLOGBASES: (807) - To validate and source War
Reserve Withdrawal plans, and for execution of such plans.

d. Air Movement Load Planning

(1) Function: Units moving via strategic airlift must
detailed produce aircraft load plans which are precisely balanced and
meet ALCE requirements in accordance with FMFM 4-6.

(2) Standard System: Computer Aided Load Manifesting System
(CALMS) is the standard Class lC system which provides an interactive
graphics tool for producing detailed aircraft load plans which meet
aircraft constraints (less commercial aircraft), based on data
imported from MDSS II. Capability has been used as standalone program
for some time.

(3) Responsible Office

(a) Functional Manager: HQMC (LPO)

(b) System Sponsor: COMMARCORLOGBASES (815/70)

(c) MEF/MSC Level Functional Sponsor: G-4

(4) Standard Users

(a) MAGTF CE/MSC HQ/Regiment/Group/Separate Battalions
Separate Squadron: G/S-4, Strategic Mobility Officer (SMO),
Embarkation Officer - Training of subordinate units; consolidation of
load plan information submitted by subordinate units for export to
JOPES. MAGTF CE provides CALMS capability to airlift element (ALE) at
a APOE to assist deploying units with last minute load plan changes/
adjustments at a APOE.

(b) Battalion/Squadron/Separate Company: S-4, Embarkation
Officer - development of detailed aircraft load plans based on MDSS II
data.

e. Ship Movement Load Planning

(1) Function: Planning of ship loads and creation of detailed
ship load plans is critical during deployment, and is particularly
demanding during crisis. Embark personnel require automated tool to
assist in generating ship load plans which meet ship loading
constraints.

(2) Standard System: Computer Aided Embarkation Management
System (CAEMS) Is Class IC system which provides interactive graphics
tool for producing amphibious and commercial ship load plans and
associated reports using embarkation data imported from MDSS II.

5-9

CAEMS replaces Ship Load Planning System (SLPS). The T-AVB automated
load planning system is being developed to facilitate real time
changes that must be accommodated when the ACE aircraft notional mix
is modified just prior to the ship load out. Of primary importance is
the integration of this information with CAEMS so that the correct
mobil facility shelter specifics are known relative to were it should
be placed within the ship, its configuration code, and proper
priorities established in transportation scheduling of the units.

(3) Responsible Office

(a) Functional Manager: HQMC (LPO)

(b) System Sponsor: COMMARCORLOGBASES (815/70)

(c) MEF/MSC Level Functional Sponsor: G-4

(4) Standard Users

(a) MAGTF CE/MSC HO/Regiment/Group/Separate Battalions
Separate Squadron: G/S-4 - training of subordinate units;
consolidation of ship load plan information submitted by subordinate
units for export to JOPES. MAGTF CE provides CAEMS to (SLE) To assist
team embark officers with last minute load plan changes/adjustments at
SPOE.

(b) Battalion/Squadron/Separate Company/Unit: S-4,
Embarkation Officer - develop detailed ship load plans, based on MDSS
II data, for amphibious/commercial ships.

f. Transportation Management

(1) Function: The force movement coordination center (FMCC)
and parent units will plan and manage the transportation requirements
of the deploying MAGTF. This includes determining the proper mode and
departure/arrival time frames, managing available transportation
assets, ensuring proper documentation and packing of unit equipment
for deployment, and full manifesting and reporting movement to proper
deployment authorities. Transportation management officers manage
movement requirements. Units must effectively and efficiently
manifest moves. Motor transport community must manage transportation
assets efficiently to maximize throughput.

(2) Standard System: Transportation Coordinators Automated
Information for Movement System (TCAIMS) is the Class lC system which
provides users with automated support for movement planning and
execution of force movements from CONUS and overseas origin to POE,
and from port of debarkation POD to destination. TCAIMS provides
deploying MAGTF elements with the capability to identify
transportation requirement (to include motor transport and material
handling equipment support) to move units from origin to an SPOE/APOE
and from an SPOD/APOD to destination. This capability allows a MAGTF
CE or MAGTF components to manage/allocate organic transportation
assets to meet internal transportation requirements. System also
identifies transport requirements in excess of a deploying unit's

5-10

capabilities for sourcing by MEF. TCAIMS provides vital link between
unit movement data (MDSS II/MAGTF II/JOPES) and the Defense
Transportation System (DTS)/MILSTAMP (Military Standard Transportation
and Movement procedures) environment. This is new capability which
fills a void not previously addressed by any USMC automated system.
TCAIMS converts MDSS II data elements into MILSTAMP elements used by
DTS. TCAIMS interfaces with USTRANSCOM's Transportation Component
Commands (TCCs): Air Mobility Command (AMC), Military Sealift Command
(MSC) and Military Traffic Management Command (MTMC). In concert with
MAGTF II/JOPES, TCAIMS provides access to intransit visibility (ITV)
information on shipments.

(3) Responsible Office

(a) Functional Manager: HQMC (LPO)

(b) System Sponsor: COMMARCORLOGBASES (815/70)

(c) MEF/MSC Level Functional Sponsor: G-4

(4) Standard Users

(a) MAGTF CE: G/S-4 - Training of subordinate units, LMCC
consolidates TCAIMS inputs from MAGTF CE/MSC's/deploying units;
reviews transportation movement control documentation (TCMD) For
correctness/completeness; submits MILSTAMP data as required;
determines transportation requirement/schedules convoys from origin to
SPOE/APOE, ensuring arrival in time to accomplish preparations for
embarkation aboard strategic carriers; and determines transportation
requirement/schedules from POD to destination.

(b) MSC HO: G-4 - Consolidate TCAIMS data from
subordinate units prior to submission to LMCC (if appropriate).

(c) Regiment/Group/Separate Battalion/Separate Squadron
S-4 - Deployment officer TCAIMS data to complete TCMD, based on
MDSS II data developed by subordinate units, prior to submission to
MSC HQ/LMCC (as appropriate).

(d) Base/Station: TMO's generate shipping documentation
and track shipments as requirement.

g. Unit Supply Management

(1) Function: Units in the FMF and selected Marine Corps
Reserve (SMCR) must account for and manage materiel assets. This
includes identifying and requisitioning shortages, as well as
maintaining accountability and visibility of on-hand assets.

(2) Standard System: Landing Force Asset Distribution System
(LFADS) is the Class lC system which provides a unit commander
visibility and control of supply assets in garrison and during
employment. LFADS is currently being converted to Asset Tracking,
Logistics and Supply System (ATLASS), which will provide the same

5-11

functionality as LFADS, but will conform more closely to DoD software
standards. LFADS/ATLASS replaces all deployable ground supply systems
(PC SASSY, etc.) currently in use.

Note: Use of LFADS, a stand-alone PC-based system, does not negate
the need for early deployment of the Deployable Force Automated
Service Center (DFASC) To provide bulk data processing in
expeditionary environment.

(3) Responsible Office

(a) Functional Manager: HQMC (LPP)

(b) System Sponsor: COMMARCORLOGBASES (815/70)

(c) MEF/MSC Level Functional Sponsor: G-4

(4) Standard Users: LFADS/ATLASS will be used down to
battalion/squadron/separate company level, and in CSSD's as
STANDARD tool for unit supply officers.

(a) Battalion/Squadron/Separate Company: Supply officer.

(b) AAOG During MPS/NALMEB Deployment: To account for MPS
equipment distributed to units.

h. Standardization of Data

(1) Function: All the preceding functions must rely on common
or compatible data to ensure interoperability. More importantly,
equipment and basic unit data (table of organization and T/E) Must be
standardized through the family of systems unless specifically changed
for a specific purpose.

(2) Standard System: MAGTF Data Library (MDL) Is a Class 1C
system which provides standard data to all MAGTF II/LOG AIS
systems. MDL is a new capability.

(3) Responsible Office

(a) Functional Manager: HQMC (LPS)

(b) System Sponsor: COMMARCORLOGBASES (815/70)

(c) MEF/MSC Level Functional Sponsor: G-4

(4) Standard Users: All of the previously mentioned systems
(including WRS) will receive source data from MDL. Data will be
distributed by the MARFOR G-4 or designated subordinate agency.


5-12

6. Policy

a. Use of the aforementioned automated systems will be mandatory
upon receipt of Version 3 of MAGTF II/LOG AIS family of systems.
MARCORLOGBASES will coordinate training for MEF's, during which,
Version 3 will be delivered and installed.

b. These systems will be used to support development of all CINC
OPLAN's and all operations and exercise deployments.

(1) Planning

(a) During normal garrison operations, units use MDSS II
to identify on-hand equipment and personnel.

(b) Responsibilities

1 MAGTF Commander (MEF/MEU/SPMAGTF). Develops force
deployment requirements in MAGTF II based on concept of operations/
task organizations for a particular operation/exercise, and exports
requirements to JOPES (distributes MAGTF II data as appropriate).

2 MSC Commanders/CG MARRESFOR. Receive distribution
of MAGTF II data or import requirements from JOPES to MAGTF II for
detailed sourcing/refinement.

3 MSC Commanders/CG MARRESFOR. Provide appropriate
MAGTF II requirement data to regiments/groups/separate squadrons/
separate battalions. Convert MAGTF II data to MDSS II and provided to
battalions/separate company.

4 Unit sources and refines deployment requirements
using MDSS II. Unit level MDSS II input consolidated at regiment/
group/separate squadron/separate battalion level, exported to MAGTF II
and provided back to MSC Commander.

5 MSC Commander consolidates MAGTF II inputs and
provides to MAGTF Commander.

(c) MAGTF Commander calculates total sustainment
requirement in MAGTF II based upon sourced/ref ined force deployment
requirement provided by MSC Commander's/CG MARRESFOR, and develops war
reserve withdrawal plan using MAGTF II/WRS interface. The MEF
Commander sources that portion of his sustainment that can be
satisfied from force-held stocks, and exports all force/sustainment
requirement (sourced and unsourced) back into JOPES.

(d) CG MARCORLOGBASES and COMMARCORSYSCOM import unsourced
sustainment requirement from JOPES/WRS (as appropriate) and source
from stocks/external agencies. Sourced data is exported back to
JOPES.

5-13

(e) Final product is sourced TPFDD with accurate level
four cargo detail resident in JOPES based on MAGTF II inputs from the
deploying MAGTF and supporting establishment. MDSS II data developed
at unit level is available to feed CAEMS, CALMS, TCAIMS, and LFADS for
logistics, transport and embarkation planning/execution.

(2) Deployment

(a) At execution, Force Movement Control Center (FMCC) and
base/station TMO use data from MDSS II exported to TCAIMS to plan
and execute unit movements. TCAIMS also provides access to ITV
information for shipments.

(b) During deployment FMCC uses MAGTF II as means of
easily manipulating JOPES data (download/upload) to adjust movements.
Deploying unit Plane Team Commanders use CALMS to create aircraft
load plans, while Team Embarkation Officers and Port Operations
Group (POG) use CAEMS to create ship load plans. DACG/POG assist
in making last minute adjustments/corrections at POE. Deploying
units use TCAIMS to generate appropriate shipping documentation
(e.g. TCMD). LMCC consolidates TCAIMS input, reviews, and
submits as required.

(c) Upon arrival, airfield or port reception party uses
MDSS II to account for equipment arriving for specific unit. LFADS/
Asset Tracking Logistic and Supply System (ATLASS) is materiel
accountability tracking tool for MPS offloads.

(d) After deployment of MAGTF and accompanying supplies,
base TMO's use TCAIMS to identify movement requirements to Military
Traffic Management Command (MTMC) or Air Mobility Command (AMC)
for movement through channels.

7. Aviation Support Systems. To be written by DC/S Aviation.

a. SNAP II and SNAP III

b. SUADPS, Release 3

c. PC SUADPS

d. NALCOMIS Phase II

e. NALCOMIS Phase III

f. SERMIS

g. CAIMS

h. TALPS

i. ALTMS

j. SALTS

5-14

5003. COORDINATING PLANNING. To be written by DC/S Plans, Policies
and Operations. FMFM 3-1 (para 2316) discusses communication planning
in relation to other staff actions and provides a basis for common
actions to be taken by MAGTF CEO's.

1. Teleconferences

2. WWMCCS

3. Planning Systems

4. Other Communications Means


5004. COORDINATING EXECUTION. To be written by DC/S Plans, Policies
and Operations.

1. Teleconferences

2. WWMCCS

a. Deplovable WWMCCS

b. Host Support

3. Planning Systems

4. Other Communications Means

a. GENSER

b. Phone

c. INMARSAT

d. SALTS

e. NALISS

f. ATAC+