Tab K: NIPRNET Individual Messaging Architecture Tab L: SIPRNET IP Address Listing
Appendix 9: Video Teleconferencing Plan
This appendix will provide necessary guidance, special instructions or restrictions, and diagrams required to install, operate, and maintain the VTC network. It will also address particular information pertaining to low bandwidth circuits and how VTC will be imple- mented on these circuits. Tabs are used to amplify this information.
Tab A: VTC Network Diagram Tab B: VTC H320 Network Diagram Tab C: VTC H323 Network Diagram Tab D: VTC Dialing Instructions
Appendix 10: Organizational Messaging Plan
This plan is often overlooked because of the reliance on individual messaging, but it should not be. It should identify how messages are received and routed to end users as well as how end users/staffs will draft and send their organizational message traffic. Coordinating instructions may specify software to be used, the requirement to submit per- missions to release message traffic, and any courier procedures. Handling of Top Secret message traffic should be addressed as well.
Tab A: SIPRNET Organizational Messaging Architecture Diagram Tab B: NIPRNET Organizational Messaging Architecture Diagram Tab C: Distinguished Name List
Tab D: Plain Language Addresses List
Appendix 11: Help Desk Procedures
This appendix outlines help-desk support procedures for all types of communications ter- minal devices and procedures. The fact that most Marines, Sailors, and contractors work with Internet service providers and telephone or cell phone providers while in garrison should become a combat multiplier for the G-6/S-6 in the deployed environment. There is no reason that help desk support in the deployed environment should be any different, or any less responsive. Provide a diagram or flowchart that maps the flow of information. Place this flowchart in a tab. Helpdesk POC should be listed as well. Other information, in tab or other form, may include—
• Procedures for how to establish network users’ accounts.
• Procedures for how to modify or delete accounts.
• Procedures for submitting trouble calls.
• Procedures for escalating trouble calls to a higher tier of maintenance/administration.
Tab A: Trouble Ticket Flow Chart Diagram
This tab should explain the trouble ticket work process from initiation of a trouble call, to closing the trouble call with the user’s problem fixed.
Appendix 12: Maintenance Procedures
This appendix should outline the procedures for inducting equipment into first echelon maintenance, as well as evacuating equipment to second echelon maintenance and above.
Considering the amount of COTS equipment that is currently used, as well as the contrac- tor support required to repair some critical low density equipment assets within the com- munications inventory, it is imperative that all users of this equipment are familiar with the proper maintenance procedures. Include maintenance POCs within this appendix.
Tab A: Contracted Logistic Support
Identify equipment that requires this type of support as well as other items such as fund- ing lines, POCs, or Marine Corps Systems Command project managers within this tab. A matrix identifying TAMCN [table of authorized materiel control number]/end item with relevant information is useful.
Tab B: Navy/Marine Corps Intranet Repair Flow Chart
The procedures for repairing Navy/Marine Corps Intranet assets should be identified within this appendix. The flowchart assists as a reference for this difficult process. These procedures and the flowchart ensure that the help desk is aware of the evacuation and repair procedures of these assets.
Appendix 13: Special Intelligence Network Plan
This appendix is a detailed plan of the communications support agreements made between intelligence section communications planners and communications section communications planners. It should expound upon annex K, paragraph 3.e, Intelligence and Reconnaissance.
Tab A: Radio Network Diagram
Similar types of diagrams (symbology, terms, SLD/CCSD) to those used in the Radio Network Plan, appendix 5, apply here; this will ensure standard operations and ser- vices provided.
Tab B: Multiplexing Network Diagram
Similar types of diagrams, such as symbology, terms, or SLD/CCSD, to those used in the Multiplexing Network Plan, appendix 6, apply here; this will ensure standard operations and services provided.
Tab C: Telephone Network Diagram
Similar types of diagrams, such as symbology, terms, or SLD/CCSD, to those used in the Telephone Network Plan, appendix 7, apply here; this will ensure standard operations and services provided.
Tab D: Data Network Diagram
Similar types of diagrams, such as symbology, terms, or SLD/CCSD, to those used in the Data Network Plan, appendix 8, apply here; this will ensure standard operations and ser- vices provided.
Tab E: VTC Network Diagram
Similar types of diagrams, such as symbology, terms, SLD/CCSD, to those used in the VTC Network Plan, appendix 9, apply here; this will ensure standard operations and ser- vices provided.
Appendix 14: Communications Support
This appendix covers the support areas that are required for a communications plan, as well as services that are not always required, but support the plan. For example, it may outline how the power requirements for the command post, xCCC, SYSCON, and TECH- CON will be maintained, or how forward command posts will use power. It should also contain diagrams for generators and power cables. In addition, it should outline what agency within H&S (company/battery/battalion) is responsible for power.
Tab A: Power Requirements
Though numerous items may be listed in this tab to include diagrams, concentration should be placed on at least the following items:
• Location of generators.
• Power cable routes.
• Power requirements for the command post/Marine TACC, SYSCON, TECHCON, staff tents/buildings, or maintenance facilities.
• Refueling plan/refueling route.
• Preventive maintenance plan to include power outage procedures and a checklist of what agencies need to be coordinated with for an outage.
Tab B: Special Maintenance Procedures
This tab covers everything that does not properly fit into the maintenance procedures appendix. For example, when video and storage WAN was initially fielded to I MEF as a proof of concept during Operation Iraqi Freedom II, repair parts for the platform were often difficult to obtain. Eventually, a small team of Marines and contractors worked out the supply problems. These procedures would fit well into this tab.
Tab C: Messenger Service
Messenger service during Operation Desert Storm/Desert Shield was used extensively by 5th MEB. During Operation Iraqi Freedom I, the GCE capitalized on this capability, while the ACE did not. This tab is not always required; however, this capability does exist within the GCE, ACE, and LCE. If a messenger plan is established, this appendix should outline the implementation of it. Often messengers travel in teams and leaving what they do to chance can be dangerous and costly in terms of life and equipment. The procedures and details — actions upon completion of the courier’s mission, immediate action procedures, or lost communications procedures — need to be thoroughly out- lined within this tab.
Appendix 15: Operational Risk Management
The purpose of this appendix is not to teach the operational risk management (ORM) pro- cess, but to use the ORM process in support of the various missions and actions the com- munications community must take in support of an operation. For example, an ORM assessment of the placement of a VHF retransmission team in support of a division for- ward movement would be critical in identifying the multiple risks and scenarios that a team may face, as well as what actions are required to mitigate those risks. This appendix may list some scenarios for the communicators to consider.
Tab A: ORM Worksheet
An example of a completed communications-related ORM worksheet should be included in this section.