Joint Metoc Handboo - IHMC Ontology and Policy Management
Joint Metoc Handboo - IHMC Ontology and Policy Management
Joint Metoc Handboo - IHMC Ontology and Policy Management
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
E-METOC LOI<br />
Appendix E - METOC Letter of Instruction (LOI) Examples<br />
E.1 METOC Letters of Instruction<br />
In developing a METOC LOI, be sensitive to differences between the Services. The Air<br />
Force tends to be explicit <strong>and</strong> will explain <strong>and</strong> task many items in an LOI. The “plan” is<br />
developed, <strong>and</strong> deviations or additional actions are coordinated as required during the<br />
“decentralized execution”. The Navy minimizes amplifying guidance, maximizing use of<br />
existing internal directives. If the CONOPS or LOI doesn’t say not to do it, you can do it<br />
(comm<strong>and</strong> by negation). Each mission is much like the previous, <strong>and</strong> Navy personnel<br />
usually know what to do without need for coordination. Suggested format for an LOI<br />
(from JP 3-59):<br />
• Originator<br />
• Addressees: units in the JTF, supporting force comm<strong>and</strong>ers, <strong>and</strong> supporting activities<br />
• Classification<br />
• Subject: unclassified exercise/operation name, followed by 'METOC LOI'<br />
• Reference: applicable/supporting OPORDs, OPLANs, etc.<br />
• Points of contact<br />
• Purpose: what does this LOI achieve?<br />
• Situation: why is a joint force METOC operation required?<br />
• Concept of METOC operations: how will the METOC function operate? Can<br />
reference Annex H<br />
• Assumptions<br />
• Planning factors: METOC conditions that may affect plan execution<br />
• Mission: METOC objectives in support of the <strong>Joint</strong> Force Comm<strong>and</strong>er's plan<br />
• Execution: time period of expected operations, coordinating instructions, tasks <strong>and</strong><br />
responsibilities. Paragraph B.1.2.3 of the <strong>H<strong>and</strong>boo</strong>k includes suggestions for<br />
paragraph 3 (Execution) of Annex H that are applicable in an LOI<br />
• Deployment: on-station time<br />
• OPSEC<br />
• Coordination instructions: instructions common to two or more components or<br />
subdivisions<br />
• Operational constraints: limiting factors, such as manning or equipment<br />
• Administration <strong>and</strong> Logistics<br />
• Equipment <strong>and</strong> Supplies<br />
• Comm<strong>and</strong> <strong>and</strong> Control: comm<strong>and</strong> relationships<br />
• METCON, OCEANCON, ICECON, SPACECON: conditions for implementation<br />
• Communications: METOC data flow/availability; homepages, KQ identifiers, etc.<br />
• Reporting: after action reports, equipment/personnel status, product assessments, etc.<br />
• METOC Assistance Requests: how to request special products<br />
E-1