About
Community
Bad Ideas
Guns & Weapons
Irresponsible Activities
KA-FUCKING-BOOM!
Locks and Security
Scams and Rip-offs
Drugs
Ego
Erotica
Fringe
Society
Technology
register | bbs | search | rss | faq | about
meet up | add to del.icio.us | digg it

Battlefield Information Transmission System: Far T


NOTICE: TO ALL CONCERNED Certain text files and messages contained on this site deal with activities and devices which would be in violation of various Federal, State, and local laws if actually carried out or constructed. The webmasters of this site do not advocate the breaking of any law. Our text files and message bases are for informational purposes only. We recommend that you contact your local law enforcement officials before undertaking any project based upon any information obtained from this or any other web site. We do not guarantee that any of the information contained on this system is correct, workable, or factual. We are not responsible for, nor do we assume any liability for, damages resulting from the use of any information on this site.


BATTLEFIELD INFORMATION TRANSMISSION SYSTEM

FAR-TERM STRATEGY

(version 1.0)

COLONEL K. THOMAS, ACTING DIRECTOR
SPACE & TERRESTRIAL COMMUNICATIONS
DIRECTORATE
(908) 427-4449/DSN 987-4449

PAUL SASS
ACTING CHIEF, SPECIAL PROJECTS OFFICE
SPACE & TERRESTRIAL COMMUNICATIONS
DIRECTORATE
(908) 427-2306/DSN 987-2306


U.S. ARMY COMMUNICATIONS-ELECTRONICS
COMMAND
RESEARCH, DEVELOPMENT AND ENGINEERING CENTER
FORT MONMOUTH, NEW JERSEY

1 OCTOBER 1995

DISTRIBUTION UNLIMITED



------------------------------------------------------------------------
TABLE OF CONTENTS
------------------------------------------------------------------------

1 INTRODUCTION


1.1 BATTLEFIELD INFORMATION TRANSMISSION SYSTEM

1.2 BACKGROUND

1.3 PURPOSE

1.4 ORGANIZATION



2 BATTLEFIELD INFORMATION TRANSMISSION SYSTEM OVERVIEW

2.1 BATTLEFIELD INFORMATION TRANSMISSION SYSTEM EVOLUTION

2.2 SUPPORTING PROGRAMS

2.2.1 Digital Battlefield Communications Advanced Technology
Demonstration

2.2.2 Future Digital Radio

2.2.3 Commercial Communications Technology Test
Bed/Commercial Communications Technology Laboratory

2.2.4 Advanced Concepts and Technology Program

2.2.5 Project Manager System Improvement Programs





3 FAR-TERM STRATEGY

3.1 INTRODUCTION


3.2 APPROACH


3.2.1 Research and Development Phase

3.2.2 Leave-Behind Phase

3.2.3 Acquisition Phase


3.3 REQUIREMENTS GENERATION

3.4 USER INVOLVEMENT


3.4.1 Battle Lab Warfighting Experiments

3.4.2 Advanced Warfighting Experiments

3.4.3 Joint Warfighting Interoperability Demonstrations


3.5 MANAGEMENT





4 EXECUTION


4.1 INTRODUCTION


4.2 BATTLEFIELD INFORMATION TRANSMISSION SYSTEM ELEMENTS


4.2.1 Tactical End-to-End Encryption Device

4.2.2 SPEAKEASY/Future Digital Radio (Broad Agency
Announcement)/Near-Term Digital Radio

4.2.3 Wideband HF

4.2.4 Asynchronous Transfer Mode Technology Integration

4.2.5 High-Capacity Trunk Radio

4.2.6 Terrestrial Personal Communications Systems

4.2.7 Army Direct Broadcast Satellite

4.2.8 Radio Access Point

4.2.9 Phased-Array Communications Antenna

4.2.10 Satellite Personal Communications Systems

4.2.11 Airborne Relay


APPENDIX TITLE PAGE

ACRONYMS AND ABBREVIATIONS

FIGURE TITLE PAGE

1-1 BITS Concept

2-1 BITS Evolution

2-2 Tactical Internet

2-3 Objective BITS Architecture

2-4 Supporting Programs

2-5 Digital Battlefield Communications Architectural Elements

2-6 DBC ATD Addresses Stated Army C41 Deficiencies

2-7 FDR Evolution

3-1 BITS Strategic Framework

3-2 Joint Advanced Development Environment

3-3 BITS Development Strategy

3-4 BITS Management Structure

4-1 Tactical End-to-End Encryption Device

4-2 Tactical End-to-End Encryption Device Milestone Summary

4-3 Near-Term Digital Radio Open Architecture

4-4 FDR/NTDR Milestone Summary

4-5 Wideband HF

4-6 WBHF Milestone Summary

4-7 Unified Endeavor Multi-Point VTC Experiment

4-8 ATM Technology Integration Program Milestone Summary

4-9 High-Capacity Trunk Radio

4-10 High-Capacity Trunk Radio Milestone Summary

4-11 Terrestrial PCS

4-12 Terrestrial PCS Milestone Summary

4-13 Direct Broadcast Satellite

4-14 Army Direct Broadcast Satellite Milestone Summary

4-15 Radio Access Point

4-16 Radio Access Point Milestone Summary

4-17 Phased-Array Communications Antenna

4-18 Phased-Array Communications Antenna Milestone Summary

4-19 Satellite Personal Communications System

4-20 Satellite PCS (UAV) Milestone Summary

4-21 Airborne Relays

4-22 Airborne Relay Milestone Summary



TABLE TITLE PAGE



2-1 BITS AWE Product Insertions



------------------------------------------------------------------------
ACKNOWLEDGEMENT
------------------------------------------------------------------------



1 INTRODUCTION



1.1 BATTLEFIELD INFORMATION TRANSMISSION SYSTEM

The Battlefield Information Transmission System (BITS) is a direct
outgrowth of the Army Digitization Master Plan (ADMP). The
ADMP describes the process that will lead to seamless
interoperability across the battlefield, the capability required to
transform the Army into a 21st-century force (Force XXI), and
provides guidance for developing, testing, and producing digital
hardware and software to meet Force XXI requirements. BITS is
the umbrella program under which the elements needed to support
Force XXI information-transport requirements come together.

Figure1-1 --> BITS Concept


1.2 BACKGROUND

Three documents provide the concepts and requirements for
battlefield digitization:

(1) the Horizontal Interoperability Battle Command Mission Needs Statement,
(2) the Army Battle Command System Common Operating Environment/Common
Applications Operational Requirements Document, and
(3) the Force XXI Battle Command for Brigade and Below Operational
Requirements Document.

To achieve the capabilities defined in
these documents, the Army Digitization Campaign Plan was
developed.

The four main thrusts of the Army Digitization Campaign Plan are:

1. Acquire a digitized capability for lower echelon forces
2. Develop a tactical Internet (TI) capability
3. Integrate all battlefield operating systems (BOSs)
4. Manage the evolution of BITS.


BITS is seen as a next-generation requirement because the future
digital load is expected to exceed the combined capacity of the
legacy systems (e.g., Single Channel Ground and Airborne Radio
System [SINCGARS], Enhanced Position Location Reporting
System [EPLRS], and Mobile Subscriber Equipment [MSE]
Tactical Packet Network [TPN]). These three systems,
interconnected with Internet Protocol (IP)-compliant routers,
comprise the TI. Distribution of digital information among the
profusion of devices such as command and control (C2) systems,
sensor platforms, and embedded computers will become the
dominant activity for information transport. Requirements for
imagery and real-time video in addition to voice and data point to
the need for multimedia services.

The BITS concept consists of both near-term and far-term paths.
The near-term strategy is defined by the ADMP. It calls for
solicitations to industry for a Near-Term Digital Radio (NTDR) in
Fiscal Year (FY) 95, which will be more capable than EPLRS
while costing less. It is expected to be available to support the
Division XXI Advanced Warfighting Experiment (AWE) in 1998.
The near-term strategy will also include the introduction of other
selected products as they are determined to be sufficiently mature.
The far-term strategy will be defined by this document.

The requirement for the BITS far-term strategy was originally
identified in the ADMP. Development of the strategy was
identified as an action for the Directorate of Information Systems
for Command, Control, Communications and Computers (DISC4).
The U.S. Army Communications-Electronics Command (CECOM)
Space & Terrestrial Communications Directorate (S&TCD) was
tasked by DISC4 to develop the BITS far-term strategy document.
A draft of that document was distributed for comment in March
1995. Based on the initial draft, the Army Digitization Office
(ADO) modified the task by calling for a comprehensive plan at the
milestone/resource level by FY for contributing programs, which
included a description of how the programs tie together and the
transition to an acquisition strategy, with dollars and milestones.
ADO requested that the strategy: (1) define a BITS program to
execute from FYs 95-99, (2) define an acquisition program for
BITS in the Program Objective Memorandum (POM) from FY99 to
support Force XXI fielding, and (3) identify required resource
shortfalls in both the experimental phase and the acquisition phase
in the FY97 POM.


1.3 PURPOSE

The purpose of this document is to describe the far-term BITS
strategy and provide both a management framework and a long-term
focus for the 6.2/6.3A technology base and Advanced Technology
Demonstration (ATD) products, Advanced Research Projects
Agency (ARPA) projects, Advanced Concepts and Technology
(ACT II) programs, and Battle Lab Warfighting Experiments
(BLWEs) that are addressing future communications needs.
Additionally, the far-term strategy will serve to focus the Program
Manager (PM) System Improvement Plans (SIPs) on emerging
communications systems requirements.

The far-term strategy will use warfighter experimental processes to
assess military utility and cost-effectiveness, and develop
requirements documents. The basis of these assessments will be the
ability to support Army forces participating in actions ranging from
major regional conflicts to operations other than war.


1.4 ORGANIZATION

Section 2 of this document presents an overview of the BITS, how
it will evolve, and the programs that support its evolution. Section
3 describes the far-term strategy for achieving a BITS capability,
including a discussion of how the user will participate in the
process, and the management framework for implementing the
strategy. Section 4 presents a detailed discussion of the 11
individual technologies that will comprise BITS. This document
also includes 2 appendices; Appendix A presents resource
requirements for BITS while Appendix B contains acronyms and
abbreviations.

------------------------------------------------------------------------

2 BATTLEFIELD INFORMATION TRANSMISSION SYSTEM OVERVIEW

------------------------------------------------------------------------




2.1 BATTLEFIELD INFORMATION TRANSMISSION SYSTEM EVOLUTION

The migration from today's legacy communications systems to the
objective BITS will be an evolutionary process. BITS elements will
be fielded as part of an incremental buildup beginning with Task
Force XXI (TF XXI) and continuing into the post-Year 2000 time
frame. The TF XXI, Division XXI, and Corps XXI AWEs will
demonstrate the incremental buildup of BITS capabilities in
simulated warfighting experiments. The BITS evolution is shown in
Figure 2-1 (BITS Evolution).

Subsequent to the approval and release of the ADMP, a significant
effort was undertaken by the ADO, DISC4, U.S. Army Training
and Doctrine Command (TRADOC) Battle Labs, CECOM, and the
Program Executive Office for Command, Control and
Communications Systems (PEO C3S) to define the BITS far-term
strategy. As part of this effort, existing programs were restructured
to support the introduction of BITS technologies as early as the TF
XXI AWE. As a result, technologies discussed as part of the far-
term strategy will first appear at the TF XXI AWE. Additional
capabilities will be added as they are deemed significantly mature.

The TI is the TF XXI baseline from which BITS must evolve. The
TI will support horizontal integration of highly mobile users and
seamless connectivity among tactical users. The TI is a means, of
integrating the various legacy battlefield communications systems
through the use of IP protocols and routers. This integration will
provide battlefield users with a seamless communications capability
and access to all available communications systems. The initial TI
will consist of SINCGARS, EPLRS, and the MSE TPN. These
three systems will be internetworked through the use of gateways to
form a complete, seamless system for the brigade task force,
division, and corps AWEs. The basis for the TI is the adoption of
IP protocols and commercial routers used with legacy
communications systems. Figure 2-2 (Tactical Internet) depicts the
TI.

The TI is functionally similar to the commercial Internet due to the
use of actual Internet technology and protocols. When sending
messages, TI users will only need to concern themselves with
message addresses, just as commercial Internet users address
electronic mail. Commercial Internet technology such as routers
and gateways, and protocols including Transmission Control
Protocol (TCP)/User Datagram Protocol and IP will provide
seamless connectiontivity between legacy communications systems.
As the Army solves the unique problems inherent in the adaptation
of this technology, it will create a baseline for smooth migration.
These standards will be the key to creating a backbone
internetwork seamlessly interconnecting legacy systems.

In addition to the TI, the BITS far-term strategy will contribute
several significant communications technologies to the TF XXI
AWE. Asynchronous Transfer Mode (ATM) switching,
successfully demonstrated in FY95 during the Proteus, Unified
Endeavor, and Grecian Firebold exercises, will be integrated with
the Area Common User System (ACUS) to provide video
teleconferencing capabilities. As part of the AWE experimentation,
wideband trunk radios, offering greater bandwidth than existing
ACUS LOS radios, will be used to more fully realize the benefits
of ATM technology. Experimentation with a prototype Future
Digital Radio (FDR) and Wideband HF Radios will demonstrate
the benefits of providing additional data capacity as a supplement
to the legacy (SINCGARS, EPLRS) radios. Direct-broadcast
satellite (DBS) technology will provide a means of disseminating
wideband imagery independent of the terrestrial infrastructure.
Commercial terrestrial Personal Communications Systems (PCS)
technology will be demonstrated as an upgrade to MSE.

While the TI and other BITS technologies introduced during the TF
XXI AWE will significantly improve on existing battlefield
communications capabilities, information requirements for the
future digital battlefield are expected to exceed the capacity of the
legacy systems and grow beyond the single-medium packet data
supported by the TI. The near-term BITS will build on the baseline
TI of TF XXI by providing additional data capacity and expanded
video/imagery services to support the increasing warfighterappetite
for information of all types. These capabilities will be demonstrated
during the Division XXI AWE. While near-term BITS will support
separate voice, data, and imagery services, there will be no
widespread use of integrated multimedia services. Supplementary
data capacity will be provided through the acquisition of an NTDR
capable of increased throughput and dynamic multihop networks.
The NTDR will satisfy critical speed of service needlines; provide a
self-healing, adaptive mobile network; and support TCP/IP hosts.
Integration with legacy radios will be achieved with IP gateways.

Experimentation during Division XXI will include enhancements to
the ATM switches initially demonstrated during TF XXI.
Enhancements will include adaptive forward-error correction
(FEC), survivable protocols, and dynamic bandwidth allocation.
High-Capacity Trunk Radios (HCTRs) capable of 45-Megabits-per-
second (Mbs) operation will be used to connect selected nodes.
Ongoing experimentation with terrestrial PCS technology will
continue during the Division XXI AWE with the demonstration of
a code-division multiple access (CDMA)-based system. The
Division XXI AWE will see the introduction of the use of
unmanned aerial vehicles (UAVs). For the division exercise, the
UAV will provide a platform for DBS; ultimately, UAVs will also
provide the platform for satellite PCS base stations and for relays
that will provide range extension for mobile HCTRs.

The far-term BITS will develop and introduce additional
technologies needed for an objective information-transport
architecture that provides wideband multimedia services and
supports the total force structure. While requirements for voice are
expected to remain fairly constant past the Year 2000, the demand
for data and imagery is expected to increase exponentially.
Moreover, split-based operations and the requirement to respond
and deploy rapidly require connectivity between highly mobile
forces in theater and the continental United States (CONUS).

BITS will support Force XXI concepts of:

Acquiring, exchanging, and employing timely digitized
information throughout the battlespace Providing the commander,
shooter, and supporter with a clear and accurate vision of the
battlespace Supporting seamless and timely delivery of
information across all boundaries Achieving horizontal and
vertical interoperability. Greater mobility, C3OTM


BITS will meet ADMP goals of:

Increased data capacity Reduced size for greater system
integration Multimode capability for more-efficient
communications Exploitation of commercial technology Use of
commercial standards and protocols.


The objective BITS, shown in Figure 2-3 (Objective BITS
Architecture), will provide increased throughput for ACUS and
interoperability with CONUS-based information systems through
the integration of ATM technology. The integration of ATM
technology will provide an objective switching architecture that
offers fully integrated multimedia services. Split-based operations
will necessitate connection to the Defense Information Systems
Network (DISN) using ATM format. The use of ATM technology
will address the requirement for multimedia services while making
efficient use of available bandwidth.

Mobile operations at echelons brigade and below will be supported
by a mobile communications center, the Radio Access Point (RAP).
Connectivity between the RAP and rear area will be provided by a
mobile HCTR, capable of (minimum) 45-Mbps operation while on
the move (OTM). Range extension will be provided through the
exploitation of aerial relays, including UAVs. Data distribution
will be improved through evolution toward an FDR, satellite PCS,
and continued experimentation with direct-broadcast video
services.

Reach-back will be accomplished using commercial and military
satellite communications.

Products and capabilities being developed or studied at this time
that are expected to contribute to the BITS architecture are shown
in Table 2-1, as are product insertion opportunities. All
technologies in the BITS far-term strategy will be demonstrated
during the TF, Division, or Corps XXI AWEs, with the exception
of the RAP, mobile HCTR, and satellite PCS, which will be
demonstrated in late FY99. Each of these products is discussed in
detail in Section 4 of this document.


2.2 SUPPORTING PROGRAMS

The Army will develop and integrate a series of technologies that
will support the Force XXI digitization initiatives and lead to a
complete definition of the Force XXI BITS. Programs sponsoring
these efforts (see Figure 2-4 -->Supporting Programs) include the
CECOM Digital Battlefield Communications (DBC) ATD, the
Joint Service/ARPA SPEAKEASY program, the Army NTDR
acquisition, the TRADOC ACT II program, the ARPA/CECOM
Commercial Communications Technology Test Bed
(C2T2)/Commercial Communications Technology Laboratory
(C2TL) programs, and the PM SIPs. These programs are discussed
in the following paragraphs.


2.2.1 Digital Battlefield Communications Advanced Technology
Demonstrations

DBC is a five-year (FYs 95-99) ATD designed to integrate and
exploit emerging wireless communications services and technology.
These include ATM switching, phased-array antennas, wideband
data radios, emerging satellite and terrestrial-based PCS, direct-
broadcast satellite video technology, aerial relays, and HCTR. The
ATD addresses command, control, communications, computers,
and intelligence (C4I) deficiencies identified in the May 1994
United States Army Modernization Plan. DBC provides improved
capabilities for command, control, and communications (C3) OTM,
range extension, and information distribution that will enhance
tactical effectiveness and survivability.

Technical objectives of the DBC ATD are as follows:


Major departure from classical echelon-aligned communications
architecture to support emerging requirements for real-time tactical
information dissemination Exploitation of non-groundbased
services/technology to extend communications range Heavy
exploitation/adaptation of commercial communications services
Warfighter access to Global Grid ATM infrastructure (DISN)
Complementary modeling and simulation (M&S).



Elements of the DBC ATD are shown in Figure 2-5 (Digital
Battlefield Communications Architectural Elements). The technical
objectives of the program will be achieved through the successful
demonstration and warfighter evaluation of the following:


Direct Task Force XXI support (FDR, Tactical Multinet Gateway
[TMG]/Internetwork Controller [INC]) ATM exploitation RAP
HCTR Airborne relays OTM antenna Satellite PCS DBS.


Subsequent to the initiation of the DBC ATD, Army leadership
identified additional areas for insertion into the DBC ATD. They
include:


Terrestrial PCS Wideband HF Multilevel security (MLS) FDR for
TF XXI experimentation.


The DBC ATD is funded under program elements D247, D257, and
AH92. Additional D247 funding was identified to accelerate the
DBS work and to establish connectivity between the Battle
Command Battle Lab at Fort Gordon, Georgia (BCBL [G]), and the
CECOM ATM test bed. Figure 2-6 (DBC ATD Addresses Stated
Army C41 Deficiencies) depicts how the DBC products address
deficiencies identified in the United States Army Modernization
Plan. The DBC products and the operational capabilities they
provide are discussed in greater detail in Section 4 of this
document.


2.2.2 Future Digital Radio

The FDR is described by an approved mission needs statement
(MNS), dated 16 May 1994, to meet future Force XXI multiband
multimode communications requirements. The FDR is described as
an "enhanced multiband digital radio, providing short to long range,
simultaneous secure voice and high-speed data, and multi-
waveform interoperability with existing and proposed systems."
Three programs are currently underway that support the FDR
requirements. The Army NTDR program will provide the basic
building block for the FDR. The NTDR will provide an open-
architecture radio capable of accepting modular hardware and
software. The establishment of an NTDR test bed at CECOM will
support this evolutionary approach through technology insertion.
The joint SPEAKEASY program will transition enabling
technologies to the NTDR program to support FDR evolution. The
DBC ATD has issued a broad agency announcement (BAA) to
provide prototype radios with FDR capabilities for sidebar testing
at the TF XXI AWE. The FDR evolution is illustrated in Figure 2-7
(FDR Evolution).


2.2.2.1 Near-Term Digital Radio Program.

The NTDR program is a planned FY95 PM Tactical Radio
Communications Systems (TRCS) acquisition of nondevelopmental
item (NDI) technology to supplement EPLRS with an interim
wideband data capability for experimentation during the Division
XXI and Corps XXI AWEs. The program goals are to establish an
open-system architecture to permit technology growth at both the
box and system levels, and to have a high-data-rate waveform that
provides higher throughput than the EPLRS radio. The NTDR will
have the external interfaces and data capacity to replace EPLRS in
Division XXI and will be required to internetwork with
SINCGARS and MSE using Tactical Multinet Gateway (TMG) and
Internet Controller (INC) IP-based technology.

2.2.2.2 SPEAKEASY Multiband Multimode Radio.

The SPEAKEASY Multiband Multimode Radio (MBMMR) is a
Joint Service program to develop technology needed to meet the
Army's FDR requirement. Phase I of the SPEAKEASY MBMMR
program will end in the third quarter of FY95 (3QFY95) with the
award of Phase II in 4QFY95 (July 1995). Phase II will provide
advanced development models (ADMs) to demonstrate a highly
flexible open-system-architecture radio, allowing rapid waveform
reprogram-mability/reconfigurability to support the dynamically
changing mission requirements of electronic warfare (EW) threat,
interopera-bility, networking, traffic load, frequency assignment,
and general modes of operation. State-of-the-art design will provide
the ability to enhance existing waveforms (such as SINCGARS,
ultra high frequency, EPLRS, etc.) or emulate new waveforms
simply by software or common-module exchange. Technology
insertion will include the use of advanced digital signal processing
multichip modules, programmable four-channel CYPRIS chip
information security (INFOSEC) modules, and new
multiband/wideband antenna designs.

Initial ADM prototypes will be available in FY98 and will be used
in the DBC ATD, with the final ADM available in FY99.


2.2.2.3Future Digital Radio Broad Agency Announcement.

As part of the DBC ATD, CECOM is acquiring a small quantity of
operational hardware that addresses functional areas of the FDR
MNS for evaluation during the TF XXI AWE. The BAA approach
was used to acquire the most sophisticated technology industry has
to offer in a time frame that makes its evaluation during TF XXI
possible. In addition to providing advanced radio technology prior
to the availability of the NTDR, the FDR BAA radios address
requirements stated in the FDR MNS that are not requirements of
the NTDR. These include multiband/multimode and voice-plus-
data capabilities. The FDR BAA will provide 10 to 20 radios for
sidebar experimentation at the TF XXI AWE.


2.2.3 Commercial Communications Technology Test
Bed/Commercial Communications Technology Laboratory


2.2.3.1 Commercial Communications Technology Test Bed.

The C2T2 program, developed jointly by ARPA and CECOM, was
initiated to exploit rapidly developing commercial communications
capabilities in the military environment. Commercial
communications technologies identified under the C2T2 program
will be evaluated in conjunction with TRADOC Battle Labs for
military utility. The C2T2 program objectives include the
characterization and measurement of the use of, and need for, voice
and data communications on the modern battlefield, with an
emphasis on the dismounted soldier. As each piece of equipment is
evaluated for its applicability to military communications
requirements, the results will be provided to the Battle Labs and to
the manufacturers of the equipment. The C2T2 efforts are
coordinated with PEOs and the Battle Labs for equipment insertion
in AWEs, and are evaluated in the CECOM Digital Integration
Laboratory/Test Bed (DIL/T), prior to the AWE.

A C2T2-developed system will be demonstrated at the Joint
Readiness Training Center (JRTC) during the Warrior Focus AWE,
JRTC 96-02, from 4 through 23 November 1995. The purpose of
the experiment-sponsored by the Dismounted Battle Space Battle
Lab and supported by the CECOM Research, Development and
Engineering Center (RDEC)-is to examine the battlefield impact of
digital communications and own-the-night capabilities across all
BOSs, for the dismounted soldier. This AWE will also provide key
information for the Army's leadership as they chart the future
course for digitization of the Army.


2.2.3.2 Commercial Communications Technology Laboratory.

The CECOM RDEC is extending the C2T2 to the C2TL to
evaluate state-of-the-art communications equipment and further
explore a wider range of commercial technology application to
military communications requirements. C2TL areas of interest
include data links, wireless networks, communications devices
(MBMMRs, secure telephone in bag, video docking bay, etc.),
office automation, INFOSEC, and protocols. The early evaluation
of commercial products and feedback to the manufacturers and
Battle Labs will result in more cost-effective and timely fielding of
leading-edge communications technology. The output of the C2TL
program is a series of evaluation reports, which can be used as the
basis for developing operational requirements for transition to the
PEO/PM.


2.2.4 Advanced Concepts and Technology Program

The TRADOC ACT II program provides seed money for proof-of-
principle demonstrations of high-risk/high-payoff concepts
proposed by industry. Such efforts provide an opportunity to try
unconventional approaches and/or technology not currently
supported in mission- oriented Army programs. ACT II projects are
frequently cost-shared or leveraged efforts partly supported by
others. The ACT II Program provides direct support to the
TRADOC Battle Labs and Louisiana Maneuvers. This coupling to
the user community is the best means of evaluating new capabilities
enabled by ACT II technologies and provides additional direct
support from the research, development, test and evaluation
community.

Contracts in response to ACT II proposals are awarded by various
Army procurement offices. A number of ongoing efforts under the
ACT II program have the potential to contribute to the far-term
BITS. Evaluation of range extension for the MSE Radio Access
Unit (RAU) is currently planned for the TF XXI AWE. CECOM is
the contracting authority for a large number of these effort, with
S&TCD serving as the contracting officer's representative and
providing overall technical guidance. These efforts are executed in
close coordination with the sponsoring Battle Lab.

2.2.5 Project Manager System Improvement Programs

A PM SIP is a five-year plan for evolving and enhancing existing
Army communications assets. The Pms work closely witht he R&D
community to ensure that the PM SIP is aligned with R&D product
concepts. Pms responsible for acquiring and fielding BITS include
Joint Tactical Area Communications Systems (JTACS), TRCS, and
MILSTAR. The Pms identify five-year resource requirements for
fielding BITS elements Army-wide. PEO C3S and the relevant PM
are responsible for aligning the SIP to exploit advances in
technology and adopt products emerging formt he R&D technology
base. This phase of the GITS strategy is discussed in Section 3 of
this document.

------------------------------------------------------------------------

3 FAR-TERM STRATEGY

------------------------------------------------------------------------




3.1 INTRODUCTION

Because lengthy R&D and production cycles will impede the fight
to win the information war and budgetary constraints will limit the
number of new system developments, the BITS far-term strategy is
consistent with the Army Enterprise Vision in emphasizing the
exploitation of readily available solutions, developing new systems
only to meet unique military requirements. Scarce resources and
new realities necessitate the imposition of a value system whereby
the introduction of communications-systems technology provides
maximum return on investment in terms of operational capabilities.

3.2 APPROACH

The approach used in developing, demonstrating, and fielding BITS
capabilities consists of the three phases shown in Figure 3-1 (BITS
Strategic Framework). The R&D, or "Blue," phase is the
responsibility of CECOM and other R&D activities and culminates
in technology insertion into an AWE, BLWE, Joint Warfighting
Interoperability Demonstration (JWID), or other field exercise. The
leave-behind, or "Yellow," phase consists of providing additional
equipment to operational units, for a period of up to two years, for
the purpose of product evaluation and requirements definition.
During the acquisition, or "Green," phase, the products developed
and refined during the first two phases are handed of to the
PEO/PM for acquisition and fielding.


3.2.1 Research and Development Phase

R&D efforts conducted in support of BITS consist of adapting of
NDIs to provide required capabilities, product evaluation in a
laboratory environment, adopting commercial standards, developing
system components to meet military-specific needs, exploiting
M&S, and performing experimental testing in a user environment.

A foundation of this approach is the appropriate use of NDI
technology. Products will be aligned to exploit technologies
already available in the defense or commercial sectors. R&D
programs and ATDs must include extensive market surveys and
literature searches to determine the availability of required
capabilities. Off-the-shelf products will be adapted to meet
emerging Army requirements whenever possible.

A primary tool for evaluating products in a laboratory environment
is the DIL/T. The DIL/T is a collection of real and simulated C3
facilities designed to validate compliance with standards and
protocols and certify interoperability. The DIL/T is the first stop for
all BITS products prior to field experimentation. The DIL/T,
located at and operated by CECOM, is the focal point for many
other Army agencies involved in BITS development. The DIL/T
provides connectivity to the Battle Labs through the Army
Interoperability Network and the Joint Advanced Demonstration
Environment (JADE). The JADE test bed, shown in Figure 3-2
(Joint Advanced Development Environment), was established in
FY94 under the Joint Directors of Laboratories Technology Panel
for C3 Communications Network Subpanel to investigate, develop,
and demonstrate ATM switching technology for the tactical
environment.

Requirements for data communications on the battlefield have led
to the adoption of commercial standards. This approach allows the
Army to leverage commercial successes while promoting
interoperability. The baseline TI is based on commercial IP
protocols. Adopting IPs allows the Army to leverage commercial-
off-the-shelf (COTS) software applications and information-
transport hardware, while providing a common baseline with the
commercial sector for evolutionary growth. To meet requirements
for integrated voice, data, and imagery services, BITS will evolve
towards International Telecommunications Union (ITU)
Telecommunications Standardization Sector (TSS)
recommendation-compliant integrated-services digital networks
(ISDNs, e.g., ATM switching, synchronous digital hierarchy
transmission systems, and standardized subscriber loops for
broadband and narrowband ISDN [B-ISDN, N-ISDN]).

While the BITS far-term strategy seeks to leverage commercial
products and technologies to the maximum extent possible, it is
recognized that new development activities will be required to meet
military-specific needs. This is particularly true in the area of
INFOSEC, where the needs of commercial world are not aligned
with those of the military. Other areas where the needs of the Army
are not likely to be met by the commercial sector include OTM
antennas, aerial relays, and high-capacity digital radios capable of
operating in a high-bit-error-rate, mobile, noncellular environment.

M&S is a cost-effective means for evaluating equipment
characteristics in a simulated environment prior to live
hardware/software demonstrations. System performance modeling
will provide the basis for developing functional and performance
requirements and detailed system architecture definitions for
subsequent NDI acquisitions. Virtual and constructive simulations
and live exercises support early user involvement and operational
effectiveness analysis and will play a major role in the BITS
development.

Throughout the R&D process technology base activities are
coordinated with the TRADOC Battle Labs and the ADO. Army
Science and Technology objectives (STOs), which include all
ATDs, are reviewed annually to ensure that they are consistent with
the needs of the warfighter. During the STO review process,
programs are prioritized based on the extent to which they address
Battle Lab Operational Capability Requirements (OCRs). Early
and continuous involvement of warfighters in the capabilities-
definition process provides a balance between investments for
"technology push" from the R&D community and the immediate
needs from warfighters as a "requirements pull." The development
of the BITS far-term strategy has been a coordinated effort between
DISC4, the ADO, CECOM, PEO/PMs, and the Battle Labs. In
developing the strategy, supporting programs were aligned to strike
a balance between supporting the near-term needs of the warfighter
and the Force XXI concept while maintaining a reasonable
investment strategy for the longer-term vision of Battlefield
Information System 21 (BIS 21)

In implementing BITS far-term strategy, the focus will be on user
operational effectiveness and utility. Technology will be placed in
the hands of the warfighter at the earliest opportunity. This is
accomplished by participation in AWEs, BLWEs, and JWIDS.
Figure 3-3 illustrates the contribution-"Blue" funded-made during
the R&D phase to user experimentation. AWE support included in
ATD funding includes equipment fieldworthiness
preparation/evaluation and installation in the appropriate vehicle or
assemblage. Nine months prior to the AWE, the R&D activity will
provide personnel for a two-week period to train the acquiring units
and provide engineering support during the training. In the nine
months preceding the AWE, the R&D activity will send personnel
on two trips of one week each to the acquiring units location to
provide on-side engineering support for "trouble calls." The R&D
activity will also provide two weeks of engineering labor prior to
the exercise to set up and will remain on-side for two additional
weeks to support the exercise. The R&D activity will also provide
repair parts and maintenance for the exercise and a brief checklist
of operating instructions. All "blue" funding is provided by
technology base program lines(i.e., Digital Battlefield
Communications ATD)

Figure 3-3 --> BITS Development Strategy

3.2.2 Leave-Behind Phase

Following the completion of an AWE, BLWE, or JWID, if the user
determines that a candidate technology offers promise for meeting
operational needs, a leave-behind phase is initiated. During the
leave-behind phase an operationally significant quantity of
equipment is left with the unit for further experimentation and
evaluation. While the leave-behind equipment is not intended for
actual warfighting, it could be used for that purpose if required.

The leave-behind phase provides a mechanism for user involvement
with the products of ATDs and other R&D programs while they are
still at a formative stage. The objectives of the leave-behind phase
are to:

1.have the user gain an understanding of and evaluate the military
utility of products prior to committing to acquisition, 2.develop
corresponding concepts of operation and doctrine that make best
use of the new technology, 3.develop operational requirements that
are transitioned to the PEO/PM to begin the formal acquisition
process, and 4.provide residual capabilities to the forces.


The leave-behind phase also provides a forum for the user to
informally evaluate and compare competing products that provide
similar operational capabilities. The leave-behind phase typically
lasts for two years or less. Funding for the ("yellow") leave behind
phase is not included in the ATD.

The concept of operations and the corresponding equipment
quantities for the leave-behind phase for BITS have been identified
by CECOM, the ADO, the Signal Center DCD, and BCBL(G) and
are documented in Section 4 of this document. TRADOC is
responsible for developing the measures of performance/measures
of effectiveness (MOPs/MOEs) for user evaluation during the
leave-behind phase, and DISC4 is charged with overseeing the
development of system requirements for the BITS based on the
outcome of these evaluations. The ADO has responsibility for
resourcing the leave-behind phase for BITS products. In addition,
TRADOC is responsible for BITS requirements generation.

The desired end-products of the leave-behind phase are operational
requirements. The leave-behind phase will culminate in a decision
by the user whether to proceed with acquisition. If the user
determines acquisition is warranted, TRADOC will develop a
Required Operational Capability (ROC) document to initiate the
process. Funding for the fielding of the new system is budgeted in
the OPM by PEO/PM participation during the R&D phase.
Acquisition POM funding follow yellow leave-behind.


3.2.3 Acquisition Phase

The acquisition process for the communications systems needed to
support Force XXI concepts will differ greatly from those of the
past. Meaningful acquisition reform will be implemented to
modernize for Force XXI in a timely and affordable manner. The
foundation of this reform will be extensive use of commercially
available equipment and standards, early introduction and
evaluation of new products as an integral part of warfighting
experimentation, and rigid adherence to the Army's Technical
Architecture.

The task of transitioning requirements identified during the leave-
behind phase into technical specifications usable by PEOs and
PMs in the acquisition of hardware and ensuring that those
specifications meet the desired commercial standards and protocols
and are consistent with the Technical Architecture falls to the U.S.
Army Materiel Command (AMC)/CECOM. And just as the
requirements for new systems cannot be developed on a business-
as-usual basis, neither can the process of moving the systems
required to meet those requirements to the field. The PEO/PM is
responsible for acquiring and fielding the technology.

The PEO/PM community works closely with the R&D community
and TRADOC during the planning phase of all tech base initiatives
to ensure that sufficient funding is built into the POM for fielding.
Not all "Blue" and "Yellow" funded activities, however, result in a
"Green" acquisition phase. In some instances, products evaluated
during the R&D and leave-behind will include competing products
that provide similar capabilities. In such cases the user down-
selects one of the products for the follow-on acquisition. If the user
determines that a product offers limited operational utility, the
effort may be terminated prior to the initiation of acquisition.

To keep pace with new technology, COTS products and
capabilities proven to be effective in warfighting experimentation
will need to be transitioned quickly to the soldier. The use of
existing commercial standards will expedite this process, as will
the application of lessons learned from the experimentation process
pertaining to the degree of additional ruggedization required for
any given system.

The focus of the process will be on ensuring room for future
technology insertion, using the pre-planned product improvement
(P3I) process, and accommodating modular enhancements.
Acquisition ("green") funding is not addressed in this document.


3.3 REQUIREMENTS GENERATION

Despite the emphasis on the use of commercial products and the
acceptance of the need for acquisition reform, the development of
BITS will be a requirements-based process. The fundamental
requirements documents for Force XXI cited in Section 1 are
overarching documents that provide a vision and framework for
Force XXI; they do not, however, contain the detailed requirements
necessary to support specific technology-assessment and product-
development programs. Requirements for the information-transport
system that will support the warfighter's increasing need for
information of all types are more implied than explicitly stated at
this time. BITS requirements will be developed through an iterative
process of laboratory and user evaluation.

OCRs are created by the Battle Labs from their battle dynamics
concepts. These are critical requirements statements because Battle
Labs provide the focus for all Army experimental work leading to
the satisfaction of warfighter needs. In essence, OCRs are used by
the Battle Labs to articulate science and technology needs to the
development community. As overseer of the Battle Labs, TRADOC
is responsible for ensuring that OCRs reflect the redesigned force,
conform to Army priorities, fit within the operational architecture,
meet joint and combined information exchange requirements, and
are in accord with other digitization objectives. OCRs provide
basic operational requirements during the ATD planning process
for establishing exit criteria. During the annual STO review
process, ATDs are evaluated to determine the extent to which they
are supporting the OCRs.

The requirements process continues with laboratory and user
evaluation. M&S experiments and testing in the DIL/T are
conducted to gain insights concerning the application of
technology to meeting the needs of the warfighter as expressed in
the OCRs. The technology is ultimately offered to the user for
experimentation during an AWE, BLWE, or JWID. Lessons
learned during the user evaluation are used in the evaluation of the
utility of the technology, in assessing what modifications might be
made to improve the technology, and in considering how the
technology might be best deployed. The leave-behind phase gives
the user an extended period to further evaluate the product and
develop requirements. The product of the leave-behind will be a
formally documented requirement from the user, such as a ROC.
The development of operational requirements for the BITS is the
responsibility of TRADOC.

Operational requirements resulting from the user evaluation process
will initiate the acquisition process. The operational requirements
will be handed off to the PEO/PM who will develop system-level
requirements. The generation of system-level requirements for BITS
will be supported by AMC/CECOM.


3.4 USER INVOLVEMENT

Early and continued involvement of the user is a key component of
the BITS far-term strategy. User experimentation will be used to
streamline the acquisition process and refine operational
requirements.


3.4.1 Battle Lab Warfighting Experiments

BLWEs are simulated or live events designed to examine new
equipment, processes, and force-design issues. BLWEs are
intended to provide significant opportunities for rigorous data
collection to satisfy evaluation requirements.

TRADOC is responsible for coordinating, conducting,
andanalyzing BLWEs to provide timely feedback for decisions on
Force XXI design. TRADOC is also responsible for aligning ACT
II BLWEs with digitization objectives. Participating commands are
the U.S. Army Operational Test and Evaluation Command
(OPTEC), ADO, the Army Materiel Systems Analysis Activity
(AMSAA), and CECOM.


3.4.2 Advanced Warfighting Experiments

AWEs are major events conducted in a tactically rigorous
environment to confirm experimental hypotheses regarding
increases in warfighting capability. System performance data
collection during these events will be limited to minimize
interference with training, realism, and other objectives.

AWEs are intended to demonstrate improvements in force-
effectiveness as a result of fielding digital information
technologies, and by changing organizational designs and tactics,
techniques, functions, and procedures. Appliqu? and ATD
equipment will be examined in these experiments to establish an
early understanding of their warfighting potential. Each experiment
will build on the results of previous experiments, creating the
"rolling baseline" assessment to measure force-effectiveness
increases.

Key AWEs in the near future are:


Focused Dispatch (August 1995) Warrior Focus (November 1995)
Task Force XXI (February 1997) Division XXI (February 1998)
Corps XXI (February 1999).


3.4.3 Joint Warfighting Interoperability Demonstrations

JWIDs are a series of interoperability demonstrations sponsored by
the Joint Staff to test interoperability on the digitized battlefield.
They are complex undertakings that bring together the Services,
federal agencies, and commercial vendors. Interoperability and
Joint operations are the fundamental goals of these demonstrations,
goals that are intended to advance the "C4I for the Warrior"
concept.

JWID '95 is sponsored by the Marine Corps and will be held in
September 1995. The primary objective of JWID '95 is to
demonstrate the interoperability of existing and emerging C4I
systems employed in a Joint Task Force deployment scenario.
Several key BITS technologies are expected to be introduced at
JWID '95.

The Marine Corps will use this opportunity to exercise its MAGTF
C4I systems strategy. The Army will take advantage of the
opportunity presented by JWID '95 to assess interoperability
between MAGTF C4I systems and Force XXI Battle Command for
Brigade and Below (FBCB2).


3.5 MANAGEMENT

The evolution of BITS cannot be "business as usual," and
management of the process will be a collaborative effort between
various agencies, organizations, and offices. Figure 3-4 (BITS
Management Structure) shows the organizations responsible for the
BITS evolution. Timely, accurate synchronization of the activities
of the participating entities will be the key to the success of the
program.

------------------------------------------------------------------------

4 EXECUTION

------------------------------------------------------------------------




4.1 INTRODUCTION

As discussed in Section 2, there are 11 products that contribute to
the BITS far-term strategy. Each product is a result of one, or in
some cases several, of the supporting programs identified in
Section 2. This chapter describes each product, provides a summary
of the R&D, leave-behind, and acquisition phases, and identifies
development milestones. Resource requirements for each product
are included in Appendix A.


4.2 BATTLEFIELD INFORMATION TRANSMISSION SYSTEM
ELEMENTS

4.2.1 Tactical End-to-End Encryption Device

As illustrated in Figure 4-1 (Tactical End-to-End Encryption
Device), the Tactical End-to-End Encryption Device (TEED) will
provide end-to-end security services to Force XXI data users. The
TEED will provide MLS capability to the TI, which currently
operates at a level of SECRET HIGH. Program milestones are
illustrated in Figure 4-2 (Tactical End-to-End Encryption Device
Milestone Summary).


4.2.1.1 Research and Development.

Proof of concept (POC) development of TEED began in FY94 with
D491 funding. Certifiable models will be delivered in May 1996.
Waivered models (not as fully functional as POC models) are being
developed for JWID '95 (August through September 1995) DBC
funding, D247, is being used to exercise an option on the POC
TEED contract to acquire 18 models to support the TF XXI AWE.
These models will be delivered in May 1996, making them
available for use at the TF XXI AWE in February 1997. All 18
models on the DBC build are dedicated to the Experimental Force
(EXFOR) exercises. Twelve of the basic-build TEEDs will be made
available to cover major EXFOR exercises.

The National Security Agency (NSA) has funded a study to
investigate the new BATON encryption algorithm for application to
TEED. BATON is an algorithm that will encrypt ATM, as well as
IP, traffic. BATON is the encryption technique for the future. The
TEED Internet Security Manager (TISM) is being developed to
support TEEDs in the field; it will perform remote keying, remote
zeroization, auditing, and other security and security-management
functions for TEED. Full-scale engineering development (FSED)
TEEDs will be IP/ATM-capable. If the POC TEEDs are successful
at JWID '95, a possible acquisition scenario would be to provide
production funding in FYs 97 through 99. The R&D cost would be
amortized over a production lot of 4,500 units. An initial delivery
of 200 TEEDs will support the Corps XXI AWE. The acquisition
of an additional 4,300 units will allow the Army to acquire the
minimum number of TEEDs needed as rapidly as possible (4,500
units represents one TEED at every C3-XA packet switch in the
Army). These units would start delivery in FY98 with deliveries
through FY00. On a success-oriented schedule, FSED TEEDs
could be delivered as early as May 1998. This would make them
available for use at the Corps XXI AWE in February 1999.

A fieldworthy TEED will be approximately the size of a
commercial telephone book Yellow Pages, and will be desktop-
mountable, much like an external modem. TEEDs can be powered
by 24 volts direct current (Vdc), as found on Army vehicles, or by
commercial power using the supplied power supply that converts
110 to 120 volts alternating current (Vac) to 24Vdc. The TISM will
include a host computer and a secure front end, will be desktop-
mountable, and will use commercial power.

Delivery of 30 prototype IP TEEDs is expected in May 1996. A
training course (at the contractor's facility) and operator manuals
(to commercial standards) will be delivered as well.
Troubleshooting (logistics and maintenance) will be covered by a
time and materials (T&M) contract to the vendor. This will cover
repairing TEEDs and shipping them to and from the contractor's
facility. On-site engineering support for exercises will be provided
by contractor and CECOM personnel.

The EXFOR will continue to use the 30 TEED models delivered in
FY96, and TEED support will begin transition to leave-behind
funding. Portions of logistics and engineering support are covered
by R&D funding to support the users in preparing for the TF XXI
AWE. The remaining costs are leave-behind funded. A user training
course will be provided at Fort Hood, Texas, for the TEED and the
TISM. The TISM will provide the security-management and
support functions for TEEDs until the Army Key Management
System (AKMS) and Integrated System Control (ISYSCON)
become available. The cost of training TEED operators is leave-
behind funded while TISM training is R&D funded.

R&D funds will be used to support TISMs in the Division XXI
AWE. This includes training, maintenance, and engineering
support and initialization of the TISMs. TEEDs with IP and ATM
capability are projected to be available in May 1998. If this date is
met additional funding may be needed to support the new devices.
Although they will be built with production money, the supporting
infrastructure will probably not be ready by May 1998.

Transition to ATM/IP TEEDs will be completed in FY99. The
material developer may still have to support these units as the
infrastructure may not yet be in place. A training course on the new
TEED, and logistics and engineering support will be required.


4.2.1.2 Leave-Behind Phase.

The leave-behind package will consist of 30 TEEDs, which will be
available at the TF XXI AWE. These 30 units will be purchased
with R&D funds. Additional leave-behind dollars will be required
for training and logistics and engineering support to support the
("yellow") leave-behind phase following each AWE insertion.


4.2.1.3 Acquisition.

FSED acquisition with low-rate initial production (LRIP)
quantities could begin as early as FY97. Instructor and key
personnel training will take place under the FSED TEED effort. A
maintenance course will also take place during FSED so that
military personnel will have capability to repair FSED as well as
production TEEDs. Production funds will be used with the R&D
cost amortized over the LRIP quantities. These units will start
delivery during FY98 and continue through FY00. Subsequent
production could start in FY98 with deliveries in FY01. Both of
these efforts are, at present, unfunded.


4.2.1.4 Concept of Operations.

As long as the TPN remains at its current security level of SECRET
HIGH, the TEED would be used by unclassified (UNCLAS)
logistics users who need to use the TPN as a common carrier and
intelligence and electronic warfare users whose security needs
exceed the SECRET level of the MPN. In the first instance, the
TEED will be used to protect the base-level (SECRET) users from
users at a lower classification (UNCLAS); in the second, the TEED
protects the higher-level TOP SECRET users from the base
network (SECRET). The TEED is designed to protect both of these
applications. Specifically, TEEDs will be collocated with logistics
users at the division support command (DISCOM) elements and
their counterparts at the brigade trains areas. TEEDs will also be
located with any military intelligence (MI) users and any elements
at division main (DMAIN) that interact with them. Allowing 3 of
the 30 units for "hot spares," the UNCLAS users might use 6 to
support TEEDs at DISCOM, with 12 units distributed to brigade
trains area logistics users. To support the TS community, three
TEEDs would service division headquarters (HQ), with six
available to secure MI users at various echelons (MI company,
engineers, etc.)

If TPN becomes unclassified, the TEED would be used by
SECRET and TS users. The unclassified community could then use
the unclassified TPN directly without the need for a TEED or any
other security device. Network planners find this an attractive
possibility as the TPN could then be concatenated to any public
network to provide robust internetworking to destination addresses
on the Internet. In this case, the TEEDs that had been requisitioned
to logistics users would be reallocated to SECRET users in other
battlefield functional areas. Eight of the eighteen units originally
provided to UNCLAS users would be redistributed to DMAIN to
secure the commanding officer (CO), executive officer (XO), G1,
G3, G4, G6, division artillery officer, and the division signal
officer. At brigade trains, the CO, XO, S1, S3, S4, and signal
forward area platoon leader would receive TEEDs.


4.2.2 SPEAKEASY/ Future Digital Radio (Broad Agency
Announcement)/Near-Term Digital Radio

SPEAKEASY, FDR (BAA), and NTDR are feeder programs
needed to develop the digital and MBMMR technology to enable
the Army to field the objective FDR. The NTDR will be based on
an open architecture that facilitates technology insertion.

Figure 4-3 -->Near-Term Digital Radio Open Architecture.

Program milestones are illustrated in Figure 4-4.


4.2.2.1 Research and Development.

The requirement for the FDR is described in the FDR MNS, which
was originally written as the supporting user documentation for the
Joint SPEAKEASY program. Because, the SPEAKEASY program
was not conceived or planned to provide operational hardware that
would be available in time for the TF, Division, or Corps XXI
AWEs, the FDR BAA and NTDR efforts were planned and are
being executed.

The SPEAKEASY program was initiated as a tech base program to
provide technical capabilities required by the FDR MNS. The
Phase II SPEAKEASY program is currently underway. The first
part of the effort involves the design and fabrication of equipment,
after which there will be an intermediate demonstration. After the
demonstration, there will be continued refinement, leading to
fabrication of the final Phase II hardware. The principal barriers in
this phase are the physical size and power consumption of the
Phase I hardware. The other major technical challenge is the radio
frequency (RF) interfacing of the simultaneous multiband and
multimode signals being transmitted and received by the radio.

The FDR BAA, which predates the NTDR, is to provide a small
quantity of operational hardware to address functional areas of the
FDR MNS during the TF XXI AWE. The BAA approach was used
to obtain the most technically sophisticated hardware as quickly as
possible. The contracts for this effort are currently being
negotiated. The plan is to award competitive contracts for from
three to five radios each to two contractors. These radios will be
tested in the CECOM DIL/T and a decision will be made as to
which of the radios comes closest to meeting the objectives of the
FDR MNS. Ten to twenty units of the down-selected radio will be
procured as an option to the basic contract. These radios will be
available in time for participation in a limited experiment during
the TF XXI AWE.

Laboratory models from the 2 FDR (BAA) vendors are due no later
than 90 days after award. These models will undergo extensive
testing in the DIL/T to determine to what extent the equipment
meets the manufacturer's specification and how close it comes to
meeting the requirements of the MNS. A down-selection will then
be made to the one closest to meeting the MNS, and an option will
be exercised to procure 10 to 20 radios for participation in the TF
XXI AWE. The FDR BAA radios have features that address
requirements stated in the FDR MNS, but which are not
requirements of the NTDR. These features are
multiband/multimode operation and voice-plus-data capability.
These features, along with the availability of the FDR BAA radios
for the TF XXI AWE, are strong factors for making sure that the
FDR BAA program proceeds. An additional benefit of the FDR
BAA program isthat it is funding the initial design and
implementation of an area in the DIL/T that will be used for the
testing of digital radios. This area will provide access to INCs,
TMGs, legacy radio systems, and host hardware, including
appliqu?s. This facility will be in place in time for the September
through October 1995 DIL/T testing of the FDR BAA lab models.
This is an entire year before the NTDR will undergo DIL/T testing.
As such, the FDR BAA DIL/T testing will provide a valuable
educational opportunity to prepare for NTDR testing as well as a
vehicle for establishing a test bed facility for use both by CECOM
and PM TRCS.

The FDR BAA field models will be available in March 1996;
April, May and June 1996 will be dedicated to installation and
training. Included with the field models will be installation kits and
antennas as well as operator manuals. A two-week training period
is planned for May 1996 following installation of the radios. The
current plan is to buy 15 radios for the TF XXI AWE. CECOM
personnel will install the radios, train the troops, and provide on-
site support as needed. A T&M repair contract will be instituted
with the manufacturer or support contractor to be on call for repairs
and o provide spare parts.

The NTDR is a PM TRCS-managed program. The objective of the
program is to acquire a data-transport system principally serving
users at brigade and below with applications at higher echelons.
The NTDR will support the Division and Corps XXI AWEs. The
system will have an open-hardware/software open-system-
architecture. An NTDR test bed will be established in the DIL/T for
inserting technology from such programs as SPEAKEASY.
Through technology insertion, the NTDR will ultimately provide
the full range of functions and capabilitiesrequired of the FDR.


4.2.2.2 Leave-Behind Phase.

The basic award for the NTDR will be for 200 to 400 radios to
support the Division XXI AWE and a subsequent leave-behind
phase. Prior to the AWE, the radios will be tested in the DIL/T,
Aberdeen (Maryland) Electronic Proving Grounds, and in a field
experiment to ensure readiness for the exercise. The tested
equipment will be installed and provided to the soldiers for training
nine months prior to the Division XXI AWE. To support the Corps
XXI AWE, an option for up to 950 additional units may be
exercised. Leave-behind ("yellow") funding for the NTDR has not
been identified.


4.2.2.3 Acquisition.

To support Force XXI, a build of 5,000 production NTDRs is
planned.


4.2.2.4 Concept of Operations.

The concept of operations for the TF XXI AWE is to equip a
portion of a brigade with the FDR BAA field models to form a
digital net. The goals of the experiment will be to determine how
effective the radio is in passing high-volume digital traffic through
a network in a battlefield situation. Specific issues that will be
addressed include the effective geographic coverage that can be
effected by the 15 radios without the use of dedicated repeaters;
maximum throughput, both point-to-point and over the network
fixed and OTM; the extent to which the system is TCP/IP
compliant; interoperability with MSE, EPLRS, and SINCGARS
through INCs and TMGs; how well the radio operates with various
hosts, including the various versions of appliqu?; and cosite
interference.


4.2.3 Wideband HF

The objective of the Wideband HF (WBHF) radio program is to
extend the Tactical Internet to the High Frequency (HF) band using
state of the art commercial off-the-shelf (COTS) packet technology
and inventoried HF communication equipment. For TF XXI, we
will demonstrate narrowband HF packet data communication at
2400 Baud into the Tactical Internet using AX.25 protocols
through Internet Protocol (IP) Tactical Multinet Gateways(TMGs).
IP datagrams will be exchanged over secure COTS HF radios using
UDP/IP protocols over AX.25 lower layer protocols. An
experimental IP-compliant file transfer protocol using Net Block
Transfer Protocol (NETBLT) constructs over UDP will be used to
take advantage of available serial tone HF modems for beyond line-
of -site (BLOS) extended range communications with forward
units. Figure 4.5 (Wideband HF) illustrates the baseline HF tactical
internet hardware configuration.

In later phases of the program, PM TRCS Internet Controller (INC)
hardware will be adapted with lower layer modifications to MIL-
STD-188-220( ) suitable for HF tactical internet communications.
The lower layer protocol modifications will be tested for IP
compliance on INC hardware and submitted through joint protocol
standards groups as a proposed standard for HF tactical Internet
communications.

The final phase of the program will exploit state-of-the-art
advances in wideband HF data communications to improve the
capacity for IP datagram transmission over HF channels.
Technology suitable for this phase has not yet been decided, but
will be based on continued market analysis and correspondence
with HF communication vendors.

The WBHF AWE demonstrations will provide a capability of
seamless transmitting warfighter information using internet
protocols to forward deployed units. Demonstrations in DIV XXI
AWE will introduce wideband technology and lower layer
protocols to inventory internet controller and tactical multinet
gateway technology. A milestone schedule for the WBHF program
is shown in Figure 4-6 (WBHF Milestone Summary).


4.2.3.1 Research and Development.

Each step in the three phase R&D effort will lead to the acquisition
of advanced data transmission devises resulting from product
improvements and modifications that evolved from the preceding
step. Laboratory testing in the CECOM DIL will lead to a
demonstration during the TF XXI AWE as well as follow-on DIV
and Corps AWEs.

Phase 1 will provide baseline hardware and AX.25 packet
controllers with TMGs. Contracts to purchase six WBHF radio sets
are scheduled for award during 1QFY96, with delivery at the end of
2QFY96. Testing in the DIL is scheduled to begin 2QFY 96. Two
units will remain at the DIL for ongoing test and evaluation, in both
a laboratory and field environment. The remaining four units will
be made available in 3QFY96 for the TF XXI AWE for which is
scheduled for the 2QFY97. The four WBHF radios that will be
delivered to the field in preparation for the TF XXI AWE will
include CECOM engineers installing the units and providing
training of the users. Issues such as field worthiness, mounting
installation kits, and protective hardware for the platforms in which
they will be mounted will be addressed at a later date. Funding
remaining after the procurement will be divided between
manpower, contractor support, spare parts to maintain the
equipment, and travel. This should include a field worthiness
determination, and installation documentation. A nominal two
week AWE training period, requiring two engineers, will take place
in the 4QFY96. Engineering support will include a two week
period to set up equipment prior to the exercise and two weeks of
support into the exercise. Two one week trips will be reserved for
"trouble calls", andrepair of equipment if required. Brief operating
instructions will also be made available at that time.

Phase 2 of this effort will consist of an evaluation of lower layer
protocols during which time AX.25 protocols will be replaced.
Protocol modifications will be made allowing the insertion of
Internet Controllers(INC) hardware and compliance with MIL-
STD-188-220( ). This task is not scheduled for insertion into TF
XXI but should be available to future AWEs such as DIV and
CORP XXI .

Phase 3 will exploit state-of-the-art advances in wideband HF data
communication. Wideband data communication equipment offers
the possibility to significantly improve the data throughput in a HF
system. The follow-on AWEs will offer an oportunity to evaluate
their suitability for Army utilization. Market analysis as well as
continuing correspondance with vendors indicate that wideband
radio equipment will be available that will offer orders of
magnitude improvements in the transmission of data over HF.
Issues related to spectrum availability, and performanceof the
candidates will be evaluated prior to the selection of a radio for
AWE evaluation. This technological insertion will be evaluated in
DIV and CORP XXI AWEs.


4.2.3.2 Leave-Behind Phase.

Following the TF XXI AWE the four WBHF radio will be left
behind for soldier evaluation in the field. Evaluation reports and
informal training documents will be made available assisting the
soldier in the continuing evaluation of WBHF technology.


4.2.3.3 Acquisition.

The acquisition plan is still under consideration.


4.2.3.4 Concept of Operation.

The Wideband radio(WBHF) is intended to demonstrate an
extension of range of communication services to highly mobile
forces. The HF radio will provide forces such as Long Range
Surveillance Units(LRSU) with access to the Tactical Internet using
state-of-the-art COTS technology. During Phase 1 we are planning
to use radios such as the IHFR or VRC 101( Harris RF500 series)
communication assets. We will demonstrate both base station to
base station communication. We will also deploy a Manpack HF
radio with a portable Laptop computer for NVIS access to the
Tactical Internet. The radios will use commercially available
antennas. The most significant aspect is to demonstrate BLOS data
transmission using a HF manpack radio ability to access the
Tactical Internet. Longer range goals for DIV and CORP XXI will
be demonstrations of enhansements to the basic system.
Enhansements are considered to be in the area of higher data
throughput.


4.2.4 Asynchronous Transfer Mode Technology Integration

The objective of the ATM technology integration program is to
support the insertion of ATM technology into the Army's tactical
wide-area communications system through a series of planned
product improvements (ultimately replacing MSE with the next-
generation switching system). ATM experiments conducted during
Unified Endeavor in April 1995 (see Figure 4-7 --> Undified
Endeavor Multi-Point VTC experiment) serve as the baseline for
this program. During Unified Endeavor, seven ATM switches were
installed in MSE shelters, enabling MSE voice traffic to be
combined with additional data traffic over the existing MSE
backbone network. The additional data traffic was used to support
collaborative planning and desktop video conferencing at four
deployed sites. Program milestones are illustrated in Figure 4-8
(ATM Technology Integration Program Milestone Summary).


4.2.4.1 Research and Development.

Emerging services and applications, including video, worldwide
web servers, and collaborative planning, are beginning to be used
on the battlefield. These types of services and applications are not
supported by the existing MSE system. ATM technology has the
potential to support these and other wideband services desired by
the warfighter. ATM technology, however, was designed for use in
low-bit-error-rate fiber-optic-based static networks. Effective use of
ATM technology in a tactical environment will therefore require
that a number of key areas be addressed. These include FEC, low-
rate survivable protocols, bandwidth allocation, signaling, and
wireless ATM. As the Army replaces its current limited-bandwidth
radios with new HCTRs, the full potential of ATM will be realized,
but additional areas will need to be addressed to make full use of
the ATM technology.

The ATM technology program consists of two phases. The first
phase will provide incremental improvements to the MSE system
within the existing bandwidth constraints. During this phase, a
number of areas will be investigated, and solutions will be
prototype and evaluated. The use of adaptive FEC based on
requested quality of service (QoS) parameters will be examined.
Different types of services have different QoS parameters, e.g.,
voice is more tolerant than compressed video to errors.
Consequently, the FEC method should be adaptive to use a less
restrictive code for voice. In addition, the network links should
have a feedback mechanism to determine whether to use FEC on
the link. This subtask will explore the possibility of modifying the
microcode within a switch to perform these functions.

Survivable protocols for use in a tactical environment will be
investigated. Tactical communications links are characterized by
low-data-rate high-bit-error-rate (BER) channels. To use ATM
effectively in a tactical environment, protocols are needed to
improve ATM cell recovery techniques and provide timing
information and framing synchronization. The work will use the
LANET protocol developed by IST as a starting point to investigate
survivable protocols.

The current MSE architecture uses time-division multiplexing
(TDM), which is an inefficient transmission method. Voice trunks
are allocated a fixed bandwidth, regardless of whether any calls are
in progress. The goal of this effort is to use part of the unused voice
circuits for other services. This will be accomplished by sensing
when the channel is active and only sending cells for the active
channels. This will require access to each of the subscriber loops
and a method for sensing when the channel is active. A portion of
the TDM bandwidth must be reserved to ensure that voice users are
not locked out of the network, but the rest of the bandwidth can be
used by other services. This effort will focus on sensing the TDM
channel and only producing cells for the active calls. Issues
involving flow control, signaling, and channel allocation will also
be examined in this task. The benefit of this effort is that it will
make more efficient use of available MSE bandwidth.

Q.2931 is the ITU-approved COTS signaling protocol for ATM
networks. As it was designed for use in static fixed-plant high-
bandwidth low-bit-error rate environments, its performance in
tactical ATM networks is unknown. Additionally, there appears to
be only limited and primitive support for multicast connections,
and no support for mobile users. This effort will assess by
qualitative analysis the functional capabilities of Q.2931 to support
users in the tactical environment. A detailed baseline-performance
characterization of Q.2931 for the tactical environment will be
developed. With the Q.2931 limitations thoroughly understood, a
protocol enhancement effort will be undertaken. It is anticipated
the tactical enhancements will ride on top of the commercial
Q.2931. Efforts will be undertaken to insert these enhancements
into the standards community.

ATM technology assumes the transport medium will be fiber-optic-
based with a BER > 10-12. In a tactical environment, the
transmission medium will be radio-based with a BER of < 10-6. In
addition, the network can be characterized as low-bandwidth,
typically < 1 Mbps, and highly mobile, with the topology of the
network changing frequently. The wireless ATM program will
experiment with ATM over different radios, including the Mobile
Subscriber Radiotelephone Terminal (MSRT) and Wireless
Network Access, to characterize the performance of ATM over
wireless point-to-point links. The program will examine issues
associated with cell synchronization, framing, BER, throughput,
and delay characteristics. The work will build on the experiment
done during Unified Endeavor, which interfaced ATM to the MSE
MSRT radios. This effort will be a direct feed for the Low Rate
Survivable Protocol effort.

The second phase of the ATM technology integration R&D
program will include the investigation of issues associated with the
introduction of high-bandwidth radios to the tactical battlefield. At
the end of this phase, a functional specification for a replacement
to the existing MSE system will be provided to PM JTACS for
fielding.

The objective of this effort is to map MSE subscribers to other
subscribers on the ATM network. Issues involving different voice
encoding schemes and signaling conversion between MSE
signaling and ATM signaling will be examined. The goal is to
provide full interoperability between MSE voice subscribers and
other subscribers on the ATM network.

The addition of the HCTR with its OC3 bandwidth provides
additional network bandwidth to support video and other wideband
services and/or provide enhanced survivability by allocating
network capacity to support user requirements. For example, if a
high-priority user required one Mbps between source and
destination, the network could, if required, allocate two
independent paths between source and destination to provide an
additional degreeof survivability. A more sophisticated approach
might allocate additional bandwidth through certain critical but
vulnerable areas. An even more sophisticated scheme might have
the network dynamically allocate additional end-to-end bandwidth
in response to both enemy threat and user requirements. It should
be noted that this approach involves more than simple routing (i.e.,
finding a path or paths from source to destination) it also requires a
global network-wide allocation algorithm due to the fundamental
nature of ATM. This effort willinvolve the identification and
investigation of additional allocation schemes.

A number of problems must be resolved before ATM technology
can be used in a mobile environment. These include dynamically
managing virtual path identifiers/virtual circuit identifiers as hosts
move and guaranteeing QoS as nodes move to different locations
within the network. The problem of how to guarantee tracking,
service, and connectivity to hosts or subscribers that move around
the network will be addressed.

Training will be provided to users during the R&D phase leading
up to the AWEs and during the leave-behind phase. Support will be
provided by CECOM and contractor personnel.


4.2.4.2 Leave-Behind Phase.

The strategy for the leave-behind phase includes providing the user
with ATM technology at the earliest opportunity, then
incrementally implementing additional capabilities through
technology insertion and system upgrades.

It is planned is to leave behind eleven ATM switches and six
workstations to be used as video teleconferencing (VTC) stations.
Five switches will be located at node centers (NCs), four at Fort
Hood and a fifth at Fort Carson, Colorado. Five switches will be
used to interconnect small extension nodes (SENs) at DMAIN,
division tactical (DTAC), the 1st brigade (1Bde), 2Bde (all located
at Fort Hood), and 3Bde (located at Fort Carson). The remaining
switch will be located at the large extension node (LEN) at division
rear (DREAR)/DISCOM. The system will allow the user to utilize
the full bandwidth of the MSE communications infrastructure.
During this phase, one of the links between NCs will be
implemented using a 10-Mbps trunk radio provided by the HCTR
program. Four low-rate ATM switches will be used to demonstrate
ATM over a wireless network to a mobile platform with a laptop
running a whiteboard application. Funding for the initial leave-
behind ("yellow") phase is expected to be provided by ADO during
FY-96.

The plan is to leave behind a corps slice of equipment. During this
phase, it is anticipated that an upgraded GRC-226 radio with a
higher data rate will be available. This will be accomplished by
leveraging work performed by the radio's manufacturer to produce a
circuit card that doubles the radio's bandwidth. The results of the
work performed in the areas of adaptive FEC, survivable protocols,
and the first part of the dynamic bandwidth effort will be inserted
into the existing equipment at Fort Hood. It is anticipated that the
changes will involve hardware/firmware and will be a modification
to the existing switches at division and corps.

Existing equipment will eventually be replaced with new equipment
incorporating the modifications to date. The maturation of the
technology and standards and the magnitude of the enhancements
will warrant the replacement of the existing equipment. VTC
workstations will be upgraded or replaced with Common
Hardware/Software II (CHS II) hardware. The new switches will
incorporate FEC, dynamic bandwidth, and support for ATM
signaling in the tactical environment. The FY99 leave-behind will
provide full ATM functionality, including ATM signaling,
survivable protocols, mobile hosts, security (based on NSA
products), network management, and interoperabiliy between MSE
voice subscribers and other network subscribers.


4.2.4.3 Acquisition.

A plan for acquiring ATM technology as an Army-wide upgrade to
MSE is being developed by PM JTACS.


4.2.4.4 Concept Of Operations.

ATM technology will be inserted into the MSE backbone to allow
simultaneous voice, data, and video communications services to
MSE subscribers. This technology will provide more-efficient use
of the available bandwidth of the MSE network. This increased
data capacity will provide the necessary bandwidth for new
warfighter capabilities and services on the battlefield. As part of the
leave-behind package, workstations with VTC hardware and
software will be installed for use at DMAIN, DTAC,
DREAR/DISOCM, 1 Bde, 2Bde (at Fort Hood), and 3Bde (Fort
Carson). During the R&D phase, a subset of equipment, four
switches and two workstations, will be used for demonstrations at
AWEs. The workstations will provide the capabilities of multipoint
video conferencing, interactive electronic whiteboarding for
collaborative planning, and accessing information on databases
located on the network. From an operational standpoint, the
network will increase the timeliness of information flow and
intelligence confirmation. Increased situation awareness, access to
the combat posture, intelligence dissemination and validation, and
distribution of the Commander's intent to subordinate commanders
for battle planning are real-time operational capabilities gained by
improving the MSE network with ATM technology and utilizing
the VTC systems. ATM is the enabling technology that allows
traditional voice subscribers and high-bandwidth data subscribers
to share the tactical bandwidth.

ATM technology will be demonstrated in conjunction with the
142nd Signal Battalion. MSE assets belonging to the 142nd will be
modified with ATM systems. The plan presently calls for
populating five node center switches, one LEN at
DREAR/DISCOM, and five SENs at DMAIN, DTAC, 1Bde, 2Bde,
and 3Bde with ATM switches. In addition, VTC workstations will
be installed and integrated at those command posts.


4.2.5 High-Capacity Trunk Radio

HCTR will be capable of a minimum data rate of 45 Mbps to
support ATM switching under dynamic battlefield conditions. The
HCTR will also help define appropriate technology for the next-
generation MSE LOS radio. As an integral part of the RAP, the
HCTR will also extend wideband integrated communications
services to highly mobile forces. Potential HCTR applications are
illustrated inFigure 4-10 (High-Capacity Trunk Radio Milestone
Summary).


4.2.5.1 Research and Development.

The HCTR program is a technology-based advanced-development
initiative to explore and develop technologies to support the
development of a wideband trunk radio with the capability of
operating OTM. The HCTR will be a part of the wide-area
backbone and mobile subsystems, such as the RAP, and be
compatible with local-area hubs and ATM switching.

The HCTR program will include the evaluation of a COTS
synchronous optical network (SONET)-based radio, starting with
the delivery of the radio in November 1996 and concluding with a
report in September 1995. The evaluation will be supported by
establishing a link between AT&T Bell Laboratories, Holmdel,
New Jersey, and the Albert J. Myer Center, Fort Monmouth.
Propagation and performance data will be collected using this link,
and the results will be used as part of a concurrent M&S effort. The
M&S effort will include realistic modeling of critically related
communications system elements, both channel and network, and
will play a major role in defining the design of the final OTM
system as well as potential enhancements to legacy radio systems.

Concurrent with the COTS SONET radio experiment and M&S
program, an accelerated procurement will be conducted to provide a
near-term wideband radio, HCTR(-), with a performance goal of
10Mbps and 20-km range for near-term ATM upgrades to MSE. A
number of candidates will be identified during 4QFY95 from a
market survey that has been completed. The selection of the radio
will be supported by detailed analysis in the CECOM DIL/T of
candidate radios on loan from the manufacturers. BCBL(G), Signal
Center Directorate of Combat Development, and PEO C3S will
participate with CECOM in the evaluation process. Bandwidth,
range, cost, antenna suitability, interface compatibility, frequency
allocation, and ruggedness for a military environment are primary
considerations in the selection process. An in-process review will
be conducted in February 1996 to assess the experimental data and
select the HCTR (-). Contract award is targeted for May 1996 with
the delivery of four units early in January 1997. Considerable
testing will be carried out in the DIL/T to establish efficient links
with the ATM test bed before delivery and installation of the
HCTR(-) at Fort Hood in May 1997 in preparation for the Division
XXI AWE.

CECOM will provide training and field support for the four
HCTR(-)s during the Division XXI AWE. The radios will be
temporarily installed alongside the present AN/GRC-226 radios in
the MSE LOS shelters. Two CECOM engineers will accompany
the equipment for a period of two weeks during the installation and
training period. Two one-week trips for two engineers on-site
during the nine-month training for the AWE will also be provided.
The same level of support will be provided during the month-long
Division XXI AWE in February 1998.

Development of a tactical objective HCTR capable of providing
155-Mbps operation in a static or stationary mode and 45 Mbps in
an OTM mode will begin in November 1996. Data from the COTS
radio experiments and M&S effort will provide the foundation for
the development. Initial deliverables of the objective HCTR will be
required to operate in the static mode and will be available for
DIL/T testing and for the Corps XXI AWE, with delivery in May
1998. One stationary HCTR will be integrated with the RAP, with
the remaining three used to increase the capacity of MSE links.
These radios will utilize stationary parabolic-dish antennas. The
training and field support provided for the Corps XXI AWE will be
as described for the Division XXI AWE.

Four OTM HCTRs will be delivered early in 1QFY99 with a full
OTM capability to support mobile RAP operations. These radios
will undergo extensive testing in the DIL/T prior to integration with
the RAP. Two of these HCTRs will be integrated with RAPs for
demonstration at JWID '99. One of these OTM radios will utilize
an OTM antenna developed under the phased-array antenna
program. An alternative antenna (investigated as part of the HCTR
development) will be provided as an expedient solution for use at
the other OTM RAP node. The other two OTM radios will be used
at ATM-equipped stationary nodes for connectivity with the OTM
RAPs. After an initial demonstration, these OTM radios will be an
integral part of the RAP for future AWEs.


4.2.5.2 Leave-Behind Phase.

Four HCTR(-) radios will be demonstrated in the Division XXI
AWE in February 1998. Upon completion of this exercise, a
decision will be made as to whether leave-behind radios are desired
by the user. If so, the radios will be procured, and installation and
training will be conducted. These units will be left with an
operational ATM-equipped MSE unit to provide wideband trunk
connectivity between ATM switches. These radios will be installed
in MSE LOS shelters in place of a to-be-determined number of
AN/GRC-226 radios.

Four static HCTRs will be available in March 1998 for
participation in the Corps XXI AWE. Training and familiarization
for the AWE will be provided with radios acquired during the R&D
phase. On completion of the AWE, a decision to proceed with the
fabrication and installation of an additional (unfunded) four units
for leave-behind with an ATM/RAP-equipped MSE unit will be
made.

A decision to fund four additional HCTRs with OTM capability
will be based on test results from the Corps XXI AWE (static
operation) and testing of the OTM radios in the DIL/T. Antennas
will be provided as part of the OTM antenna program leave-behind
package.

Training and logistics packages for the static and OTM radios will
be provided as the radios become available. Contractor support is
anticipated for both training and repair/spare parts as required.
Funding for the leave-behind ("yellow") phase has not been
identified.


4.2.5.3 Acquisition.

The acquisition strategy for the HCTR will be developed as the
requirements process an HCTR located in division HQ and another
within the Joint Task Force. This link will used in conjuction with
an airborne relay and OTM antenna to assist in the rapid
establishment of the link to the moving airborne platform(even
though the ground terminal will be stationary).

4.2.6 Terrestrial Personal Communications Systems

The objective of the Terrestrial PCS program is to investigate the
feasibility and benefits of using emerging commercial cellular/PCS
technology as an enhancement to the Army's MSE. Figure 4-11
(Terrestrial PCS) illustrates a potential application as an upgrade or
supplement to the Radio Access Unit (RAU).

Figure 4-12 (Terrestrial PCS Milestone Summary) provides a
milestone chart for the terrestrial PCS efforts.


4.2.6.1 Research and Development.

R&D performed in the area of terrestrial PCS is a cooperative
effort between the ARPA-funded C2T2 program and the CECOM
C2TL program. PCS technology developed under these programs
will be demonstrated during the TF and Division XXI AWEs.

The C2T2 program performed a market survey in FY93 to identify
available PCS technology for dismounted infantry. Since no PCS
technology was mature at that time, the Ericsson trunked Land
Mobile Radio (LMR) system was identified and selected as the
first system to be evaluated. This system provides intermixed digital
voice and data transmission over multiple 9,600-baud half-duplex
channels. Handheld Personal Digital Assistants and generic laptop
486 computers are interconnected via this system. Global
Positioning System (GPS) receivers and heads-up displays are also
integrated with the computing devices. The hardware, software, and
a gateway to the Battalion and Below Command and Control
(B2C2) system will be tested during the Warrior Focus AWE. This
hardware will become available at the conclusion of Warrior Focus
and will serve as the baseline hardware for use during the TF XXI
AWE. The hardware includes one 12-channel base station and
approximately 50 handheld radios. These assets will be refurbished
and additional high-power vehicular-mount units will be purchased.

A number of enhancements to the LMR have already been
identified as a result of Warrior Focus training, and it is expected
that more will be identified by the end of the exercise. Some of the
enhancements that can be explored under the R&D phase include
improved data protocol, base station ruggedization, and a more
robust waveform. Execution of these and any other enhancements is
dependent on continued ARPA funding of LMR technology. If the
enhancements are agreed upon and are not too extensive, the
enhanced LMR will be used for the TF XXI AWE. The hardware
will consist of one base station and 50 user radios. These units will
be delivered in April 1996 for evaluation in the CECOM DIL/T and
will be delivered for the exercise in May 1996.

The definition of the C2T2 second-phase system, identified as
Hybrid PCS, is in progress. It is expected that the second system
will have smaller (transportable) base stations, better hand-off and
peer forwarding, more users per channel, higher data rates, better
scalability, and lower transmit power. A prime candidate for this
system is broadband code-division multiple access (B-CDMA)
technology, currently being explored under the C2T2 program. The
R&D phase will result in two base stations and 50 handheld
terminals for the Division XXI AWE. This hardware will be
delivered in February 1997 for DIL/T testing and will then be
delivered in May 1997 for installation and training for the AWE.

A key piece of the demonstrations for the TF XXI and Division
XXI AWEs is the interface to MSE. These interfaces will be
developed under the DBC ATD. The LMR system and the B-
CDMA system currently being tested have an interface to the
public switched telephone network (PSTN). This interface is a two-
wire analog plain-old telephone service (POTS) interface. The only
existing POTS interfaces for MSE are two central office lines that
require operator intervention. To provide a useful demonstration of
the LMR for the TF XXI AWE, the interface to MSE must be
seamless. In the simplest sense, this interface will look like a
Digital Nonsecure Voice Terminal (DNVT) to MSE and a POTS
telephone line to the LMR system attached. The interface will be
replicated for the number of users the base station will support.
One of these MSE interfaces will be supplied to support the LMR
or Enhanced LMR (ELMR) system and one spare. This R&D effort
will deliver the interface for DIL/T evaluation in April 1996 and TF
XXI training and installation in May 1996.

The Hybrid PCS system will require a more complex interface to
MSE, which might have to be at the trunk level. This interface will
be the main thrust of the R&D effort to prepare the Hybrid PCS
system for the Division XXI AWE. In support of the interface
development, a number of options will be explored. These include
modification of commercial mobile telephone switching offices or
the purchase/lease of a GTE Switch Multiplex Unit. This R&D
effort will deliver two copies of the interface for DIL/T evaluation
in February 1997 and Division XXI training and installation in
May 1997.

A tactical feasibility study was proposed in June 1995 to examine
the extent to which the Army can exploit and leverage emerging
digital cellular and PCS technology. The ability of this technology
to support the increased demand for information flow on the fluid
tactical battlefield will be determined. The overriding issue is
whether the commercial cellular infrastructure can be extended into
the mobile forward areas of the battlefield through careful planned
adaptation of commercial investments in low-power handset
technology, spread-spectrum transceiver chip sets, and
miniaturization of cell site/switching technology enabling
transportable or mobile operations. Areas of investigation in the
study include cell size, alternative frequency bands, adapting
commercial technology to military frequency bands, tactical "back-
haul" communications links, mobile cell sites, range extension for
cellular subscribers, and vulnerability/security.
Engineering/installation/training support for the LMR/ELMR for
TF XXI will include installation of an LMR base station in a
tactical vehicle, installation of an MSE interface at an MSE switch,
installation of vehicular mount units in tactical vehicles, classroom
and field training, and technical support. Two CECOM engineers
will accompany the equipment during the installation and training
period, which will take two weeks. During the nine-month training
period, two engineers will be provided for two one-week on-site
visits. This same level of support will be given during the one
month TF XXI AWE and for the Hybrid PCS system for the
Division XXI AWE.


4.2.6.2 Leave-Behind Phase.

The leave-behind package for LMR/ELMR will consist of two to
three base stations and 200 handheld radios. The leave-behind
package for the Hybrid PCS will consist of an additional two to
three base stations and 200 handheld radios. The leave-behind
package for the MSE interface will include four MSE/LMR
interfaces. Funding for the leave-behind ("yellow") phase has not
been identified.


4.2.6.3 Acquisition.

PEO COMM has identified PCS as a candidate for technology
insertion under its ACUS SIP. Military adaptation is foreseen, with
ACUS utilizing commercial technology for tactical users as quickly
as economically feasible. Any combination of these systems and
their interfaces may be selected for acquisition.


4.2.6.4 Concept of Operations.

The LMR/ELMR systems will be used as a RAU/MSRT
replacement. The LMR base station will be housed in one or two
MSE shelters. Two versions of the user terminal will be available, a
low-power handheld unit and a higher-power vehicular-mounted
unit.

Since the Hybrid PCS system will have hand-off and peer-
forwarding capability, its concept of operations can be flexible. It
can be used as a RAU replacement or to provide new capabilities.
One concept could be in a DMAIN area to provide wireless voice
and data service to subscribers who are normally hard-wired. It
could also be used at lower echelons. The limiting factor is access
to MSE.

The MSE interface for the LMR/ELMR system will be located in a
SEN switch shelter. The Hybrid PCS MSE interface will be in its
own shelter and will be deployed near a LEN or a SEN.


4.2.7 Army Direct Broadcast Satellite

The Direct Broadcast Satellite (DBS) program will investigate a
wideband communications system using commercial technology for
battlefield data dissemination (see Figure 4-13 --> Direct Broadcast
Satellite).

Program milestones are illustrated in Figure 4-14.


4.2.7.1 Research and Development.

American DBS systems offer the potential for low-cost wideband
data and video dissemination. Unfortunately, these systems are
geographically limited to CONUS, designed specifically for the
home user, use commercial frequency bands, and are near capacity.
The DBS program, in coordination with the Joint Global
Broadcasting System (GBS), will develop an Army DBS system
providing the flexibility required to support operations while
maximizing the benefit of low-cost commercial developments.

Three commercial DBS terminals will be acquired, modified to
work with standard Ku-band antennas, and integrated with Sun
workstations. These terminals will initially be used in JWID '95 to
support Common Ground Station (CGS) data dissemination, after
which they will be used to support continued development and
AWEs beginning with TF XXI. An uplink capability will be
provided for use during TF XXI which will use a standard Ku band
transmitter/antenna. This will provide an end-to-end capability for
the TF XXI AWE and subsequent demonstrations. The segregation
of the terminal and RF portions of these systems will support
future band changes. Additionally the downlink segments will be
made fieldworthy, including migration to CHS II.

A DBS programming center will be developed/acquired to
consolidate, schedule, and control data/video dissemination. This
will be used to support the Corps XXI AWE.

An airborne DBS transponder will be developed to provide and
demonstrate a global capability for in-theater data dissemination
under direct control of the theater commander. While the ideal
platform is the TIER II+ UAV, the goal is to develop a system that
is platform-independent. Thus, a limited capability can be available
for the Division XXI demonstrations and subsequent applications
sooner than the expected TIER II+ production start date of 2002.

An effort to develop a system to receive DBS data on a moving
platform will focus on antenna subsystems development. Current
plans are to develop and produce a single unit for demonstration at
the Corps XXI AWE.

Training and support functions will include initial training and
engineering support, including sparing or support agreements, for
the TF XXI AWE. It is assumed that satellite time required to
conduct TF XXI will be provided. It is anticipated that support to
the Division XXI AWE in FY98 will be conducted in conjunction
with the Airborne Relay program.


4.2.7.2 Leave-Behind Phase.

Each DBS development effort supports an AWE leave-behind
phase. Preparation for the leave-behind phases should begin by late
FY96 for the uplink/downlink elements and late FY97 for the
remainder. This preparation includes the drafting of planning and
acquisition documents. Estimates for leave-behind based on inputs
received from BCBL(G) include a single uplink and eight downlink
terminals.

Based on initial discussions with BCBL(G) and Joint Program
Office UAV, it is assumed that UAV or manned aircraft support
will be available during the leave-behind phase. Funding for the
leave-behind ('Yellow") phase has not been identified.


4.2.7.3 Acquisition.

As an unfunded new capability, it is critical that this project be
supported by validated requirements documentation. The GBS
program is expected to be a joint program, for which joint
requirements are already under development.On the assumption
that such documentation is present, and funding is identified, the
acquisition phase can begin no earlier than FY99, with the
completion of a data package and the start of the contracting
process. If the contracting process is very simple (very few
contractors), a contract could be awarded in early FY00 with
fielding beginning in FY01. If there are complications in the
process, contract award and fielding will slip to FY01 and FY02,
respectively.

Estimates for equipping a single corps are based on 40 downlink
terminals and 20 OTM units. Additional corps equipment consists
of two uplinks with programming centers.


4.2.7.4 Concept of Operations.

DBS can greatly improve the timeliness and quality of information
for tactical users and is particularly well-suited to graphical
information, including live video. Consequently, the initial focus of
experiments should be current users of this form of data. A typical
implementation may consist of data from an MI company being
broadcast as a continuous data stream to several divisional users,
both mobile and stationary. Thus DTAC, DTOC and DREAR can
simultaneously receive current data including situation reports,
weather, and UAV video. BCBL (G) has indicated that a minimal
configuration for the TF XXI AWE will require one uplink and six
downlink terminals, one at brigade, one at battalion, and four at
company level. An alternative configuration would be to place one
at brigade, two at battalion, and three at company level. To meet
this requirement, alternative arrangements for the use of three
additional receive terminals are being explored. UAV-based DBS
transponders will be part of the UAV communications suite under
the control of the corps signal brigade. The UAV payload will
provide a flexible means of providing DBS services under local
control.


4.2.8 Radio Access Point

The RAP will seamlessly extend wideband trunks from the tactical
point-to-point backbone to lower echelons (brigade and below)
with support for integrated voice, data, and video access to/from
users located on highly mobile (tank, helicopter, etc.) platforms, as
well as to the individual soldier (See Figure 4-15 --> Radio Access
Point). The RAP relies on four components: ATM, HCTR, airborne
relay, and OTM antenna.

Milestones for the RAP are illustrated in Figure 4-16.


4.2.8.1 Research and Development.

By using the results of other DBC efforts and commercial products,
this program will implement a phased approach of developing and
demonstrating a RAP capability. This will include
developing/acquiring and integrating the required interfaces,
developing protocols/software for execution/management, and
assembling the system hardware. The process begins with
developing a high-level system document/specification. The
specification phase will conclude with a detailed functional and
performance specification for the RAP. The functional
specification will emphasize mobility requirements, including
support for mobile hosts and subscribers, automatic
reconfiguration, and automatic recovery from failed nodes/links.
The first-year effort will include a high-level system design,
identifying main components, and will produce a detailed design
for system elements requiring adaptation/development.

A laboratory RAP prototype phase (RAP V1) will be integrated
into DIL to demonstrate connectivity in a static laboratory
environment. The data rate of the initial wideband trunk will be a
maximum of T1. Connectivity will be demonstrated with MSE TPN
and EPLRS. The baseline RAP, consisting of dismounted COTS
hardware and software, will be characterized from both a functional
and performance standpoint.

RAP V2 will demonstrate a mobile RAP host in a laboratory
environment, integrating mobile IP over a low-to-medium (2.4 kbps
to 56 kbps) data-rate channel to provide survivable connectivity and
dynamic configuration. The effort will show support for mobile
hosts, using the commercial Internet Engineering Task Force
protocol or military protocols, as appropriate. The characterization
will include both mobile net entry and hand-off capability, similar
to that in the commercial cellular world. Equipment will be COTS.
Demonstration will be performed using the DIL/T at Fort
Monmouth and a remote site laboratory (ATT Holmdel or Evans
area).

A static RAP field demonstration will demonstrate connectivity to
both the narrowband tactical systems and to strategic and tactical
ATM-based networks. HCTR linkage will be to static HCTR/ATM,
as only one RAP will be available. Interoperability will be tested
for both functionality and performance. OTM operations will not
be possible prior to the availability of an OTM version of the
HCTR. M&S will be used to study scalability and wide-area
mobility.

The RAP field demonstration will be performed using one RAP,
and is planned for the Corps XXI AWE. The field demonstration
RAP will incorporate a static version of the HCTR radio provided
by the HCTR program.

A mobile RAP relies on an OTM antenna to provide HCTR
connectivity to LOS or UAV relay. An OTM phased-array antenna
will be integrated to allow the RAP to establish and track linkages
while OTM. If the OTM antenna is not available (or is needed to
construct the mobile RAP demonstration unit), a standard dish
antenna will be used. The RAP prototype used for this
demonstration will utilize government-furnished equipment (GFE)
for connectivity to the narrowband subscribers. Cost considerations
preclude the RAP used for this demonstration being mounted in a
tracked vehicle or being capable of demanding off-road operation.
SPEAKEASY Phase II hardware will be integrated if available.

A mobile RAP demonstration will demonstrate OTM
communications with HCTR links to an ATM network and fully
integrated network management within a field environment. This is
planned for JWID '99. Only one mobile RAP is currently projected
for this demonstration, based on cost and the projected availability
of only one OTM antenna, but a demonstration of more than one
would enable demonstration/user feedback on a fuller range of
RAP capabilities. One possibility is to return with the static RAP,
with upgraded (mobile) HCTR, to increase possible network
demonstration scenarios.

The concept of the demonstration is for the static RAP to be
available for the Corps AWE. As such, it would be provided nine
months prior to the AWE, with two weeks training and engineering
support provided following delivery, an additional two weeks of
engineering support associated with AWE setup, and an additional
two weeks engineering support for the exercise. Two additional
trips of one week each are planned during the nine-month training
period. Repair parts and logistic support are planned for the AWE.
Operational manuals will be somewhat less than normal training
documents, but will provide operating instructions/checklist with
as much supporting information as can be assembled. The mobile
RAP will be providedfor JWID '99. No nine-month training cycle is
planned. However,it is planned that the mobile RAP will be
delivered approximatelyone month prior to the beginning of the
JWID, and that two weeks assistance will be provided for setup and
orientation/training with on-site personnel returning for three
weeks during the JWID.

The RAP project will incorporate equipment appropriate to each
demonstration in a shelter or vehicle. The ultimate objective is for a
tactical tracked vehicle; however, for the demonstrations described
here cost considerations will likely result in the use of a vehicle not
suitable for realistic tactical envirnments.


4.2.8.2 Leave-Behind Phase.

Six RAPs will be provided, two for the static RAP in FY99 and
four for the Mobile RAP field demonstration in FY00.

Equipment provided from other production and R&D programs
(ATM, HCTR, SINCGARS, OTM antenna program, EPLRS, MSE
MSRT, etc.) will be integrated and networked to provide a RAP
capability that can be demonstrated, managed, and evaluated as a
basis for a production phase. The costing figures include purchase
cost for vehicle/shelter, all internal racking and cabling, ATM
switch, and a workstation. Costing does not include the HCTR,
OTM antenna, SINCGARS, EPLRS, and MSRT units, which are
costed in other R&D lines or GFE. Funding for the leave-behind
("yellow") phase has not been identified.


4.2.8.3Acquisition.

The acquisition plan for the RAP has yet to be determined.


4.2.8.4 Concept of Operations.

The RAP is a vehicular-mounted self-contained communications
center that contains an ATM switch, an HCTR, an OTM antenna, a
controlling workstation, and interfacing/equipment for narrowband
tactical systems such as SINCGARS, EPLRS, NTDR, MSRTs, and
others as they become available. The RAP allows the mobile
narrowband tactical users to access wide bandwidth networks for
voice, data, and video communications.

The RAP will provide access to selected narrowband users to the
wideband ATM network via an HCTR. Range extension between
the RAP and wide area will be provided by UAVs. The RAP has
the capability to be used in a concentrated network of multiple
RAPs and/or multiple RAPs with a more traditional MSE-like
backbone, as a "skip echelon" or "skip geography" extension to the
rear. The functionality of the RAP is analogous to that of a mobile
survivable base station in the PCS cellular concept. Commercial
PCS technology will be utilized to the maximum extent feasible
and practicable in the RAP development.

The concept of operations for the Corps XXI AWE and JWID '99
are more limited because of the limited quantity of RAPs. For the
Corps XXI AWE, one static RAP will be provided. It is expected
that this will operate in the forward area of one brigade, and that
connectivity will be provided via HCTR to an ATM switch further
to the rear. The gateway to the MSE/TRI-TAC/strategic networks
mwill be provided by the ATM switch. For the JWID '99
demonstration, the concept is similar except that the RAP itself
will operate OTM.


4.2.9 Phased-Array Communications Antenna

The Phased-Array Communications Antenna program will develop
a wideband communications OTM antenna to support RAP HCTR
communications. The antenna must be capable of operating in line-
of-sight (LOS) mode and via an airborne relay (See Figure 4-17 -->
Phased-Array Communications Antenna).

Milestones for the Phased-Array Antenna program illustrated in
Figure 4-18.


4.2.9.1 Research and Development.

Phased-array antennas are generally lower in profile and more agile
than reflectors. There are, however, technical limitations that
impact their effectiveness, particularly at low- and varying-look
angles. The RAP antenna program will address these concerns by
developing an OTM capability for the CGS antenna and adapting
that technology to support the HCTR.

An OTM CGS antenna will be developed, with a static CGS
demonstration scheduled for JWID '95 and an OTM demonstration
scheduled for FY96. The major challenge is in developing the
antenna control software for OTM operation.

An analysis is being conducted by Lincoln Laboratories to derive
technical performance criteria for the RAP antenna. This study will
be used to support comparative analyses, design, and specification
development.

A reenginering phase will apply the CGS antenna technology to
HCTR communications. It will develop a complete prototype
antenna consisting of the arrays and controlling software.

All-inclusive bench testing and integration will include hardware
(from individual elements to entire panels) and software and will
culminate with integrating and testing on a vehicle. This will
produce a single antenna subsystem for demonstrations with a RAP
during the DIV XXI AWE.

It is planned to support these functions as part of the overall RAP
training and support package.


4.2.9.2 Leave-Behind Phase.

Four antennas will be required. Funding for the leave-behind
("yellow") phase has not been identified.


4.2.9.3 Acquisition.

Phased-array antenna acquisition has yet to be determined.


4.2.9.4 Concept of Operations.

The phased-array antenna will be deployed as an integral element
of the RAP. It will allow the RAP-mounted HCTR to communicate
in LOS mode or beyond-LOS mode via an airborne relay.


4.2.10 Satellite Personal Communications Systems

Satellite PCS will allow the Army to leverage and exploit emerging
commercial satellite based systems to develop an autonomous
battlefield personal communications capability (see Figure 4-19 -->
Satellite Personal Communications System). This will include
development of a UAV-based system, universal handsets, and a
military gateway.

Milestones for satellite PCS are illustrated in Figure 4-20.


4.2.10.1 Research and Development.

Satellite PCS are planned to provide worldwide communications
via networks of low-earth orbiters using handheld units. Systems
are expected to support voice communications, facsimile, data
transmission, and paging. Candidate emerging systems include
Iridium (Motorola), Globalstar (Loral/Qualcom), Odyssey (TRW),
Orbcomm, and Ellipsat (Ellipso). Most systems will utilize L-band
and S-band frequencies and code-division multiple access or time-
division multiple access.

System definition will include developing and evaluating Army
PCS concepts and continuing to monitor PCS candidate systems.
An initial PCS study of projected architectures, their evolution, and
Army applications of a universal gateway is forthcoming. The
current strategy is to create memoranda of agreements with industry
for sharing ideas and technology. System definition will determine
the feasibility (technical and legal) of handsets with multiple PCS
receivers and investigate the means of obtaining commercial PCS
handsets.

Establishing MOAs with industry is critical to demonstration and
testing PCS technology. Loral, Motorola, ORBCON, and ELIPSO
have shown interest in developing military satellite PCS
capabilities. The current schedule and target goals of a universal
handset and military gateway are aggressive and near-term
developments with industry toward sharing ideas and leased or
loaned equipment will enable the Army to determine feasibility. It
is important to demonstrate these future capabilities with airborne
platforms to obtain critical feedback from the user. This will
provide a method for gauging military exploitation of PCS
capabilities.

It is anticipated that cooperative DoD/contractor demonstrations of
UAV-based PCS will be extended for use during AWEs leading to
the acquisition of a leave-behind capability. Although it is too early
to finalize plans, a single UAV-based satellite PCS payload with
up to 25 handsets is expected to be available for the Division XXI
AWE.

A universal PCS handset effort will develop, test, and demonstrate
a ruggedized handheld unit capable of communicating via multiple
service providers. Potential applications include voice, facsimile,
data, and paging. Agreements with all service providers will be
necessary to implement and use this equipment.

Development of a national military gateway will provide links
between multiple providers and the PSTN. When used in
conjunction with a universal handset, the overall robustness of the
system will be increased through multiple paths via different
satellite systems. The gateway will also support the possible
implementation of a ground-based anti-jam capability. A key issue
to be resolved is the military/commercial interface for coordinating
resource access and allocation. The viability of the gateway hinges
on which satellite systems survive financially and functionally.

Training and support functions will include initial training
provision of two UAV payloads with antennas, 100 commercial
handsets, and a commercial base station and installation.


4.2.10.2 Leave-Behind Phase.

Planning for this phase begins in early FY97 with stay-behind
acquisition scheduled to commence in FY98. Costs and quantities
are based on provision of two UAV payloads with antennas, 100
commercial handsets, and a commercial base station and
installation.

Ongoing contractor engineering support is required as are non-
recurring engineering costs. Costs are based on a contractor-
provided rough-order-of-magnitude estimate. Leave-behind costs
for the universal handsets (FY99) are based on 100 handsets. A
single leave-behind military gateway is projected for FY00.
Funding for the leave-behind ("yellow") phase has not been
identified.


4.2.10.3 Acquisition.

As an unfunded new capability, it is critical that this project be
supported by validated requirements documentation. On the
assumption that such documentation is present and funding is
identified, the acquisition phase can begin during the leave-behind
phase in FY98, with the completion of a data package and the start
of the contracting process. If the contracting process is very simple
(single vendor), a contract could be awarded in early FY99. It is
possible, however, that the contract cannot be awarded until FY00,
with fielding beginning in FY01.


4.2.10.4 Concept of Operations.

The PCS UAV payload will be part of the UAV communications
suite operated by the corps signal brigade. Demonstrations and
trials will be conducted using PCS handsets at all echelons to
determine the overall utility of the technology.


4.2.11 Airborne RelayAirborne Relay

This program will develop a wideband point-to-point airborne relay
to provide in-theater extended-range communications (see Figure 4-
21 --> Airborne Relays) for the RAP/HCTR system and as a
platform for DBS and satellite PCs.

Program milestones are illustrated in Figure 4-22.


4.2.11.1 Research and Development.

Extended-range communications are currently heavily dependent on
satellite links and terrestrial networks. Recent experiences have
highlighted limitations in both approaches that will worsen with
the increasing demand for wideband battlefield communications.
This project will develop an airborne relay capability, providing
wideband communications range extension. This project supports
the HCTR, RAP, DBS, and satellite PCS programs.

Program definition/agreements will develop a strategy for
developing and demonstrating the Airborne Relay. A key part of the
process is completing memorandums of agreements (MOAs) with
UAV program offices at PEO Cruise Missiles and UAVs (Joint)
and ARPA. These agreements are essential to UAV availability for
integration, testing, and demonstration.

The next R&D phase will develop/test and demonstrate an airborne
relay capable of supporting 45-Mbps communications. This will
support initial RAP/HCTR demonstration and form the basis for a
higher-capacity relay. A single relay will be available for
demonstration during the DIV XXI AWE but will probably not be
needed until CORPS XXI.

Subsequent phases will build on the 45-Mbps relay to develop an
airborne relay capable of supporting 155-Mbps communications
and will test and demonstrate the higher-data-rate relay. It is
intended that this will be an upgrade to the 45-Mbps relay and not
directly support an AWE. If possible, however, the demo unit will
be made available to the EXFOR for demonstrations/trials. As one
of several UAV-based communications packages, it is assumed that
UAV costs will be covered or minimized by agreements.


4.2.11.2 Leave-Behind Phase.

This phase will begin in FY98 with the drafting of planning and
acquisition documents, with leave-behind acquisition beginning in
FY99. Costing is based on the assumption that 4hrs/day operation
is adequate to support demonstrations/exercises. This can be done
using a single UAV payload with a second as spare.

All UAV-related cost estimates (See Appendix A) are based on the
assumption that an MOA is completed for ongoing Joint Program
Office UAV support. It is possible that much of the UAV operating
and personnel cost can be shared with other applications. Funding
for the leave-behind ("yellow") phase has not been identified.


4.2.11.3 Acquisition.

As an unfunded new capability, it is critical that this project be
supported by validated requirements documentation. On the
assumption that such documentation is present and funding is
identified, the acquisition phase can begin during the leave-behind
phase in FY00, with the completion of a data package and the start
of the contracting process. A contract award is not likely prior to
FY02, with fielding begining in FY03.


4.2.11.4 Concept of Operations.

The wideband airborne relay will be part of the suite of UAV
communications payloads operated by the corps signal brigade. Its
primary purpose will be providing extended-range communications
between either mobile or stationary HCTRs and as a surrogate
satellite for DBS and satellite PCS payloads. Opportunities to use
the relay in support of other functions will also be investigated.

------------------------------------------------------------------------

ACRONYMS AND ABBREVIATIONS

ACT II Advanced Concepts and Technology Program
ACUS Area Common User System
ADM advanced developmental model
ADMP Army Digitization Master Plan
ADO Army Digitization Office
AMSAA Army Materiel Systems Analysis Activity
ARPA Advanced Research Projects Agency
ATD advanced technology demonstration
ATDP advanced technology demonstration plan
ATM asynchronous transfer mode
AWE advanced warfighting experiment
B-CDMA broadband code-division multiple access
B-ISDN broadband ISDN
B2C2 Battalion and Below Command and Control
BAA broad agency announcement
BCBL(G) Battle Command Battle Lab (Fort Gordon)
BER bit error rate
BIS 21 Battlefield Information System 21
BITS Battlefield Information Transmission System
BLWE Battle Lab warfighting experiment
BOS battlefield operating system
C2 command and control
C2T2 Commercial Communications Technology Test
Bed
C2TL Commercial Communications Communications
Technology Laboratory
C3S Command, Control and Communications
Systems
C4I command, control, communications, computers
and intelligence
CCS Command and Control Systems (PEO)
CDMA code-division multiple access
CECOM Communications-Electronics Command (U.S.
Army)
CGS Common Ground Station
CHS Common Hardware/Software
CO commanding officer
CONUS continental United States
COTS commercial off-the-shelf
CRDA cooperative research and development agreement
DBC Digital Battlefield Communications
DCD Directorate of Combat Development
DISCOM division support command
DIL/T Digital Integration Laboratory/Test Bed
DISC4 Director of Information Systems for Command,
Control,
Communications and Computers
DISN Defense Information Switched Network
DMAIN division main
DNVT Digital Nonsecure Voice Terminal division rear
ELMR Enhanced Land Mobile Radio
EPLRS Enhanced Position Location Reporting System
EW electronic warfare
EXFOR extended force
FBCB2 Force XXI Battle Command for Battalion and
Below
FDR Future Digital Radio
FEC forward error correction
FSED full-scale engineering development
FY fiscal year
GBS Global Broadcasting System
GFE government-furnished equipment
GPS Global Positioning System
HCTR High-Capacity Trunk Radio
HQ headquarters
INFOSEC information security
IP Internet Protocol
ISDN integrated services digital network
ISYSCON Integrated System Control
ITU International Telecommunications Union
JADE Joint Advanced Demonstration Environment
JRTC Joint Readiness Training Center
JTACS Joint Tactical Area Communications Systems
LEN Large Extension Node
LMR Land Mobile Radio
LOS line of sight
LRIP low rate initial production
M&S modeling and simulation
MBMMR Multiband Multimode Radio
Mbps megabits per second
MI military intelligence
MLS multilevel security
MOA memorandum of agreement
MSE Mobile Subscriber Equipment
MSRT Mobile Subscriber Radiotelephone Terminal
N-ISDN narrowband ISDN
NC Node Center
NDI nondevelopmental item
NRaD Naval Command, Control and Ocean
Surveillance
Center Research, Development, Test and
Evaluation Division
NSA National Security Agency
NTDR Near-Term Digital Radio
OCR operational capability requirements
OPTEC Operational Test and Evaluation Command (U.S.
Army)
OTM on the move
PCS Personal Communications Systems
PEO program executive office®
PM project manager
POC proof of concept
POM program objective memorandum
POTS plain old telephone service
PSTN public switched telephone network
QoS quality of service
R&D research and development
RAP Radio Access Point
RAU Radio Access Unit
RDEC Research, Development and Engineering Center
RF Radio Frequency
S&TCD Space & Terrestrial Communications Directorate
SARDA Secretary of the Army, Research, Development
and Acquisition
SEN Small Extension Node
SINCGARS Single-Channel Ground and Airborne Radio
System
SIP system improvement program
SONET synchronous optical network
SPM system performance model
STO science and technology objectives
T&M time and materials
TCP Transmission Control Protocol
TDM time-division multiplexing
TEED Tactical End-to-End Encryption Device
TF XXI Task Force XXI
TI Tactical Internet
TISM TEED Internet Security Manager
TPN Tactical Packet Network
TRADOC Training and Doctrine Command (U.S.
Army)
TRCS Tactical Radio Communications Systems
TSS Telecommunications Standardization Sector
UAV unmanned aerial vehicle
UHF ultra high frequency
Vac volts alternating current
Vdc volts direct current
VTC video teleconference
XO executive officer

------------------------------------------------------------------------

------------------------------------------------------------------------



ACKNOWLEDGEMENT

The authors gratefully acknowledge the technical contributions of
CECOM Space & Terrestrial Communications Directorate
engineers, the technical and production support by Mark Lambert,
Madentech and Michele Hudak, TAMSCO Support, and Mita Shah
of CECOM for her launching this document onto the Worldwide
Web.
 
To the best of our knowledge, the text on this page may be freely reproduced and distributed.
If you have any questions about this, please check out our Copyright Policy.

 

totse.com certificate signatures
 
 
About | Advertise | Bad Ideas | Community | Contact Us | Copyright Policy | Drugs | Ego | Erotica
FAQ | Fringe | Link to totse.com | Search | Society | Submissions | Technology
Hot Topics
Plausible mixture, need expertise
i wanna make a bottle rocket
PVC end cap failiure.
Detonation by fire?
would this work???
so I've been googling around but:
Books
SHOOTER MOVIE ((Hollywood vs. Reality))
 
Sponsored Links
 
Ads presented by the
AdBrite Ad Network

 

TSHIRT HELL T-SHIRTS