• Military Menu                       

• Introduction
• Systems
• Facilities
• Agencies
• Industry
• Operations
• Countries
• Hot Documents
• News
• Reports
• Policy
• Budget
• Congress
• Links

• WMD
• Intelligence
• Homeland Security
• Space

Army Digitization Master Plan '96

2. RESPONSIBILITIES

The technical nature and aggressive timelines associated with Army digitization efforts require the coordinated actions of all agencies involved to successfully accomplish the Force XXI modernization objectives. The following is a listing of the primary partners in this process and their responsibilities related to digitization:

2.1 Assistant Secretary of the Army for Research, Development and Acquisition/Army Acquisition Executive (ASA(RDA)/AAE)

ASA(RDA)/AAE is responsible for:

• Sponsoring ATDs that bring digital capabilities to a state of technical maturity and demonstrate their military utility before incorporation into follow-on BLWEs and AWEs.
• Providing planning, authorization, and funding support for Force XXI requirements.
• Serving as the Army Technical Architect.
• Coordinating digitization science and technology (S&T) efforts with the Advanced Research Projects Agency (ARPA).
• Ensuring that digitization efforts capitalize on acquisition streamlining initiatives.
• Providing appropriate M/S support.
• Coordinating technical architecture (TA) and S&T efforts with joint and DoD C4I Component Acquisition Executives (CAEs).

2.2 Deputy Chief of Staff for Personnel (DCSPER), HQDA

DCSPER is responsible for ensuring that properly qualified soldiers are recruited, trained, assigned, and retained to meet the skill requirements of the digital battlefield.

2.3 Deputy Chief of Staff for Intelligence (DCSINT), HQDA

DCSINT is responsible for:

• Coordinating signal, human, imagery, measurements, and signature intelligence programs and the counterintelligence and security countermeasures activities supporting the digitized battlefield.
• Establishing priorities for expanding and maintaining the digital terrain database.
• Coordinating security-related policy changes required for digitization efforts.

2.4 Deputy Chief of Staff for Operations and Plans (DCSOPS), HQDA

DCSOPS is responsible for:

• Integrating and synchronizing all efforts across the three axes of the Force XXI Campaign Plan, and leading the axis to re-engineer the Table of Distribution and Allowances (TDA)/Institutional Army in concert with Army commanders.
• Adjusting the fielding schedules of programs—such as Army Tactical Command and Control Systems (ATCCS) and tactical radio communications systems—as needed to support AWE train–up and execution schedules.
• Ensuring digitization programs are prioritized and resourced consistent with the CSA’s goals and timelines associated with fielding a digitized Army XXI.
• Overseeing and validating the Operational Architecture (OA) developed by TRADOC.
• Coordinating Land Information Warfare activities.
• Maintaining the Force XXI Campaign Plan.
• Providing appropriate M/S support.

2.5 Deputy Chief of Staff for Logistics, (DCSLOG), HQDA

DCSLOG is responsible for providing a seamless logistics system which is flexible, deployable, tailorable, and integratable into the digitized battlespace.

2.6 Chief of Engineers (OCE-P), HQDA

OCE-P is responsible for maintaining the digital terrain database.

2.7 Director of Information Systems for Command, Control, Communications, and Computers (DISC4), HQDA

DISC4 is responsible for:

• Providing oversight and proponency for the Army Enterprise Strategy and ensuring that the strategy is executable, compatible, and consistent with Army guidance and direction.
• Supporting the AAE by developing and updating the ATA with the support of the ARSTAF, PEOs, MACOMs, and agencies.
• Exercising spectrum management responsibilities in support of digitization efforts.
• Overseeing the employment of Communication Security (COMSEC) devices in the System Architecture (SA).
• Overseeing and coordinating the implementation of Army software reuse policy in support of digitization efforts.
• Orchestrating the development of the Command and Control Protect program in coordination with DCSOPS and DCSINT.
• Addressing and resolving integration security issues.
• Coordinating the Army’s Operational, Technical, and System architectures with the Office of the Secretary of Defense (OSD) and the other Services.
• Providing appropriate M/S support.
• Overseeing development, programming, and funding for BITS.
• Overseeing data standardization efforts for the Army while retaining the capability to interface with joint systems.

2.8 Army Digitization Office (ADO), HQDA

ADO is responsible for:

