Building Enterprise Network COP based on industry Standards and Protocols
LAN
BATTLE
INFORMATION ASSURANCE
WAN Manager x 2 Planner
Solar Winds
Scrutinizer Solar Winds TACLANE (netflow SNMPc Manager
Figure 3-88 Current NetOps Capability 3.6.9 Battle Rhythm
3.6.9.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 G6 and S6 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.6.10 Establishing the CP
3.6.10.1 The setup and teardown of the CP is the most critical time 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 (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.6.11 Reporting
3.6.11.1 As mentioned previously, the G6 does not control or own the signal assets or personnel in the BCT. However, when the BCT is connected to the Division network, then the Division G6, 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 Annex H to the division 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 the G6 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.6.12 Commander Network Roles
3.6.12.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 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 S6 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 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 S6 and Bde/Division Spectrum Manager are critical to the development of the spectrum utilization plan in support of operations and commanders intent.
CP Operations - Commanders must integrate the increased personnel and systems, including increases in Battle
Command Systems (BCSs) and applications, to enable effective C2. Each staff section residing in the TOC has extensive data requirements to develop products 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 TOC 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 S2 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 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-109