Acknowledgements

Many individuals from various programs and organizations across the Army contributed to the content and creation of this Command Post Handbook.

PdM CPS&I LTC Carl J. Hollister Charles Henry (DAC)

Cameron Kramer (CTR) William Christopher (CTR)

Steve Jones (CTR) Susan Bermes (CTR) Michael Lynch (CTR) Montie Beaty (CTR) Mark Larkin (CTR)

TCM-MC

Steve Welks (DAC)

Combined Army Doctrine Directorate (CADD)

LTC Tony Deskis

MCCoE DOT-L

CPT (P) John C. Acosta MSG Jeffery L. Foster

SFC Jeremy M. Schultz SFC William M. Collins SFC Ronald E. Parrish SFC Raymond L. Petrik

James C. Madigan (DAC) Terence Jones (DAC)

Robert E. Mayhew (DAC) Christopher Glenn (DAC) Patrick L. Iverson (CTR)

Armin Ogden (CTR)

PM MEPS Jose Santos (DAC) Rob Nutter (DAC)

i

TABLE OF CONTENTS

Chapter 1.0 Introduction ............................................................................... 1-1 Chapter 2.0 Mission Command (MC) ........................................................... 2-1 2.1 Mission Command Defined ................................................................. 2-1 2.2 Mission Command Warfighting Function ............................................ 2-2 2.3 The Mission Command System (MCS) ............................................... 2-3

2.4 INFOSYS and Support to Mission Command ..................................... 2-6 Chapter 3.0 Characteristics of the Brigade Command Post (CP) ................. 3-1 3.1 Introduction ......................................................................................... 3-1 3.2 Physical CP Components ................................................................... 3-2 3.3 Initial CP Setup and Configuration ...................................................... 3-5 3.4 Power Distribution ............................................................................. 3-64

3.5 Combat Net Radios (CNR) and CP Communication System (CPCS) ......................................................................................... 3-76 3.6 Network Cabling ................................................................................ 3-78 3.7 Network Operations and System Architecture .................................. 3-79 3.8 Information Systems ......................................................................... 3-97

3.9 Configuration Customization ........................................................... 3-101 3.10 Network Services Architecture ........................................................ 3-102 3.11 Closing Information ......................................................................... 3-102 Chapter 4.0 Division/Corps/Army Service Component Command (ASCC) CPs ........................................................................................... 4-1 4.1 Introduction ......................................................................................... 4-1

4.2 Components of a Mission Command System ..................................... 4-3 4.3 Establishing the Command Post ......................................................... 4-5 4.4 Power Distribution ............................................................................. 4-75 4.5 Combat Net Radios (CNR) and CP Communication System (CPCS) ...... ......................................................................................... 4-86

4.6 Network Cabling ................................................................................ 4-88 4.7 Network Operations and System Architecture .................................. 4-89 4.8 Information Systems ....................................................................... 4-109 4.9 Configuration Customization ........................................................... 4-112 4.10 Conclusion. ..................................................................................... 4-114

ii

Chapter 5.0 Establishing the Command Post ............................................... 5-1 5.1 Introduction ......................................................................................... 5-1 5.2 Order of Setup .................................................................................... 5-2

5.3 Establish the BCT Tactical CP ............................................................ 5-2 5.4 Establish the Battalion CP (BN CP) .................................................... 5-5 5.5 Establish the BCT Main CP................................................................. 5-5 5.6 Standing Operating Procedures (SOPs) ............................................. 5-7 5.7 Displace the CP .................................................................................. 5-8 5.8 Select CP Location ............................................................................. 5-9

5.9 Occupy CP Location ........................................................................... 5-9 5.10 Transfer C2 Between CPs .................................................................. 5-9 5.11 System Validation ............................................................................. 5-13 5.12 Common Operational Picture (COP) ................................................. 5-14 5.13 Battle Drills ........................................................................................ 5-27

Chapter 6.0 Sustaining the Command Post (CP) ......................................... 6-1 6.1 Introduction ......................................................................................... 6-1 6.2 Daily Operation ................................................................................... 6-1 6.3 Safety ........................................................................................... 6-2 6.4 Information Systems (INFOSYS) ........................................................ 6-7 Chapter 7.0 Fielding and Training Support ................................................... 7-1

7.1 Introduction ......................................................................................... 7-1 7.2 Unit Set Fielding (USF) ....................................................................... 7-1 7.3 MCSI Overview ................................................................................... 7-7 7.4 Digital Systems Engineer (DSE) Roles and Responsibilities .............. 7-9 Chapter 8.0 Equipment and Maintenance .................................................... 8-1

8.1 Introduction ......................................................................................... 8-1 8.2 Troubleshooting Support ..................................................................... 8-1 8.3 TQGs and PDISE Support .................................................................. 8-6 APPENDIX A ................................................................................................ A-1 APPENDIX B ................................................................................................ B-1 APPENDIX C ............................................................................................... C-1

iii

LIST OF TABLES

Table 2.4.17-1 Example Brigade MC System Authorization ............................ 2-14 Table 3.3.2-1. CPP Initial Setup Tasks............................................................ 3-5 Table 3.3.3-1. Required Supplies for CP Setup .............................................. 3-5 Table 4.3.2-1. CP Initial Setup Tasks .............................................................. 4-5 Table 4.3.3-1. Required Supplies for CP Setup .............................................. 4-6 Table 5.3.2-1. Setup Procedures of BCT TAC CP (Modified BN CP) ............. 5-4 Table 5.5.2-1. Setup Procedures of BCT Main CP .......................................... 5-6 Table 5.10.4-1. Data Transfer between Main CP and TAC CP ..................... 5-11 Table 5.10.5-1. Establish CP ATQH .............................................................. 5-11 Table 5.12.5-1. Parts of the COP .................................................................. 5-17 Table 5.12.6-1. AO Information ..................................................................... 5-18 Table 5.12.8-1. Information Comprising and Contributing to COP ................ 5-20 Table 5.13.2-1. Status of Task Steps and Performance Measures ............... 5-30 Table 6.2-1. Daily Duties .............................................................................. 6-1 Table 7.2.2-1. Model/Steps with Timeline and Corresponding Phase ............. 7-5 Table 7.4.6-1. DSE Tasks ............................................................................. 7-12

LIST OF FIGURES

Figure 2.3.1-1. The Mission Command System .............................................. 2-4 Figure 3.1.3-1. BCT Main Command Post (Isometric View) ............................ 3-2 Figure 3.3.3-1. Brigade Combat Team (BCT) Main CP Topdown View ........ 3-7 Figure 3.3.3-2. BCT Main CP - Power Disbribution and Grounding ................ 3-8 Figure 3.3.3-3. BCT Main CP – SIPR/NIPR Network and CPCS Cable Distribution ........................................................................................................ 3-9 Figure 3.3.3-4. BCT Main CP - Current Operations Cell Modified Table of Organization and Equipment (MTOE) Position ................................................ 3-10 Figure 3.3.3-5. BCT Main CP - Current Operations Cell Power Distribution and Grounding ........................................................................................................ 3-11 Figure 3.3.3-6. BCT Main CP - Current Operations Cell SIPR/NIPR Network and CPCS Cable Distribution .......................................................................... 3-12 Figure 3.3.3-7. BCT Main CP – NETOPS Cell - MTOE Position ................... 3-13 Figure 3.3.3-8. BCT Main CP – NETOPS Cell Power Distribution and Grounding ........................................................................................................ 3-14 Figure 3.3.3-9. BCT Main CP – NETOPS Cell - SIPR/NIPR Network and CPCS Cable Distribution ............................................................................................ 3-15 Figure 3.3.3-10. BCT Main CP – Fires/Protection Cell - MTOE Position ....... 3-16 Figure 3.3.3-11. BCT Main CP – Fires/Protection Cell Power Distribution and Grounding ........................................................................................................ 3-17 Figure 3.3.3-12. BCT Main CP – Fires/Protection Cell SIPR/NIPR Network and CPCS Cable Distribution ................................................................................. 3-18 Figure 3.3.3-13. BCT Main CP – ADAM Cell - MTOE Position ..................... 3-19 Figure 3.3.3-14. BCT Main CP – ADAM Cell - Power Distribution ................ 3-20

iv

Figure 3.3.3-15. BCT Main CP – ADAM Cell - SIPR/NIPR Network and CPCS Cable Distribution ............................................................................................ 3-21 Figure 3.3.3-16. BCT Main CP - INTEL Cell - MTOE Position .................... 3-22 Figure 3.3.3-17. BCT Main CP - INTEL Cell - Power Distribution and Grounding ........................................................................................................ 3-23 Figure 3.3.3-18. BCT Main CP - INTEL Cell - SIPR/NIPR Network and CPCS Cable Distribution ............................................................................................ 3-24 Figure 3.3.3-19. BCT Main CP - Mvmt/Mvr Protection Cell MTOE Position ....... Figure 3.3.3-20. BCT Main CP - Mvmt/Mvr Protection Cell Power Distribution and Grounding ................................................................................................. 3-26 Figure 3.3.3-21. BCT Main CP - Mvmt/Mvr Protection Cell SIPR/NIPR Network and CPCS Cable Distribution ............................................................ 3-27 Figure 3.3.3-22. BCT Main CP - Sustainment Cell - MTOE Position ............. 3-28 Figure 3.3.3-23. BCT Main CP - Sustainment Cell Power Distribution and Grounding ........................................................................................................ 3-29 Figure 3.3.3-24. BCT Main CP - Sustainment Cell SIPR/NIPR Network and CPCS Cable Distribution ................................................................................. 3-30 Figure 3.3.3-25. BCT Main CP - PLANS Cell - MTOE Position................. 3-31 Figure 3.3.3-26. BCT Main CP - PLANS Cell - Power Distribution and Grounding ........................................................................................................ 3-32 Figure 3.3.3-27. BCT Main CP - PLANS Cell - SIPR/NIPR Network and CPCS Cable Distribution ................................................................................. 3-33 Figure 3.3.3-28. BCT TAC CP - MTOE Position ........................................... 3-34 Figure 3.3.3-29. BCT TAC CP - - Power Distribution and Grounding ............ 3-35 Figure 3.3.3-30. BCT TAC CP - - SIPR/NIPR Network and CPCS Cable Distribution ...................................................................................................... 3-36 Figure 3.3.3-31. BCT TAC CP - OPS-1 Cell - MTOE Position .................. 3-37 Figure 3.3.3-32. BCT TAC CP - OPS-1 Cell - Power Distribution and Grounding ........................................................................................................ 3-38 Figure 3.3.3-33. BCT TAC CP - OPS-1 Cell - SIPR/NIPR Network and CPCS Cable Distribution ................................................................................. 3-39 Figure 3.3.3-34. BCT TAC CP - OPS-2 Cell - MTOE Position .................. 3-40 Figure 3.3.3-35. BCT TAC CP - OPS-2 Cell - - Power Distribution and Grounding ........................................................................................................ 3-41 Figure 3.3.3-36. BCT TAC CP - OPS-2 Cell - - SIPR/NIPR Network and CPCS Cable Distribution ................................................................................. 3-42 Figure 3.3.3-37. BCT MVR BN Armor BCT / Infantry BCT (ABCT/IBCT) CP - MTOE Position ................................................................................................ 3-43 Figure 3.3.3-38. BCT MVR BN (ABCT-IBCT) CP - Power Distribution and Grounding ........................................................................................................ 3-44 Figure 3.3.3-39. BCT MVR BN (ABCT-IBCT) CP - SIPR/NIPR Network and CPCS Cable Distribution ................................................................................. 3-45 Figure 3.3.3-40. BCT MVR BN (ABCT-IBCT) CP – CUROPS - MTOE Position ........................................................................................................................ 3-46

v

Figure 3.3.3-41. BCT MVR BN (ABCT-IBCT) CP – CUROPS - Power Distribution and Grounding .............................................................................. 3-47 Figure 3.3.3-42. BCT MVR BN (ABCT-IBCT) CP – CUROPS - SIPR/NIPR Network and CPCS Cable Distribution ............................................................ 3-48 Figure 3.3.3-43. BCT MVR BN (ABCT-IBCT) CP – Sustainment - MTOE Position............................................................................................................ 3-49 Figure 3.3.3-44. BCT MVR BN (ABCT-IBCT) CP – Sustainment - Power Distribution and Grounding .............................................................................. 3-50 Figure 3.3.3-45. BCT MVR BN (ABCT-IBCT) CP – Sustainment - SIPR/NIPR Network and CPCS Cable Distribution ............................................................ 3-51 Figure 3.3.3-46. BCT SPT BN CP - MTOE Position ...................................... 3-52 Figure 3.3.3 47. BCT SPT BN CP - Power Distribution and Grounding ............... ........................................................................................................................ 3-53 Figure 3.3.3 48. BCT SPT BN CP - SIPR/NIPR Network and CPCS Cable Distribution ...................................................................................................... 3-54 Figure 3.3.3-49. BCT SPT BN CP - CUROPS - MTOE Position ................. 3-55 Figure 3.3.3-50. BCT SPT BN CP - CUROPS - Power Distribution and Grounding ........................................................................................................ 3-56 Figure 3.3.3-51. BCT SPT BN CP - CUROPS - SIPR/NIPR Network and CPCS Cable Distribution ................................................................................. 3-57 Figure 3.3.3-52. BCT SPT BN CP – SPT OPS - MTOE Position ................ 3-58 Figure 3.3.3-53. BCT SPT BN CP – SPT OPS - Power Distribution and Grounding ........................................................................................................ 3-59 Figure 3.3.3-54. BCT SPT BN CP – SPT OPS - SIPR/NIPR Network and CPCS Cable Distribution ................................................................................. 3-60 Figure 3.3.3-55. BCT SPT BN CP – Sustainment - MTOE Position ............ 3-61 Figure 3.3.3-56. BCT SPT BN CP – Sustainment - Power Distribution and Grounding ........................................................................................................ 3-62 Figure 3.3.3-57. BCT SPT BN CP – Sustainment - SIPR/NIPR Network and CPCS Cable Distribution ................................................................................. 3-63 Figure 3.4.2-1. M100 Pigtail Connection to TQG .......................................... 3-68 Figure 3.4.2-2. M100 Conntections ............................................................... 3-69 Figure 3.4.2-3. M40 Connections .................................................................. 3-70 Figure 3.5.1-1 Example of CNR Employment .............................................. 3-76 Figure 3.7.3-1. Network Operations .............................................................. 3-81 Figure 3.7.6-1. BCT Hierarchy ...................................................................... 3-87 Figure 3.7.7-1. Current NetOps Capability .................................................... 3-88 Figure 3.7.11-1. Controlling Bandwidth ......................................................... 3-92 Figure 3.7.13-1. NetViz Diagram ................................................................... 3-95 Figure 4.1.3-1. Division Main Command Post ................................................. 4-2 Figure 4.3.3-1. DIV Main CP – Power Distribution .......................................... 4-7 Figure 4.3.3-2. DIV Main CP – Power Distribution and Grounding .................. 4-8 Figure 4.3.3-3. DIV Main CP – SIPR/NIPR ..................................................... 4-9 Figure 4.3.3-4. DIV Main CP – Current Operations Cell – Modified Table .... 4-10 Figure 4.3.3-5. DIV Main CP – Current Operations Cell ................................ 4-11 Figure 4.3.3-6. DIV Main CP – Current Operations Cell – SIPR/NIPR .......... 4-12

vi

Figure 4.3.3-7. DIV Main CP – Movement and Maneuver/Special Staff Cell ........................................................................................................................ 4-13 Figure 4.3.3-8. DIV Main CP – Movement and Maneuver / Special Staff Cell ...... ........................................................................................................................ 4-14 Figure 4.3.3-9. DIV Main CP – Movement and Maneuver / Special Staff Cell ...... ........................................................................................................................ 4-15 Figure 4.3.3-10. DIV Main CP – Fire Support / Protection Cell MTOE Position ........................................................................................................................ 4-16 Figure 4.3.3-11. DIV Main CP – Fire Support / Protection Cell ..................... 4-17 Figure 4.3.3-12. DIV Main CP – Fire Support / Protection Cell ..................... 4-18 Figure 4.3.3-13. DIV Main CP – ADAM Cell - MTOE Position ....................... 4-19 Figure 4.3.3-14. DIV Main CP – FUOPS / Plans Cell - MTOE Position ......... 4-20 Figure 4.3.3-15. DIV Main CP – FUOPS / Plans Cell .................................... 4-21 Figure 4.3.3-16. DIV Main CP – FUOPS / Plans Cell .................................... 4-22 Figure 4.3.3-17. DIV Main CP – Sustainment Cell - MTOE Position ............. 4-23 Figure 4.3.3-18. DIV Main CP – Sustainment Cell ........................................ 4-24 Figure 4.3.3-19. DIV Main CP – Sustainment Cell - SIPR/NIPR Network ..... 4-25 Figure 4.3.3-20. DIV Main CP – HRA/SJA Cell – MTOE Position ................. 4-26 Figure 4.3.3-21. DIV Main CP – HRA/SJA Cell – Power Distribution ............ 4-27 Figure 4.3.3-22. DIV Main CP – HRA/SJA Cell – SIPR/NIPR Network ......... 4-28 Figure 4.3.3-23. DIV Main CP – Mvmt & Mvr Cell – MTOE Position ............. 4-29 Figure 4.3.3-24. DIV Main CP – Mvmt & Mvr Cell – Power Distribution ........ 4-30 Figure 4.3.3-25. DIV Main CP – Mvmt & Mvr Cell – – SIPR/NIPR Network .. 4-31 Figure 4.3.3-26. DIV Main CP – CMD Group Cell – MTOE Position ............. 4-32 Figure 4.3.3-27. DIV Main CP – CMD Group Cell – Power Distribution ........ 4-33 Figure 4.3.3-28. DIV Main CP – CMD Group Cell – SIPR/NIPR Network ..... 4-34 Figure 4.3.3-29. DIV Main CP – Entry Cell – MTOE Position ........................ 4-35 Figure 4.3.3-30. DIV Main CP – Entry Cell – Power Distribution ................... 4-36 Figure 4.3.3-31. DIV Main CP – Entry Cell – SIPR/NIPR Network and ......... 4-37 Figure 4.3.3-32. DIV Main CP – NETOPS-1 G6 HQ Cell – MTOE Position .. 4-38 Figure 4.3.3-33. DIV Main CP – NETOPS-1 G6 HQ Cell .............................. 4-39 Figure 4.3.3-34. DIV Main CP – NETOPS-1 G6 HQ Cell .............................. 4-40 Figure 4.3.3-35. DIV Main CP – NETOPS-2 – MTOE Position ..................... 4-41 Figure 4.3.3-36. DIV Main CP – NETOPS-2 – Power Distribution ................ 4-42 Figure 4.3.3-37. DIV Main CP – NETOPS-2 – SIPR/NIPR Network ............. 4-43 Figure 4.3.3-38. DIV Main CP – INTEL-1/ACP – MTOE Position .................. 4-44 Figure 4.3.3-39. DIV Main CP – INTEL-1/ACP – Power Distribution ............. 4-45 Figure 4.3.3-40. DIV Main CP – INTEL-1/ACP – SIPR/NIPR Network .......... 4-46 Figure 4.3.3-41. DIV Main CP – INTEL-2 – MTOE Position .......................... 4-47 Figure 4.3.3-42. DIV Main CP – INTEL-2 – Power Distribution ..................... 4-48 Figure 4.3.3-43. DIV Main CP – INTEL-2 – SIPR/NIPR Network .................. 4-49 Figure 4.3.3-44. DIV Main CP – DTSS VAN Cell – MTOE Position .............. 4-50 Figure 4.3.3-45. DIV Main CP – INTEL-3/SCIF – MTOE Position ................. 4-51 Figure 4.3.3-46. DIV Main CP – INTEL-3/SCIF – Power Distribution ............ 4-52 Figure 4.3.3-47. DIV Main CP – INTEL-3/SCIF – SIPR/NIPR Network ......... 4-53

vii

Figure 4.3.3-48. DIV TAC CP - Topdown View ............................................. 4-54 Figure 4.3.3-49. DIV TAC CP – Power Distribution and Grounding .............. 4-55 Figure 4.3.3-50. DIV TAC CP - SIPR/NIPR Network and .............................. 4-56 Figure 4.3.3-51. DIV TAC CP - Current Operations Cell - MTOE Position .... 4-57 Figure 4.3.3-52. DIV TAC CP - Current Operations Cell ............................... 4-58 Figure 4.3.3-53. DIV TAC CP - Current Operations Cell ............................... 4-59 Figure 4.3.3-54. DIV TAC CP - Intelligence / SCIF Cell .............................. 4-60 Figure 4.3.3-55. DIV TAC CP - Intelligence / SCIF Cell - - .......................... 4-61 Figure 4.3.3-56. DIV TAC CP - Intelligence / SCIF Cell – ........................... 4-62 Figure 4.3.3-57. DIV TAC CP - Network Operations Cell .............................. 4-63 Figure 4.3.3-58. DIV TAC CP - Network Operations Cell .............................. 4-64 Figure 4.3.3-59. DIV TAC CP - Network Operations Cell .............................. 4-65 Figure 4.3.3-60. DIV Headquarters and Headquarters Battalion (HHB) ........ 4-66 Figure 4.3.3-61. HHB CP - Power Distribution and Grounding ...................... 4-67 Figure 4.3.3-62. HHB CP - SIPR/NIPR Network and .................................... 4-68 Figure 4.3.3-63. DIV HHB CP - Current Operations Cell ............................... 4-69 Figure 4.3.3-64. DIV HHB CP - Current Operations Cell ............................... 4-70 Figure 4.3.3-65. DIV HHB CP - Current Operations Cell ............................... 4-71 Figure 4.3.3-66. Div HHB CP - Sustainment Cell - MTOE Positions ........... 4-72 Figure 4.3.3-67. DIV HHB CP - Sustainment Cell ....................................... 4-73 Figure 4.3.3-68. DIV HHB CP - Sustainment Cell - SIPR/NIPR Network .... 4-74 Figure 4.4.2-1. M100 Pigtail Connection to TQG .......................................... 4-79 Figure 4.4.2-2. M100 Connections ................................................................ 4-80 Figure 4.4.2-3. M40 Connections .................................................................. 4-80 Figure 4.5.5-1. CNR Deployment Example ................................................... 4-88 Figure 4.7.3-1. Network Operations .............................................................. 4-91 Figure 4.7.7-1. BCT Hierarchy ...................................................................... 4-99 Figure 4.7.8-1. Current NetOps Capability .................................................. 4-102 Figure 4.7.12-1. Controlling Bandwidth ....................................................... 4-105 Figure 4.7.14-1. NetViz Diagram ................................................................. 4-107 Figure 5.2.1-1. Conduct Command Post Operations ...................................... 5-2 Figure 5.3.1-1. Steps 1 through 5 of TAC CP (BN CP) Setup ......................... 5-3 Figure 5.3.2-1. Steps 6 through 7 of TAC CP (BN CP) Setup ......................... 5-4 Figure 5.12.1-1. COP .................................................................................... 5-15 Figure 5.13.1-1. Battle Drill Flowchart ........................................................... 5-29 Figure 7.2.2-1. Phase V Unit Set Fielding and Reset ...................................... 7-6 Figure 7.3.4-1. Typical Sequencing of MCSI ................................................... 7-8 Figure 8.2.7-1. SIF Login Page ....................................................................... 8-5

viii

This page intentionally left blank.

Chapter 1 Introduction

This page intentionally left blank.

1-1

Chapter 1.0: Introduction

1.1 The Vice Chief of Staff Army provided guidance advising Program Executive Officer Command, Control, Communications Tactical (PEO C3T) to standardize Command Post variants at each echelon. Lack of a standard set of processes and procedures to develop, field, setup and operate a Command Post have led to a proliferation of many effective, but different unit developed methodologies. Differences in approaches have led to unnecessary complexity in training, operations, and sustainment.

1.2 The intended audience for this book is commanders and staff who will set up, operate, and maintain CPs at the Brigade and Battalion, as well as those who train them. This guide is not intended to replace or supersede existing doctrine. It was designed to provide additional techniques, procedures, and best practices; most of which were developed during the PEO-C3T TOCFEST 2008 and numerous iterations of Mission Command System Integration (MCSI). CP stakeholders will expand this handbook to include other CP variants with input from the user and materiel developer communities. Future CP Handbooks will include all components of the mission command system, including those external to PEO-C3T.

1.3 The doctrinal references that support this guide can be found online at The Army Training Network (ATN) and the Department of the Army Publications and Forms website listed below. https://atn.army.mil

http://armypubs.army.mil/index.html

1-2

This page intentionally left blank.

Chapter 2 Mission Command

This page intentionally left blank.

2-1

Chapter 2.0 Mission Command (MC)

2.1 Mission Command Defined MC as defined in ADP 6-0, is “the exercise of authority and direction by the commander using mission orders to enable disciplined initiative within the commander’s intent to empower agile and adaptive leaders in the conduct of unified land operations”.

2.1.1 The Army’s philosophy of command is mission command. It describes the Army’s ideology of how commanders lead forces to accomplish missions. The fundamental principles of mission command assist commanders and staff in balancing the art of command with the science of control.

2.1.2 Effective commanders understand that their leadership guides the development of teams and helps to establish mutual trust and shared understanding throughout the force. Commanders allocate resources and provide a clear intent that guides subordinates’ actions while promoting freedom of action and initiative. Subordinates, by understanding the commander’s intent and the overall common objective, are then able to adapt to rapidly changing situations and exploit fleeting opportunities. When given sufficient latitude, they can accomplish assigned tasks in a manner that fits the situation. Subordinates understand that they have an obligation to act and synchronize their actions with the rest of the force. Likewise, commanders influence the situation and provide direction, guidance, and resources while synchronizing operations. They encourage subordinates to take bold action, and they accept prudent risks to create opportunity and to seize the initiative.

2.1.3 The exercise of mission command is based on mutual trust, shared understanding, and purpose. Commanders understand that some decisions must be made quickly at the point of action. Therefore, they concentrate on the objectives of an operation, not how to achieve it. Commanders provide subordinates with their intent, the purpose of the operation, the key tasks, the desired end state, and resources. Subordinates then exercise disciplined initiative to respond to unanticipated problems. Every Soldier must be prepared to assume responsibility, maintain

2-2

unity of effort, take prudent action, and act resourcefully within the commander’s intent.

2.1.4 The principles of mission command are:

• Build cohesive teams through mutual trust • Create shared understanding • Provide a clear commander’s intent • Exercise disciplined initiative • Use mission orders • Accept prudent risk

2.1.5 Within the unit, the commander exercises the art of command, the creative and skillful exercise of authority through timely decision making and leadership. The commander is aided by the staff, which exercises the science of control, the systems and procedures used to improve the commander’s understanding and support accomplishing the mission in accordance with the commander’s intent. Staffs coordinate, synchronize, and integrate actions; inform the commander; and exercise control for the commander.

2.2 Mission Command Warfighting Function

2.2.1 As defined in Army Doctrine Publication (ADP) 3-0, a warfighting function (WfF) is “a group of tasks and systems (people, organizations, information, and processes) united by a common purpose that commanders use to accomplish missions. Within the Army, they are: Mission Command, Movement and Maneuver, Intelligence, Fires, Sustainment, and Protection.

2.2.2 As defined in ADP 6-0, the mission command warfighting function is “the related tasks and systems that develop and integrate those activities enabling the commander to balance the art of command and the science of control in order to integrate the other WfFs”. Commanders use the mission command WfF to integrate the other WfFs into a coherent whole to mass the effects of combat power at the decisive place and time:

2-3

• Driving the operations process through their activities of understanding, visualizing, describing, directing, leading, and assessing operations.

• Developing teams, both within their organizations and with joint, interagency, and multinational partners.

• Informing and influencing audiences, inside and outside their organizations.

2.2.3 The staff supports the commander in the exercise of mission command by performing their primary staff tasks:

• Conduct the operations process: plan, prepare, execute, ands assess.

• Conduct knowledge management and information management.

• Conduct, inform and influence activities. • Conduct cyber electromagnetic activities.

2.2.4 To allow the commander and staff to perform these functions, the commander establishes a mission command system.

2.3 The Mission Command System (MCS)

2.3.1 The MCS, as defined in ADP 6-0, is “the arrangement of personnel, networks, information systems, processes and procedures, and facilities and equipment that enable commanders to conduct operations”.

2-4

2.3.2 Commanders organize their mission command system to support decision making and facilitate communication.

2.3.3 Personnel. A commander’s mission command system begins with people. Therefore, commanders base their mission command system on human characteristics and abilities more than on equipment and procedures. An effective mission command system requires trained personnel; commanders must not underestimate the importance of providing training. Key personnel dedicated to mission command include seconds in command, command sergeants major, and staff.

2.3.4 Networks. Social and technical networks enable commanders to communicate information and control forces, leading to successful operations. Generally, a network is a grouping of people or things interconnected for a purpose. Commanders develop and leverage various social networks - individuals and organizations interconnected by a common Interest - to exchange information and ideas, build teams, and promote unity of effort. Technical networks also connect people and allow sharing of resources and information. For example, LandWarNet (the Army’s portion of the Global Information Grid) is a technical network. It encompasses all Army information management systems and information systems that collect, process, store, display, disseminate, and protect information worldwide.

Figure 2.3.1-1. The Mission Command System

2-5

2.3.5 Information Systems (INFOSYS). Commanders determine their information requirements and focus their staffs and organizations on using information systems to meet these requirements. An information system consists of equipment that collects, processes, stores, displays, and disseminates information. This includes computers - hardware and software - and communications, as well as policies and procedures for their use. Staffs use information systems to process, store, and disseminate information according to the commander's priorities. These capabilities relieve the staff of handling routine data. Information systems—especially when merged into a single, integrated network—enable extensive information sharing.

2.3.6 Processes and Procedures. Processes and procedures help commanders organize the activities within the headquarters and throughout the force. Processes and procedures govern actions within a mission command system to make it more effective and efficient. A process is a series of actions directed to an end state. One example is the military decision making process. Procedures are standard, detailed steps, often used by staffs, which describe how to perform specific tasks to achieve the desired end state. One example is a standard operating procedure. Adhering to processes and procedures minimizes confusion, misunderstanding, and hesitation as commanders make frequent, rapid decisions to meet operational requirements.

2.3.7 Facilities and Equipment. Facilities and equipment include command posts, signal nodes, and all mission command support equipment, excluding information systems. A facility is a structure or location that provides a work environment and shelter for the personnel within the mission command system. Facilities range from a command post composed of vehicles and tentage to hardened buildings. Examples of equipment needed to sustain a mission command system include vehicles, generators, and lighting.

2-6

2.4 INFOSYS and Support to Mission Command

2.4.1 Background

2.4.1.1 The inventory of INFOSYS is dependent upon the type of unit and its primary mission. Three standardized BCT designs exist in the Army: Armored (ABCT), Infantry (IBCT), and Stryker (SBCT). Five other types of brigades support or complement the three combat brigades: battlefield surveillance, fires, combat aviation, maneuver enhancement, and sustainment.

2.4.1.2 INFOSYS, intelligence, surveillance, reconnaissance, and human intelligence within the modular design coupled with a network of organizations linked together by technology have enabled precision effects against the most sought-after enemies. These networks provide the ability to pass information and intelligence quickly across the battlefield, significantly decreasing the response time from target detection to target destruction.

2.4.2 INFOSYS Architecture and Interoperability

INFOSYS at each echelon (commanders at the theater or joint task force level to the individual Soldier or weapons platform) integrate. Whether a force deploys for land combat, peacetime operations, or humanitarian or civil authority assistance, INFOSYS support the commander by integrating operational environment automation systems and communications to link strategic and tactical headquarters. The Army’s inventory of INFOSYS is interoperable with joint and multinational INFOSYS across the full range of INFOSYS functionality. Reference figure 2.3.1-1.

2.4.3 Battle Command Common Services (BCCS) servers suite

The BCCS servers suite provides INFOSYS interoperability services, information services infrastructure, and tactical enterprise services to CPs at multiple echelons in order to provide collaboration servers, databases, file servers, website, and email; as well as support in expanding the array of INFOSYS and networks operating in either a stand-alone configuration or as part of the Department of Defense Global Information Grid. The suite utilizes virtual machines to provide the services.

2-7

We generally talk about this suite in three parts:

1. The Mission Command Interoperability components (i.e. BC Server, Command Post of the Future (CPOF) Servers, Publish and Subscriber Service / Data Dissemination Service (PASS/DDS), Command and Control Registry (C2R) etc).

• C2R provides a common means to manage addressing information that allows the user to determine the unit reference number, Internet protocol (IP) address, host name, and other addresses of a particular unit or platform.

• DDS provides data distribution services both outside and inside the CP. INFOSYS advertise data and clients needing data related to that subject subscribe.

• CPOF Mid Tier Server provides the local caching of data for CPOF clients at the brigade echelon.

• Alerts provide the infrastructure and application program interfaces to allow applications to send and receive alert type messages.

• Military messaging supports state management, own position, and security architecture/IP to Extensible Markup Language (XML) translation.

2. The Tactical Enterprise Services (i.e. Active Directory, Email, Portal, etc).

• Microsoft Active Directory provides network services including Lightweight Directory Access Protocol-like directory services, Kerberos-based authentication, Domain Name System- based naming, and other network information. Active directory allows administrators to assign policy, deploy software, and apply critical updates.

• Microsoft Exchange Server is a messaging and collaborative software product for email.

• The Microsoft SharePoint Server offers a browser-based collaboration and documentation platform. It can be used to host websites that access shared workspaces and documents, as well as specialized applications like wikis and blogs.

2-8

3. The Information Services Infrastructure (i.e. hardware, virtualization, storage, disaster recovery/COOP, etc)

• Disaster Recovery Solutions utilizing high-availability and backup capabilities inherent in the virtualization and storage technologies will provide for the protection of critical data and services.

• State management provides a means for INFOSYS to ensure receipt of current information regarding orders, warning orders, fragmentary orders, and unit task reorganization.

• Security architecture over IP XML translation provides the capability to publish real-time friendly force position data to the PASS/DDS by listening for VMF messages.

• Security architecture over IP XML translation provides the capability to publish real-time friendly force position data to the PASS/DDS by listening for VMF messages on the security architecture multicast groups and translating them into the appropriate XML format.

• Time synchronization provides a common time reference for clients.

• Own position supplies the position from an attached Precision Lightweight Global Positioning System Receiver via a Variable Message Format (VMF) sent to a security architecture multicast group.

2.4.4 Advanced Field Artillery Tactical Data System (AFATDS)

AFATDS is an integrated fire support system that processes fire missions and other related information to coordinate and maximize the use of all fire support assets (mortars, field artillery, attack helicopters, air support, naval gunfire, and offensive electronic warfare). AFATDS is found in command posts battalion through ASCC that have a Fires Cell. AFATDS:

• Manages critical resources; supports personnel assignment; collects and passes intelligence information; and controls supply, maintenance, and other logistic functions. These tasks are fire WfF related only.

• Processes fire mission requests and gives the commander a planning tool for proposed and planned targets.

• Provides information to DCGS–A to create priority intelligence requirements for the commander’s approval.

2-9

• Publishes position reports and graphics to the PASS/DDS that other INFOSYS can then subscribe to. These tasks are fire WfF related only.

2.4.5 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS is a joint and combined warfighting application that provides precision strike and C2 capabilities. Although JADOCS may be loaded on unit provided computers at brigade, the Fires COE has directed that JADOCS not be issued below division level. JADOCS:

• Provides warfighters with a combination of tools, services, and mission managers to bridge capability gaps identified by combatant commanders and service components.

• Provides capabilities for rapid SoS integration, visualization, coordination, and de-confliction of critical mission information.

2.4.6 Air and Missile Defense Workstation (AMDWS)

AMDWS is responsible for managing air defense missions and provides the ability to electronically generate and display weapon and sensor locations, manipulate map graphics, conduct terrain analysis, and analyze and monitor missions in near-real time. AMDWS is found in command posts brigade through ASCC that have an ADAM Cell. AMDWS:

• Allows the operator to notify other WfFs of potential enemy air strikes and TBM launch point and impact.

• Displays real time air tracks, air control orders, current fire unit status, alert posture, missile expenditure, and personnel ready for duty for air battle management.

• Conducts air defense planning and analysis to develop Air Defense Artillery (ADA) missions and determines sensor-to-shooter early warning/cueing.

• Displays the air picture (rotary wing, fixed wing, UAS, sensor/shooter locations [the “umbrella”], and TBM/ABM) alerts on the COP.

• Enhances collaborative planning through threat corridor displays, play back capability, and ADA plans and estimates.

2-10

2.4.7 Aviation Mission Planning System (AMPS)

AMPS provides an interface bridge between select rotary-wing aircraft and INFOSYS at brigade and battalion. AMPS is found in command posts brigade through ASCC, as well as aviation battalions. AMPS:

• Bridges between AH-64C/D, OH-58D, CH-47D, UH-60A, UH-60Q, and RAH-66 and INFOSYS.

• Automates mission planning and distribution of mission files between units.

• Provides mission data loading into the aircraft for navigation, communications, weapons, and post mission information.

• Utilizes a menu-driven user interface that includes a combination of both tabular and mapping overlay data entry that allows the mission planner to develop a mission efficiently.

• Provides access to the most current situation data, which is transferred to the aircraft by the Data Transfer System.

2.4.8 Tactical Airspace Integration System (TAIS)

TAIS takes the input provided through various radar and data communication links and displays two-dimensional and three-dimensional, near-real-time views of the operational environment. TAIS is found in command posts brigade through ASCC that have ADAM and aviation sections. TAIS operators are able to organize current and planned airspace usage and provide this information to the brigade commander and staff. The advanced visualization provides a complete picture of both the air

2.4.9 Battle Command Sustainment Support System (BCS3)

BCS3 enables warfighters to target, access, scale, and tailor critical logistic information in near real time. BCS3 is found in command posts battalion through ASCC that have a Sustainment Cell. At battalion level, the BCS3 is found in the Forward Support Company (FSC) supporting the battalion from the BSB. BCS3:

• Provides a more effective and efficient means to gather and integrate assets and in-transit information to manage distribution and deployment missions.

2-11