• Integrating and synchronizing Army digitization efforts.
• Providing guidance, assistance, and direction in acquisition matters related to digitization.
• Planning, programming, and budgeting for all applique-related costs. These include: applique procurement; installation kit procurement and installation; system engineering; hardware and software changes resulting from the Task Force XXI and Division XXI experiments; and the development and maintenance of the FBCB2 software module for embedded systems.
• Recommending and applying streamlined acquisition procedures to emerging digital technologies in support of Force XXI digitization objectives.
• Coordinating and synchronizing the efforts of combat, materiel, and training developers to develop and deploy Force XXI information technologies.
• Overseeing ATA compliance, to include assuring that system and technical architectures are consistent and that ATA standards are incorporated in contract requirements.
• Maintaining the ADMP.
• Coordinating with the Joint Staff and Unified Commands on all ADMP matters that impact on interoperability of joint and multinational information exchanges.
• Monitoring Army-wide digitization integration to ensure consistency with the ADMP.
• Advising the VCSA and AAE on all matters concerning the integration of digital capabilities across the force.
• Developing and coordinating Memoranda of Agreement (MOA) with the Navy, Marine Corps, and Air Force.
• Coordinating the digitization portion of multinational MOA.
• Coordinating Red Teaming of information systems used in Force XXI AWEs to accomplish vulnerability assessments and provide feedback to developers.
• Ensuring that all systems are certified by the Digital Integrated Laboratory (DIL) before providing them to the EXFOR.

2.9 U.S. Army Forces Command (FORSCOM)

FORSCOM is responsible for:

• Providing personnel and resources in accordance with FORSCOM/TRADOC agreements.
• Providing feedback to the ARSTAF concerning the utility of fielded digital equipment.
• Assisting in design and review of joint/multinational information exchange requirements.

2.10 U.S. Army Training and Doctrine Command (TRADOC)

TRADOC is responsible for:

• Redesigning the operating force to be knowledge-based, modular in design, and tailorable in capability.
• Reviewing the annual Total Army Analysis (TAA) and Program Objective Memorandum (POM) for conformance with Army priorities stemming from Joint Venture experiments.
• Coordinating Joint Venture experiments and findings with other Services and nations.
• Developing and documenting operational requirements associated with the HIBC MNS.
• Developing and updating the OA.
• Identifying and tasking appropriate service schools to support the development of the OA by providing Integrated Definition for Function (IDEF) activity models for information systems (i.e., IDEF0); supporting development of system data models (i.e., IDEFIX); and developing end-user requirements.
• Planning, programming, and budgeting for: Force XXI training and simulations; Division XXI and Corps XXI experimentation; Applique Force Development Test and Evaluation (FDTE); and any other EXFOR/4ID(M) digitization experiments.
• Designing, planning, resourcing, coordinating, conducting, and analyzing AWEs/BLWEs to provide timely feedback for decisions on Force XXI design.
• Developing training and doctrinal literature for digitization implementation.
• Developing, in conjunction with materiel developers, BLWEs that evaluate and refine the operational capabilities of new equipment and software from the FBCB2 contract, related ATDs, and other digitization-related development efforts.
• Aligning ACT II BLWEs with digitization objectives.
• Providing operational control of the EXFOR Coordination Cell (ECC) at Fort Hood, TX.
• Developing programs in conjunction with FORSCOM, AMC, and PEOs for training EXFOR personnel to operate, employ, and maintain their digital equipment.
• Defining, coordinating, and consolidating joint and multinational information exchange requirements in coordination with the Joint Staff, Unified Commands, DISA and the Joint Interoperability Test Center (JITC).
• Providing appropriate M/S support.
• Developing baseline and modified Tables of Organization and Equipment (TO&Es) to reflect equipment authorizations, new manning levels, and required individual skills emanating from Force XXI digitization efforts.
• Developing criteria for evaluating the operational effectiveness of digitization.
• Reviewing Requests for Proposals (RFPs) and Invitations for Bids (IFBs) to ensure Statements of Work (SOWs) sufficiently address training development and requirements.

2.11 U.S. Army Materiel Command (AMC)

AMC is responsible for:

