JP 3-59, Joint Doctrine Tactics, Techniques, and ...edocs.nps.edu/2012/December/joint pub 3_59_1999.pdf · joint METOC officer (JMO) directs the JMFU when it is in the operational

23 March 1999

Joint Doctrine, Tactics,Techniques, and Procedures

for Meteorological andOceanographic Operations

Joint Pub 3-59

PREFACE

i

1. Scope

This publication sets forth the joint doctrineand tactics, techniques, and procedures for theplanning and execution of meteorological,oceanographic, and space environmentaloperations throughout the range of militaryoperations.

2. Purpose

This publication has been prepared underthe direction of the Chairman of the JointChiefs of Staff. It sets forth doctrine andselected joint tactics, techniques, andprocedures (JTTP) to govern the jointactivities and performance of the ArmedForces of the United States in joint operationsand provides the doctrinal basis for USmilitary involvement in multinational andinteragency operations. It provides militaryguidance for the exercise of authority bycombatant commanders and other jointforce commanders and prescribes doctrineand selected tactics, techniques, andprocedures for joint operations and training.It provides military guidance for use by theArmed Forces in preparing their appropriateplans. It is not the intent of this publication torestrict the authority of the joint forcecommander (JFC) from organizing the forceand executing the mission in a manner the JFCdeems most appropriate to ensure unity ofeffort in the accomplishment of the overallmission.

3. Application

a. Doctrine and selected tactics,techniques, and procedures and guidanceestablished in this publication apply to thecommanders of combatant commands,subunified commands, joint task forces, andsubordinate components of these commands.These principles and guidance also may applywhen significant forces of one Service areattached to forces of another Service or whensignificant forces of one Service supportforces of another Service.

b. The guidance in this publication isauthoritative; as such, this doctrine (or JTTP)will be followed except when, in the judgmentof the commander, exceptional circumstancesdictate otherwise. If conflicts arise betweenthe contents of this publication and thecontents of Service publications, thispublication will take precedence for theactivities of joint forces unless the Chairmanof the Joint Chiefs of Staff, normally incoordination with the other members of theJoint Chiefs of Staff, has provided morecurrent and specific guidance. Commandersof forces operating as part of a multinational(alliance or coalition) military commandshould follow multinational doctrine andprocedures ratified by the United States. Fordoctrine and procedures not ratified by theUnited States, commanders should evaluateand follow the multinational command’sdoctrine and procedures, where applicable.

V. E. CLARKVice Admiral, US NavyDirector, Joint Staff

For the Chairman of the Joint Chiefs of Staff:

ii

Preface

Joint Pub 3-59

Intentionally Blank

TABLE OF CONTENTS

iii

PAGE

EXECUTIVE SUMMARY ............................................................................................. v

CHAPTER IINTRODUCTION

• Overview.................................................................................................................. I-1• METOC’s Impact on Military Capability.................................................................. I-1• Role of METOC Personnel....................................................................................... I-2• METOC Joint Doctrine, Tactics, Techniques, and Procedures Overview................... I-2

CHAPTER IIJOINT FORCE METOC ORGANIZATIONS

• Overview................................................................................................................. II-1• Senior METOC Officer............................................................................................ II-1• Joint Force METOC Officer..................................................................................... II-1• Joint METOC Advisory Group................................................................................ II-1• Joint METOC Forecast Unit......................................................................................II-2• Joint Force Service Components METOC Organizations......................................... II-3• Joint Special Operations Task Force......................................................................... II-5• Joint Force Functional Component Commands METOC Organizations................... II-5

CHAPTER IIIJOINT FORCE METOC PRINCIPLES

• Overview............................................................................................................... III-1• METOC Principles................................................................................................. III-1

CHAPTER IVJOINT FORCE METOC OPERATIONS

• Overview............................................................................................................... IV-1• Joint Force METOC Functions............................................................................... IV-1• Responsibilities...................................................................................................... IV-4• SMO and JMO Duties............................................................................................ IV-4• JMFU Operations................................................................................................. IV-10• Service and Functional Component Operations Within the Joint Force................. IV-15• METOC Forecast Center...................................................................................... IV-19

iv

Table of Contents

Joint Pub 3-59

APPENDIX

A SMO and JMO Involvement in Planning.......................................................... A-1B METOC Information in Operation Plans............................................................ B-1C METOC Letters of Instruction........................................................................... C-1D METOC Data Sources From Non-METOC Operations.................................... D-1E Joint Operations Area Forecast.......................................................................... E-1F Examples of METOC Information Requirements and Responsibilities

Within a Joint Force......................................................................................... F-1G METOC Impacts to Selected Operations........................................................... G-1H Notional Joint METOC Forecast Unit Operation.............................................. H-1J Communications................................................................................................. J-1K Deployable METOC Equipment....................................................................... K-1L METOC Dial-In Bulletin Board and Web-Based Systems.................................. L-1M METOC Forecast Center.................................................................................. M-1N References........................................................................................................ N-1O Administrative Instructions............................................................................... O-1

GLOSSARY

Part I Abbreviations and Acronyms................................................................... GL-1Part II Terms and Definitions.............................................................................. GL-6

FIGURE

II-1 Meteorological and Oceanographic Structure for Joint Force Support............ II-3II-2 Typical Joint Force/Meteorological and Oceanographic Organization............ II-4IV-1 Management of Meteorological and Oceanographic Data

and Applicable Operations......................................................................... IV-2IV-2 Analysis....................................................................................................... IV-3IV-3 Forecasting................................................................................................... IV-4IV-4 Tailored Applications................................................................................... IV-5IV-5 Dissemination of Meteorological and Oceanographic Information............... IV-6IV-6 Evaluation.................................................................................................... IV-7IV-7 Determining Meteorological and Oceanographic Effectiveness.................. IV-11IV-8 JMFU Operations....................................................................................... IV-12A-1 Meteorological and Oceanographic Operation Plan Development................. A-2A-2 JOPES Deliberate Planning Process and Crisis Action Planning Process

Functional Alignment................................................................................. A-3F-1 Example of Air Refueling Forecast Parameters.............................................. F-1F-2 Examples of METOC Information Requirements and Responsibilities

Within a Joint Force.................................................................................... F-2G-1 METOC Impacts to Selected Operations....................................................... G-1J-1 Notional Meteorological and Oceanographic Communications....................... J-2M-1 Contents of the Integrated Product Set........................................................... M-3

EXECUTIVE SUMMARYCOMMANDER’S OVERVIEW

•

•

•

•

v

During military operations, adverse and/or unfavorablemeteorological and oceanographic (METOC) conditions aresometimes encountered. Accurate, timely, and reliableMETOC information can provide the commander withknowledge necessary to anticipate and exploit the best windowof opportunity to plan, execute, support, and sustain specificoperations. The joint METOC forecast unit (JMFU) conceptis the cornerstone of the three-tiered (strategic, operational,and tactical) support structure. An invaluable aspect of theJMFU is the ability to fuse METOC information from a varietyof sources into a coherent METOC picture and provide acomprehensive suite of customer tailored products. Thejoint METOC officer (JMO) directs the JMFU when it is inthe operational area, or closely coordinates when it is at aMeteorological and Oceanographic Forecast Center, andinteracts with the commander, joint task force’s (CJTF’s) staffto determine objectives and requirements that support effectiveplanning and execution of joint operations.

The JMFU’s joint operations area forecast (JOAF) providesthe official forecast for operational planning and should beused by all operational planners in the joint operational area. Itprovides a discussion and rationale for the expected METOCconditions that impact joint force operations during the forecastperiod. Component activities communicate significantdifferences between their forecasts and the JOAF with theJMFU to maximize situational awareness of present METOC

Meteorological andoceanographic (METOC)conditions will encompassthe entire range ofenvironmental phenomenaextending from the bottomof the ocean into space,and will influence allcomponents of militarycapability.

METOC forecasts can bedeveloped for the near orfar term to cover global,theater, and tactical scales.

Overview

One Theater, One Forecast

Provides an Overview of Importance of Meteorological andOceanographic (METOC) Conditions to Joint ForceOperations

Discusses Combatant Command METOC Organizations

Covers the Principles of METOC

Discusses Joint Force METOC Operations

vi

Executive Summary

Joint Pub 3-59

conditions plus facilitate assessment of future METOCconditions and their impact on joint operations. This processis universally regarded in the METOC community assupporting a “one theater, one forecast” concept. The JMOis the final authority for the JOAF and will ultimately settleany significant differences over the forecast content of theJOAF raised by participating METOC agencies.

METOC forces, data bases, products, and equipment must beresponsive to the requirements of the CJTF. To be responsive,readiness must be maintained through properly joint-trainedpersonnel with compatible joint communication capabilities.The overall effectiveness of METOC operations requiresMETOC organizations at all levels to be fully integrated in

The METOC principlesconsist of timeliness,accuracy, relevance, unityof effort, readiness, andeffectiveness.

METOC Principles

METEOROLOGICAL ANDOCEANOGRAPHIC STRUCTURE FOR JOINT

FORCE SUPPORT

Joint Task Force Organization

TacticalScale

TacticalMETOC

UnitExecution Forecast

Joint OperationsArea Forecast

JMFUJoint

MaritimeOperations

TheaterScale Strategic

MobilityOffice(r)

METOCForecastCenter

Data Management and/orConversion

Information Guidance and/orCoordination

Data and/orFeedback

StrategicData

Bases

vii

Executive Summary

the planning and execution of all military actions. The useof customer feedback will continually improve the primaryMETOC functions: sensing and collecting data, analysis,forecasting, tailoring data into information, disseminating, andevaluating.

This publication sets forth the joint doctrine and tactics,techniques, and procedures for the planning and employmentof METOC operations throughout the range of militaryoperations.

CONCLUSION

viii

Executive Summary

Joint Pub 3-59

Intentionally Blank

CHAPTER IINTRODUCTION

I-1

1. Overview

T h i s c h a p t e r s u m m a r i z e s t h emeteorological and oceanographic(METOC) contributions to US militarycapabilities as well as roles of METOCpersonnel, and provides a brief overview ofthis publication. Throughout this publication,the word “METOC” will refer to the entirerange of environmental phenomena extendingfrom the ocean floor into space. METOCphenomena include the effects on warfare ofoceanography, meteorology, and the spaceenvironment. METOC conditions influenceall aspects of military operations.

“Know yourself, know your enemy; Your victory will never be endangered.Know the ground, know the weather; Your victory will then be total......”

Sun Tzu, Chinese General, 500 B.C.

2. METOC’s Impact onMilitary Capability

During military operations, adverse and/or unfavorable METOC conditions aresometimes encountered. Accurate, timely, andreliable METOC information can provide thecommander with the knowledge necessary toanticipate and exploit the best window ofopportunity to plan, execute, support, andsustain specific operations. ExploitingMETOC information to optimize employmentof sensors, weapons, logistics, equipment, andpersonnel is key to successful militaryoperations. Likewise, military operations can

METOC conditions influence all components of military capability.

I-2

Chapter I

Joint Pub 3-59

be made needlessly difficult by failing toconsider the effects of METOC conditions.Even the most technologically advancedweapon or sensor system can be influencedby the environment. Making aggressive useof the full spectrum of METOC informationis essential to every facet of military forceplanning, deployment, and employment, aswell as system design and evaluation.

3. Role of METOC Personnel

a. METOC personnel provide tailoredinformation on the climatological (historical),current , and forecast conditions of theatmosphere, ocean, land, and spaceenvironments within or through whichweapon systems and their supportinginfrastructure operate. METOC resourcesfunction as an integral part of the joint force.Their most important function is to providethe joint force commander (JFC) andsubordinate forces with information that canenhance mission effectiveness throughoptimum employment of weapon systems.METOC personnel can provide informationimportant to personnel safety and resourceprotection; the development of newequipment, weapon systems, combat tactics,and tactical decision aids; and intelligencegathering. The Air Force, Navy, and Marine

Military operations can be made difficult by failing to consider METOC conditions.

Corps METOC personnel comprise theresources from which joint METOCoperations are tailored to meet the uniqueneeds of the JFC. (Note: In accordance withthe National Security Act of 1947, the AirForce provides personnel and resources tomeet most of the METOC information needsfor Army operations except direct support ofArmy artillery systems.)

b. US military operations have becomeincreasingly joint and frequentlymultinational. This mandates that theMETOC communities maintain or have readyaccess to a pool of expertise and resourcescapable of operating in this joint and/ormultinational arena.

4. METOC Joint Doctrine,Tactics, Techniques, andProcedures Overview

a. This publication provides the basicdoctrine, tactics, techniques, and proceduresto describe how METOC assets should beemployed in joint operations. Althoughprimarily written for the JFC andsubordinate METOC staffs, it hasapplications down to the tactical level andshould be used by all supporting METOCactivities.

I-3

Introduction

b. This publication describes thecapabilities, roles, functions, planningconsiderations, and employment andintegration concepts of each METOCelement within the joint force. It alsodescribes how the METOC Forecast Center(MFC) is involved in the process with the jointMETOC forecast unit (JMFU). Additionally,this publication describes Department of

METOC personnel provide tailored information on the conditions of theatmosphere, ocean, land, and space environments.

Defense (DOD) communications systems,which METOC forces employ, to the extentnecessary for the senior METOC officer(SMO), the joint METOC officer (JMO), andall subordinate joint elements to meet theneeds of the JFC. It describes METOCequipment and interoperability considerationsthat might assist the JFC.

I-4

Chapter I

Joint Pub 3-59

Intentionally Blank

CHAPTER IIJOINT FORCE METOC ORGANIZATIONS

II-1

1. Overview

This chapter outlines the METOCorganizational structure within joint forceoperations. It describes the role of the keyMETOC personnel, units, and forces thattypically support the commander of acombatant command (CINC) and asubordinate JFC such as a commander, jointtask force (CJTF).

2. Senior METOC Officer

Chairman of the Joint Chiefs of StaffInstruction (CJCSI) 3810.01A, “Meteorologicaland Oceanographic Operations,” specifies thatthe CINC is ultimately responsible for thedirection of METOC assets within the area ofresponsibility (AOR). The SMO is theCINC’s staff officer assigned to fulfill thisresponsibility. The SMO interacts with theCINC’s staff, the command’s Service andfunctional components, and the MFC todevelop and execute a METOC conceptof operations, identify informationrequirements, and ensure unity of effort.

3. Joint Force METOC Officer

CJCSI 3810.01A, “Meteorological andOceanographic Operations,” specifies that aJFC is ultimately responsible for the directionand coordination of METOC activities underthe JFC’s operational control. The JMO actsas the CJTF’s agent to fulfill thisresponsibility. Although the JMO and theJMO’s staff are normally on the CJTF’sOperations staff (J-3), the CJTF may organizethem as necessary to best support the mission.During execution, the JMO should collocatewith the Joint Operations Center. The JMO

“The allies...prevailed because of superior meteorologists...”

President Dwight D. Eisenhower, 1961

plays a critical role in preparing for thesuccess of the joint force mission bysupporting either deliberate planning forcontingencies, or reacting to a situationusing crisis action planning procedures.The JMO interacts with the CJTF’s staff(Intelligence (J-2), J-3, Logistics, Plans, andCommand, Control, Communications, andComputer Systems (J-6)), the components ofthe joint force, the JMFU, the SMO, and theMFC to monitor the METOC operation andcoordinate resource, communication, andinformation requirements with the SMO. TheJMO is ultimately responsible for assembling,organizing, and tasking the JMFU or, at aminimum, ensuring that the JMFU’s dutiesas outlined in Chapter IV, “Joint ForceMETOC Operations,” are carried out. It isimportant to note that the SMO could also bethe JMO.

4. Joint METOC AdvisoryGroup

The SMO has a wide range of options andresources to use in acting as the CINC’s agentfor developing and executing a METOCconcept of operations, identifying METOCinformation requirements, and ensuring unityof effort in METOC operations. For example,when planning is initiated for a joint operation,especially an operation involving multipleunified commands, the SMO has the latitudeto stand up a Joint METOC Advisory Group(JMAG) — an ad hoc group of METOCexperts from Service and componentresources — to assist in optimizing the jointtask force (JTF) METOC force.

The JMAG can assist the supported CINC’sSMO by focusing the experience, expertise,

II-2

Chapter II

Joint Pub 3-59

and technical capabilities of the METOCcommunity to support the operation beingplanned. Initial JMAG discussions couldinvolve sharing information concerning theoperation in question, requirements forMETOC products for the operation, and theappropriate data sources to produce therequired products. Subsequent discussionscould involve, for example, determiningwhether a JMFU should be established for theoperation, the need for additional METOCpersonnel to augment METOC forces, andother topics as needed by the supportedCINC’s SMO.

If the supported CINC’s SMO desires toestablish a JMAG, the SMO should considerincluding representatives from theater ServiceMETOC centers, allied and coalition METOCcomponents, or other assets as required. ACINC’s SMO will have to carefully weigh thevalue of expanding the JMAG to includeresources outside the theater with the chainof command’s desire to involve non-theaterassets in an advisory role. By bringing theseagencies together as needed into a singleforum to assist with the operation in question,the SMO should be better prepared to assistthe supported CINC in directing METOCassets within the AOR.

5. Joint METOC Forecast Unit

The JMFU concept is the cornerstone ofthe 3-tiered support structure (Figure II-1).An invaluable aspect of the JMFU is theability to fuse METOC information fromthe MFC with tactical information receivedfrom the joint forces into a coherentMETOC picture and provide acomprehensive suite of customer tailoredproducts. Under the JMO’s direction andguidance, the JMFU develops, integrates,and maintains the theater operationalMETOC data base for the JFC’s operationalarea. This operational data base will typicallyconsist of observations and forecasts from avariety of sources. The JMFU can be forwarddeployed with the JFC (Air Force combatweather team [CWT], US Navy [USN] mobileenvironmental team [MET] supporting anaval, land or air force commander, anOperations Aerology (OA) shipboardMETOC division, or a US Marine Corps[USMC] meteorological mobile facility[METMF] ashore). As an alternative, theJMO can designate a dedicated support cellor element within an MFC to provide JMFUproducts. The JMO should consider usingexisting theater forecast units as the JMFUwhenever possible.

Airborne operations depend on direct support from deployed weather teams.

II-3

Joint Force METOC Organizations

6. Joint Force ServiceComponents METOCOrganizations

Regardless of whether the CJTF organizesthe forces into Service or functionalcomponents, or a mix of both (Figure II-2),each Service involved in the operation bringsits own organic METOC resources.

a. Air Force. The Air Force forces(AFFOR) component receives directweather support at the Commander, AirForce Forces air operations center, or otherelements of the theater air control system, and

at subordinate wings, groups, and squadronsrequiring METOC support for conductingoperations. US Air Force (USAF) METOCpersonnel provide direct METOC services totheir component customers using organicMETOC personnel which are augmented, asrequired, by additional Air Force personnel.

b. Army. Per applicable Servicedirectives, the Air Force providesmeteorological services for the Army forces(ARFOR) component so the Army is ableto accomplish its assigned operationalobjectives. Army meteorological sections areresponsible for providing direct upper air

METEOROLOGICAL ANDOCEANOGRAPHIC STRUCTURE FOR JOINT

FORCE SUPPORT

Joint Task Force Organization

TacticalScale

TacticalMETOC

UnitExecution Forecast

Joint OperationsArea Forecast

JMFUJoint

MaritimeOperations

TheaterScale Strategic

MobilityOffice(r)

METOCForecastCenter

Data Management and/orConversion

Information Guidance and/orCoordination

Data and/orFeedback

StrategicData

Bases

Figure II-1. Meteorological and Oceanographic Structure for Joint Force Support

II-4

Chapter II

Joint Pub 3-59

TYPICAL JOINT FORCE/METEOROLOGICAL ANDOCEANOGRAPHIC ORGANIZATION

COMBATANT COMMANDERCINC

SMO

JMO

JMFU

JFACC

COMAFFOR

AIR FORCEWING

COMMARFOR COMNAVFOR

NAVY BATTLEGROUP

SHIPMWSS

MST MST MST

SQUADRON

COMARFOR

METOCOFFICER

METOCOFFICER

GROUNDCOMBATELEMENT

AVIATIONCOMBATELEMENT

COMMANDERMAGTF

METOCOFFICER

METOCDIV

WEATHERFLIGHT

COMMANDELEMENT

COMBAT SERVICESUPPORT ELEMENT

METTEAM

METOCOFFICER

WEATHERTEAM

WEATHERTEAM

THEATERAVIATIONBRIGADE

CORPSAVIATIONBRIGADE

DIVISIONAVIATIONBRIGADE

JOINT AIROPERATIONS

COMPONENTWEATHER

TEAMS

COMPONENTWEATHER TEAMS

COMPONENTWEATHER

TEAMS

JOINT LANDOPERATIONS

JOINT MARITIMEOPERATIONS

WEATHER TEAMS/MET (USAF/USN)

SPECIAL OPERATIONSFORCES BASES/

GROUPS

Forward Operating Base/Location

METMF

ARMY CORPS

ARMY DIVISION

JFLCC JSOTF / JFSOCC JFMCC

SUBUNIFIED COMMAND/JOINT TASK FORCE

METOC OFFICER METOC OFFICER METOC OFFICER METOC OFFICER

COMAFFORCOMARFORCOMMARFORCOMNAVFORJFACCJFLCCJFMCCJFSOCC

JMFU

Commander, Air Force ForcesCommander, Army ForcesCommander, Marine Corps ForcesCommander, Navy Forcesjoint force air component commanderjoint force land component commanderjoint force maritime component commanderjoint force special operations componentCommanderjoint METOC forecast unit

JMOJSOTFMAGTFMETMFMETMSTMWSSSMOUSAFUSN

joint METOC officerjoint special operations task forcesMarine air-ground task forcemeteorological mobile facilitymobile environmental teamMEF weather support teamMarine wing support squadronsenior METOC officerUnited States Air ForceUnited States Navy

ARMOREDCAVALRY

REGIMENT

REGIMENTALAVIATION

SQUADRON

Figure II-2. Typical Joint Force/Meteorological and Oceanographic Organization

II-5


support to Army field artillery units, relativeto their operations.

c. Navy. The Navy forces (NAVFOR)component receives METOC support from amultitude of different METOC agencies.Ashore METOC centers, facilities, anddetachments provide regional support toforces afloat and shore activities. DeployedMETs provide METOC operations to thosemi l i ta ry assets w i thout o rgan icenvironmental capabilities. Afloat OAdivisions provide organic METOCcapabilities to fleet assets (e.g., aircraftcarriers, large deck amphibious, and commandships).

d. Marine Corps. Staff weather officersassigned to Marine Corps forces(MARFOR), Marine expeditionary force(MEF) headquarters, Marine aircraft wingheadquarters, and personnel assigned to theMarine wing support group (MWSG) andMarine wing support squadron (MWSS)provide the Marine Corps with METOCsupport. The MWSG and MWSS are part ofthe aviation combat element of the Marine air-ground task force (MAGTF). MEF weathersupport teams (MSTs), are task-organized tosupport all elements of the MAGTF and theJMFU.

7. Joint Special OperationsTask Force

Personnel assigned to the theater specialoperations command (either dedicated or asan additional duty) plan for METOC supportto the joint special operations task force(JSOTF). Service special operationscomponent METOC assets support theJSOTF when it stands up. Subordinate Armyand Air Force components have organicmeteorology support provided by Air Forceunits. Dedicated Air Force special operationsweather teams (SOWTs) are normally underthe tactical control of Army special forcesgroups and battalions, the Ranger Regiment,

and the Special Operations AviationRegiment. The Air Force provides dedicatedSOWTs to Air Force special operations basesand detachments. The Navy’s METs augmentNaval special warfare units and provideMETOC operations to the JSOTF and otherspecial operations forces (SOF) ashore asrequired.

8. Joint Force FunctionalComponent CommandsMETOC Organizations

Joint METOC personnel are almost neverorganic to functional components. Whenavailable, functional component commandersmust rely on METOC resources provided bythe Service forces within their functionalcommand. To satisfy all functionalcomponent commander’s requirements,however, the METOC operation may requireaugmentation from other Service

Personnel assigned to the theater specialoperations command plan for METOC support.

II-6

Chapter II

Joint Pub 3-59

components. In either case, this requires earlySMO, JMO, and Service componentcoordination to ensure adequate staffing.Enough METOC personnel and equipmentmust be available to be responsive to the needsof the functional component commander andto exploit and tailor JMFU and MFC productsto meet unique mission requirements.

a. Joint Force Air ComponentCommander (JFACC). If the JFACC isdual-hatted as a Service componentcommander, the JFACC will normally havea staff to provide METOC information. ThisMETOC staff (with augmentation from otherServices, as required) should be adequate tosuccessfully execute the JFACC’sresponsibilities. The JFACC requiresMETOC information to support developmentof the air tasking order and a wide range ofair operations.

b. Joint Force Land ComponentCommander (JFLCC). Regardless ofwhether the JFLCC is ARFOR or MARFOR,METOC forces organic to the Marine Corpsand/or Air Force units assigned to assistArmy forces are usually available andadequate to support JFLCC operations (withaugmentation from other Services asrequired). The JFLCC requires METOC

information focused on the operational area,its approaches, and threat force occupiedareas.

c. Joint Force Maritime ComponentCommander (JFMCC). Regardless whetherthe JFMCC is NAVFOR or MARFOR,METOC forces organic to those two Service

F-18 operations depend on direct support from METOC personnel.

METOC personnel are almost never organicto functional components.

II-7