• Pulls logistical data from a variety of sources with primary emphasis on position, location, information of logistical vehicles, radio frequency identification tagged commodities, and supply-support activities. BCS3 does receive limited personnel feeds and can get information on medical classes of supply (e.g., blood).

• Facilitates quicker, more accurate decision making by providing a more effective means for the brigade to determine the sustainability and supportability of current and planned operations.

2.4.10 Combined Information Data Network Exchange (CIDNE)

CIDNE is a web-based tool that provides forces with a unified event reporting system for operations and intelligence information. CIDNE is found in command posts battalion through ASCC that have an Intelligence Cell. CIDNE:

• Enters, correlates, aggregates, and manages significant activities and events throughout the area of operations through a user-definable and customizable workflow model.

• Provides tactical-level reporting flexibility while simultaneously maintaining the force-level data standardization necessary for analysts to perform theater-wide analysis and trend reports.

• Provides the ability for commanders at all levels to see rollups of significant activities within their specific Areas of Responsibility (AORs) and “drill into” the underlying data across multiple AORs.

2.4.11 Mission Command Workstation

2.4.11.1 Team members working on TMC/CPOF share workspaces and collaborate to create a rich, multi-perspective, operational picture.

2.4.11.2 CPOF is a decision support system that provides Situational Awareness (SA) and collaborative tools for tactical decision making, planning, and rehearsal and execution management from battalion through Army Service Component Command (ASCC) level. The TMC Workstation is found in command posts battalion through ASCC and is in multiple cells based on unit MTOE. CPOF:

2-12

• Provides a collaborative operating environment using Voice over Internet Protocol (VoIP), Graphical User Interface, and enhanced briefing capabilities.

• Allows battalion level and above commanders to feed real-time SA into the system and have that information immediately available to fellow commanders and operations officers.

• Allows operators to visualize the commander’s intent and COP and manipulate tactical data in a collaborative manner.

• Supports parallel, synchronous, asynchronous, and cross-functional planning and execution.

2.4.12 Distributed Common Ground System–Army (DCGS-A)

2.4.12.1 DCGS-A, as an information system, provides a net-centric Information Collection (IC), weather, geospatial engineering, and space operations capability to maneuver, maneuver support, and maneuver sustainment support organizations from company-level intelligence support team to ASCC. DCGS-A is the IC component of the modular and future force and the Army’s primary system for IC tasking of sensors, processing of data, exploitation of data, and dissemination of intelligence information about the threat, weather, and terrain at all echelons. DCGS-A is found in command posts battalion through ASCC that have an Intelligence Cell.

2.4.12.2 DCGS-A consolidates and/or replaces the capabilities found in these Programs of Record (POR) systems: all versions of the All Source Analysis System, the Division Tactical Exploitation System, all versions of the Digital Topographic Support System (DTSS), the Counterintelligence and Intelligence Operations Work Station, PROPHET Control, the Common Ground Station, and the Integrated Meteorological System (IMETS). DCGS-A integrates direct data receipt and processing capabilities of Army UAS and select DCGS baseline sensors. Through incremental enhancements, DCGS-A will also replace the Space Operations System, the Space Support Enhancement Toolset, the Guardrail Ground Baseline, the TES-Forward, and the Enhanced Trackwolf.

2-13

2.4.13 Force XXI, Battle Command–Brigade and Below/Blue Force Tracking/Joint Capabilities Release (FBCB2/BFT/JCR).

FBCB2/BFT/JCR manages SA and Situational Understanding (SU) down to the individual platform level. Each platform using BFT is equipped with a Ground Positioning Satellite (GPS) receiver and L-Band transponder for Satellite Communication (SATCOM), giving beyond Line of Sight (LOS) networking. The distribution of systems per platform is based on unit MTOE. The TOC Kit/Operations Box is found in command posts battalion through ASCC and is in multiple cells based on unit MTOE. FBCB2/BFT/JCR:

• Provides units the capability to transmit key combat information in near real-time through formatted digital messages while on the move.

• Supports lower-echelon tactical mission requirements by providing near real time SA for commander, staff, and Soldiers.

• Provides a shared common picture of the operational environment, graphical displays with friendly and enemy unit locations, target identification, logistic support, and communications/electronics interfaces with host platforms.

• Supports the individual’s SA/SU of the relevant aspects of the battlefield.

• Provides a satellite-based SA and messaging capability for CP, vehicular, and selected rotary wing platforms, as well as a parallel data link to the COP and operational/strategic-level MC systems.

• Merges the Army’s FBCB2 and a commercial satellite network to provide a shared view of the operational environment at the tactical, operational, and strategic levels.

2.4.14 Global Command and Control System–Army (GCCS–A)

GCCS-A is the theater and Army component commander’s MC system. The MC Contemporary Operating Environment (COE) has directed that GCCS-A not be issued below division level. GCCS–A:

• Provides the joint friendly and enemy situation. • Supports monitoring, planning, and executing joint,

combined, and Army conventional military operations. • Supports information exchange with numerous joint and

other Army MC systems.

2-14

• Provides the digital link between joint task force and strategic commanders to Army operational and tactical commanders by way of the Joint Global Command and Control System.

2.4.15 Tactical Ground Reporting System (TIGR)

TIGR is an information management system designed for the lowest tactical leaders (patrol and squad leaders) at the company level. It supports small-unit mission planning, rehearsals, execution, Intelligence Preparation of the Battlefield (IPB), and AARs. It can operate disconnected or in a shared, secure, low bandwidth, tactical, network environment. It is a collaborative repository system designed for company and below to store and share combat information. The system is ideal for relief in place or transfer of authority (which may occur daily at the platoon or company level operating in a hybrid or irregular warfare environment). It is a starting point for bottom-up refinement of operational assessments as well a tool to build mission preparation briefs, capture mission execution data, and conduct end of mission briefs and IPB. TIGR is found in command posts battalion through Division, and is also found in company command posts of deployed units.

2.4.15.1 INFOSYS Authorization

The table below shows an example MTOE authorization

Table 2.4.17-1 Example Brigade MC System Authorization

System

Brigade Type

AFA

TDS

DC

GA

–A

BC

S3

TMC

Gat

eway

FBC

B2

TAIS

TMC

Clie

nt

Wor

ksta

tion

AM

PC

S

Armored 22 18 10 7 379 1 48 1 Light 22 17 20 7 268 1 48 1 Stryker 14 23 7 7 763 0 38 1

Fires 42 7 7 6 105 1 33 1 Aviation 7 10 10 6 202 1 38 1 Sustainment 0 2 19 1 21 0 14 1 Battlefield Surveillance 0 4 0 3 82 0 23 1

2-15

2.4.16 INFOSYS Tasks

• Commander: o Provides command guidance for employing INFOSYS. o Provides automation resources. o Establishes automation support priorities. o Specifies the unit’s COP. o Establishes CCIR and ensures requirements are depicted

in ABCS. o Ensures subordinate leaders are trained in the

employment, operation, and sustainment of automation. o Trains subordinate leaders and staff to create, maintain,

distribute, and use the COP. o Establishes network priorities.

• Deputy Commander/Executive Officer: o Coordinates the staff to ensure INFOSYS integration. o Ensures the staff integrates and coordinates INFOSYS

activities internally, vertically (with higher headquarters and subordinate units), and horizontally (with adjacent units).

o Manages and ensures satisfaction of the CCIR. o Directs the creation and distribution of the COP to include

procedures for updating enemy and friendly SA. o Monitors the information filters, collection plans, and

networks that distribute the COP. o Provides guidance for automation support. o Coordinates the staff to ensure automation support. o Coordinates procedures for inter-CP

video-teleconferences and white board sessions. o Supervises the main CP and headquarters cell to include

displacement, protection, security, and communications. o Monitors liaison teams with analog units and joint/allied

forces for their contributions to the COP. • S1:

o Employs Battle Command Sustainment Support System (BCS3) to monitor and report on personnel-related portions of the Commander’s Tracked Item List.

o Monitors Standard Installation/Division Personnel System interface with BCS3.

o Manages the Electronic Military Personnel Office.

2-16

• S2: o Acts as staff proponent for Distributed Common Ground

Station–Army (DCGS–A) and weather effects. o Supervises DCGS–A and Integrated Meteorological

System operations and support. o Provides guidance on employment and support of

DCGS–A and weather effects. o Supervises the information security program and

evaluates security vulnerabilities. o Assists the S6 in implementing and enforcing local area

network (LAN) security policies. o Provides software application expertise on proponent

systems. • S3:

o Acts as staff proponent for TMC Workstation. o Plans, integrates, and employs INFOSYS. o Develops the INFOSYS annexes for plans and orders. o Develops INFOSYS garrison and tactical standing

operating procedures (TACSOP) annexes. o Oversees, informs, and influences cyber/electromagnetic

activities. o Provides operational and support guidance regarding

network employment to subordinate units. o Manages information dissemination. o Creates, maintains, and displays the COP; maintains SU

of all units. o Coordinates with S6/G6 for communications connectivity

in support of INFOSYS. o Plans and monitors operator digital sustainment training. o Provides software application expertise on proponent

systems. o Assigns liaison officers and coordinates their support.

• S4: o Acts as staff proponent for BCS3. o Supervises BCS3 operations and support. o Provides guidance on employment and support of BCS3. o Monitors and reports on the status of all automation

equipment. o Provides software application expertise on proponent

systems.

2-17

• S6:

o Acts as staff proponent for TMC Server Suite. o Serves as signal Subject Matter Expert (SME) to the

commander; advises the commander and staff on all signal support matters.

o Establishes the network. o Monitors Wide Area Network (WAN) performance;

integrates the CP LAN. o Manages automation information systems, automation

and network, and information security. o Ensures consistency and compatibility of transmission

requirements for the tactical situation automation systems.

o Manages the tactical Internet; monitors network employment, network configuration, and network status and reporting.

o Receives planning worksheets with LAN/WAN requirements.

o Ensures information network connectivity between unit and higher/lower echelons.

o Plans, coordinates, and manages network need lines, unit task organization, and base configuration files.

o Plans, coordinates, and manages communication links to include reach-back communications.

o Coordinates with higher echelon signal officers for additional communications support.

o Develops and coordinates the signal digital support plan. o Determines system and retransmission requirements for

the tactical situation. o Coordinates with higher, adjacent, and subordinate units

in developing the signal digital support plan. o Manages the release of INFOSYS software within the

unit. o Provides a focal point for automation support (Help

Desk). o Implements and enforces LAN security policies. o Establishes communications security accountability,

distribution, destruction, and procedures within the unit.

2-18

• FA57 BCO

o Leads staff to plan, develop, execute, and assess digital staff training strategies and INFOSYS integration training.

o Assists brigade combat team (BCT) commander in training subordinate leaders and staff to create, maintain, distribute, and use unit’s network.

o Conducts coordination with S6/G6 for communications connectivity in support of ABCS.

o Coordinates with higher, adjacent, and subordinate units in developing the Knowledge Management (KM) plan.

o Acts as BCT staff proponent for the KM cell. o Monitors operator/system digital training. o Serves as commander’s SME on Training Aids, Devices,

Simulators, and Simulations (TADDS) for digital training to include low-overhead situational drivers.

o Acts as BCT commander’s SME for digital staff integration issues.

o Coordinates INFOSYS activities internally, vertically (with higher headquarters and subordinate units), and horizontally (with adjacent units).

o Supports development of the unit TACSOPs; acts as staff lead for developing unit KM plan.

o Coordinates with higher echelon BCO or KM sections for additional digital automation support.

o Provides guidance for priority work to assigned field service representatives (FSRs). Coordinates for external FSR support when required.

o Participates in BCT operations planning/execution to support developing the CCIR.

• WfF Digital Master Gunner (DMG) The DMG program provides a higher level of system understanding and integration of the MC system. Current DMG courses are: Network DMG, Ft Gordon; Mission Command DMG, Ft Leavenworth; Fires DMG, Ft Sill; Maneuver DMG, Ft Benning; Aviation DMG, Ft Rucker; and Sustainment DMG, Ft Lee.

o Serves as the Operating Force Commander's SME on the operation, maintenance and integration of their specific WfF system into the unit's system of systems network

o Develops and implements a training plan for their specific WfF system to ensure staff, cell or element proficiency

2-19

• System Maintainer:

o Helps the S6 manage the network. o Plans and coordinates the linking of WfFs to the CP. o Supervises, installs, operates, and performs unit level

maintenance on multi-functional/multi-user information processing systems, peripheral equipment, and associated devices in mobile and fixed facilities.

o Performs analyst functions; constructs, edits, and tests computer system programs.

o Performs preliminary tasks necessary for CP LAN initialization.

o Assists in troubleshooting systems. o Conducts data system studies and prepares

documentation and specifications for proposals. o Maintains master copies of software. o Backs up data for user-owned and operated automation

information systems. o Assists in recovery of data at user level. o Operates and performs preventive maintenance checks

and services (PMCS) on assigned vehicles and power generators.

o Monitors WfF PMCS program. o Coordinates repairs with S6 section.

• System Operator: o Installs and operates assigned digital hardware and

software. o Establishes connectivity of assigned WfFs within

LAN/WAN; ensures system interfaces with correct tactical communications.

o Inputs operational data. o Produces reports required by commanders and staff

leaders. o Performs PMCS on assigned WfFs. o Isolates, identifies, and tracks digital system problems. o Maintains continuity of operations. o Maintains portions of the COP, as assigned. o Ensures unit-level information security.

2-20

• Battle Captain/Battle Staff NCO:

o Oversees operations of assigned WfF. o Controls/directs the initialization of the WfF within the CP

LAN (battle staff NCO). o Ensures information flow and necessary coordination

takes place among staff sections and with higher, adjacent, and lower headquarters.

o Accesses and employs information through ABCS in support of operations and planning.

o Ensures key WfF products are available and current in support of the mission.

Chapter 3 Characteristics of the

Mission Command System Battalions and Brigade

This page intentionally left blank.

3-1

Chapter 3.0 Characteristics of the Brigade Command Post (CP)

3.1 Introduction

3.1.1 This chapter breaks down the physical components of the Brigade Command Post (CP) and how they are assembled and/or connected. The diagrams in this chapter depict CPs at the Brigade Combat Team and battalion level per their authorized equipment and personnel by Modification Table of Organization and Equipment (MTOE). The diagrams show the physical layout for each cell and for each aggregate CP. Note the layouts presented show the CP only and do not include support elements that would be co-located. Also, while not all the different types BCT Bn CPs are illustrated in this Handbook most maneuver Bn CPs are the same. Adjust as needed for each type Battalion.

The conventions in this book allow for Chapter 3 (BCT/BN) and Chapter 4 (DIV/Corps/ASCC) to stand alone. This has caused certain elements to be repetitive.

3.1.2 Diagrams for Functional and Multi-Functional Support Brigades are included in an Annex at the end of the Handbook..

3.1.3 This handbook addresses the physical aspect of the Command Post in the context of ADP 6-0’s definition of the mission command system, the arrangement of personnel, networks, information systems, processes and procedures, and facilities and equipment that enable commanders to conduct operations. The focus of this handbook is not on the concept but on the physical aspects of the CP layout. The physical components of a mission command system include:

• Personnel – Warfighting Function (WfF) and Coordinating Cell Locations.

• Networks – Non-Secure Internet Protocol Router (NIPR) (NIPR), Secure Internet Protocol Routing (SIPR), data cable distribution and Combat Net Radios (CNR).

3-2

• Information Systems – Examples include but not limited to TMC Client Work Stations, FBCB2, AFATDS, PBUSE, VSAT, and AHRS.

• Processes and Procedures – Examples are standard operating procedures.

• Facilities – Physical Structures such as Tentage/Buildings.

• Equipment – Examples: Power Generation and Distribution; Large Screen Displays (LSD), Tables, Chairs, Sandbags.

Figure 3.1.3-1. BCT Main Command Post (Isometric View)

3.2 Physical CP Components

3.2.1 Physical Structure. The physical structure of the CP provides work space and the framework for the infrastructure.

3.2.1.1 The physical outdoor layout of the CP is composed of the Army-fielded Trailer-Mounted Support Systems (TMSS), associated CP vehicles, personnel, assigned information systems, Supporting equipment, networks and other related components. While a physical structure can also be an existing building or permanent shelter depending on the unit mission, for the purposes of this Handbook we are looking at the CP when not located in buildings.

3-3

3.2.1.2 The TMSS encompasses a tent shelter, self-powered Environmental Control Unit (ECU), tables, and internal shelter lights. TMSS shelters are fielded in both medium (High-Mobility Multipurpose Wheeled Vehicle [HMMWV] towable) and large Light Medium Tactical Vehicle (LMTV/5-ton towable) shelters. Both sizes are fully compatible with each other and can be rapidly deployed in various configurations to provide well-lit, environmentally-controlled, weather-resistant shelters. The shelters are fielded for a mobile force to deploy anywhere in the world and operate in unimproved environments.

3.2.1.3 The CP vehicles provide information management of the integrated network of communication. They are located within the headquarters sections at each echelon down to the battalion level. With the integrated mission command system it provides commanders with situational understanding.

3.2.1.4 Staff personnel are assigned to warfighting functions according to individual Military Occupational Specialty (MOS) and authorized MTOE position, and are assigned a designated information system according to position. Tent layouts in this handbook designate recommended staff positions within various sections. A specific unit’s MTOE may depend on MOS or assigned information system

3.2.2 Infrastructure. The infrastructure of the CP is depicted with diagrams of power generation and distribution, electrical grounding, fiber distribution, Secure Internet Protocol Routing (SIPR) data cable distribution, Non-Secure Internet Protocol Router (NIPR) data cable distribution, and CP Communication System (CPCS) cable distribution. Each may be tailored to the unit’s needs. Although shown in this handbook with the TMSS, the infrastructure can be adapted to any physical structure.

3.2.3 Information Systems. Information systems of the CP consist of various components that range from individual laptop computers (Advanced Field Artillery Tactical Data System

3-4

[AFATDS], which can be loaded with Joint Automated Deep Operations Coordination System, JADOCS), [Tactical Battle Command - Client Work Stations (TMC-Client WS)] to integrated vehicle platforms (Command Post Platform [CPP], Warfighter Information Network -Tactical [WIN-T], Air Defense Airspace Management [ADAM]). CP vehicle platforms integrate capabilities into mobile and survivable shelters, or trailers that facilitate setup and teardown and improve mobility. Many of the shelters are designed to connect to the CP for easy access, but can also be remoted into buildings. For a description of each of these systems, see section 3.8, Information Systems.

3.2.4 Large Screen Display. The information systems ensure that everyone is working from the same mission command information, but it is also necessary for the staff to be able to plan and execute missions from the same visual picture. A Large Screen Display (LSD) in the Current Operations section is important to display the COP, mission dependent relevant information, video and other system views that are relevant to the mission. The BCT has a total of 4 LSD, 3 for the Main and 1 for the TAC. Some of the drawings show these in different locations as an example, but the totals remain 4. Same for the number of Crew Access Units (CAUs). Be sure to understand how best to use these assets for CP layouts. For more information on the Common Operational Picture (COP) and displaying information in the CP, refer to section 5.12.

3.2.5 Combat Net Radios (CNR) and Intercom System. A key component to the mission command system is voice communications. CNR, or tactical radios, provide voice communications to all echelons on the battlefield. Within the CP, the CPCS provides any staff section with access to these radios and allows for internal intercom system. The Hard “Green Box” CAUs are a limited number but *Soft CAUS) can be downloaded to individual workstations for the same capability. Be sure to understand how best to use these assets for each CP layout. For more information on CNR and the CPCS see section 3.5.

3-5

3.3 Initial CP Setup and Configuration

3.3.1 During the fielding and reset phases, a unit receives individual system training and puts each system into operation independent of the other CP components. To set the CP up as a System of Systems (SoS) for the first time, certain tasks need to be completed to link all of the systems together and various supplies are needed that are not furnished by any of the individual fieldings.

3.3.2 During the initial setup of the CP, a unit should plan to conduct the tasks in Table 3.3.2-1.

Table 3.3.2-1. CPP Initial Setup Tasks

TASK HANDBOOK SECTION Build data wiring bundles for both SIPR and NIPR networks

3.6, Network Cabling

Build power distribution grid 3.4, Power Distribution Customize CPCS coax cable wiring 3.5, Combat Net Radios Configure Combat Net Radios, antennas, and CPCS access units

3.5, Combat Net Radios

Validate data product 3.7, System Architecture Validate network configurations and Connectivity

3.7, Network Operations

3.3.3 During the setup validation of these CPs, various supplies are required. These supplies are not fielded by any program. Some supplies are required and others significantly facilitate the initial setup of a CP. Below is a full list with recommended quantities. The list is also available at the CP Handbook AKO site.

Table 3.3.3-1. Required Supplies for CP Setup

ITEM QUANTITY Step Ladder, 4' 1 per CP

Power strips, 20 amp 5 per TMSS Med; 12 per TMSS Lrg

Extension cords, 50', heavy gauge

1 per TMSS Med; 3 per TMSS Lrg

3-6

ITEM QUANTITY Extension cords, 25', heavy gauge

3 per TMSS Med; 10 per TMSS Lrg

30’ long sheathed grounding cables

2 per TMSS

Safety goggles 1 per SWGS kit and 1 for tent pegs

12 lb sledge hammer 1 per CP

Lens cleaner, projector, kit 1 per CP

D-rings, 3" 15 per TMSS Med; 25 per TMSS Lrg

Fuel cans 6 per TMSS

Field chairs 12 per TMSS Med; 28 per TMSS Lrg

Coax cable, 75 Ohm, RG-59 500 ft

BNC T-Connectors, 75 Ohm 5 per CP

BNC male connector, 75 Ohm, RG-59

20 ea

BNC barrel connectors, female, 75 Ohm

5 per CP

BNC terminators, 75 Ohm 5 per CP

CAT 5e, UTP, box, 1000ft, red (SIPR)

12 boxes

CAT 5e, UTP, box, 1000ft, blue (NIPR)

5 boxes

RJ-45 connectors 1000 ea

TUFF Tables Based on unit SOP

J-Stakes 25 ea TMSS Lrg

Shelter repair kit 1 ea

Fuse box w/ assorted fuses 1 ea

Connector BNC female to N-type female

5 ea

Headset, computer audio/mic, dual 3.5 mm

30 per BCT and 12 per Bn

Double sided Velcro, 1" wide 300 ft

Zip ties, 6" 500 ea

Zip ties, 12" 500 ea

Heavy duty cable covers (floor/ground)

Various

3-7

Figure 3.3.3-1. Brigade Combat Team (BCT) Main CP Topdown View

3-8

Figure 3.3.3-2. BCT Main CP - Power Disbribution and Grounding

3-9

Figure 3.3.3-3. BCT Main CP – SIPR/NIPR Network and CPCS Cable Distribution

3-10

Figure 3.3.3-4. BCT Main CP - Current Operations Cell Modified Table of Organization and Equipment (MTOE) Position

3-11

Figure 3.3.3-5. BCT Main CP - Current Operations Cell Power Distribution and Grounding

3-12

Figure 3.3.3-6. BCT Main CP - Current Operations Cell SIPR/NIPR Network and CPCS Cable Distribution

3-13

Figure 3.3.3-7. BCT Main CP – NETOPS Cell - MTOE Position

3-14

Figure 3.3.3-8. BCT Main CP – NETOPS Cell Power Distribution and

Grounding

3-15

Figure 3.3.3-9. BCT Main CP – NETOPS Cell - SIPR/NIPR Network and CPCS Cable Distribution

3-16

Figure 3.3.3-10. BCT Main CP – Fires/Protection Cell - MTOE Position

3-17

Figure 3.3.3-11. BCT Main CP – Fires/Protection Cell Power Distribution and Grounding

3-18

Figure 3.3.3-12. BCT Main CP – Fires/Protection Cell SIPR/NIPR Network and CPCS Cable Distribution

3-19

Figure 3.3.3-13. BCT Main CP – ADAM Cell - MTOE Position

3-20

Figure 3.3.3-14. BCT Main CP – ADAM Cell - Power Distribution and Grounding

3-21

Figure 3.3.3-15. BCT Main CP – ADAM Cell - SIPR/NIPR Network and CPCS Cable Distribution

3-22

Figure 3.3.3-16. BCT Main CP - INTEL Cell - MTOE Position

3-23

Figure 3.3.3-17. BCT Main CP - INTEL Cell - Power Distribution and Grounding

3-24

Figure 3.3.3-18. BCT Main CP - INTEL Cell - SIPR/NIPR Network and CPCS Cable Distribution

3-25

Figure 3.3.3-19. BCT Main CP - Mvmt/Mvr Protection Cell MTOE Position

3-26

Figure 3.3.3-20. BCT Main CP - Mvmt/Mvr Protection Cell Power Distribution and Grounding

3-27

Figure 3.3.3-21. BCT Main CP - Mvmt/Mvr Protection Cell SIPR/NIPR Network and CPCS Cable Distribution

3-28

Figure 3.3.3-22. BCT Main CP - Sustainment Cell - MTOE Position

3-29

Figure 3.3.3-23. BCT Main CP - Sustainment Cell Power Distribution and Grounding

3-30

Figure 3.3.3-24. BCT Main CP - Sustainment Cell SIPR/NIPR Network and CPCS Cable Distribution

3-31

Figure 3.3.3-25. BCT Main CP - PLANS Cell - MTOE Position

3-32

Figure 3.3.3-26. BCT Main CP - PLANS Cell - Power Distribution and Grounding

3-33

Figure 3.3.3-27. BCT Main CP - PLANS Cell - SIPR/NIPR Network and CPCS Cable Distribution

3-34

Figure 3.3.3-28. BCT TAC CP - MTOE Position

3-35

Figure 3.3.3-29. BCT TAC CP - - Power Distribution and Grounding

3-36

Figure 3.3.3-30. BCT TAC CP - - SIPR/NIPR Network and CPCS Cable Distribution

3-37

Figure 3.3.3-31. BCT TAC CP - OPS-1 Cell - MTOE Position

3-38

Figure 3.3.3-32. BCT TAC CP - OPS-1 Cell - Power Distribution and Grounding

3-39

Figure 3.3.3-33. BCT TAC CP - OPS-1 Cell - SIPR/NIPR Network and CPCS Cable Distribution

3-40

Figure 3.3.3-34. BCT TAC CP - OPS-2 Cell - MTOE Position

3-41

Figure 3.3.3-35. BCT TAC CP - OPS-2 Cell - - Power Distribution and Grounding

3-42

Figure 3.3.3-36. BCT TAC CP - OPS-2 Cell - - SIPR/NIPR Network and CPCS Cable Distribution

3-43

Figure 3.3.3-37. BCT MVR BN Armor BCT / Infantry BCT (ABCT/IBCT) CP - MTOE Position

3-44

Figure 3.3.3-38. BCT MVR BN (ABCT-IBCT) CP - Power Distribution and Grounding

3-45

Figure 3.3.3-39. BCT MVR BN (ABCT-IBCT) CP - SIPR/NIPR Network and CPCS Cable Distribution

3-46

Figure 3.3.3-40. BCT MVR BN (ABCT-IBCT) CP – CUROPS - MTOE Position

3-47

Figure 3.3.3-41. BCT MVR BN (ABCT-IBCT) CP – CUROPS - Power Distribution and Grounding

3-48

Figure 3.3.3-42. BCT MVR BN (ABCT-IBCT) CP – CUROPS - SIPR/NIPR Network and CPCS Cable Distribution

3-49

Figure 3.3.3-43. BCT MVR BN (ABCT-IBCT) CP – Sustainment - MTOE Position

3-50

Figure 3.3.3-44. BCT MVR BN (ABCT-IBCT) CP – Sustainment - Power Distribution and Grounding

3-51

Figure 3.3.3-45. BCT MVR BN (ABCT-IBCT) CP – Sustainment - SIPR/NIPR Network and CPCS Cable Distribution

3-52

Figure 3.3.3-46. BCT SPT BN CP - MTOE Position

3-53

Figure 3.3.3-47. BCT SPT BN CP - Power Distribution and Grounding

3-54

Figure 3.3.3-48. BCT SPT BN CP - SIPR/NIPR Network and CPCS Cable Distribution

3-55

Figure 3.3.3-49. BCT SPT BN CP - CUROPS - MTOE Position

3-56

Figure 3.3.3-50. BCT SPT BN CP - CUROPS - Power Distribution and Grounding

3-57

Figure 3.3.3-51. BCT SPT BN CP - CUROPS - SIPR/NIPR Network and CPCS Cable Distribution

3-58

Figure 3.3.3-52. BCT SPT BN CP – SPT OPS - MTOE Position

3-59

Figure 3.3.3-53. BCT SPT BN CP – SPT OPS - Power Distribution and Grounding

3-60

Figure 3.3.3-54. BCT SPT BN CP – SPT OPS - SIPR/NIPR Network and CPCS Cable Distribution

3-61

Figure 3.3.3-55. BCT SPT BN CP – Sustainment - MTOE Position

3-62

Figure 3.3.3-56. BCT SPT BN CP – Sustainment - Power Distribution and Grounding

3-63

Figure 3.3.3-57. BCT SPT BN CP – Sustainment - SIPR/NIPR Network and CPCS Cable Distribution

3-64

3.4 Power Distribution

3.4.1 The Army-fielded standardized CPs with the Network Information Systems suites are powered in a different way from previous versions. Rather than each particular system or item running off of its own generator, all are collectively powered from a single source. This concept is called Central Power. Power is provided by a Power Plant (PP) and supplied to the equipment through a network of cables and distribution equipment referred to in this guide as a “grid.” This guide provides an overview of the equipment and instructions on how to set up the Central Power grid. Units should identify/appoint in their SOP and train a Central Power operator who develops and supervises establishing the Central Power grid for all operations.

3.4.1.1 TQG. The Tactical Quiet Generators (TQGs), used to power the CPs, are all configured as PPs. Each PP consists of two generators, each on its own trailer and linked through a switch box and power cable. The PPs used are the 15-kW AN/MJQ-48; the 30-kW AN/MJQ-40; and the 60-kW AN/MJQ-41. When available, backup power for each shelter in the CP is provided by either a 10-kW Auxiliary Power Unit (APU) or a 10-kW power unit, designated PU-798. Other TQGs can be found throughout the brigade and battalion, but for the purposes of CP power, this guide will only address the PPs listed above.

3.4.1.2 PDISE. The Power Distribution Illumination System Electrical (PDISE) system is a family of power distribution and illumination equipment which transmits electrical power between power-generation and power-using equipment. By adding components to meet specific organizational missions and requirements, it forms a consolidated power network. The PDISE system and the user’s electrical equipment are protected by circuit breakers within the PDISE equipment, rated at the maximum permissible load. The PDISE also:

3-65

• Permits using units more flexibility by consolidating power sources

• Provides flexibility to unit operations and can be quickly assembled/disassembled for rapid relocation

• Is designed for basic climatic (120° to -25°F [49° to -32°C]) •and field conditions

• Is designed to be used with generator sets (120/208 VAC, 50/60 Hz, 5-200 kW), but is compatible with any similar power source (e.g., utility or “pole” power)

• Uses standard military connectors

3.4.1.3 The line distance from the PP to the load is limited to a total of 300 feet (91.4 m) at maximum load; anything longer would cause an unacceptable voltage loss. Various types of PDISE and ancillary equipment are listed below.

3.4.1.4 The M100 is the central distribution point for the CP power, and connects the PP to the shelters and to the smaller boxes (M40). It also serves as a circuit breaker box for the CP, identical in operation to residential circuit breaker boxes. The M100s are sometimes referred to as “turtles” or “big hibachis.” Two M100s are used with each MJQ-41 power cable and one is used with each of the MJQ-40 and MJQ-48 power cables. Each M100 is equipped with phase indicator lights that indicate the presence of input power.

3.4.1.5 The M40 acts as a “branch circuit” for the CP. It is a smaller distribution box that provides rows of electrical outlets which, when used with the M46, allows CP operators the flexibility to power electrical and electronic equipment (servers, UPSs, laptops, cellphone chargers, etc.) directly from the PPs. At the Brigade (BDE) and BSB CPs, the M40 connects to the M100. At the BNs, the M40 wires directly into the terminal lugs on the switch box of the MJQ-48. The M40 also functions in the same cap as a residential circuit breaker box.

3.4.1.6 The M46 Electrical Distribution Kit contains the electrical outlets and cables that allow users to plug their equipment

3-66

into the PP. Each M46 kit consists of drop boxes with electrical duplex receptacles, branch cables for connecting and stringing up the drop boxes, and extension cables that run from the PDISE box to the branch cables. The M46 kits also contain extension power cables that can be connected to the M100 box or M40 box, 120 Volts AC (VAC), single phase. These kits are primarily used to connect to the outlet boxes or the light strings within the M46 Kit. In general, two M46s are issued with each M40. They can also be connected to the small 20 A connectors on the M100. Additional M46 Kit information that will assist in CP and Power setup follows:

• Receptacle/Outlet Boxes. The outlet boxes are used to connect weapon systems, command post systems and electrical appliances to the power grid using a standard electrical plug.

• Light sets. The light sets can be either incandescent or fluorescent lights. Both have a barrier that surrounds the light fixture to prevent damage to the bulbs or tubes.

• Extension Cables. These cables are connected from the M100 or M40 to the light strings or outlet boxes. These cables provide a watertight connection to prevent shorting in inclement weather. These cables are rated at 120 VAC.

3.4.2 General Guidelines for Setup

3.4.2.1 Power Plant Setup

• Setup and grounding of each PP is covered in the TM for that TQG. THE TQGs MUST BE GROUNDED PRIOR TO STARTUP! This cannot be stressed enough. Each set up requires a ground analysis, and might require a different grounding solution for each site. Example would be to check to see if the soil for the grounding rods (properly buried per TM) needs the addition of rock salt and water. For questions on grounding, refer to the CECOM Earth Grounding and Bonding Pamphlet (CECOM TR-98-6).

3-67

• Each PP consists of an A and a B unit. The A unit has the switch box. The B unit has the power cable. Each PP has two paralleling cables, one for each generator. On the MJQ-40, MJQ-41, and MJQ-48, they are stored inside the rear doors, along with the auxiliary fuel hose. Remove the cables from storage and install using the following steps:

1. Connect one end of the paralleling cable to connector J3 on the switch box located on unit A. Route the other end of this cable through the power cable sock and connect to connector J16 on unit B. The J16 receptacle is found inside the load terminal area in the far upper left corner. This provides power to the switch box. This connection can be difficult to secure; the cable has to seat properly for the switch box to work.

2. Connect the second paralleling cable between the two paralleling receptacles on the generator set control panels. This allows the TQGs to “talk” to each other.

3. Once these two cables are connected, ensure they do not form an X. If they do, the cables are connected incorrectly.

4. Unwrap the power cable from around unit B, but do not disconnect it from the unit B. Connect the plug end of the power cable to port J2 of the switch box on unit A. Route the other end of the cable through the power cable sock and connect leads to appropriate load terminals on unit B. Leads will be labeled with load terminal designations.

5. For detailed instructions and diagrams, refer to TM 9-6115-663-13. These TMs are provided with the generators, and can be accessed online through the LOGSA Website (https://www.logsa.army.mil/etms/online.cfm). or the PM-MEP Website (https://www.pm-mep.army.mil/logistics/index.html).

3-68

3.4.2.2 Connecting M100s to PPs

• Each M100 is supplied with two 50-ft feeder cables and one 4-ft pigtail used to connect the M100 to the power plant. Each power plant has a switch box that combines the power produced by the TQGs, and provides a safe, common connection point. The power is taken off the switch box through the terminal lugs found on the side of the switch box.

• The pigtail from the M100 connects to the switch box terminal lugs. The marking on the switch box (G, N, L1, L2, and L3) matches the marking on the pigtail. The wires are color coded but different manufacturers/ contracts may have different colors so be alert to specific instructions included in the operating manuals. In general the wires are color coded as follows:

• The wires are also color coded:

1) Green = ground = G 2) White = neutral = N or L0 3) Black = Phase A = L1 4) Red = Phase B = L2

• Orange or Blue = Phase C = L3M100. These enable the user to move the PP away from the CP, and reposition the M100 as needed.

Figure 3.4.2-1. M100 Pigtail Connection to TQG

3-69

3.4.2.3 Connecting Shelters to M100s

• Each shelter mounted on a HMMWV has one 50-ft cable and one 10-ft pigtail, both rated for 60 A. Prior to connecting anything to the M100, ensure the connector to be used is not ON. This is done by switching the appropriate circuit breaker into the OFF position.

• For the CPP and ADAM shelters, use the 50-foot vehicle cable to connect from the J1 port on the power entry panel to a 60-A rated port on the M100 (J3 or J6). Other shelters (such as DTSS) can use J4 or J5 on the M100. After the cable is connected, close the appropriate circuit breaker. Ensure shelter power requirement of 40 or 60 A prior to connecting power. See Figure 3.4.2-2.

Figure 3.4.2-2. M100 Conntections

3.4.2.4 PDISE: M40, M46

• The M40 PDISE boxes are used in conjunction with the M46 electrical distribution kit to provide a place to plug in electrical and electronic equipment. Use the large feeder cables that come with the M40. Connect the cables to the J1 port on the M40 and a port rated for 40 A on the M100 (J4 or J5; Figure 3.4.2.-3).

3-70

NOTE: No mention of M40 connections

• The M40 receives 3-phase power and splits each phase to separate connectors. On each side of the M40 are two connectors for each phase. These connectors alternate – ABCABC. A corresponds to L1 on the TQG, B corresponds to L2, and C corresponds to L3.

• When connecting the M46 cables to the M40, use groups of three connectors. This keeps the total load balanced on the generator, and prevents overloading any one phase. Use the C connector first, then B, then A, and then repeat as needed.

• The M46 branch is one line with three outlet boxes. Each box has four outlets. The entire line is connected to one 20-A circuit breaker. When connecting, go in numerical order, i.e., J3, then J4, then J5. This ensures each phase gets loaded, and that C is guaranteed a load. The items that are connected to each branch are METT-TC dependent.

Figure 3.4.2-3. M40 Connections

3-71

3.4.3 General Operation

3.4.3.1 Start and Parallel PPs

• Start one generator and apply load as per the TQG operation instructions. To parallel the TQGs or transfer load from one to the other, follow the instructions below. These instructions are also on the inside of the switch box control panel door. For detailed instructions and diagrams, refer to the PP TM.