• Providing matrix engineering support to the Army Technical Architect and PEOs/PMs.
• Serving as the Army's Systems Engineer, reporting to the Army’s Technical Architect on technical architecture matters.
• Establishing an Army Systems Engineering Office (ASEO) to support DISC4 in updating the ATA and to provide subject matter experts to Integrated Product Teams (IPTs) preparing SOWs and RFPs.
• Planning, programming, and budgeting for:
• Maintenance of the ASEO.
• Development and maintenance of Weapons System Technical Architecture (WSTA).
• Continued standards development (i.e., MIL STD 188-220A, VMF set, and validation tools).
• The DIL.
• The Army Information Network (AIN).
• Post-Deployment Software Support (PDSS) requirements, to include required changes to embedded system interfaces to comply with the requirement for all systems to migrate to Version 4.0 of the ATA.
• Army participation in commercial standards bodies.
• Multinational interoperability efforts.
• Coordinating all information technology generation and application efforts as they relate to the Army digitization effort.
• Developing plans to migrate systems to the ATA, and evaluating the detailed execution plans submitted by PMs, PEOs, and ACTD/ATD managers.
• Interfacing with joint and multinational technical agencies.
• Influencing commercial standards and participating in related fora.
• Providing expertise in assessing the latest information processing technologies.
• Evaluating commercial technologies.
• Establishing and maintaining the DIL to verify interoperability of C3 and Intelligence and Electronic Warfare (IEW) hardware and software.
• Providing appropriate M/S support.
• Serving as the Army executive agent for multinational digitization efforts.
• Coordinating platform integration.
• Ensuring that a system safety program is implemented, associated responsibilities are accomplished, and safety releases are provided IAW AR 385-16 (System Safety Engineering and Management).
• Ensuring that PMs execute the Manpower and Personnel Integration (MANPRINT) Program IAW AR 602-2 (MANPRINT in the System Acquisition Process).
• Providing technical assistance, subject matter expertise, and materiel support to exercises and experiments.

2.12 U.S. Army Space and Strategic Defense Command (SSDC)

SSDC is responsible for:

• Ensuring that Army programs for the missile defense system developed by the Ballistic Missile Defense Office (BMDO) remain interoperable with evolving information architectures.
• Identifying, evaluating, and coordinating the inclusion of space and missile defense capabilities into Force XXI.
• Providing space and Theater Missile Defense (TMD) M/S support.

2.13 Program Executive Offices (PEO) and Program Managers (PM)

PEOs and PMs are responsible for:

                                                                PLATFORM PM/   
                       TASK                    APPLIQUE PM      END ITEM MGR   
       1. Design common installation kit                                       
       components (e.g., applique mount)            X                          
       2. Produce installation kits                 X                          
       3. Design platform modifications             X                X         
       (e.g., drawings of hole patterns        (Platforms        (Platforms    
       and unique installation kit             identified        identified    
       hardware)                                 in 4/95        after 4/95)    
                                                contract)                      
       4. Modify platforms                                           X         
       5. Install and verify installation           X                          
       kit                                                                     
       6. Verify platform integration                                X         

Note: ADO is responsible for programming and budgeting for all applique-related tasks.

Figure 2-1 Installation Kit Responsibilities

2.14 PEO for Command, Control, and Communications Systems (PEO C3S)

PEO C3S is responsible for:

• Managing the acquisition and fielding of Force XXI C3 systems.
• Managing the Force XXI system integration effort with support from AMC, to include the development and maintenance of the TF XXI Systems Integration Plan (TSIP).
• Developing software products supporting the COE.
• Evaluating COE candidate products and ensuring that Army COE requirements are provided to DISA.
• Developing, in conjunction with TRADOC, programs to train EXFOR personnel to operate, employ, and maintain their digital equipment.
• Providing appropriate M/S support.
• Creating and updating the Force XXI SA.
• Preparing and overseeing the overarching Digitization Risk Management Plan.
• Serving as the ADO’s executive agent for the Applique contract.
• Ensuring that all components of the Tactical Internet are programmed in the POM.
• Preparing an Applique EXMP in coordination with the ADO.
• Preparing, in coordination with the ADO, a capstone Tactical Internet EXMP.
• Developing and coordinating all documentation for Milestone Decision Reviews (e.g., the TEMP).

2.15 U.S. Army Operational Test and Evaluation Command (OPTEC)

OPTEC is responsible for:

2.16 Experimental Force (EXFOR): 4th Mechanized Infantry Division

The EXFOR is responsible for: