Army Digitization Master Plan (ADMP)

CHAPTER 2 - DIGITIZATION REQUIREMENTS

Weapon System Build-Up

In the 1980s, the Army fielded the Abrams tank, Bradley Fighting Vehicle (BFV), Apache attack helicopter, Multiple Launch Rocket System (MLRS), and Patriot Missile System. These investments, along with other new systems and improvements to then-existing platforms, made possible the design of new organizations and the implementation of a new doctrine—AirLand Battle. These revolutionary advancements were proven on the battlefields of the Gulf War. Their unequivocal success temporarily silenced the critics of the defense buildup that preceded Desert Storm.

Less Modernization in the '90s

For the remainder of the 1990s and into the beginning of the next century, the modernization program of the Army is not as robust as it was in the 1980s. With notable exception of the Advanced Field Artillery System (AFAS), there are few major programs scheduled for production. Incremental modernization of current weapons systems is planned.

Needed Capability

What is needed is another quantum surge in force capability. Interoperable digitization of the battlefield has the potential to provide the means for the next renaissance of military art and science, in the same manner that the infusion of digital technology into the American society is providing a transitional bridge from the Industrial Age to the Information Age.

2.2 Information Warfare

Information is power. The commander who possesses it and uses it has a decisive advantage over an opposing commander who does not have the most current information. Yet, the current method of distributing critical, time-sensitive information across the battlefield has not changed, despite significant improvements brought about by automation efforts within specific battlefield operating systems (BOS), such as in fire support and military intelligence.

Current Situation

Currently, spot reports are passed upward from the lowest tactical level by voice radio when a brief pause in the close-in battle allows time to forward the report. At the next echelon, the information is received by a radio operator who hand-copies it and aggregates it with other reports being simultaneously received; retransmitting it to the next higher command echelon as time permits. This time-consuming cycle is repeated at each succeeding level as the information gradually climbs upward within the hierarchical communications net structure which parallels the pyramidal organizational command layers. Time lag can be significant.

Passing the information laterally within the command structure or from one BOS to another is a hit-or-miss proposition, based on the criticality of the information and the net loading occurring at that particular point in time. It is in the midst of battle, when information is the most critical and radio nets receive the highest loading factor, that the system tends to choke on the volume of traffic and receipt of vital information is often delayed. Tactical and operational windows of opportunity can be ex eedingly brief, based on the battlefield physics of time and space.

Digitization Expedites Information Flow

Passing of information digitally expedites the information flow and accelerates the decision making cycle. Information is more readily available to everyone with access to the network at the appropriate echelons. It dramatically decreases the time needed to convert a decision into execution, whether via a cryptic fragmentary order appearing on a tank commander's graphics display or a hasty "John Madden" operations sketch electronically received and transposed on top of a digital terrain map.

At the lower tactical levels, essential decision making needs can be very basic. The most often requested information on every command net consists of: Where are you? Where is the enemy? What are each of you doing?

Shared Situational Awareness

Shared situational awareness provides everyone with the same near-real-time picture of their relative battlespace. The company commander can see on his digital display where each of his elements are located, to include those out of the line-of-sight. In the same manner, the battalion commander can track his platoons, the brigade commander his companies, and the division commander his battalions. By means of a distributed database, the division can also portray the location of any single vehicle transmitting its position. By conversion to a network structure, the leader on the ground can also follow the progress of the units across his lateral boundaries, as well as those to his front, regardless of their unit affiliation. Maneuver operations can be more tightly synchronized while the instances of fratricide can be greatly reduced. At the same time, intelligence obtained from multiple sources is rapidly fused, analyzed, and transmitted, with enemy icons appearing on the same visual display.

Figure 2-1 Digital Capability

Battllefield Digitization Example