• To start the MJQ-48: the DEAD CRANK switch must be in the NORMAL position, the DC Control Power circuit breaker must be pushed in, and the Emergency Stop Switch must be in the OUT position. Move the MASTER SWITCH to the START position and HOLD until the frequency gauge reads 60 Hz, the voltage gauge reads 120 volts, and oil pressure is at 60 psi. Once the generator set is running, move the AC CIRCUIT INTERRUPTER switch to the CLOSED position to supply power to the load. If the generator set’s STATUS light is on, move the ON/OFF switch at the switch box to the ON position to supply power to the load.

• Use to following steps to parallel the MJQ-48. Gen 1 is the generator that is on; Gen 2 is the generator that is off.

1. Start the vehicle engine to supply power to the shelter equipment (except the ECU), while transferring power to the TQGs.

2. On Gen 1, set UNIT-PARALLEL switch to PARALLEL.

3. Start Gen 2. Adjust VOLTAGE and FREQUENCY to match Gen 1.

4. On Gen 2 switch box, set ON-OFF switch to ON. ON LINE and STATUS lights should illuminate.

5. At Gen 2, set UNIT-PARALLEL switch to PARALLEL. Both SYNCHRONIZING lights should be flashing at the same time.

3-72

6. Increase frequency until SYNCHRONIZING lights flash in sync one or more times per second.

7. Decrease FREQUENCY until lights flash in sync once every 3 to 4 seconds.

8. When lights are off, set Gen 2 CIRCUIT INTRPT SWITCH to CLOSE. Gen contactor light should illuminate and SYNCHRONIZING lights should go out.

9. At Gen 1, set CIRCUIT INTRPT SWITCH to OPEN, set UNIT-PARALLEL switch to UNIT. Turn MASTER switch to STOP. At switch box, ON LINE and STATUS lights should be off.

10. At Gen 2, set UNIT-PARALLEL switch to UNIT.

• Use the following steps to start the MJQ-40 and MJQ-41:

1. Move the MASTER CONTROL switch to the ON position and allow the Computer Interface Module (CIM) to load.

2. Once the CIM software has loaded, clear any faults previously registered on the CIM display screen by holding the FAULT RESET switch in the ON position for 5 seconds.

3. Hold the ENGINE CONTROL switch in the start position until frequency gauge reads 60 Hz, and the voltage gauge reads 208 volts.

4. Once the generator set is running, supply power to the load by moving the AC CIRCUIT INTERRUPTER switch to the CLOSED position. The green light should come on.

5. On the generator set with a STATUS light on, move the switch box ON/OFF switch to the ON position to supply power to the load.

• Use the following steps to parallel the MJQ-40 and MJQ-41. Gen 1 is the generator that is on; Gen 2 is the generator that is off.

3-73

1. Start the vehicle engine to supply power to shelter equipment (except the ECU), while transferring power to the TQGs.

2. Start Gen 2. Adjust VOLTAGE and FREQUENCY to match Gen 1.

3. At the Gen 2 switch box, set ON-OFF switch to ON. ON LINE and STATUS lights should illuminate.

4. Set Gen 2 CKT INTRPT SWITCH to CLOSE. Contactor position on CIM display screen reads CLOSED.

5. At Gen 1, set CKT INTRPT switch to OPEN. Turn ENGINE CONTROL switch to STOP. At switch box, ON LINE and STATUS lights should go off.

3.4.3.2 Use the following steps to switch from on-board power to import power:

1. If an APU is installed in the shelter, turn off APU and remove the feeder cable at the J1 import connector of the shelter’s Power Entry Panel (PEP). BEFORE CONNECTING THE CABLE AT THE M100, MAKE SURE THE CIRCUIT BREAKER ASSOCIATED WITH THE CONNECTOR IS TURNED OFF!

2. Connect the 50-ft, 60-A feeder cable supplied with the CPP from a 60-A rated port on the M100 (J3 or J6) to the J1 Import connector on the CPP’s PEP.

3. With the connections made, first turn the circuit breaker at the M100 to the ON position, and then turn the IMPORT POWER circuit breaker and the DC POWER SUPPLY circuit breaker at the shelter’s PEP to the ON position.

4. To verify power at the PEP, press the PUSH TO TEST button and the three PWR SUPPLY AC INPUT and PWR SUPPLY DC OUTPUT LEDs should illuminate.

3-74

3.4.4 PDISE Placement – General Guidance

3.4.4.1 BDE Main, BSB

• The BDE HHC Main CP uses one MJQ-41 as the primary power source. The BSB CP uses one MJQ-40 as the primary power source. Figure 3-83 shows a suggested layout for the BDE Main based on the TRADOC-designed CP configuration. After the CP tents are set up, place the M40s so there is one M40 for about every two TMSS tents (the exception is the CIC, which may need its own M40). Then place each M100 within 50 ft of two shelters and one of the M40s. Keep the number of items connected to the M100s balanced. This helps prevent overloading and tripping circuit breakers. At the BDE Headquarters and Headquarters Company (HHC), park the PP halfway between M100s. At the BSB, park the PP no more than 50 ft away from M100.

• Use the branch cables and two or three outlet boxes in the M46 to run a line of outlets for items like the TMC-Client WS, laptops, cell phone chargers, etc.

• Use extension cables to provide a single power drop for items such as Tactical Battle Command Servers and Warfighters Information Network-Tactical (WIN-T)/Joint Network Node (JNN) SIPR/NIPR stack.

• Provide a single power drop for the coffee pot to share with •items that draw a lot of power, but are used infrequently, such as printers, plotters, or shredders. Again, when connecting the M46 cables to the M40, use groups of three connectors. This helps keep the total load balanced on the generator, and prevents overloading any one phase. When in doubt, put the larger load on L3. L3 corresponds to Phase C. On the generators, the logic / controllers monitor the voltage output to make sure it's kept constant. Depending on the load, the controllers will speed up or slow down the engine to keep the voltage at 120 V. More load requires more energy from the generator, which can cause the voltage to dip. Because of the expense and complexity

3-75

of these controllers, it's only feasible to monitor and control one phase; otherwise, the engine is always trying to adjust to three different setpoints. On all Generators, L3 (Phase C) is the line that's monitored. If there's a lot of load on L1 and L2, but none on L3, then the voltage on L1 and L2 will dip below 120V; this can cause equipment to brown out.

3.4.4.2 Maneuver BNs, BDE TAC

• The BDE TAC and Maneuver BN Command Posts (CPs) each use one 15-kW PP, MJQ-48, as the primary power source. Place the M40 near where the tents come together. Place the M100 as close to the M40 and CPPs as possible, but no more than 50 ft from the CPPs. Park the PP no more than 50 ft from the M100.

• Use the branch cables and two or three outlet boxes in the M46 to run a line of outlets for items like the TMC-Client WS, laptops, cell phone chargers, etc. Use the extension cables to provide a single power drop for items such as the TMC Servers. Provide a single power drop for the coffee pot to share with items that draw a lot of power, but are used infrequently, such as printers, plotters, or shredders. When connecting the M46 cables to the M40, use groups of three connectors. This keeps the load balanced on the generator and prevents overloading any one phase. Put the larger load on L3.

3.4.5 Address questions/comments about this guide or TOC power to:

PM-Mobile Electric Power ATTN: SFAE-CSS-ME (R. Nutter) 10205 Burbeck Rd, Suite 105 Ft. Belvoir, VA 22060-5863 Phone: DSN 654-3802, Comm 703-704-3802 E-mailmailto: robert.nutter.civ@mail.mil or jose.santos8.civ@mail.mil.

3-76

3.5 Combat Net Radios (CNR) and CP Communication System (CPCS)

3.5.1 The system includes the FM very high frequency (VHF) SINCGARS, high frequency (HF) AM radios, and TACSAT radio systems.

Figure 3.5.1-1. Example of CNR employment

3.5.2 Single Channel Ground and Airborne Radio System (SINCGARS)

3.5.2.1 SINCGARS is the most widespread communications system, found in all units. These radios are portable, mobile, and can be used on the move easier than other CNR systems. Although limited in range, their reach can be extended with directional antennas, retransmission stations, or relays.

3.5.2.2 SINCGARS transmits both voice and limited data traffic and resists jamming and other electronic attack techniques by frequency hopping. Imbedded communications security (COMSEC) further contributes to survivability.

3-77

3.5.3 High Frequency (HF) Radios

3.5.3.1 HF AM radios extend ranges beyond that possible with VHF radios such as SINCGARS. They are reliable, with good frequency management and antenna selection and can be used in a retransmission mode to extend the ranges of VHF nets. Current available versions are the vehicular-mounted, short-range AN/GRC-213 and the long-range AN/GRC-193 HF radios. Both support secure voice and data transmission.

3.5.4 Tactical Satellite (TACSAT) Radios

3.5.4.1 TACSAT radios carry both voice and data traffic globally, eliminating distance constraints inherent in other CNR systems. Range is the main advantage of TACSAT radios for beyond-line-of-sight capability. For contingency operations, CORPS and DIV need to include TACSATs in Mission Command architecture planning.

3.5.4.2 Higher Echelon Commanders (Division/Corps/ASCC) can direct that single-channel Earth stations be provided to subordinate BDE-sized elements if distances or terrain exceed other CNR system capabilities.

3.5.5 Command Post Communication System (CPCS)

3.5.5.1 Tactical Operations Center Intercommunication System (TOCNET™) provides an expandable approach to voice and data communications for field tactical mission command personnel. The system consists of three different Line Replaceable Units: Enhanced Micro Central Switching Unit (eMCSU), Desktop Crew Access Unit (CAU), and Soft CAU. Each eMCSU with attached communication assets comprises a node. Different sized systems can be constructed by adding or deleting nodes. Multiple nodes (up to 64) can be networked to form one larger system with up to 1024 assets (radios, phones, CAUs, etc.).

3.5.5.2 TOCNET enables users to interface and remotely manage tactical radio assets and other communication applications

3-78

consistently, regardless of platform, while reducing training and logistical impact. Workstations and radios can be configured easily and replicated in all common stations with access to CAUs not physically on the platform.

3.5.5.3 Extended Voice Communication (EVC) provides the capability to interconnect many TOCNET systems. The radio cross-banding function can be easily accomplished, resulting in optimal use of each platform’s resources, and transparent to off-platform users.

3.5.5.4 The eMCSU’s configuration file allows control of the following radio equipment:

• SINCGARS RT-1523E via a PPP serial or Ethernet connection to the INC

• SINCGARS RT-1523E through a direct RS-232 connection

• ARC-231 through a direct RS-232 connection • PSC-5D through a direct RS-232 connection • ARC-220 through a direct RS-232 connection • PRC-117F through a direct RS-232 connection • PRC-150 through a direct RS-232 connection • STE-R through a direct RS-232 connection

3.6 Network Cabling

3.6.1 The methods outlined in this handbook provide best practices and procedures for the installation and utilization of physical network assets. Installation of a CP Local Area Network (LAN) from a distribution point (e.g., CPP or data access case) to end user can be performed more efficiently once the end user systems are positioned within the CP.

3.6.2 Equipment should be emplaced but not connected until a final layout is obtained. The use of a diagram or notional architecture allows for concurrent execution in various cells within a CP. When running cable from the distribution point to the end user, the installer should route the cable according to the plan outlined in this handbook or unit Standing Operating

3-79

Procedure (SOP). Once sections of a specific cell have been wired, class-specific wires can be bundled into harnesses utilizing hook-and-loop ties. Single-use nylon zip ties should not be used for cable bundling since over tightening may damage cabling.

3.6.3 Class-specific wiring harnesses increase efficiency in establishment and subsequent displacement of the CP. In accordance with NSA 73-2A TEMPEST, SIPR and NIPR cables running in parallel for distances greater than 30 m must be 15 cm from each other. For more security requirements, refer to NSA 73-2A and other TEMPEST-related regulations.

National Security Telecommunications and Information Systems Security Advisory Memorandum (NSTISSAM) TEMPEST/2-95, RED/BLACK Installation Guidance specifies RED/BLACK equipment/system installation guidance, provides an explanation of the TEMPEST policy concept, and addresses RED/BLACK considerations for facilities wherein national security information is processed. This publication supersedes National COMSEC Information Memorandum (NACSIM) 5203, dated 30 June 1982. However, Appendix K of NACSIM 5203 will remain in effect until NACSI 4009, Protected Distribution Systems, dated 30 December 1981, is superseded. NACSI 4009 is currently under revision.

3.7 Network Operations and System Architecture

3.7.1 The purpose of this chapter is to outline key components of Network Operations (NetOps):

• Capabilities and responsibilities for supporting military operations

• Commander’s role and responsibility concerning the establishment of network priorities

• Guidance for facilitating both internal connectivity as well as external connectivity to the Global Information Grid (GIG)

3.7.2 In addition, this chapter will highlight the fact that the network reaches far beyond the tactical boundaries of the battlefield, crossing operational and strategic echelons up to the

3-80

Department of Defense in support of the Land War Net (LWN). This chapter will also discuss:

• Specific network management activities, functions, and tasks performed by network managers

• An overview of Information Assurance (IA) (including responsibilities, tools, and incident reporting)

• An overview of Information Dissemination Management (IDM) as an enabler of information management

3.7.3 Role of NetOps