components should normally be available foruse by the JFMCC (with augmentation fromother Services as required). The JFMCCrequires METOC information focused on theoperational area, its approaches, and threatforce occupied areas.

d. Joint Force Special OperationsComponent Commander (JFSOCC). TheService special operations components’METOC forces provide augmentationwhich support the JFSOCC METOCoperations.

II-8

Chapter II

Joint Pub 3-59

Intentionally Blank

CHAPTER IIIJOINT FORCE METOC PRINCIPLES

III-1

1. Overview

This chapter describes METOC principlesthat are the cornerstone of joint forceMETOC operations. By applying theseprinciples, METOC staffs are better preparedto enhance and sustain joint force operations.

2. METOC Principles

a. Timeliness. METOC operations areonly effective when the CINC and subordinateJFC receive accurate METOC information intime to consider its impact within theirdecis ion making cycle. Rel iab lecommunication links between all jointMETOC forces are vital in order to supportand sustain the timely dissemination ofMETOC information and are key to theoverall capability of METOC forces.

b. Accuracy. Joint forces depend onaccurate METOC information to plan anddirect their operations. Inaccurateinformation can cost lives, undermine thesuccessful execution of a mission, wasteresources, and impair readiness. This is trueacross the range of military operations. Allof the following affect the accuracy ofMETOC information: the capability to collectdata within the area of interest with sufficientspatial and temporal coverage to model andforecast the METOC conditions; theperishable nature of METOC data; andhuman error. The impact these factors haveon forecast accuracy should be explained tothe JFC to enable the JFC to weigh these

“The rapid transmission by wireless of meteorological information is of theutmost importance....”

General Erich F. W. LundenhoffGerman General Staff 1917

factors when making weather sensitiveoperational decisions.

c. Relevance. Attaining this principlerequires the joint force user to communicateits specific requirements for content, form,medium, presentation, timeliness, andfrequency of delivery, and asks METOCpersonnel to satisfy these requirements. It willinfluence the joint force’s current, planned,and alternative courses of action (COAs) ateach level of responsibility. Each operationrequires tailored METOC information so thatthe user can quickly identify and applyrelevant information without additionalanalysis or manipulation.

d. Unity of Effort. METOC informationthat influences a JFC’s decision usually cannotbe derived from a single source. Instead,METOC data from the MFC, component, andtactical sources should be assembled into adata base that contains a complete andintegrated summary of METOCconditions of interest to the JFC and allcomponent commanders. This will simplifyaccess and ensure consistency of data usedby multiple forecast activities. Within a jointforce, there must be unity of effort to ensurethe METOC data base is complete, up-to-date, consistent, and accurate. Toaccomplish this task, METOC organizationsat all levels should have clearly definedfunctions, outlined in an operation plan(OPLAN) or operation order (OPORD),Annex H, or letter of instruction (LOI), whicheliminate unnecessary duplication, maximize

III-2

Chapter III

Joint Pub 3-59

sharing of information, and mutually supportthe overall METOC concept. Collaborationand coordination between functional andService component METOC forces is criticalwhen METOC conditions will impact onecomponent’s ability to support anothercomponent (i.e., tanker support or coordinatedair strikes).

e. Readiness. METOC forces, data bases,products, and equipment must be responsiveto the requirements of the JFC. To beresponsive, readiness will be maintainedthrough Service component participation injoint exercises and operations.Communications equipment will beinteroperable with joint and Servicecomponent capabilities. Where required,METOC resources must be maintained in adegree of readiness that ensures immediateemployment capability. METOC plansdeveloped to support joint operations shouldbe exercised and evaluated in realistic trainingscenarios to ensure that those plans are feasibleand can support the overall mission at alllevels. Conducting joint exercises trainsassigned forces, maintains readiness, enhancesinteroperability, and confirms the feasibilityof communications and OPLANs. TheServices should plan and coordinatestandardized and interoperable equipment andtraining techniques to realize a seamlesstransition to joint wartime and/orcontingency METOC operations. Servicecomponents should identify their trainingrequirements for inclusion in CINC andChairman of the Joint Chiefs of Staff (CJCS)sponsored exercises through the CINC’sSMO. Joint training requirements aredeveloped from the CINC’s Joint Mission

Essential Task List as governed by Chairmanof the Joint Chiefs of Staff Manual (CJCSM)3500.03, “Joint Training Manual for theArmed Forces of the United States.”

f. Effectiveness. The overall effectivenessof METOC operations should be based on thesuccessful and effective use of METOCinformation in support of specific jointforce operations. Each METOC organizationshould direct its actions toward this goal andconstantly assess its performance. Thisrequires METOC organizations at all levelsto be fully integrated in the planning andexecution of all military actions and to usecustomer feedback to continually improvetheir overall effectiveness.

METOC organizations at all levels are requiredto be fully integrated in the planning and executionof all military actions.

CHAPTER IVJOINT FORCE METOC OPERATIONS

IV-1

1. Overview

This chapter describes the primaryoperations that the METOC communityperforms in order to enhance joint militaryoperations, both in combat and noncombat.Additionally, joint force METOC functions,responsibilities, SMO and JMO duties, JMFUoperations, and Service and/or functionalcomponent operations are described. Theintegration of METOC capabilities duringall phases of OPLAN development and theability to provide accurate and timely METOCinformation as an operation unfolds is criticalto the success of joint force operations.

2. Joint Force METOCFunctions

a. Sensing and Collection. METOCoperations depend on the timely collection ofhigh quality METOC data. The foundationfor effective METOC operations is set byobservations from aerospace, land, and atsea by sensors or platforms such as upper airsounding devices; meteorological satellites;weather radar; lightning detection systems;atmospheric profilers; solar telescopes;ionospheric sounders; space-based spaceenvironment sensors; buoys; unmanned aerialvehicles (UAVs); remote surface sensors; tidegauges; current meters; and topographic andbathymetric data collection devices. Theseobservations, gathered from friendly andunfriendly areas of interest, are the essentialcomponents of theater and/or regional andworldwide data bases from which METOCservices and products are derived. Due to therapidly changing nature of the METOC

“In military operations, weather is the first step in planning and the finaldetermining factor in execution of any mission...”

General Carl SpaatzAir Force Chief of Staff, 1948

environment, these observations are extremelyperishable and must be continuously updatedand available to METOC organizations. TheJMO must develop and implement a sensingand collection strategy for METOC datamanagement that orchestrates the timing,distribution of collection sites, and efforts ofall components within the joint force, as wellas reliable sources of foreign data. A completestrategy will ensure unity of effort whileoptimizing data collection, dissemination,and integration into forecast products.Spreading observational resources across anarea of interest with regard to climatic zonesto obtain optimum coverage will significantlyimprove the quality of METOC services.Figure IV-1 gives an example of themanagement of METOC data and applicableoperations taking place within an area ofinterest.

b. Analysis. After collection of availabledata, the MFC, JMFU, and componentMETOC activities develop a coherentpicture of the current state of the METOCenvironment for their level of interest(national strategic, theater strategic,operational, and tactical). Analysis is thecritical function which enables productionof accurate forecasts of the METOCenvironment. Figure IV-2 provides anexample of analysis responsibilities.

c. Forecasting. Through timely analysis,evaluation, interpretation, and distribution ofMETOC data, the JMFU and other forecastelements develop specific METOC productsto enhance military operations and to meetthe CJTF’s requirements. METOC forecasts

IV-2

Chapter IV

Joint Pub 3-59

can be developed for the near or far termto cover global, theater, and tactical scales.These forecasts vary from generalizedplanning forecasts issued several days inadvance of an operation to forecasts issued tosupport the execution of a specific mission oroperation immediately prior to their launchor start. Figure IV-3 provides an example ofthe forecast information that is provided fromdifferent METOC levels. Within the JMFU,the JMO ultimately determines whichMETOC activity provides what forecastproducts. The joint operations area forecast(JOAF) provides the official forecast foroperational planning and should be used byall operational planners in the joint operationalarea. It provides a discussion and rationalefor the expected METOC conditions thatimpact joint force operations during theforecast period. It is expected that thecomponent tactical level forecast may take a

different form because of a difference inmission focus. Component activitiescommunicate significant differences betweentheir forecasts and the JOAF with the JMFUto maintain a “one theater, one forecast”concept. The JMO is the final authorityfor the JOAF and will ultimately settle anysignificant differences over the forecastcontent of the JOAF raised by participatingMETOC agencies. METOC personneldeveloping control and/or execution forecastswill use the planning forecasts as a startingpoint and fuse in situ data (e.g., target weatherand intelligence [TARWI], forward arealimited observation program [FALOP], pilotreports [PIREPs]) and local observations toproduce tailored mission specific forecasts.

d. Tailored Application. A key role ofthe METOC community is to enhance thedecision making process of the JFC and

MANAGEMENT OF METEOROLOGICALAND OCEANOGRAPHIC DATA

AND APPLICABLE OPERATIONS

RESPONSIBLELEVEL

MANAGEMENT OPERATIONS

METOC FORECASTCENTER

(MFC)

REQUESTS DATA FORMODEL EFFORTS

MONITORS AND PROCESSESWORLDWIDE, REGIONAL,

THEATER, AND SPACEENVIRONMENT DATA

IMPLEMENTS PLAN

INTEGRATES MFC,COMPONENT, AND

TACTICAL DATA

DEVELOPS PLAN

REQUESTS ANDFORWARDS DATA

SENIOR METOC OFFICERAND/OR

JOINT METOC OFFICER

COLLECTS, PROCESSES, FORWARDS

JOINT METOCFORECAST UNIT

COMPONENT ANDTACTICAL

METOC ACTIVITIES

Figure IV-1. Management of Meteorological and OceanographicData and Applicable Operations

IV-3

Joint Force METOC Operations

subordinate joint forces through tailoredapplication of forecast products. Byreceiving METOC information and its impactto operations, decision makers can evaluateoperational limitations of both friendly andenemy weapon systems as well as associatedtactics, techniques, and procedures. Forexample, integration of METOC informationinto the planning process allows the JFC andsubordinate joint forces to make informeddecisions with regard to the design andoperation of a plan and the use of variousweapon systems. Early integration ofinformation from METOC studies developedfrom climatological data bases can aid thelong-range planning of military operations aswell. In another example, METOCinformation is included as part of theintelligence estimate of the enemy’s probableCOA and capabilities, based on the enemy’sability to perform in given METOCconditions. Figure IV-4 provides an exampleof tailored applications and/or operationsbased on level of responsibility.

e. Dissemination. Due to the perishablenature of METOC information , current andforecast information must have prioritycommunications to reach the JFC andsubordinate forces in time to be of operationaland planning value. Therefore, observing andforecasting functions must process anddisseminate METOC information to jointforce users by the fastest and most reliablemeans available. Passing METOCinformation from the tactical and operationallevels to the MFC, as outlined in AppendixM, “METOC Forecast Center,” is vital forinclusion in METOC numerical model runs.This also allows the centers to act as backupfor the JMFU, as required. Communicationsis the key supporting element for theMETOC community to successfully performits mission. Appendix J, “Communications,”is dedicated to discussing communicationissues. METOC personnel and users ofMETOC information must determine, withinthe JMO’s theater information strategy, whatinformation merits distribution, to whom,

ANALYSIS

RESPONSIBLELEVEL

ANALYSIS

METEOROLOGICAL ANDOCEANOGRAPHIC (METOC)FORECAST CENTER (MFC)

DEPARTMENT OF DEFENSE FOCAL POINTFOR CURRENT WORLDWIDE, REGIONAL,

AND/OR SPACE ENVIRONMENT INFORMATION

THEATER EXPERT CREATES AND TAILORSPRODUCTS TO SUPPORT OPERATION

MISSION-SPECIFIC DATACOMPONENT AND/OR

TACTICAL METOCACTIVITIES

JOINT METOCFORECAST UNIT

Figure IV-2. Analysis

IV-4

Chapter IV

Joint Pub 3-59

when, and the format and media required.This will ensure that users receive only theinformation needed for the task at hand ratherthan being inundated with unneeded products.Users of METOC information must also beable to quickly define and request uniqueproducts required for specific operations orweapon systems. Figure IV-5 shows thedissemination of the types of informationrequired by the various METOC levels withina joint force.

f. Evaluation. Operational awareness,staff networking, METOC debriefs, andthe use of the Joint Uniform LessonsLearned System (JULLS) will significantlyenhance the capability to evaluate METOCeffectiveness. Evaluations based uponcustomer requirements and/or equipmentlimitations identify shortfalls in the value ofvarious types of products, the responsivenessof the METOC products to the user, andtechniques used to provide the information.Implementing timely corrective actionsenhances the overall quality of METOCoperations. Figure IV-6 describes the

METOC information within a joint forceoperation that should be evaluated.

3. Responsibilities

CJCS, Service, CINC, subordinate JFC,SMO, and JMO responsibilities for METOCsupport to joint operations are provided inCJCSI 3810.01A, “Meteorological andOceanographic Operations.” SMO and JMOduties and responsibilities are further detailedin this publication.

4. SMO and JMO Duties

The duties of the SMO and JMO are similarand interrelated during the planning andexecution of joint operations. The primarydifference is that an SMO supports theCINC in the development and maintenanceof established OPLANs and operation plansin concept format (CONPLANs). Conversely,the JMO supports a joint task forcecommander in the execution of a specificmission and/or task by either modifying anexisting plan or developing a new one. In all

FORECASTING

RESPONSIBLELEVEL

GENERALFORECASTS

MISSION SPECIFICFORECASTS

METEOROLOGICAL ANDOCEANOGRAPHIC

(METOC) FORECASTCENTER (MFC)

JOINT METOC OFFICERAND/OR JOINT METOC

FORECAST UNIT

WORLDWIDE AND/ORREGIONAL

RESPONDS TO REQUESTSAS NEEDED

THEATER FORECASTS BASED ON OPERATIONALCRITICAL THRESHOLDS, RESPONDS TO REQUESTS

AS NEEDED

TAILORED EXECUTION AND/OR ORIGINATESASSISTANCE REQUESTS AS NEEDED

COMPONENT ANDTACTICAL

METOC ACTIVITIES

Figure IV-3. Forecasting

IV-5


stages of time-phased force and deploymentdata (TPFDD) development, the SMO and/or JMO need to work with planners to ensurethe appropriate mix of Service METOCpersonnel and equipment are identified for thejoint operation. Potentially, the SMO couldstep in for the JMO for a particular operationand fulfill all planning and executionresponsibilities. SMO and JMO duties andrelationships are discussed below.

A future example of these interrelated dutieswill involve the Global Command and ControlSystem (GCCS). As METOC productcapability evolves on GCCS, the SMO and/or JMO at the echelon where responsibilityresides for building and maintaining thecommon operating picture (COP) will needto determine what METOC data, products,and sources will be a part of the COP.Coordination with the JMFU will be essentialto optimize this capability for joint operations.

a. SMO Duties. During the planning andexecution of joint operations, the SMO’sduties are as follows.

• Serve as the focal point for joint forceMETOC support as outlined inAppendix A, “SMO and JMOInvolvement in Planning.” The SMOmust ensure that METOC capabilitiesand requirements are included in theCINC’s campaign plan, OPLAN,CONPLAN, OPORD, or in the LOI, asappropriate. The SMO works with theService component METOC officers andthe CINC’s staff in the development ofthe following annexes for each OPORD,OPLAN and CONPLAN: B(Intelligence), C (Operations), H(METOC Operations), K (Command,Control, and Communications Systems),and N (Space). Appendix B to thispublication, “METOC Information in

TAILORED APPLICATIONS

RESPONSIBILITY OPERATIONS

METOC FORECAST CENTER (MFC)AND/OR JOINT METOC FORECAST

UNIT

DIRECT INVOLVEMENT WITH COMMANDER INCHIEF AND JOINT FORCE COMMANDER

OVERALL SUPPORT PLANJOINT METOC ASSESSMENT

PROVIDES TAILOREDMETOC INFORMATION

FOCUSED AIR, GROUND, SEA SITUATIONTARGET DEVELOPMENT

SITUATIONAL AWARENESS WEAPONAND/OR TACTICS EMPLOYMENT METOCEFFECTS ON WEAPONS AND THREATS

SENIOR METEOROLOGICALAND OCEANOGRAPHIC

(METOC) OFFICER AND/ORJOINT METOC OFFICER

COMPONENT

TACTICAL LEVEL

Figure IV-4. Tailored Applications

IV-6

Chapter IV

Joint Pub 3-59

Operation Plans,” provides details on theMETOC content of these annexes.Appendix C to this publication,“METOC Letters of Instruction,” showsan example of an LOI that describesinformation important to the METOCconcept. The LOI is an effective vehicleto distribute the METOC concept ofoperations (CONOPS) to the METOCpersonnel participating duringcontingency operations when an OPORDis not available or there are changes toan existing OPORD. CJCSM 3122.03,“Joint Operation Planning and ExecutionSystem Vol II: (Planning Formats andGuidance),” provides guidance fordeveloping an Annex H.

• Coordinate with the US diplomaticmissions, Joint Staff, and other USagencies as required to ensure that allavailable METOC information andsystems, as well as indigenous assets anddata, are properly considered and madeavailable, if needed, for use by the jointforce. Coordination should include areview by the servicing legal office ofapplicable treaties with other countriesand of memoranda of understanding withnon-DOD agencies that may beimplicated by the provision of METOCinformation or services. In developingthe METOC CONOPS, use of in-countryassets should only complement USmilitary METOC capabilities. US

DISSEMINATION OF METEOROLOGICAL ANDOCEANOGRAPHIC INFORMATION

RESPONSIBILITY TYPES OFINFORMATION

TO WHOM

METOC FORECASTCENTER

(MFC)

WORLDWIDE AND/ORREGIONAL ATMOSPHERIC,

OCEANIC AND SPACEDATA BASE

JMFU,JOINT FORCES

JOINT FORCE COMMANDER,JOINT FORCES, MFCs

JOINT FORCESAND MFCs

LOCAL CUSTOMER AND/ORCOMPONENT, JMFU, AND

MFCs

COMPONENT ELEMENTSAND/OR

JMO, JMFU

APPLICABLE ANNEXES,LETTER OF INSTRUCTION

METOC GUIDANCE

APPLICABLE COMPONENTANNEXES, LETTER OF

INSTRUCTION

JOINT OPERATIONSAREA FORECAST,

SPECIFIC PRODUCTS

LOCAL OBSERVATIONSAND TAILORED

FORECAST PRODUCTS


JOINT METOC OFFICER (JMO)

JMO, JOINT METOCFORECAST UNIT

(JMFU)

COMPONENT

TACTICAL LEVEL

Figure IV-5. Dissemination of Meteorological and Oceanographic Information

IV-7


military METOC assets should maintainthe capability to function in a stand-aloneenvironment without indigenousassistance.

• Coordinate with the Service componentMETOC officers and the CINC’s staffin formulating a concept of METOCoperations which supports the CINC’sconcept of operations. Coordinationshould include the Air MobilityCommand (AMC) functional manager,through the US TransportationCommand (USTRANSCOM), forstrategic airlift and tanker missionMETOC support. Once a joint force isformed and a JMO designated, the SMOmust work closely with the JMO andService components to obtain andsynthesize METOC requirements andcapabilities prior to the execution ofoperations. The joint force concept of

METOC operations should implementthe principle of unity of effort byintegrating the capabilities of the MFCwith those of the joint force. The SMO,JMO, Serv i ce and func t iona lcomponents, and all elements of theJFC’s staff will plan, evaluate, andcoordinate the METOC requirementsfor the joint operation. Theserequirements include organization,location, manpower, communications,equipment, logistics, data, and products.The METOC CONOPS should includethe following.

•• A summary of the operations conceptbased on the theater strategy.

•• The logistics concept, which outlinesthe support required by the joint METOCforce.

EVALUATION

RESPONSIBLELEVEL

OPERATIONS

METEOROLOGICAL ANDOCEANOGRAPHIC (METOC)

FORECAST CENTERS(MFCs)

SPECIFIC REQUESTSFROM JOINT FORCE

COMMANDER

WORLDWIDE AND/ORREGIONAL FORECASTS (JOINT

OPERATIONS AREAFORECASTS) (JOAF),

CLIMATOLOGY

OPERATIONAL GUIDANCE TOMETOC FORCES (JOAF),

CLIMATOLOGY

OPERATIONAL AREAFORECASTS

FORECAST OF LOCALAND/OR TARGET

CONDITIONS

OPERATION ORCAMPAIGN PLAN

COMPONENT PLANNING

MISSION PLANNINGAND EXECUTION


JOINT METOC OFFICER

COMPONENT LEVEL

TACTICAL LEVEL

METOCINFORMATIONEVALUATED

Figure IV-6. Evaluation

IV-8

Chapter IV

Joint Pub 3-59

•• The deployment concept (sequencingof operational capabilities via theTPFDD).

•• The organizational concept (externaland internal command relationships).

•• The communications concept,developed by the J-6, to include thearchitecture for real time transmission ofMETOC data between the MFC(s) andthe joint force operational area. TheServices provide interoperablecommunications systems to ensureMETOC elements within the joint forcecan effectively access and transferMETOC data.

•• The employment concept (day-to-dayoperations of forces). In developing thisconcept, the SMO must know customerrequirements and tailor METOCoperations accordingly. Some examplesof questions the SMO must answer are:(1) What forces (JFC staff, componentheadquarters) require support and whattype of METOC support is needed? (2)What are the capabilities of the MFCs?What type of support is needed for theCINC’s AOR? How is support providedto the CINC’s subordinate commands?Are there any shortfalls? (3) Whatcommunication system(s) are present inthe CINC’s AOR that will transmit andreceive METOC information from theMFC to the METOC staffs andorganizations under the CINC’s chain ofcommand? What systems will allowinformation flow throughout thesubordinate JFC’s chain of command?(4) Where and how will METOC databe collected, processed, and disseminated(sensing strategy and data management)?

• Obtain METOC requirements from alljoint force components and recommendtasking, through the CINC, of Servicecomponents’ METOC capabilities.

Coordinate with J-3, and document inapplicable OPLANs and/or CONPLANsas needed, critical environmentalthresholds for restricted and/orunrestricted operations decisions.Coordinate with the JMO for MFCsupport or other additional capabilitiesrequired to fulfill operational needs thatare not within the capability of the jointforce. Coordinate with the JMO onMETOC personnel and equipmentrequirements and ensure that the CINC’sstaff validates METOC TPFDDrequirements. Work with CINC’scomponent commands to coordinateMETOC personnel and equipmentavailability for the operations.

• Ensure the widest dissemination ofMETOC operations informationthrough the use of network homepagetechnologies. Consult with J-6 forassistance in establishing the METOCHomepage on both the CINC’s SECRETInternet Protocol Router Network(SIPRNET) and the Unclassified butSensitive Internet Protocol RouterNetwork (NIPRNET) and obtainingrequired command, control, communications,computers, and intelligence (C4I)connectivity. The SMO will determinespecific homepage design, butrecommended elements include:

•• METOC points of contact and HOTLINKS to their respective homepage ande-mail addresses (SMO; JMO; Servicecomponents; functional components [asappropriate, e.g., special operations orJFACC]; JMFU; and MFC as aminimum);

•• Annex H, LOI, or CONOPS,whichever is appropriate;

•• HOT LINK to JOAF; and

•• Specially-tailored products.

IV-9


• Keep CINC appraised of METOCoperations and conditions in the jointforce operating area.

b. JMO Duties

• Coordinate with the SMO and CJTFstaff on updates to the various annexessupporting the OPORD. Specificattention should be given to Annexes B,C, H, K, and N of the OPORD, and dutiesoutlined in Appendix A to thispublication, “SMO and JMOInvolvement in Planning.” Ensure thatall METOC personnel and equipment areincluded in the TPFDD. Coordinate withthe SMO to ensure that the CINC’s staffvalidated METOC TPFDD requirements.

• Coordinate with the SMO to ensure thatall available METOC information andresources, as well as indigenous assets,are properly considered and madeavailable for use by joint forces. TheJMO, in conjunction with the SMO,establishes and implements an all-sourcetheater observing strategy that fulfillsthe requirements of the joint force andMFC. Attention to efficiently using allavailable observational assets willmaximize operating area coverage andpreclude duplicative efforts. As anexample: multiple simultaneous weathersites recording upper-air soundingswithin a few mile radius shouldcoordinate launch times to conserveresources and maximize effectiveness.Adjacent sounding sites’ effectivenesscan be optimized by tasking certainstations to take non-standardobservations (i.e., 03, 06Z, etc.). Thisplan could better depict the changingatmospheric conditions. Importantsources of METOC data from Servicecomponent non-METOC activities areoutlined in Appendix D, “METOC DataSources From Non-METOCOperations.”

• Consistent with the scope and missionof the joint force, recommend to the CJTFthe establishment, manning, andlocation of the JMFU (duties could beembedded into an existing MFC). TheJMFU is an important element in theMETOC organization because it is thecenter for integration of all METOCdata in the joint operations area. Theneed to balance sufficient METOC dataflow with sufficient operational input willdrive the decision of where to locate theJMFU. Communications connectivitytends to drive this decision; however, theJMO must also consider available airlift,manning, equipment, and other possibleres t r ic t ing fac tors . The JMOrecommends to the CJTF the manpowerrequirements, force composition, andlocation of the JMFU. The JMO willprovide overall direction to the JMFUand the MFC production facilitiessupporting the operating area.

• Establish and publish METOC productrequirements and coordinate METOCsupport services for the joint force.

• Ensure coordination for strategic airliftand tanker mission METOC supportwith either the air mobility elements, ifdeployed, or the AMC functionalmanager through USTRANSCOM.

• Assemble the joint force METOC staffand equipment within the operatingarea, consisting of the personnel andresources assigned by the CINC andconsistent with the scope of the joint forcemission.

• Assist the CJTF, JTF staff, centers, andthe components to understand the stateof the METOC environment in whichboth friendly and threat weapon systemsand/or their supporting infrastructure willoperate. The JMO must validate andrefine their requirements for METOC

IV-10

Chapter IV

Joint Pub 3-59

information to assist them in planning,conducting, and evaluating operationsto achieve the CJTF objectives. Sincepotential missions are wide-ranging, theJMO must be aware of METOCcapabilities, assets, and resourcesavailable. Coordinate with the SMO onMETOC manning, communications,information, and service requirementsbeyond the capabilities of assignedMETOC assets, and aggressively workwith the joint force staff to obtainadditional resources as deficiencies areidentified.

• Actively monitor and evaluate theplanning and execution of theoperation, and work METOC issues thatarise. During training scenarios, the keyis to exercise the same process andprocedures as would be employedthrough the range of military operations.Feedback on the overall performanceof the METOC operation effort is critical.The JMO should aggressively workthrough the CJTF’s staff and the JULLSfor feedback on METOC support forexercises as well as operations. FigureIV-7 provides an example of proceduresto determine overall METOCeffectiveness to the joint force.

• Ensure that all deploying METOC forceshave adequate tactical location identifiers(KQ-identifiers). Request additionalidentifiers using Service procedures, ifrequired. Ensure that enough currentpasswords are requested for access toJoint Worldwide IntelligenceCommunications System (JWICS), AirForce weather information network(AFWIN) or secure Air Force weatherinformation network (SAFWIN), orNaval Oceanographic Data DistributionSystem (NODDS) and/or Joint METOCViewer (JMV). Request passwords viaService procedures, if required.

5. JMFU Operations

The JMFU concept is the cornerstone ofthe METOC three-tiered operations structure.Using Annex H, Annex K, and the LOI as theblueprint, the JMFU, under the JMO’sdirection, provides overarching support tothe CJTF. The challenge for the JMFU: takeexisting METOC center forecasts and meldwith operational and tactical information,produce the JOAF, and disseminate theJOAF to all joint forces. At the onset of ajoint force operation, the CINC’s SMOcoordinates with MFC production sites andfacilities to provide products and services forthe area of interest. The SMO determines therequirement for a JMFU. If the SMOdetermines that existing METOC facilities areunsuitable, the JMO works in conjunctionwith the SMO and the CJTF staff to establishor designate a JMFU for the operation. TheJMFU should be capable of producing theproducts necessary for the CJTF; however, itmay be constrained by restrictions onmovement of manpower and equipment intothe joint force operating area. In the case oflimited capability, production responsibilitiesmay rest with an existing MFC productionfacility. The JMFU may be required toprovide support directly to tactical forces inthe event that organic METOC support isunavailable. During JMFU operations, otherMFC elements would still provide productsto out-of-operating area METOC unitssupporting joint force operations (e.g., airlift,long-range bombers, tankers, sealift, fleetoperations). The functionality of the JMFUmay differ based on its geographic focusand/or missions. The JMFU receivesdirection and information on plannedoperations from the JMO. The JMO is thelead action agent in the joint operations area,ensuring effective METOC operations. TheJMFU is one of the tools the JMO uses toimplement the principles of joint METOCoperations. The focus is on the integration ofMETOC information from joint force

IV-11


components, MFC, other sources, and fusingMETOC and tactical information. The JOAF,ideally produced by the JMFU incollaboration with component METOCforces, is the overarching operationalplanning forecast for all joint forceoperations and will be used by all METOC

forces. The JMO is the final authority tosettle any disagreements on the JOAF. TheJOAF will be used by tactical units to tailorexecution forecasts at appropriate levels inthe joint force. Figure IV-8 identifies thebuilding block elements of JMFUoperations.

DETERMINING METEOROLOGICAL ANDOCEANOGRAPHIC EFFECTIVENESS

JFCJMFUJMO

JFCJMFUJMO

JULLSMETOCMFC

JULLSMETOCMFC

joint force commanderjoint METOC forecast unitjoint METOC officer

Joint Universal Lessons Learned Systemmeteorological and oceanographicMETOC forecast center

Consider JFC Objective

What METOC support was required?

Did METOC support meet objective?

Integrate fix into next JFCexercise and evaluate

NO

Document and/orCrossfeed (Thru J-3and/or J-5 toapplicable METOCunits)

What area did not meet objective?(JMFU, component, MFC, JMO)

What was the METOC problem?(accuracy, timeliness, integration (planning))

Document and/or Crossfeed (Submit thruJ-3 and/or J-5 and include in JULLS)

YES

Work with appropriate agency and/or Servicefor fix

Figure IV-7. Determining Meteorological and Oceanographic Effectiveness

IV-12

Chapter IV

Joint Pub 3-59

With connectivity to other MFC productionfacilities for worldwide data and/orinformation, joint forces, and availableindigenous assets for tactical data, the JMFUnormally has the greatest access toinformation with which to produce METOCproducts meeting the requirements of theCJTF. Adequate communications andcoordination between the JMO, joint forces,and MFC are required for effective METOCoperations.

a. The JMFU operates 24 hours per dayintegrating and analyzing METOCinformation to assess the state of METOCconditions. Synthesis of this informationresults in the planning forecast for joint forceMETOC personnel to use when developing

tailored METOC information for missionexecution support. With this in mind, JMFUinformation, which can be packaged indifferent “product” formats, must beconstructed with an understanding of specificMETOC thresholds (restricted and/orunrestricted recommendation and/or decisionmatrix) that affect military capabilities andjoint operations in the field. This requirescomplete knowledge of the joint forceoperation, the overall objective, and specificMETOC thresholds that affect joint forcecomponent operations. This requirement willbe difficult to achieve if the JMFU is notcollocated with the CJTF. If the JMFU cannotcollocate with the CJTF, a minimumrequirement for the JMFU is to have effectiveC4I connectivity with the JTF to ensure a

Figure IV-8. JMFU Operations

JMFU OPERATIONS

REQUIREMENTSMETOC DATA AND/ORIMAGERY MFC

OTHERMETOC SOURCES

(E.G., INDIGENOUS)

JOINT FORCE

TACTICAL LEVEL

COMPONENTS

JMFU

JOAF, OTHER PRODUCTS AS REQUIRED

Collection&

Dissemination

SensingRequirement Evaluation

Analysis&

Productionof METOCProducts

JMFUJOAFMETOCMFC

joint METOC forecast unitjoint operations area forecastmeteorological and oceanographicMETOC forecast center

OBSERVATIONS,FORECASTS,DATA FLOW

IV-13


smooth flow of operations data necessary toproduce accurate and timely METOCinformation.

b. JOAF . A primary JMFU forecastproduct is the JOAF. (See Appendix E, “JointOperations Area Forecast,” for example.) Itprovides a detailed discussion and rationalefor the expected mean METOC conditions inthe operating area for time periods requiredby the JTF. The JOAF may have several “sub”areas identified within the operating area tofurther tailor the METOC conditions expected(e.g., land forces area of operations,amphibious operations area, spaceenvironmental effects). The JOAF shouldspecify time of occurrence, duration andintensity when certain METOC parametersare expected to exceed critical thresholdvalues and impact joint force operations. Thisproduct is generally disseminated toMETOC forces on a regular basis (usuallyevery 12 hours). Since the JMFU isconducting a continuous watch of METOCconditions within the entire joint force area,they should amend the JOAF as requiredbased on the thresholds that METOC tacticalunits identify and coordinate through theJMO. The JOAF is a dynamic product whichadapts to and reflects the changingrequirements of the operating area. As anexample, predominately amphibiousoperations may transition to deep strike airoperations. This clearly shows the need forthe JMFU to be flexible in order to supportthe needs of the JTF while emphasizingcoordination between all CJTF METOCforces to successfully orchestrate jointMETOC support. Consideration should begiven to including a section of the JOAF tocover an analysis and forecast of the spaceenvironment.

c. Other METOC information and/orproducts can be developed, produced, anddisseminated by the JMFU as required.Current surface analyses, short and long-rangesignificant weather depiction displays, low

level hazard prognoses, point specificadvisories, electro-magnetic decision aids, andelectro-optical tactical decision aids (E-OTDAs) are just a few examples of informationthe JMFU can provide. Climatologicalsupport capabilities may also be available.Similar to the JOAF, these products are basedon joint force requirements and should beamended as required. If required, the JMFUwill develop tactical execution forecasts ifprovided with appropriate intelligence andtargeting information.

d. Appendix F, “Examples of METOCIn fo rmat ion Requ i rements andResponsibilities Within a Joint Force,” is alist of the majority of METOC informationthat would be required within a joint force.Worldwide and regional computer-generateddata grids which are “pushed” to the jointforce in near real time from the MFC providethe baseline for much of the information listed.Within the joint force, however, tailoredsupport evolves. Additionally, Appendix F,“Examples of METOC InformationRequirements and Responsibilities Within aJoint Force,” provides a framework andshould be used to determine METOCorganizational level responsibilities fortailoring individual parameters anddeveloping specific products. Ideally, thedivision of labor and responsibility for thedevelopment and distribution of thisinformation are addressed in OPLANs,CONPLANs, OPORDs, or LOIs. In theabsence of a plan at the outset of a crisis, theJMO must work with the joint forcecomponents and the MFC to review eachinformation need and determine theresponsible provider. Careful evaluationshould be conducted especially wherefunctions are performed simultaneously insupport of more than one operation or whereUnified Command boundaries cross.

e. METOC Data Management. To meetthe joint force’s need for METOCinformation, the JMO focuses on defining

IV-14

Chapter IV

Joint Pub 3-59

and submitting requirements and managingMETOC observing efforts. The JMOshould work closely with the SMO, JMFU,the CJTF staff, joint force components, andthe MFC to ensure that the joint force METOCdata collection plan supports the needs of theoverall operation. For example, in additionto the receipt of conventional METOCobservations and forecasts, the JMFU mayrequire access to “unconventional”information (non-METOC assets) fromintelligence sources, remote sensors, UAVs,reconnaissance patrols, and special operationsteams. This additional information can greatlyenhance both MFC modeling efforts and theJMFU production of specific forecast productsfor the JTF. If this information is required bythe JMFU, the JMO must work closely withthe JTF staff to ensure that the JMFU receivesthe information necessary to develop qualityproducts.

f. METOC Communications. TheJMFU will normally rely on thecommunications concepts outlined inAppendix J, “Communications,” and AnnexK of the OPLAN. The JMFU should establisha transmission schedule for their products(sent electronically and/or posted on ahomepage) and continually monitor theoverall effectiveness of their communicationsconcept.

g. Coordinating Instructions. Whenactivated, the JMFU should have direct liaisonauthorized with the other MFC elements andcomponent METOC officers. SpecificOPLANs, OPORDs, or LOIs should specifythis overall guidance, including procedures toestablish overall CJTF product priorities. TheJMFU, under JMO direction, should satisfy(or arrange other support to satisfy) allMETOC requirements which cannot be metby component capabilities. Joint forces shouldforward their METOC assistance requests(MARs) to the JMO. The JMO, inconjunction with the JMFU, will determineif the required information is within the

JMFU’s capability and, if not, will submit asupport request to the appropriate MFCproduction facility. Additionally, if an MFCproduction facility has a requirement forspecific information from within the operatingarea, it will submit requests to the JMO whowill coordinate with the JMFU. If a differentMFC serves as a backup to the JMFU, thisrequirement should be outlined in theCONOPS, OPORD, OPLAN, and/or LOI asappropriate to ensure that data is provided tothe facility. Service specific informationrequired at either the operational or tacticallevels may be coordinated through the JMOand/or JMFU.

h. JMFU Manning. The JMFU shouldcomprise the proper Service componentexpertise required to effectively support thejoint force. The JMO will determine thecomposition of the JMFU in the planningprocess. The JMFU must be sized to supportthe operation and be normally manned for24 hour operations. Appendix H, “NotionalJoint METOC Forecast Unit Operation,”describes a notional JMFU operation tosupport a major theater war (MTW) and canbe modified to support a smaller scalecontingency (SSC). Appendix H, “NotionalJoint METOC Forecast Unit Operation,”includes a list of duties and a minimumrecommended manning level to execute theseduties. Once developed, the JMFU must workwith the JMO in identifying requiredaugmentation of METOC personnel, systems,and communications to support requirementsand for connectivity and interoperabilitybetween the combatant command SMO, theJMO, joint METOC forces, and the MFC.

i. JMFU Equipment. The SMO and JMOmust consider how to equip the JMFU withthe METOC processing equipment andcommunications interfaces it will need tocarry out its functions. This equipment mayalready be available as organic capabilities oravailable as deployable assets which must beincluded in the TPFDD. Some basic

IV-15


capabilities for consideration should includethe following.

• Access to DOD and/or theater andcomponent data command and control(C2) systems (e.g., GCCS, GlobalCommand and Control System-Maritime[GCCS-M], Contingency TheaterAutomated Planning System, ArmyBattle Command System [ABCS] orArmy Global Command and ControlSystem). The Joint METOC Segmentof GCCS can be installed on any DefenseInformation Infrastructure CommonOperating Environment computingplatform.

• METOC processing systems (e.g.,Tactical Environmental Support System[TESS], Integrated MeteorologicalSystem [IMETS], METMF, NewTactical Forecast System [N-TFS], NavyIntegrated Tactical EnvironmentalSystem [NITES]).

• METOC dial-in systems and WorldwideWeb Homepages (e.g., NODDS,AFWIN, SAFWIN, JWICS Air ForceWeather In format ion Network[JAFWIN], SIPRNET and/or NIPRNETHomepages, Navy’s JMV, 55th SpaceWeather Squadron [SWXS]Homepages).

• Local area network access to theater- and/or DOD-wide area network(s) (e.g.,Defense Information Systems Network[DISN]).

• Weather networks (e.g., AutomatedWeather Network [AWN]).

• Meteorological satellite (METSAT)ground systems (e.g., USAF E-STT,USN SMQ-11, USMC METMF) thatreceive and process real time, highresolution meteorological imagery from

polar orbiting and geostationary satellitesworldwide.

• Theater servers for collecting, storing,and disseminating all-source weatherinformation.

• Special weather intelligence (SWI)provided as classified reports on a regularbasis through J-2 channels. Note thatsome SWI is available on electronic databroadcast systems such as tacticalinformation broadcast service.

• Theater weather radar connectivity,integration, and dissemination capability.

• Theater-specific communicationssystems such as NATO MeteorologicalInformation System.

j. Security Issues. Classification of theMETOC information and/or productsshould always be considered. AlthoughMETOC information by itself is generallyunclassified, products which specify particularoperating areas or targets, unit locations, andcritical operational thresholds may beclassified. The JMO and JMFU shouldcoordinate with the J-2 and J-3 on the overallclassification guidance. Ensure that securitycontainers are available for communicationssecurity (COMSEC) required equipment, ifrequired.

6. Service and FunctionalComponent OperationsWithin the Joint Force

Component METOC officers best know theunique capabilities their forces bring tocombat and how those capabilities can helpattain the JFC’s objectives. They should alsoknow how these capabilities mesh with theMETOC forces of the other components.Organic METOC capabilities and/oroperations are typically sized in support of

IV-16

Chapter IV

Joint Pub 3-59

the Service and special operations componentmissions that were described in Chapter II,“Combatan t Commands METOCOrganizations.” Component METOC officersprovide decision assistance to theircommanders and staffs and serve as the focalpoint for component METOC planning andexecution. Based on the overall guidancefrom the SMO or JMO and their component’smission, METOC officers plan, coordinate,and evaluate the METOC supportrequirements for their component. TheMETOC officers should document theserequirements in appropriate annexes tocomponent level plans or LOIs for subordinateunits’ information. A key duty for METOCofficers is to determine information andproducts which are beyond their capabilityto provide. This requires coordination withsubordinate units. Each component can thendetermine what it can provide for subordinateoperations and work with the JMO and JMFUfor the support that the component cannotprovide. Multiple component METOCresources within an operating area will collectMETOC data in a coherent, unified sensingstrategy (the METOC LOI should be used tofacilitate the strategy). This data should beintegrated to produce METOC productssuperior to any which an individualcomponent could deliver. Other componentand subordinate unit duties include: take anddisseminate METOC observations, asrequired; prepare and disseminate METOCforecasts, to include weather watches andwarnings, as required; operate METOCcommunications equipment; work METOCpersonnel and equipment problems; identifyshortfalls in METOC personnel andequipment to their staff and JMO or SMO asapplicable; and provide input to the TPFDDas required.

a. AFFOR. USAF METOC forces at thecomponent, wing, and squadron use acombination of surface observations, upperair data, weather satellite, weather radar,MFC and JMFU products, locally

generated products, space environmentdata, and climatology to provide tailoredmission information. Tailored informationincludes observing, forecasting, and staffweather services. Information includessurface-based atmospheric observations (e.g.,clouds, visibility, winds, pressure,temperature), upper-air observations (e.g.,temperature, winds, and humidity), satellitedata, and space environmental forecasts and/or observations (from 55th SWXS) for the areaof interest. USAF METOC personnelprovide advisory and warning services,climatological information, andinterpretation of meteorological and spaceenvironmental conditions and their impacton operations and personnel. METOCpersonnel support planning and execution byproviding information such as climatologicaldata, tactical indices for weapon and/or sensorsystem employment, and tactical decisionaids. Additionally, METOC personnel havethe capability to deploy and use tacticalequipment to measure and record atmosphericconditions and to transmit, receive, andmanipulate data from the MFC, the JMFU,and weather satellite imagery. Descriptionsof this equipment are in Appendix K,“Deployable METOC Equipment.” Inaddition to USAF METOC support, METOCinformation can be gained from aviationTARWI reports and through the J-6 and theintelligence community. Air Force regionalweather hubs and/or operational weathersquadrons can provide theater-scalebattlespace forecasts; drop zone, range, and/or air refueling forecasts; and fine-scale targetforecasts as well as issue force protectionweather warnings and terminal area forecastsfor AFFOR and ARFOR locations within theiroperating area.

b. ARFOR

• Air Force METOC forces at the Armycomponent and subordinate echelonsprovide METOC information to Armyfo rces such as su r face -based

IV-17


observations (e.g., clouds, visibility,winds, pressure, temperature, groundconditions), upper-air observations (e.g.,temperature, winds, and humidity),satellite data, and space environmentalforecasts and/or observations. METOCpersonnel provide battlefield andaviation forecasts, weather warningsand advisories, meteorological watchof target areas and air and groundavenues of approach, and interpretationof the effects of METOC conditionsand their impact on operations andpersonnel. METOC personnel supportplanning and execution by providingMETOC information such as tacticalindices for weapon and/or sensor systememployment, tactical decision aids, andclimatological information for long-range planning purposes. Air ForceMETOC personnel who deploy insupport of ARFOR consist of CWTs thathave the capability to use tacticalequipment to receive satellite imagery,measure atmospheric weatherparameters, and generate forecastproducts to provide this support.Appendix K, “Deployable METOCEquipment,” provides descriptions ofthis equipment.

• In addition to USAF METOC support,the Army provides two kinds of directweather support to the Army combatmission. First, Army artillerymeteorological crews provide surfaceand upper air observations for artilleryfire support. Second, Army militaryintelligence personnel provide limitedobservations from areas where Air Forceweather teams are not manned, and typicallydo not operate. These observations can befrom manned or automated sensors. Armypersonnel use tactical atmosphericsounding and observing equipment toprovide this capability. This is furtherdescribed in Appendix K, “DeployableMETOC Equipment.”

c. NAVFOR

• METOC data collection and assimilationcapabilities and products and servicesprovided to operating forces afloat aretailored according to the requirementsof the Commander of Navy Forces.Support consists primarily of METOCinformation and forecasts foroperational use; forecast tacticalindices for weapon and/or sensorsystem employment and tacticaldecision aids; and climatologicalinformation for long-range planningpurposes. OAs receive global andregional METOC data fields,alphanumeric (AN) data, satellite dataand imagery, and local observationaldata. These data include high resolutionDefense Meteorological SatelliteProgram (DMSP), National Oceanic andAtmospheric Administration (NOAA)and/or television infrared observationsatellite (TIROS), geostationary satellitedata, complete upper air soundinginformation, and ocean acousticprofiling. The OAs provide tailoredforecasts for safety and execution ofoperations, with tactical effects forweapons and sensors, by use ofonboard prediction systems. AppendixK, “Deployable METOC Equipment,”describes these capabilities.

• Deployable and/or relocatable assetsconsist of METs. METs provide short-term, deployable, on-scene METOCcapabilities (e.g., data collection,ana lys is , fo recast ing , tac t ica lapplications, climatology), normally tounits and activities without organicMETOC personnel. METs carry portablesensing, processing, and displayequipment and have the capability toreceive and display satellite imagery andtheater METOC data broadcasts, as wellas to run tactical application programs.METs are capable of setting up

IV-18

Chapter IV

Joint Pub 3-59

automated weather systems at remotesites which sense temperature, humidity,pressure, and wind. Additional sensingcapabilities includes upper air support,acoustic profiling, and remote datacollection. Appendix K, “DeployableMETOC Equipment,” describes thesecapabilities.

• All Navy, Navy contract, and CoastGuard ships also take and report standardmaritime weather observations, with orwithout embarked METOC personnel.

• Amphibious ships also provide surfforecasts for potential landing areas,supported by sea-air-land team surfobservations.

d. MARFOR. Marine METOC supportincludes surface-based atmosphericobservations (clouds, visibility, winds,pressure, temperature, precipitation) andupper-air observations (temperature, winds,and humidity) for the area of interest;battlefield and aviation forecasts; weatherwarnings and advisories; meteorologicalwatch of target areas and air and groundavenues of approach; and interpretation ofthe effects of METOC conditions onoperations and personnel (this supportconsists of METOC information and forecasttactical indices for weapon and/or sensorsystem employment and tactical decision aids;climatological services; and planning and staffadvice). Marine METOC personnel whodeploy have the capability to use tacticalequipment to receive satellite imagery,measure atmospheric weather parameters(to include storm detection with weatherradar), and generate forecast products toprovide this support. MSTs from the MWSSwill provide METOC support to the commandelement, ground combat element and combatservice support element of the MAGTF. TheMSTs will be equipped with the InterimMobile Oceanography Support System(IMOSS) and a minifax capability, relying

heavily on communications with the MWSSMETMF. See Appendix K, “DeployableMETOC Equipment,” for equipmentdescriptions. In addition to Marine METOCsupport, artillery meteorological crewsprovide upper air observations for artillery firesupport. Additional METOC information canbe gained from aviation TARWI reports andfrom deployed reconnaissance forces via theintelligence chain of communications.

e. Special Operations Component. AirForce METOC personnel organized into SOWTsand Navy METs provide direct support andinformation to SOF at the tactical level usinga combination of surface observations, upper-air data, weather satellite, weather radar, MFCand JMFU products, locally generated products,space environment data, and climatology.Tailored information provided includessurface-based atmospheric observations(clouds, visibility, winds, pressure, temperature),upper-air observations (temperature, winds,humidity, and refractivity) and spaceenvironmental observations for the area ofinterest; advisories and warnings;climatological information; and interpretationof meteorological conditions on operationsand personnel as well as planning (this supportconsists of METOC information and forecastsfor operational use; forecast tactical indices forweapon and/or sensor system employment andtactical decision aids; and climatologicalinformation for long-range planning purposes).These SOWTs and/or METs have the capabilityto deploy and use tactical equipment to measureand record atmospheric conditions and totransmit, receive, and manipulate data from theMFC, the JMFU, and imagery from weathersatellites. They are equipped with a variety ofService and SOF-unique equipment to executethese capabilities.

7. METOC Forecast Center

The MFC consists of Air Force and Navyworldwide production and climatologyfacilities and theater and/or regional

IV-19


METOC production facilities . The MFCsupporting a joint operation is normallydesignated by the SMO or JMO in a LOI. Thedesignated MFC will coordinate the effortsof all other MFCs to ensure that a full suite ofproducts are available for use by the jointforces. The use of web technology is highlyencouraged to build a virtual METOC datawarehouse of support products. Allproduction facilities perform critical activitiesthat provide basic and applied METOCinformation to METOC forces and joint forceoperations. A designated MFC productionfacility may function as the JMFU during jointforce operations. Selection of an MFCproduction facility to fill the JMFU roledepends on location, capabilities, andcommunications connectivity. Theproduction and climatology facilities provideworldwide METOC data and products. MostMFC production sites maintain homepagetechnology which may or may not requirespecial identifications and passwords foraccess. JMOs and SMOs should maintainprocedures for accessing MFC production sitehomepages as well as procedures forrequesting specialized support. The regional

and theater component level organizationsprovide tailored METOC information for aspecific geographic area. Refer to AppendixM, “METOC Forecast Center,” for a break-out of MFC capabilities. Examples of MFCproducts include:

a. Current analyses for global andhemispheric scales;

b. Forecast products for extended timeperiods and large geographic areas;

c. Point-specific data;

d. Climatological analyses for long-rangeoperational and contingency support planning;

e. Space environmental analysis, forecast,and climatology products; and

f. Air Force operational weather squadronsproduce mission-scaled tailored forecasts,point weather warnings and/or advisories,point forecasts for bases, drop zones, landingzones, and air refueling tracks, plus flighthazard products.

IV-20

Chapter IV

Joint Pub 3-59

Intentionally Blank

APPENDIX ASMO AND JMO INVOLVEMENT IN PLANNING

A-1

1. Overview

This appendix provides assistance to theSMO and JMO involved in planning a jointoperation. The key to planning, whether foran exercise or real world operation, is earlyident i f ica t ion of spec i f ic suppor trequirements.

a. Planning Requirements. Theseinclude but are not limited to transportation,logistics, communications, and information.The size, structure, and content of METOCsupport depends on the JFC’s operationalneeds. METOC support will includeintegrating a mix of global, regional, andlocally produced METOC products as wellas data and products received from reliableforeign sources. METOC operations must beconsidered and included in long-rangeplanning, mission planning, and operationalexecution. Figure A-1 is a flow diagram thatcan be used by the SMO or JMO in thedevelopment of the specific METOC plan.

b. Planning Data and/or Climatology.The study and application of historicalMETOC information is invaluable forplanning, staging, and executing worldwidemilitary operations. In many cases, andespecially in the Third World, climatologicaldata provides the only METOC data available.Such information includes, but is not limitedto, summarized historical METOCinformation, derived environmental impactson weapon systems, and tailored narrativestudies. Exploiting this information can allowthe warfighter to take advantage of favorableMETOC conditions, minimize impacts of

“Never in the history of warfare have weather decisions played such animportant role in operational planning as they have here in Southeast Asia....”

General Creighton AbramsCommanding General, Vietnam, USMACV, 1968

adverse conditions, or use unfavorableMETOC conditions to gain advantage.

2. Joint Operation Planningand Execution System

The Joint Operation Planning andExecution System (JOPES) is the principalsystem within the Department of Defense fortranslating policy decisions into OPLANs andOPORDs in support of national securityobjectives. To accomplish this task, JOPESconsists of a deliberate and a crisis planningprocess shown in Figure A-2. Deliberateplanning is accomplished in five phases:initiation, concept development, plandevelopment, plan review, and supportingplans. The deliberate planning process cantake up to two years, but in reality is acontinuous process. In crisis situations,planners follow established crisis actionprocedures. These procedures provide for therapid and effective exchange of informationand analysis, timely preparation of militaryCOAs for consideration by the NationalCommand Authorities (NCA), and the prompttransmission of NCA decisions to supportedcommanders. The impact and need forMETOC information is important to the crisisaction planning process and is outlined below.

a. Situation Development. When anevent occurs with possible national securityimplications and a CINC’s assessment iswarranted, the SMO can provide valuableinput to the CINC. This includes:

• Current METOC conditions (land, ocean,air and space) in the area of interest;

A-2

Appendix A

Joint Pub 3-59

METEOROLOGICAL AND OCEANOGRAPHICOPERATION PLAN DEVELOPMENT

Consider joint force plan

Determine the operating area

Determine the joint force structure

Determine organic METOC capabilities and what METOC information is required

Determine theirobserving and/or

forecastingtaskings

Canexisting

capabilitiesmeet

requirements?

YES

YES

CONOPSJFCJMFU

concept of operationsjoint force commanderjoint METOC forecast unit

LOIMETOCMFCOPLAN

letter of instructionmeteorological and oceanographicMETOC Forecast Centeroperation plan

YES

NO

NO

NO

Can theysupport

OPLAN and/orCONOPS?

Determine support requirements

Inform JFC Staff

Develop acquisition strategy

Obtain capability

Is JMFUrequired?

What communicationsare required to support

flow of METOCinfo from MFC,

JMFU and components?(J-6 determines)

Develop acquisition strategy

Obtain capability

Inform unitsOf responsibility

Produce METOC Annex H to plan

Coordinate on and provide inputs to other applicable annexes

Integrate intooverall concept

Inform subordinateunits of responsibility

in component LOI

Determinesupport

requirements

Develop orobtain

capability

Figure A-1. Meteorological and Oceanographic Operation Plan Development

• Climatological factors;

• Forecast weather;

• Potential METOC impact on the event,

to include suitability of sites foremployment of forces; and

• Degree of accuracy and limitations offorecast products.

A-3

SMO and JMO Involvement in Planning

b. Crisis Assessment. During CJCSassessment of the event and review of theCINC’s Assessment, METOC support can aidin the determination of whether to initiatemilitary action and how METOC conditionsmight impact potential military options.

c. COA Development. The arrival of theCJCS warning order denotes a critical phasefor the SMO. Development of a realistic,efficient, and effective COA can be criticallylinked to METOC information. The taskingof subordinates to provide input to this processinvolves another layer of METOC officers thatcan significantly improve the METOC database for the operating area. Appendix B,“METOC Information in Operation Plans,”provides guidance on the METOC

information requirements of the CINC’s“Commander’s Estimate” message.

d. COA Selection. This is the time forcommunication between the SMO, JMO (ifidentified), and Service component METOCplanners who will provide the METOCpersonnel, equipment, and services judgednecessary to fully support the plannedoperation.

e. Execution Planning. During this phasethe OPORD is developed by modifying anexisting OPLAN, expanding an existingCONPLAN, or building an OPORD fromscratch. Appendix B, “METOC Informationin Operation Plans,” provides guidelines forthe preparation of OPLAN Annex H, METOC

JOPES DELIBERATE PLANNING PROCESS AND CRISISACTION PLANNING PROCESS FUNCTIONAL ALIGNMENT

DELIBERATEPLANNINGPROCESS

CRISIS ACTIONPLANNINGPROCESS

APPROVED FORFURTHER PLANNING

PHASE IINITIATION

PHASE IICONCEPT

DEVELOPMENT

PHASE IIIPLAN

DEVELOPMENT

PHASE IVPLAN

REVIEW

PHASE VSUPPORTING

PLANS

ALERTORDER

EXECUTEORDER

PHASE ISITUATION

DEVELOPMENT

PHASE IIICOA

DEVELOPMENT

PHASE IVCOA

SELECTION

PHASE VEXECUTIONPLANNING

PHASE IICRISIS

ASSESSMENT

PHASE VIEXECUTION

THREATIDENTIFICATION& ASSESSMENT

STRATEGYDETERMINATION

COADEVELOPMENT

DETAILEDPLANNING

WARNINGORDER

JSCP

IMPLEMENTATION

Figure A-2. JOPES Deliberate Planning Process and Crisis ActionPlanning Process Functional Alignment

A-4

Appendix A

Joint Pub 3-59

Services, and details other annexes requiringMETOC input.

f. Execution. The JFC assembles theorganization and implements the OPORD.

Communication must continue between theSMO, JMO, and the Service components tofacilitate problem solving and to ensure thatthe commander has a METOC organizationappropriate to the mission.

APPENDIX BMETOC INFORMATION IN OPERATION PLANS

B-1

1. Overview

This appendix summarizes standardlocations where METOC information is usedwithin the JOPES. It is provided to aid theSMO and JMO in determining where andwhat METOC information can be integratedwith other staff functions as the JFC’s plandevelops. JMOs should work with theappropriate J-staffs to ensure that METOCguidance and information provided in otherfunctional annexes are complete and accurate.

Reference CJCSM 3122.03, “Joint OperationPlanning and Execution System Vol II:(Planning Formats and Guidance),” forAnnex formats and guidance on whereMETOC information should be included.

“It is always necessary to shape operation plans.....on estimates of theweather, and, as this is always changing, one cannot imitate in one seasonwhat has turned out well in another...”

Frederick the Great: Instructions for His Generals, iii, 1747

2. JMO Responsibilities

The JMO is responsible for METOCinformation commonly used in theintelligence estimate, the commander’sestimate of situation, and OPLAN AnnexesB, C, H, K, and N.

a. Intelligence Estimate. Accurate andtimely METOC information can help in theformation of an accurate intelligenceassessment. The intelligence estimatedescribes the topography, terrain, andapproaches and exits from borders; naturalobstacles; the nature of the coastline; adjacentislands; location, extent, and capacity oflanding beaches and their approaches andexits; and the nature of the offshore

METOC information assists in the formation of an accurate intelligenceestimate, including the nature of the offshore approaches.

B-2

Appendix B

Joint Pub 3-59

approaches, including type of bottom andgradients; natural obstacles; and surf, tide,and ocean and/or water current conditions.The intelligence estimate requires METOCparameters such as temperature, humidity,cloud cover, visibility, precipitation,illumination data, and other METOCconditions to assess effects on roads,airfields, rivers, and soil trafficability. Fromthese METOC specifications, geographicintelligence personnel can accurately gaugethe METOC effects on enemy capabilities andpossible COA for friendly and enemy forces.

b. Commander’s Estimate of theSituation. The commander’s estimate willinclude the characteristics of currents, tides,and similar maritime considerations, anddetermine and state extremes of temperature,wind velocities, cloud cover, visibility,precipitation, and other such factors that canaffect all military operations. Sunrise and set,moonrise and set, civil, nautical, and/orastronomical twilight data, and moon percentillumination are also normally provided.

c. Annex B, “Intelligence.” Annex B willsummarize the hydrographic data (waterdepths, tides, wave height, and currents)needed to support amphibious and logistics

over-the-shore operations. reference AnnexH and any others (C, K, N, etc.) as required;include climatology and weather aspects asthey pertain to the operational environment;and perform a thorough intelligencepreparation of the battlespace from a METOCperspective.

Use JP 2-01.3, “Joint Tactics, Techniques, andProcedures for Joint Intelligence Preparationof the Battlespace,” as a guide.

d. Annex C, “Operations.” Annex C willsummarize the general nature of METOCphenomena or conditions, with emphasis onthose that could have an impact on the mainand supporting efforts of the operation, as wellas any planned deception actions.

e. Annex H, “METOC Operations.”This is the SMO’s and JMO’s primary vehiclefor describing the METOC operations withina joint force.

• List documents that provide informationrequired for use with this annex.

• State the general concept of METOCsupport for the forces assigned to theOPLAN.

Amphibious assault operations heavily depend on hydrographic data.

B-3

METOC Information in Operation Plans

• State the assumptions that affect theMETOC operations required by the plan.Realistic estimates of the availability ofdata and facilities in the joint operationsarea, availability of support from non-US and US nonmilitary agencies, and thefeasibility of obtaining METOC datafrom satellites will be included.

• Identify any significant METOCconditions that may influence theexecution of the plan. The purpose ofthis paragraph should be to establish therequirement for any unusual METOCoperations that will clarify the assignmentof specific responsibilities. METOCfactors that may influence operations andthe probability of their occurrence willbe included.

• State clear and concise METOCoperation objectives in support of theplan.

• Describe the METOC support systemand how it will function in theimplementation of the plan. Refer toother documents available to tasked unitsthat establish doctrine and procedures, as

appropriate. Note any deviations fromstandard practices and any additionalprocedures peculiar to the operation.

• Identify the Service component(s)responsible for providing METOCsupport to the operation, includingcommunications and productionresponsibilities for METOC information.Assign responsibilities to specific Servicecomponents. Ensure that operationssecurity (OPSEC) planning guidance isincluded so as to not reveal indicators offriendly intentions. Clearly delineate foreach applicable component or othersubdivision of the force individualMETOC services, tasks, and responsibilities.Ensure that severe weather notificationprocedures are outlined for each METOCagency throughout the AOR.

• Coordinating Instructions. Include theinstructions common to two or morecomponents or subdivisions.

• Administration and Logistics. Providebroad guidance on how logistic andadministrative support is to be furnishedfor the METOC forces (a reference to the

Unusual METOC conditions can impact operations.

B-4

Appendix B

Joint Pub 3-59

OPLAN’s Annex D or other pertinentcommand directives may suffice.)

• Command and Control. Indicate thechannels for control of METOCoperations if different from the commandrelationships outlined in the basic planor in Annex J. Provide instructions tocover periods when communicationcircuits are not operational. Provideinstructions for transmitting METOCinformation to units where METOC orstandard C2 circuits are not available.Provide instructions for denyingMETOC data and information to theenemy through implementation ofcontrol of meteorological information(METCON), oceanographic information(OCEANCON), ice information(ICECON), and space information(SPACECON). Provide a shortdescription of strategic and tacticalcommunications architectures that willbe developed to support METOC datatransmission and information flow.

See JP 3-54, “Joint Doctrine forOperations Security,” for furtherguidance on operations security issues.

f. Annex K, “Command, Control, andCommunications Systems.” Communicationsis an essential element of METOC operations.Because METOC data is extremelyperishable, effective METOC operations aredependent on timely, reliable communicationssupport. The joint communicationsarchitecture should support the collection orinterception, storage and retrieval,dissemination, quality control, and processingof large amounts of data. High-speedcommunications are required to rapidlytransmit and receive real-time global scaleMETOC information between the MFC,JMFU, component, and tactical units. Workwith the J-6 to determine the overarchingcustomer backbone communicationarchitecture. METOC communicationsconcept, procedures, and requirements tosupport METOC information flow throughoutthe joint force operating area should beincluded in this annex. Coordinate with J-6on the development of the technical details inAnnex K (e.g., network diagrams that identifyall connectivities). In general, the METOCproviders are subscribers to the DISN and tothe tactical communication resources listed inAnnex K. Annexes H and K will not list allof the communications resources used to

Solar activities can impair communication capabilities.

B-5

METOC Information in Operation Plans

generate and disseminate METOC products.For example, a wide array of communicationsnetworks and serial connections are used todisseminate and share data among theparticipants of the data exchange agreementsin the World Meteorological Organization andthe US Office of the Federal Coordinator forMeteorological Services and SupportingResearch. These nonsecure communicationresources, although not part of the Departmentof Defense Information Infrastructure, arecritical to the production centers. Specialattention must be given to coordinating theirinclusion into the communication architecture(Annex K to the OPLAN) to make sure theinformation is accessible.

g. Annex N, “Space Operations.” AnnexN provides a description of weather satellites

and weather satellite terminals available to theAOR, along with a brief description of thecapabilities these terminals provide. Itmentions types and levels of possibledegradation to communications, radar, andnavigation systems due to solar, geomagneticdisturbances which can cause missionimpacts. Commanders may require specificquantification of impacts at execution; thislevel of detail will be facilitated as METOCcapabilities mature. Annex N will state howan operator can obtain assistance from the 55th

SWXS to mitigate the problems to friendlyforces or exploit the space environment togain an advantage over adversaries.Optimally, this requires the SMO, JMO, andcomponent METOC forces to be proactiveon behalf of their customers in assessingspace impacts.

B-6

Appendix B

Joint Pub 3-59

Intentionally Blank

APPENDIX CMETOC LETTERS OF INSTRUCTION

C-1

1. Overview

This appendix identifies the type ofguidance an SMO or JMO shouldcommunicate to joint force METOC and otheroperational forces via an LOI. An LOI maybe published when an OPORD is not yetavailable or when additional information mustbe passed to lower joint echelons.

2. Contents

The JMO, or the SMO if the CINC has notyet established a JTF, should issue the initialLOI message based on information collectedduring the first stages of the deliberate and/orcrisis planning process for an exercise oroperation. The first message may not be acomplete LOI and is intended to alert theMETOC community of the forthcomingactivity or assignment. Subsequently, ifrequired, the JMO prepares a complete LOImessage which details taskings andinstructions for all aspects of METOCsupport. The LOI should be sent to all unitsin the joint force, supporting forcecommanders, and all supporting activities (i.e.,MFC) and included as part of the METOChomepage on the SIPRNET (if available).This message should amplify informationcontained in Annex H of the OPLAN.Potentially, if an Annex H is not developed insupport of a joint force operation, the LOIwould provide the necessary information tosynchronize METOC support. Informationthat is available in an Annex H is not expectedto reappear in the LOI unless a change isrequired.

3. LOI Topics

The following is a comprehensive listingof topics that might be included in a METOCLOI message.

a. Originator. CINC, subordinate JFC,and/or delegated authority.

b. Addressees. All units in the force,supporting force commanders, and supportingactivities, to include senior Service METOCpersonnel.

c. Classification. As appropriate.

d. Subject. Unclassified subject thatincludes exercise or operation name followedby “METOC LOI.”

e. Reference. Reference all othersupporting CONOPS, OPORDs, OPLANs,CONPLANs, and exercise plans.

f. Points of Contact. The SMO’s andJMO’s names and phone numbers should beindicated in this section.

g. Purpose. Provide a concise descriptionof the purpose to be achieved by implementingthe LOI.

h. Situation. Describe the situation thathas created the need to establish a joint forceMETOC operation.

i. Concept of METOC Operations. Statethe general concept of METOC operations forthe forces assigned to the OPLAN and anyJMFU and MFC involvement. Describe theMETOC system and how it will function inthe implementation of the plan. Refer toAnnex H and other documents available totasked units that establish doctrine andprocedures, as appropriate.

j. Assumptions. State the assumptions thataffect the METOC operations required by theplan.

C-2

Appendix C

Joint Pub 3-59

k. Planning Factors. State the significantMETOC conditions that may influence theexecution of the plan. Detail air, sea, and spaceclimatology during operations.

l. Mission. Concisely state the METOCobjectives in support of the JFC plan.

m. Execution. Provide the time period ofexpected operations, METOC staff locations,responsibilities for METOC informationmanagement, tasks and responsibilities,coordinating instructions, and operationalconstraints. Include an overall sensingstrategy and/or plan as required. Thefollowing should be detailed.

• SMO responsibilities, duties, andlocation.

• JMO responsibilities, duties, andlocation.

• JMFU composition, equipment, location,products provided, product schedule, andcommunication capabilities.

• A list of MFC production facilitiesinvolved and their responsibilities.

• A list of METOC teams on functionaland Service component staffs and theirlocations

n. Deployment. Provide the time METOCforces will be on station.

o. OPSEC. Describe OPSEC requirements.

p. Coordination Instructions. Provideinstructions common to two or morecomponents or subdivisions.

q. Operational Constraints. Providerestrictions due to manning, equipment, orother areas that might impact operations. In

addition, issue guidance directing eliminationof personnel and equipment duplication inboth joint and Service echelons to reducemovement requirements and the footprint ofdeployed personnel.

r. Administration and Logistics. Providebroad guidance on how logistic andadministrative support and/or requirementsare to be furnished for METOC operations (ifnot already documented in a related OPLANAnnex H).

s. Equipment and Supplies. Listequipment requirements for the functionalcomponent METOC teams and/or staffs andexpendable supply requirements.

t. Command and Control. Summarizethe command relationships applicable to theconduct of the operation.

u. METCON, OCEANCON, ICECON,and SPACECON. Provide instructions forimplementation as required by JFC.

v. Communications. Detail communicationsguidance to include METOC data flow intoand out of the joint force operating area.Address homepage availability and accessprocedures, NIPRNET and/or SIPRNETconnectivity and address list, high frequency(HF) regional broadcast (HFRB), fleet HFFAX broadcast, HF METOC net availability,and products. Designate “KQ” identifiers forMETOC units as required.

w. Reporting. Detail METOC reportrequirements (e.g., after action reports,equipment status, product assessments)including content and delivery times.

x. METOC Assistance Requests.Provide guidance for requesting specialMETOC products not in normal distributionthrough MARs.

APPENDIX DMETOC DATA SOURCES FROM NON-METOC OPERATIONS

D-1

1. Overview

This appendix summarizes METOC datathat is available from sources other thanongoing METOC operations described inChapter IV, “Joint Force METOCOperations.” This additional data is criticalto supplementing the METOC data base fromwhich the various METOC echelons deriveforecast products.

Special Weather Intelligence availablethrough intelligence sources is described inJP 2-01, “Joint Intelligence Support toMilitary Operations.”

2. ARFOR

In addition to the weather operationsprovided by the Air Force, the Army hasorganic resources which provide supplementalreports of METOC conditions. These Armyelements possess a limited measuringcapability designed to meet their ownimmediate needs. Consequently, theirMETOC observing capabilities aresupplemental to their primary mission. Theyshould not be viewed as a replacement orsubstitute for Air Force METOC operations.Since Army units are mobile, locations mustbe included as part of the METOC report;consequently, the Army requires these reportsto be classified and transmitted over securecommunications channels. Within the Armystructure, secure METOC communicationstravel either over HF radio (IMETS and/or

“In modern warfare, any single system is easy to overcome; combinations ofsystems, with each protecting weak points in others and exposing enemyweak points to be exploited by other systems, make for an effective fightingforce.”

Vice Admiral Stanley R. ArthurCommander, US Naval Forces, Central Command

Operation DESERT STORM

quick reaction communications terminal[QRCT] III ) or mobile subscriber equipment(MSE), or SIPRNET systems to the highestArmy echelon. This echelon will relay thedata to the JMFU via available secure means.The following represents the most significantsources of weather data within the Armytactical structure.

a. Artillery Meteorological (ARTYMET)Sections

• ARTYMET teams are assigned to, anddeploy with divisions and separate fieldartillery brigades. In general, theARTYMET teams provide upper-airobservations and artillery limitedsurface observations; however,meteorological support varies with themission of the Army unit. Specializedmeteorological teams can be deployedto support missions as needed. Forinstance, the need for falloutmeteorological messages requires thatone meteorological section bedesignated to produce fallout data.

• Geographical locations of themeteorological sections will vary withatmospheric conditions,communications capabilities,administrative support, and localsecurity as well as artillery unitlocation.

• Data Collection Capabilities

D-2

Appendix D

Joint Pub 3-59

•• ARTYMET sections are equipped toperform upper-air observationsemploying a balloon-sounding method.These sections can electronically soundthe atmosphere and provide upper-airwinds, temperatures, and densities toheights of 98,424 feet (30,000 meters),day or night, and in all types of weatherexcept during severe surface winds. Ifelectronic equipment fails, they have analternate, but limited, method ofmeasuring upper-air winds by visuallyobserving pilot balloons. A limitingfactor is the time required for a soundingballoon to reach its required height(normally 2 hours to reach 30,000 meters).However, the sections are capable ofsounding the atmosphere every 4 hours and,once in position, can produce a ballisticmessage for light artillery within 30 minutesafter releasing the balloon.

•• ARTYMET sections can produce thefollowing: computer meteorologicalmessages, fallout messages, upper-airdata, target acquisition meteorologicalmessages, and limited surface weatherobservations.

• Communications Capabilities

•• At the Corps level, the sections arenormally equipped with frequencymodu la t ion rad io and MSEcommunications for verbal and dataexchange capabilities. Meteorologicaldata can be acquired by monitoring thisnet at specified times.

•• At the Division level, units may obtainmeteorological data over the divisionartillery fire direction radio net, andthrough Tactical Fire Direction ComputerSystem automatic data processing (ADP)systems.

b. Air Traffic Control (ATC) Units. ATCunits may have weather-observing

instruments to include measurement of surfacepressure, temperature, and surface windvelocity and direction. In addition, aircrews,flight operations personnel, and control toweroperators visually estimate horizontalvisibility and obstructions to visibility. Theyalso observe such special phenomena aslightning, thunderstorms, and tornadoes.Control tower operators assigned to ATC unitsare trained by Air Force METOC personnelto make limited weather observations.

c. Engineer Units. The engineers canprovide stream flow measurements andpredictions of river stages and floods.

d. Ground Reconnaissance andSurveillance Elements. Cavalry unitsprovide the Corps and Division principalground reconnaissance capability. Cavalryand maneuver battalions have organic groundreconnaissance capability that may be usedto obtain information related to weather,terrain, and overall environmental conditionsrequested by the intelligence staff officer (G-2and/or S-2). In addition, long-rangesurveillance units at Division and Corps maybe required to take weather observations deepacross the forward line of its own troops basedon specific weather requirements meeting thegiven situation.

e. Imagery Interpretation Elements.These units can provide information onvisibility, cloud cover, trafficability, andflooding.

f. Armored Cavalry Regiment (ACR),Brigade, Battalion, and SquadronIntelligence Personnel. ACR, brigade,battalion, and squadron intelligence officersare tasked by the G-2 to provide supplementalweather observations. The frequency ofobservations depends on the intelligencepreparation of the battlespace process whichidentifies critical areas where adverse weathermay have a major impact on land forceoperations, weapons, personnel, and tactics.

D-3

METOC Data Sources from Non-METOC Operations

High priority must be placed on thesemessages to transmit them immediately to theAir Force staff weather officer (SWO) at theDivision, Brigade, or Regimental MainCommand Post.

g. Supplemental WeatherObservations Taken by Army Personnel.Doctrinally, the Army is responsible forcollecting weather and environmental datafrom areas in which Air Force METOCpersonnel are not manned, trained, orequipped to operate. To accomplish this,the Army provides supplementalobservations under FALOP. The lowerechelon S-2 transmits the supplementalobservations promptly to higherheadquarters. These observations requirea high priority to ensure transmission within15 minutes of the time they are taken. TheG-2 specifies the supplemental observationrequirement and ensures that theseobservations flow directly to the USAFCWT, which handles further distribution.The supplemental observations serve as thebasis for the G-2 and SWO to determinethe effects of adverse weather on Armysystems, operations, and tactics. The CWTincorporates supplemental observations

with all other sources of information, whenthey are available, to make a completeweather picture of the battlefield at the timeof the observation. In some cases, thesupplemental observations may be the onlysource of observations in forward areas andare the key to forecasts tailored to the user’sneeds. The collected data in a supplementalweather observation taken by Armypersonnel may include measurement oftemperature, wind direction and speed,cloud information, visibility estimate, typeof precipitation and intensity, atmosphericpressure, and road, ground, and waterconditions.

h. Aviation Squadrons and/or Brigades.Aircrews provide en route pilot reports viaradio to ATC units and/or USAF CWTs; or,upon return from the flight, to the USAF CWToperating location for use in developing theirforecast products.

i. Space Support Teams. The Armyobtains some space environmentalinformation from satellite operationssquadrons and Army space support teams aswell as outside sources, such as universitiesand research facilities.

Reconnaissance personnel can take weather observationsdeep into enemy territory.

D-4

Appendix D

Joint Pub 3-59

3. NAVFOR

a. The following represent the mostsignificant sources of METOC data within theNavy tactical structure.

• Battle Force Surface Ships

• Carrier Air Wing

• Maritime Patrol Aircraft

• Submarines

• Naval Air Stations and/or Facilities

METOC observations taken by these unitsconsist of surface weather, upper air, PIREPs,and bathythermograph (BT) data.

b. Battle Force Surface Ships. All battleforce and/or group surface combatants(aircraft carriers, cruisers, destroyers, frigates,amphibious, mine warfare, and logisticsupport ships) provide METOC surfaceweather observations every 6 hours while atsea. These reports are submitted on thesynoptic hours of 0000Z, 0600Z, 1200Z, and1800Z. If the winds exceed 35 knots or theseas exceed 12 feet, then the reporting rate

increases to a report every 3 hours until thewinds and/or seas decrease to below theselimits. All ships at sea are required to takeregular observations, but where ships aresteaming in company or in close proximity,the officer in tactical command may designateone ship to report for the group.

• All antisubmarine warfare (ASW) ships(cruisers, destroyers, and frigates) collectBT data by dropping an expendabletemperature sensor into the sea.Operational requirements drive thecollection rate of BT data.

• Upper-air observations are regularlycollected by those Navy vessels with apermanently assigned OA or embarkedMET. Upper-air observations areroutinely taken twice per day and targetedfor the synoptic times of 0000Z and1200Z.

c. Carrier Air Wing. Aircrews providemeteorological observations and PIREPs asspecified by their mission, or when requiredin areas of sparse data. PIREPs are submittedvia radio or upon return from the flight to thecarrier weather office for inclusion in theirforecast products.

Navy surface ships take routine weather observations.

D-5

METOC Data Sources from Non-METOC Operations

d. Maritime Patrol Aircraft. Aircrewsprovide meteorological observations asspecified by their mission, or when requiredin areas of sparse data. Aircraft observationsare transmitted when radio contact is made,or are delivered (along with observations ofunexpected en route weather), to the NavalMeteorology and Oceanography Command(NAVMETOCCOM) activity at the air stationat which the aircraft lands. BT observationsshall be taken by sonobuoy equipped aircraftin open ocean areas where depths exceed 100fathoms. A minimum of one BT observationshall be taken during each ASW flight whichuses sonobuoys. All collected data will besubmitted to the NAVMETOCCOM activityat the air station at which the aircraft lands.

e. Submarines. Submarines are capableof, and can be tasked with, collecting surfaceweather and BT observations. They will takeand report these observations unlessoperational requirements preclude them fromdoing so.

f. Naval Air Stations and/or Facilities.METOC personnel at these sites providesurface observations, upper air soundings, andterminal aerodrome forecasts.

g. Space Support Teams. The Navyobtains some space environmentalinformation from satellite operationssquadrons and Navy space support teams aswell as outside sources, such as universitiesand research facilities.

h. Communication procedures forMETOC observations include locations;therefore, the Navy requires these reports tobe classified to protect ship and aircraftoperating locations. All METOCobservations collected by the Navy areforwarded to the collective address designator(CAD) “OCEANO WEST” or “OCEANOEAST.” These CADs distribute observationsto the Fleet Numerical Meteorology andOceanography Center (FLENUMMETOCCEN),Monterey, California, Naval OceanographicOffice (NAVOCEANO), Stennis SpaceCenter, Mississippi, and Air Force WeatherAgency (AFWA) for use in their forecastmodels and for further distribution to all Navalfleet units requiring observation data. TheCAD’s OCEANO EAST and OCEANOWEST include theater METOC centers.OCEANO EAST contains the NavalEuropean Meteorology and OceanographyCenter (NAVEURMETOCCEN ROTA SP)

Submarines are capable of collecting METOC information.

D-6

Appendix D

Joint Pub 3-59

and the Naval Atlantic Meteorology andOceanography Center (NAVLANTMETOCCENNORFOLK VA). OCEANO WEST includesthe Naval Pacific Meteorology andOceanography Centers in Pearl Harbor,Guam, Yokosuka, San Diego, and Bahrain(NAVPACMETOCCEN PEARL HARBORHI, NAVPACMETOCCEN WEST GU,NAVPACMENTOCCEN YOKOSUKA,NAVPACMETOCCEN SAN DIEGO, andNAVCENTMETOCCEN BAHRAIN,respectively).

4. AFFOR

The most significant non-METOC AirForce sources of weather data are aircrews.This is often in the form of PIREPs and airreports, or the information is contained in theTARWI report. ATC teams have limitedobservation capabilities. Also, the Air Forceobtains some space environment informationfrom satellite operations squadrons as well asoutside sources, such as universities andresearch facilities.

5. MARFOR

Marine ARTYMET sections providemeteorological data for artillery firing unitsin the same manner as the Army. They also

provide upper-air observations and artillerysurface observations which can be added tothe overall METOC data base. Marine Corpsaircrews are tasked with providing TARWIreports and PIREPs. Limited observations areavailable from reconnaissance forces throughintelligence channels. ATC detachments alsohave wind and pressure sensors.

6. Special Operations

Depending on the size and composition ofthe forces, special operations components willdeploy with similar capabilities to theirequivalent conventional Service components.Army and Air Force special operationsaviation units can provide PIREPs andTARWI reports from missions into deniedareas. Forward area weather observations canbe taken by special forces teams, specialoperations combat control teams, specialoperations weather teams, and Ranger unitsin denied areas and transmitted to the JSOTFon an irregular basis. Naval special warfaretask units can provide beach profile data aswell as surf zone observations. Although thisdata is required by the JMFU to help thembuild a coherent METOC picture, JMOs mustbe sensitive to OPSEC considerations whenincorporating this data into their theatersensing strategy.

TARWI information from aircrews are an integral part ofdetermining battlefield weather conditions.

APPENDIX EJOINT OPERATIONS AREA FORECAST

E-1

1. Overview

This appendix provides an example of thetype of information that the JOAF couldprovide and the details which need to beworked by the JMO, JMFU, and the joint forcecomponents. The JOAF, as approved by theJMO, is the official planning forecast for allcomponents of the joint force. It is issued atthe JFC level to ensure that all componentsare aware of what the JFC is using to plan thecoordinated battle. Significant deviationsfrom the JOAF will be coordinated with theJMO. Components and individual units willuse the JOAF as the point of departure to tailorMETOC information and to develop tailoredmission execution forecasts. The JOAF mayinclude a forecast data base when needed fortactical decisions used in planning.

2. Example of a JOAF

a. Part 1. Current and ProjectedSituation Discussion. This discussionintegrates synoptic, upper-air, and METSATinformation; highlights influences on, orpotential for, any forecast significant surfaceor upper-air weather in the joint operationsarea (JOA); and provides cumulativesummary and assessment for weather ofcontinuing duration (e.g., strong winds,continual rainfall for flooding potential, orlack of rain for drought conditions).

b. Part 2. 0-24 Hour Forecast. Thisforecast will detail and/or partition area(s)affected within the JOA as required (identify

“People have to fight in war on all sorts of days, and under all sorts ofconditions...”

Winston Churchill14 Aug 1940

affected ranges, air refueling tracks, etc.);briefly summarize and/or characterize modelinitialization (e.g., “good, but slightly fast”);and provide 0-24 forecast of the followingcriteria.

• Clouds (amounts, bases and/or tops).

• Upper-air significant weather and/orlevel(s) (turbulence, icing, thunderstorms).Moderate and severe intensities are key.

• Surface significant and/or sensibleweather (winds, thunderstorms [and hailw/size, if applicable], rain). Surfacewinds (or gusts) >= 35 knots are usuallyconsidered a key threshold.

• Sea state (surf levels, tides, watertemperatures, turbidity) as required.

• Surface visibility.

• Surface temperatures (highs and/or lows)with wind chill or heat indices, asappropriate. -20ºF and below is a keylevel for wind chill, and 105ºF and aboveis key for heat index.

• Minimum altimeter setting.

c. Part 3. 24-72 Hour JOA Outlook. Byexception only. If no change, so state.

d. Part 4. 3-5 Day JOA Outlook. Byexception only. If no change from 24-72 houroutlook, so state.

E-2

Appendix E

Joint Pub 3-59

Intentionally Blank

APPENDIX FEXAMPLES OF METOC INFORMATION REQUIREMENTS

AND RESPONSIBILITIES WITHIN A JOINT FORCE

F-1

Figure F-1. Example of Air Refueling Forecast Parameters

EXAMPLE OF AIR REFUELING FORECAST PARAMETERS

Parameter Elements Ke y Threshold

CloudsAmount, type, bases and/ortops

Any ceiling at flight level

VisibilityFlight level visibility (nauticalmiles [NMs])

Visibility < 1 NM

Thunderstorms Coverage and maximum tops Any occurrence

Icing Type, bases and/or tops Moderate or greater

Turbulence Type, bases and/or tops Moderate or greater

F-2

Appendix F

Joint Pub 3-59

Figure F-2. Examples of METOC Information Requirements andResponsibilities Within a Joint Force

EXAMPLES OF METOC INFORMATION REQUIREMENTS ANDRESPONSIBILITIES WITHIN A JOINT FORCE

Information(see instructions at end of Appendix)

JMFU/MFC

Functional orService Component

Tactical Level

Air Refueling Track Forecasts

Altimeter

ASW Products (Acoustics, Bottom Cond., etc.)

Ballistic Winds

Bathythermograph and/or Sound Profiles

Ceilings and/or Cloud Layers a/o Bases and Tops

CHAFF Forecast

Chemical Downwind Message

Cloud Free Line of Sight Forecasts

Clouds

Computerized Flight Plan

Contrails

Currents, Speed, and Direction

Customer Threshold Forecasts

D-Values

Deep Layer Mean Winds

Ditch Headings

Drop Zone and Landing Zone Forecasts

Ducting and/or Refractivity Index

EO-TDA and/or Automated

Forward Looking Infrared (IR) Forecast

Freezing Level

Fronts and Eddies

Geomagnetic Conditions

HF, Radar, and/or Radio Propagation Forecasts

High Resolution Forecast Database

High Seas Warnings

Horizontal Weather Depiction

Ice Edge and/or Bergs

Ice and/or Snow Coverage

Icing

Ionospheric Scintillation

IR Thermal Crossover Times

IR Transmissivity

Integrated Refractive Effects Prediction System

Jet Stream (Location and Strength)

Joint Operations Area Forecast

Lighting Detection

Longwaves, 500mb

Moisture and/or Humidity

F-3

Examples of METOC Information Requirements and Responsibilities Within a Joint Force

Figure F-2. Examples of METOC Information Requirements andResponsibilities Within a Joint Force (cont’d)

EXAMPLES OF METOC INFORMATION REQUIREMENTS ANDRESPONSIBILITIES WITHIN A JOINT FORCE (cont’d)

Information(see instructions at end of Appendix)

JMFU/MFC

Functional orService Component

Tactical Level

Nighttime Illumination

Optimum Track Ship Routes

Pilot Weather Reports

Precipitation (Type and Amount)

Radar Observations

Relative Humidity and/or Moisture Fields (Sfc-10,000 ft)

Sea Surface Conditions

Search and Rescue

Severe Weather Advisory and/or Forecast

Shore Conditions

Shortwaves, 500mb

Soil Surface Temperature

Soil and/or Ground Moisture Fields (6 in. depth)

Solar Activity

Solar Wind Conditions

Sound Focus

Surf Forecasts

Synoptic Charts

Synoptic Discussions

Temperature Forecasts (Max and/or Min, etc.)

Terminal Aerodrome Forecasts

Tidal Data

Thickness, 1000-500mb

Thunderstorms

Tropical Storm Advisories

Tropopause Heights and/or Winds

Upper Air Charts

Upper Air Observations

Upper Trop Mean Winds

Visibility

Vorticity (500mb)

Winds

Weather Observations

Wet Bulb Globe Temperature Index

Turbulence

Windshear

Use of this Appendix:1. Use the above items as a list of parameters in which one or more of the METOC agencies listedabove may have a need or interest. Mark which agency or agencies would have an interest in a specificMETOC parameter.2. The above list is not intended to be all-inclusive, but to serve as a memory-jogger when establishingMETOC information requirements. Feel free to copy it and use as is, or to fold it in as part of your AnnexH and OPORD writing process.

F-4

Appendix F

Joint Pub 3-59

Intentionally Blank

APPENDIX GMETOC IMPACTS TO SELECTED OPERATIONS

G-1

Figure G-1. METOC Impacts to Selected Operations

METOC IMPACTS TO SELECTED OPERATIONS

OPERATION FAVORABLE(No Degradation)

(GREEN)

MARG INAL(Some Degradation)

(AMBER)

UNFAVORABLE(Significant Degradation)

(RED)

ARFOR OPERATIONS

BRIDGING WIND < 10 KTS WIND 10-34 KTS WIND > 34 KTS

ARMOR GUN SIGHTS VIS > 2000 m VIS 1000-2000 m VIS < 1000 m

TOW MISSILE VIS > 3000 m VIS 2000-3000 m VIS < 2000 m

HELICOPTER (LIFT) CIG > 500 FT CIG 300-500 FT CIG < 300 FT

(no specific airframe) VIS > 1600 m VIS 800-1600 m VIS < 800 m

NO ICG/TURBC LGT OR MDT SVR TURBC/ICG

TURBC OR ICG

HELICOPTER (ATTACK) CIG > 2600 FT CIG 1100-2600 FT CIG < 1100 FT


WIND < 25 KTS WIND 25-50 KTS WIND > 40 KTS

TEMP > 90F

NO PRECIP MDT PRECIP HVY PRECIP

NO Thunderstorms FEW Thunderstorms SCT Thunderstorms

HELLFIRE MISSILE CIG > 2000 FT CIG 800-2000 FT CIG < 800 FT

VIS > 5000 m VIS 3000-5000 m VIS < 3000 m

CLOSE AIR SUPPORT CIG > 2000 FT CIG 1000-2000 FT CIG < 1000 FT

(For Army PlanningPurposes)

VIS > 8000 m VIS 3200-8000 m VIS < 3200 m

AERIAL RECON < 2/8 CLD COVER 2/8-4/8 CLD COVER > 4/8 CLD COVER

VIS > 8000 m VIS 4800-8000 m VIS < 4800 m

Aerial Recon covers three levels — Strategic (above 25,000 ft),High (8,000 - 25,000 ft), and Low (below 3,000 ft).Cloud cover is for at or below flight (operating) level.

GROUND RECCE VIS > 3000 m VIS 1000-3000 m VIS < 1000 m

PARADROP WIND < 13 KTS WIND 13-18 KTS WIND > 18 KTS

CIG < 1000 FT

LGT PRECIP MDT/HVY PRECIP

DA < 4000 FT DA 4000-6900 FT DA > 6900 FT

(DA = Density Altitude)

NBC OPERATIONS WIND < 10 KTS WIND > 30 KTS

WIND CALM

Wind From Enemy

Stable Atmosphere Neutral Stability Unstable Atmosphere

NO PRECIP LIGHT PRECIP MDT/HVY PRECIP

SMOKE WIND 5-10 KTS WIND < 5 KTS

WIND > 19 KTS

Wind From Enemy

TEMP > 120 F

MDT PRECIP HVY PRECIP

G-2

Appendix G

Joint Pub 3-59

Figure G-1. METOC Impacts to Selected Operations (cont'd)

METOC IMPACTS TO SELECTED OPERATIONS (cont’d)


(GREEN)


(AMBER)


(RED)

ARFOR OPERATIONS (cont’d)

PERSONNEL NO PRECIP LIGHT PRECIP MDT PRECIP

(temp — heat and/or windchill indices)

> 20F and < 85F 85-95F or -15 to 20F > 95F or < -15F

Lock On Before Launch CIG > 1900 FT CIG 400-1900 FT CIG < 400 FT

VIS > 7000 m VIS 500-7000 m VIS < 500 m

Lock On After Launch CIG > 1700 FT CIG 800-1700 FT CIG < 800 FT

VIS > 7000 m VIS 1700-7000 m VIS < 1700 m

COPPERHEAD CIG > 3000 FT CIG 1000-3000 FT CIG < 1000 FT

VIS > 2500 m VIS 1000-2500 m VIS < 1000 m

NO PRECIP MDT PRECIP HEAVY PRECIP

SEA PORTS WIND < 20 KTS WIND 20-35 KTS WIND > 35 KTS

AIR PORTS CIG > 1500 FT CIG 200-1500 FT CIG < 200 FT

VIS > 4800 m VIS 900-4800 m VIS < 900 m

AIR DEFENSE CIG > 5000 FT CIG 2500-5000 FT CIG < 2500 FT

VIS > 5000 m VIS < 5000 m

TEMP > 120F

ARTILLERY FIRES CIG > 1500 FT CIG 600-1500 FT CIG < 600 FT

VIS > 3000 m VIS 1000-3000 m VIS < 1000 m


TEMP < 20F

TEMP > 125F

NO TO LGT PRECIP MDT PRECIP HVY PRECIP

SIGINT WIND < 30 KTS WIND 30-45 KTS WIND > 45 KTS

TEMP 85-120F TEMP < 32 F

TEMP > 120F

TRAFFICABILITY NO PRECIP MDT PRECIP HVY PRECIP

AFFOR OPERATIONS

AIRLIFT CIG > 1000 FT CIG 500-1000 FT CIG < 500 FT


Light Freezing Precip Freezing Precip whichcloses runway

FLIGHT OPERATIONS CIG > 3500 FT CIG 1000-3500 FT CIG < 1000 FT

(CAS and/or DEEPATTACK)

VIS > 3200 m VIS 1600-3200 m VIS < 1600 m

(no specific airframe) WIND < 25 KTS WIND 25-35 KTS WIND > 35 KTS

LTG-MDT TURBC SVR TURBC

ELECTRO-OPTIC SUPPORT CIG CLR-SCT CIG BKN CIG OVC

(Absolute Humidity Limitations) < 14 g/m3 14-18 g/m3 > 18 g/m3

(Transmittance) > .4 0.2-0.4 < 0.2

(Moon Illumination) Moonrise/Moonset No Moon

(no specific system) HVY PRECIP

G-3

METOC Impacts to Selected Operations

Figure G-1. METOC Impacts to Selected Operations (cont'd)

METOC IMPACTS TO SELECTED OPERATIONS (cont’d)


(GREEN)


(AMBER)


(RED)

AFFOR OPERATIONS (cont’d)

PREDATOR CIG > 2000 FT CIG 800-2000 FT CIG < 800 FT

VIS > 4800 m VIS 3200-4800 m VIS < 3200 m

Crosswind < 10 KTS Crosswind 10-15 KTS Crosswind > 15 KTS

AIR REFUELING NO CLOUDS ATFLIGHT LEVEL

SCT-BKN CLOUDS ATFLIGHT LEVEL

OVERCAST CLOUDS ATFLIGHT LEVEL

NO Thunderstorms FEW Thunderstorms SCT Thunderstorms

NAVFOR OPERATIONS

AMPHIBIOUS WARFARE CIG > 5000 FT CIG 300-5000 FT CIG < 300 FT

VIS > 4800 m VIS 1000-4800 m VIS < 1000 m

LANDING CRAFT

(Combined Seas) > 5 FT

(Percent Illumination) > .0001 FT CANDLES

(Moderate Surf Index) < 8 8-10 > 10

(Breaker Heights) < 5 FT 5-12 FT > 12 FT

(Wake Period) > 7 SECONDS 6-7 SECONDS < 6 SECONDS

ANTI-SURFACE WARFARE

Over the Horizon — Targeting NO/LGT PRECIP MDT PRECIP HVY PRECIP

TEMP > 103F

(Seas) < 6 FT 6-8 FT > 8 FT

WIND > 60 KTS

COMBAT SERVICE SUPPORT VIS < 400 m

(Combined Seas) < 12 FT 12-19 FT > 19 FT

MINE WARFARE AVIATION CIG < 300 FT

VIS < 1000 m


EOD DIVERS CURRENT 1-2 KTS CURRENT > 2 KTS


HUNT WIND < 20 KTS WIND 20-30 KTS WIND > 30 KTS


SWEEP < 3 FT 3-6 FT > 6 FT

Compiled from a combination of manuals, including FM 34-81, FM 34-81-1, Service manuals, and variousequipment technical orders to present a general picture of METOC impacts to operations. This list is not all-inclusive, nor is it intended to restrict SMOs and/or JMOs to these limitations. SMOs and JMOs should feelfree to use this list as a baseline, expanding or changing it as needed to suit the forces and limitations oftheir various commands.

G-4

Appendix G

Joint Pub 3-59

Intentionally Blank

APPENDIX HNOTIONAL JOINT METOC FORECAST UNIT OPERATION

H-1

1. Overview

This appendix provides a notional JMFUorganization with associated tasks in supportof a joint force operation.

2. Considerations andAssumptions

a. JMFU planning assumes that a robustMETOC organization is required for anMTW. Less manning could be required for aSSC or military operations other than war(MOOTW).

b. Planners must consider C4I data baselocation and ease of communications withjoint METOC forces when determining JMFUorganization, size, and location.

c. Manning assumes long-term event —contingency manning (no days off) wouldrequire less.

d. Personnel are trained on JMFUfunctions and equipment prior to initiation ofJMFU.

3. Manning

a. In a JMFU production facility, manningconsists of in-place assets and otherService augmentation to fill-out expertiserequirements.

b. JMFU team composition is operation-dependent. The example here uses a mix ofpersonnel from different Service components.The key to a successful JMFU is to amass theproper functional expertise to complement theJTF mission, including the followingpersonnel.

• An officer in charge.

• A mix of meteorologists and forecasters(officer and enlisted mix) for initial rapidresponse to requests for focused area ofoperations support.

• Weather apprentices and/or aerographermate technicians.

4. METOC Related Duties

The JMFU is responsible for the followingduties.

a. Refine operational requirements.

b. Obtain METOC data.

c. Analyze METOC data.

d. Handle classified material, sensitivecompartmented information, and/or specialaccess requirements when appropriatelycleared.

e. Disseminate METOC information viaavailable communications resources toinclude C4I systems architecture.

f. Prepare and disseminate JOAF.

g. Prepare and disseminate special supportproducts as required.

h. Perform a meteorological watch for thejoint force area of interest.

i. Amend and/or update products asrequired.

j. Perform quality control.

H-2

Appendix H

Joint Pub 3-59

k. Perform effectiveness evaluation.

l. Provide support to JFC components.

m. Provide support to SMO, JMO, and/orJFC staff as required.

n. Prepare report inputs as required.

o. Serve as net control station (NCS) forMETOC HF operations, if required.

p. If required, perform system managerfunctions on tactical weather systems andoperator maintenance on equipment.

q. Develop logistic requirements for JMFUoperations.

r. Implement, manage, and monitor thetheater METOC server.

APPENDIX JCOMMUNICATIONS

J-1

1. Overview

This appendix provides the SMO and JMOwith an overview of the communicationconcepts and capabilities of the Services tosupport the METOC operations identified inChapter IV, “Joint Force METOCOperations.” To the maximum extentpossible, conduct METOC operations usingcommon C4I systems.

2. Requirements

The rapidly changing nature of the air,space, and ocean environments makesMETOC data extremely perishable.Therefore, effective METOC support to jointoperations is dependent upon timely, reliablecommunications that allow for the rapidtransfer and refresh rate of METOC data toall deployed forces. In simplest terms, allMETOC units must be able to share METOCinformation with each other to ensureconsistency and accuracy of information atall stages of the operation. It is vital that allforces involved be able to communicate witheach other in both clear and secure modes.Communication of METOC informationshould be designed to fulfill the datacol lect ion, s torage, ret r ieval , anddissemination efforts of the METOC forcesat all levels. In a broad sense, the conceptincludes the following.

a. The flow of information between allcomponent-level METOC forces within theAOR.

b. The flow of information between allMETOC forces within the AOR. Forexample, the METOC unit supporting theArmy component should be able to passforecasts and observations to the Navycomponent and the JMFU. It should be noted

that the JMFU is not the primary conduit ofthe METOC data flow between existingMETOC centers and tactical units, but ratherit integrates METOC information.

c. The flow of METOC information fromtactical METOC forces back to the JMFU andout of the AOR.

3. Considerations

Specific responsibilities concerningcommunications are contained in CJCSI3810.01A, “Meteorological and OceanographicOperations.” However, the following itemsshould be considered to ensure the flow ofMETOC information throughout the AOR.

a. Communications links between theMFC, JMFU, JMO, SMO, components, andtactical METOC forces.

b. Required COMSEC material for usewithin the AOR.

c. Terminal equipment required at theJMFU (e.g., METMF, Tactical ForecastSystem (TFS), server, HF transceivers,Tactical Very Small Apeture Terminal,NITES).

d. Requirements for satellite broadcast andcomponent HF support.

e. Direct access to JWICS, SIPRNET(with access to GCCS and INTELINK-S), andNIPRNET.

4. Notional CommunicationsArchitecture

a. To turn the communicationsrequirements into a working system, eachparticipating METOC element must

J-2

Appendix J

Joint Pub 3-59

understand the generic flow of METOCinformation throughout an AOR. This flowis graphically depicted in Figure J-1. Byunderstanding the generic architecture and

how each of the component METOC forcespasses information, the SMO, JMO, and J-6can better tie the pieces together into a whole.

Figure J-1. Notional Meteorological and Oceanographic Communications

NOTIONAL METEOROLOGICAL ANDOCEANOGRAPHICCOMMUNICATIONS

SOCRATES /SOFTACS

USSOCOMUSSOCOM

JIC

ARSOC AFSOC

MTS / SOF-IRIS MTS / SOF-IRIS

SOCRATES / METOCVIRTUAL

SERVER / GATEWAY

FMCHBROADCAST

GBS

TDC STACCS

AFFORCWT

ARFORCWT MARFOR NAVFOR

OA DIV

WINGCWT

CORPSCWT

SQDNMETOC

SQDNMETOC

SQDNMETOC

SHIPOA DIV

SQDNCWT

DIVCWT

SHIPMETBRIGADE

CWT

ASHOREMET

NOTE: DOD communications is currently anybackbone and/or reachback system, movingtoward GCCS and/or SIPRNET

JOINTHF NET

HF

HFRB INDIGENOUS

NAVFAXHF

THEATER COMPONENT/REGIONAL

METOC CENTERSDOD COMMUNICATIONS

MFC

JMFU

THEATER SOCs

MTS / SOF-IRIS

NAVFOR

MTS / SOF-IRIS

MTS / SOF-IRIS MTS / SOF-IRISMTS / SOF-IRIS

AFFORAFSOCARFORARSOC\CWTDIVDODFMCHGBSGCCSHFHFRBJICJMFUMARFORMETMETOC

Air Force forcesAir Force special operations componentArmy forcesArmy special operations componentAir Force combat weather teamdivisionDepartment of Defensefleet multichannelGlobal Broadcast SystemGlobal Command and Control Systemhigh frequencyhigh frequency regional broadcastJoint Intelligence Centerjoint METOC forecast unitMarine Corps forcesmobile environmental teammeteorological and oceanographic

MFCMTS/SOF-IRISNAVFAXNAVFOROA

SIPRNETSOCRATES

SOCsSOFTACS

SQDNSTACCS

TDCUSSOCOM

METOC Forecast Center

multifunction systemNavy facsimileNavy forcesOperations Aerology Shipboard METOCDivisionSECRET Internet Protocol Router NetworkSpecial Operations Command, Research,Analysis, and Threat Evaluation Systemspecial operations commandsSpecial Operations Forces Tactical Air ControlSystemsquadronStandard Theater Army Command and ControlSystemtheater deployable communicationsUnited States Special Operations Command

J-3

Communications

b. The backbone of the METOCcommunications structure which allowsconnectivity into and out of the AOR is theDISN. The DISN allows worldwide andtheater data to flow into the AOR from theMFC. DISN connectivity also allows forMETOC information collected in the AORto be available for use by the MFC. DISNcan be used for the flow of classified andunclassified METOC data.

c. Within the AOR, METOC informationmust be exchanged using Servicecommunications links and joint C4I systems.

5. JMFU Communications andEquipment

The JMFU focuses on the integration ofMETOC information from joint forcecomponents, MFC, and tactical sources. Assuch, meticulous communications planning iscritical to success. The communicationsrequired will change significantly dependingon the nature and size of the joint operation.The JMFU will primarily rely on SIPRNETand/or NIPRNET, satellite broadcast, and HFbroadcast (from HFRB or Navy facsimile[NAVFAX]). The JMFU communicationrequirements will depend on where they arelocated. Specific type of connectivity to theJMFU and MFC depends on what terminalequipment is available and can be supportedby the theater communications capabilities.

a. If the JMFU has robust DISNconnectivity and access to a TFS and/orautomated weather distribution system(AWDS), TESS and/or NITES, METOCIntegrated Data Display System-Tactical(MIDDS-T), IMETS, or METMF, thenMETOC data will primarily be received viathese self-contained systems.

b. If the JMFU does not have sufficientDISN connectivity to effectively use TFS and/or AWDS, IMETS, TESS and/or NITES,MIDDS-T, or METMF, it will rely on the

“early-in” techniques described later in thisappendix until DISN connectivity is achievedwith the MFC.

c. METOC HF Net. When other, morereliable means are not available, one methodof communication among METOC forces isvia an HF net. HF should be considered as abackup only and not planned for use as theprimary means of communications. If theJMO establishes an HF net, the JMFU or oneof the Service components may be the NCS.The NCS must work with the J-6 to gainfrequency clearance by the host nation,coalition forces, and joint Services beforeoperating any transmitter. The net is operatedusing a joint key list which is controlled bythe Intertheater COMSEC Package (ICP)manager. HF-equipped units should establishrequirements for COMSEC material throughlocal COMSEC custodians. The NCS willprovide field units with both AN data andfacsimile products over the METOC net.Field units will attempt to transmit data to theNCS directly. If unable to contact the NCS,field units must try to contact other units onthe net to ensure that data is passed. The NCSwill collect all observations, forecasts, andupper-air data from field units and transmitthem to other network hubs and/or stations,JMFU (if not designated the NCS), and theMFC. The JMFU will input METOC datainto the AWN. The following topics arestandard for NCS operations, and should beconsidered for inclusion in an HF section inthe LOI.

• Frequencies and frequency clock (bestuse of available frequencies duringvarious times of the day)

• Transmission schedule

• HF net KQ identifiers, nodes, and callsigns

d. HFRB System. The HFRB system is areceive only system designed to provide

J-4

Appendix J

Joint Pub 3-59

dedicated METOC teletype and facsimile datato deployed units. Air Force HFRBs areoperational at Elkhorn, Nebraska andHomestead Air Force Base (AFB), Florida.NAVFAX broadcasts are available in AtlanticCommand and Pacific Command on “RequestOnly” basis from the appropriate regionalcenters listed in Appendix M, “METOCForecast Center.”

e. JMFU Afloat. Ships most capable ofproviding the manpower, equipment andcommunications infrastructure to support anafloat JMFU include aircraft carriers,amphibious command ships, or amphibiousassault ships that are equipped with TESS and/or NITES and GCCS. The SMQ-11 satellitereceiver acquires and processes data frompolar orbiting and geostationary satellites intoTESS and/or NITES. TESS and/or NITESare integrated into shipboard C2 systems toprovide access to established DOD C4I andService networks. A JMFU has access toestabl ished common-user satel l i tecommunications networks that can be usedto disseminate METOC products tocomponent commanders through Service and/or joint networks. The ship can transmit andreceive classified Automatic Digital Network(AUTODIN) traffic, access commercial voicenetworks and/or the Defense SwitchedNetwork (DSN), and can operate in a secureenvironment using secure telephone unit-III(STU-III).

6. Service-Unique Systems

Within each component, capabilities,procedures, and equipment vary. Thefollowing is a description of each Service’sMETOC communications structure so that theSMO and JMO can better integrate allresources within the AOR.

a. Navy. Naval METOC ProductionCente rs (NAVOCEANO andFLENUMMETOCCEN) are the hubs for thedissemination of global and regional METOC

data and/or models to regional METOCcenters as well as to METOC forcesworldwide. The regional centers are alignedwith the CINC’s Navy componentcommanders and manage the disseminationof global and regional data as well as locallyproduced METOC products within theirAOR. Products are made available to theaterforces via the DISN (NIPRNET, SIPRNET,and JWICS). Afloat customers accessMETOC products via SIPRNET and TESSand/or NITES (aircraft carriers, large deckamphibious, and C2 ships only), satellite fleetmulti-channel broadcast, AUTODIN,Streamlined Automated Logistics TerminalSystem, and on-demand HF facsimilebroadcasts.

b. Army

• In the AOR, the Army receives productsfrom the non-theater MFC productionfacilities at a single theater entry point, ifone exists, or at the Army tactical supportcommunications system collocated withthe highest Army echelon deployed (or,if a direct satellite broadcast weathercommunications capability exist, directlyto subordinate USAF CWTs throughUSAF provided and maintained standardground transceivers). CWTs at either thetheater, ARFOR, or Corps level have theresponsibility to coordinate thetransmission of data to lower echelonsthrough standard Army communications,although the path of the data and thesystems used will change depending onthe size and nature of the contingency.During an MTW, the ARFOR CWT actsas the coordinator for transmission ofMETOC data from outside the AOR tothe lower echelon CWTs. DuringMOOTW missions, weather support maybe organized into a single, small CWTdesigned to support a brigade or battaliontask force. A task force CWT may needan alternate source of communicationsuntil the normal theater, ARFOR, or

J-5

Communications

Corps communication structure isestablished in the AOR.

• In an MTW, a full contingent of CWTsand communications equipment willdeploy with the ARFOR, Corps,Divisions, ACR, and Special Forcesgroups and/or Ranger Regiment. In suchan MTW, the ARFOR CWT, equippedwith QRCT III or IMETS, will tailor andretransmit MFC-prepared products to thelower echelons using the ABCS. TheIMETS will be the CWT’s main weathersystem connected to the ABCS. Inaddition, QRCT III HF Radio networksprovide an alternate, limited mode of ANcommunications among CWTs and as areceiver for HFRB. QRCT III will be ableto communicate with IMETS when a mixof systems are deployed. In an MTWwithout IMETS deployed, transmissionof graphics over facsimile through MSEequipment can supplement QRCT III.Alden 9315 TRT-R can receive faxweather graphics broadcasts when withintransmission range. In MOOTW andjoint force support, split-base weathersupport from the ARFOR CWT,operating from Army intelligencefacilities and using the Army GlobalCommand and Control System (GCCS-A), will provide MFC products,forecasts, and observations to the G-2until a CWT arrives. With the joint forcein place, it will use a combination of splitbase support, local indigenousinformation, and data received by tacticalequipment deployed with the CWT. Withtransportable computers and modems, theCWT can use dial-in access to the MFC.In a MOOTW which transitions to anMTW, the capabilities of a full ARFORCWT with IMETS will be built asquickly as the headquarters, andheadquarters companies of the Corps andDivisions arrive in the theater. The flowof METOC data would also transition

from split base, GCCS-A transmissionto reception of MFC products at theARFOR IMETS and transmission to thelower echelon CWTs as described earlierfor an MTW.

c. Air Force. Air Force METOCcommunications are currently centeredaround the AWN as the primary means ofreceiving and disseminating AN weather dataand graphical weather data but are rapidlymigrating to high speed informationtransmission services such as global broadcastservice and common user networks such asDISN. Systems such as the web-basedAFWIN, SAFWIN, and/or JAFWIN provideaccess to METOC information over state-of-the-art secure and unsecure communications.HFRB broadcasts and HF and/or QRCT IIInet operations when available, are a viablebackup. Outside the Korean theater, QRCTIII operations are limited to Army operations.AN data and graphics products are madeavailable in theater primarily via data sourcesthat rely on the DISN such as theMeteorological Information StandardTerminal and AFWIN/SAFWIN.

d. Special Operations Forces. Generationand dissemination of METOC data sets toSOF units requires timely access to data froma number of varied sources both inside andoutside the SOF community. SOF METOCelements use a laptop computer loaded withstandard application software that providesmapping, word processing, image analysis,electronic mail, spreadsheet, documentstorage, search, and retrieval, computer aideddesign, and backup capabilities. This laptopcan access backbone communications, otherServices’ networks, and dial-in systems. Italso interfaces with antennas and receivers forreceipt of geostationary and unencryptedpolar-orbiting meteorological satellites. ThisMETOC ADP support is compatible withSOF deployable intelligence ADPcapabilities.

J-6

Appendix J

Joint Pub 3-59

e. Marine Corps. METMFs in the MWSSare equipped to receive the fleet multichannelbroadcast. The fleet multichannel broadcastvia satellite is the primary source for METOCinformation. The METMFs are also equippedto receive HFRB as well as indigenous HFbroadcasts in the AOR. Web-basedNIPRNET/SIPRNET and dial-in systems,such as NODDS and AFWIN, provideadditional METOC data collectioncapabilities. For transmission capabilities, theMETMFs rely on HF and MAGTF C4I localarea network and/or wide-area network todisseminate METOC information to organicunits. The MEF SWO and MSTs are equippedwith the IMOSS or its replacement, a portableMETOC system, Navy’s NITES IV, asdescribed in Appendix K, “DeployableMETOC Equipment.” The portable systemwill have an HF receive capability and be ableto access/disseminate via conventional and/or tactical communication paths, the MEFSWO can also collect METOC informationusing G-2 resources, systems, and networks.

7. Early-In and InitialCommunications Concept

a. Early-in communications equipmentmust be capable of allowing the METOCforces to support the warfighter untilsustaining backbone communications areavailable. Early-in communications includeHF broadcasts, satellite and telephone lines.AMC tanker airlift control elements(TALCEs) have an indigenous satellitecommunications (SATCOM) capability.AMC TALCEs forward their observations andforecasts via SATCOM to the tanker airliftcontrol center (TACC) for injection into theAWN. The TACC can also forward limitedAN theater weather data packages to deployedTALCEs. Air Force HFRB and Navy on-demand NAVFAX take AN and graphicweather information from dedicated circuitsand transmit it to tactical HF receivers. HFRBoperates in the unclassified mode. These fixedsite broadcast stations are pre-existing at the

following locations and can be used as anearly-in capability.

• Elkhorn, Nebraska; operated by AirCombat Command.

• Barrigada, Guam; operated by the USN.

• Isabell, Puerto Rico; operated by theUSN.

• On-demand NAVFAX in the Pacific:Diego Garcia; Guam; Japan; Hawaii;and Stockton, California. Alternatebroadcast sites are located at Australia’sNorthwest Cape (Naval CommunicationStation Harold E. Holt) and San Diego,California. The data for these broadcastsoriginate from NAVPACMETOCCEN.

• On-demand NAVFAX in the Atlantic:Norfolk, Virginia; Cutler, Maine;Jacksonville, Florida; Key West, Florida;Isabella, Puerto Rico; Keflavik, Iceland;and Guantanamo Bay, Cuba. The datafor these broadcasts originate fromNAVLANTMETOCCEN.

• On-demand NAVFAX in theMediterranean area: Sigonella, Sicily.The data for these products originatefrom NAVEURMETOCCEN.

b. METOC dial-in systems can also beused for early-in operations or as backupduring NIPRNET and/or SIPRNET outages.Various Navy and Air Force METOCfacilities have systems which users can accessto acquire METOC information for their usein planning, analysis, and forecasting. Thesesystems provide a capability to obtain timelyaccess to a wide range of METOC productsfrom practically anywhere in the world. TheJMO and component METOC officers shouldconsider the requirements for and viability ofusing these systems to augment the METOCsupport effort at the JMFU and componentlevels, particularly before backbone

J-7

Communications

communications are established. Users accessthese systems using a phone dial-in from acomputer over established telephone lines orvia SATCOM access (e.g., InternationalMaritime Satellite B [INMARSAT-B]) tosatellite based telephone communicationscircuits. These communications paths limit theuse of these dial-in systems since theavailability of telephones or SATCOM maybe highly dependent upon the remoteness ofthe battlefield or whether a unit has SATCOMequipment. Appendix L, “METOC Dial-InBulletin Board and Web-Based Systems,”provides more detail on both classified andunclassified bulletin board systems andinformation on their capabilities and use.

c. NIPRNET and SIPRNET systems arealso key to an early-in communicationsconcept. These connections are generallyavailable in limited quantity during the initialdays of a deployment, but can become morerobust after 1 to 2 weeks in the AOR. This isan effective means to provide initial supportfrom an established METOC facility to alimited METOC force operating in an austerecommunications environment.

8. Security Considerations

The JFC is responsible for denial ofMETOC information to an enemy. Whenrequired, encryption of METOC data shouldbe accomplished with the appropriate subsetof keying material provided by the localCOMSEC custodian. Since the JMFU andMFC require these observations for theircomputer models, the encryption ofobservations must be standardized to protect

location. The joint keying material providesthat standardization. HF equipment shouldoperate with KG-84 model encryption gearso that all HF equipment in use can usecompatible COMSEC tapes. The JMFU orService component will operate the theaterHF net using joint keying material providedby the ICP manager at MacDill AFB, Florida.Joint keying material may be used to encryptinformation (e.g., an observation’s location)before passing it over nonsecure lines.Likewise, theater HFRB broadcasts will usejoint keys when encrypting. Common use ofthe joint keying material will provide astandardized interoperable method ofencoding originating locations for METOCproducts.

9. KQ Identifiers

Units deployed for an operation will requirea tactical station identifier (KQ identifier).AFWA is the central manager for KQidentifiers for Air Force and Army. Thesupported CINC’s SMO has the option forassigning KQ identifiers for all weather teamsin the theater of operations. In the absence ofpublished guidance by the theater SMO,deploying weather teams will obtain their KQidentifiers from AFWA. Navy and MarineCorps KQ identifiers are obtained fromFLENUMMETOCCEN Detachment Tinker.Normally, units should obtain these on theirown prior to deployment, but can also obtainthem after arrival in theater. The JMO mustensure that there is only one active KQidentifier reporting for each location (althoughthere may be more than one unit at a particularlocation with KQ identifiers).

J-8

Appendix J

Joint Pub 3-59

Intentionally Blank

APPENDIX KDEPLOYABLE METOC EQUIPMENT

K-1

1. Overview

This appendix provides an overview of theMETOC tactical equipment that may beavailable to components within a joint force.Note: This list is not intended to suggest thatall individual Service METOC unitssupporting their local operation would haveand maintain this equipment. For a detailedlist and complete description of these andother mobile systems available, refer to theFederal Directory of Mobile MeteorologicalEquipment and Capabilities published by theOffice of the Federal Coordinator forMeteorological Services and SupportingResearch.

2. Air Force

a. AN/TMQ-34, Tactical MeteorologicalObserving Set. Provides measurement oftemperature and dew point, wind speed anddirection, precipitation, and barometricpressure in a tactical environment.

b. Manual Observing System. Containsinstruments to allow an observer to makeobservations of temperature, dew point, windspeed and direction, precipitation, ceiling,visibility, and atmospheric pressure.

c. AN/GMQ-33, Cloud Height Set. Self-contained, operator maintained, portable unitthat determines and displays the base heightof cloud layers directly overhead by the useof a laser.

d. AN/TMQ-36, Tactical WindMeasurement System. Operator-maintained,self-contained, portable unit that providesmeasurement of wind speed and direction.

e. AN/GRQ-27, HF FlyawayCommunications System/QRCT III.

Standard secure tactical communicationsusing Joint Interoperability of Tactical C2System message text formats. All versionsinclude an Alden 9315 TRT HF receiver andrecorder.

f. Wraase Weather Satellite ReceiverSystem. The Wraase system is a commercial,off-the-shelf, portable satellite receiver thatreceives imagery from geostationary and civilpolar orbiting satellites. The Wraase systemcannot receive DMSP imagery.

g. Alden Weather Facsimile (WEFAX)3T Receiving Set. This is a commercial, off-the-shelf system for receiving WEFAXpictures from geostationary operationalenvironmental satellite, METSAT, andGeostationary Meteorological Satellite.

Wind direction and speed may be measured byusing the AN/TMQ-34, -36, or manual observingsystems.

K-2

Appendix K

Joint Pub 3-59

h. Alden Compact Facsimile(9315TRT). Commercial, off-the-shelffacsimile receiver and recorder with a built-in HF synthesized receiver. It includesradioteleprinter reception capability at 67 and100 words per minute.

i. ML-102G, Barometer. Portable, highlyaccurate aneroid barometer which is designedfor use in fixed or tactical locations.

j. AN/TPS-68, Tactical Weather Radar.C-band weather radar system housed insideS-280 shelter housing (8ft x 8ft x 12ft).

k. Weather Facsimile and Teletype HFRecording System. Receiver and recorderthat copies radio facsimile weather charts andradio teleprinter text broadcasts.

l. AN/UMQ-12, MARWIN TacticalUpper-Air Wind Measuring Set. Automatictracking, operator-maintained, portable unitthat provides upper-air wind direction andspeed, pressure, temperature, and relativehumidity to an altitude of 30 kilometers.

m. AN/TMQ-43, Small TacticalTerminal (STT), Meteorological SatelliteReceiving System. The STT is a modularsatellite reception terminal which provides

receive only capability for both low and highresolution weather satellites. It comes in fiveSTT versions: basic, enhanced, joint taskforce satellite terminal, L-STT, andworkstation.

n. Tactical Forecast System. TFS is asmall, lightweight, modular system designedfor production of weather forecastingproducts. It is the standard system fordeployed, garrison, and weather centeroperations. TFS software will consolidate thefollowing functions onto Combat Air Forcesworkstation; AWDS capability to analyze dataand prepare forecast products, EO-TDAs, AirForce Combat Climatology Center (AFCCC)applications, display Air Force WeatherAgency Dial-In Subsystem (AFDIS),NODDS, and AFWIN and/or SAFWIN data.TFS will also interface with STT and interfacewith STT and multiple external systems viaC4I networks (e.g., NIPRNET, SIPRNET).

o. International Marine SatelliteTerminal. Since the use of INMARSAT isgoverned by international agreements, thissystem may not necessarily be available forall non-routine operations. There are a limitednumber of INMARSAT terminals fielded toArmy and Air Force weather units.INMARSAT terminals will be used for

The Wraase system cannot receive DMSP imagery.

K-3

Deployable METOC Equipment

deployed telephone communications, toinclude voice and data.

p. Electronic Staff Weather Officer Kit(ESK). ESK is a personal computer, in eithera laptop or desktop configuration, with officeautomation, Air Force and Navy METOCdial-in, and network software. ESK’s primaryrole is to provide deployed weather teams withaccess to basic weather products (e.g.,AFWIN and SAFWIN products, satelliteimagery, forecast charts) when TFS is notavailable, and to supplement TFS operations.

3. Army

In addition to the above Air Force supportequipment, Army weather support units usethe following systems.

a. AN/TMQ-40, IMETS. IMETSreceives, processes and distributes METOCdata and/or information over Army tacticalcommand and control systems. It hascommunications compatibility with AllSource Analysis System, Digital TerrainSupport System, and HF QRCT III systems,and receives weather satellite information. Itis highly mobile multi-wheeled vehiclesmounted, with a standard integrated commandpost shelter, and is C-130, rail, and seatransportable.

b. AN/TMO-41, MeteorologicalMeasuring System. Automatic tracking,deployable system that provides upper-airwind direction and speed, pressure,temperature, and relative humidity to analtitude of 30 kilometers.

4. Navy

a. Tactical Environmental SupportSystem and/or Navy Integrated TacticalEnvironmental System. TESS and/orNITES are modular, interactive, computer-based systems which collect, processes,

analyze, display, and disseminate METOCdata and products. Sources of data includeFLENUMMETOCCEN, remotely sensedsatellite data and imagery, AN data from thefleet broadcast, locally-observed data, and theSIPRNET.

b. Navy Integrated TacticalEnvironmental System. Government and/or commercial, off-the-shelf modular,interactive METOC analysis and forecastingsystem for the simultaneous reception,processing, display, and dissemination ofMETOC data which will become operationalin FY99. NITES will be compliant with thedefense information infrastructure (DII)common operating environment (COE) whereapplicable. Modular, DII COE-compliantsegments will support Navy and Marine Corpsconfigurations for regional METOC centers,ships, GCCS-M workstations in non-METOCspaces, METOC facilities and detachmentswith or without a tactical support center, MET,Marine Corps Air Stations, MSTs, and theAllied Environmental Support System.Primary network connectivity will beprovided by the Joint MaritimeCommunications Systems, NIPRNET, andSIPRNET. The fielded NITES versions areas follows.

• NITES I. Local data fusion center andprincipal METOC analysis andforecasting system, consisting of bothclassified and unclassified workstations.

• NITES II. Classified METOC softwaresegment for the GCCS-M and/or GCCS.

• NITES III. Unclassified forecast,briefing, and display system tailored toMETOC shore activities supportingaviation operations.

• NITES IV. Portable system tailored tomobile METOC support to C4Isurveillance and reconnaissance.

K-4

Appendix K

Joint Pub 3-59

c. METOC Integrated Data DisplaySystem-Tactical. Government and/orcommercial, off-the-shelf client-server basedMETOC analysis and forecasting system forthe simultaneous reception, processing,display and dissemination of METOC data.MIDDS-T currently receives satellite imagery,digital facsimile charts, analog facsimile, AN,NODDS and/or Optimum Path AircraftRouting System (OPARS), AFDIS, satellitemessage, Graphics Fleet Mission ProgramLibrary, and radar data. MIDDS-T providesbriefing support for Navy and/or MarineCorps aviation. Each MIDDS-T is a stand-alone system where each may be set updifferently to meet current operationalrequirements. MIDDS-T capabilities arebeing incorporated into NITES.

d. Alden Marinefax TR-IV Recorder.Commercial, off-the-shelf facsimiledesigned to receive and reproduce radiofacsimile weather charts from HF radiotransmissions.

e. Interim Mobile OceanographySupport System. IMOSS is a three-parthardware and software package that providescomputational, communications, and satellitemodules. The computational module is apersonal computer (PC) based system whichuses the Geophysics Fleet Mission ProgramLibrary to generate meteorological,electromagnetic, oceanographic, and acousticforecasts. The communication module willreceive AN data via the HF receiver or theship’s SATCOM network. The communicationmodule is connected to a HF receiver. Thesatellite module will receive, store, andprovide the computational module withautomatic picture transmission data fromNOAA and/or TIROS-N and Russianmeteorological polar-orbiting satellites.

f. AN/UMQ-12, Mini Rawin System.Upper-air data collection system consistingof receiver and balloon launched rawinsondes.Data collected includes pressure, temperature,

relative humidity, and wind as a function ofheight above the surface of the earth.Networked to the TESS/NC.

g. AN/SMQ-11, Meteorological DataReceiver-Recorder Set. The SMQ-11system is capable of receiving, storing, andmanipulating high resolution polar orbitingsatellite data and geostationary satelliteimagery.

h. Naval Satellite Display Station-Enhanced (NSDS-E). NSDS-E is a satellitereceiving system. It receives bothgeostationary and polar orbiting imagery fromMETOC satellites, stores the received data,and provides the means to manipulate,analyze, and enhance imagery, as well asfurther distribute the data to other METOCsystems such as NITES. NSDS-E is capableof outputting both raw data and processed,enhanced imagery.

i. Marta Geostationary WeatherSatellite Direct-Readout Ground Station.Low cost commercial, off-the-shelf receiverthat acquires, processes, and displays high-resolution digital imagery directly fromgeostationary satellites. Graphics displayapplication is incorporated into the MIDDS-Tsystem. Data fusion supports the ability tooverlay any infrared (IR), water vapor, orvisible image combination.

5. Marine Corps, METMF

Each MWSS is equipped with a METMFcomplex normally deployed to a forwardoperating base in direct support of that airfield.A METMF complex consists of the following.

a. AN/TMQ-45, Primary METMF. TheAN/TMQ-45 is configured with extensivecommunications equipment, includingSIPRNET access capability, to allowreception and transmission of encrypted andunencrypted METOC data in AN, facsimile,and voice formats.

K-5

Deployable METOC Equipment

b. AN/TMQ-46, Secondary METMF.The AN/TMQ-46 is configured to provide aclean area for maintenance of sensitiveelectronic equipment.

c. AN/TMQ-47, Weather Radar (AN/FPS-106). The AN/TMQ-47 is configuredwith an AN/FPS-106 weather radar which hasthe capability to detect, analyze, and trackmeteorological phenomena within a 200nautical mile radius and to an altitude of60,000 feet. Note: Only fixed-wing MWSSspossess the AN/TMQ-47.

d. AN/TMQ-35, (MARK-IV). The AN/TMQ-35 provides for the capture,manipulation, and detailed analysis of imageryoriginating from DMSP and NOAA polar-orbiting satellites.

e. METMF Replacement (METMF[R]). The METMF (R) is a fully integratedsystem capable of automatic data acquisitionfrom communications channels providingMETOC data, meteorological satellitedownlinks, and local and remotemeteorological sensors. The METMF (R)will be capable of disseminating METOCdata and products v ia communicationlinks, such as the MAGTF C4I local areanetwork and SIPRNET, and an indigenousvideo briefing system. The METMF (R)consists of ten subsystems.

• Processing Subsystem (PCS). The PCSconsists of NITES I and II as describedin para 4b of this Appendix.

• Communications Subsystem (CSS). TheCSS is capable of transmitting and receivingsecure and non-secure data frommeteorological channels of the fleet multi-channel broadcast, USAF HFRB,worldwide meteorological broadcastfrequencies, satellite communications, andsecure/non-secure internet protocol router.

• Meteorological Satellite Subsystem(MSS). The MSS receives high and lowresolution meteorological imagery frompolar/geostationary orbiting satellites.

• Rawinsonde Subsystem (RWS). TheRWS consists of the AN/UMQ-12, MiniRawin System, described in para 4f ofthis Appendix.

• Local Sensor Subsystem (LSS). TheLSS measures and reports meteorologicalobservations, including surface winddirection and speed, surface air and dewpoint temperature, liquid precipitation,cloud height, visibility, atmosphericpressure, and lightning detection.

• Remote Sensors Subsystem (RSS).The RSS consists of two remote sensorsets capable of reporting meteorologicalinformation up to 200 nautical miles fromthe METMF (R). The RSS measures andreports surface wind direction and speed,surface air and dew point temperature,liquid precipitation amounts, andatmospheric pressure.

• Video Subsystem (VDS). The VDS iscapable of originating and displayingvideo images to on location external ofthe METMF (R).

• Meteorological Radar Subsystem(MRS). The MRS is a Doppler systemcapable of providing real-time,surveillance, and advanced warning ofpotentially hazardous atmosphericconditions in the vicinity of the METMF(R).

• Portable Meteorological Sybsystem(PMS). The PMS is the Navy's IMOSSuntil replaced by NITES IV, previouslydescribed in para 4b of this appendix.There are two PMSs per METMF (R)

K-6

Appendix K

Joint Pub 3-59

— one is for use by the MSTs and onefor use by the MWSS.

• Shelter Subsystem (SSS). The SSSconsists of one standard InternationalOrganization for Standards (8'x8'x20')shelter, environmental control units, andpower distribution systems.

6. Special Operations Forces

In addition to service standard systems,SOF METOC elements may be equipped withunique equipment, such as SOF METOCsystems.

APPENDIX LMETOC DIAL-IN BULLETIN BOARD AND WEB-BASED

SYSTEMS

L-1

1. Overview

This appendix provides an overview of thevarious “dial-in” and “web-based” systemsthat the Air Force and Navy have availablefor a joint force to obtain METOC data.

2. Dial-In System Descriptions

a. Naval Oceanographic DataDistribution System. An unclassified systemallowing access to FLENUMMETOCCENenvironmental products. The user defines theproducts desired for an area and initiates anautomatic process of acquiring the data, usinga commercial communications protocol. Theprogram extracts data for each field and/orproduct from a global or regional data basedepending upon the area selected andtransmits in a compacted, communications-efficient format. Once the raw data is receivedby the user’s NODDS system, the softwarecontours, streamlines, and shadesautomatically until all products are in aready-to-display format. The systemdownloads data via modem to a PC or laptopcomputer. Products include contoured,gridded data fields of meteorological andoceanographic parameters (e.g., surfaceweather analysis and progs, standard levelsupper-air height, temperature, and/orthickness, analysis and progs, sea surfacetemperature), 3-D gridded data fields (GDFs),upper-air soundings, surface reports, DMSPsatellite imagery, general acoustic conditionscharts, and high wind and seas warnings.Product runs refresh at 12-hour intervals.Users connect to NODDS via DISN, DSN,Public Switched Telephone Network (PSTN),STU-III, INMARSAT, or commercialtelephone (including cellular). There is cost

incurred by the use of commercial telephonesystems to acquire products.

b. 55th SWXS Dial-In System. Allowscustomers to access space environmentalbulletins. Types of products include HFpropagation and atmospheric and interferenceconditions. For system access dial DSN560-6257. System is menu driven (whenaccessing for the first time, users will need torequest an account, password, and useridentification).

c. Autopolling and/or Voice Facsimile.Distributes unclassified METOC informationvia a dial-in facsimile system. The system isentirely automated, with the user selectingMETOC graphics from a variety of productgroups and initiating the transmit process. Thesystem will fax the selected products to theuser’s telefax machine or PC. Users canaccess this system using any nonsecure telefaxmachine or PC-based telefax system. Productsinclude surface and upper-air analysis andprogs, high winds and/or high seas graphics,sea height analysis, and ocean frontal chartsas well as analysis and forecasts of sea ice.Users can select prepackaged groups ofproducts from a menu-driven listing. Productsare available on-call 24 hours a day at the costof dialing into the system.

d. Personal Computer ImageCommunications System. Software packagethat downloads satellite images reflectingprimarily oceanic sea surface temperaturefeatures by telephone-modem for display ona computer. Satellite images are binary filesand software is used to enhance the sea surfacetemperature images. Software is similar toNODDS and can be collocated with NODDS.

L-2

Appendix L

Joint Pub 3-59

3. Web-Based SystemDescription

a. Air Force Weather InformationNetwork, Secure Air Force WeatherInformation Network, and JWICS AirForce Weather Information Network.AFWIN provides the NIPRNET-connecteduser with the capability to select, retrieve, anddisplay AFWA products using commercial,off-the-shelf web browser software. SAFWINprovides the SIPRNET-connected user withthe capability to select, retrieve, and displayAFWA products web browser software.SAFWIN was designed to mirror AFWA’sAFWIN product suite and provide additionalclassified products via the SIPRNET.SAFWIN will mirror the AFWIN growth tothe classified user and continue to exploittechnology to enhance classified support.JAFWIN is similar to SAFWIN but supportsthe Intelligence Community.

b. AFCCC Homepages and FileTransfer Protocol (FTP) Sites. This Internetstyle homepage allows the user to submitrequests for climatology support, to viewselected climatology products, and todownload selected software. The NIPRNEThomepage is accessible via the Internet. TheSIPRNET homepage basically mirrors theNIPRNET homepage. AFCCC alsomaintains an unclassified FTP site for thosewho do not have NIPRNET and/or SIPRNETaccess but do have a modem and telephoneaccess. The product suite contains items suchas 30, 60, and/or 90 day visualizations,operational climatic data summaries, airfieldflying weather statistics, and PC software suchas SKEW-T PRO and NITELIGHT. It alsocontains hot links to other NIPRNET and/orSIPRNET sites.

c. Naval METOC Operational SupportWeb (NMOSW). All Naval METOCproduction centers, regional centers, andfacilities have NIPRNET and SIPRNEThomepages. All aviation detachments haveNIPRNET homepages. Additionally, theproduction centers and regional centers haveJWICS homepages. The NMOSW links allof the Naval METOC homepages of a givenclassification level and provides a commonvirtual Naval METOC data base with globalreal-time access to all supported NavalMETOC products. Through the NMOSW,warfighter and selected customer support(data, imagery, products, chat, video) iscustomized as required.

d. Joint METOC Viewer. JMV is agovernment-owned system developed byFLENUMMETOCCEN and SpaceWarfighting Systems Command, used to viewgridded METOC data. It has the capabilityof receiving data via the NIPRNET orSIPRNET from multiple sources and inmultiple data formats. Using state-of-the-artgraphical user interface, the METOC user hasthe ability to “rubber-band” geographicarea(s) of interest and overlay a variety of datatypes (gridded data, satellite imagery, andobservational weather symbols) and otherenhancements. Products that are generatedby JMV are exportable to a variety of formats,usable on stand-alone workstations, webpages, and C4I systems.

e. 55th SWXS Homepages. Spaceenvironment data, analysis, and forecastproducts are available via an Internet-stylehomepage being developed for the NIPRNETand SIPRNET. As this transition progresses,the 55th SWXS is developing easy tounderstand, highly user friendly products toreplace current text-based products.

APPENDIX MMETOC FORECAST CENTER

M-1

1. Overview

The DOD MFCs are composed ofproduction facilities from two categories. Thefirst category consists of Air Force and Navyworldwide production and climatologyfacilities (FLENUMMETOCCEN, AFWA,NAVOCEANO, 55th SWXS, AFCCC, andF l e e t N u m e r i c a l M e t e o r o l o g i c a land Oceanograph ic De tachment(FLENUMMETOCDET), Asheville, NorthCarolina). The second category consists ofAir Force and Navy theater component and/or regional METOC production facilities thatare responsible for a specific geographic area.All MFC production facilities can provideproducts that are used to support the JFC andcomponent forces. MFC production facilitiesand their capabilities are described in thisappendix as a tool to assist the JMO indeveloping and executing JFC METOCoperations.

2. MFC Worldwide Productionand Climatology Facilities

a. FLENUMMETOCCEN. The primarymission of FLENUMMETOCCEN is toprovide global numerical METOC data fieldsto other production centers, regional centers,and operating forces worldwide. Consistencyamong all military forecast products isprovided through the common DOD baselineglobal numerical METOC data setgenerated by FLENUMMETOCCEN.FLENUMMETOCCEN runs global and higherresolution regional atmospheric andoceanographic analyses and forecast models.Its primary global atmospheric model is theNavy Operational Global AtmosphericPrediction System (NOGAPS). NOGAPSprovides the common baseline globalnumerical METOC data set utilizedthroughout the Department of Defense. The

high-resolution Coupled Ocean AtmosphereMesoscale Prediction System (COAMPS)regional numerical forecast model can berelocated to cover any contingency region inthe world on short notice. COAMPS is a nextgeneration tactical scale model, providingfully integrated METOC prediction capabilityfor DOD missions in sea-air-land operations.It can output numerical fields at resolutionsless than 10 km. In addition to globalNOGAPS and regional COAMPS, theEnsemble Forecast System provides aprobability approach to longer-term weatherprediction. The Oceanographic Wave Modelis run at both global and regional resolutions.FLENUMMETOCCEN’s primary oceannowcast model is the Optimum ThermalIn te rpo la t i on Sys tem, w i th theThermodynamic Ocean Prediction Systemproviding the forecast of the upper oceanthermal structure. Through linkages withDOD and NOAA environmental datadistribution and satellite systems,FLENUMMETOCCEN acquires globalobservational METOC data. Dataassimilation capabilities for initialization ofthe numerical models include use of all-sourceobservational data. Data acquisition isprimarily through direct connectivity to theAutomated Digital Weather Switch, NationalCenters for Environmental Prediction,AFWA, and NAVOCEANO. Data sourcesinclude: worldwide land and shipobservations, METARS, rawindsondeobservation reports, drifting buoy data, bathyreports and ingest of polar orbiting satellites,and geostationary satellites by either directreadout or satellite and/or landlineconnectivity with receiving and/or processingsites. General product types include analysisand numerical forecast fields of primaryMETOC parameters. These fields are madeavailable for distribution on Navy or joint C4Isystems via Navy theater MFC production

M-2

Appendix M

Joint Pub 3-59

facilities, and are sent to AFWA for use indeveloping products and GDFs shipped onAir Force or Army C4I systems. Availableworldwide and/or regional satellite productsinclude operational linescan system imagery(visual and/or IR), special sensor microwaveimager (wind speed, rain rate, and watervapor) and scatterometery data (available viaFLENUMMETOCCEN web homepages).Numerical model and satellite productdissemination is also made via NODDS(phone line and/or computer modem) and theJMV (NIPRNET, SIPRNET, and/or JWICS[INTELINK]). JMV, a web-based browser,is FLENUMMETOCCEN’s primary viewerfor both numerical fields and satelliteproducts. Computer flight planning isachieved via phone line and/or computermodem using FLENUMMETOCCEN’sOPARS. FLENUMMETOCCEN’s numericalmodel output is also used to produce tailoredproducts in response to customer requests.These products include general environmentaldata, ballistic winds, ocean temperatureprofiles and search and rescue information.

b. AFWA. AFWA is the DOD center fordefense meteorological satellite dataprocessing, and the only US agency providingautomated worldwide cloud depictions andforecasts. Within AFWA, the SpecialOperations Forces Weather Operations Centerprovides worldwide, mission-tailoredMETOC services to SOF, acts as aclearinghouse for unique data requests fromthe SOF customers, and serves as a liaison toNavy METOC organizations providing SOFsupport during joint operations. AFWAfocuses primarily on weather support toworldwide air and/or land operations, but canperform theater and/or regional specificsupport as well. To do this, AFWA integratesatmospheric and satellite observations to buildan accurate, worldwide weather data base inorder to produce gridded analysis and forecastfields of parameters that feed specificapplication programs for the warfighter.Weather reports from meteorological sources

throughout the world are gathered and relayedto AFWA. These reports are combined withinformation available from military andcivilian meteorological satellites to constructa near real time, integrated environmental database. Computer programs then model thisatmospheric data base and project changes.These models form building blocks forworldwide, tailored weather support towarfighters. Contingencies are supportedusing fine-scale, highly accurate mesoscalemodel output. Deployed forces can besupported with the Mesoscale Model 5(MM5) on short notice, usually less than 1hour. AFWA provides the warfighter withworldwide forecasts of hazards to flight suchas turbulence, icing, and thunderstorms.Model output is used to produce worldwideforecasts of fronts, sensible weather, andinstrument meteorological conditions and/orvisual meteorological conditions regions.Access to numerical weather prediction(NWP) METOC f ie lds i s ga inedth rough landline connectivity withFLENUMMETOCCEN. AFWA’s dataacquisition is chiefly through the AWN, withobservations, forecasts, and advisories relayedvia high-speed circuitry. Satellite data fromDMSP and the National EnvironmentalSatellite Data and Information Service polarorbiting and geostationary satellites is relayedto AFWA via communications satellite and/or direct readout. Foreign geostationarysatellite imagery is relayed over landlines.Worldwide data and product dissemination isvia the Air Force Digital Graphics System forfacsimile graphics; via the AWN for AN data;and the AWDS for both graphics and AN.Deployed forecasters can use AFWIN and/orSAFWIN to access AFWA generated ANbulletins, GDFs, graphical analysis andforecast products, imagery from satelliteglobal data base and high resolution DMSPsatellite imagery. Observations, terminalaerodrome forecasts, and non-AFWA AN canalso be obtained. Computer flight plans,mission-tailored products, and other ANproducts are provided over AUTODIN to

M-3


users in the field. Computer flight plans arealso delivered via PSTN, DISN, Air ForceDigital Communications Network, and STU-III. General product types include clouddepiction and forecast products and air-landbattle support products (E-O TDAs, soilmoisture). An integrated product in the GDFformat provides the basis for AFWA supportto JFC operations. This support productachieves consistency through the use ofcommon NWP data fields fromFLENUMMETOCCEN. Procedures toreceive support are contained in Air ForceInstruction (AFI) 15-118. Additionally,graphic products and some AN products arelisted in Air Force Catalog 15-152, Volumes1, 2, and 3.

Note: FLENUMMETOCCEN and AFWAare the two primary production facilities ofthe worldwide MFC network. Incombination, these centers provide most ofthe central site data and/or products neededto support in-theater requirements.Operationally, these centers are electronicallyconnected and produce an integrated productset for the theater and are available fortransmission to supported componentsthrough existing component C4I systems.

Primary contributions made to the integratedproduct set from each site include NWPanalysis and forecast fields of primarymeteorological parameters, ocean basinmode l data and/or products fromFLENUMMETOCCEN, cloud depiction, andforecast products and/or air-land battle supportproducts (E-O TDAs, soil moisture) fromAFWA. Consistency within the integratedproduct set is achieved through use ofcommon NWP da ta f i e lds f romFLENUMMETOCCEN at both sites in thegeneration of all applications products.Analysis, forecasts, and parameters includedin the integrated product set are shown inFigure M-1.

c. NAVOCEANO. The primary missionof NAVOCEANO is the global collection,processing, analysis, and distribution ofhydrographic and/or bathymetric geospatialfeature layers, littoral oceanographicphenomena, geophysical parameters, andimagery and/or remote sensing derivedproducts to military services and DODactivities. This distribution is in response tostrategic planning (OPLANs and OPORDs),tactical, littoral, and riverine missionexecution and crisis support requirements.

CONTENTS OF THE INTEGRATED PRODUCT SET

Temperature Dew Point Depression

Wind Speed Wind Direction

Geopotential Height Surface Pressure

Cloud Analysis Products Inversion Height

Rain Rate Precipitation Accumulation

Soil Moisture Soil Temperature

Snow Cover Sea State Conditions

Visibility Upper Air Pressure

Contrails Inversion Top Temperature

Thunderstorms Icing

Turbulence Cloud Forecast Products

Relative Humidity Vertical Vorticity

Present Weather

Figure M-1. Contents of the Integrated Product Set

M-4

Appendix M

Joint Pub 3-59

NAVOCEANO is the Department ofDefense’s only dedicated “center ofexcellence” for operational oceanographicdata collection, analysis, and products.NAVOCEANO controls eight multi-purposeoceanographic and hydrographic survey shipswhich survey forward areas of interestagainst geographic CINC requirements.NAVOCEANO’s Warfighting Support Centerposts a number of operational products onNIPRNET, SIPRNET, INTELINK, and JointDeployable Intelligence Support System.These products use all-source information, toinclude notice to mariners, commercialsources, foreign data (through exchangeagreements for port, harbor, and riverineproducts), and other agency remotely sensedcollections, to provide over 100 differentessential elements of information for anygiven area of interest. Through agreementswith naval laboratories, universities, andindustry, NAVOCEANO uses aircraft,unmanned underwater vehicles, autonomousairborne vehicles, buoys, and other deployedsensors to collect tactically significant spectraldata required for littoral mission supportproducts. NAVOCEANO maintains theworld’s largest oceanographic, bathymetric,and hydrographic data bases, which can beaccessed through classified and unclassifiedweb interfaces. NAVOCEANO also operatesthe Maury Library (world’s largestoceanographic library). The command alsoprovides operational model predictions formine drift, oil dispersion, water temperature,tides, currents, wave heights, and otheroceanographic dynamic processes by usingthe unique computing resources of their DODmajor shared resource center, which containsstate-of-the-art vector and parallel processinglarge scale computer systems linked to theTrent Lott Visualization Institute for datasimulation and display. NAVOCEANO’s1,000 employee team of military and civilianexperts is comprised of engineers, computerscientists, oceanographers, mathematicians,physicists, geologists, geophysicists,biologists, image analysts, and physical

scientists that make up the core oceanographiccollection, analysis, and production capability.NAVOCEANO is also responsible for trainingall military and civilians in operationaloceanography and hydrography. Foreign andUS officers can attend a 6-monthhydrographic program that culminates in aninternationally recognized B class license.Service METOC officers can attend a jointMETOC tactical training program or canselect from several tactical oceanographyworkshops designed to emphasize marineenvironmental impacts on weapons, sensors,and missions in support of ASW, minewarfare, undersea warfare, special warfare,and amphibious operations. NAVOCEANO’straining department also conducts training forfleet units in oceanography and hydrology,including the following courses: TacticalOceanography Refresher, Tactical AtmosphericRefresher, Tactical Oceanography Workshop,Joint METOC Tactical Applications Course,Tactical OA Division Trainer, InternationalHydrographic Management and EngineeringProgram, Basic Oceanography AccessionTraining, Reserve Aerographer ’s MateSchool, Satellite Video Tele-Training, andtraining and support during fleet exercises.

d. Naval Ice Center (NAVICECEN).The primary mission of the NAVICECEN isto provide global, regional, specialized, andtactical tailored ice products (analyses andforecasts) and services to deployed forces andother production centers. Additionally,NAVICECEN deploys ice reconnaissanceteams to observe and forecast ice conditionsand provide tactical METOC servicesthroughout the polar regions.

e. 55th Space Weather Squadron(formerly Air Force Space ForecastCenter). 55th SWXS is the sole source ofoperational space environment support to theDepartment of Defense. Customers includemission planners and operators of satellites,surveillance and/or space-tracking radars, andcommunication systems that operate in or

M-5


through the space environment (altitudes ofroughly 50 km and above). 55th SWXS isthe most advanced and complete spaceenvironment support facility in the world.Advanced computer hardware and softwareis used to process incoming spaceenvironment measurements from ground- andspace-based sensors to build a comprehensive,accurate real-time data base from which togenerate analysis and forecast productstailored to specific user needs. A sophisticatedon-site, real-time communications networkgives 55th SWXS the ability to receive anassortment of space environment data anddisseminate numerous support products to awide variety of DOD users. 55th SWXS’smission is to provide timely and accuratespace environment observations, analyses,forecasts, and warnings to enhance theoperational capability of worldwide DODforces and national agencies. To accomplishthis mission, 55th SWXS observes andpredicts space environment parameters for theearth’s ionosphere and magnetosphere, as wellas the sun and interplanetary space. 55thSWXS also provides event warningnotifications for solar flares, solar radio bursts,geomagnetic disturbances, energetic chargedparticle events, and radio absorption events.Data collected by ground-based solarobservatories and magnetometers are used togenerate solar and planetary geomagneticindices needed to specify neutral atmosphericdensity variations, as well as provide anoverall indication of solar and geomagneticactivity. 55th SWXS also performs customer-tailored anomaly assessments of spaceenvironment impacts for spacecraft,radars, and communication systems.Communications connectivity includestelephone (DSN, Comm, and secure voice),electronic bulletin board, AUTODIN, AWN,AFDIS, AFWIN, SAFWIN, and facsimile.SIPRNET and NIPRNET homepages arebeing developed for SMOs and JMOpersonnel.

Procedures to receive support are referencedin AFI 15-118. Detailed product listing is inAFCAT 15-152, Vol 5.

f. Air Force Combat ClimatologyCenter. AFCCC collects and stores globalweather observations in its climatic data base.It analyzes and applies information from thatdata base, the Air Force Weather (AFW)Technical Library, and other sources toprepare tailored weather studies and analysesfor DOD forces. AFCCC can prepare tailoredweather studies on almost any facet ofmeteorology affecting military operationsfrom the earth’s surface through 400,000 feetmean sea level. All studies and analyses aretailored to user requests. Communicationscapabilities include DSN and commercialphone (both STU-III and nonsecure),Worldwide homepage, nonsecure and securefacsimile, and Defense Message System.General product types include airfieldsummary packages, surface observationclimatic summaries, cloud ceilingclimatologies (CD-ROM only), climaticbriefs, specialized precipitation andtemperature studies, descriptive (narrative)climatology studies, engineering design andconstruction studies, environmentalsimulation studies, low-level routeclimatologies, mission success indicators,wind duration studies. Selected products arecurrently being converted to CD ROM.

Procedures to receive support are found inAFI 15-118. Special product requestprocedures are provided in both Chapter IIand Appendix A of AFCCC TechnicalNote-94/001.

Contingency support needed before JMFUactivation should be requested from either anAFCCC or USAF component operationsofficer or the Department of Justice. USAFand/or Army support requests requiring NavyMETOC climatological support input will

M-6

Appendix M

Joint Pub 3-59

be coordinated between AFCCC andFLENUMMETOCDET Asheville, withresponse provided through AFCCC asspecified by Commander, NAVMETOCCOM(COMNAVMETOCCOM) and AFWMemorandum of Agreement.

Detailed product listing is found in AFCAT15-152, Vol 4. Additionally, a complete listingis provided in “Capabilities, Products, andServices of AFCCC,” published periodicallyas an AFCCC Technical Note (current versionis AFCCC Technical Note-95-001).

g. FLENUMMETOCDET Asheville.FLENUMMETOCDET Asheville managesthe Navy’s climatology program. In thiseffort, the Asheville Detachment collects,quality controls, and archives Navy andUSMC meteorological observations. Thisdata is analyzed monthly and made availablevia the Detachment’s web site. Navy andUSMC station climatology is updated at leastevery 3 years or more often, as required. In ajoint effort with the National Climatic DataCenter, an international station meteorologicalclimatic summary (ISMCS) is produced andregularly updated. This jointly produced CD-ROM product provides over 6,500climatology updates for stations all over theglobe. Communications connectivity for theDetachment includes: secure, unsecuretelephone (recording after normal workhours), Federal Telecommunications System,facsimile, and Internet access (e-mail andhomepage). Additionally, the Detachment hasAUTODIN message receipt and transmitcapabilities. General product types includepaper-based marine atlases, regional studies,and tabular publications. CD-ROM productsinclude selected global station climaticsummaries (ISMCS), global tropical atlases,global upper air data, and a global MarineClimatology Atlas. On-line products includea gridded marine data set, tropical data, Navyand USMC station data, selected manuals andinstructions, and on-line request capabilities.

Additionally, the Detachment serves as arepository for global gridded fields.

For procedures to receive support, seeCOMNAVMETOCCOM Instruction 3140.1series, “US Navy Oceanographic andMeteorological Support System Manual,” orcoordinate directly via phone.

3. Theater Component andRegional MFC ProductionFacilities

a. Navy. Navy theater MFC productionfacilities function as regional and/or theatercomponent hubs for dissemination ofMETOC data, providing a full spectrum ofMETOC support services to Navy componentforces and joint forces upon request. Theseproduction facilities administer NavyMETOC operations within assigned operatingareas. Regional MFC production facilitiesprovide tailored analyses and forecastguidance products focused on individualcomponent’s maritime and littoral operatingareas. These centers routinely producesignificant weather and sea advisories andwarnings, individual ship route forecasts and/or aviation weather forecasts, optimum trackship routing services, deployable METservices, ocean frontal position analyses, andacoustic prediction services to supportmaritime operations. Additional tailoredMETOC data, products, and/or services canbe packaged to support exercise andcontingency operations. These centers canserve as the coordinating MFC during theplanning and execution phase of jointoperations. Expertise in regional and/ortheater METOC conditions coupled withaccess to multiple communication paths givethese centers ideal capabilities to perform theduties of a JMFU on short notice.

Theater and/or regional MFC productionfacilities are located as follows.

M-7


• NAVLANTMETOCCEN, NAS Norfolk,Virginia.

• NAVEURMETOCCEN, Rota, Spain.

• NAVPACMETOCCEN, Pearl Harbor,Hawaii.

• NAVPACMETOCCEN West and/orJoint Typhoon Warning Center, Guam.

Support procedures may be found inCOMNAVMETOCCOM Instruction 3140.1series, “US Navy Oceanographic andMeteorological Support System Manual,” orphone the supporting theater MFC elementdirectly to request services.

b. Air Force. USAF theater and/orregional MFC production facilities functionas the Air Force, Army, and SOF componenthubs for the dissemination of tailored METOCinformation support to Air Force and Armycomponent forces within their operating areas,and joint forces upon request or tasking fromthe SMO or JMO. Air Force theater MFCproduction facilities produce and providetailored analysis and forecast guidanceproducts focused on the individualcomponents’ air-land areas. These centersroutinely produce significant weatheradvisories and warnings, analyses, andforecasts as well as other tailored METOCforecast data bases, products, and/or servicesto support peacetime, exercise, and

contingency operations. These centersproduce AN and graphical products such ascloud and visibility forecasts, drop zoneforecasts, hazards forecasts, air refuelingforecasts, and various other tailored METOCdata, products, and/or services. Detailedproduct descriptions and information on howto obtain specific support can be obtained bycalling the individual center directly. Thefollowing is a list of Air Force theatercomponent MFC production facilities.

• 607 Weather Squadron, Yongsan AIN,South Korea

• 11th Operational Weather Squadron,Elmendorf AFB, Alaska

• USAFE Operational Weather Squadron,Sembach AB, Germany

• 25th Operational Weather Squadron,Davis-Monthan AFB, Arizona

• 15th Operational Weather Squadron,Scott AFB, Illinois

• 28th Operational Weather Squadron,Shaw AFB, South Carolina

• 25th Operational Weather Squadron,Barksdale AFB, Louisiana

• 20th Operational Weather Squadron,Yokota AB, Japan

M-8

Appendix M

Joint Pub 3-59

Intentionally Blank

APPENDIX NREFERENCES

N-1

The development of Joint Pub 3-59 is based upon the following primary references.

1. Joint Pub 1, “Joint Warfare of the Armed Forces of the United States.”

2. Joint Pub 0-2, “Unified Action Armed Forces (UNAAF).”

3. Joint Pub 1-01, “Joint Publication System, Joint Doctrine and Joint Tactics, Techniques,and Procedures Development Program.”

4. Joint Pub 1-02, “DOD Dictionary of Military and Associated Terms.”

5. Joint Pub 2-0, “Doctrine for Intelligence Support to Joint Operations.”

6. Joint Pub 2-01, “Joint Intelligence Support to Military Operations.”

7. Joint Pub 2-01.3, “Joint Tactics, Techniques, and Procedures for Joint IntelligencePreparation of the Battlespace.”

8. Joint Pub 3-0, “Doctrine for Joint Operations.”

9. Joint Pub 3-54, “Joint Doctrine for Operations Security.”

10. Joint Pub 5-03.1, “Joint Operation Planning and Execution System Vol I: (PlanningPolicies and Procedures).”

11. CJCSI 3500.01A, “Joint Training Policy for the Armed Forces of the United States.”

12. CJCSI 3810.01A, “Meteorological and Oceanographic Operations.”

13. CJCSM 3122.02, “Crisis Action Time-Phased Force and Deployment Data Developmentand Deployment Execution.”

14. CJCSM 3122.03, “Joint Operation Planning and Execution System Vol II: (PlanningFormats and Guidance).”

15. CJCSM 3500.03, “Joint Training Manual for the Armed Forces of the United States.”

16. DOD Directive Number 5100.1, “Functions of the Department of Defense and its MajorComponents.”

17. Joint METOC Interoperability Team Functional Process Improvement AS-IS ModelingReport on Joint METOC Operations, 15 May 95.

N-2

Appendix N

Joint Pub 3-59

18. AF Doctrine Document 45, 31 August 1994, “Aerospace Weather Operations.”

19. AF Doctrine Document 1, September 1997, “Air Force Basic Doctrine.”

20. Army Field Manual 6-15, 18 Jun 1992, “Tactics, Techniques, and Procedures for FieldArtillery Meteorology.”

21. Army Field Manual 34-81/Air Force Joint Pamphlet 15-127, “Weather Support to ArmyOperations.”

22. Army Field Manual 34-130, “Intelligence Preparation of the Battlefield.”

23. Army Field Manual 100-5, “Operations.”

24. Army Regulation 115-10/Air Force Joint Instruction 15-157, “Weather Support for theUS Army.”

25. COMNAVMETOCCOM Instruction 3140.1 Series, “US Navy Oceanographic andMeteorological Support System Manual.”

26. FCM-I5-1995, Dec 95, “Federal Directory of Mobile Meteorological Equipment andCapabilities.”

27. Marine Corps Warfighting Publication 3-35.7, “MAGTF METOC Support.”

28. Naval Warfare Publication-l, “Strategic Concepts of the US Navy.”

29. Special Operations METOC Tactics, Techniques and Procedures, 1 June 1996

30. TRADOC Pamphlet 525-5, 1 August 1994, “Airland Operations — A Concept for theEvolution of Airland Battle for the Strategic Army of the 1990s and Beyond.”

31. TRADOC Pamphlet 525-21/MAC Pamphlet 105-3, 10 July 1987, “Joint OperationalConcept for Weather and Environmental Support to Army Operations.”

32. SOCOM Manual 525-6, March 1998, “Critical METOC Thresholds for SOF Operations.”

APPENDIX OADMINISTRATIVE INSTRUCTIONS

O-1

1. User Comments

Users in the field are highly encouraged to submit comments on this publication to theUnited States Atlantic Command Joint Warfighting Center, Attn: Doctrine Division,Fenwick Road, Bldg 96, Fort Monroe, VA 23651-5000. These comments should addresscontent (accuracy, usefulness, consistency, and organization), writing, and appearance.

2. Authorship

The lead agent for this publication is the US Air Force. The Joint Staff doctrine sponsorfor this publication is the Director for Operations (J-3).

3. Supersession

This publication supersedes Joint Pub 3-59, 22 December 1993, “Joint Doctrine forMeteorological and Oceanographic Support.”

4. Change Recommendations

a. Recommendations for urgent changes to this publication should be submitted:

TO: HQ AFDC MAXWELL AFB AL//DR//INFO: JOINT STAFF WASHINGTON DC//J7-JDD//

Routine changes should be submitted to the Director for Operational Plans andInteroperability (J-7), JDD, 7000 Joint Staff Pentagon, Washington, DC 20318-7000.

b. When a Joint Staff directorate submits a proposal to the Chairman of the JointChiefs of Staff that would change source document information reflected in thispublication, that directorate will include a proposed change to this publication as anenclosure to its proposal. The Military Services and other organizations are requestedto notify the Director, J-7, Joint Staff, when changes to source documents reflected inthis publication are initiated.

c. Record of Changes:

CHANGE COPY DATE OF DATE POSTEDNUMBER NUMBER CHANGE ENTERED BY REMARKS__________________________________________________________________________________________________________________________________________________________________________________________________________________

O-2

Appendix O

Joint Pub 3-59

5. Distribution

a. Additional copies of this publication can be obtained through Service publicationcenters.

b. Only approved pubs and test pubs are releasable outside the combatant commands,Services, and Joint Staff. Release of any classified joint publication to foreigngovernments or foreign nationals must be requested through the local embassy (DefenseAttaché Office) to DIA Foreign Liaison Office, PSS, Room 1A674, Pentagon,Washington, DC 20301-7400.

c. Additional copies should be obtained from the Military Service assignedadministrative support responsibility by DOD Directive 5100.3, 1 November 1988,“Support of the Headquarters of Unified, Specified, and Subordinate Joint Commands.”

By Military Services:

Army: US Army AG Publication Center SL1655 Woodson RoadAttn: Joint PublicationsSt. Louis, MO 63114-6181

Air Force: Air Force Publications Distribution Center2800 Eastern BoulevardBaltimore, MD 21220-2896

Navy: CO, Naval Inventory Control Point700 Robbins AvenueBldg 1, Customer ServicePhiladelphia, PA 19111-5099

Marine Corps: Marine Corps Logistics BaseAlbany, GA 31704-5000

Coast Guard: Coast Guard Headquarters, COMDT (G-OPD)2100 2nd Street, SWWashington, DC 20593-0001

d. Local reproduction is authorized and access to unclassified publications isunrestricted. However, access to and reproduction authorization for classified jointpublications must be in accordance with DOD Regulation 5200.1-R.

GLOSSARYPART I — ABBREVIATIONS AND ACRONYMS

GL-1

ABCS Army Battle Command SystemACR armored cavalry regiment (Army)ADP automated data processingAFB Air Force BaseAFCCC Air Force Combat Climatology CenterAFDIS Air Force Weather Agency Dial In SubsystemAFFOR Air Force forcesAFI Air Force InstructionAFW Air Force WeatherAFWA Air Force Weather AgencyAFWIN Air Force Weather Information NetworkAMC Air Mobility CommandAN alphanumericAOR area of responsibilityARFOR Army forcesARTYMET artillery meteorologicalASW antisubmarine warfareATC air traffic controlAUTODIN Automatic Digital NetworkAWDS automated weather distribution systemAWN Automated Weather Network

BT bathythermograph

C2 command and controlC4I command, control, communications, computers, and

intelligenceCAD collection address designatorCINC commander in chiefCJCS 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 ForceCOA course of actionCOAMPS Coupled Ocean Atmosphere Mesoscale Prediction SystemCOE common operating environmentCOMNAVMETOCCOM Commander, Naval Meteorology and Oceanography

CommandCOMSEC communications securityCONOPS concept of operationsCONPLAN operation plan in concept formatCOP common operating pictureCSS communications subsystemCWT combat weather team

GL-2

Glossary

Joint Pub 3-59

DII defense information infrastructureDISN Defense Information Systems NetworkDMSP Defense Meteorological Satellite ProgramDOD Department of DefenseDSN Defense Switched Network

E-O TDA electro-optical tactical decision aidESK electronic staff weather officer kit

FALOP forward area limited observation programFLENUMMETOCCEN Fleet Numerical Meteorology and Oceanography CenterFLENUMMETOCDET Fleet Numerical Meteorological and Oceanographic

DetachmentFTP file transfer protocol

G-2 Army or Marine Corps component intelligence staff officerGCCS Global Command and Control SystemGCCS-A Global Command and Control System-ArmyGCCS-M Global Command and Control System-MaritimeGDF gridded data field

HF high frequencyHFRB high frequency regional broadcast

ICECON control of ice informationICP Intertheater Communication Security (COMSEC) PackageIMETS Integrated Meteorological SystemIMOSS interim mobile oceanographic support systemINMARSAT International Maritime SatelliteIR infraredISMCS international station meteorological climatic summary

J-2 Intelligence Directorate of a joint staffJ-3 Operations Directorate of a joint staffJ-6 Command, Control, Communications, and Computer Systems

Directorate of a joint staffJAFWIN JWICS Air Force weather information networkJFACC joint force air component commanderJFC joint force commanderJFLCC joint force land component commanderJFMCC joint force maritime component commanderJFSOCC joint force special operations component commanderJMAG Joint METOC Advisory GroupJMFU joint METOC forecast unitJMO joint METOC officerJMV joint METOC viewerJOA joint operations areaJOAF joint operations area forecast

GL-3

Glossary

JOPES Joint Operation Planning and Execution SystemJSOTF joint special operations task forceJTF joint task forceJULLS Joint Uniform Lessons Learned SystemJWICS Joint Worldwide Intelligence Communications System

KQ tactical location identifiers

LOI letter of instructionLSS local sensor subsystem

MAGTF Marine air-ground task forceMAR METOC assistance requestMARFOR Marine Corps forcesMEF Marine expeditionary forceMET mobile environmental teamMETARS aviation routine weather report (translated from French;

METARS is the international standard code format forhourly surface weather observations)

METCON control of meteorological informationMETMF meteorological mobile facilityMETMF (R) meteorological mobile facility (replacement)METOC meteorological and oceanographicMETSAT meteorological satelliteMFC Meteorological and Oceanographic (METOC) Forecast CenterMIDDS-T Meteorological and Oceanographic (METOC) Integrated Data

Display System-TacticalMOOTW military operations other than warMRS meteorological radar subsystemMSE mobile subscriber equipmentMSS meteorological satellite subsystemMST Marine expeditionary force (MEF) weather support teamMTW major theater warMWSG Marine wing support groupMWSS Marine wing support squadron

NAVEURMETOCCEN Naval Europe Meteorology and Oceanography CenterNAVFAX Navy facsimileNAVFOR Navy forcesNAVICECEN Naval Ice CenterNAVLANTMETOCCEN Naval Atlantic Meteorology and Oceanography CenterNAVMETOCCOM Naval Meteorology and Oceanography CommandNAVOCEANO Naval Oceanographic OfficeNAVPACMETOCCEN Naval Pacific Meteorology and Oceanography CenterNCA National Command AuthoritiesNCS net control stationNIPRNET Unclassified but Sensitive Internet Protocol

Router Network

GL-4

Glossary

Joint Pub 3-59

NITES Navy Integrated Tactical Environmental SystemNMOSW Naval METOC Operational Support WebNOAA National Oceanic and Atmospheric AdministrationNODDS Naval Oceanographic Data Distribution SystemNOGAPS Navy Operational Global Atmospheric Prediction SystemNSDS-E Navy Satellite Display System-EnhancedN-TFS New Tactical Forecast SystemNWP numerical weather prediction

OA Operations Aerology shipboard METOC divisionOCEANCON control of oceanographic informationOPARS Optimum Path Aircraft Routing SystemOPLAN operation planOPORD operation orderOPSEC operations security

PC personal computerPCS processing subsystemPIREP pilot reportPMS portable meteorological subsystemPSTN Public Switched Telephone Network

QRCT quick reaction communications terminal

RSS remote sensors subsystemRWS rawinsonde subsystem

S-2 battalion or brigade intelligence staff officer (Army, MarineCorps battalion or regiment)

SAFWIN secure Air Force weather information networkSATCOM satellite communicationsSIPRNET SECRET Internet Protocol Router NetworkSMO senior METOC officerSOF special operations forcesSOWT special operations weather teamSPACECON control of space informationSSC smaller scale contingencySSS shelter subsystemSTT small tactical terminalSTU-III secure telephone unit IIISWI special weather intelligenceSWO staff weather officerSWXS Space Weather Squadron

TACC tanker airlift control centerTALCE tanker airlift control elementTARWI target weather and intelligenceTESS Tactical Environmental Support System

GL-5

Glossary

TFS Tactical Forecast SystemTIROS television infrared observation satelliteTPFDD timed-phased force and deployment data

UAV unmanned aerial vehicleUSAF United States Air ForceUSMC United States Marine CorpsUSN United States NavyUSTRANSCOM United States Transportation Command

VDS video subsystem

WEFAX weather facsimile

GL-6 Joint Pub 3-59

atmosphere. The air surrounding the Earth.(Joint Pub 1-02)

direct support. A mission requiring a forceto support another specific force andauthorizing it to answer directly to thesupported force’s request for assistance.Also called DS. (This term and itsdefinition modify the existing term and itsdefinition and are approved for inclusionin the next edition of Joint Pub 1-02.)

environmental services. The variouscombinations of scientific, technical, andadvisory activities (including modificationprocesses, i.e., the influence of manmadeand natural factors) required to acquire,produce, and supply information on thepast, present, and future states of space,atmospheric, oceanographic, and terrestrialsurroundings for use in military planningand decision making processes, or tomodify those surroundings to enhancemilitary operations. (Joint Pub 1-02)

interoperability. 1. The ability of systems,units, or forces to provide services to andaccept services from other systems, units,or forces and to use the services soexchanged to enable them to operateeffectively together. (Joint Pub 1-02)

joint for ce. A general term applied to a forcecomposed of significant elements, assignedor attached, of two or more MilitaryDepartments, operating under a single jointforce commander. (Joint Pub 1-02)

joint force meteorological andoceanographic officer. Officer designatedto provide direct meteorological andoceanographic support to a joint forcecommander. Also called JMO. (This termand its definition modify the existing termand its definition and are approved for

PART II — TERMS AND DEFINITIONS

inclusion in the next edition of Joint Pub 1-02.)

joint meteorological and oceanographicforecast unit. An organization consistingof a jointly supported collective ofmeteorological and oceanographicpersonnel and equipment formed to providemeteorological and oceanographic supportto the joint force commander. Also calledJMFU. (This term and its definition modifythe existing term and its definition and areapproved for inclusion in the next editionof Joint Pub 1-02.)

meteorological and oceanographic. A termused to convey all meteorological(weather) and oceanographic (physicaloceanography) factors as provided byService components. These factors includethe whole range of atmospheric andoceanographic phenomena from the sub-bottom of the earth’s oceans up to the spaceenvironment (space weather). Also calledMETOC. (This term and its definition areapproved for inclusion in the next editionof Joint Pub 1-02.)

Meteorological and Oceanographic ForecastCenter. The collective of electronicallyconnected, shore-based meteorological andoceanographic (METOC) production facilitiesthat includes centers such as Air Force WeatherAgency, Navy Fleet Numerical METOCCenter, 55th Space Weather Squadron, NavalOceanographic Office, Warfighting SupportCenter, Air Force Combat Climatology Center,Fleet Numerical METOC Center Detachment,Asheville, North Carolina, and the Air Forceand Navy theater and/or regional METOCproduction activities. Also called MFC. (Thisterm and its definition modify the existing termand its definition and are approved forinclusion in the next edition of Joint Pub 1-02.)

GL-7

Glossary

meteorological data. Meteorological factspertaining to the atmosphere, such as wind,temperature, air density, and otherphenomena which affect militaryoperations. (Joint Pub 1-02)

meteorological watch. Monitoring theweather for a route, area, or terminal andadvising concerned organizations whenhazardous conditions that could affect theiroperations or pose a hazard to life orproperty are observed or forecast to occur.Also called METWATCH. (This term andits definition are applicable only in thecontext of this publication and cannot bereferenced outside this publication.)

meteorology. The study dealing with thephenomena of the atmosphere including thephysics, chemistry, and dynamics extendingto the effects of the atmosphere on theearth’s surface and the oceans. (This termand its definition are approved for inclusionin the next edition of Joint Pub 1-02.)

oceanography. The study of the sea,embracing and integrating all knowledgepertaining to the sea and its physicalboundaries, the chemistry and physics ofseawater, and marine biology. (Joint Pub 1-02)

senior meteorological and oceanographicofficer. Meteorological and oceanographicofficer responsible for assisting the

combatant commander and staff indeveloping and executing operationalmeteorological and oceanographic serviceconcepts in support of a designated jointforce. Also called SMO. (This term andits definition modify the existing term andits definition and are approved for inclusionin the next edition of Joint Pub 1-02.)

space environment. The region beginningat the lower boundary of the Earth’sionosphere (approximately 50 km) andextending outward which contains solidparticles (asteroids and meteoroids),energetic charged particles (ions, protons,electrons, etc.), and electromagnetic andionizing radiation (x-rays, extremeultraviolet, gamma rays, etc.). (This termand its definition are approved for inclusionin the next edition of Joint Pub 1-02.)

troposphere. The lower layers of theatmosphere, in which the change oftemperature with height is relatively large.It is the region where clouds form,convection is active, and mixing iscontinuous and more or less complete.(Joint Pub 1-02)

weather forecast. A prediction of weatherconditions at a point, along a route, orwithin an area, for a specified period of time.(Joint Pub 1-02)

GL-8

Glossary

Joint Pub 3-59

Intentionally Blank

Assess-ments/

Revision

CJCSApproval

TwoDrafts

ProgramDirective

ProjectProposal

J-7 formally staffs withServices and CINCS

Includes scope ofproject, references,milestones, and who willdevelop drafts

J-7 releases ProgramDirective to Lead Agent.Lead Agent can beService, CINC, or JointStaff (JS) Directorate

STEP #2Program Directive

!

!

!

The CINCS receive the puband begin to assess it duringuse

18 to 24 months followingpublication, the Director J-7,will solicit a written report fromthe combatant commands andServices on the utility andquality of each pub and theneed for any urgent changes orearlier-than-scheduledrevisions

No later than 5 years afterdevelopment, each pub isrevised

STEP #5Assessments/Revision

!

!

!

ENHANCEDJOINT

WARFIGHTINGCAPABILITY

Submitted by Services, CINCS, or Joint Staffto fill extant operational void

J-7 validates requirement with Services andCINCs

J-7 initiates Program Directive

!

!

!

STEP #1Project Proposal

All joint doctrine and tactics, techniques, and procedures are organized into a comprehensive hierarchy asshown in the chart above. is in the series of joint doctrine publications. Thediagram below illustrates an overview of the development process:

Joint Pub 3-59 Operations

JOINT DOCTRINE PUBLICATIONS HIERARCHYJOINT DOCTRINE PUBLICATIONS HIERARCHY

JOINT PUB 1-0 JOINT PUB 2-0 JOINT PUB 3-0

PERSONNEL

JOINT PUB 4-0 JOINT PUB 5-0 JOINT PUB 6-0

LOGISTICSINTELLIGENCE OPERATIONS C4 SYSTEMSPLANS

JOINTDOCTRINE

PUBLICATION

Lead Agent forwards proposed pub to JointStaff

Joint Staff takes responsibility for pub, makesrequired changes and prepares pub forcoordination with Services and CINCS

Joint Staff conducts formalstaffing for approval as a Joint Publication

STEP #4CJCS Approval

!

!

!

Lead Agent selects Primary ReviewAuthority (PRA) to develop the pub

PRA develops two draft pubs

PRA staffs each draft with CINCS,Services, and Joint Staff

!

!

!

STEP #3Two Drafts

JOINT PUB 1

JOINTWARFARE

JOINT PUB 0-2

UNAAF

Documents

JP 3-59, Joint Doctrine Tactics, Techniques, and ...edocs.nps.edu/2012/December/joint pub 3_59_1999.pdf · joint METOC officer (JMO) directs the JMFU when it is in the operational