The effectiveness of digitization can be shown by considering the following example. On a digitized battlefield, a tank triggers his laser range finder on the lead vehicle of an approaching enemy. The Global Positioning System (GPS) equipped tank "knows" its location, the range and azimuth to the enemy vehicle, and can immediately compute the coordinates of the enemy. This information is automatically placed in a spot report message that the tank Platoon Leader calls up on his screen. This spot report is then transmitted over the digital radio to the company commander. This near instantaneous (seconds instead of minutes) transfer of information provides the commander with a more complete picture of his battlespace, enabling him to quickly direct his subordinates, getting every shooter into the fight, and making maximum effective use of direct and indirect fires available to him. The enemy location information can be easily transferred to a call-for-fire (CFF) message template that the tank Platoon Leader calls up on his screen. The CFF message is then transmitted over the digital radio to the fire direction center which automatically begins the decide, detect, and deliver targeting sequence. The firing unit is then alerted. The targeting information is processed while simultaneously being routed into the intelligence database. If a firing platoon is in position waiting for a CFF, rounds can be in the air within 45 seconds of the original CFF sent by the tank. All of this can be done without a voice transmission.

2.3 Value Added

To insert or retrofit a new technology onto the Army's substantial equipment inventory is a massive undertaking. The first question properly posed by programmers and budgeters is "What is the value added?". The Army's hypothesis is that a digitized capability will enhance force effectiveness, specifically in terms of improved lethality, survivability, and tempo. Early modeling and simulation results have indicated that forces that can exchange information digitally can move more quickly and engage the enemy more decisively. The Army is structuring the Advanced Warfighting Experiments (AWE) to further test this hypothesis and will be collecting data to refine and, where possible, quantify the relationship between improvements in digitized capabilities and improvements in force effectiveness.

Empirical Data Needed

While the effect of digitization on the battlefield can be crudely modeled by decreasing response times and subjectively adjusting combat factors, modeling a totally new capability is always a daunting challenge. In the absence of hard, empirical data, the immediate answer is elusive. Without empirical data, analyses based on the results of simulations lack the degree of requisite credibility.

The necessary empirical data will be provided in the near and mid-term by a series of planned Advanced Technology Demonstrations (ATDs), Advanced Warfighting Demonstrations (AWDs), Advanced Concept Technology Demonstrations (ACTDs), and AWEs. They will serve as the technical and doctrinal testing grounds which will provide the updated foundation for the Army of the 21st century.

Specific BOSs can be isolated. For example, applying a higher artillery rate of fire and increased level of accuracy would be based on improved digital fire direction control and precise locations of observer, target, and firing unit. However, the synergism of similar technology-driven advances simultaneously occurring within multiple layers of each BOS in the conduct of the deep, close and rear battles requires far too many assumptions at this early stage of implementation.

Baseline studies and analyses as well as assessing the impact of digital technology using current tables of organization and equipment is an essential starting point for subsequent excursions. However, the ensuing rough estimate would measure future battlefield value using present warfighting means, and would ignore the baseline changes in doctrine and structure that would take place prior to fielding the digitized force. Attempting to apply several changes simultaneously in a predictive model would statiscally bury the marginal contribution of any one input and could result in incorrect conclusions.

2.4 Operational Requirements Documents (ORD) and Mission Needs Statement (MNS)

Requirements Documents

There is no single requirements document for digitization. Instead, the conceptual and requirement underpinnings on which digitization is built come from a variety of sources that include Mission Needs Statements (MNSs), Operational Concepts, Operational Requirements Documents (ORDs), and Policy Guidance and Regulations. The key documents for digitization are the Horizontal Integration of Battle Command (HIBC) MNS and the Army Battle Command System COE/CA ORD.

2.4.1 Horizontal Integration of Battle Command Mission Needs Statement (HIBC MNS)

Baseline Operational Requirements

The HIBC MNS establishes the baseline operational requirements for digitization of the battlefield and future command systems. It was approved by the Department of the Army and forwarded to the Joint Requirements Oversight Council (JROC) for validation in October 1994. The Defense Information Systems Agency (DISA) and J6 granted Command, Control, Communications, and Computers (C4) interoperability certification on 6 December 1994. The MNS was validated by JROC on 10 January 1995. MNS validation supports the expenditure of Task Force XXI Research, Development, Training, and Evaluation (RDTE) digitization funds. The operational baseline provides for:

Capability to react on information faster than the enemy.
Enhanced situational awareness at all levels.
Rapid processing and transfer of information.
Faster and more comprehensive access to intelligence data.
Increased ability to synchronize direct and indirect fires.
Means to establish and maintain an overwhelming operational tempo.

MNS Objectives

The objectives of the MNS are broad in nature, intended to address the stated operational needs and provide the Army with the technical means to meet the battlefield command and control (C2) challenges of the 21st century by:

Providing commanders with a clear, near-real-time picture of their relative battlespace.
Establishing Army Battle Command System (ABCS) database for expeditious information transfer.
Exploiting state-of-the-art communications, sensors, and computers.
Developing an integrated ABCS with:
Horizontal integration among BOSs.
Vertical integration among command echelons.
Achieving battle command linkages among discrete C2 systems.
Integrating weapons systems, command posts, sensors, and support systems.
Devising standard, interoperable data exchange methods and protocols.
Accomplishing Joint/Combined interoperability through migration to the Global Command and
Control System (GCCS) and its common operating environment (COE) system.
Interconnecting of digital terrain data and terrain visualization, fused with intelligence data, for graphic portrayal of battlespace and situational awareness.

Capability Constraints

The MNS does not describe a materiel solution but does establish a series of basic hardware and software constraints:

Standard hardware to reduce costs and simplify maintenance.
The use of modularity and an open architecture to facilitate ease of upgrades.
The option of embedded or applique hardware—as appropriate to the system.
A mix of commercial off the shelf (COTS), ruggedized, and military specification components.
A Technical Architecture consisting of common applications, standards, and protocols.
A user-friendly interface, permitting effective operation in a tactical field environment.
Standard Defense Mapping Agency (DMA) digital map and terrain data as well as hasty data provided by Army topographic elements.
Common graphics and tactical symbology.
C2 of supporting operations on-the-move without degradation.
Equipment capable of operating in the same battlefield, climate, and weather as the host platforms.
A means to identify friend, foe, or noncombatant using sensor information and/or data sources.
Meet Joint standards for Command, Control, Communications, Computers, and Intelligence (C4I) interoperability to interface seamlessly with GCCS.

The general capabilities are tailored to allow the smaller force projection Army to more efficiently and decisively concentrate battlefield "effects," rather than the massing of forces and firepower by traditional means. The intent is to enable contingency forces - comprised of fewer and smaller units - to be more lethal and survivable in an environment characterized by an accelerated operational tempo demanding instant communications and immediate response times.

2.4.2 Army Battle Command System Common Operating Environment/Common Applications Operational Requirements Document (ABCS - COE/CA ORD)

The ABCS-COE/CA ORD further refines the operating capability needs defined in the HIBC MNS. It defines the need for a common operational environment for common applications. It is being developed by the combat developer (TRADOC) with submission to the Department of the Army targeted for mid-January 1995 and approval projected by March 1995.

The draft ABCS-COE/CA ORD incorporates the requirements of the HIBC MNS and envisions the repackaging and consolidation of existing systems. The ABCS-COE/CA ORD calls for the migration of current separate Army C2 component systems into one integrated system. Its purpose is to merge existing capabilities and requirements into one integrated battle command system from individual squad/platform through strategic levels. The ABCS-COE/CA components are the Army Global Command and Control System (AGCCS), the Standard Theater Army Command and Control System (STACCS), and the Combat Service Support at Echelons Above Corps (CSS at EAC); the Army Tactical Command and Control Systems (ATCCS) consisting of: the Maneuver Control System (MCS), All Source Analysis System (ASAS), Combat Service Support Control System (CSSCS), Air/Missile Defense Tactical Operational System, and the Advanced Field Artillery Tactical Data System (AFATDS); and the Force XXI Battle Command Brigade-and-Below (FBCB2) system which has the functionality of systems at brigade and below such as the Brigade and Below Command and Control System (B2C2) and Inter-vehicular Information System (IVIS).

Figure 2-2 Army Command and Control Umbrella

ABCS Concept

ABCS is the integration of systems battlefield automation systems (BAS) and communications which functionally link strategic, operational, and tactical headquarters. It employs a mix of fixed and semi-fixed installations and mobile networks, depending on the subsystem. It is interoperable with theater, Joint, and Combined C2 systems across the full range of BOS functions, and is vertically and horizontally integrated at the tactical and operational levels.

Global Command and Control System (GCCS)

GCCS

The GCCS was designated the single C2 system for the Department of Defense (DoD). It is built within the framework of the:

Technical Architecture for Information Managment (TAFIM) dated 30 June 1994;
Technical Reference Model within the TAFIM;
GCCS Integration Standard, dated 26 October 1994;
GCCS User Interface Specification, Version 1.0, dated October 1994; and
GCCS Common Operating Environment, dated 28 November 1994.

GCCS is the realization of "C4I for the Warrior" concept. GCCS improves the Joint Warfighter's ability to manage and execute crisis and contingency operations and provide a means to interface to Commanders-in-Chief (CINCs), Services/Agencies C4I systems for peacetime deliberate planning as well as crisis planning and execution. The concept builds upon lessons learned from previous conflicts, operational requirements, and the effects of rapidly changing technology.

Figure 2-3 Army Battle Command System

The Warfighter requires a seamless information system, where boundaries between functions and sources are erased. GCCS provides the seamless, integrated information to the Warfighter when, where, and how it is needed. This enhances Warfighter effectiveness by driving interoperability through the elimination of duplicated functionality and the convergence of Joint Warfighter doctrine via GCCS's encapsulation of common Command, Control and Intelligence (C2I) methods. GCCS uses the secret internet protocol network (SIPRNET) as its communications backbone.

The goals of the GCCS are:

For all CINCs, provide one affordable system that integrates across Services and functions to provide the Warfighter with a single picture of the battlespace.
To migrate legacy applications to modern computing principles and technologies through the use of a COE.

To support these goals, the GCCS includes applications that provide efficient monitoring, planning, deployment, employment, and sustainment of military operations from the National Command Authority (NCA) to the Commander, Joint Task Force level.

Army Global Command and Control System (AGCCS)

AGCCS

AGCCS, a seamless C2 system, will be built around the Joint Common Operating Environment (JCOE) and will be an interoperable component of the GCCS. It will be designed to ensure software and technology reuse and minimize duplication among C2 systems. AGCCS is a system development, integration, and maintenance effort initially consolidating three existing projects: Army World Wide Military Command and Control Systems Information System (AWIS), Standard Theater Army Command and Control System (STACCS) and Combat Service Support Control System (CSSCS). AGCCS provides a source of technical support and services in fielding a seamless C2 structure for the Army at echelons above corps.

Army Tactical Command and Control System (ATCCS)

ATCCS

Initially, ATCCS will be linked directly to AGCCS providing the framework of seamless connectivity from brigade to corps. Objectively, the traditional disparate stovepipe functions will merge into a coherent and seamless interoperable program that binds the combined arms BOS together by using the COE. FBCB2 will complete holistic, seamless integration of the tactical battle command by adding capabilities at individual squads and platforms and passing and receiving required data with higher headquarters.

Force XXI Battle Command, Brigade and Below (FBCB2)

FBCB2 provides the lower level interface into ABCS.

Force Level Information Database

The Force XXI Battle Command Brigade and Below (FBCB2) system provides digital connectivity from brigade to the weapon systems/platform level and is comprised of:

The "applique" -- processing devices connected to navigation devices and radios to provide processing and display capabilities to platforms without an embedded processor.
Common software, hosted both on appliques and embedded processors, that is interoperable with the C2 systems at brigade and above.
The "Tactical Internet" -- battlefield communication systems internetted using commercially-based Internet protocols.

The FBCB2 acquisition strategy is phased to support the Force XXI experimental process. During the Concept Exploration Phase, non-developmental prototype equipment will be rapidly acquired to support the redesign of brigade and below organizations; to evolve new, information based tactics, techniques, and procedures; and to refine digitization requirements. During the combined Demonstration/Validation and Engineering and Manufacturing Development Phase, the acquisition efforts will focus on supporting division and corps level experiments. Software and hardware products will be matured and evaluated to support the decision to enter the production phase. Each phase will be competitively awarded with emphasis on commercial equipment and "best value." Streamlining procedures will be applied throughout.

Force Level Information (FLI) in ABCS

Overall, ABCS provides commanders and staffs with standard, modular, system support and applications support software, coupled with a tailorable set of unique and common functional applications software, to create, access and update a FLI database and generate a user-defined picture of the battlefield, in both time and space.

The key integration feature of ABCS above the operating environment is the establishment of the FLI database, which provides commanders and staffs with the ability to:

Graphically portray the relevant common picture of the battlefield.
Project situations, requirements, and capabilities.
Determine the impact of possible courses of action.
Develop staff estimates.
Present findings and conclusions.

The common picture that provides situation awareness for all levels is the sum of all information contained in the FLI database in a graphic display format, defined and tailored by the user according to his needs. The common picture for a division commander differs significantly from that of a battalion commander in terms of time and distance scales and the scope of information tracked, yet each access the same common database. Inputs into the picture include:

Own, enemy, and friendly locations, to include across boundaries within specified areas.
Maneuver graphics and control measures portrayed on a digital map display using Army doctrinal scales of 1:50,000, 1:100,000, 1:250,000, and 1:1,000,000.
Operational, logistical, and personnel status of subunits.
Digitized terrain data.

In essence, the graphical portrayal of the common picture is very similar to that provided by a state-of-the-art commercial battle simulation, with a zoom-in/zoom-out capability and the ability to access a wealth of information via a series of pull-down menus.

Hardware

ABCS relies heavily on common hardware (CH) to meet future needs and upgrades of current systems at battalion level and above. Platform-specific hardware is developed in keeping with space, configuration, and power constraints of the host air/ground vehicle. Platform hardware consists of embedded or applique sets, as appropriate. Dismounted soldiers use portable systems in general purpose vehicles. The use of smaller hardware at echelons below battalion is desirable in terms of cost and probability.

Common hardware consists primarily of a suite of proven COTS and non-developmental item (NDI) computer hardware. Interfaces to tactical and commercial communications and peripheral devices make up individual workstations, configured into nodes and elements in the C2 architecture via local and wide area networks (LAN/WAN). CH and peripherals incorporate evolving state-of-the-art processing technology to enhance general system performance over time.

Software

Users receive a Common Software (CS) suite appropriate to their hierarchical echelon and Battlefield Functional Area (BFA) consisting of three types of software written to operate with one another.

COTS system software and other basic functions, such as database management and word processing.
COE modules supporting basic system-related transparent operations such as message handling and workstation management.
Common and unique software modules with common functions, such as movement control and operations plans/orders and unique applications for specific platform and/or BOS functionality.

Provisions also exist to execute applications unique to a specific platform and/or BOS.

Software design incorporates a standard multi-layered open system architecture. Modular functional applications are ported on the COE, interfacing with the COTS system software in a COE, operating on a standard suite of processors.

2.4.3 Force XXI Battle Command Brigade-and-Below (FBCB2) ORD

The FBCB2 ORD further refines the operational capability needs defined in the HIBC MNS and the ABCS-COE/CA ORD. It defines the need for the lowest level C2 interface capability to the ABCS and standardizes the components of that capability. It is being developed by the combat developer (TRADOC) with submission to the Department of the Army targeted in-January 1995 and approval projected by March 1995. The final FBCB2 ORD will evolve through the experimentation process and be refined in coordination with the Air Force and Marine Corps based upon experimentation results. Interoperability certification by the JCS J6 will verify the refinement.

Definition

For the purpose of the ORD, the term "brigade-and-below" encompasses the headquarters and subordinate elements organic to:

Maneuver brigades (armor and mechanized, light, airborne, or air assault infantry and aviation).
Armored cavalry regiments (heavy and light).
Divisional air and ground cavalry/reconnaissance squadrons.
Aviation battalions (attack, assault, heavy lift).
Combat Support (CS)/Combat Service Support (CSS) brigade level support units.
ADA battalions, batteries, platoons, and fire units.

Brigades can be subordinate to a division or operate separately as task forces reporting to a Joint/Combined command authority.

Scope