3.7.3.1 As technology continues to advance the development of more sophisticated weapons systems, so does reliance on the network to integrate these systems in order to achieve their desired effects. In this light the network can and should be considered a weapons system, equal to any of the traditional combat platforms, which provides commanders shared situational understanding, enhanced speed of command, and task force synchronization. This is an important distinction to make, especially when discussing what comprises a weapons system. The DoD definition of a weapons system is “...a combination of one or more weapons with all related equipment, materials, services, personnel, and means of delivery and deployment (if applicable) required for self-sufficiency” (As listed in Approved Joint Definitions, Acronyms, and Abbreviations contained in Joint Publication 1-02, DOD Dictionary of Military and Associated Terms 08 November 2010, as amended through 15 July 2012.

3-81

Figure 3.7.3-1. Network Operations

3.7.3.2 When comparing a traditional weapon system with the network, they both utilize the exact same components to put them into operation. These components are listed below:

• Training • Preventative Maintenance • Function Checks • Operation • Capabilities • Limitations • Corrective Actions • Management • TTPs • Crew Roles and Responsibilities

3.7.3.3 As this list shows, whether a combat or network platform, mission success depends on a detailed operational (and functional) understanding if the system capabilities and limitations in order to properly apply the system to the fight.

3-82

3.7.3.4 NetOps provides the over-arching management of these capabilities and can be prioritized based on the commander’s intent and guidance.

3.7.3.5 NetOps is defined as the operational construct consisting of the essential tasks, situational understanding and mission command that the commander uses to operate and defend the tactical network and its connectivity to the GIG. In this construct, NetOps allocates network, information system, information security, and information resources directly in support of the warfighter. Although immediate operational commanders “own” the network, they grant control, operation, and oversight to the senior signal officer and staff. NetOps control is granted by the operational commander in order to ensure the day-to-day compliance of the network with the associated Tactical Information Grid (TIG) and GIG requirements. Due to the fast moving nature of NetOps and its 24/7 operation, NetOps requires quick decisions and adjustments in order to fully support the dynamics of an ever-changing battlefield. NetOps enables the commander by providing assured network availability, information protection, and information delivery.

3.7.4 Key Components

3.7.4.1 NetOps is the critical fusion point in the CP that combines infrastructure and services that provide processing, storing, and transporting information across the network. The functional areas that comprise this infrastructure and services consist of the wireless area network (WAN) and LAN management, Battle Command systems, IA, Communications Security (COMSEC), and Electromagnetic Spectrum Operations (EMSO). Each of these areas is interrelated. As such, they cannot be viewed and operated as single stove-piped systems, but instead must be viewed from a holistic approach. It is also important to understand that these areas are executed at both the Division and BCT level and, therefore, must be synchronized both horizontally

3-83

and vertically between the two echelons so the shared bandwidth, spectrum, and GIG (network) access is properly managed. NetOps provides this management by:

• Identifying the user’s information requirement (who, what, when, where)

• Identifying which network, information systems, and security architecture (hardware and software configuration management) is required

• Ensuring availability and access to networks • Applying the right technology and equipment • Protecting network resources and user information with

IA security measures • Ensuring the right information is disseminated to users in

a usable format at the right time and place

3.7.4.2 The synchronization between the BCT and Division cannot be overlooked and marginalized. Although the Division G6 does not own the signal assets in the BCT (this includes signal personnel as well) all network configuration changes and WAN transport equipment (WIN-T/JNNs and specifically satellite terminal) locations must be coordinated with the next NetOps echelon. See Chapter 4 for additional G-6 Responsibilities at Division and higer Echelons of Mission Command. Failure to do so will significantly impact not only the affected BCT, but the entire tactical network as well. There must be an informal command relationship between the Division (and Corps/ASCC) G-6 and S6 in regard to network operations and management. Although the BCT commander has the right to move assets based on operational necessity, the BCT S-6 still has the requirement to coordinate any configuration changes, report network incidents, and highlight future operations and any additional network requirements needed for support of those operations.

3-84

3.7.5 Organizational Structure and Force Multipliers

3.7.5.1 As mentioned earlier, the operational commander grants network control to the senior signal officer in the organization. In the BCT the S-6. Although the S-6s are considered primary staff officers, they have the authority to make “command” decisions and changes to the tactical network in order to ensure that it operates at maximum efficiency. The mission statement for the S-6 is similar to G-6s at higher echelons as listed below:

The G-6 (CIO) integrates, manages, and provides operational oversight for the mission command system architecture ensuring the availability, reliability, and security of voice, video, and data networks that support robust, adaptable, and survivable mission command capability for the Commanding General and subordinate U.S. and coalition commanders throughout the Area of Operations (AO). See more details in Chapter 4.

3.7.6 NetOps at the BCT

3.7.6.1 As part of the overall LWN construct, the BCT is now considered the centerpiece of the Army fighting force. As such, the BCT could be called upon to deploy and conduct operations independent of their organic command structure. To do this, the BCT must be able to establish, operate, and maintain its own network for the duration of the operation. This includes the establishment of a central integrated section dedicated to execute NetOps functions and is manned by the S-6 section, Signal Company personnel and assigned government and civilian contractors. Figure 3-86 shows the BCT hierarchy.

3.7.6.2 The Brigade Signal Officer (S-6) organization is augmented by their STB Signal Company to provide a robust Brigade Network Operations and Security Center (BNOSC). The Brigade S-6 could not operate without direct support/attachment of those key personnel. The Brigade organization provides both the tactical support for the BCT and also the interface with the Division for all C4I issues.

3-85

The brigade S-6 section is task organized to best support the commanders’ intent, normally located within the brigade command posts to support the commander’s communications requirements across the AO.

3.7.6.3 The S6 is the principal officer for all matters concerning communications and networks for a fully digitized BCT with one Cavalry BN, two Combined Arms BN, one Field Artillery BN, one Special Troops BN, one Support BN, and a separate Headquarters company. Responsible for advising the commander and staff on all aspects of mission command system (Formerly Command, Control, Communications, and Computer Operations (C4OPS), COMSEC, automation, and ensuring all aspects of mission command systems are ready to conduct combat operations. Due to the dynamics of having signal assets assigned to multiple separate organizations, the S-6 must first have the support of the BCT commander and develop a close working relationship with the BSTB and maneuver battalion commanders, each of the battalion S-6s, and the Division G-6 (or other assigned Higher HQS). The BCT S-6 is also responsible for the maintenance and employment of FBCB2, MSE, lower and upper tactical internet, automation, strategic, TACSAT, FM, HF, MSE, and UHF tactical communications systems, and the digital connectivity between all echelons. The BCT S-6 works closely with the higher hqs, such as the Division G-6 and the Network Signal Company Commander (NSC). The brigade NSC commander works closely with the brigade S-6 when deployed. In addition, the Brigade S-6 has technical authority over all brigade NSC equipment. When the BCT operates independently, the brigade S-6 performs all of the same duties and responsibilities as the G-6.

3-86

3.7.6.4 Brigade S-6 Responsibilities. These are Brigade S-6 responsibilities:

• Prepare, maintain, and update mission command system operations estimates, plans, and orders. Orders will often cause configuration management changes across multiple battalions

• Monitor/make recommendations on technical mission command system operations

• Designated as the ARFOR G-6 when needed. Equipment and personnel augmentation required to support this mission

• Advise the commander, staff, and subordinate commanders on mission command system operations and network priorities for battle command

• Develop, produce, change/update, and distribute SOI • Prepare/Publish mission command system operations

SOPs for BCT CPs • Coordinate, plan, and manage BCT spectrum within its

AOR • Plan and coordinate with higher and lower headquarters

regarding information systems upgrade, replacement, elimination, and integration

• Coordinate with S-2 and S-3 to plan and direct all IA activities and mission command system operations, vulnerability, and risk assessments

• Coordinate with staff from a variety of external agencies to develop the information and communications plans, manage the information network, obtain required services, and support mission requirements

• Confirm and validate user information requirements in direct response to the tactical mission

• Establish mission command system policies and procedures for the use and management of information tools and resources

3-87

Figure 3.7.6-1. BCT Hierarchy

3.7.7 Tool Sets

3.7.7.1 NetOps tools enable network managers (G-6/S-6) to get near-real-time information on the status and health of the integrated network (LAN, WAN, and CNR) to enable commanders to make sound decisions and execute operations. The information collected can be used to conduct detailed analysis of the network to identify trends that can be used to optimize the efficiency and better protect it and its users. These tools are normally consolidated and reside in the Division and BCT NOSC under the control of the G-6 (S-6). These tool sets are fielded as part of the Unit Set Fielding (USF) process and incorporated into the system architecture and data product development. Discussion on data product develop will follow in a later section. Figure 3.7.7-1 shows the Current NetOps capability.

3-88

Figure 3.7.7-1. Current NetOps Capability

3.7.8 Battle Rhythm

3.7.8.1 Due to the number of briefings and mandatory events occurring in a CP, both in garrison and combat, it is critical that these events be synchronized. From a NetOps perspective, this ensures that the network is available and accessible to support operations. All mission essential network-related events MUST be nested in with the Division/BCT battle rhythm. Critical events that the G-6 and S-6 must pay close attention to include, Battle Update Briefs (BUBs), network operational updates, server maintenance, generator services, other scheduled system downtime requests, and mission planning for future operations.

3.7.9 Establishing the CP

3.7.9.1 The setup and teardown of the CP is the most critical time for the unit to conduct Ops. It is during these periods that the NetOps section has minimal tools with which to monitor the stability of the network and to take corrective action if any degradation occurs. The unit must ensure that these processes are part of the unit SOP, and trained and

3-89

executed in accordance with established unit battle drills. During the movement of the CP (specifically the main CP) NetOps functions will remain with the CP that has operational control of operations within the AO. Once the displaced CP has established full network connectivity, a battle handover of tasks, functions, and responsibility will be transferred to it. This battle handover is a deliberate process with control measures (decision points) in place to ensure the proper handover criteria is met.

3.7.10 Reporting

3.7.10.1 As mentioned previously, a Division G-6 or higher does not control or own the signal assets or personnel in the BCT. However, when the BCT is connected to the Division (or Corps or higher) network, then the Division G-6, empowered by the Division commander, has technical control of the network and the BCTs are obligated to report their network status to the higher HQ. Reporting procedures are normally included as part of a specific Annex to the division or task force operations order and specific timelines and report formats are part of the NetOps battle rhythm. Data gathered from these reports serve as a method for the G-6 and staff to conduct additional analysis on the overall health of the network, looking for trends that may signal an issue before it happens, track the maintenance status of all network related equipment, systems and platforms, and to prepare updates to be presented as part of the commander’s battle update brief. Report formats and content are defined as part of the unit SOP.

3.7.11 Commander Network Roles

3.7.11.1 The potential missions a BCT can be assigned are more diverse than ever. Since the BCT is capable of unit-specific, self-sustained operations for a period of time, it must be able to establish and maintain access to the GIG to conduct operations. It is imperative that BCT commanders have a better understanding of the network and its capabilities, the BCT architecture and systems that utilize the network, and

3-90

the responsibility for utilizing and protecting the network. The commander is not the resident expert, but must possess an operational understanding of the network, its applications, and systems to employ and utilize it as a weapons system; and be able to provide the appropriate guidance and support to the S-6 running and maintaining the BCT enterprise network. It is important for commanders to understand that the decisions made about the network and how they operate have an impact on the larger enterprise information grid. This affects not only the ability to execute operations, but affects the larger task force as well. Depending on the situation, adverse network effects can be felt all the way back to the sustaining base. The following are some specific areas for the commander to focus:

• Spectrum – There has been a significant increase in the number of emitters and spectrum dependent systems fielded down to the Brigade level. In some cases, these new emitters are competing for the same limited spectrum that the existing battle command and transport systems are utilizing. Commanders must understand and incorporate spectrum as part of their overall mission planning process. Of specific concern is the impact that the operational environment (terrain, urban density, proximity to U.S. and coalition partners, host nation spectrum utilization, etc.) has on the availability of spectrum to support operations. The closer in proximity that similarly configured and equipped units are operating, the more likely that spectrum conflicts become. Unmanned aerial platforms are an example. Due to the frequency band used to operate each platform and the bandwidth required, numerous units operating a defined area must be prepared to share the spectrum, limiting the number of platforms that can be airborne at any given time. Commanders cannot use all of the emitters that fielded and must prioritize installation, operation, and restoration of these systems. The S-6 and Bde/Division/Other Higher HQs Spectrum

3-91

Managers are critical to the development of the spectrum utilization plan in support of operations and commanders intent.

• CP Operations – Commanders must integrate increased personnel and systems, including increases in the robustness of the mission command system and applications, to enable effective mission command. Each staff section residing in the CP has extensive data requirements to develop products for the commander. This information is critical to CP operations; but excessive data can rapidly exceed the allocated bandwidth for a unit. It is critical that commanders establish and enforce “digital rules of engagement” inside the CP to ensure all systems are utilized to their fullest potential. These rules help to protect bandwidth supporting critical CP events. Applications and products requiring extensive time and/or bandwidth to produce should be allocated a time slot in conjunction with daily operations. These products should be synchronized with/included as key events on the unit’s battle rhythm. For example, the S-2 cannot pull multi-megabit sized map products through the network when the commander is executing a battle update brief with the higher headquarters. Trying to access the map/intel products can impact the quality of the update brief. Disciplined adherence to the digital rules will ensure network stability and unhindered support to operations.

3-92

Figure 3.7.11-1. Controlling Bandwidth

• Information Assurance (IA) – With this influx of data coming into the CP comes the operational necessity to safeguard it. The tactical network is no longer “closed” to the global community, and as a result makes network more vulnerable intrusion aimed at data collection (Intel) or to undermine operations. To this end, the IA posture is aimed at protecting systems from such attacks. There is no differentiation or separation between the network in garrison or in a forward theater of operations. This concept also applies to the fact that there is no difference between the tactical and strategic network. There are stringent rules on what is and is not allowed on the network and the commander is an essential part of enforcement of these rules. If the commander does not ensure compliance, anomalies can be injected into the network that can cripple an entire theater in just a matter of hours, having ramifications that reach all the way back to the sustaining base. Units must gain approval to add components, especially Commercial Off-the-Shelf (COTS) components outside their MTOE. This is important for several reasons. In a network where each and every component has an assigned IP address, the addition of outside components can interfere with the proper functions of other systems. These additional

3-93

systems utilize precious bandwidth that was not planned for, potentially reducing available bandwidth required for operational support. In addition, “non-standard COTS systems” are not included as part of the approved unit system architecture driving the production of data products that establish specific unit configuration baselines for digital connectivity. These additions force network managers to manually add their IP addresses to the baseline files, increasing the likelihood of configuration mismatches. There are stringent guidelines and policies in place to safeguard the network and critical information. The Brigade S-6 ICW the applicable higher Hqs G-6 has overall responsibility in the BCT and has a small staff section dedicated to monitoring IA across the BCT footprint, as does the Higher HQs. The Brigade and Battalion S-6 work directly as needed with higher HQs G6s on all compliance matters.

3.7.12 Data Products

3.7.12.1 Data Products are a collection of mission data required to initialize Mission Command. This data includes the information required to enable end-to-end network-centric connectivity and interoperability across the Tactical Internet (TI). In simpler terms, Data Products are a set of software databases which provide the following:

• Blueprint for building a unit • Initialization data required to configure the network • Upper and lower tactical internet address book

3.7.12.2 These software files ensure the configuration and connectivity requirements of the individual Warfighting Functions (WfF within mission command system are met. They include the data that provides accurate addressing and networking information for routing communications and information system messaging between these systems. Two specific products that are produced to facilitate network management by the G-6/S-6 are the System Architecture

3-94

and Lightweight Data Integration Format (LDIF) which contains the role name and IP address for every mission command system in the unit.

3.7.13 System Architecture As alluded to previously, the system architecture is the foundation for which unit digital connectivity is developed and serves as an essential guide to support CP establishment and operations. By definition, the system architecture “is a graphical display of radios and computer systems (based off of the MTOE from USAFMSA, the Army Requirements Development Plan (ARDP) from TCM-MC, and the KLO from TCM MC-BCT (formerly TCM-Platform Battle Command/Combat ID), inside their platform (e.g., vehicles, tents, transit cases, or aircrafts) networked together in order to provide a computer networking blueprint.” The diagram in Figure 3.7.13.1-1 shows an example of a NetViz diagram which displays the interconnectivity between the CP, network platforms, and the mission command system. Without this interrelationship, network connectivity, and situational understanding across the unit could not be shared.

3-95

Figure 3.7.13-1. NetViz Diagram

3.7.14 Data Product Development

3.7.14.1 Data products are extremely detailed and their development can take anywhere between 60-120 days. It is critical that the unit commander understands this complexity and ensures the development timeline is synchronized with the unit’s operational timeline. Failure to do so can adversely affect unit training events across multiple echelons. Throughout the development process, it is imperative that the right people are involved. At the Brigade level, the S-6, network techs (warrant officers), and senior automation officers/NCOs play a pivotal role. These people must be familiar with the type and location of all the mission command systems, including the combat platforms and command vehicles. Additionally, they must have a clear

3-96

understanding of the unit’s system architecture and be able to make recommendations to the commander regarding redistributing assets or making additions platforms. There are several planning conferences taking place at different phases in the process. It is essential that these personnel are involved with each of them.

3.7.14.2 The development process begins with a review of all approved authorization documents for a particular unit (MTOE, ARDPs, Fielding Schedules, Fragos, ARFORGEN timelines, etc). With these documents, the developers create a baseline systems architecture which will serve as a baseline that any scheduled new equipment fielding or system changes can be annotated. Once completed, the systems architecture is provided to the unit at the initial synchronization conference. During this conference, the unit is provided fielding timelines linked to the operational and training calendars.

3.7.14.3 Once this initial conference is complete, there are a number of technical exchange conferences that occur between the data product developers and the WfF leads to verify network and configuration parameters. At the same time, they continually refer to the source documentation and ensure that the system architecture accurately reflects these protocols. This is the most important phase, as any unit-specified equipment/system changes are reflected in the configuration matrices. The final step in this phase is the addition of Unit Reference Numbers (URNs) to the system architecture documentation and database files.

3.7.14.4 The final phase involves a multi-tiered review of the system architecture data product and all system configurations. This phase involves a special data review board, the unit, and the Pd NetOps data products working groups. Once approved, these configurations are installed in CP router, switches, servers, and applicable TMC Servers to serve as baseline configurations the unit uses to execute their mission essential training events. Once training is complete,

3-97

the unit receives a final set of data products to support their deployment. These data products are classified and must be treated as any other classified document.

3.8 Information Systems

3.8.1 Applicable Command Post Information Systems are listed below. Additional information, to include descriptions and latest updates can be found at the Single Interface to the Field (SIF) site at https://sif.kc.army.mil/ ADAM Shelter - Air Defense Airspace Management System ADSI - Air Defense System Integrator AFATDS - Advanced Field Artillery Tactical Data System , several LINS AMDWS - Air and Missile Defense Workstation BCS3 - Battle Command Sustainment Support System CCS - Command Center System CHATS - Counterintelligence Human Intelligence Automated Tools Set CPCS - Command Post Communications System CPP- Command Post Platform CSS VSAT-Combat Service Support Very Small Aperture Terminal DCGS-A Enabled ACT-E - Distributive Common Ground Station Army Enabled Analysis Control Team-Enclave DCGS-A Enabled ASAS-L- Distributed Common Ground System-Army Enabled All Source Analysis System-Light DCGS-A Enabled ASAS-L IFS - Distributed Common Ground System-Army Enabled All Source Analysis System (ASAS) Intelligence Fusion System (IFS) DCGS-A Enabled DTSS - Digital Topographic Support System EMT - Effects Management Tool, part of AFATDS Family FAAD - Forward Area Air Defense FBCB2/BFT- Force XXI Battle Command Brigade and Below/Blue Force Tracker

3-98

FBCB2 TOC System (TOC Kit) GBS - Global Broadcast Service IMETS - Integrated Meteorological System, being replaced by Weather Systems Software on DCGS-A Enabled Systems. JADOCS - Joint Automated Deep Operations Coordination System MC4 - Medical Communications for Combat Casualty Care Family of Systems MTS - Movement Tracking System SMART-T - Secure Mobile Anti-Jam Reliable Tactical - Terminal TAIS - Tactical Airspace Integration System TC-AIMS -Transportation Coordinator – Automated Information for Movements System II TGS – Tactical Ground Station TMC-GW - Tactical Mission Command - Gateway TMC-WS - TMC – Work Station TMC-Server - TMC-Server (Previously known as the Battle Command Common Services (BCCS)) TMC- SMC - TMC Server Management Console WIN-T INC 1 and 2 - Warfighter Information Network – Tactical Increment 1 and 2 (formerly JNN)

3.8.2 Additional Information Systems

3.8.2.1 WAN Manager V2 and V3

3.8.2.2 These provide WAN fault, performance, and configuration management functions for routers within division, brigade, and ESB responsibility.

3.8.2.3 LAN Manager V3 provides LAN management functions for S6 cell supporting the BN CP. It serves as a syslog server due to lack of other NetOps platforms at that echelon, used to configure or reconfigure the local routers managed by a higher echelon. SNMPc Workgroup is the primary software component hosted.

3-99

3.8.2.4 Help Desk (HEAT) Management Software provides administrators the ability to log trouble tickets, manage personnel and assets, and provide stored solutions for network problems. The system utilizes a HEAT software suite developed by FrontRange Solutions: HEAT Support and Services, iHEAT, and HEAT Self Service.

3.8.2.5 Detailed Planning and Engineering Module (DPEM) is the planning and engineering tool used within NetOps cells and G6/S6 staff sections. DPEM software operates on a GETAC M220 laptop. The system provides software modeling and display capability that planners use to build graphically-planned networks. Planners lay down and link communications nodes on a map background. The network can be viewed in a logical diagram indicating how assets are connected, but not their location. Planners place assets on a battlefield map and graphically assess connectivity in a logical view, or on a map background. Patching diagrams, cutsheets, and reports for switch configurations are generated from the DPEM.

3.8.2.6 ISYSCON (V)4, being replaced by WIN-T systems, is a digital, battle command InfoSys for G-6/S-6 sections providing on-the-move, real-time mission command information. It provides a semi-autonomous management capability to aid in the planning, configuration, initialization, monitoring, troubleshooting, and reconfiguration of TOC and LTI communications networks. ISYSCON(V)4 and its replacement systems within WIN-T also supports SA down to the warfighter/platform level.

3.8.2.7 Army Key Management System (AKMS)

3.8.2.8 AKMS is the Army’s implementation of the Electronic Key Management System (EKMS). EKMS involves the following tiered hierarchy:

• Tier 0 – NSA Central Facility (CF) • Tier 1 – Service-level EKMS account support • Tier 2 – LCMS software and KP support

3-100

• Tier 3 – End User (Field-level) key and non-key data loading to mission support equipment

AKMS is comprised of three subcomponents: LCMS, ACES, and SKL. The following paragraphs describe each component.

• The Army Local COMSEC Management Software (LCMS) Workstation Phase 5 Upgrade is an InfoSys functioning at the user level (Tier 2) of the EKMS, to integrate all functions of COMSEC. The LCMS Workstation automates and integrates processes required to generate, distribute, and manage data needed by various secure communications systems. The Workstation provides tools to support changing requirements in strategic and tactical environments, and is fully compatible with EKMS and Joint Key Management System (JKMS). The LCMS Workstation Phase 5 Upgrade includes the LCMS Workstation (AN/GYK-49(V)3). The Laptop (Tactical) LCMS Workstation (AN/GYK-49(V)2) has been replaced by the LCMS Workstation (AN/GYK-49(V)3).

• Automated Communications Engineering Software (ACES) was designed to replace the legacy Revised Battlefield Electronic CEOI System (RBECS) for automated cryptonet planning and EP data. It generates and distributes SOI and EP fill data for CNR operations. It also enhances the operator’s ability to provide cryptonet planning for other devices. The data stream used to randomly generate SOI and EP data will be implemented via software, replacing the legacy Random Data Generator (RDG) hardware.

3-101

• Simple Key Loader (SKL) component was developed by PD NetOps and is used as the Tier 3 data-loading device. The SKL’s primary task is managing key material. The SKL is a ruggedized, hand-held PDA consisting of a host computer and NSA-developed cryptographic and ECU protocol engine on a Personal Computer Memory Card International Association (PCMCIA) Type II card (KOV-21). It uses service-specific applications software called UAS to automate the loading process for field/mobile COMSEC components. SKL will replace DTDs and provide simple loading capabilities. It will be backward compatible with existing DTDs (i.e., CT3 UAS) until all DTDs have been replaced.

3.9 Configuration Customization

3.9.1 Customizating a CP must be planned to incorporate all essential CP elements. A CP may need to be customized for numerous reasons. The following things need to be planned out: power distribution and grounding, distances for network, flow of traffic, security measures, and operational tempo.

3.9.2 Terrain is the largest factor in planning for CP customization. Security and fueling operations must be considered. Terrain dictates where to place security. Adequate areas around the CP must exist to put security measures in place. Fuel trucks need room to travel around the CP to refuel power and environmental equipment, or alternative plans must be made for refueling.

3.9.3 Power distribution is a major priority when planning CP customization. Planners must consider distances from the power plant to ensure the proper length of power cable is available. Planners must also ensure cable distances do not interfere with the electrical grounding system in the power plant. Safety is a concern if power cables are run where they may cross a walkway or roadway. Plan to ensure that the correct equipment, PDISE M40 or M100, is on hand and can cover the power needs of the change. The maximum distance from the power plant to the CP should be 100 feet. Longer

3-102

distances require additional cables. Use of additional cables cause the voltage to drop to a level that prevents proper operation of CP Information System equipment.

3.9.4 Some information system networks are limited by the distance the signal can travel and the surrounding terrain features. When customizing the CP, plans have to be made to ensure that network assets can communicate to other information systems. Network cable runs must be planned according to Army regulations for security and safety, personnel, and cable.

3.9.5 CP customization requires a consideration of flow-of-traffic considerations. Fire exits and other safety features need to be clearly identified in the plan. The CP planner needs to ensure that the CP does not turn into a “maze” of corridors. A minimum amount of cells that have walk-through traffic is desired.

3.9.6 Although deviation from the CP standard is not encouraged, customization is sometimes necessary. Prior planning and considerations for all elements of the mission command system within the CP will ensure it is safe and functional.

3.10 Network Services Architecture

For information on Network Services Architecture, see the CP Warfighter Handbook website at https://www.us.army.mil/suite/page/547567.

3.11 Closing Information

3.11.1 Doctrinal Templates for the Functional and Multifunctional Support Brigades will be covered in covered in an annex to be published later. The Templates while very similar to the BCTs will still need application of the unique MTOEs of the other type Brigades. These Templates when published will be available with a link to CP Handbook.

Chapter 4 Characteristics of the

Mission Command System Division / Corps / ASCC

This page intentionally left blank.

4-1

Chapter 4.0 Division/Corps/Army Service Component Command (ASCC) CPs

4.1 Introduction

4.1.1 This chapter breaks down the physical components of the Command Post (CP) for the Division/Corps/ASCC (Theater Army) and how they are assembled and/or connected at these echelons. The diagrams in this chapter depict CPs at Division level per their authorized equipment and personnel by Modification Table of Organization and Equipment (MTOE) for a unit that has been fielded Capability Set 11/12. The doctrinal templates show the physical layout for each cell and for each aggregate CP. Note the layouts presented show the CP only and do not include support elements that would be co-located. Additionally, ADP and ADRP 6-0 discuss mission command. Not all the Supporting EAD Units/Commands/Enabler Formations CPs are illustrated in this Handbook, but most of the CP layouts are very similar. Commanders can adjust their CP as needed for each type Formation or specific mission. All these formations CPs at these echelons are essentially the same but with differences in grade and function as appropriate. Key references for the doctrinal employment and set up of these CPs are FM 71-100 (Division), FM 3-92 (Corps), ATTP 5-0.1, JP 3-33, Joint Task Force Operations, and JP 3-31, C2 for Joint Land Operations.

The conventions in this book allow for Chapter 3 (BCT/BN) and Chapter 4 (DIV/Corps/ASCC) to stand alone. This has caused certain elements to be repetitive.

4.1.2 A separate Annex to be published as a link to this Handbook will cover Doctrinal Templates for the EAD Supporting Commands and Enabling Formations, such as Theater Sustainment Command (TSC), Theater Aviation Command (TAC) and Engineer Command. These Doctrinal Templates are somewhat similar to the BCT, Functional and Multifunctional Brigades CP Layouts. Diagrams for the Echelons Above Division (EAD) Formations will also be included in this Annex TBP.

4-2

4.1.3 This Chapter addresses the physical aspect of the Command Post in the context of ADP 6-0’s definition of the mission command system, the arrangement of personnel, networks, information systems, processes and procedures, and facilities and equipment that enable commanders to conduct operations. A command post is one place where all five of those components can be integrated and organized to perform the specific functions either by design or assigned to them by the commander. ATTP 5-0.1 provides a listing of activities common to all Command Posts include:

• Maintaining running estimates and the common operational picture.

• Controlling operations. • Assessing operations. • Developing and disseminating orders. • Coordinating with higher, lower, and adjacent units. • Conducting knowledge management and information

management (See FM 6-01.1). • Performing CP administration

Figure 4.1.3-1. Division Main Command Post

4-3

4.2 Components of a mission command system

4.2.1 Personnel. Staff personnel are assigned to warfighting functions according to individual Military Occupational Specialty (MOS) and authorized MTOE position, and are assigned a designated information system according to position. Tent layouts in this handbook designate recommended staff positions within various sections. A specific unit’s MTOE may depend on MOS or assigned information system

4.2.2 Networks. Generally, a network is a grouping of things that are interconnected for a purpose. They enable commanders to communicate information and control forces whether mounted or dismounted. Networks are key enablers to successful operations. While the Army defines both Technical and Social networks, this handbook focuses only on technical networks.

4.2.3 Mission Command System. The mission command system consists of equipment that collect, process, store, display, and disseminate information. This includes computers – hardware and software – and communications, as well as policies and procedures for their use. (See ADP 6-0 and ADRP 6-0.)

4.2.3.1 Computers, hardware and software. A listing and brief explanation of the most common systems issued as part of SWB 11/12 to be published.

4.2.3.2 Large Screen Display. A Large Screen Display (LSD) in the Current Operations section is important to display a common operational picture (COP) which may consist of a common map, Significant Activities (SIGACTS), video and other system views that are relevant to the mission and enable the CDR’s execution of Mission Command. The Large Screen Display enables an integrated view of multiple information systems, ensuring that everyone is working from the same Mission Command information. The Division has a total of 12 LSDs, 8 for the Main, 2 for the TAC, 1 for the Command Group and 1 for the Division Headquarters and Headquarters Battalion (HHB) . Some of the drawings show these in different locations as an example, but the totals remain 12. This is the same for the number of Crew Access Units (CAUs). Be sure to understand how best to use these assets for CP layouts.

4-4

4.2.3.3 Combat Net Radios (CNR) and Intercom System. CNR, or tactical radios, provide voice communications to all echelons on the battlefield. Within the CP, the CPCS provides any staff section with access to these radios and allows for internal intercom system. The Hard,Green Box, CAUs are a limited number but Soft CAUs can be downloaded to individual workstations for the same capability. Be sure to understand how best to use these assets for each CP layout. For more information on CNR and the CPCS see section 4.5.

4.2.4 Commanders establish and use systematic process and procedures to organize activities within a Command Post. Processes are a series of actions directed to and endstate, such as the military decision making process or execution of a Commander’s Update Brief. Procedures are standard, detailed steps, often used by staffs, which describe how to perform specific tasks to achieve the desired end state. For example, establishing the unit’s Command Post or establishing its COP.

4.2.5 The physical structure of the CP provides work space and the framework for the infrastructure.

4.2.5.1 The physical outdoor layout of the CP is composed of the Army-fielded Trailer-Mounted Support Systems (TMSS), associated Command Post vehicles and Central Power Solution. While the physical structure can be in an existing building or permanent shelter depending on the unit mission, for the purposes of this handbook we are looking at the CP utilizing it’s Army fielded equipment.

4.2.5.2 The TMSS encompasses a tent shelter, self-powered Environmental Control Unit (ECU), tables, and internal shelter lights. TMSS shelters are fielded in both medium (High-Mobility Multipurpose Wheeled Vehicle [HMMWV] towable) and large Light Medium Tactical Vehicle (LMTV/5-ton towable) shelters. Both sizes are fully compatible with each other and can be rapidly deployed in various configurations to provide well-lit, environmentally-controlled, weather-resistant shelters. The shelters are fielded for a mobile force to deploy anywhere in the world and operate in unimproved environments.

4-5

4.2.5.3 The infrastructure of the CP is depicted with diagrams of power generation and distribution, electrical grounding, fiber distribution, Secure Internet Protocol Routing (SIPR) data cable distribution, Non-Secure Internet Protocol Router (NIPR) data cable distribution, and CP Communication System (CPCS) cable distribution. Each may be tailored to the unit’s needs. Although shown in this handbook with the TMSS, the infrastructure can be adapted to any physical structure.

4.3 Establishing the Command Post

4.3.1 During the RESET Phase of ARFORGEN, a unit receives individual system training and puts each system into operation independent of the other Command Post components. To establish the Command Post as a System of Systems (SoS) for the first time, certain collective tasks need to be completed to configure and link all of the systems together. In addition to what a unit has been fielded, various supplies are needed that must be provided by the unit.

4.3.2 When establishing a CP, a unit should plan to conduct the tasks listed in Table 4.3.2-1.

Table 4.3.2-1. CP Initial Setup Tasks

TASK HANDBOOK SECTION Build data wiring bundles for both SIPR and NIPR networks

4.6, Network Cabling

Build power distribution grid 4.4, Power Distribution Customize CPCS coax cable wiring 4.5, Combat Net Radios Configure Combat Net Radios, antennas, and CPCS access units

4.4, Combat Net Radios

Validate data product 4.7, System Architecture Validate network configurations and Connectivity

4.7, Network Operations

4.3.3 During the setup validation of these CPs, various supplies are required. These supplies are not fielded by any program. Some supplies are required and others significantly facilitate the initial setup of a CP. Below is a full list with recommended quantities.

4-6

Table 4.3.3-1. Required Supplies for CP Setup

ITEM QUANTITY Step Ladder, 4' 1 per CP Power strips, 20 amp 5 per TMSS Med; 12 per

TMSS Lrg Extension cords, 50', heavy gauge 1 per TMSS Med; 3 per TMSS

Lrg Extension cords, 25', heavy gauge 3 per TMSS Med; 10 per

TMSS Lrg 30’ long sheathed grounding cables 2 per TMSS Safety goggles 1 per SWGS kit and 1 for tent

pegs 12 lb sledge hammer 1 per CP Lens cleaner, projector, kit 1 per CP D-rings, 3" 15 per TMSS Med; 25 per

TMSS Lrg Fuel cans 6 per TMSS Field chairs 12 per TMSS Med; 28 per

TMSS Lrg Coax cable, 75 Ohm, RG-59 500 ft BNC T-Connectors, 75 Ohm 5 per CP BNC male connector, 75 Ohm, RG-59 20 ea BNC barrel connectors, female, 75 Ohm 5 per CP BNC terminators, 75 Ohm 5 per CP CAT 5e, UTP, box, 1000ft, red (SIPR) 12 boxes CAT 5e, UTP, box, 1000ft, blue (NIPR) 5 boxes RJ-45 connectors 1000 ea TUFF Tables Based on unit SOP J-Stakes 25 ea TMSS Lrg Shelter repair kit 1 ea Fuse box w/ assorted fuses 1 ea Connector BNC female to N-type female 5 ea Headset, computer audio/mic, dual 3.5 mm

30 per BCT and 12 per Bn

Double sided Velcro, 1" wide 300 ft Zip ties, 6" 500 ea Zip ties, 12" 500 ea Heavy duty cable covers (floor/ground) Various

4-7

Figure 4.3.3-1. DIV Main CP – Power Distribution

4-8

Figure 4.3.3-2. DIV Main CP – Power Distribution and Grounding

4-9

Figure 4.3.3-3. DIV Main CP – SIPR/NIPR Network and CPCS Cable Distribution

4-10

Figure 4.3.3-4. DIV Main CP – Current Operations Cell – Modified Table of Organization and Equipment (MTOE) Position

4-11

Figure 4.3.3-5. DIV Main CP – Current Operations Cell Power Distribution and Grounding

4-12

Figure 4.3.3-6. DIV Main CP – Current Operations Cell – SIPR/NIPR Network and CPCS Cable Distribution

4-13

Figure 4.3.3-7. DIV Main CP – Movement and Maneuver/Special Staff Cell MTOE Position

4-14

Figure 4.3.3-8. DIV Main CP – Movement and Maneuver / Special Staff Cell Power Distribution and Grounding

4-15

Figure 4.3.3-9. DIV Main CP – Movement and Maneuver / Special Staff Cell SIPR/NIPR Network and CPCS Cable Distribution

4-16

Figure 4.3.3-10. DIV Main CP – Fire Support / Protection Cell MTOE Position

4-17

Figure 4.3.3-11. DIV Main CP – Fire Support / Protection Cell Power Distribution and Grounding

4-18

Figure 4.3.3-12. DIV Main CP – Fire Support / Protection Cell SIPR/NIPR Network and CPCS Cable Distribution

4-19

Figure 4.3.3-13. DIV Main CP – ADAM Cell - MTOE Position

4-20

Figure 4.3.3-14. DIV Main CP – FUOPS / Plans Cell - MTOE Position

4-21

Figure 4.3.3-15. DIV Main CP – FUOPS / Plans Cell Power Distribution and Grounding

4-22

Figure 4.3.3-16. DIV Main CP – FUOPS / Plans Cell SIPR/NIPR Network and CPCS Cable Distribution

4-23

Figure 4.3.3-17. DIV Main CP – Sustainment Cell - MTOE Position

4-24

Figure 4.3.3-18. DIV Main CP – Sustainment Cell Power Distribution and Grounding

4-25

Figure 4.3.3-19. DIV Main CP – Sustainment Cell - SIPR/NIPR Network and CPCS Cable Distribution

4-26

Figure 4.3.3-20. DIV Main CP – HRA/SJA Cell – MTOE Position

4-27

Figure 4.3.3-21. DIV Main CP – HRA/SJA Cell – Power Distribution and Grounding

4-28

Figure 4.3.3-22. DIV Main CP – HRA/SJA Cell – SIPR/NIPR Network and CPCS Cable Distribution

4-29

Figure 4.3.3-23. DIV Main CP – Mvmt & Mvr Cell – MTOE Position

4-30

Figure 4.3.3-24. DIV Main CP – Mvmt & Mvr Cell – Power Distribution and Grounding

4-31

Figure 4.3.3-25. DIV Main CP – Mvmt & Mvr Cell – – SIPR/NIPR Network and CPCS Cable Distribution

4-32

Figure 4.3.3-26. DIV Main CP – CMD Group Cell – MTOE Position

4-33

Figure 4.3.3-27. DIV Main CP – CMD Group Cell – Power Distribution and Grounding

4-34

Figure 4.3.3-28. DIV Main CP – CMD Group Cell – SIPR/NIPR Network and CPCS Cable Distribution

4-35

Figure 4.3.3-29. DIV Main CP – Entry Cell – MTOE Position

4-36

Figure 4.3.3-30. DIV Main CP – Entry Cell – Power Distribution and Grounding

4-37

Figure 4.3.3-31. DIV Main CP – Entry Cell – SIPR/NIPR Network and CPCS Cable Distribution

4-38

Figure 4.3.3-32. DIV Main CP – NETOPS-1 G6 HQ Cell – MTOE Position

4-39

Figure 4.3.3-33. DIV Main CP – NETOPS-1 G6 HQ Cell Power Distribution and Grounding

4-40

Figure 4.3.3-34. DIV Main CP – NETOPS-1 G6 HQ Cell SIPR/NIPR Network and CPCS Cable Distribution

4-41

Figure 4.3.3-35. DIV Main CP – NETOPS-2 – MTOE Position

4-42

Figure 4.3.3-36. DIV Main CP – NETOPS-2 – Power Distribution and Grounding

4-43

Figure 4.3.3-37. DIV Main CP – NETOPS-2 – SIPR/NIPR Network and CPCS Cable Distribution

4-44

Figure 4.3.3-38. DIV Main CP – INTEL-1/ACP – MTOE Position

4-45

Figure 4.3.3-39. DIV Main CP – INTEL-1/ACP – Power Distribution and Grounding

4-46

Figure 4.3.3-40. DIV Main CP – INTEL-1/ACP – SIPR/NIPR Network and CPCS Cable Distribution

4-47

Figure 4.3.3-41. DIV Main CP – INTEL-2 – MTOE Position

4-48

Figure 4.3.3-42. DIV Main CP – INTEL-2 – Power Distribution and Grounding

4-49

Figure 4.3.3-43. DIV Main CP – INTEL-2 – SIPR/NIPR Network and CPCS Cable Distribution

4-50

Figure 4.3.3-44. DIV Main CP – DTSS VAN Cell – MTOE Position

4-51

Figure 4.3.3-45. DIV Main CP – INTEL-3/SCIF – MTOE Position

4-52

Figure 4.3.3-46. DIV Main CP – INTEL-3/SCIF – Power Distribution and Grounding

4-53

Figure 4.3.3-47. DIV Main CP – INTEL-3/SCIF – SIPR/NIPR Network and CPCS Cable Distribution

4-54

Figure 4.3.3-48. DIV TAC CP - Topdown View

4-55

Figure 4.3.3-49. DIV TAC CP – Power Distribution and Grounding

4-56

Figure 4.3.3-50. DIV TAC CP - SIPR/NIPR Network and CPCS Cable Distribution

4-57

Figure 4.3.3-51. DIV TAC CP - Current Operations Cell - MTOE Position

4-58

Figure 4.3.3-52. DIV TAC CP - Current Operations Cell Power Distribution and Grounding

4-59

Figure 4.3.3-53. DIV TAC CP - Current Operations Cell SIPR/NIPR Network and CPCS Cable Distribution

4-60

Figure 4.3.3-54. DIV TAC CP - Intelligence / SCIF Cell MTOE Positions

4-61

Figure 4.3.3-55. DIV TAC CP - Intelligence / SCIF Cell - - Power Distribution and Grounding

4-62

Figure 4.3.3-56. DIV TAC CP - Intelligence / SCIF Cell – SIPR/NIPR Network and CPCS Cable Distribution

4-63

Figure 4.3.3-57. DIV TAC CP - Network Operations Cell MTOE Positions

4-64

Figure 4.3.3-58. DIV TAC CP - Network Operations Cell Power Distribution and Grounding

4-65

Figure 4.3.3-59. DIV TAC CP - Network Operations Cell SIPR/NIPR Network and CPCS Cable Distribution

4-66

Figure 4.3.3-60. DIV Headquarters and Headquarters Battalion (HHB) Command Post (CP) – Topdown View

4-67

Figure 4.3.3-61. HHB CP - Power Distribution and Grounding

4-68

Figure 4.3.3-62. HHB CP - SIPR/NIPR Network and CPCS Cable Distribution

4-69

Figure 4.3.3-63. DIV HHB CP - Current Operations Cell MTOE Positions

4-70

Figure 4.3.3-64. DIV HHB CP - Current Operations Cell Power Distribution and Grounding

4-71

Figure 4.3.3-65. DIV HHB CP - Current Operations Cell SIPR/NIPR Network and CPCS Cable Distribution

4-72

Figure 4.3.3-66. Div HHB CP - Sustainment Cell - MTOE Positions

4-73

Figure 4.3.3-67. DIV HHB CP - Sustainment Cell Power Distribution and Grounding

4-74

Figure 4.3.3-68. DIV HHB CP - Sustainment Cell - SIPR/NIPR Network and CPCS Cable Distribution

4-75

4.4 Power Distribution

4.4.1 The Army-fielded standardized CPs with the Network Information Systems suites are powered in a different way from previous versions. Rather than each particular system or item running off of its own generator, all are collectively powered from a single source. This concept is called Central Power. Power is provided by a Power Plant (PP) and supplied to the equipment through a network of cables and distribution equipment referred to in this guide as a “grid.” This guide provides an overview of the equipment and instructions on how to set up the Central Power grid. Units should identify/appoint in their SOP and train a Central Power operator who develops and supervises establishing the Central Power grid for all operations.

4.4.1.1 TQG. The Tactical Quiet Generators (TQGs), used to power the CPs, are all configured as PPs. Each PP consists of two generators, each on its own trailer and linked through a switch box and power cable. The two generator sets allow the CP to operate continuously, one is the main generator set the other serves as backup. The connection of the generator sets at the switch box allows the transfer of power and maintenance can be performed without interruption of power. The PPs used are the 15-kW AN/MJQ-48; the 30-kW AN/MJQ-40; and the 60-kW AN/MJQ-41. In addition, when available, backup power for each shelter in the CP is provided by either a 10-kW Auxiliary Power Unit (APU) or a 10-kW power unit, designated PU-798. Other TQGs can be found throughout the division, but for the purposes of CP power, this guide will only address the PPs listed above.

4.4.1.2 PDISE. The Power Distribution Illumination System Electrical (PDISE) system is a family of power distribution and illumination equipment which transmits electrical power between power-generation and power-using equipment. By adding components to meet specific organizational missions and requirements, it forms a consolidated power network. The PDISE system and the user’s electrical equipment are protected by circuit breakers within the PDISE equipment, rated at the maximum permissible load. The PDISE also:

4-76

• Permits using units more flexibility by consolidating power sources

• Provides flexibility to unit operations and can be quickly assembled/disassembled for rapid relocation

• Is designed for basic climatic (120° to -25°F [49° to -32°C]) and field conditions

• Is designed to be used with generator sets (120/208 VAC, 50/60 Hz, 5-200 kW), but is compatible with any similar power source (e.g., utility or “pole” power)

• Uses standard military connectors

4.4.1.3 The line distance from the PP to the load is limited to a total of 300 feet (91.4 m) at maximum load; anything longer would cause an unacceptable voltage loss. Various types of PDISE and ancillary equipment are listed below.

4.4.1.4 The M100 is the central distribution point for the CP power, and connects the PP to the shelters and to the smaller boxes (M40). They enable the user to move the PP away from the CP and reposition the M100 as needed It also serves as a circuit breaker box for the CP, identical in operation to residential circuit breaker boxes. The M100s are sometimes referred to as “turtles” or “big hibachis.” Two M100s are used with each MJQ-41 power cable and one is used with each of the MJQ-40 and MJQ-48 power cables. Each M100 is equipped with phase indicator lights that indicate the presence of input power.

4.4.1.5 The M40 acts as a “branch circuit” for the CP. It is a smaller distribution box that provides rows of electrical outlets which, when used with the M46, allows CP operators the flexibility to power electrical and electronic equipment (servers, UPSs, laptops, cell phone chargers, etc.) directly from the PPs. At the Division and HHB CPs, the M40 connects to the M100. At the BNs, the M40 wires directly into the terminal lugs on the switch box of the MJQ-48. The M40 also functions in the same capability as a residential circuit breaker box. The M40 comes with some cables and duplex receptacle boxes to power the loads. It also comes with a portable Ground Fault Circuit Interrupter (GFCI) adapter to protect any extension cable going outside the tent or in an area where water may be present.

4-77

4.4.1.6 The M46 Electrical Distribution Kit contains the electrical outlets and cables that allow users to plug their equipment into the PP. Each M46 kit consists of drop boxes with electrical duplex receptacles, branch cables for connecting and stringing up the drop boxes, and extension cables that run from the PDISE box to the branch cables. In general, two M46s are issued with each M40. They can also be connected to the small 20 A connectors on the M100. The M46 is equipped with a portable Ground Fault Circuit Interrupter (GFCI) adapter to protect any extension cable going outside the tent or in an area where water may be present.

4.4.2 General Guidelines for Setup

4.4.2.1 Power Plant Setup

• Setup and grounding of each PP is covered in the TM for that TQG. THE TQGS MUST BE GROUNDED PRIOR TO STARTUP!

• Each PP consists of an A and a B unit. The A unit has the switch box. The B unit has the power cable. Each PP has two paralleling cables, one for each generator. On the MJQ-40, MJQ-41, and MJQ-48, they are stored inside the rear doors, along with the auxiliary fuel hose. Remove the cables from storage and install using the following steps:

1. Connect one end of the paralleling cable to connector J3 on the switch box located on unit A. Route the other end of this cable through the power cable sock and connect to connector J16 on unit B. The J16 receptacle is found inside the load terminal area in the far upper left corner. This provides power to the switch box. This connection can be difficult to secure; the cable has to seat properly for the switch box to work.

2. Connect the second paralleling cable between the two paralleling receptacles on the generator set control panels. This allows the TQGs to “talk” to each other.

3. Once these two cables are connected, ensure they do not form an X. If they do, the cables are connected incorrectly.

4-78

4. Unwrap the power cable from around unit B, but do not disconnect it from the unit B. Connect the plug end of the power cable to port J2 of the switch box on unit A. Route the other end of the cable through the power cable sock and connect leads to appropriate load terminals on unit B. Leads will be labeled with load terminal designations.

5. For detailed instructions and diagrams, refer to TM 9-6115-663-13. These TMs are provided with the generators, and can be accessed online through the LOGSA Website (https://www.logsa.army.mil/etms/online.cfm) or the PM-MEP Website (https://www.pm-mep.army.mil/logistics/index.html).

4.4.2.2 Connecting M100s to PPs

• Each M100 is supplied with two 50-ft feeder cables and one 4-ft pigtail used to connect the M100 to the power plant. Each power plant has a switch box that combines the power produced by the TQGs, and provides a safe, common connection point. The power is taken off the switch box through the terminal lugs found on the side of the switch box. ONCE THE PIGTAIL IS CONNECTED TO THE LOAD TERMINALS, IT DOES NOT COME OFF!

• The pigtail from the M100 connects to the switch box terminal lugs. The marking on the switch box (G, N, L1, L2, L3) matches the marking on the pigtail. The wires are color coded but different manufacturers/contracts may have different colors so be alert to specific instructions included in the operating manuals. In general the wires are color coded as follows:

• The wires are also color coded:

1) Green = ground = G 2) White = neutral = N or L0 3) Black = Phase A = L1 4) Red = Phase B = L2 5) Orange or Blue = Phase C = L3

4-79

Figure 4.4.2-1. M100 Pigtail Connection to TQG

4.4.2.3 Connecting Shelters to M100s

• Each shelter mounted on a HMMWV has one 50-ft cable and one 10-ft pigtail, both rated for 60 A. Prior to connecting anything to the M100, ensure the connector to be used is OFF. This is done by switching the appropriate circuit breaker into the OFF position.

• For the CPP and ADAM shelters, use the 50-foot vehicle cable to connect from the J1 port on the power entry panel to a 60-A rated port on the M100 (J3 or J6). Other shelters (such as DTSS) can use J4 or J5 on the M100. After the cable is connected, close the appropriate circuit breaker. Ensure shelter power requirement of 40 or 60 A prior to connecting power. See Figure 4.4.2-2.

4-80

Figure 4.4.2-2. M100 Connections

4.4.2.4 PDISE: M40, M46

• The M40 PDISE boxes are used in conjunction with the M46 electrical distribution kit to provide a place to plug in electrical and electronic equipment. Use the large feeder cables that come with the M40. Connect the cables to the J1 port on the M40 and a port rated for 40 A on the M100 (J4 or J5; Figure 4.4.2-3).

Figure 4.4.2-3. M40 Connections

4-81

• The M40 receives 3-phase power and splits each phase to separate connectors. On each side of the M40 are two connectors for each phase. These connectors alternate – ABCABC. A corresponds to L1 on the TQG, B corresponds to L2, and C corresponds to L3.

• When connecting the M46 cables to the M40, use groups of three connectors. This keeps the total load balanced on the generator, and prevents overloading any one phase. Use the C connector first, then B, then A, and then repeat as needed.

• The M46 branch is one line with three outlet boxes. Each box has four outlets. The entire line is connected to one 20-A circuit breaker. When connecting, go in numerical order, i.e., J3, then J4, then J5. This ensures each phase gets loaded, and that C is guaranteed a load. The items that are connected to each branch are METT-TC dependent.

• If a portable GFCI adapter is available (part of the M40 or M46), connect the male end of the GFCI adapter to the M40 output connector first, then connect to the other M46 cable to the female end. Run the extension cable protected by the GFCI adapter to the location where water may pool or may be present.

4.4.3 General Operation

4.4.3.1 Start and Parallel PPs

• Start one generator and apply load as per the TQG operation instructions. To parallel the TQGs or transfer load from one to the other, follow the instructions below. These instructions are also on the inside of the switch box control panel door. For detailed instructions and diagrams, refer to the PP TM.

• To start the MJQ-48: the DEAD CRANK switch must be in the NORMAL position, the DC Control Power circuit breaker must be pushed in, and the Emergency Stop Switch must be in the OUT position. Move the MASTER SWITCH to the START position and HOLD until the frequency gauge reads 60 Hz, the voltage gauge reads 120 volts, and oil pressure is at 60 psi. Once the generator set is running, move the AC CIRCUIT INTERRUPTER switch to the CLOSED position to supply power to the load. If the generator set’s STATUS light is on, move the ON/OFF switch at the switch box to the ON position to supply power to the load.

4-82

• Use to following steps to parallel the MJQ-48. Gen 1 is the generator that is on; Gen 2 is the generator that is off.

1. Start the vehicle engine to supply power to the shelter equipment (except the ECU), while transferring power to the TQGs.

2. On Gen 1, set UNIT-PARALLEL switch to PARALLEL.

3. Start Gen 2. Adjust VOLTAGE and FREQUENCY to match Gen 1.

4. On Gen 2 switch box, set ON-OFF switch to ON. ON LINE and STATUS lights should illuminate.

5. At Gen 2, set UNIT-PARALLEL switch to PARALLEL. Both SYNCHRONIZING lights should be flashing at the same time.

6. Increase frequency until SYNCHRONIZING lights flash in sync one or more times per second.

7. Decrease FREQUENCY until lights flash in sync once every 3 to 4 seconds.

8. When lights are off, set Gen 2 CIRCUIT INTRPT SWITCH to CLOSE. Gen contactor light should illuminate and SYNCHRONIZING lights should go out.

9. At Gen 1, set CIRCUIT INTRPT SWITCH to OPEN, set UNIT-PARALLEL switch to UNIT. Turn MASTER switch to STOP. At switch box, ON LINE and STATUS lights should be off.

10. At Gen 2, set UNIT-PARALLEL switch to UNIT.

Use the following steps to start the MJQ-40 and MJQ-41:

1. Move the MASTER CONTROL switch to the ON position and allow the Computer Interface Module (CIM) to load.

2. Once the CIM software has loaded, clear any faults previously registered on the CIM display screen by holding the FAULT RESET switch in the ON position for 5 seconds.

3. Hold the ENGINE CONTROL switch in the start position until frequency gauge reads 60 Hz, and the voltage gauge reads 208 volts.

4-83

4. Once the generator set is running, supply power to the load by moving the AC CIRCUIT INTERRUPTER switch to the CLOSED position. The green light should come on.

5. On the generator set with a STATUS light on, move the switch box ON/OFF switch to the ON position to supply power to the load.

• Use the following steps to parallel the MJQ-40 and MJQ-41. Gen 1 is the generator that is on; Gen 2 is the generator that is off.

1) Start the vehicle engine to supply power to shelter equipment (except the ECU), while transferring power to the TQGs.

2) Start Gen 2. Adjust VOLTAGE and FREQUENCY to match Gen 1.

3) At the Gen 2 switch box, set ON-OFF switch to ON. ON LINE and STATUS lights should illuminate.

4) Set Gen 2 CKT INTRPT SWITCH to CLOSE. Contactor position on CIM display screen reads CLOSED.

5) At Gen 1, set CKT INTRPT switch to OPEN. Turn ENGINE CONTROL switch to STOP. At switch box, ON LINE and STATUS lights should go off.

4.4.3.2 Use the following steps to switch from on-board power to import power:

1) If an APU is installed in the shelter, turn off APU and remove the feeder cable at the J1 import connector of the shelter’s Power Entry Panel (PEP). BEFORE CONNECTING THE CABLE AT THE M100, MAKE SURE THE CIRCUIT BREAKER ASSOCIATED WITH THE CONNECTOR IS TURNED OFF!

2) Connect the 50-ft, 60-A feeder cable supplied with the CPP from a 60-A rated port on the M100 (J3 or J6) to the J1 Import connector on the CPP’s PEP.

3) With the connections made, first turn the circuit breaker at the M100 to the ON position, and then turn the IMPORT POWER circuit breaker and the DC POWER SUPPLY circuit breaker at the shelter’s PEP to the ON position.

4-84

4) To verify power at the PEP, press the PUSH TO TEST button and the three PWR SUPPLY AC INPUT and PWR SUPPLY DC OUTPUT LEDs should illuminate.

4.4.4 PDISE Placement – General Guidance

4.4.4.1 Division Main CP

• The Division Main CP uses two 60-kw PPMJQ-41s and one 30-kw PP MJQ-40 as the primary power sources. One MJQ-41 provides power to the CUROPS, PLANS/FUOPS, SUSTAINMENT, HRA, MVT & MVR and CMD GRPS tents in Power Zone 3. The second MJQ-40 provides power to the FIRES, INTEL, and MVT&MVT tents, as well as the shelters supporting the INTEL section in Power Zone 1. The MJQ-40 provides power to the two NETOPS tents, as well as the JNN shelter in Power Zone 2. If the CMD GRP CPP is included in the Main CP, the MJQ-40 also provides power to this CPP.

• Power Zone 1. Place one M100 inside the INTEL wire close to the DTSS vehicle and the second M100 outside the wire by the FIRES tent end cap. The M40s go in the INTEL-2, FIRES, and CUROPS tents. (See figure 4.3.3-2)

• Power Zone 2. Place the M100 outside the NETOPS-2 tent near the JNN shelter. The M40 goes in NETOP-2 tent. (See figure 4.3.3-1)

• Power Zone 3. Place one M100s between the SUSTAINMENT and MVT & MVR tents, and the second M100 between the CMD GRP and PLANS/FUOPS tents. The M40s go inside the SUSTAINMENT and MVT & MVR/SPECIAL STAFF tents.

• Use the branch cables and two or three outlet boxes in the M46 to run a line of outlets for items like the TMC-Client WS, laptops, cell phone chargers, etc. Use the extension cables to provide a single power drop for items such as the TMC Servers. Provide a single power drop for the coffee pot to share with items that draw a lot of power, but are used infrequently, such as printers, plotters, or shredders. When connecting the M46 cables to the M40, use groups of three connectors. This keeps the load balanced on the generator and prevents overloading any one phase. Put the larger load on L3.

4-85

4.4.4.2 Division TAC CP

• The Division TAC uses one 60-kw PP MJQ-41 and one 30-kw PP MJQ-40 as the primary power sources. The MJQ-41 provides power to the CUROPS and NETOPS tents, as well as the CPPs and the JNN shelters. The MJQ-40 provides power to the INTEL tent, as well as the TROJAN SPIRIT and DTES shelters.

• Place the M100 outside the NETOPS tent between the MJQ-41 and CPP-A. After tents are set up, connect the M100 to M40s in CUROPS and NETOPS tents.

• Place an M40 in the INTEL tent and connect it to the MJQ-40.

• Use the branch cables and two or three outlet boxes in the M46 to run a line of outlets for items like the TMC-Client WS, laptops, cell phone chargers, etc. Use the extension cables to provide a single power drop for items such as the TMC Servers. Provide a single power drop for the coffee pot to share with items that draw a lot of power, but are used infrequently, such as printers, plotters, or shredders. When connecting the M46 cables to the M40, use groups of three connectors. This keeps the load balanced on the generator and prevents overloading any one phase. Put the larger load on L3.

4.4.4.3 HHB CP

• The HHB CP uses one 15-kW PP, MJQ-48, as the primary power source. Place the M40 inside the access control tent. Park the PP no more than 50 ft from the M4.

• Use the branch cables and two or three outlet boxes in the M46 to run a line of outlets for items like the TMC-Client WS, laptops, cell phone chargers, etc. Use the extension cables to provide a single power drop for items such as the TMC Servers. Provide a single power drop for the coffee pot to share with items that draw a lot of power, but are used infrequently, such as printers, plotters, or shredders. When connecting the M46 cables to the M40, use groups of three connectors. This keeps the load balanced on the generator and prevents overloading any one phase. Put the larger load on L3.

4-86

4.4.5 Address questions/comments about this guide or TOC power to:

PM-Mobile Electric Power

ATTN: SFAE-CSS-ME (R. Nutter)

10205 Burbeck Rd, Suite 105

Ft. Belvoir, VA 22060-5863

Phone: DSN 654-3802, Comm 703-704-3802

E-mail robert.nutter.civ@mail.mil or jose.santos8.civ@mail.mil.

4.5 Combat Net Radios (CNR) and CP Communication System (CPCS)

4.5.1 The system includes the FM very high frequency (VHF) SINCGARS, high frequency (HF) AM radios, and TACSAT radio systems. Figure 4.5.5-1 is an example of CNR employment.

4.5.2 Single Channel Ground Air Radio System (SINCGARS)

4.5.2.1 SINCGARS is the most widespread communications system, found in all units. These radios are portable, mobile, and can be used on the move easier than other CNR systems. Although limited in range, their reach can be extended with directional antennas, retransmission stations, or relays.

4.5.2.2 SINCGARS transmits both voice and limited data traffic and resists jamming and other electronic attack techniques by frequency hopping. Imbedded communications security (COMSEC) further contributes to survivability.

4.5.3 High Frequency (HF) Radios HF AM radios extend ranges beyond that possible with VHF radios such as SINCGARS. They are reliable, with good frequency management and antenna selection and can be used in a retransmission mode to extend the ranges of VHF nets. Current available versions are the vehicular-mounted, short-range AN/GRC-213 and the long-range AN/GRC-193 HF radios. Both support secure voice and data transmission.

4-87

4.5.4 Tactical Satellite (TACSAT) Radios

4.5.4.1 TACSAT radios carry both voice and data traffic globally, eliminating distance constraints inherent in other CNR systems. Range is the main advantage of TACSAT radios for beyond-line-of-sight capability. For contingency operations, CORPS and DIV need to include TACSATs in mission command architecture planning.

4.5.4.2 Higher Echelon Commanders (Division/Corps/ASCC) can direct that single-channel Earth stations be provided to subordinate BDE-sized elements if distances or terrain exceed other CNR system capabilities.

4.5.5 Command Post Communication System (CPCS)

4.5.5.1 Tactical Operations Center Intercommunication System (TOCNET™) provides an expandable approach to voice and data communications for field tactical mission command personnel. The system consists of three different Line Replaceable Units: Enhanced Micro Central Switching Unit (eMCSU), Desktop Crew Access Unit (CAU), and Soft CAU. Each eMCSU with attached communication assets comprises a node. Different sized systems can be constructed by adding or deleting nodes. Multiple nodes (up to 64) can be networked to form one larger system with up to 1024 assets (radios, phones, CAUs, etc.).

4.5.5.2 TOCNET enables users to interface and remotely manage tactical radio assets and other communication applications consistently, regardless of platform, while reducing training and logistical impact. Workstations and radios can be configured easily and replicated in all common stations with access to CAUs not physically on the platform.

