4-92. Combatant commanders often require their supporting theater signal forces to define and maintain packages of equipment and personnel to support rapid insertion of forces into a theater. For the purpose of this manual, these are referred to as contingency communications packages. The content of deployed contingency packages will be determined on a case-by-case basis by METT-TC. The communications packages discussed below provide a standardized starting point for planners who are tasked with providing such packages. A key feature of this predefined baseline is that it relates services and number of supported subscribers to required airlift.
4-93. The communications packages illustrated for ITSB will be equipped with Army standard equipment fully supported by standard Army logistics practices. The communications packages illustrated for non-ITSB organizations are notional starting points for planning. Historically, non-ITSB organizations have developed the data package portions of their contingency communications packages locally, outside formal Army systems acquisition channels. Such packages are not standardized from organization to organization. When tasking non-ITSB organizations to provide contingency communications packages, planners should contact the providing organizations to learn the actual equipment configurations available.
4-94. Organizations needing to create or upgrade data packages prior to the fielding of Army type classified standard solutions should contact NETCOM/9th ASC G3. NETCOM/9th ASC G3 will provide assistance in equipment selection to obtain the maximum degree of standardization and interoperability among units and theaters that can be achieved under the circumstances.
4-95. The technical capabilities provided by communications packages from
organizations. The main operational difference is that communications packages provided by ITSBs typically come from a single platoon, or at worst, a single company. These individuals have lived together, trained together, worked together, and fought together under the same leadership. Such teams have greater cohesiveness than ad-hoc teams. Parent unit support to the deployed team has the advantage of coming from a single parent unit. In contrast, contingency packages assembled from non-ITSB organizations are likely to have elements from several different companies, battalions, and/or commands. Unit cohesiveness may not be as great. Parent unit support is less efficient when it comes from multiple parent units.
ITSB SMALL CONTINGENCY COMMUNICATIONS PACKAGE
4-96. The mission of the ITSB small contingency communications package is to provide an initial entry theater-strategic link in support of forward deployed contingency headquarters (for example, JTF or ARFOR) with follow-on support of forward tactical headquarters (for example, divisifollow-on rear and division tactical command). Figure 4-22 provides an example of a small contingency communications package. Table 4-1 identifies the services, capabilities, and transportability requirements of a small contingency communications package.
DSVT
STU III
DNVT
Multiband TACSAT C & W Team
FEC Loop Power Nest (rear) KVM Call Manager
VG248 VG248 Laptop
3640 Router 3550 Ethernet Switch
3640 Router
PU-798
________________________________________________________________________________FM 6-02.45
Table 4-1. ITSB Small Contingency Communications Package Example
Service Qty/Criterion Major
Element/Component
Equipment Crew
Voice (256 KB) OIC OR NCOIC N/A 1
DSN 96 subscribers
plus 8 long locals
Multiband TACSAT (for example, Phoenix)
1xECV w/system 1xECV w/generator
4
DRSN Available BBN-early entry pkg Data pkg in four transit cases: 3
VTC (256 KB) 1 Suite 1xHMMWV – cargo
SIPRNET 50 subscribers 1xPU-798 (10kw) trailer
NIPRNET 50 subscribers Cable and Wire Team 1xHMMWV – cargo (wire and phones)
3
JWICS 0 subscribers 1xHMT cargo trailer
(cable and wire)
C-LAN/C-WAN No Maintenance Team N/A 1
Trailers (cargo and generator)
Qty:
Up to three small contingency packages can be task organized within each ITSB.
When it is critical to minimize air transport requirements, the base band node (BBN) – early entry data package components can be shipped on a pallet, and one HMMWV and one generator can be transported later. In this configuration, the team is only 75 percent self-sufficient for ground transport and will be reliant on the supported unit for data package power.
Aircraft numbers required are estimates and include pallets for two personal bags per soldier. Food is not included.
Deployment times as required by supported combatant commander. Level of alert/standby to support times shorter than N+72 hours severely impacts training.
Bandwidths allocated to various services are for illustration only. Allocation in the field will be by METT-TC.
Total bandwidth available depends on the combination of ancillary equipment installed in the SATCOM terminal and on availability of bandwidth from the space segment (the bird); up to 8 Mbps can be achieved.
Switch capacity is listed; unit usually deploys with only a fraction of that number of phones.
ITSB MEDIUM CONTINGENCY COMMUNICATIONS PACKAGE
4-97. The mission of the ITSB medium contingency communications package is to provide an initial entry theater-strategic link in support of forward deployed contingency headquarters (for example, JTF or ARFOR) with follow-on support of forward tactical headquarters (for example, divisifollow-on rear and division tactical command). Figure 4-23 provides an example of a medium contingency communications package. Table 4-2 identifies the services, capabilities, and transportability requirements of a medium contingency communications package.
PU-798
HF Radio
Single Channel TACSAT C2 Radio Services
DSVT
STU III
DNVT
Coalition LAN
SIPRNET Multiband
TACSAT
NIPRNET
Figure 4-23. ITSB Medium Contingency Communications Package
________________________________________________________________________________FM 6-02.45
Table 4-2. ITSB Medium Contingency Communications Package
Service Qty/Criterion Major
Element/Component
Equipment Crew
Voice OIC or NCOIC N/A 1
DSN 96 analog subscribers 60 tactical subscribers
Multiband TACSAT (for example, Phoenix)
1xECV w/system 1xECV w/generator
4
DRSN Dedicated interface BBN-Shelterized 1xECV w/system 1xECV w/TSM-210
5
VOIP Up to 1000 subscribers 1xHMMWV – cargo
VTC (384 K) 1 Suite 1xPU-798 (10kw) trailer
SIPRNET (512K) 250 subscribers 1xHMT cargo trailer NIPRNET (512K) 250 subscribers Cable and Wire Team 1xHMMWV – cargo (wire and phones)
5
JWICS (128K) 1 subscriber 1xHMT cargo trailer
(cable and wire)
C-LAN/C-WAN Yes – 50 Maintenance Team N/A 1
IA/Network Management
Yes Total Personnel 16
Bandwidth Up to 8 Mbps Total Equipment:
HMMWV
Trailers (cargo and generator) Qty:
6 4
Deploys N+18 hrs Transportation:
C130
Typically one extension node from the ITSB extension node platoon without LOS; augmented with wire and cable team and maintenance.
Initial communications for highest priority users arrival+24 hours.
Deployment times as required by supported combatant commander. Level of alert/standby to support times shorter than N+72 hours severely impacts training.
Bandwidths allocated to various services are for illustration only. Allocation in the field will be by METT-TC.
Total bandwidth available depends on the combination of ancillary equipment installed in the SATCOM terminal and on availability of bandwidth from the space segment (the bird); up to 8 Mbps can be achieved.
Aircraft numbers required are estimates and include pallets for two personal bags per soldier. Food is not included.
ITSB LARGE CONTINGENCY COMMUNICATIONS PACKAGE
4-98. The mission of the ITSB large contingency communications package is to provide an initial entry theater-strategic link in support of forward deployed contingency headquarters (for example, JTF or ARFOR) with follow-on support of forward tactical headquarters (for example, divisifollow-on rear and division tactical command). Figure 4-24 provides an example of a large contingency communications package. Table 4-3 identifies the services, capabilities, and transportability requirements of a large contingency communications package.
HF Radio
Single Channel TACSAT C2 Radio Services
Can run phones from SSS and BBN
C & W Team
Coalition LAN NIPRNET SIPRNET Multiband
TACSAT
SSS DSVT
DNVT STU/STE PU-798
BBN Spt Vehicle
SSG Spt Vehicle PU-798
Figure 4-24. ITSB Large Contingency Communications Package
________________________________________________________________________________FM 6-02.45
Table 4-3. ITSB Large Contingency Communications Package
Service Qty/Criterion Major
Element/Component (for example, Phoenix)
1xECV w/system 1xECV w/generator
4
VOIP Up to 1000 subscribers
TTC-56 SSS 1xECV w/system 1xECV w/TSM-210
5
VTC (384 K) 1 Suite 1xHMMWV - cargo
SIPRNET (512K) 500 subscribers 1xPU-798 (10kw) trailer NIPRNET (512K) 500 subscribers 1xHMT cargo trailer JWICS (128K) 1 subscriber
C-LAN/C-WAN Yes - 50 BBN - transit case Data pkg in 10-14 transit cases:
1xHMMWV - cargo
3
IA/Network Management
Yes 1xPU-798 (10kw) trailer
Bandwidth Up to 8 Mbps Cable and Wire Team 2xHMMWV – cargo (wire and phones)
7
Deploys N+24 hrs 2xhigh mobility cargo trailer
(cable and wire) IOM (99% of
subscribers connected)
Arrival + 72 hrs
Maintenance Team 1xHMMWV – cargo 2
Total Personnel 23
Total Equipment:
HMMWV
Trailers (cargo and generator)
Qty:
Typically formed with elements of area node platoon augmented with cable and wire team and maintenance.
Bandwidths allocated to various services are for illustration only. Allocation in the field will be by METT-TC.
Total bandwidth available depends on the combination of ancillary equipment installed in the SATCOM terminal and on availability of bandwidth from the space segment (the bird); up to 8 Mbps can be achieved.
Aircraft numbers required are estimates and include pallets for two personal bags per soldier. Food is not included.