The FBCB2 ORD establishes the requirements for horizontal and vertical integration of digitized battle command within the Task Force XXI. The ORD looks beyond current interim efforts, such as IVIS and B2C2, toward an objective C2 system for the 21st century. It describes both an integrated C2 system and a future warfighting concept.

The emphasis at brigade-and-below is on situational awareness at all echelons. Information is sent and received digitally in real or near-real time. Information that would take many minutes to obtain is retrieved and displayed in seconds, employing a user-friendly system designed to enhance the capabilities of the individual soldier.

The concept addresses the answers to four basic questions:

Where am I?
Where are my soldiers?
Where is the enemy?
What is each of them doing?

Functional Requirements

Functional requirements for the platform and squad/section levels are:

Automatic position location and reporting.
Digital map with graphics, with a limited color capability (i.e. 8-bit/256 colors) and hasty mapping products.
Graphical display of the location of radio net members and adjacent friendlies.
Display enemy locations in predetermined zone or sector.
Link to the line-of-sight battlefield combat identification system with visual and aural alerts.
Automated logistics and operational status reports.
Templates for digital reports and requests, with prompts.
Information storage and recall.

Platoon Leader and Sergeant

Functional requirements for the platoon leader and platoon sergeant are the same as above, plus ability to:

Synchronize and control sub-elements.
Create, send, and receive text and graphics.
Receive and consolidate status reports.
Calculate and display platoon center-of-mass (COM) or individual vehicles/squads.
Display COMs across the battlefield.
Display COMs of adjacent units outside the company/team radio net.
Filter out information outside the desired area of interest.

Company Commander, Executive Officer, and First Sergeant

Functional requirements for the company commander executive officer and first sergeant are the same as above, plus ability to:

Automatically receive, consolidate, and transmit platoon reports.
Provide an automated roll-up of logistical requirements.
Display company/team positions by squad/vehicle or platoon COM.
Display COMs of all elements in battalion task force radio net.
Display COMs of adjacent units outside the battalion task force radio net.

Battalion Commander, Executive/ Operations Officer, and Command Sergeant Major

Functional requirements for the battalion commander, executive/operations officer and command sergeant major are the same as above, plus ability to:

Provide access to the ABCS FLI database.
Provide access to ATCCS to coordinate operations and support.
Provide a LAN for:

- C2 Vehicle(C2V).

- Tactical Operations Center (TOC).

- Combat and field trains.

Brigade Commander, Executive/ Operations Officer, and Command Sergeant Major

Functional requirements for the brigade commander, executive/operations officer and command sergeant major are the same as above, plus have the ability to:

Provide access to all available databases.
directly to both B2C2 (or its equivalent) and ATCCS.

It is important to note the friendly location requirement includes units across adjacent boundaries, in a different combat radio net and possibly belonging to a different parent unit. The urgent need for this information in a near-real-time manner reduces the incidence of fratricide and better coordinates cross-boundary fire and maneuver. It is also a major factor in determining the architectural requirements and procedures to transfer position/location data.

As a subset of ABCS, FBCB2 complies with the ABCS Technical Architecture and COE. This migration to a COE facilitates meeting Joint interoperability requirements. It also is fully functional with other ABCS systems for horizontal and vertical integration. With FBCB2, users can:

Transmit voice and data from the same platform without mutual interference.
Use common message formats and protocols.
Automatically access multiple communications paths.
Other Requirements of FBCB2
Operate their systems through user-friendly software and interfaces.
Acquire and disseminate weather data.
Operate while on-the-move.
Employ multi-use application software for use in garrison and in the field.
Access on line, embedded, or off-line training support packages.
Fuse digital terrain data and intelligence data into a graphic portrayal of battlespace and situational awareness.

2.5 Other Requirements

2.5.1 Logistics

Supportability

The logistics support strategy for digitization subsystems and components is initially established in accordance with appropriate objectives and policies contained in AR 700-127, Integrated Logistics Support. Early phases rely heavily on contractor logistics support, particularly during experimentation cycles. For systems using appliques, the longer term support strategy depends upon issues such as unit cost, ease of repair, and level of repair. For those systems with embedded digitization subsystems (see section 4.1.1), the logistics are based on the approach applied to the host platform. Generally, supportability and sustainability issues will be addressed by the relevant PEOs/PMs and item managers.

2.5.2 Manpower and Personnel Integration (MANPRINT)

Soldier Considerations

The MANPRINT process focuses on integrating the system with the soldier based on analyses and tradeoffs within and across the seven domains listed below. Implementation of the digitization program will require careful analysis to minimize the overall impact on individual operators, maintainers, supporters, fighting unit, and force as a whole. Although many of the issues are addressed at the platform level by individual PEOs and PMs, tradeoffs addressing force level considerations require particular ADO management and oversight. The character of the issues vary depending upon the implementation at various phases of the program (e.g., applique vs. embedded system). Representative issues associated with the domains include:

Manpower - Minimizing system manning requirements for operations, maintenance, and support by using automation to reduce manpower spaces for selected functions.
Personnel - Designing subsystems and components which are compatible with existing military occupational specialty (MOS) skill requirements and personnel capabilities.
Training - Minimizing the requirement for additional, unique training to operate or maintain digitization subsystems and components; using embedded training and interactive simulation networks to support integrated force training.
Human Factors Engineering - Optimizing the man-machine interface to maximize effectiveness and minimize harmful effects (e.g., increased workload).
System Safety - Ensuring that integration of the applique does not compromise the overall safety of the host system (e.g., by affecting ease of egress in an emergency).
Health Hazards - Ensuring that the integration of the applique does not introduce potential health hazards (e.g., by increasing the potential for electrical shock or physical injury).
Soldier Survivability - Assessing the contribution of digitization to fratricide reduction through greater situational awareness.

2.5.3 Spectrum Management

Managing the Spectrum

Current and future battlefields present a complex radio frequency (RF) environment. The potential for interference, whether intentional or unintentional, is significant. Such interference degrades the speed, accuracy, and reliability of communications. Even in peacetime operations, limitations on use of the RF spectrum presents a significant challenge. The design of the communications subsystem(s) supporting digitization will have to balance multiple factors such as bandwidth requirements, spectrum availability, compatibility with other communications systems, and susceptibility to jamming.

2.5.4 Security

Information Security

Digitization systems must maintain an appropriate level of security. This will be accomplished by integrating computer and communications security capabilities using technologies currently available and those under development. Additionally, those systems that accomplish data fusion and have Multi-Level Security (MLS) requirements will be met using the technological capabilities of the Multi-Level Information Systems Security Initiative (MISSI) program products as applicable. Other products and services which may come available through market research and technology advances w will be considered in lieu of MISSI components where appropriate. Systems that provide common-view-of-the-battlefield capabilities will be initially secured using Tactical Packet Network (TPN), which is accredited for operations at the Secret level and operates in the Systems High Mode. A migration path will be established to reduce communications accreditation levels to unclassified and encrypt data transmission at appropriate levels from originator to receiver. This path will ensure technology infusion in a timely and cost effective manner. Adequate attention will be given to human resource requirements associated with system security administration.

2.5.5 Survivability

Environmental Factors

Survivability considerations associated with the digitization program cover a broad range of issues. At the lowest level, the ability of the digitization subsystem or component to survive environmental factors (e.g. shock, vibration, temperature, and dust) associated with the host platform must be addressed. This is of particular concern for applique systems consisting of COTS hardware. Means must be found to ruggedize or isolate the subsystem and components from environmental effects.

Electronic Warfare

At a second level, the susceptibility of digitization systems to interception, jamming, deception and exploitation must be addressed. The vulnerability of the information, resident in and accessible through the Internet must be assessed. Information may be lost to corruption by malicious code or the introduction of viruses, as well as the vulnerability of information flow to disruption. The system design must minimize the potential for enemy interference or for exploiting these capabilities against friendly forces.

Finally, the impact of the introduction of digitization subsystems and components on host system survivability must be addressed. For example, the effect of the addition of digitization capabilities on the RF signature associated with the host system must be assessed. Additionally, the enhancement to mission capabilities should outweigh the costs in terms of increased susceptibility to enemy sensors and weapons.

NEWSLETTER

Join the GlobalSecurity.org mailing list