4.5.5.3 Extended Voice Communication (EVC) provides the capability to interconnect many TOCNET systems. The radio cross-banding function can be easily accomplished, resulting in optimal use of each platform’s resources, and transparent to off-platform users.

4-88

4.5.5.4 The eMCSU’s configuration file allows control of the following radio equipment:

• SINCGARS RT-1523E via a PPP serial or Ethernet connection to the INC

• SINCGARS RT-1523E through a direct RS-232 connection • ARC-231 through a direct RS-232 connection • PSC-5D through a direct RS-232 connection • ARC-220 through a direct RS-232 connection • PRC-117F through a direct RS-232 connection • PRC-150 through a direct RS-232 connection • STE-R through a direct RS-232 connection

Figure 4.5.5-1. CNR Deployment Example

4.6 Network Cabling

4.6.1 The methods outlined in this handbook provide best practices and procedures for the installation and utilization of physical network assets. Installation of a CP Local Area Network (LAN) from a distribution point (e.g., CPP or data access case) to end user can be performed more efficiently once the end user systems are positioned within the CP.

4-89

4.6.2 Equipment should be emplaced but not connected until a final layout is obtained. The use of a diagram or notional architecture allows for concurrent execution in various cells within a CP. When running cable from the distribution point to the end user, the installer should route the cable according to the plan outlined in this handbook or unit Standard Operating Procedure (SOP). Once sections of a specific cell have been wired, class-specific wires can be bundled into harnesses utilizing hook-and-loop ties. Single-use nylon zip ties should not be used for cable bundling since over tightening may damage cabling.

4.6.3 Class-specific wiring harnesses increase efficiency in establishment and subsequent displacement of the CP. In accordance with NSA 73-2A TEMPEST, SIPR and NIPR cables running in parallel for distances greater than 30 m must be 15 cm from each other. For more security requirements, refer to NSA 73-2A and other TEMPEST-related regulations.

National Security Telecommunications and Information Systems Security Advisory Memorandum (NSTISSAM) TEMPEST/2-95, RED/BLACK Installation Guidance specifies RED/BLACK equipment/system installation guidance, provides an explanation of the TEMPEST policy concept, and addresses RED/BLACK considerations for facilities wherein national security information is processed. This publication supersedes National COMSEC Information Memorandum (NACSIM) 5203, dated 30 June 1982. However, Appendix K of NACSIM 5203 will remain in effect until NACSI 4009, Protected Distribution Systems, dated 30 December 1981, is superseded. NACSI 4009 is currently under revision.

4.7 Network Operations and System Architecture

4.7.1 The purpose of this chapter is to outline key components of Network Operations (NetOps):

• Capabilities and responsibilities for supporting military operations

• Commander’s role and responsibility concerning the establishment of network priorities

• Guidance for facilitating both internal connectivity as well as external connectivity to the Global Information Grid (GIG)

4.7.2 In addition, this chapter will highlight the fact that the network reaches far beyond the tactical boundaries of the battlefield, crossing operational and strategic echelons up to the

4-90

Department of Defense in support of the Land War Net (LWN). This chapter will also discuss:

• Specific network management activities, functions, and tasks performed by network managers

• An overview of Information Assurance (IA) (including responsibilities, tools, and incident reporting)

• An overview of Information Dissemination Management (IDM) as an enabler of information management

4.7.3 Role of NetOps

4.7.3.1 As technology continues to advance the development of more sophisticated weapons systems, so does reliance on the network to integrate these systems in order to achieve their desired effects. In this light the network can and should be considered a weapons system, equal to any of the traditional combat platforms, which provides commanders shared situational awareness, enhanced speed of command, and task force synchronization. This is an important distinction to make, especially when discussing what comprises a weapons system. The DoD definition of a weapons system is “...a combination of one or more weapons with all related equipment, materials, services, personnel, and means of delivery and deployment (if applicable) required for self-sufficiency” (As listed in Approved Joint Definitions, Acronyms, and Abbreviations contained in Joint Publication 1-02, DOD Dictionary of Military and Associated Terms 08 November 2010, as amended through 15 August 2011.

4-91

Figure 4.7.3-1. Network Operations

4.7.3.2 When comparing a traditional weapon system with the network, they both utilize the exact same components to put them into operation. These components are listed below:

• Training • Preventative Maintenance • Function Checks • Operation • Capabilities • Limitations • Corrective Actions • Management • TTPs • Crew Roles and Responsibilities

4.7.3.3 As this list shows, whether a combat or network platform, mission success depends on a detailed operational (and functional) understanding if the system capabilities and limitations in order to properly apply the system to the fight.

4-92

4.7.3.4 NetOps provides the over-arching management of these capabilities and can be prioritized based on the commander’s intent and guidance.

4.7.3.5 NetOps is defined as the operational construct consisting of the essential tasks and Situational Awareness (SA) that the commander uses to operate and defend the tactical network and its connectivity to the GIG. In this construct, NetOps allocates network, information system, information security, and information resources directly in support of the warfighter. Although immediate operational commanders “own” the network, they grant control, operation, and oversight to the senior signal officer and staff. NetOps control is granted by the operational commander in order to ensure the day-to-day compliance of the network with the associated Tactical Information Grid (TIG) and GIG requirements. Due to the fast moving nature of NetOps and its 24/7 operation, NetOps requires quick decisions and adjustments in order to fully support the dynamics of an ever-changing battlefield. NetOps enables the commander by providing assured network availability, information protection, and information delivery.

4.7.4 Key Components

4.7.4.1 NetOps is the critical fusion point in the CP that combines infrastructure and services that provide processing, storing, and transporting information across the network. The functional areas that comprise this infrastructure and services consist of the wireless area network (WAN) and LAN management, mission command systems, IA, Communications Security (COMSEC), and Electromagnetic Spectrum Operations (EMSO). Each of these areas is interrelated. As such, they cannot be viewed and operated as single stove-piped systems, but instead must be viewed from a holistic approach. It is also important to understand that these areas are executed at both the Division/Corps/ASCC/EAD Formations and BCT level and, therefore, must be synchronized both horizontally and vertically between the two echelons so the shared bandwidth, spectrum, and GIG (network) access is properly managed. NetOps provides this management by:

4-93

• Identifying the user’s information requirement (who, what, when, where)

• Identifying which network, information systems, and security architecture (hardware and software configuration management) is required

• Ensuring availability and access to networks • Applying the right technology and equipment • Protecting network resources and user information with IA

security measures • Ensuring the right information is disseminated to users in a

usable format at the right time and place

4.7.4.2 The synchronization between the BCTs and Divisions and Higher HQs cannot be overlooked and marginalized. Although the Division/Corps/ASCC G-6s do not own the signal assets in the BCTs (this includes signal personnel as well) all network configuration changes and WAN transport equipment (WIN-T/JNNs and specifically satellite terminal) locations must be coordinated with the next NetOps echelon. The Division and Above Echelons do control assigned enabler Signal assets such as Expeditionary Signal Battalions (ESBs) and Theater Tactical Signal Brigades (TTSBs), and Theater Strategic Signal Brigades (TSSBs). Failure to do so will significantly impact not only the subordinate affected BCTs and other Formations, but the entire tactical network as well. There must be an informal command relationship between the Division (and/or Corps/ASCC) G-6 and supported S-6s in regard to network operations and management. Although as an example the BCT commanders have the right to move assets based on operational necessity, the BCT S-6 and other supported Formation S-6s still have the requirement to coordinate any configuration changes, report network incidents, and highlight future operations and any additional network requirements needed for support of those operations. The Division/Corps/ASCC G-6s have the same responsibilities.

4-94

4.7.5 Organizational Structure and Force Multipliers

4.7.5.1 As mentioned earlier, the operational commander grants network control to the senior signal officer in the organization. In the Division this would be the G-6. Although the G-6s are considered primary staff officers, they have the authority to make “command” decisions and changes to the tactical network in order to ensure that it operates at maximum efficiency. The mission statement for the G-6s at Division and higher echelons is listed below:

The G-6 (CIO) integrates, manages, and provides operational oversight for the mission command system architecture ensuring the availability, reliability, and security of voice, video, and data networks that support robust, adaptable, and survivable mission command capability for the Commanding General and subordinate US and coalition commanders throughout the Area of Operations (AO).

4.7.5.2 Division G6 Responsibilities. These responsibilities are similar to the Corps and ASCC G-6. We will focus on the Division G-6 with the idea that these duties are applicable to Corps and ASCC as well. The G6 is the principal staff officer and senior advisor to the Division Commander for all matters concerning communications and networks. The G-6 has the technical authority over the division information networks including Training Readiness Oversight (TRO) of the DNOSC, subordinate signal units and signal personnel. The G-6 is responsible for planning, designing, and directing the Division NetOps and Security Center (DNOSC) to execute the Information Systems Mission Command (previously called C4) plan in support of the division commander’s intent. By executing the commander’s intent, the G-6 directs all technical changes to the network. To make physical moves to signal equipment, the G-6 produces a Technical Support Order (TSO) and recommends Fragmentary Orders (FRAGOs) to direct such movement with the G-3. The G-6 is responsible for advising the division commander, staff, and subordinate commanders on Information Systems operational matters (staff responsibilities, technical authority, and training readiness oversight). G-6 staff responsibilities include–

4-95

• Prepare, maintain, and update Information Systems operations estimates, plans, and orders. These orders will often cause configuration management changes across multiple brigades.

• Monitor and make recommendations on all technical Information Systems operations.

• Act as the Army Forces’ (ARFOR) G-6 when needed (equipment and personnel augmentation will be required to support this mission). Refer to FM 6-02.71, Network Operations for more information.

• Advise the commander, staff, and subordinate commanders on Information Systems operations and network priorities for mission command (e.g., changing bandwidth allocation to support the division main effort—a brigade reinforced with additional Information Collection (IC) assets).

• Direct technical changes to all portions of the division network via the TSO process.

• Act as the JTF J-6, if required. Equipment and personnel augmentation will be required to support this mission and will be provided by the corps and/or theater as necessary. Refer to FM 6-02.71, Network Operations for more information.

• Oversee development, production, changes, updates, and distribution of the Signal Operating Instructions (SOIs).

• Direct preparation and or publication of Information Systems operations SOPs for division command posts.

• Coordinate, plan, and manage division spectrum management within its Area of Responsibility (AOR).

• Plan and coordinate with higher and lower headquarters regarding information systems upgrade, replacement, elimination, and integration.

• Coordinate with G-2, G-3, G-7, and the operational CoC to plan and direct all IA activities and Information Systems operations vulnerability and risk assessments.

• Coordinate with staff of a variety of external agencies to develop the information and communications plans, manage the information network, obtain required services, and support mission requirements.

• Confirm and validate user information requirements in direct response to the tactical mission.

4-96

• Establish Information System policies and procedures for the use and management of information tools and resources.

4.7.5.3 Technical Authority Responsibilities. The following are the technical authority’s responsibilities

• Provide signal unit operations sections with direction and guidance during preparation of network plans and produces diagrams establishing the information network (WAN).

• Plan and integrate information systems and mission command equipment due to unit task organization/reorganization.

• Coordinate with the corps and JTF to plan and direct all NetOps activities within the division AOR.

4.7.5.4 Training Readiness Oversight Responsibilities. The following are the TRO responsibilities:

• Ensure the development of required skills to all signal personnel within the division AOR.

• Develop and mentor all signal officers, including career management.

• Coordinate with G-1 to identify requirements and manage the distribution of signal personnel within the division.

• Ensure the division NSC is trained to support division missions and tasks.

4.7.6 Division NetOps and Security Center (DNOSC) This applies to Corps and ASCC as well.

4.7.6.1 The Division G-6 employs a fully integrated NetOps and Security Center (NOSC), providing all NetOps functions for the division. It has combined key assets within the G-6 sections (primarily NetOps, Ops, LAN, WAN). All division signal elements must coordinate with the NOSC during the engineering, installation, operation, maintenance, and defense of the division information network. It has overall responsibility for establishing the division information network and provides the operational and technical support to all of the division signal elements in its AOR.

4-97

4.7.6.2 The division NOSC performs the NetOps activities, functions, and tasks required to create a dynamic and responsive network. This network also quickly shifts priorities in order to support the ground tactical plan. This management function extends the strategic GIG capabilities into the responsive, dynamic, and tactical formations.

4.7.6.3 In order to increase responsiveness of a complex network and to facilitate the bandwidth required to support the division headquarters and brigade networks, the division employs a NetOps cell with the Tactical Hub Node (THN). The THN reallocates the TDMA satellite network structure and increases the bandwidth capability from approximately 6 Mbps to 40 Mbps. The embedded NetOps cell provides the management to enable the division network. In addition, by expanding bandwidth, the division has the capability to dynamically re-assign the bandwidth so that the communications support plan can match the division commander’s ground tactical plan. The division G-6 matches the communications support plan enabling the added, non-organic, capability by allocating a larger segment of the division enabled bandwidth.

4.7.6.4 DNOSC Responsibilities. The following are the DNOSC responsibilities:

• Coordinate with the operational CoC and subordinate organizations to monitor, manage, and ensure implementation of Network Management, Information Dissemination Management, and IA activities.

• Provide near-real-time awareness of division networks and systems to the division G-6.

• Coordinate actions to resolve attacks/incidents on the division network with subordinate organizations.

• Coordinate operational procedures and requirements for IA and Information Systems Security (ISS) with the operational CoC and supporting corps Regional Computer Emergency Response Team (RCERT).

• Coordinates wit subordinate NSCs to monitor, manage, and control intra-division information network components.

• Monitor the operation of the networks in the division’s subordinate units.

• Provide support and assistance to the subordinate NOSCs Administer the organizational message system (Defense

4-98

Message System [DMS]) in the division, including managing network addresses and sub-domains.

• Coordinate operation and maintenance support of mission

command system. These systems are attached to support deployed division forces with the split-base and reach operations capability to the home base.

• Share Network Management information with other management or monitoring centers.

• Provide the supporting ARFOR NOSC with near-real-time information on the status and performance of inter-division networks.

• Order and account for all forms of COMSEC material, including storing keys in encrypted form and performing key generation and automatic key distribution.

• Perform COMSEC material accounting functions and communicates with other COMSEC elements.

• Perform Information Dissemination Management/Combat Service (IDM/CS) functions to support all aspects of relevant information dissemination.

• Provide near-real-time awareness of division networks and systems that support the joint backbone to the Joint Task Force Joint Communications Control Center (JTF JCCC) when the division is serving as the ARFOR.

• Inform the G-6 of network outages and shortcomings that require the electronic maintenance shop.

4.7.7 Netops at the BCT and other attached units, such as a TSC, TAC or EN Command. For brevity we will refer to the BCT/EAD Formations in this Section.

4.7.7.1 As part of the overall LWN construct, the BCT is now considered the centerpiece of the Army fighting force. As such, the BCT could be called upon to deploy and conduct operations independent of their organic command structure. To do this, the BCT must be able to establish, operate, and maintain its own network for the duration of the operation. This includes the establishment of a central integrated section dedicated to execute NetOps functions and is manned by the S6 section, Signal Company personnel and assigned government and civilian contractors. Figure 4.7.7-1 shows the BCT hierarchy. A TSC or EN Brigade would have a similar

4-99

hierarchy.

Figure 4.7.7-1. BCT Hierarchy

4.7.7.2 The Brigade/Supporting Command (unit) Signal Officer G-6 (S-6) organization is augmented by their organic Signal Company or assigned Signal assets to provide a robust Network Operations and Security Center (NOSC). The Brigade/EAD S-6 could not operate without direct support/attachment of those key personnel. The Brigade/EAD organization provides both the tactical support for the supporting unit and also the interface with the Division for all Mission Command Information System issues. The brigade/supporting unit S-6 section is task organized to best support the commanders’ intent, normally located within the brigade command posts to support the commander’s communications requirements across the AO.

4.7.7.3 The S-6 is the principal officer for all matters concerning communications and networks for a fully digitized unit with assigned/attached units for that echelon and mission set.

4-100

Responsible for advising the commander and staff on all aspects of the mission command system (Formerly Command, Control, Communications, and Computer Operations (C4OPS), COMSEC, automation, and ensuring all aspects of mission command system are ready to conduct combat operations. Due to the dynamics of having signal assets assigned to multiple separate organizations, the S-6 must first have the support of the EAD commander and develop a close working relationship with the subordinate and supporting unit battalion commanders, each of the battalion S-6s, and the Division G-6 (or other assigned Higher HQs in the AOR). The EAD formations G-6 (S-6) is also responsible for the maintenance and employment of FBCB2, lower and upper tactical internet, automation, strategic, TACSAT, FM, HF, MSE, and UHF tactical communications systems, and the digital connectivity between all echelons. The EAD G-6(S-6) works closely with the higher hqs, such as the Division G6, the Division Network Signal Company Commander (NSC) and any other signal assets in the AOR. The EAD NSC commander works closely with any other BCT/FSB/MfSB/EAD S-6s when deployed. In addition, the EAD S-6 has technical authority over all EAD Bde Signal unit equipment. When the EAD Bde operates independently, though not normal, the S-6 performs all of the same duties and responsibilities as the Division G-6.

4.7.7.4 Brigade/EAD G-6 (S-6) Responsibilities:

• Prepare, maintain, and update mission command system operations estimates, plans, and orders. Orders will often cause configuration management changes across multiple battalions.

• Monitor/make recommendations on technical mission command system operations.

• Designated as the ARFOR G-6 when needed. Equipment and personnel augmentation required to support this mission.

• Advise the commander, staff, and subordinate commanders on mission command system operations and network priorities for mission command.

• Develop, produce, change/update, and distribute SOI. • Prepare/Publish mission command system operations

SOPs for BCT/EAD CPs.

4-101

• Coordinate, plan, and manage BCT/EAD spectrum within its AOR.

• Plan and coordinate with higher and lower headquarters regarding information systems upgrade, replacement, elimination, and integration.

• Coordinate with each subordinate unit S-2 and S-3 to plan and direct all IA activities and mission command system operations, vulnerability, and risk assessments.

• Coordinate with staff from a variety of external agencies to develop the information and communications plans, manage the information network, obtain required services, and support mission requirements.

• Confirm and validate user information requirements in direct response to the tactical mission.

• Establish mission command system policies and procedures for the use and management of information tools and resources.

4.7.8 Tool Sets NetOps tools enable network managers G-6 (S-6) to get near-real-time information on the status and health of the integrated network (LAN, WAN, and CNR) to enable commanders to make sound decisions and execute operations. The information collected can be used to conduct detailed analysis of the network to identify trends that can be used to optimize the efficiency and better protect it and its users. These tools are normally consolidated and reside in the Division and BCT/EAD NOSC under the control of the G-6 (S-6). These tool sets are fielded as part of the Unit Set Fielding (USF) process and incorporated into the system architecture and data product development. Discussion on data product develop will follow in a later section. Figure 4.7.8-1 shows the Current NetOps capability.

4-102

Figure 4.7.8-1. Current NetOps Capability

4.7.9 Battle Rhythm Due to the number of briefings and mandatory events occurring in a CP, both in garrison and combat, it is critical that these events be synchronized. From a NetOps perspective, this ensures that the network is available and accessible to support operations. All mission essential network-related events MUST be nested in with the Division/BCT/EAD units’ battle rhythm. Critical events that the G-6 and S-6 must pay close attention to include, Battle Update Briefs (BUBs), network operational updates, server maintenance, generator services, other scheduled system downtime requests, and mission planning for future operations.

4.7.10 Establishing the CP The setup and teardown of the CP is the most critical time for the unit to conduct Ops. It is during these periods that the NetOps section has minimal tools with which to monitor the stability of the network and to take corrective action if any degradation occurs. The unit must ensure that these processes are part of the unit SOP, and trained and executed in accordance with established unit battle drills. During the movement of the CP

4-103

(specifically the main CP) NetOps functions will remain with the CP that has operational control of operations within the AO. Once the displaced CP has established full network connectivity, a battle handover of tasks, functions, and responsibility will be transferred to it. This battle handover is a deliberate process with control measures (decision points) in place to ensure the proper handover criteria is met.

4.7.11 Reporting As mentioned previously, a Division G-6 or higher does not control or own the signal assets or personnel in the BCT. However, when the BCT is connected to the Division (or Corps or higher) network, then the Division G-6, empowered by the Division commander, has technical control of the network and the BCTs are obligated to report their network status to the higher HQ. Reporting procedures are normally included as part of a specific Annex to the division or task force operations order and specific timelines and report formats are part of the NetOps battle rhythm. Data gathered from these reports serve as a method for the G-6 and staff to conduct additional analysis on the overall health of the network, looking for trends that may signal an issue before it happens, track the maintenance status of all network related equipment, systems and platforms, and to prepare updates to be presented as part of the commander’s battle update brief. Report formats and content are defined as part of the unit SOP.

4.7.12 Commander Network Roles The potential missions a BCT/EAD unit can be assigned are more diverse than ever, it must be able to establish and maintain access to the GIG to conduct operations. It is imperative that BCT/EAD commanders have a better understanding of the network and its capabilities, the BCT/EAD architecture and systems that utilize the network, and the responsibility for utilizing and protecting the network. The commander is not the resident expert, but must possess an operational understanding of the network, its applications, and systems to employ and utilize it as a weapons system; and be able to provide the appropriate guidance and support to the S-6 running and maintaining the BCT/EAD enterprise network. It is important for commanders to understand that the decisions made about the

4-104

network and how they operate have an impact on the larger enterprise information grid. This affects not only the ability to execute operations, but affects the larger task force as well. Depending on the situation, adverse network effects can be felt all the way back to the sustaining base. The following are some specific areas for the commander to focus:

• Spectrum – There has been a significant increase in the number of emitters and spectrum dependent systems fielded down to the Brigade level. In some cases, these new emitters are competing for the same limited spectrum that the existing mission command and transport systems are utilizing. Commanders must understand and incorporate spectrum as part of their overall mission planning process. Of specific concern is the impact that the operational environment (terrain, urban density, proximity to U.S. and coalition partners, host nation spectrum utilization, etc.) has on the availability of spectrum to support operations. The closer in proximity that similarly configured and equipped units are operating, the more likely that spectrum conflicts become. Unmanned aerial platforms are an example. Due to the frequency band used to operate each platform and the bandwidth required, numerous units operating a defined area must be prepared to share the spectrum, limiting the number of platforms that can be airborne at any given time. Commanders cannot use all of the emitters that fielded and must prioritize installation, operation, and restoration of these systems. The S-6 and Bde/Division/Other Higher HQs Spectrum Managers are critical to the development of the spectrum utilization plan in support of operations and commanders intent.

• CP Operations – Commanders must integrate increased personnel and systems, including increases in mission command system applications, to enable effective mission command. Each staff section residing in the CP has extensive data requirements to develop products for the commander. This information is critical to CP operations; but excessive data can rapidly exceed the allocated bandwidth for a unit. It is critical that commanders establish and enforce “digital rules of engagement” inside the CP to ensure all systems are utilized to their fullest potential. These rules help to protect bandwidth supporting critical CP events. Applications and products requiring extensive time and/or bandwidth to produce should be allocated a time slot in conjunction with daily operations. These

4-105

products should be synchronized with/included as key events on the unit’s battle rhythm. For example, the S-2 cannot pull multi-megabit sized map products through the network when the commander is executing a battle update brief with the higher headquarters. Trying to access the map/Intel products can impact the quality of the update brief. Disciplined adherence to the digital rules will ensure network stability and unhindered support to operations.

Figure 4.7.12-1. Controlling Bandwidth

• Information Assurance (IA) – With this influx of data coming into the CP comes the operational necessity to safeguard it. The tactical network is no longer “closed” to the global community, and as a result makes network more vulnerable intrusion aimed at data collection (Intel) or to undermine operations. To this end, the IA posture is aimed at protecting systems from such attacks. There is no differentiation or separation between the network in garrison or in a forward theater of operations. This concept also applies to the fact that there is no difference between the tactical and strategic network. There are stringent rules on what is and is not allowed on the network and the commander is an essential part of enforcement of these rules. If the commander does not ensure compliance, anomalies can be injected into the network that can cripple an entire theater in just a matter of hours, having ramifications that reach all the way back to the sustaining base. Units must gain approval to add components, especially Commercial Off-the-Shelf (COTS) components outside their MTOE. This is important for several reasons. In a network where each and every component has an

4-106

assigned IP address, the addition of outside components can interfere with the proper functions of other systems. These additional systems utilize precious bandwidth that was not planned for, potentially reducing available bandwidth required for operational support. In addition, “non-standard COTS systems” are not included as part of the approved unit system architecture driving the production of data products that establish specific unit configuration baselines for digital connectivity. These additions force network managers to manually add their IP addresses to the baseline files, increasing the likelihood of configuration mismatches. There are stringent guidelines and policies in place to safeguard the network and critical information. The Brigade/EAD G-6 (S-6) ICW the applicable higher HQ G-6 has overall responsibility in the BCT/EAD and has a small staff section dedicated to monitoring IA across the BCT/EAD footprint, as does the Higher HQs. The Brigade/EAD and subordinate/assigned Battalion S-6 works directly as needed with higher HQs G-6 on all compliance matters.

4.7.13 Data Products

4.7.13.1 Data Products are a collection of mission data required to initialize mission command and other Army mission command systems. This data includes the information required to enable end-to-end network-centric connectivity and interoperability across the Tactical Internet (TI). In simpler terms, Data Products are a set of software databases which provide the following:

• Blueprint for building a unit • Initialization data required to configure the network • Upper and lower tactical internet address book

4.7.13.2 These software files ensure the configuration and connectivity requirements of the individual Warfighting Functions (WF) within mission command system are met. They include the data that provides accurate addressing and networking information for routing communications and mission command messaging between these systems. Two specific products that are produced to facilitate network management by the G-6 (S-6) are the System Architecture and Lightweight Data Integration Format (LDIF) which contains the role name and IP address for every mission command system in the unit.

4-107

4.7.14 System Architecture

4.7.14.1 As alluded to previously, the system architecture is the foundation for which unit digital connectivity is developed and serves as an essential guide to support CP establishment and operations. By definition, the system architecture “is a graphical display of radios and computer systems (based off of the MTOE from USAFMSA, the ABCS Resourced Distribution Plan (ARDP) from TCM-MC, and the KLO from TCM MC-BCT (formerly TCM-Platform Battle Command/Combat ID), inside their platform (e.g., vehicles, tents, transit cases, or aircrafts) networked together in order to provide a computer networking blueprint.” The diagram in Figure 4-90 shows an example of a NetViz diagram which displays the interconnectivity between the CP, network platforms, and mission command systems. Without this interrelationship, network connectivity, and situational awareness across the unit could not be shared.

Figure 4.7.14-1. NetViz Diagram

4-108

4.7.15 Data Product Development

4.7.15.1 Data products are extremely detailed and their development can take anywhere between 60-120 days. It is critical that the unit commander understands this complexity and ensures the development timeline is synchronized with the unit’s operational timeline. Failure to do so can adversely affect unit training events across multiple echelons. Throughout the development process, it is imperative that the right people are involved. At the Brigade/EAD level, the S-6, network techs (warrant officers), and senior automation officers/NCOs play a pivotal role. These people must be familiar with the type and location of all the mission command systems, including the combat platforms and command vehicles. Additionally, they must have a clear understanding of the unit’s system architecture and be able to make recommendations to the commander regarding redistributing assets or making additions platforms. There are several planning conferences taking place at different phases in the process. It is essential that these personnel are involved with each of them.

4.7.15.2 The development process begins with a review of all approved authorization documents for a particular unit (MTOE, ARDPs, Fielding Schedules, Fragos, ARFORGEN timelines, etc). With these documents, the developers create a baseline systems architecture which will serve as a baseline that any scheduled new equipment fielding or system changes can be annotated. Once completed, the systems architecture is provided to the unit at the initial synchronization conference. During this conference, the unit is provided fielding timelines linked to the operational and training calendars.

4.7.15.3 Once this initial conference is complete, there are a number of technical exchange conferences that occur between the data product developers and the WfF leads to verify network and configuration parameters. At the same time, they continually refer to the source documentation and ensure that the system architecture accurately reflects these protocols. This is the most important phase, as any unit-specified equipment/system changes are reflected in the configuration matrices. The final step in this phase is the addition of Unit Reference Numbers (URNs) to the system architecture documentation and

4-109

database files.

4.7.15.4 The final phase involves a multi-tiered review of the system architecture data product and all system configurations. This phase involves a special data review board, the unit, and the Pd NetOps data products working groups. Once approved, these configurations are installed in CP router, switches, servers, and applicable TMC Servers to serve as baseline configurations the unit uses to execute their mission essential training events. Once training is complete, the unit receives a final set of data products to support their deployment. These data products are classified and must be treated as any other classified document.

4.8 Information Systems

Applicable Command Post Information Systems are listed below. Additional information, to include descriptions and latest updates can be found at the Single Interface to the Field (SIF) site at https://sif.kc.army.mil/

ADAM Shelter - Air Defense Airspace Management System ADSI - Air Defense System Integrator AFATDS - Advanced Field Artillery Tactical Data System , several LINS AMDWS - Air and Missile Defense Workstation BCS3 - Battle Command Sustainment Support System CCS - Command Center System CHATS - Counterintelligence Human Intelligence Automated Tools Set CPCS - Command Post Communications System CPP- Command Post Platform CSS VSAT-Combat Service Support Very Small Aperture Terminal DCGS-A Enabled ACT-E - Distributive Common Ground Station Army Enabled Analysis Control Team-Enclave DCGS-A Enabled ASAS-L- Distributed Common Ground System-Army Enabled All Source Analysis System-Light DCGS-A Enabled ASAS-L IFS - Distributed Common Ground System-Army Enabled All Source Analysis System (ASAS) Intelligence Fusion System (IFS) DCGS-A Enabled DTSS - Digital Topographic Support System EMT - Effects Management Tool, part of AFATDS Family FAAD - Forward Area Air Defense FBCB2/BFT- Force XXI Battle Command Brigade and Below/Blue Force Tracker

4-110

FBCB2 TOC System (TOC Kit) GBS - Global Broadcast Service IMETS - Integrated Meteorological System, being replaced by Weather Systems Software on DCGS-A Enabled Systems. JADOCS - Joint Automated Deep Operations Coordination System MC4 - Medical Communications for Combat Casualty Care Family of Systems MTS - Movement Tracking System SMART-T - Secure Mobile Anti-Jam Reliable Tactical - Terminal TAIS - Tactical Airspace Integration System TC-AIMS -Transportation Coordinator – Automated Information for Movements System II TGS – Tactical Ground Station TMC-GW - Tactical Mission Command - Gateway TMC-WS - TMC – Work Station TMC-Server - TMC-Server (Previously known as the Battle Command Common Services (BCCS)) TMC- SMC - TMC Server Management Console TMC-STM - Server-Tactical Mission Command-Server (Previously known as the Battle Command Common Services (BCCS) WIN-T INC 1 and 2 - Warfighter Information Network – Tactical Increment 1 and 2 (formerly JNN)

4.8.1 Additional Information Systems

4.8.1.1 WAN Manager V2 and V3

4.8.1.2 These provide WAN fault, performance, and configuration management functions for routers within division, brigade, and ESB responsibility.

4.8.1.3 LAN Manager V3 provides LAN management functions for S-6 cell supporting the subordinate Bn CPs. It serves as a syslog server due to lack of other NetOps platforms at that echelon, used to configure or reconfigure the local routers managed by a higher echelon. SNMPc Workgroup is the primary software component hosted.

4.8.1.4 Help Desk (HEAT) Management Software provides administrators the ability to log trouble tickets, manage personnel and assets, and provide stored solutions for network problems. The system utilizes a HEAT software suite

4-111

developed by FrontRange Solutions: HEAT Support and Services, iHEAT, and HEAT Self Service.

4.8.1.5 Detailed Planning and Engineering Module (DPEM) is the planning and engineering tool used within NetOps cells and G-6/S-6 staff sections. DPEM software operates on a GETAC M220 laptop. The system provides software modeling and display capability that planners use to build graphically-planned networks. Planners lay down and link communications nodes on a map background. The network can be viewed in a logical diagram indicating how assets are connected, but not their location. Planners place assets on a battlefield map and graphically assess connectivity in a logical view, or on a map background. Patching diagrams, cutsheets, and reports for switch configurations are generated from the DPEM.

4.8.1.6 ISYSCON (V) 4, being replaced by WIN-T systems, is a digital, mission command systems for G-6 (S-6) sections providing on-the-move, real-time mission command information. It provides a semi-autonomous management capability to aid in the planning, configuration, initialization, monitoring, troubleshooting, and reconfiguration of TOC and LTI communications networks. ISYSCON(V)4 and its replacement systems within WIN-T also supports SA down to the warfighter/platform level.

4.8.1.7 Army Key Management System (AKMS)

4.8.1.8 AKMS is the Army’s implementation of the Electronic Key Management System (EKMS). EKMS involves the following tiered hierarchy:

• Tier 0 – NSA Central Facility (CF) • Tier 1 – Service-level EKMS account support • Tier 2 – LCMS software and KP support • Tier 3 – End User (Field-level) key and non-key data

loading to mission support equipment

AKMS is comprised of three subcomponents: LCMS, ACES, and SKL. The following paragraphs describe each component.

• The Army Local COMSEC Management Software (LCMS) Workstation Phase 5 Upgrade functioning at the user level

4-112

(Tier 2) of the EKMS, to integrate all functions of COMSEC. The LCMS Workstation automates and integrates processes required to generate, distribute, and manage data needed by various secure communications systems. The Workstation provides tools to support changing requirements in strategic and tactical environments, and is fully compatible with EKMS and Joint Key Management System (JKMS). The LCMS Workstation Phase 5 Upgrade includes the LCMS Workstation (AN/GYK-49(V)3). The Laptop (Tactical) LCMS Workstation (AN/GYK-49(V)2) has been replaced by the LCMS Workstation (AN/GYK-49(V)3).

• Automated Communications Engineering Software (ACES) was designed to replace the legacy Revised Battlefield Electronic CEOI System (RBECS) for automated cryptonet planning and EP data. It generates and distributes SOI and EP fill data for CNR operations. It also enhances the operator’s ability to provide cryptonet planning for other devices. The data stream used to randomly generate SOI and EP data will be implemented via software, replacing the legacy Random Data Generator (RDG) hardware.

• Simple Key Loader (SKL) component was developed by PD NetOps and is used as the Tier 3 data-loading device. The SKL’s primary task is managing key material. The SKL is a ruggedized, hand-held PDA consisting of a host computer and NSA-developed cryptographic and ECU protocol engine on a Personal Computer Memory Card International Association (PCMCIA) Type II card (KOV-21). It uses service-specific applications software called UAS to automate the loading process for field/mobile COMSEC components. SKL will replace DTDs and provide simple loading capabilities. It will be backward compatible with existing DTDs (i.e., CT3 UAS) until all DTDs have been replaced.

4.9 Configuration Customization

4.9.1 Customizing a CP must be planned to incorporate all essential CP elements. A CP may need to be customized for numerous reasons. The following things need to be planned out: power distribution and grounding, distances for network, flow of traffic, security measures, and operational tempo.

4-113

4.9.2 Terrain is the largest factor in planning for CP customization. Security and fueling operations must be considered. Terrain dictates where to place security. Adequate areas around the CP must exist to put security measures in place. Fuel trucks need room to travel around the CP to refuel power and environmental equipment, or alternative plans must be made for refueling.

4.9.3 Power distribution is a major priority when planning CP customization. Planners must consider distances from the power plant to ensure the proper length of power cable is available. Planners must also ensure cable distances do not interfere with the electrical grounding system in the power plant. Safety is a concern if power cables are run where they may cross a walkway or roadway. Plan to ensure that the correct equipment, PDISE M40 or M100, is on hand and can cover the power needs of the change. The maximum distance from the power plant to the CP should be 100 feet. Longer distances require additional cables. Use of additional cables cause the voltage to drop to a level that prevents proper operation of CP mission command system equipment.

4.9.4 Some information system networks are limited by the distance the signal can travel and the surrounding terrain features. When customizing the CP, plans have to be made to ensure that network assets can communicate to other information systems. Network cable runs must be planned according to Army regulations for security and safety, personnel, and cable.

4.9.5 CP customization requires a consideration of flow-of-traffic considerations. Fire exits and other safety features need to be clearly identified in the plan. The CP planner needs to ensure that the CP does not turn into a “maze” of corridors. A minimum amount of cells that have walk-through traffic is desired.

4.9.6 Although deviation from the CP standard is not encouraged, customization is sometimes necessary. Prior planning and considerations for all elements of the mission command system within the CP will ensure it is safe and functional.

4-114

4.10 Conclusion. As mentioned at the beginning of this Chapter, additional Doctrinal CP Templates for the Corps, ASCC and Echelons Above Division (EAD) Formations are covered in a supporting Annex to be published (TBP). The Templates are very similar though but will need application of the unique MTOEs of the other type units. Diagrams for the Echelons Above Division (EAD) Formations will also be included in this Annex TBP.

Chapter 5 Establishing the Command Post

This page intentionally left blank.

5-1

Chapter 5.0 Establishing the Command Post

5.1 Introduction

5.1.1 This chapter outlines the setup procedures of the Brigade Combat Team (BCT) Main, Tactical Command Post (TAC CP), and Battalion Command Posts (CPs). When establishing a CP at any echelon, it is important to follow priorities of work in order to maintain mission command while expanding warfighting function capabilities. Through the mission command warfighting function, commanders integrate all warfighting functions to accomplish the mission.

5.1.2 Chapter 5 of FM 7-15, The Army Universal Task List states: Mission command is the exercise of authority and direction by the commander using mission orders to enable disciplined initiative within the commander’s intent to empower agile and adaptive leaders in the conduct of unified land operations. It is commander-led and blends the art of command and the science of control to integrate the warfighting functions to accomplish the mission (ADP 6-0). Mission command is the warfighting function that develops and integrates those activities enabling a commander to balance the art of command and the science of control. It is an adaptation that captures what we’ve the Army has learned in a decade of war. References:

• ADP and ADRP 3-0, Unified Land Operations

• ADP and ADRP 5-0, The Operations Process

• ADP and ADRP 6-0, Mission Command

• ATTP 5-0.1, Commander and Staff Officer Guide

• FM 6-0, Commander and Staff Organization and Operations (Replaces ATTP 5-0.1 in 2013)

• FM 6-01.1, Knowledge Management Operations

5-2

5.2 Order of Setup

5.2.1 This section outlines CP order of setup following applicable portions of the Army Tactical Task (ART) 5.2, Conduct Command Post Operations.

Figure 5.2.1-1. Conduct Command Post Operations

5.2.2 Organize, create/erect, operate, and move the principal facility used by the commander to exercise mission command of tactical operations. The command post performs the mission command functions discussed in succeeding subtasks. (See ATTP 5-0.1, Commander and Staff Officer Guide, and when published refer to FM 6-0, Commander and Staff Organization and Operations for more information on command post organization and operations.)

5.3 Establish the BCT Tactical CP

5.3.1 The BCT TAC CP is staffed and equipped to perform the warfighting functions of movement and maneuver, intelligence, and fires. The priorities of work for establishing this CP should follow this purpose. The TAC CP is made up of two integration cells: Current Operations 1 and Current Operations 2. After completing site occupation and establishing tactical voice communications to higher and

5-3

lower echelons, the Current Operations 2 tent can be established while the Warfighter Information Networks-Tactical (WIN-Ts) and Command Post Platforms (CPP) are being set up. Once this equipment is erected and operational, the Tactical Mission Command-Work Stations (TMC-WS), Distributive Common Ground Systems – Army (DCGS-A), and Advanced Field Artillery Tactical Data System (AFATDS) information systems can be powered and connected by the CPP Tent Interface Panels (TIPs) for operation by their respective staff operators. Digital voice capabilities should also be established by setting up a Crew Access Unit (CAU). When completed, personnel can emplace the power plant, as well as the Access Control Point (ACP) and Current Operations 1 tents, without hindering battle tracking in the adjacent tent.

Figure 5.3.1-1. Steps 1 through 5 of TAC CP (BN CP) Setup

5.3.2 The Current Operations 1 tent should be fully established so the TMC-WS, DCGS-A and AFATDS operators can seamlessly relocate to their assigned positions. Once the Current Operations 2 tent is cleared, assigned personnel can begin setting up equipment per the diagrams in this handbook or unit Standing Operating Procedure (SOP).

5-4

Figure 5.3.2-1. Steps 6 through 7 of TAC CP (BN CP) Setup

Table 5.3.2-1. Setup Procedures of BCT TAC CP (Modified BN CP)

No. Task/Subtask Description ART 1 Occupy site Execute activities following a

tactical or administrative movement to establish and conduct command post operations

New task 5.2.1

2 Establish Tactical Voice Communications

Establish LOS and OTH tactical radio communications to higher, lower, and adjacent echelons from command vehicles

New Task 5.2.1.2

3 Emplace Network Equipment

Establish data links to NIPR/SIPR network

New Task 5.2.1.2

Emplace WIN-T (JNN) system

Position and connect JNN, STT, and 10Kw generator

Emplace CPP Shelters

Connect CPPs to WIN-T, expand tactical voice capabilities, prepare to support INFOSYS

Establish server connections

Establish server links to populate common operational picture, data exchange, and collaboration

4 Erect Current Operations 2 Tent

Establish first tent to conduct mission tracking. Executed in parallel with previous step

New Task 5.2.1.2

Set up power generation

Set up generator power plant, emplace power distribution cables to vehicles and tents

5-5

No. Task/Subtask Description ART 5 Conduct mission

tracking using TMC-WS, DCGS-A, and AFATDS

Set up and connect key INFOSYS for Movement and Maneuver, Intelligence, and Fires warfighting functions

New Task 5.2.1.2

6 Set up complete TAC footprint

Complete setup of TAC tents and infrastructure IAW unit layout SOP

New Task 5.2.1.2

Set up ACP tent Set up ACP and conduct access control

Set up Current Ops 1 tent

Establish Current Ops 1 tent and all internal INFOSYS to conduct operations

7 Conduct CP operations

TAC CP can assume tactical control at this time if needed

7.1.1

8 Complete setup of Current Ops 2 tent

Complete setup of TAC CP staff in Current Ops 2 tent

7.1.1.2

9 TAC CP fully operational

TAC CP at full combat effectiveness

7.1.1.2

5.4 Establish the Battalion CP (BN CP) The BN CP is very similar to the BCT TAC CP in regard to equipment and footprint. The setup procedures are the same; however, instead of a Current Operations 2 cell, the BN employs a Sustainment cell which handles the additional warfighting functions of Sustainment, Logistics, Personnel Services, and Protection. This cell also serves the Integrating cell function of Plans. The BNs do not have the WIN-T INC 1 (JNN) shelter. Only the trailer-mounted secure Satellite Transportable Terminal (STT) is fielded at the BN level. CPP shelters are only fielded to Stryker Battalions, therefore all other BNs will need to deploy their transit case-mounted CPCS and setup tactical radios.

5.5 Establish the BCT Main CP

5.5.1 The BCT Main CP is tasked with executing mission command of operations. It includes representatives of all staff sections and a full suite of INFOSYS to plan, prepare, execute, and assess operations. The Main CP is functionally organized into a mix of functional and integrating cells.

5-6

5.5.2 During the establishment of the Main CP, mission command is conducted from an alternate CP, such as the TAC CP. There is still a requirement during setup to maintain situational awareness and track operations. Again, the sequence of CP establishment is done by priorities of work. See Table 5.5.2-1 for the BCT Main CP setup procedures.

Table 5.5.2-1. Setup Procedures of BCT Main CP

No. Task/Subtask Description ART

1 Occupy site Execute activities following a tactical or administrative movement to establish and conduct command post operations.

New Task 5.2.1

2 Establish Tactical Voice Communications

Establish LOS and OTH tactical radio communications to higher, lower, and adjacent echelons from command vehicles.

5.2.1.1

3 Emplace C2 Data equipment

Establish data links to SIPR network.

5.2.1.1

Emplace WIN-T (JNN) system

Position and connect JNN, STT, and 10Kw generator

Emplace CPP Shelters

Connect CPPs to WIN-T, expand tactical voice capabilities, prepare to support INFOSYS

Establish server connections

Establish server links to populate common operational picture, data exchange, and collaboration

4 Erect Network Operations Tent

Erect the Network Operations tent to establish initial voice and data systems and battle tracking. Executed in parallel with previous step. Do not fully stake down tent as is will need to be repositioned to boot to Current Operations tent.

5.2.1.1

5 Conduct mission tracking using TMC, DCGS-A, and AFATDS

Set up key information systems for Movement and Maneuver, Intelligence, and Fires warfighting functions in the Network Operations Tent. (Use help desk table.)

5.2.1.1

5-7

No. Task/Subtask Description ART

6 Set up the Current Operations Cell

Set up complete Current Operations Cell. Executed in parallel with step 4. Relocate information systems from Network Operations tent when complete.

7.1.1

7 Set up power generation

Set up generator power plant, emplace power distribution cables to vehicles and tents as emplaced. (Executed in parallel with step 6.)

8 Set up Main CP section cells

Set up Network Operations Cell

Reposition network operations tent and complete cell setup.

Set up Fires Cell Set up fires cell tent and systems to include the ADAM shelter and tent.

Set up Movement and Maneuver Cell

Erect vestibule tent and set up Movement and Maneuver tent and systems.

Set up Intelligence Cell

Set up Intelligence tent and all systems to include vehicle platforms (TGS, ACT-E, etc.).

Set up ACP Set up ACP tent and begin CP access procedures.

Set up Sustainment Cell

Set up Sustainment tent and all assigned systems.

Set up Plans Cell Set up Plans tent and all systems to include DTSS shelter.

Set up Commander’s tent

Commands tent may be booted into either the Current Ops tent or Plans tent as directed.

9 Conduct CP operations

TAC CP can assume tactical control at this time if needed.

7.1.1

10 Complete setup of Current Ops tent

Complete setup of TAC CP staff in Current Ops tent.

7.1.1.2

11 Main CP fully operational

Main CP is at full combat effectiveness

7.1.1.2

5.6 Standing Operating Procedures (SOPs)

ART 5.2.1.3 ESTABLISH OR REVISE STANDARD OPERATING PROCEDURES

5.6.1 Create or modify a set of instructions covering those tasks and functions that lend themselves to a definite or standard procedure without a loss of effectiveness; the standard operating procedures is effective unless ordered otherwise to meet altered conditions.

5-8

5.6.2 As outlined in FM 3-90.5, TAC SOPs for each CP should be established, known to all, and rehearsed. TAC SOPs include:

• The organization and setup of each CP

• Plans for teardown and displacement of the CP

• Eating and sleeping plans during CP operations

• CP shift manning and operation guidelines

• Physical security plans for the CP

• Priorities of work during CP operations

• Loading plans and checklists

• Orders production

• Clearance of fires drills

• Techniques for monitoring enemy and friendly situations

• Displays of electronic map boards and status charts

• Maintenance of CP journals and logs

• Units are encouraged to utilize any portion of these procedures to establish unit SOPs. For additional documents that provide more detail of this section, go to https://www.us.army.mil/suite/page/547567

5.7 Displace the CP

ART 5.2.2 DISPLACE THE COMMAND POST Move or transfer the principal facility used by the commander to exercise mission command of tactical operations in order to support mission command of a specific operation.

ART 5.2.2.1 PREPARE THE COMMAND POST FOR DISPLACEMENT

Execute activities before movement to make the command post more ready to move. These activities include, but are not limited to, dismantling information systems and associated networks, dismantling the facilities and equipment, and packing elements of the command post according to load plans.

ART 5.2.2.2 SELECT, RECONNOITER, AND EVALUATE THE NEW COMMAND POST LOCATION

Decide and confirm the suitability of the location to which the command post should displace, including the time of/for movement.

5-9

5.8 Select CP Location

5.8.1 As outlined in FM 3-90.6, Chap 3, The Main CP is positioned to maintain communications with subordinate units and control of the operation. Considerations for positioning the Main CP:

• Where the enemy can affect the main CP operations least

• Where the Main CP can achieve the best communications

• Where the Main CP can control operations best

5.8.2 In contiguous AOs, the BCT main CP usually locates behind battalion TOC and out of medium artillery range. In noncontiguous Areas of Operations (AOs), the BCT Main CP usually locates within a subordinate battalion’s AO.

5.8.3 Battalion level CPs are considerably smaller and able to be positioned with more flexibility. FM 3-90.5, Section 3-58, Command Post Survivability, outlines considerations of location, access, size, shelter, and operational security that may be apply to both echelons.

5.9 Occupy CP Location

ART 5.2.2.3 OCCUPY THE NEW COMMAND POST LOCATION Execute activities following a tactical or administrative movement to establish and conduct command post operations.

5.10 Transfer C2 Between CPs

ART 5.2.2.4 TRANSFER COMMAND AND CONTROL FUNCTIONS DURING DISPLACEMENT

Reassign mission command functions from the old location to the new location. Maintain mission command functions during the move without disruption.

5.10.1 Before transferring mission command functions from one CP to another, there are numerous considerations to ensure that all information is properly transferred. In the deliberate establishment of a CP, there are two types of mission command transfer functions. Either the TAC CP is established to provide mission command to allow the Main CP to displace, or the TAC CP is established in an area of

5-10

operation to provide improved mission command to subordinate echelons in that geographic area. This may be done to allow the use of additional Line-of-Sight (LOS) communications systems and provide improved local situational awareness.

5.10.2 At the BCT level and above, headquarters has TAC and Main CPs with redundant information systems. Although these systems are redundant by capability, information may only reside in one location. It is important to consider what information should be duplicated or transferred to ensure it is available to the commander and staff at the proper location and at the right time.

5.10.3 Once a CP is established, all pertinent information such as planning documents, operations orders, fragmentary orders, intelligence files, map data/imagery, and other pertinent files should be duplicated. Even if both CPs will be operational, this will ensure that all information is available locally in the event that digital communications are lost. Information system servers should be synchronized with the appropriate node to ensure that all data is up to date. Staff relocating to another CP will also need to have their respective email accounts transferred.

5.10.4 If a CP will be displacing, there are additional steps to take to ensure that information systems will continue to properly share data between CPs at various echelons (refer to Table 5.10.4-1). The staff proponent for each INFOSYS will need to report a GO/NO GO status before digital communications can be disconnected and displaced.

5-11

Table 5.10.4-1. Data Transfer between Main CP and TAC CP

INFOSYS Information

• Verify current operational picture in TAC CP on FBCB2/BFT/JCR, TMC-WS, AFATDS, and DCGS-A.

• If not using DDS, Initiate PASS-to-PASS connection from TAC CP BCS to Main CP BCS. No actions required for DDS.

• Retrieve pertinent information from Main CP PASS. • Conduct C2R replication (this is done only if modifications to units data

products have been made). • Verify information transfer is complete through PASS. • Verify that subordinate unit servers are communicating with the TAC

server (applies to various INFOSYS). Enterprise Service Information • When TAC CP servers are initialized, verify replication of Active

Directory for all login accounts, computers, and additional resources. Ensure that any new required accounts or computers are added BEFORE communication to Main CP is broken.

• Transfer all users’ email accounts at the TAC and any additional accounts that may be needed (Admin accounts) to the TAC CP exchange server. Consider subordinate unit e-mail accounts as well.

• Verify email functionality within TAC CP. • Verify email is flowing outside TAC to other units and higher

headquarters.

5.10.5 Establish CP at the Quick Halt (ATQH)

Table 5.10.5-1. Establish CP ATQH

Task Subtask System/ Vehicle Operator

Conduct Quick Halt (QH)

All All

Position vehicles in QH formation for security

All All

Establish JNN (WAN) Position/Ground Vehicle

and Generator STT Team

Power Generator up and JNN

STT Team

Position STT for STT STT Team

5-12

Task Subtask System/ Vehicle Operator

Operations

Level STT STT STT Team

Ground STT STT STT Team

Connect TFOCA-II cable from STT to JNN

STT STT Team

Power up STT STT STT Team

Erect antenna, deploy dish wings

STT STT Team

Establish STT link STT STT Team

JNN Team notifies CPP A operator when WAN link is established

STT STT Team

Establish CPP A

Monitor radios through Cab CAU

CPP A CPP A TC

Position and Ground CPP A

CPP A CPP A Driver

Power up APU; switch power from vehicle to APU

CPP A CPP A Driver

Verify internal systems operation (BIT Laptop)

CPP A CPP A Driver

Connect TFOCA-II between JNN and CPP Signal Entry Panel (SEP)

CPP A CPP A Driver

Establish CPP B

Monitor radios through Cab CAU

CPP B CPP B TC

Position and Ground CPP B

CPP B CPP B Driver

Power up APU; switch power from vehicle to APU

CPP B CPP B Driver

Verify internal systems operation (BIT Laptop)

CPP B CPP B Driver

Connect TFOCA-II between CPP A and B SEP

CPP B CPP B Driver

5-13

Task Subtask System/ Vehicle Operator

Confirm SWLAN connectivity between CPP A and B (Stryker Units Only)

CPP A and B CPP A Driver

Initiate INFOSYS and Enablers

Connect TMC Workstation and other required INFOSYS via CAT 5 Cables to TIP of CPP A or B

Respective INFOSYS

INFOSYS Operator

Connect Enabler Vehicles as Required to CPP A or B

CPP A or B Operator

Verify Connectivity of INFOSYS and Enablers to PASS or DDS

Respective INFOSYS

Operator

Access unit portal/download OPORD/FRAGO

Respective INFOSYS

Operator

Send email SITREP Respective INFOSYS

Operator

5.11 System Validation

5.11.1 Due to density and complexity of the CP INFOSYS it is necessary to plan for and conduct validation checks. These checks ensure that all systems are properly configured and have full functionality prior to deployment for training or real-world operations. There are various tools that can be utilized and incorporated into units’ SOPs, including the following:

• Setup procedure checklists

• Individual system validation sheets

• System status charts

5.11.2 Units should utilize these procedures and validation tools for the following events:

• Initial CP setup (garrison training)

• Unit CP Exercise (CPX) Training

5-14

• Mobilization Readiness Exercise (MRE)

• Deployment Reception, Staging, Onward, & Integration (RSO&I)

• Tactical Assembly Area (TAA) occupation and setup

5.11.3 When conducting a CP checkout, it is recommended that the current operations Battle Captain/Non-Commissioned Officer (NCO) lead the coordinated effort to track system status. Each system’s functionality correlates to a capability and information source. By coordinating system status at the current operations cell, the commander/Battle Captain will have situational awareness (SA) of the information available for tactical decision making. For example, if indirect fire is received and the air picture is not available, the current operations staff needs to know that a clearance of fires for a counter-fire cannot be conducted per the standard unit battle drill. Alternate resources would need to be employed to react to the threat.

5.12 Common Operational Picture (COP)

5.12.1 The COP (Figure 5.12.1-1) is a display of relevant information within a commander’s area of interest, tailored to the user’s requirements and based on common data and information shared by more than one command. The COP features a scale and level of detail that meets the information needs of the commander and staff and varies among staff sections and echelons. The COP facilitates mission command and allows subordinates to see the overall operation and their contributions to it. Separate echelons can create a shared COP. (Refer to ADRP 6-0, Mission Command and FM 6-01.1, Knowledge Management Operations for more information on the common operational picture.)

5-15

Figure 5.12.1-1. COP

5.12.2 The COP is based on information from individual platforms (FBCB2/BFT) and subordinate, higher, and adjacent units. Each Information System (INFOSYS) in the CP creates and manages specific staff-related COP components. INFOSYSs can share and display data The Data Dissemination Service (DDS) running on the CP’s Mission Command Server (MCS)or TMC Gateway is the conduit for data sharing across the INFOSYS spectrum. Sharing and displaying INFOSYS data allow the commander and staff to be able to see themselves, see the enemy, and see the environment. The COP, observations of commanders, and running estimates are primary tools for assessing the operation against operations, mission, and commander’s intent. Running estimates provide information, conclusions, and recommendations from each staff section to refine and supplement information not readily displayed.

5.12.3 Commanders begin with SA, immediate knowledge of the conditions of the operation, constrained geographically and in time. SA is an awareness of the immediate surroundings. It is not a display or the COP, but the interpretation of displays or actual observation.

5-16

5.12.4 Commanders use the SA available to shape their Situational Understanding (SU), enhancing decision making by identifying opportunities, threats to the force or mission accomplishment, and information gaps. SU based on a continuously updated COP fosters individual initiative by reducing uncertainty.

5.12.5 INFOSYSs provide unique data contributions and a view of the battle space, which comprise the COP. The COP reflects changes and enables commanders and staffs to see the battle space more accurately and in near-real time. INFOSYS contributions to the COP include the following (see Table 5.12.5-1):

• AFATDS: Fire unit and radar range fans; Fire Support Coordination Measures (FSCM); preplanned fires; final protective fires; active fire support missions

• AMDWS: Air defense weapon and sensor coverage; location, speed, and flight direction of aircraft; tactical ballistic missile launch and impact point, current track, and launch/impact point pairing line

• BCS3: Unit combat power; supply status by class of supply for units, facilities, and transportation features; supply and maintenance points and supply routes; location of logistics assets and convoys

• DCGS-A/ASAS: Enemy unit locations; enemy equipment, facilities, and individuals; gathering, analysis, and display of enemy event and activity data.

• DTSS: Digital maps for INFOSYS, mobility and trafficability, LOS tactical decision aids, and background images.

• FBCB2/BFT: Individual vehicle icons of equipped platforms, graphic control measures, geo-referenced graphical observation reports.

• GCCS-A: Political boundaries with countries differentiated by color; friendly and enemy ground units, naval vessels, obstacles, and military installations.

5-17

• IMETS: Standard weather symbols depicting current weather conditions, forecasts, and severe weather warnings; weather contour overlays to show 30+ different weather conditions.

• TAIS: Multi-dimensional display of ACOs and ACMs.

• TMC Client: Unified picture of operational environment; friendly and enemy unit locations; graphic control measures; executive level decision support and collaboration; troop to task creation, analysis, and sharing

Table 5.12.5-1. Parts of the COP

Parts of the COP AFATDS DCGS-A (ASAS) AMDWS

− Fire Unit Locations − Range Fans − Target Locations − Radar / Observer

Locations − Fire Support Overlays

− Intelligence Summary − Enemy Locations − Enemy Geometry − Enemy Overlays − Intelligence

Preparation of the Battlefield

− Sensor Coverage − Weapon Coverage − Air Picture − Air Defense Overlay

BCS3 DTSS FBCB2/BFT − Status Reports − Logistics Capabilities − Personnel Reports − Logistic Overlays

− Terrain analysis & management

− “Go / No-Go” Areas − Terrain Overlays

− Situation Awareness − Combat Reports − Combat Orders − Combat Service

Records − Combat Service

Support − Overlays − Unit Task

Organization − Radio Net Join − Cuts Through “Fog

of War”

5-18

Parts of the COP GCCS-A IMETS ISYSCON V.4

− Army’s Strategic & Theater C2 System

− Joint & Coalition Interoperability

− Deployed in EAC

− Weather Effects Matrix

− Battle Scale Forecast Model

− Weather Overlays

− Tactical Internet Manager

− Configures routers and switches in CPs

− Monitors the Lower Tactical Internet

− Executes unit task reorganization functions

TMC TAIS − OPLAN / OPORD − Unit Task Organization − Reports − Maneuver, Engineer,

Chemical Overlays

− Air Space Command and Control

− Air traffic services − Linkage to joint

systems

5.12.6 The unit determines which INFOSYS to use as the central COP display based on INFOSYS availability and unit mission. Generally, however, a TMC Client system is used as the displayed COP. As events or other reports warrant, INFOSYS operators can zoom in to the appropriate level of detail as required. Many INFOSYS allow operators to create specific map type, scale, and zoom views as needed, and then choose them to automatically change the map. background. As the map focuses on a smaller area, more detailed information is displayed. Additionally, INFOSY Sallow operators to filter live feeds to the required echelon and types. The basic formula is

Table 5.12.6-1. AO Information

AO Information Displayed

(1) Division Down to TF icons / Brigade boundaries / Div MSRs

(2) Brigade Down to CO/TM icons / TF boundaries / Bde Routes

(3) TF Down to PLT icons / CO/TM boundaries / TF Routes

(4) CO/TM Down to Veh icons / PLT graphic CMs / CO/TM Routes

5-19

5.12.7 COP Manager The COP Manager is a person selected and designated to serve in this position due to their high degree of attention to detail, greater understanding of the INFOSYS and enhanced computer skills, knowledge of ADP and ADRP 3-0, ADP and ADRP 5-0 and ADP and ADRP 6-0, intelligence, and experience working in a CP. The COP Manager works for the Battle NCO. The COP Manager’s duties include:

• Responsible for all information displayed as the COP.

• Updates unit locations and events through the digital.

• component of the COP.

• Updates unit locations and events on the analog COP (if used)

• Coordinates with other staff sections for COP manipulation

• during briefings.

• Receives guidance from the G-3/S-3 and Commander on specific views or manipulations of the COP for SA purposes.

5.12.8 INFOSYS Contributions to the COP. Digital INFOSYS allow the commander and staff to tailor the wealth of information into specified functional area views. Although the information is functionally managed and updated by various systems throughout the network, the data distribution architecture ensures the availability of critical, time-sensitive information to the commander and staff. The table below details the types of graphical information that comprise and contribute to the COP. The table details information types and INFOSYS capability to send/receive them. While only a guideline, the listed information is likely to be highly relevant to the commander and staff. Inputs to the COP are of two types: overlays and data displayed within the COP, and reports that contribute to the display of information in the COP.

5-20

Table 5.12.8-1. Information Comprising and Contributing to COP

Information Name Applicable BFA Description Position Report GCCS-A, TMC-WS,

FBCB2/BFT/JCR, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A report that provides friendly unit location data preferably by automatic data exchange

Operations Overlay GCCS-A, TMC-WS, FBCB2/BFT/JCR, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A graphical depiction of the OPORD showing units, boundaries, control measures, and so forth, in a digital color map display

Enemy Overlay GCCS-A, TMC-WS, FBCB2/BFT/JCR, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A graphical depiction of the location, size, and activity (past, current or planned) of enemy units

Obstacle Overlay GCCS-A, TMC-WS, FBCB2/BFT/JCR, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A graphic depiction of locations of friendly and enemy obstacles, including information on key terrain, status of friendly obstacles or barriers (completed, executed, planned, prepared), enemy obstacles, enemy ground avenues of approach, and effective times of the obstacles if known

Combined Obstacle Overlay

GCCS-A, TMC-WS, FBCB2/BFT/JCR, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A graphic depiction of terrain under dry, normal, or wet conditions that depicts mobility and cross-country movement rates for use in avenue of approach analysis. The overlay integrates all obstacles into a single display, greatly simplifying further avenue of approach and mobility corridor analyses

5-21

Information Name Applicable BFA Description Modified Combined Obstacle Overlay (MCOO)

GCCS-A, TMC-WS, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A graphical depiction of the analysis results of the battlefield’s effects on military operations. Based on a product depicting all obstacles to mobility, modified to also depict the following which is not prescriptive or inclusive: cross-country mobility classification, objectives, and mobility corridors, likely locations of counter-mobility obstacle systems, defensible terrain, likely engagement areas and key terrain

Fire Support Overlay GCCS-A, TMC-WS, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A graphical depiction of FS coordinating measure text and graphics, locations of friendly artillery, mortar, and FS assets, areas that can be supported by FS weapons, areas that can be covered by FS sensors, radar, or observers, and ammunition supply points

Air Space Coordination Overlay

GCCS-A, TMC-WS, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A graphical depiction of the lateral boundaries of the airspace control area, low-level transit routes, high-density airspace control zones, aircraft checkpoints, and standard Army aircraft flight zones

5-22

Information Name Applicable BFA Description Range Card FBCB2/BFT/JCR,

TMC-WS A graphical depiction of a range card that is normally developed for each defensive fighting position and includes: left and right firing limits, dead zones (areas that cannot be engaged by weapons in the fighting position), range to likely points enemy may use, best grazing fire lines, final protective fire line. Range cards typically feed platoon fire plan overlay

Sector ID Overlay FBCB2/BFT/JCR, TMC-WS

A graphical depiction of defensive operations at company level and below to show division of responsibilities

NBC Overlay GCCS-A, TMC-WS, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A graphical depiction of decontamination site locations, reconnaissance sites, smoke operation lines

Fire Plan Overlay GCCS-A, TMC-WS, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A graphical depiction of information used to control and integrate direct and indirect fires at company level and below. It depicts the location of planned targets; target reference points; dead space; final protective fires; engagement areas; sectors of fire; and primary, alternate, and subsequent firing positions

Traffic Control Overlay

GCCS-A, TMC-WS, BCS3, AFATDS, AMWWS, DCGS-A, TAIS

A graphic depiction of the routes, locations, and size of depicted units. Visually depicts the physical relationships of units (represented by the overlay) and terrain (represented by the map)

5-23

5.12.9 COP and the Operations Process. By providing a clear, accurate, and common view of the battle space in near real time, the COP is key to each step of the operations process—plan, prepare, execute, and assess—as summarized below.

5.12.9.1 Plan

• Intent and Planning Guidance. The commander can readily impart intent and issue planning guidance. The COP also helps ensure a subordinate commander is planning within the intent and concept of operations of the superior commander.

• Relevant Information (RI). A commander can use the COP to depict the operational picture. This helps staff and subordinate leaders focus on relevant information for the operation. This facilitates the planning process, resulting in more rapid planning and precise understanding of and adherence to the commander’s intent. SU of friendly forces (air and ground) is automatically fed into the COP. However, graphical data must be manually input into INFOSYS before being displayed in the COP.

• Collaboration. Because leaders at different locations can simultaneously view the battle space in an identical manner, collaboration is significantly enhanced, thereby facilitating planning, directing, and brief-backs. Staffs can use the same graphics and overlays (both active and notional) concurrently from different INFOSYS.

• Parallel Planning. The COP helps subordinate units conduct their own planning concurrent with the development of parent headquarters’ plans.

• Branches and Sequels. Different configurations of the COP can be developed to match anticipated branches and sequels of an operation. As the tactical situation evolves, revisions to the original plan, such as changed operational graphics, can be rapidly disseminated.

5-24

• Reduced Control Measures. Increased SU attained through the COP may reduce the need for extensive control measures to coordinate maneuver and to avoid friendly-on-friendly engagements. This allows units to function more effectively should the battle become fluid and/or non-linear. However, this must be weighed with the fact that SU is imperfect.

5.12.9.2 Prepare

• Brief-Backs. Using the common framework provided by the COP, subordinate leaders are better able to confirm the commander’s intent and concept of operations. This common framework also assists subordinates in conveying their own plans during the brief-back. Plan Updates. Units can monitor the current tactical situation even as they ready themselves for an operation. Tactical plans and staff estimates can be revised as necessary to meet changes in the battle space as seen through the COP. This is especially critical in a highly fluid tactical situation. Rules of Engagement (ROE). The COP can be used to depict certain parts of the ROE. This will help to ensure the ROE are disseminated uniformly down to the lowest echelons.

5.12.9.3 Execute

• Adaptability. Units can respond rapidly to the dictates of the evolving tactical situation during an operation. The shared SU increases the ability of commanders at all levels to quickly make the right decisions, synchronize their forces and fires, and increase the operational tempo.

• Initiative. Armed with the commander’s intent and superior SU, subordinate leaders are better able to seize and retain the initiative within their respective tactical spheres. Units, therefore, will be better able to dictate the terms of combat in order to build momentum quickly and to win decisively.

5-25

• Risk Management. Commanders are better able to assess risk using the SU gained via the COP. This enables them to act more aggressively while simultaneously enhancing the protection of their forces.

• Friendly-on-Friendly Engagements. The enhanced SU gained through the COP, combined enhancements and improved optics, offer the opportunity to reduce the chance that friendly forces will become engaged with one another. This contributes to force protection, rapid engagement, and aggressive maneuver. This is, of course, contingent on the premise that all friendly forces involved have a full suite of fully operational INFOSYS.

• Changes to Operations. Using the COP, the commander can rapidly communicate changes to an ongoing operation. This might entail following a branch or sequel, changes to control measures, or even a new line of operations.

5.12.9.4 Assess

• Monitoring Operations (Mission Tracking). The COP helps leaders to measure, analyze, and report unit performance during an operation. This enables them to compute or otherwise identify variance from the plan or its assumptions and to forecast change. Using the COP, staff sections can employ their respective INFOSYS to monitor operations according to a common baseline to assess unit performance. A commander can help satisfy CCIRs by ensuring requirements are depicted within the COP, as applicable. This ensures staff and subordinates focus on this information during an operation.

• COP Maintenance. The COP is not static but requires continuous monitoring and revision, where appropriate. Factors that might indicate such changes include: success on the battlefield, changes in task organization, significant alteration to the enemy picture, change in mission, significant friendly losses, change in concept of operation, movement to a new phase of the joint campaign, and/or environmental changes or shifts (e.g.,

5-26

weather, civil disturbances). Such changes may be anticipated and, therefore, preplanned.

5.12.9.5 Relevant Information. RI is all information of importance to commanders and staffs in the exercise of Mission Command (Refer to ADRP 3-0 and ADRP 6-0 for more details on relevant information). To be relevant, information must be accurate, timely, usable, complete, precise, reliable, and secure. RI provides the answers commanders and staffs need to conduct operations successfully..

• The COP consists primarily of knowledge, which the staff provides through analysis and evaluation. Information becomes RI if it supports exercising mission command. Staffs support their commanders’ decisions through the use of information management to collect, process, display, store, and disseminate RI..

• Not all information required in the CP is displayed on the COP. Information on unit strength, CCIR, mission and intent statements, briefings, and orders tracking are examples of this type information. The data needs to be available and displayed, but is not part of the graphical COP. The fielded Command Center System (CCS) provides for unit-configured INFOSYS displays on multiple screens as well as multiple displays on a single screen. This capability enables units to display the COP plus RI and other data as deemed necessary by the command, the staff, and the situation. For example, a unit can use one screen to display the COP, and use another screen to display in a quad format of the combat power from BCS3, a rolling BUB, UAS feed, and TMC. Units should take into consideration display requirements when cabling video output connections to the CCS.

• For CPs or CP cells with only a single screen, the CCS can be used for creating multiple displays. The unit can have a single display for their COP and also configure multiple INFOSYS displays to use as required. Utilizing hot key shortcuts, the unit can move back and forth quickly from one view setting to another.

5-27

5.13 Battle Drills

5.13.1 These Battle Drills can be used when staff is conducting training on staff operations in a classroom/field environment. These Battle Drills show what staff actions need to be taken, in relation to the Battle Drill, when a message is received in the CP. The event is designed to trigger the staff and start the Battle Drill process. The flowchart in Figure 5.13.1-1 shows shows a sample battle drill messaging, information and staff action flowchart.

• Friendly KIA/WIA

• Friendly Death (Non-Hostile Action)

• Iraqi NIA/ICDC/Police Death (Enemy Action)

• Friendly Fratricide

• Non-Lethal Fire Fratricide

• Homicide/Suicide Bomber Attack (Dismounted/Vehicular)

• Missing Soldier/Civilian/Contractor (POW/Missing/AWOL)

• Detainee

• Downed Aircraft

• Demonstration/Riot

• Power Outage in Town

• Oil Line Sabotage

• Oil Line Stops Flowing

• Mass Grave Found

• WMD Site Located

• Deck of Cards Information/Intelligence

• Division Contacts BCT for Raid

• Refugee Crisis

• Short Fuse Tasking

• Bridge Collapse/Destruction

• MSR Blocked by Enemy Activity

• MSR Blocked by Civilian Activity

• Local National Murders Another Local National

5-28

• NGO Is Attacked/Killed

• VIP Visit

• DIV or Higher Convoy Escort

• Wrongful Killing of Detainee

• Wrongful Killing of Civilians

• Potential War Crime by U.S. Soldier

• U.S. Soldier Felony Crime

• ROE Violation Reported

• FOB Security Breach

• FOB Mortar Attack

• Mass Casualties (Five or More in a Single Incident)

• Critical Friendly Communication Failure

• Counter Radar Breakdown

• WMD Employed (Intentional/Accidental)

• PAO Emergency

• Minefield Located

• Political Asylum Seeker

• Stolen/Missing Sensitive Item

• Change in Task Organization BN or Higher

• Change in Unit Area of Operation BN or Higher

• Clearance of Fires

• Close Air Support

• Counterfire

• VBIED/IED Attack

5-29

Figure 5.13.1-1. Battle Drill Flowchart

5.13.2 Example Battle Drill Proponent: S3 Action: S1, S2, FSE, S3 Air, ALO, ENG BATTLE DRILL: Counterfire CONDITIONS: The BCT Staff receives a Counterfire Mission.

5-30

STANDARDS: The BCT Staff: 1. S3 Battle CPT immediately disseminated report to selected staff

according to SOP. 2. Assessed the impact on BCT operations. 3. Determined appropriate response, notified appropriate units and

individuals.

Table 5.13.2-1. Status of Task Steps and Performance Measures

TASK STEPS & PERFORMANCE MEASURES STATUS • Date/Time • Sensor: Q-36, Q-37 • Type of weapon system • Origin/Impact/Altitude • Action Taken • Any WIA/KIA

Current OPS Staff initiates internal requirements, conducts hasty analysis, develops recommendations, provides input to CHOPS: • S1: Replacements, escorts, documents processing. • S2: Coordinate with Fires; perform trend analysis,

analyze information from crater analysis. • S4: Assess property destroyed. • ENG: Coordinate reconstruction efforts. • FSE: Assist S2 in information collection through FS

channels. • S3 Air: Coordinate with FSE. • ALO: Air Component asset availability for

surveillance/CAS. • ASAS, -WS & TMC-GW in CP1 & CP2 subscribe to

AIS PASS for observed location overlay published by FBCB2.

CHOPS • Recalls the current OPS Staff to a huddle. • Gathers recommendations. • Develops current OPS assessment/recommendations

to S3 • Briefs S3 on current OPS actions/recommendations.

5-31

TASK STEPS & PERFORMANCE MEASURES STATUS

S3/S2 Battle CPT: • Continues to update CHOPs with information from

LNOs or higher • S3 OPS MCS WS receives VMF Near Real Time

Server (NRTS) object type “SPOT” on CP LAN (Multicast group) from CP2 MCS Gateway via NRTS Service Broadcast and displays on COP

S3 receives recommendations from CHOPS, provides guidance.

CHOPS disseminates / supervises execution of guidance.

5.13.3 SUPPORTING COLLECTIVE TASKS:

ART 5.3.4 Manage Information and Data Task: 20-6-7261.6400 Maintain the Common Operational Picture (COP) ◦◦Tailored to the User’s Needs (Staff)

Task: 20-6-7262.6400 Manage Relevant Information (Staff)

ART 5.3 Assess Tactical Situations and Operations Task: 20-6-7362.6400 Evaluate Situation or Progress of Operations (Staff)

Task: 20-6-7363.6400 Develop Staff Estimates (Staff)

ART 5.3 Integrate Information Superiority Contributors Task: 20-6-7661.6400 Synchronize Tactical Operations (Staff)

Task: 20-6-7662.6400 Coordinate Sustainment Operations (Staff)

ART 5.2.5 Maintain Unity of Command Task: 20-6-7863.6400 Brief the Brigade Combat Team Command Post Using the Battle Update Briefing (BUB)

Task: 20-6-7864.6400 Brief the Brigade Combat Team Command Post During a Shift Change)

ART 1.4 Conduct Direct Fires Task: 20-6-3161.6400 Process Targets Using the Decide Function for the Brigade Combat Team)

Task: 20-6-3261.6400 Detect Targets to Attack for the Brigade Combat Team)

5-32

Task: 20-6-3262.6400 Deliver Lethal and Non-Lethal Fires on Targets Using Attack Guidance Developed in the Decide Function)

Task: 20-6-3263.6400 Process Targets Using the Assess Function for the Brigade Combat Team)

ART 3.1 Integrate Fires OPFOR TASKS AND STANDARDS: None REFERENCES:

• FM 3-0, Operations, 14 June, 2001

• FM 3-09 Fire Support BATTLE DRILL: Counterfire EVENT: BN reports a platoon-sized combat patrol convoy, composed of two M3A3s and three up-armored M1114, has been ambushed along Hwy 1, vic: 38SMC324002. Patrol was engaged by mortars, small arms, and RPG fire. Patrol estimated there are approx 50–60 enemy fighters. Patrol called for immediate attack helicopter support and counter fire artillery. Three warfighters were wounded and two M1114s were destroyed. Warfighters were taken by vehicle to BAS. M1114s need to be recovered.

See Enemy Reporting [Incoming to ASAS – ACE SA] chart for steps that ASAS Operator/S2 take to process incoming messages and incorporate into All Source Correlated Database. For additional Tools, SOPs and other Doctrinal assists go to this page: https://www.milsuite.mil/wiki/Portal:Standard_Operating_Procedures

Chapter 6 Sustaining the Command Post

This page intentionally left blank.

6-1

Chapter 6.0 Sustaining the Command Post (CP)

6.1 Introduction CP sustainment is the process of managing personnel safety, fuel consumption, power management, environmental impacts, and maintainability of equipment. In order to compensate for the trade-offs encountered between effectiveness and survivability, proper sustainment techniques should be developed and implemented to ensure maximum life cycle longevity. The content within this section can be used to augment a unit’s existing sustainment plan.

6.2 Daily Operation Outline of duties and tasks to be considered in planning and sustaining CP operations. These should include fuel consumption factors, maintenance intervals, extreme environment issues, and best practices for conduction duties and tasks with regular 24-hour events, such as shift change. Table 6.2-1 gives examples of daily duties.

Table 6.2-1. Daily Duties

Daily Duties • Fuel Generators and CP • Verify wind lines are tight and

secure around CP • Clear log/queues on CP

FBCB2/BFT • Verify electrical grounding

• Confirm INFOSYS operators perform daily maintenance

• Visually inspect internal/external cables & connections

• Maintain information resources • Verify security perimeter • Clear fans on Information

Systems • Check CP for damage

• Check maintenance schedules for power generation units

• Shred all classified and unclassified documents

• Check maintenance on CP vehicles

6-2

6.3 Safety

6.3.1 This section outlines safety concepts and considerations that unit and section leaders should be aware of to plan, configure, set up, operate, and train for CP operations.

6.3.2 Use ground guides when positioning vehicles, Tactical Quiet Generators (TQGs), Trailer-Mounted Support System (TMSS) trailers, and Light Tactical Vehicle (LTV) trailers.

• Set parking brakes.

• Place chock blocks around wheel.

• Place drip pans under engine drip points.

• Install Surface Wire Grounding System (SWGS) and attach to Rigid Wall Shelter (RWS) Power Entry Panel (PEP) ground lug and LTV bumper ground.

• Wear eye protection, gloves and helmet when driving grounding rods

6.3.3 Comply with applicable Command Post (CP) subsystem Technical Manual ™ setup procedures.

6.3.4 Cabling

• Visually confirm that cables are routed with appropriate bend radius and support, inspect for visible exterior damage and sharp edges that can cause insulation damage.

• Minimize trip hazards using proper cable routing, cable guards, etc. Mark remaining hazards.

• Visually inspect that connector pins are not bent. Document cable pin-to-pin continuity is correct.

• Visually confirm color-coded or keyed connectors are properly mated.

• Visually confirm that connectors or cables do not protrude into aisle ways, significantly impeding egress.

• Visually confirm that cables have permanent and legible identification within 2 inches of both cable ends.

• Visually confirm that exposed wiring and cable condition is not cut or crushed.

6-3

• Visually confirm all AC-powered remote equipment is supplied from Ground Fault Circuit Interrupter (GFCI) protected outlets or surge protection devices.

6.3.5 Grounding

• Visually confirm that path from tie point to ground is continuous and secure

• Visually confirm that ground lug connectors are present, marked and tightened.

• Verify equipment case grounding to external ground point continuity and resistance less than 100 Ohms (25 Ohms preferred). Verify ground cable amps are sufficient to carry maximum fault current to ground.

• Visually confirm shelter grounding terminal is identified and marked with warning to establish ground before applying power.

6.3.6 Antennas

• Erect no antennas within two times the antenna height to the base of the power lines.

• When setting up antenna farm, consider adding additional guy wires if bad weather is expected.

• Clearly mark antenna farms with engineer tape or signs.

• Insure vehicle-mounted antenna tips are present and secured to protect against eye injury/puncture.

• Verify that personnel positions are beyond the minimum safe distance to operating antennas and visually confirm general RF safety markings present near antenna access.

6.3.7 Hazardous Materials (HAZMAT)

• Enforce no smoking or welding within 50 ft of refueling, solvent use, or flammable storage points.

• Comply with local installation HAZMAT procedures for storing and disposing of Petroleum Oil and Lubricant (POL) products, cleaning solutions, and contaminated waste.

6-4

• Set up HAZMAT spill barriers around fuel truck points

• Set up HAZMAT spill kits inside soft shelter entrance point.

• REMOVE to CH 3: set up HAZMAT spill point around Emergency Fuel Point.

6.3.8 Place TMSS and TQG trailers at max distance from tents.

• TMSS- Medium recommended distance is 10-12 ft.

• TMSS-Large recommended distance is 20-22ft.

• TQG recommended distance is 50ft.

• Visually confirm that systems are positioned where exhaust from one will not enter another’s fresh air intake or blow into occupied tents/shelter.

• Verified bubble level touch ring (MIN) on the TMSS trailers. o Wear PPE when driving grounding rods. o Visually confirm all circuit breakers OFF before

starting the engine. o Do not attempt service or adjustment to electrical

connections until GenSet is OFF and completely de-energized.

6.3.9 Lighting

• Place tent lighting high enough to prevent head strikes.

• Connect light sets with power OFF.

6.3.10 Shelter Life Safety

• Maintain a clear egress path and mark exits for each tent.

• Set up fire extinguisher points near each shelter exit and power systems.

• Set up medical aid point. o Provide minimum first aid kits and resuscitation

equipment per unit requirements.

6-5

o Identify personnel trained as emergency life savers. Ensure that all personnel know emergency contact number.

o Follow Technical Bulletins Medical (TB MED) guidance for heat and cold stress.

• Ensure the RWS ladders are in contact with ground before using.

6.3.11 Transit Case Setup

• Visually confirm presence of lift labels on items that exceed 37 lb. Use proper number of lifters per MIL-STD-1472F guidance.

• Connect all Operational Transit Cases (OTCs) to a ground, with power OFF prior to use.

• Connect fiber optics with power OFF to avoid Ultra Violet (UV) eye hazard.

• Connect INFOSYS with power OFF.

6.3.12 Operation

• Identify unobstructed emergency egress routes for vehicles in the CP complex should they need to be moved quickly.

• Protect and/or mark head strike hazards

• Enforce personnel use of Personal Protective Equipment (PPE) where required (around operating generators, pounding metal stakes, etc.).

• Confirm that noise levels are less than 85 dBA (82dBA for 12-Hr operation). Hearing protection, as recommended by medical or safety officers, must be worn within identified noise hazard areas.

• Confirm that shelter floor, step surfaces of roof and ladder climbing and access surfaces for elevated equipment (e.g., Environmental Control Unit [ECU]) are equipped with nonskid pads.

• Maintain filler nozzle and fuel tank contact and attach boding wires where available to avoid static spark ignition of fuel vapors.

6-6

• Discharge static electricity from the body by touching a metal chassis or cabinet before touching electrostatic discharge (ESD)-sensitive electronic components, otherwise, internal circuits can be destroyed.

• Follow Lithium Battery guidance to avoid runaway (especially lithium sulfate non-rechargeable battery). o Recharging o Direct shorts and high draw loads o Use of Complete Discharge Devices (CDDs) o Maximum storage temperatures. o Disposal per Unit requirements o Remove conductive jewelry for electrical/battery

operations and maintenance.

• Remove power before making/breaking electrical connections.

• During storms, follow lightning guidance in Communications Electronics Command (CECOM) TR-98-6, Earth Grounding and Bonding Pamphlet, Oct 1998 (Appx.F).

• Inspect and correct sharp edges that may have been created in transportation, handling, or setup.

• Do not store lithium batteries in Ops, break rooms, smoking areas, or any space normally occupied by people. Lithium batteries should be segregated from other types of batteries.

6.3.13 Maintenance

• Cool down hot engines before performing Preventive Maintenance Checks and Services (PMCS) or require PPE use.

• Visually confirm that fuel lines and connections are not leaking or subject to moving part damage.’

• Require qualified persons for hazardous electrical tasks and practice the buddy system.

6-7

• Remove power when possible during electrical circuit work.

• Shut down rotating equipment when possible for servicing.

• Use appropriate PPE for tent repair adhesives.

6.3.14 Move Preparations

• Comply with TMs and unit load plan directives, including Warnings/Cautions when packing vehicles and trailers. Adhere to approved load plans.

• Confirm that load plans are not causing a weight and center of gravity problem for the carrying platform (cannot exceed the Gross Vehicle Weight [GVW] for the vehicle and towing limit, including its trailer system).

• Properly tie down whip antennas.

• Connect safety chains, light, and brake connections to trailers. Verify proper operation of trailer and vehicle lights.

6.4 Information Systems (INFOSYS)

6.4.1 Keeping laptop computers laying flat on table tops for extended periods can lead to overheating, degraded performance, and possible system damage. Utilize locally purchased cooling devices or docking stations to keep systems cool. If these are not available, use the power adapter or another item to lift the back to the laptop off the table about 1 inch to allow air flow.

6.4.2 Ensure proper air flow around transit case-mounted systems to prevent overheating.

6.4.3 At a minimum, clean air filters on projectors to ensure continuous operations.

6.4.4 Maintain a stock of spare bulbs for projectors to ensure continuous operations.

6-8

6.4.5 Only use approved methods for cleaning computer and display systems. The use of non-approved solutions and devices can damage these systems.

6.4.6 Maintain steady and interrupted electrical supply, units utilize locally purchased Uninterruptible Power Supply (UPS). Most crucial reason to use UPS is to obtain continuous power supply, clean and noiseless current, stable current output and prevent temporary power surge or drop by generator power. UPS allowed user to save INFOSYS products when CP blackout by a warning beep.

Chapter 7 Fielding and Training

Support

This page intentionally left blank.

7-1

Chapter 7.0 Fielding and Training Support

7.1 Introduction

This chapter summarizes the Unit Set Fielding process and the Army Forces Generation (ARFORGEN) process. Manning of information systems, specific mission operations specialties, and the commander's use of his Mission Command System are not within the scope of this handbook.

7.2 Unit Set Fielding (USF)

7.2.1 The ARFORGEN cycle and the USF process are holistic approaches to warfighting and equipping Army units. Although the two processes are not directly aligned by phase and cycle, they are synchronized to achieve the desired end state of trained and ready combat forces.

7.2.1.1 USF consists of 5 phases (Figure 7.2.2-1) which are NOT directly aligned with the ARFORGEN cycle. The 5 phases are: • Phase I: Planning for Fielding and Engineering • Phase II: Fielding Execution (Note: Phase II is broken down into Phase IIA and Phase IIB) • Phase III: Supporting While Deploying • Phase IV: Supporting While Deployed • Phase V: Reset to DA Readiness Standards

7.2.1.2 USF is an orders-based, 5-phase process that manages the planning and implementation of fielding and reset for all major Army tactical Command, Control Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) capabilities. The U.S. Army and the organizations of the Communications-Electronic Life Cycle Management Command (CE-LCMC), simultaneously provide the warfighter with the C4I equipment needed to perform a mission in combat. [To be clear, PMs field C4I equipment and CECOM sustains the equipment.]

7.2.1.3 PEO C3T's desired end state for the USF model is: • Quality systems architecture and data products provided

in a timely manner • All systems across the PEO C3T synchronized and

focused on fielding windows of opportunity

7-2

• All required resources planned, programmed and executed

• Development and delivery of an integrated, holistic mission command capability to all Army units, as directed by Headquarters, Department of the Army (HQDA)

7.2.1.4 USF Phases – The USF model is divided into five phases:

7.2.1.5 Phase I. Planning for Fielding and Engineering This entails the preparation and execution of materiel fielding, scheduling of New Equipment Training (NET), and work on the initial Systems Architecture (SA). The main effort during this phase is PEO C3T; all other organizations are in support. The phase includes the following: • Publishing the USF schedule • Identification of the units to receive MC systems • Organization and execution of the initial site survey and

the conduct of new materiel information briefings (NMIBs) • Detailed scheduling of all NET classes • All initial system engineering work The end state for Phase I is the following: • A USF timeline, supportable SA, and data product

development plans • NET operations planned for, coordinated, and confirmed

with the unit

7.2.1.6 Phase II. Fielding Execution This phase occurs in two sub-phases: • Phase IIA – This sub-phase consists of implementing the

total package fielding effort as defined in Phase I planning documents, fielding agreements, and coordination conferences with the Army Command and / or unit. This sub-phase includes the following: − System hardware, software, and documentation

distribution and issue to the gaining unit − Joint inventory and property book transfer − Conducting PM-scheduled and -controlled

system-specific NET activities − Completion of individual acceptance and handoff

activities and documentation − The conduct of Mission Command System Integration

(MCSI) training

7-3

The end state for Phase IIA is the: − Successful delivery, issue, and initial training of

individual systems' functionality − Successful completion of MCSI − Use of data products during the conduct of MCSI

• Phase IIB – In this sub-phase, the supporting unit undergoes collective training events for the reinforcement and honing of MC skills acquired during NET. This sub-phase includes all CP training events following the conduct of system-specific NET activities, and support for unit-scheduled and -conducted training events, including the following: − CP Exercises (CPXs) − Field Training Exercises (FTXs) − Mission Command Training Program (MCTP) events − Digital Exercises (DIGEXs)

• Support for deploying unit MREs is also part of this sub-phase. This sub-phase includes monitoring "Get Well" plans and correcting any fielding discrepancies noted in the Phase IIA fielding implementation process and handoff. The end state for Phase IIB is the: − Successful use of training data products and CP

capabilities during the conduct of a major FTX/MRE/ CTC rotation

− Return unit to its home station − All "Get Well" plans for fielding discrepancies resolved

7.2.1.7 Phase III. Supporting While Deploying In this phase, the unit receives support following its CTC rotation or MRE and during preparations for deployment at home station and in-theater Reception, Staging, Onward Movement, and Integration (RSO&I) operations prior to moving to battle positions. The phase includes the following: • Support for a unit's home station deployment operations

following its return from MRE/CTC rotation • RSO&I operations in the theater of operations • Exercise of both the upper and lower Tactical Internets

(TIs)

7-4

The end state for Phase III is the following: • Successful exercise of the upper and lower TIs • Depart from RSO&I area to battle positions, commence

unit sustainment by in-theater CE-LCMC support infrastructure

7.2.1.8 Phase IV. Supporting While Deployed In this phase, the unit receives support after RSO&I is complete. The unit is deployed to its designated battle position and is actively conducting its in-theater mission. The main effort during this phase is CE-LCMC; all other organizations support. This phase includes all actions to support the unit: • After it moves from its designated in-theater RSO&I area

to its battle positions • After it moves from its designated in-theater RSO&I area

to its battle positions • During the unit's conduct of its in-theater mission • During the unit's return to its designated in-theater

redeployment staging area in preparation for its return to its home station.

The end state for Phase IV is when the unit has been properly supported during the conduct of its in-theater mission and begins arriving at the in-theater redeployment staging area.

7.2.1.9 Phase V. Resetting to Headquarters – HQDA-Directed Readiness Standards Phase V begins when the first unit arrives at the in-theater re-deployment staging area and includes all actions at the staging area and at the unit's home station. If the unit is to undergo equipment NET or upgrade upon its return to its home station due to a significant change in software or hardware, a USF-phased execution plan will be implemented. The end state for Phase V is when the unit has been reset to HQDA-directed readiness standards and selected Phase IIA actions are commenced.

7-5

7.2.2 The approximate timeline for the above USF model is shown in Table 7.2.1-1 below.

Table 7.2.1-1. Model/Steps with Timeline and Corresponding Phase

Model/Steps Timeline (months)

Corresponding Phase

1. HQDA G-3 USF Fielding Schedule T-24 Pre-Execution 2. G-3 / G-8 Publish USF Execution Order T-9 Pre-Execution 3. G-8 Fielding Equipping Conference T-6 Phase I 4. Division G-3 / G-5 / G-7 / brigade S-3 &

PEO C3T NET Fielding Synchronization Conference (at unit location). Includes conduct of detailed site survey

T-5 Phase I

5. Conduct individual system and collective SoS NMIBs

T-4 Phase I

6. Execute PM individual NET T-Day Phase IIA 7. Deliver training data products to unit T+2 Phase IIA 8. Execute MCSI T+3 to 6 Phase IIA 9. Execute SICPS NET/Reset T+3 to 6 Phase IIA 10. Unit-led / PEO C3T-supported “in TOC”

COMEXs / DIGEXs / CPXs / FTXs T+7 to 12 Phase IIB

11. Unit CTC rotation / MRE T+13 Phase IIB 12. Unit deploys to in-theater RSO&I site &

receives GTW data products T+16 Phase III

13. Unit deploys to in-theater battle positions & conducts required missions as directed by in-theater commander

T+17 Phase IV

14. Unit re-deploys to home station for reset. Cycle begins again.

T+23 to 24 Phase V

7.2.2.1 The ARFORGEN cycle has 3 phases (Figure 7.2.2-1): Reset – During the RESET Phase, the unit’s equipment is brought to DA readiness standards. Individual training commences. Units in the RESET pool are not ready or available for major combat operations. However, they should be ready to respond to homeland defense requirements and provide defense support to civil authorities at all times.Train/Ready – Units in the Ready Force complete individual training, conduct mission-specific collective training and are eligible for sourcing necessary to meet joint requirements. Their collective training is designed to focus on their METL. Available – Units in the Available force pool are in their planned deployment windows and are fully trained, equipped and resourced to meet operational requirements.

7-6

Figure 7.2.2-1. Phase V Unit Set Fielding and Reset

7.2.2.2 During the ARFORGEN Reset Phase there are “select individual training tasks” which occur. The balance of the individual training and collective training, including Mission Rehearsal Exercises (MREs)/Mission Readiness Exercises (MRXs) occur in the Train/Ready Phase. There are some new fieldings which occur during the Reset Phase with the balance of fielding’s being completed during the Train/Ready Phase.

7.2.2.3 Reset, as defined by the DA Execution Order, has 3 phases which are NOT directly aligned with the ARFORGEN cycle. The 3 phases are as follows: • Phase I: R-180 to R (In Theater Phase) • Phase II: R to R+180 (RESET Phase) • Phase III: Starts at R+181 and ends when a unit moves

into the Available phase of the ARFORGEN cycle (Train/Ready Phase). Phase III starts at R+181 and goes through the entire Train/Ready phase of the ARFORGEN cycle.

7.2.2.4 In general terms the ARFORGEN, USF and Reset are aligned as follows: • Reset Phase of ARFORGEN encompasses Unit Set

Fielding Phases I, part of Phase IIA and V and Reset Phase II.

• Train/Ready Phase of ARFORGEN encompasses part of USF Phase II A, and all of Phases IIB and III and Reset Phase III.

• Available Phase of ARFORGEN encompasses USF Phase IV and Reset Phase I.

7.2.2.5 As previously indicated, these Phases do NOT align directly. For example, Reset Phase I is from R-180 to R. The Available Phase starts well before R-180, so Reset Phase I takes place only for a portion of the Available Phase.

7-7

7.3 MCSI Overview

7.3.1 The MCSIT supports the integration of the unit command post as a mission command system (personnel, networks, information systems, processes and procedures, facilities and equipment) to ensure the staff is confident establishing and employing the system to support the commander’s decision making. All training is executed in the unit’s CP using the unit’s equipment. MCSI is coordinated and scheduled at the Program Executive Office-Command, Control, and Communications Tactical (PEO-C3T) Unit Set Fielding (USF) or Forces Command (FORSCOM) UERC conferences, and is executed during the USF Phase II/ARFORGEN Train-Ready phase. All training is executed in the unit’s CP using the unit’s equipment. MCSI is coordinated and scheduled at the Program Executive Office-Command, Control, and Communications Tactical (PEO-C3T) Unit Set Fielding (USF) or Forces Command (FORSCOM) RESET conferences, and is executed during the USF Phase II/ARFORGEN Train-Ready phase.

7.3.2 The training is facilitated and executed by Product Manager CP Systems and Integration (PdM CPS&I), who coordinates with other PMs/PdMs to facilitate MCSI. The training uses pre-developed orders, scenarios, and situational injects to train the battle staff on staff functions, battle drills, and INFOSYS integration. The training focuses on staff and system processes.

7.3.3 The primary focus for the training is the brigade staff; however, units may establish and incorporate subordinate Battalion (BN) CPs and staffs into the training. If BNs are included, all formal training occurs within the Brigade CP, with BN staff personnel returning to their respected CPs for the practical exercises. Trained units should anticipate and plan around personnel and INFOSYS density, as well as brigade CP size, when planning BN staff inclusion into the training.

7-8

7.3.4 MCSI Sequencing. The diagram below depicts a typical sequencing of MCSI in conjunction with USF Phase II events.

Figure 7.3.4-1. Typical Sequencing of MCSI

7.3.5 Event I Training is a 4-day event designed to establish the unit’s CP in order to validate CP infrastructure and network. The unit accomplishes specific tasks each day based on PdM CPS&I-provided event schedules. Progress is tracked by the unit using CP status charts and After Action Reviews (AARs) conducted at the end of each day. The end state for Event I is the successful integration of all CP equipment, and unit confidence in the ability to set up and integrate their equipment and restore capability upon major failures.

7.3.5.1 Event I consists of Enabling Learning Objectives (ELOs) based on the Terminal Learning Objective (TLO) Establish the Command Post. The following are the ELOs: • Event I Overview • Establish SICPS • Establish Power Grid • Establish Section Cells • Establish CP Network and Configure INFOSYS • Conduct Voice and Data COMEX

7.3.5.2 The key tasks for Event I are: • Set Up CP Infrastructure. The unit erects Trailer-Mounted

Support System (TMSS) tents; places tables and chairs; establishes power, environmental control, and lighting; and emplaces systems within the CP.

• Establish the Network. The unit emplaces required network cabling, powers up network and INFOSYS servers, establishes unit domain, powers up INFOSYS and other computers, establishes CP displays, validates network connectivity, and validates both system intra-operability and inter-operability among fielded INFOSYS.

• Inject Failure and Restore Capability. The unit experiences and recovers from failures to power generation, network, systems, and domain.

7-9

• Voice and Data COMEX. The unit verifies voice and data communications for all CP systems (fielded and organic) using a series of Communication Exercises (COMEXs).

7.3.6 Event II Training follows Event I. Event II is a 4-day event conducted in the unit’s command post, using unit equipment to execute command post operations. The training audience is leaders, battle captains, battle NCOs, and key system operators. The training method used is a combination of lecture, demonstration, and practical exercises (PEs). Lecture and demonstration occur in the current operations cell of the Brigade CP, and the unit personnel return to their CP cells to use their INFOSYS to conduct PEs. If the brigade includes personnel from its subordinate BNs in the training, those personnel will conduct the PEs in their respective BN CP. The end state for Event II is a staff with increased level of confidence in abilities to execute CP operations using the INFOSYS as a system of systems. Event II consists of the following ELOs based on the TLO Manage Tactical Information:

• Event II Overview (includes INFOSYS Overview) • Process Higher Command’s Order • Develop Staff Products • Create a Common Operational Picture (COP) • Conduct a Collaborative Briefing Using INFOSYS • Publish Unit Order • Process Event Information

7.3.7 Event III Training is the Mission Command System integration Exercise which is tailored to a specific unit exercise such as a CPX, STAFFEX, or WFX. During Event III the team provides integration training and support to the unit staff in support of the commander’s training objectives. The Event III end state is staff confident in their abilities to establish the CP, establish the network, and conduct CP operations with all equipment as a SoS.

7.4 Digital Systems Engineer (DSE) Roles and Responsibilities

7.4.1 DSEs provide the unit a world-wide, single interface for Team C4ISR and PEO-C3T managed Command Control Communications Computers, Intelligence Surveillance and Reconnaissance (C4ISR) and enables technical, planning,

7-10

and training support to Army formations from BCT level to Corps level during all cycles of the ARFORGEN model.

7.4.2 Operational Concept

7.4.2.1 The DSE program is Team C4ISR and PEO C3T’s primary arm throughout all Army formations (BCT through Corps), as well as things pertaining to digital C4ISR systems and enablers during Unit Set Fielding (USF) phases, supporting combat commanders in continuous, full-spectrum expeditionary operations. DSEs provide a single-point interface between units, and PEO C3T’s, C4ISR Field Support Branch (CFSB) allowing the commander and staff a single point of contact to access all the resources available for MC Systems and enablers. A DSE is typically assigned at BCT - Corps echelons during a digital exercise or RESET event. The DSE performs the following: • Serves as the Team C4ISR “Team Captain” in BCT

through Corps units • Provides leadership, organization and synchronization of

ABCS and enabler, FSE/FSR provided support training • Acts as the SME for C4ISR and enablers, technically,

logistically and operationally • Acts as the master gunner of digital TTPs in support of

MC as a weapon system • Applies advanced methodology, research, training and

TTPs for networking, configuration, and software and hardware problems

• Troubleshoots complex SoS and network malfunctions, coordinating with PM/PdM for support with identified issues and tracks them through to resolution

• Provides the commander a fully-deployable, single-unit interface for Team C4ISR and PEO-C3T supported products throughout the entire ARFORGEN process

• Advises the commander, assists in training leaders and soldiers on capabilities, integration and employment of the C4ISR SoS and supporting enablers

• Synchronizes logistics for external support throughout all phases of MC/USF

7-11

7.4.3 Lead DSE The Lead DSE is the DSE at the highest participating echelon in the MC/USF process for a particular fielding, exercise or deployment. For example, in a BCT MRE in which the HICON is the division headquarters, the division level DSE is the Lead DSE. DSEs are responsible for coordination and management of all Team C4ISR and PEO C3T support to the unit. In this role, they coordinate, manage and oversee the activities of all subordinate DSEs and FSRs at their respective echelons. The Lead DSE falls in on the support plan and organization established by the C4ISR Regional Plans and Operations (RP&O) office for that region, most often during Phase II of USF. At some point prior to Phase III, the Lead DSE accepts responsibility as directed by the RP&O and becomes responsible for all DSE support to the entire organization as well as support provided personally to the organization at the lead’s own echelon

7.4.4 Professional Imperatives The DSE must establish a rapport with the supported organization to be regarded as a valued member of the organization’s staff. This relationship should establish the DSE as the single individual to whom the organization turns to address any questions or issues pertaining to MC/USF. Such a relationship is based on the professionalism, technical expertise, proactive support, responsiveness, attention to detail, and thorough follow-up in all aspects of the DSE’s duties supporting the organization. This approach will inevitably make an immediate and sustained positive impact on the organization’s leadership and give it confidence in the DSE’s leadership and experience.

7.4.5 DSE Tasks The DSE is a C4ISR SME who is knowledgeable in System Administration (SA) and system operation (being both hardware and software capable) The DSE is able to address integration and configuration issues and serve as the Team C4ISR and PEO C3T software configuration control representative, troubleshooting system failures and resolving the majority of digital problems on site for the unit. If the DSE cannot resolve the problem, they are able to contact the responsible PM/PdM or other SME for assistance. When DSEs are embedded with Army BCTs through Corps units, they are deployable worldwide. They can provide “over the shoulder” training and a feedback conduit between units, PEO C3T, PM/PdM, and the CFSB.

7-12

7.4.6 Specific DSE Tasks by Phase Table 7.4.6-1, summarizes DSE tasks specific to a certain phases:

Table 7.4.6-1. DSE Tasks All MC/USF Phases

• Technical/operational issue identification, tracking, & resolution

• SoS lead for SEC/PEO C3T supported products

• Conduit between unit & PEO C3T CFSB

• Unit SME for SoS • Provide MC/USF phase reporting • Provide AFSB reporting • Attends G6/S6 meetings • Provide input for USF COP

Phase I – Planning (Lead: PEO C3T - PM CP) • Attend regional all-hands meetings • Attend SCR/trail boss/LAC meetings • Assist unit in data products ERB • Attend USF Synch Conference • Monitor NET schedule/execution • Initiate relationship with commander, XO,

S3, and S6

• Attend/support force modernization meetings (division/corps/installation)

• Initiate coordination meetings as lead for Team C4ISR/PEO C3T supported products as an SoS

• Attend PdM NMIB • Communicate command areas of

concern to ALT community Phase II – Fielding Execution (Lead: PEO C3T - PM MC)

• Attend regional all-hands meeting • Attend SCR/trail boss/LAC meetings • Lead/conduct TOC checkouts • Track/facilitate data product delivery • Provide technical support & leadership

during unit collective training • Support DSI-NET, as required • Conduct pre-deployment planning:

- Support roster - Conduct pre-deployment IPR with

FSR/FSE team - Coordinate refinement of GTW data

products

• Submit daily & weekly DSE report via C4ISR Support Operations Center

• Coalesce all PEO C3T issues • Participate in CFSB D-90, D-60, and

D-30 meetings • Attend CTC D-90 conference • Attend LTP with unit • Facilitate technical & operations • Submit incident reports via CFSB SOC • Lead BUB at CTCs

Phase III – RSOI (Lead: PEO C3T - PM FBCB2) • Attend regional unit BUB/CUB • Attend unit maintenance meeting • Provide daily PERSTAT report • Provide reach back to PEO C3T • Account for team property • Deploy to support unit set up and

preparation in country • Plan, coordinate, and lead execution of

DC2R • Coordinate life support for PEO C3T

FSR/FSE with BLST

• Coordinate & adjust movement of FSR/FSE personnel and equipment into sector

• Assist and participate in the unit orders process

• Provide technical and operational support to unit; serve as SIF

• Provide daily reports • Submit incident reports via CFSB SOC • Interface with AMC BLST to account for

team

7-13

Phase IV – Combat Operations (Lead: CE LCMC LRC)

• Attend regional unit BUB/CUB • Attend unit maintenance meeting • Provide reach back to PEO C3T • Account for team property • Establish connectivity & sustain • Provide OTS training as needed • Facilitate technical/operational issues • Input incident reports into the C4ISR

Support Operations Center; close out reports

• Provide daily DSE reports

• Interface daily with USAMC BLST and unit S6

• Account for property of team • Coordinate team life support from unit

and USAMC • Coordinate & plan reset action; plan for

redeployment • Lead force protection drills • Coordinate movement of contractors on

battlefield with unit & BLST • Plan & coordinate redeployment of unit

and FSR team equipment • Assist in unit reset order development

Phase V – Reset / Reconstitution (Lead: CE LCMC LRC) • Attend regional all-hands meeting • Attend SCR/trail boss/LAC meetings • Help unit to identify/unpack equipment • Assist AFSB in tracking reset of C4ISR • Participate in NET • Plan & conduct TOC

checkouts

• Reestablish connection with new leadership

• Gather data to establish unit COP • Project support requests for collective

training • Support DSI-NET • Conduct all Phase I and II actions

7.4.7 Detailed Exercise Responsibilities

7.4.7.1 During an exercise or deployment, regardless of what type, the lead DSE: • Sends CCIR reports to CFSB leadership. • Assumes lead position of support team (e.g. signs for

facility, phones, handheld units, etc). • Gains NIPR network access for support contractors. • Links up with the AMC BLST and becomes a key player in

the daily BUB. • Maintains C4ISR operations facility. • Collects charts, assembles briefing, and posts slides to

the SIF, 15 minutes prior to the daily BUB. Hosts and facilitates the daily BUB.

• Sends Incident Reporting Module (IRM) Incident Reports to the SOC and follows through on issues until resolved, posting resolution documentation on the SIF.

• Interfaces with the CTC Operations Group, providing support and resolving issues, as requested.

• Works directly with Brigade DSEs and FSRs to meet unit support requirements and resolve issues.

• Addresses support requirements and assists with establishing FSR priorities.

7.4.7.2 Configuration Management The DSEs are central to Configuration Management (CM) in

7-14

a supported unit. They are responsible for obtaining software from the CM organization, submitting reports and performing other associated activities. They are responsible for the following: • Timely, accurate feedback in the form of documented

reports. • Knowing current versions of software and advising units

on what should be used. • Prompt dissemination of software upgrades and IAVAs to

the unit as fielded. • Assisting units with the instructions included in the “read

me” file before the unit installs and software or IAVAs (all software and IAVAs have a read me file). Assistance in loading and configuring as requested.

• Knowing the number of individual C4ISR platforms issued to the supported unit.

• Notice of receipt of any software and/or IAVA packages. • Weekly reporting of any problems related to the

installation of software or IAVAs. • Complete technical details when reporting issues

pertaining to CM. • Use the web-based platform when requesting DSE

toolkits. • Minimum number of working days for CM to assemble

software drops. • Maintains current knowledge of the Host-Based Security

System (HBSS). • Knowing the unit’s current status of cyber security

(HBSS).

7.4.8 The Brigade Logistic Support Team (BLST) The Brigade Logistic Support Team (BLST) Commander is administratively responsible for the DSE; however, the DSE usually works directly for the unit and the S-6. In some instances, the DSE reports to the unit Knowledge Management Officer.

7-15

Army Field Support Brigade (AFSB) & POCs For information on current Army Field Support Brigade (AFSB) and Points of Contact (POCs) see the Single Interface to the Field (SIF) Module at https://sif.kc.us.army.mil

7-16

Chapter 8 Equipment and

Maintenance

This page intentionally left blank.

8-1

Chapter 8.0 Equipment and Maintenance

8.1 Introduction

8.1.1 Accountability of the commander’s mission command system is managed through Property Book and Unit Supply Enhanced (PBUSE). See Chapter 3 for more information on training and assistance with the PBUSE system.

8.1.2 During the CP setup, this handbook provides valuable and relevant information regarding how to effectively establish the commander’s mission command system. The following section identifies the primary resources for setup, operation, and maintenance of each CP component.

8.1.3 Equipment maintenance, Repair Parts and Special Tools Lists (RPSTLs), and other system information can be found in the Technical Manuals (TMs) in Appendix A.

8.2 Troubleshooting Support

8.2.1 The primary goal of the Command, Control, Communications, and Computers Intelligence, Surveillance, and Reconnaissance (C4ISR) Support Operations Center (SOC) is to provide a single point of contact for end users in need of assistance. End users are warfighters/operators and civilian Field Support/System Engineers (FSEs) and Digital System Engineers (DSEs). The C4ISR SOC Team provides general systems information, Tier 1 maintenance assistance, responds to requests on procedural matters, and escalates Incident Reports to the appropriate agency. The C4ISR SOC performs three major functions:

• Assists warfighters and support personnel with all C2 systems issues

• Records, tracks, and resolves software, hardware, network, satellite, radio, and support issues

8-2

• Activates Commander’s Critical Information Requirements (CCIRs) Priority Intelligence Requirement (PIRs) for Program Executive Office - Command, Control, Communications Tactical (PEO-C3T) and Program Executive Office - Intelligence, Electronic Warfare and Sensors (PEO-IEW&S) in accordance with their commanders.

8.2.2 The SOC can be used to report issues, report training, request assistance, request information, and request support. The SOC uses the automated Incident Reporting Module (IRM) tool as a repository of information. Once the knowledge base is updated and in use, most users will be able to access an enormous amount of shared information. The SOC, DSEs, Field Service Representatives (FSRs) and warfighters will be able to use the Knowledge Base for quickly resolving issues. The SOC is the central point used to record, assist, direct, and resolve issues.

8.2.3 SOC contact is available through telephone, the IRM website, and Non-Secure Internet Protocol Router (NIPR) or Secure Internet Protocol Routing (SIPR) email.

• NIPR c4isr.support@us.army.mil

• SIPR soc.support@us.army.smil.mil

• Direct Dial 254-287-1608; DSN 737-1608

• Toll Free 1-877-839-0813

• FAX 254-618-7089; DSN 259-7089

• STE 254-618-7525; DSN 259-7525

8.2.4 Support follows a tiered approach. The SOC operates in Tier 1 through problem resolution. If the SOC cannot address the issue at Tier 1, the issue is escalated. The SOC gathers data to build the knowledge base for future self-service. The four tiers are:

8-3

• Field Tier is where most issues are discovered. The Field Tier support structure consists of DSE, FSEs, FSRs, and Logistics Assistance Representatives (LARs), in their Area of Responsibility (AOR). Warfighters normally notify a DSE or FSR, LAR, or S6 when they have a support need or experience a C4ISR issue. The Field Tier Support Structure helps the warfighter assess the issue and determine the urgency of the issue. The warfighters also have the ability to reach back to a centralized support center through a web portal for Tier 1 type support.

• Support Tier 1 is the initial line of defense in Support Tier 1 is the SOC, which is responsible for logging, tracking, and conducting initial fault analysis attempting to resolve the issue in the timeliest manner. When the SOC receives an Incident Report (IR), it is logged and assigned to the SOC Operator. The SOC Operator is responsible for the assignment from the cradle to the grave. It is the responsibility of the SOC staff to ensure the ticket is followed and updated from the time it enters the IRM until the time the ticket is resolved. SOC Operators are trained DSEs that have been deployed everywhere in the world that the U.S. Army has a presence. Every DSE working in the SOC is ex-military and both understands and has experienced the issues of the warfighter. When an issue comes into the IRM, the SOC Operator on duty decides whether they can quickly resolve the issue. If the Operator cannot resolve the issue, a person on the Tier 2 FSR list is notified. SOC personnel also provide additional reach-back capability into Support Tier 2 and the Effects Cell to resolve incidents.

8-4

• Support Tier 2 is comprised of members of the Effects Cell, FSRs, and System Engineers that have access to additional expertise on the specific Battlefield Functional Area (BFA) or systems. Each BFA will determine the appropriate Tier 2 level for their system, consistent with the overall concept of operations. The SOC keeps phone and email contact lists in order to place the right people into the fight to resolve the warfighter’s issues.

• Support Tier 3 has the most detailed expertise on the specific BFA or system. Tier 3 generally consists of actual hardware and software developers and others with in-depth knowledge of the system.

8.2.5 Cradle to Grave – Once a warfighter places a ticket into the IRM, they are notified through Army Knowledge Online (AKO) email each time there is a change to the ticket. If the SOC has a suggestion for a possible solution, the SOC provides the solution to the warfighter through email. If the issue is critical, the SOC calls the person that placed the ticket into the IRM to assist and refine the information needed to resolve the issue. SOC personnel, DSEs, FSRs, and System Engineers are required to log working information into the “Incident Work Info Field” located in the IRM ticket to keep everyone that is participating in the resolution process informed of the progress. Anyone involved in ticket resolution can view the progress of the ticket at any time.

8.2.6 The Analysis section of the SOC views and records all trouble reports and provides reports to commanders and senior persons in the community. The Analysis Section is comprised of two personnel trained to analyze the reports and information coming from the IRM. These personnel assess possible trends and perform analysis to give commanders useful information in assessing the process and progress of their units as they move through the different stages of the Unit Set Fielding (USF) process.

8-5

8.2.7 A ticket can be placed into the IRM using the IRM website https://hd.kc.us.army.mil/ or through the Single Interface to the Field (SIF) Module at https://sif.kc.army.mil. The IRM is the online tool to input incident reports online.

Users can also contact the SOC to enter an incident report.

Phone: 254-287-1608 / DSN 737-1608

Toll free: 877-839-0813

Fax: 254-618-7089 / DSN 259-7089

STE: 254-618-7525 / DSN 259-7525

Email-NIPR: ◦◦c4isr.support@us.army.mil

Email-SIPR: ◦◦soc.support@us.army.smil.mil

Web: https://hd.kc.us.army.mil

Figure 8.2.7-1. SIF Login Page

8-6

8.3 TQGs and PDISE Support

8.3.1 Tactical Quiet Generators (TQGs) and Power Distribution Illumination Systems Electrical (PDISE) are organically supported, maintained and repaired by trained warfighters. The first tier for maintenance and support of TQGs is the unit’s maintenance support company, located in the Brigade Support Battalion (BSB) for Infantry, Heavy, and Stryker BCTs. Each BSB has generator mechanics (MOS 52D or 52X) to support TQGs and PDISE in their brigade.

8.3.2 When a problem occurs with CP TQGs or PDISE, first contact the unit maintenance company before contacting the Power and Environmental (P&E) LAR. Notify P&E LAR so they are aware of the issue, but they are not meant to be the “first responder.”

Appendix A Reference

This page intentionally left blank.

A-1

Appendix A: Reference

For current DA approved publications, see Official Department of the Army Publications and Forms website at http://armypubs.army.mil/index.html Air Force Instruction (AFI) AFI 10-403, Deployment Planning and Execution Army Regulation (ARs) AR 220-1, Unit Status Reporting Army Doctrine Publications (ADPs) ADP 3-0, Unified Land Operations ADP 4-0, Sustainment ADP 5-0, The Operations Process ADP 6-0, Mission Command Army Doctrine Reference Publications (ADRPs) ADRP 3-0, Unified Land Operations ADRP 4-0, Sustainment ADRP 5-0, The Operations Process ADRP 6-0, Mission Command Field Manuals (FMs) FM 3-07, Stability Operations FM 3-90.5, The Combined Arms Battalion FM 3-90.6, The Brigade Combat Team FM 3-93, Theater Army Operations FM 4-01.30, Movement Control FM 4-01.41, Army Rail Operations FM 6-01.1, Knowledge Management Operations FM 7-15, The Army Universal Task List (Incl C1-10) FM 38-701, Packaging of Material: Packing FM 55-1, Transportation Operations, HQDA FM 55-80, Army Container Operations

A-2

Joint Publications (JPs) JP 1-02, Department of Defense Dictionary of Military and Associated Terms. JP 3-16, Multinational Operations JP 3-33, Joint Task Force Headquarters Training Circulars (TCs) TC 4-13.17, Cargo Specialist Handbook Military Standards (MIL-STDs) MIL-STD-1472F, Department of Defense Design Criteria Standard: Human Engineering. Technical Manuals (TMs) & Technical Bulletins (TBs) ACES TB 11-7010-293-10-2 SOFTWARE INSTALLATION GUIDE FOR THE AUTOMATED COMMUNICATIONS ENGINEERING SOFTWARE (ACES) WORKSTATION (AR)(NG) CCS TM 11-5895-1813-13&P (CCS) OPERATOR AND FIELD MAINTENANCE MANUAL INCLUDING REPAIR PARTS AND SPECIAL TOOLS LIST FOR COMMAND SYSTEM, TACTICAL AN/TSQ-243 (NSN: 5895-01-541-4812) (EIC N/A) (THIS ITEM IS INCLUDED ON EM 0164)

CPCS TM 11-5895-1874-13&P (CPCS-OTC) TECHNICAL MANUAL OPERATOR AND FIELD MAINTENANCE MANUAL INCLUDING REPAIR PARTS AND SPECIAL TOOLS LIST FOR COMMUNICATION SUBSYSTEM AN/TSQ-259 (NSN 5895-01-560-0273) (EIC N/A)

A-3

CPP TM 11-5895-1812-10 (CPP V-2/V-4) OPERATOR`S MANUAL FOR COMMAND SYSTEM, TACTICAL AN/TSQ-232(V)2 (NSN: 5895-01-535-9546) (EIC: N/A) AN/TSQ-232 (V)4 (5895-01-536-0109) (THIS ITEM IS INCLUDED ON EM 0164)

TM 11-5895-1812-23 (CPP V-2/V-4) FIELD MAINTENANCE MANUAL FOR COMMAND SYSTEM, TACTICAL AN/TSQ-232(V)2 (NSN 5895-01-535-9546) (EIC N/A) AN/TSQ-232(V)4 (NSN 5895-01-536-0109) (EIC N/A) (THIS ITEM IS INCLUDED ON EM 0164) TM 11-5895-1812-23&P (CPP V-2/V-4) Field RPSTL for Command System, Tactical, AN/TSQ-232(V)2 (NSN 5895-01-535-9546) (EIC N/A), AN/TSQ-232(V)4 (NSN 5895-01-536-0109) (EIC N/A). EPLRS TM 11-5825-299-10 MANPACK RADIO SET (MP-RS) AIRBORNE RADIO SET AN/ASQ-17D(V)4 (NSN 5820-01-502-4043) (EIC: N/A) GROUND RADIO SETS AN/PSQ-6D (NSN 5820-01-502-7234) (EIC: N/A) AN/VSQ-2D(V)1 (NSN 5820-01-502-4040) AN/VSQ-2D(V)2 (NSN 5820-01-502-4041) (EIC: N/A) AN/VSQ-2D(V)4 (NSN 5820-01-502-4042) (EIC: N/A) GRID REFERENCE RADIO SET AN/GRC-229D (NSN 5895-01-502-4044) (EIC: N/A) PART OF ENHANCED POSITION LOCATION REPORTING SYSTEM

TB 11-5825-299-10-1 OPERATOR POCKET MANUAL AIRBORNE RADIO SET AN/ASQ-177D(V)4 (NSN 5820-01-502-4043) (EIC: N/A) GROUND RADIO SETS AN/PSQ-6D (NSN 5820--1-502-7234) (EIC: N/A) AN/VSQ-2D(V)1 (NSN 5820-01-502-4040) (EIC: N/A) AN/VSQ-2D(V)2 (NSN 5820-01-502-4041) (EIC: N/A) AN/VSQ-2D(V)4 (NSN 5820-01-502-4042) (EIC: N/A) GRID REFERENCE SETS AB/GRC-229D (NSN 5895-01-502-4044) (EIC: N/A) PART OF ENHANCED POSITION LOCATION REPORT SYSTEM (THIS ITEM IS INCLUDED ON EM 0071)

A-4

GBS TM 11-5895-1612-12 OPERATOR`S AND UNIT MAINTENANCE MANUAL FOR TERMINAL, SATELLITE COMMUNICATION AN/TSC-154 (NSN 5895-01-435-0571) (EIC: GJH) (P/N G689400-1) (CAGEC: 49956) {TO 31R2-4-1649-1}, {TM 10432A-12/1} (THIS ITEM IS INCLUDED ON EM 0169) JNN TM 11-5805-861-13&P-1 OPERATOR, UNIT AND DIRECT SUPPORT MAINTENANCE MANUAL INCLUDING REPAIR PARTS AND SPECIAL TOOLS LIST FOR CENTRAL OFFICE, TELEPHONE AUTOMATIC AN/TTC-59(V)1 (NSN: 5805-01-525-4019); CENTRAL OFFICE TELEPHONE AUTOMATIC AN/TTC-59(V)2 (5805-01-529-9573); CENTRAL OFFICE, TELEPHONE AUTOMATIC AN/TTC-59(V)3 (5805-01-553-0920) (THIS ITEM IS INCLUDED ON EM 0059) TM 11-5805-861-13&P-2 OPERATOR, UNIT AND DIRECT SUPPORT MAINTENANCE MANUAL INCLUDING REPAIR PARTS AND SPECIAL TOOLS LIST FOR CENTRAL OFFICE, TELEPHONE AUTOMATIC AN/TTC-59(V)1 (NSN: 5805-01-525-4019) (EIC: N/A); CENTRAL OFFICE TELEPHONE AUTOMATIC AN/TTC-59(V)2 (5805-01-529-9573) (EIC: N/A); CENTRAL OFFICE, TELEPHONE AUTOMATIC AN/TTC-59(V)3 (5805-01-553-0920) (EIC: N/A)

NTDR TM 11-5820-1171-12&P OPERATOR`S AND UNIT MAINTENANCE INCLUDING REPAIR PARTS AND SPECIAL TOOLS LIST FOR RADIO SET AN/VRC-108 (NEAR TERM DIGITAL RADIO (NTDR)) (NSN 5820-01-519-2729) EIC:N/A (THIS ITEM IS INCLUDED ON EM 0079)

A-5

Power Unit TM 9-6115-661-13&P Operator, Unit, and Direct Support Maintenance Manual (Incl. RPSTL) for Power Unit, Diesel Engine Driven, 2 1/2 Ton Trailer Mounted, 15 kW, 400 HZ, PU-800; Power Unit, Diesel Engine Driven, 1 Ton Trailer Mounted, 15 kW, 50/60 Hz, PU-801; Power Unit, Diesel Engine Driven, 2 1/2 Ton Trailer Mounted, 15 kW, 50/60 Hz, PU-802; Power Plant, Diesel Engine Driven, 2 1/2 Ton Trailer Mounted, 15 kW, 400 Hz, AN/MJQ-39. TM 9-6115-662-13&P Operator, Unit, and Direct Support Maintenance Manual (Incl. RPSTL) for Power Unit, Diesel Engine Driven, 2 1/2 Ton Trailer Mounted, 30 kW, 50/60 Hz, PU-803; Power Unit, Diesel Engine Driven, 2 1/2 Ton Trailer Mounted, 30 kW, 400 Hz, PU-804; Power Plant, Diesel Engine Driven, 2 1/2 Ton Trailer Mounted, 30 kW, 50/60 Hz, AN/MJQ-40 TM 9-6115-663-13&P Operator, Unit, and Direct Support Maintenance Manual (Incl. RPSTL) for Power Unit, Diesel Engine Driven, 1/2 Ton 2 Trailer Mounted, 60 KW, 50/60 Hz, PU-805; Power Unit, Diesel Engine Driven, 2 1/2 Ton Trailer Mounted, 60 kW, 400 Hz, PU-806; Power Plant, Diesel Engine Driven, 2 1/2 Ton Trailer Mounted, 60 kW, 50/60 Hz, AN/MJQ-41 SICPS TM 11-7010-321-12&P (S-832/G SICPS RWS V-4) Operator’s and Unit Maintenance Manual (Incl. RPSTL) for Tactical Command Systems Used in S-832/G Rigid Wall Shelter (RWS) Standardized Integrated Command Post System (SICPS) SKL TM 11-7010-354-12&P Technical Manual Operator’s and Unit Maintenance Manual Including Repair Parts and Special Tools List For the Computer System, Digital AN/ PYQ-10 (C) (Simple Key Loader) (NSN 7010-01-517-3587) (EIC: N/A) SMART-T TM 11-5895-1612-12 Operator’s and Unit Maintenance Manual for Terminal, Satellite Communication AN/TSC-154 (NSN 5895-01-435-0571) (EIC GJH PN G689400- 6, -1, -5 CAGEC 49956

A-6

SWLAN TM 11-5820-1170-12&P Operator’s and Unit Maintenance Manual (Incl. RPSTL) for Radio Set AN/VRC-106(V)1(C) (NSN 5820-01-505-9931) Radio Set AN/VRC- 106(V)2(C) (NSN 5820-01-506-3226) (EIC N/A) TMSS-Medium & TMSS-Large TM 11-6115-742-13&P (TMSS-Medium) Operator and Field Maintenance Manual (Incl. RPSTL) for Power Plant, Utility PU-821/T (NSN 6115-01-547-6713) (EIC N/A) PU-822A/T (NSN 6115-01-547-6738) (EIC N/A) TM 11-6115-743-13&P (TMSS-Large) Operator and Field Maintenance Manual (Incl. RPSTL) for Power Plant, Utility PU-823/T (NSN 6115-01-547-8513) (EIC N/A) PU-824A/T (NSN 6115-01-547-8552) (EIC N/A) Websites WIN-T See the WIN-T AKO website for POC telephone numbers: https://www.us.army.mil/suite/page/296151 Incident Reporting Module (IRM) https://hd.kc.us.army.mil/arsys/shared/login.jsp?/arsys/home Log in using your AKO username and password Joint Automated Deep Operations Coordination System (JADOCS) https://www.iec.belvoir.army.mil/jadocs/index.htm Need special login, password, to access Battle Command Sustainment Support System (BCS3) https://vports.atsc.army.mil Property Book Unit Supply Enhanced (PBUSE) https://www.pmlis.lee.army.mil/tls/pbuse/pbuse.htm Medical Communications for Combat Casualty Care (MC4) https://207.87.24.38/jpta

A-7

Naval Air Systems Command Mobile Facility Program (MFP) http://www.mobile-facilities.com/ Transportation Information Systems (TIS) http://www.tis.army.mil/AALPS/ http://www.tis.army.mil/tc_aims2.html LOGSA https://www.logsa.army.mil/etms/online.cfm Program Manager Mobile Electric Power (PM-MEP) http://www.pm-mep.army.mil/logistics/pubs.htm Single Interface to the Field (SIF) https://sif.kc.army.mil/

Appendix B Acronyms

This page intentionally left blank.

B-1

Appendix B

Term Definition amp Amperes (Amps) AAMDC Army Air & Missile Defense Command AAR After Action Review ABCS Army Battle Command Systems ABCT Armored Brigade Combat Teams AC Active Components *ACC Army Service Component Command ACES Automated Communications Engineering Software ACP Access Control Point ACT-E Analysis Control Team-Enclave ADA Air Defense Artillery ADAM Air Defense Airspace Management ADP Army Doctrine Publication ADRP Army Doctrine Reference Publication ADSI Air Defense Systems Integrator AFATDS Advanced Field Artillery Tactical Data System AFI Air Force Instruction AFSB Army Field Support Brigade AKMS Army Key Management System AKO Army Knowledge Online ALO Air Liaison Officer AMDWS Air and Missile Defense Workstation AMPS Aviation Mission Planning System AO Area of Operations AOR Area of Responsibility APU Auxiliary Power Unit AR Army Regulation ARDP Army Requirements Development Plan ARFOR Army Forces ARFORGEN Army Forces Generation ART Army Tactical Task ASAS All Source Analysis System

B-2

Term Definition ASAS-IFS All Source Analysis System - Intelligence Fusion System ASAS-L All Source Analysis System – Light ASCC Army Service Component Command ATQH At the Quick Halt BCCS Battlefield Command Common Services BCS3 Battle Command Sustainment And Support System BCT Brigade Combat Team BDE Brigade BFA Battlefield Functional Area BFSB Battlefield Surveillance Brigade BFT Blue Force Tracking BIT Built-In-Test BLST Brigade Logistic Support Team BN Battalion BNOSC Brigade Network Operations and Security Center bps Bits Per Second BSB Brigade Support Battalion BSTB Brigade Special Troops Battalion BUB Battle Update Briefing C2 Command and Control C2R Command and Control Registry

C4ISR Command, Control Communications, Computers, Intelligence, Surveillance, and Reconnaissance

C4Ops Command, Control, Communications, and Computer Operation

CAISI Combat Service Support Automated Information Systems Interface

CAU Crew Access Unit CASS Close Air Support System CAT 5 Category 5 CCIR Commander's Critical Information Requirements CCS Command Center System CDD Complete Discharge Device CDR Commander CECOM Communication Electronics Command CF Central Facility

B-3

Term Definition CFSB C4ISR Field Support Branch CG Commanding General CGS Common Ground Station (being replaced with TGS)

CHARCS CI/HUMINT Automated Reporting and Collection System, Counterintelligence Human Intelligence Automated Reporting and Collection System

CHATS Counterintelligence Human Intelligence Automated Tools Set CHOPS Chief of Operations CIC Combat Information Center CIDNE Combined Information Data Network Exchange CIM Computer Interface Module CIO Chief Information Officer CM Configuration Management CNR Combat Net Radios CO Company COC Combat Operations Center COE Contemporary Operating Environment COMEX Communication Exercise COMSEC Communications Security COP Common Operational Picture COS Chief of Staff COTS Commercial Off-the-Shelf CP Command Post CPCS Command Post Communication Systems CPOF Command Post of the Future CPP Command Post Platform CPS Central Power Solution CPT Captain CPX Command Post Exercise CS Combat Service CSM Command Sergeant Major CSS Combat Service Support CTC Combat Training Center CTSF Central Technical Support Facility DCGS-A Distributive Common Ground System-Army DDS Data Dissemination Service

B-4

Term Definition DIGEX Digital Exercise DIV Division DMG Digital Master Gunner DMS Defense Message System DMS-A Defense Messaging System – Army DNOSC Division NetOps and Security Center DoD Department of Defense DPEM Detailed Planning and Engineering Module DSE Digital Systems Engineer DSN Defense Switched Network DTAC Division Tactical Command Post DTSS Digital Topographic Support System DTSS-L Digital Topographic Support System-Light EAC Echelon Above Corps EAD Echelon Above Division ECB Echelons Corps and Below ECU Environmental Control Unit ELO Enabling Learning Objective eMCSU enhanced Micro Central Switching Unit EMSO Electromagnetic Spectrum Operations EMT Effects Management Tool EPLRS Enhanced Position Location Reporting System ESB Expeditionary Signal Battalion ESD Electro Static Discharge EVC Extended Voice Communication FAAD Forward Area Air Defense FBCB2 Force XXI Battle Command-Brigade & Below FM Field Manual FRAGO Fragmentary Order FSCM Fire Support Coordination Measures FSE Fire Support Element FSE Field Support / System Engineer FSR Field Service Representative FTX Field Training Exercise GBS Global Broadcast Service

B-5

Term Definition GCSS-A Global Command and Control System – Army GenSet Generator Set GFCI Ground Fault Circuit Interrupter GIG Global Information Grid GPS Global Positioning System GVW Gross Vehicle Weight GW Gateway HAZMAT Hazardous Materials HBCT Heavy Brigade Combat Teams HF High Frequency HHC Headquarters & Headquarters Company HMMWV High-Mobility Multipurpose Wheeled Vehicle HQDA Headquarters, Department of the Army IA Information Assurance IAVA Information Assurance & Vulnerability Alert IBCT Infantry Brigade Combat Team IC Information Collection IDM Information Dissemination Management IDM/CS Information Dissemination Management/Combat Service IED Improvised Explosive Device IFS Intelligence Fusion System IMETS Integrated Meteorological System INFOSYS Information System IP Internet Protocol IRM Incident Reporting Module ISS Information System Security IAVA Information Assurance Vulnerability Alerts

JADOCS Joint Automated Deep Operations Coordination System

JCR Joint Capabilities Release JKMS Joint Key Management System JNN Joint Network Node JP Joint Publication JTF Joint Task Force JTF JCCC Joint Task Force Joint Communication Control Center KM Knowledge Management

B-6

Term Definition LAN Local Area Network LAR Logistics Assistance Representative LCMS Local COMSEC Management Software LDIF Lightweight Data Integration Format LMTV Light Medium Tactical Vehicle LNO Liaison Office LOGSA Logistics Support Activity LOS Line of Sight LSD Large Screen Display LTV Light Tactical Vehicle LWN Land War Net MC Mission Command MC4 Medical Communications for Combat Casualty Care MCOO Modified Combined Obstacle Overlay MCSI Mission Command System Integration MCTP Mission Command Training Program MDMP Military Decision-Making Process MEP Mobile Electric Power

METT-TC Mission, Enemy, Terrain and Weather, Troops, Time Available, and Civil Considerations

MFP Mobile Facility Program (NAVY)

MIDS Multi-function Information Distribution System MIL-STD Military Standard MOS Military Occupational Specialty MRE Mission Readiness Exercise (FTX) MRX Mission Rehearsal Exercise (CPX) MSR Main Supply Route MTOE Modified Table of Organization and Equipment MTS Movement Tracking System NCO Non-Commissioned Officer NET New Equipment Training NetOps Network Operations NIPR Non-Secure Internet Protocol Router NMIB New Material Information Briefing NOSC NetOps and Security Center

B-7

Term Definition NRTS Near Real Time Server NSC Network Signal Company Commander NTDR Near-Term Digital Radio OPFOR Opposing Force OPORD Operation Order OTC Operational Transit Case PASS Publish and Subscribe Service PBUSE Property Book Unit Supply Enhanced PCMCIA Personal Computer Memory Card International Association PDISE Power Distribution Illumination System Electrical PdM Product Manager PDU Power Distribution Unit P&E LAR Power & Environmental Logistics Assistance Representative PE Practical Exercise

PEO-C3T Program Executive Office - Command, Control and Communications Tactical

PEO-IEW&S Program Executive Office - Intelligence, Electronic Warfare and Sensors

PEP Power Entry Panel PIR Priority Intelligence Requirement PM Program Manager PM-MEP Program Manager - Mobile Electric Power PMCS Preventive Maintenance Checks and Services POL Petroleum Oil and Lubricants POR Program of Record PP Power Plant PPE Personal Protective Equipment QH Quick Halt RBECS Revised Battlefield Electronic CEOI System RCERT Regional Computer Emergency Response Team RDG Random Data Generator RI Relevant Information ROE Rules of Engagement RP&O Regional Plans and Operation (C4ISR) RPSTL Repair Parts and Special Tools List RSO&I Reception, Staging, Onward Movement, & Integration

B-8

Term Definition RTO Radio Telephone Operator RWS Rigid Wall Shelter SA Situational Awareness SATCOM Satellite Communications SBCT Stryker Brigade Combat Team SEP Signal Entry Panel SICPS Standardized Integrated Command Post System SIF Single Interface to the Field SIGACTS Significant Activities SINCGARS Single Channel Ground and Airborne Radio System SIPR Secure Internet Protocol Routing SKL Simple Key Loader SMART-T Secure Mobile Anti-Jam Reliable Tactical-Terminal SMC Server Management Console SME Subject Matter Expert SOC Support Operations Center SOI Signal Operating Instructions SOP Standing Operating Procedure SoS System of Systems STT Satellite Transportable Terminal SU Situational Understanding SWLAN Secure Wireless Local Area Network SWGS Surface Wire Grounding System TAA Tactical Assembly Area TAADS Training Aids, Devices, Simulators, Simulations TAC Theater Aviation Command TAC CP Tactical Command Post TACSOP Tactical Standing Operating Procedures TACSAT Tactical Satellite TAIS Tactical Airspace Integration Systems TB Technical Bulletin TB MED Technical Bulletin (Medical) TBP To Be Published TC Training Circular TCM-MC TRADOC Capabilities Manager-Mission Command

B-9

Term Definition

TC-AIMS II Transportation Coordinators - Automated Information for Movements System II

TGS Tactical Ground Station THN Tactical Hub Node TI Tactical Internet TIS Transportation Information System TIG Tactical Information Grid TIGR Tactical Ground Reporting System TIP Tent Interface Panels TLO Terminal Learning Objective TM Technical Manual TMC Tactical Mission Command TMC-GW Tactical Mission Command-Gateway TMC-WS Tactical Mission Command-Work Station TMC-SMC Tactical Mission Command-Server Management Console TMSS Trailer-Mounted Support System TOC Tactical Operations Center TOCNET Tactical Operations Center Inter Communications System TQG Tactical Quiet Generator TRO Training Readiness Oversight TSC Theater Sustainment Command TTSB Theater Tactical Signal Brigade TSSB Theater Strategic Signal Brigade TSO Technical Support Order TTP Tactics, Techniques, and Procedures UPS Uninterruptible Power Supply URN Unit Reference Number USF Unit Set Fielding UV Ultraviolet VAC Volts Alternating Current VBIED Vehicle Born Improvised Explosive Device VHF Very High Frequency VMF Variable Message Format VoIP Voice over Internet Protocol VSAT Very Small Aperture Terminals

B-10

Term Definition WAN Wide Area Network WFF Warfighting Function WMD Weapons of Mass Destruction WIN-T Warfighter Information Network –Tactical XML Extensible Markup Language XO Executive Officer

Appendix C

Composite Equipment Listing Dimensions and Weights

This page intentionally left blank.

C-1

Appendix C: Composite Equipment List: Dimensions and Weights

List is also available at https://www.us.army.mil/suite/page/547567

Item Model Width Depth Height Weight (lb)

Volume (ft)

Furniture & Misc Items Fire ext short 7 16.5 14.5 1.47

Fire ext tall 6 3 26.5 15 1.73

Chairs 18.25 3 39 10.5 1.24

Bench 72 12 3 18.5 1.50

Table 24" 72 24 3 27.5 3.00

Table 30" 72 30 3 39.5 3.75

Power strip w/ 10' cord 12 2 1.75 3 0.03

Trash can 21 25 26.5 4 21.24

Velcro 5/8" x 600' 407622 JPM55A 14 5 0.00

Velcro hook 65 3/4" blk 25 yd RL 90916 14 1.5 0.5 0.53

Velcro loop 300 blk 25 yd RL 90917 14 1.5 0.5 0.53

Easels w/ paper 26 5 38 10 2.86

Wire protector for floor (small) 37 5.5 1 2.5 0.12

Wire protector for floor (large) 36 11 1.5 9 0.34

Water cooler 13 12.25 37 3.41

Water bottle 10.5 16 3.21

Weapons rack Coffee pot 10 16.25 2.5 2.95

Duffle bag/Hazardous spill bag 25 14 10 11 2.03

Tent signs 36 0.25 24 1 0.13

Modular flooring transports on separate pallet

Bike track flooring Log tent entrance 43 49 2 24 2.44

Bike track flooring Log tent entrance 25 49 2 12 1.42

C-2

Item Model Width Depth Height Weight (lb)

Volume (ft)

Bike track base Log tent entrance 43 49 2 24 2.44

Bike track flooring cable run cover

Current Ops 6 21 1.25 1 0.09

Bike track flooring base with cable tray

Current Ops 43 49 2 32 2.44

Systems Hardware Dell laptop M90 15.5 11 1.5 8.5 0.15

Dell M90 power brick 7 3 2.5 2 0.03

Desktop CAU 8 10 11.5 11.5 0.53

CAU headphones 7 8 4.5 2 0.15

Cisco IP phone 7940 11.5 4 9 3 0.24

Dell laptop w/ pwr brick 6300 15.5 11.5 1.5 10 0.15

Panasonic CF 29 12 11 2.5 8 0.19

Panasonic laptop w/pwr brick & mouse CF51 12.75 11 2 7.5 0.16

Dell Latitude 410 13.75 11.5 2.25 9.5 0.21

Dell Latitude 610 12.5 10.25 1.5 7 0.11

Dell Latitude 810 14 10 2 7 0.16

Air Fortress CAISI client module AF 1100 15 7 3.5 8 0.21

IBM ThinkPad 12.25 13 2.5 7.5 0.23

Lexmark PBUSE printer E342N 16 14 10.25 23.5 1.33

Rugged laptop DPEM 14 12 3 0.29

AN/TYQ 108 case 17.5 12.25 6 11 0.74

HP Laser Jet 1320 w/ trans case 18.25 18.25 16 49 3.08

AN/TYQ 107 case 19.25 15.25 7.5 12.5 1.27

Caise Bridge 14.25 8.5 7.25 14.5 0.51

Panasonic w/ pwr brick & mouse CF18 11 9 1.75 6.5 0.10

Panasonic w/ power brick CF73 11.75 11 1.25 6.5 0.09

CPOF monitor only 16.25 5.5 14.75 12 0.76

CPOF triple head video splitter 4 4 0.05 1 0.00

CPOF Dell M90 15.5 11 1.5 10.5 0.15

CPOF headset 7 9 4 2.5 0.15

GD Solaris CPU box AFATDS 14 14 5 15.5 0.57

GD Solaris pwr brick AFATDS 10 4 3 2 0.07

C-3

Item Model Width Depth Height Weight (lb)

Volume (ft)

GD printer AFATDS 17.25 16.5 15.5 52 2.55

Printer in trans case AFATDS MIL AC/DC adapter AFATDS Ge Tac laptop ACES 13.75 11.5 2.25 9.5 0.21

Dell keyboard LCMS 18 7 2 1.5 0.15

Dell monitor LCMS 6 15 16.5 10 0.86

Dell processor LCMS 8 19.5 17.5 29.5 1.58

AB swx box LCMS 6 4.75 2.25 2 0.04

Dell optical drive LCMS 4.5 6.25 1.25 1.5 0.02

Dell printer LCMS 15.75 14.5 9.75 22.5 1.29

SMART-T LCMS 14.5 APC Smart UPS LCMS 5.5 14 6.5 28.5 0.29

TV Sat interface 19 9.5 3 7 0.31

TV Sat laptop Gateway 13.25 11 1.5 9 0.13

CGS-WS CGS 27 34 17 11.5 9.03

Dell printer 1710 laser jet 15.75 14.5 9.25 24 1.22

Belden RG 59 coax 500 ' 14 11 13.5 1.2

Network 6 pair cable box 15 15 7.5 15 0.98

CD-ROM in cardboard box BCS 9.25 12.25 4.75 2.5 0.31

Large printer Stored in cardboard box

25 31.5 27 92 12.3

Crystal View KVM ext. 9 3.5 2 2.5 0.04

UPS box DTSS 24 24 36 100 12.00

36" scanner DTSS 60 18 18 125 11.25

TAC Laptop MilTope 12.5 11.5 4 15 0.33

Miltope power brick 11 5 3 3.5 0.10

Fax 19.25 25 17 22 4.73

Sun 600 SXR 27 24.5 10 44 3.83

Audio/Video Pelican Case 1660 Audio case 32 23.5 18.5 109.5 8.05

Audio speaker w/o cable 9.25 14.25 7 10.5 0.53

Audio speaker w/ cable 9.25 14.25 7 11.5 0.53

CCS projector system CCS 23 20 15 38.5 3.99

Large screen display LSD 63 84 41 125.56

C-4

Item Model Width Depth Height Weight (lb)

Volume (ft)

Large screen display w/ projector mounted LSD 63 84 82 251.13

CCS video switcher trans case CCS 34.5 22.5 21 141 9.43

Power Equipment 25' cord 16 ga. 12 5 2 0.75 0.07

PM MEP AC breakout box w/ pigtail

6150-01- 25109125 5.75 6 3 0.75 0.06

PMMEP 120-V power distribution cable, Triple head

97403- 13226- E737

15 4 1.5 1.64

Surge protector 13 3.25 3.25 1.5 0.08

PM MEP power dist. box M40 21.5 19 17 75 4.02

PM MEP power dist. box M100 24 21.5 20.5 75 6.12

PM MEP input power dist. trans case 1 33 21 14.5 66 5.82

PM MEP input power dist.trans case 2 33 21 14.5 54.5 5.82

PM MEP power cable 51' long

From Gen. to Mxx 34 6 66.5 12.6

PM MEP power cable 53' long

From Gen. to Mxx 38 6 114.5 15.74

PM MEP converter box trans 33 20.5 14.5 24.5 5.68

1200 V3 electric feeder 0011689- 001 23.25 20.75 26.75 128 7.47

Transit Cases JNN transit case empty 23.25 35 13.5 77 6.36

JNN transit case 1 23.25 35 11.5 115 5.42

JNN transit case 2 23.25 35 11.5 140 5.42

GBS stack case 1 Skystream 34 23.5 17 7.86

GBS stack case 2 Skystream 22.5 30 13 5.08

BCCS transit case1 23.5 35 9.5 128 4.52

BCCS transit case2 23.5 35 11.5 166 5.47

BCCS transit case 3 23.5 35 11.5 169 5.47

HP Laser Jet 4600 w/ trans case 31.5 26 28 97 13.27

ALH 102 862-001 TOCNET OTC 40.25 23 9.75 83 5.22

CPS Ruggedbox 12.25 8.25 4 0.23

C-5

Item Model Width Depth Height Weight (lb)

Volume (ft)

CPCS CAUs case TFOCA cables 25.25 25 17 72 6.21

CAISI bridge trans case 24 20 14.5 57 4.03

JADOC trans case loaded 28 34 15.25 98 8.40

IFS trans case1 ASAS 26.5 28.25 24.5 100 10.61

IFS trans case2 ASAS 28.75 28.25 15.75 129 7.40

IFS trans case 3 ASAS 22.5 30.5 11.5 129 4.57

PBUSE printer trans case 25 19 16.5 47.5 4.54

CAISI bridge trans case empty 24.5 19.75 14.25 37.5 3.99

CAISI client trans case 13.5 27.5 11 17.5 2.36

CAISI client Mod trans case 32.75 21 21.5 42 8.56

Computer soft case Soft bags 15 13 6 8 0.68

CPOF trans case w/ hdset, mon, keyboard, cpu, pwr strip

33 21 21.5 94.5 8.62

Client workstation assy trans case 32.5 20.5 20.75 100 8.00

Indoors equipment 453-1 33 22 12 82.5 5.04

RF equipment 453-3 29 27 20 121 9.06

GCS 453 22 15 90 20.5 17.19

Reflective screen case 453-4 56 35 15 143.5 17.01

Antennae pedestal case 453-2 42 27 20 151.5 13.13

TV sat trans case 61.5 23 18 44 14.73

Pelican 1490 m trans case 19 14 5 8 0.77

Pelican 1490 m trans case

TC AIMS Client/ server

19 14 5 16 0.77

Pelican 1600 trans case 24 21 8 37.5 2.33

Pelican trans case 20 15.5 8 20 1.44

Pelican trans case 16 14 6 16 0.78

Pelican case laptop softbags 32 20.5 23 5.5 8.73

Trans case empty AFATDS 18.75 18 9 13 1.76

Trans case empty AFATDS 18.75 18 9 30.5 1.76

Trans case empty AFATDS 34 27 22 105 11.69

C-6

Item Model Width Depth Height Weight (lb)

Volume (ft)

CF 29 trans case ISYSCON 20 16 7 19.5 1.30

Trans case MDL 24 20 9.5 28 2.64

IP phone trans case 25.5 24.5 17.5 42 6.33

TC-AIMS server case 14 19.5 4.5 8 0.71

Pelican case for misc Fiber repair kit 24 22 10 13 3.06

Storm 2400 case PBUSE 19.25 15 7.5 16 1.25

Storm 2750 case Projector 24 28 14 38.5 5.44

Calzone projector case . 23 16 12 16 2.56

CCS screen case CCS 17.75 50 13 37 6.68

Screen commanders CCS display loaded CCS 17.75 50 13 75.5 6.68

Trans case EMT 18.5 17 6 13 13.00

Gray metal box 31 17 12.5 46 38.1

Green metal case 21.5 20.5 10.75 2.74

Metal cable spools 16.5 8 14 3.96

Stanley tough box w/ wheels 36 23 24 91.5 11.5

Gray tote tub 25.5 18 16 10 4.25

FSR toolbox 18.5 16 9.5 29.5 1.63

MilToe trans case 22.5 21.5 7 18 1.96

Transit case w/ plotter 74 24 29 295 29.81

CPU cardboard box 36 36 24 75 18.00

Storage case 34 59 5 36 5.80

SKB trans case Router & hub 17 12 6.25 11 0.74

SKB trans case 21.5 18 11 39 2.46

Footlocker 42 18 18 50 7.88

Wood case 31.5 17 15.5 77 4.80

Wood pallet 34 59 5 36 5.80

Green trans case 27.5 13 11 2.28

Green trans case Printer 18 18 17 47.5 3.19

Green trans case ANTYQ107 19.25 15 7.5 20.5 1.25

Green trans case 34 22 11 4.76

BikeTrack™ pallet 48.25 42 6 60 CGS RWS trans case 1 CGS 33.75 27 17 134 8.96

CGS RWS trans case 2 CGS 33.75 27 24 151 12.66

CGS RWS trans case 3 CGS 33.75 23 24 102.5 10.78

C-7

Item Model Width Depth Height Weight (lb)

Volume (ft)

NETOPS - IDEF 22 35 14 6.24

NETOPS - IDEF 22 35 11 4.90

NETOPS - Firewall MGR 22 35 14 6.24

NETOPS - Firewall MGR 22 35 11 4.90

WIN-T 3 mths spares Trans case 24 19 13.5 55 3.56

Box of 50 caribeaners 16 4 5 2.5 0.19

CCS accessory kit 21 20 18 93.5 4.38

2011 antenna 38.5 12.5 16.5 46.5 4.60

2040 antenna 18.5 5 5 3.11

TS CF750 laptop 21.5 22.25 7 36.5 1.94

Antenna mast 5 55 7.5 2.5

4 WS trans case 29 25 17 77.5 7.13 Total Wt 6881.5

Item Model Width Depth Height Weight (lb)

Volume (ft)

Pallet of 30" tables* 12 tables on pallet 72 48 43 510 86.00

Pallet of 24" tables* 16 tables on pallet 72 48 29.5 476 59.00

Pallet of chairs* 36 tables on pallet 55.5 41 27 414 35.55

Pallet of chairs* 22 chairs on pallet 43.5 48 29 267 35.04

Pallet of wire protectors* 50 per pallet (approx)

45 48 20 250 25.00

Total wt 1917 * Includes pallet weight of 36 lbs

1