Human Performance Model Development of a 

Battalion Tactical Operations Center 

by Josephine Q. Wojciechowski, Beth Plott, and Patricia W. Kilduff 

ARL-TR-2635 August 2005 

Approved for public release; distribution is unlimited.
Report Documentation Page Form Approved

OMB No. 0704-0188

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and

maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,

including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington

VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it

does not display a currently valid OMB control number.

1. REPORT DATE

AUG 2005

2. REPORT TYPE

N/A

3. DATES COVERED

 - 

4. TITLE AND SUBTITLE

Human Performance Model Development of a Battalion Tactical

Operations Center

5a. CONTRACT NUMBER

5b. GRANT NUMBER

5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S) 5d. PROJECT NUMBER

5e. TASK NUMBER

5f. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES)

U.S. Army Research Laboratory Human Research and Engineering

Directorate Aberdeen Proving Ground, MD 21005-5425

8. PERFORMING ORGANIZATION

REPORT NUMBER

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)

11. SPONSOR/MONITOR’S REPORT 

NUMBER(S)

12. DISTRIBUTION/AVAILABILITY STATEMENT

Approved for public release, distribution unlimited

13. SUPPLEMENTARY NOTES

14. ABSTRACT

15. SUBJECT TERMS

16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF 

ABSTRACT

UU

18. NUMBER

OF PAGES

150

19a. NAME OF

RESPONSIBLE PERSON

a. REPORT

unclassified

b. ABSTRACT

unclassified

c. THIS PAGE

unclassified

Standard Form 298 (Rev. 8-98)

Prescribed by ANSI Std Z39-18 
NOTICES 

Disclaimers 

The findings in this report are not to be construed as an official Department of the Army position 

unless so designated by other authorized documents. 

Citation of manufacturer’s or trade names does not constitute an official endorsement or 

approval of the use thereof. 

DESTRUCTION NOTICEDestroy this report when it is no longer needed. Do not return it to 

the originator. 
Army Research Laboratory 

Aberdeen Proving Ground, MD 21005-5425 

ARL-TR-2635 August 2005 

Human Performance Model Development of a 

Battalion Tactical Operations Center 

Josephine Q. Wojciechowski and Patricia W. Kilduff 

Human Research and Engineering Directorate, ARL 

Beth Plott

Micro Analysis & Design, Inc. 

Approved for public release; distribution is unlimited.
ii 

REPORT DOCUMENTATION PAGE Form Approved 

OMB No. 0704-0188

Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the 

data needed, and completing and reviewing the collection information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the 

burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. 

Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid 

OMB control number. 

PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ADDRESS. 

1. REPORT DATE (DD-MM-YYYY)

 August 2005 

2. REPORT TYPE 3. DATES COVERED (From - To) 

 January 2004 to January 2005 

5a. CONTRACT NUMBER 

5b. GRANT NUMBER 

4. TITLE AND SUBTITLE 

 Human Performance Model Development of a Battalion Tactical Operations 

 Center 5c. PROGRAM ELEMENT NUMBER 

5d. PROJECT NUMBER 

 622716AH70 

5e. TASK NUMBER 

6. AUTHOR(S) 

 Josephine Q. Wojciechowski (ARL); Beth Plott (MA&D); Patricia Kilduff 

 (ARL) 

5f. WORK UNIT NUMBER 

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 

 U.S. Army Research Laboratory 

 Human Research and Engineering Directorate 

 Aberdeen Proving Ground, MD 21005-5425

8. PERFORMING ORGANIZATION REPORT 

 NUMBER 

ARL-TR-2635

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR'S ACRONYM(S) 

11. SPONSOR/MONITOR'S REPORT NUMBER(S)

12. DISTRIBUTION/AVAILABILITY STATEMENT 

Approved for public release; distribution is unlimited. 

13. SUPPLEMENTARY NOTES 

14. ABSTRACT 

A multi-year research and development effort was undertaken by the U.S. Army Research Laboratory in evaluating trade-offs 

between various configurations of Soldiers and equipment in the command and control (C2) environment. The work consisted 

of a series of phases (e.g., task-network design, performance data collection, model programming, etc.), which resulted in a 

number of computer-based C2 models. Two of the models built were identified for use in evaluating the impact of Soldiers 

conducting their C2 functions in a moving vehicle. This report documents the task analysis that was completed in the creation of

those models and simulations. It includes all the assumptions, input to the models, and output capabilities. The model runs can 

be used for comparative “what if” analyses to determine the impact of Soldiers conducting their C2 functions in a moving 

vehicle. While these models do not predict exact results, the analyses of the different movement profiles can be compared to 

assess the effect of C2 in a moving vehicle. The objective of this report, in particular, is to describe the simulations themselves 

and to document their development. No model runs or data analysis are provided in this report.

15. SUBJECT TERMS

 battalion tactical operations center; command and control; human performance; model and simulation 

16. SECURITY CLASSIFICATION OF:

19a. NAME OF RESPONSIBLE PERSON

 Josephine Q. Wojciechowski 

a. REPORT 

Unclassified 

b. ABSTRACT 

Unclassified 

c. THIS PAGE 

Unclassified 

17. LIMITATION 

OF ABSTRACT 

 SAR 

18. NUMBER 

OF PAGES 

 85 19b. TELEPHONE NUMBER (Include area code) 

 410-278-5878 

Standard Form 298 (Rev. 8/98) 

Prescribed by ANSI Std. Z39.1 
iii 

Contents 

List of Figures v

List of Tables v

1. Introduction vii

2. Preliminary Task Analysis 2

3. Detailed Task Analysis 3

4. Task Analysis by Operator and Staff Section 4

4.1 Configurations.................................................................................................................6 

4.1.1 Analog .................................................................................................................6 

4.1.2 Digital..................................................................................................................7 

4.2 Personnel .........................................................................................................................7 

4.3 Scenario...........................................................................................................................7 

5. Model Development 7

5.1 Operator Data ..................................................................................................................8 

5.2 Task Data.........................................................................................................................8 

5.3 Task Degradation Data....................................................................................................9 

5.4 Scenario Data ................................................................................................................10 

5.5 Application Constructs and Assumptions .....................................................................11 

6. Conclusions 19

7. References 21

Appendix A. Task Analysis of TOC 23 

Appendix B: Analog and Digital Model Personnel 29

Appendix C. Workload Scenario Development Project 39 
iv 

Appendix D. Analog and Digital Task Lists 113

Appendix E. Time Degradation Factors 131

Appendix F. Message-Routing Variable Definitions 133

Acronyms 137

Distribution List 139 
v 

List of Figures 

Figure 1. Work flow diagram for a staff section (adapted from Knapp et al., 1997). ................... 2 

Figure 2. Analog TOC diagram. ..................................................................................................... 5 

Figure 3. Digital TOC diagram...................................................................................................... 5 

Figure 4. Command group (commander and S3 in their vehicles) task networks....................... 14 

Figure 5. S2 and S3 task networks............................................................................................... 15 

Figure 6. Fire support and engineer task networks...................................................................... 16 

Figure 7. XO and ALO task networks. ........................................................................................ 17 

Figure 8. Staff huddle task networks. .......................................................................................... 18 

Figure 9. CTCP task networks..................................................................................................... 19 

List of Tables 

Table 1. List of personnel in battalion tactical operation center as modeled................................. 6 

Table 2. Operator types used in the model. ................................................................................... 8

Table 3. Model operator and operator type assignments. .............................................................. 8 

Table 4. Detailed job functions used in the models....................................................................... 9 

Table 5. Queue and “in process too long” times.......................................................................... 19 

Table A-1. Task analysis of TOC. ............................................................................................... 23 

Table B-1. Analog model personnel. ........................................................................................... 29 

Table B-2. Digital model personnel............................................................................................. 33 
vi 

INTENTIONALLY LEFT BLANK
vii 

Acknowledgments 

The authors would like to acknowledge several people for their contributions. Although this 

report is limited to documenting the model developed to support the project, “On-the-Move 

Performance Modeling of Heavy Maneuver Battalion C2V Equipped Tactical Operations 

Center,” we would like to recognize those who contributed to model development and those who 

contributed to the overall project. 

We would like to thank Dr. Beverly Knapp, Joyce Johnson, and Jennifer Swoboda from the U.S. 

Army Research Laboratory (ARL) and Ms Annette Ensing from Mitre Corporation for 

contributions that were useful to the model development. Dr. Knapp, Ms. Johnson, and Ms. 

Ensing were instrumental in the preliminary task analysis that led to the task flows represented in 

this model. Dr. Knapp’s guidance in preparation for the analysis phase improved the 

development of the model itself. Ms. Swoboda developed the task degradation factors used in 

the model from data in literature. 

We would like to thank Dr. Knapp, Sam Middlebrooks, Jennifer Swoboda, and Diane Barnette of 

ARL for their contributions to the overall project. Dr. Knapp provided guidance during the 

analysis phase. Mr. Middlebrooks was the team leader and provided project management. He 

interfaced directly with the customer and worked to ensure that all aspects of the project would 

meet the customer’s expectations. Ms. Swoboda and Ms. Barnette completed the analysis of the 

output data from the model. 
viii 

INTENTIONALLY LEFT BLANK
1 

1. Introduction 

In 1991, the U.S. Army participated in Operation Desert Storm. This engagement resulted in 

long-movement battles (i.e., fast moving battles fought over long distances) in the desert. The 

normal doctrine of tactical operations was not sufficient for the command and control (C2) of an 

operation that moves forward at such a rapid pace. To remedy this problem, the Army proposed 

a C2 vehicle (C2V) that would take the place of the “typical” maneuver battalion tactical 

operations center (TOC). Soldiers performing C2 functions would remain in the vehicle and 

perform these functions while moving along the battlefield if necessary. A method was needed 

to determine if the human operator could perform C2 tasks while moving. 

A multi-year research and development effort was undertaken by the Human Research and 

Engineering Directorate of the U.S. Army Research Laboratory (ARL) to assist the U.S. Army 

Armor Center in evaluating trade-offs between various configurations of Soldiers and equipment 

in the C2 environment. The work consisted of a series of phases (e.g., task-network design, 

performance data collection, model programming, etc.), which resulted in a number of computerbased C2 models. Several human performance simulation models were developed to represent 

maneuver unit C2, starting with a baseline model to reflect the battalion command post of that 

time period and then several alternatives, each designed to portray selected variations in unit 

personnel, equipment, and organizational dynamics. At the completion of that effort, two of the 

models built were identified for use in the evaluation of the impact of Soldiers conducting their 

C2 functions in a moving vehicle. 

The objective of the second effort was to model C2 Soldier task performance and workload in a 

“typical” maneuver battalion task force configuration for the Army at that time via a computerbased application environment for modeling. Then, with the same basic methods, we would 

build a model of a battalion outfitted with C2Vs. The models were to be used to assess the 

efficiency of information flow and task loading during a 24-hour long-movement mission. The 

model runs were to be used for comparative “what if” analyses to determine the impact of 

Soldiers conducting their C2 functions in a moving vehicle. These models do not predict exact 

results; however, the analyses of the different movement profiles can be compared to assess the 

effect of C2 in a moving vehicle. The objective of this report, in particular, is to describe these 

models and to document their development. No model runs or data analysis are provided in this 

report. 
2 

2. Preliminary Task Analysis 

The first step in creating a “good” human performance model (HPM) is task analysis. A 

thorough task analysis is needed to adequately represent the human operator in the HPM. Task 

analysis can be performed in many different ways, depending on the purpose and how the results 

are to be used. Task and task flow data were gathered for the model development process. 

Many resources were used to determine the task and task flows conducted in a TOC during a 

long-movement mission (24 hours). These included subject matter experts, training manuals, 

doctrine, standing operating procedures, and many other sources (Kilduff et al., 1999). The 

information gathered from all these sources was consolidated into a basic task and work flow 

diagram shown in figure 1. The task and work flow are representative of collective 

accomplishments in each of the staff sections or battlefield operating system and individual 

accomplishments by each operator. 

Acknowledge Message

Compare to Picture

Noise

?

No

Yes File Msg

What

Action

?

Estimate Impact

Add to Picture

Request Info

Make Recommend.

Pass Info

?

Communicate Out Adjust Plan

Issue Order

Plan Approve

No

Yes

Message

Event

Communicate Out

Input Input

Output Output

Process Process

1

2

6

5

8 9

10

3

4

7

Figure 1. Work flow diagram for a staff section (adapted from Knapp et al., 1997). 

Figure 1 shows the tasks associated with information processing and the resultant actions. The 

diagram begins at task 1. A message or piece of information is received by the TOC. It is 

acknowledged and compared to what is currently known, and a decision is made about any 

additional action. If the message is a request for information as shown by the “Request 

Information” box, the result goes directly to “Communicate Out.” The information may be 
3 

needed to revise the battlefield picture before it is passed to someone else. If the message 

contains relevant information, the operator must determine the impact and make another 

decision. If the current plan must be adjusted, the operator will convene other staff members in a 

“staff huddle” (Adjust Plan). They will follow a process that includes defining the problem, 

gathering data, finding options, comparing alternatives, making recommendations, and 

communicating their decisions. Upon completion, each flow path returns to task 1, and the 

process begins again. 

3. Detailed Task Analysis 

A detailed task analysis for the TOC was developed from the flow diagram in figure 1. Each of 

the tasks listed in figure 1 was assessed for a description, starting cue, information requirements, 

skills required, operator decisions made, operator actions, system feedback, information sources, 

and difficulties or errors. All this is presented in appendix A. 

Additionally for these models, the skills required by the operators who perform the tasks were 

determined. A taxonomy developed by Fleishman and Quaintance (1984) was used to assign the 

performance data to each task. This taxonomy represents tasks by a subset of 50 total skills and 

abilities. A task is described by the skills required to perform the task and by the level of each of 

those skills. A detailed description of the process for developing the task flow diagram and how 

the skill and ability data were attributed to each task is given in Kilduff et al. (1999). 

This task flow was built into a model via a computer-based simulation package called 

MicroSaint1 to determine such things as how much time messages require to be processed or 

where operators spend most of their time. A scenario of actual messages coming into the TOC 

during a 24-hour long-movement mission drives this model. By comparing the task, task times, 

skill and ability of the Soldiers during this mission while they are stationary and moving, we can 

measure the impact on the operator of performing C2 functions during movement. 

This type of analysis is useful but limited. The time for each task will vary with the message and 

message content. It is easy to describe the flow of tasks for each message; however, the dynamic 

nature of the C2 environment would not be captured. In actuality, C2 personnel can receive 

several messages in a short time span. To capture these dynamics, the interruptions and rerouting on the flow path (because of the number and time of each message entering the TOC) 

need to be determined. Messages flow into the TOC and are processed. Messages may enter at a 

rate that prevents operators from completing one before having to work on the next. To account 

for multiple messages, interruptions, and loss of information, the model must have rules for 

message priority and for handling priority. These rules were also collected from the same 

 1MicroSaint is a trademark of MicroAnalysis and Design.
4 

multiple sources as the task analysis. They are the assumptions that are used to develop the 

model. 

4. Task Analysis by Operator and Staff Section

The battalion TOC is responsible for C2 with 24 personnel represented. Figures 2 and 3 

represent the staff sections included in the analyses. Figure 2 is a representation of an analog 

TOC or one in which all communication is by radio or voice. Figure 3 represents a digital TOC 

or one in which digital equipment has been added for communicating information. Personnel in 

each of the sections are listed inside the box for that section. See table 1 for personnel 

definitions. The radio nets or equipment associated with each section are listed to the immediate 

left or right of that section. Generally, in each of the five functional areas2, the messages arrive 

by various radio nets and are written on formatted message pads and logged into a log book by a 

designated radio-telephone operator (RTO). The RTO then passes the message to the next senior 

person within his or her section by distributing the message to the next senior person’s in-box or 

by interrupting the person and speaking the message. The next senior person may also be 

monitoring the radio to filter messages; s/he distributes messages to other sections as deemed 

appropriate, scans map and status boards for changes, and makes the changes on the basis of 

message traffic. Map revisions or changes are made with “stickies” (similar to “post-it” notes) 

posted on map overlays; personnel make status board changes by erasing information and 

rewriting it. If a third (more senior) person is in a section, this individual monitors radios, scans 

map and status boards, decision support templates, and other action lists such as the 

commander’s critical information requirements. In addition, this person estimates the impact of 

the changes, makes decisions, may initiate staff huddles, and directs actions in the form of verbal 

orders or radio messages sent. In the two-person section, the senior person estimates the impact 

of the changes, makes decisions, may initiate staff huddles, and directs actions in the form of 

information sent. In the digital TOC, the same process occurs with some messages received and 

sent via the digital systems versus the radio nets. 

 2

intelligence staff section [S2], operations staff section [S3], fire support element [FSE], engineer staff section 

[ENG], and air liaison officer [ALO] sections
5 

Figure 2. Analog TOC diagram. 

Figure 3. Digital TOC diagram. 

S3

BC

Asst Ops Sgt

NBC NCO

Drvr/RTO

C2V

FSE

FS Sgt

Drvr/RTO

C2V*

ENG

Co XO

RTO

C2V*

S2

S2

Asst. S2

Intel Sgt

Intel Analyst

M1 or M2 C2V

Internal Interactions

Voice (ftf)

Paper and Pad

Digital

CTCP

S4

S1

Pers/Adm Sgt

Asst Supply Sgt

M577

TOC

Bn Cmd

Loader

Gunner

M1 or M2

S3

Loader

Gunner

CMD GRP

HMMWV

ALO

ALO

HMMWV

XO

XO

Bde Cmd

TF Cmd

TF A/L

TF O&I

MCS

Bde O&I

TF Cmd

TF O&I

ASAS

TF Cmd

En Bn Cmd

En Co Cmd

TF O&I

FBCB2

Bde Cmd

TF A/L

FBCB2

TF Cmd

TF O&I

TF Cmd

TF FD

DS FA Bn Ops

DS FA Bn Cmd

AFATDS Bde A/L

TF Cmd

TF A/L

CSSCS

Bde Cmd

TF Cmd

TF O&I

FBCB2

Bde Cmd

TF Cmd

TF A/L

FBCB2

* One Vehicle
6 

Table 1. List of personnel in battalion tactical operation center as modeled. 

Section Definition Personnel Definition 

S1 Personnel Section S1 Personnel Officer 

 Per/Adm Sgt Personnel and Administrative Sergeant 

S2 Intelligence Section S2 Intelligence Officer 

 Asst S2 Assistant Intelligence Officer 

 Intel Sgt Intelligence Sergeant 

 Intel Analyst Intelligence Analyst 

S3 Operations Section BC Battle Captain 

 Asst Ops Sgt Assistant Operations Sergeant 

 NBC NCO Nuclear, Biological, and Chemical Non-Commissioned Officer 

 Drvr/RTO Driver/Radio Telephone Operator 

S4 Supply Section S4 Supply Officer 

 Asst Supply Sgt Assistant Supply Sergeant 

FSE Fire Support Section FS Sgt Fire Support Sergeant 

 Drvr/RTO Driver/Radio Telephone Operator 

ENG Engineer’s Section Co XO Engineer’s Company Executive Officer 

 RTO Radio Telephone Operator 

ALO Air Liaison Section ALO Air Liaison Officer 

Other XO Battalion Executive Officer 

M1 or M2 Commander’s Vehicle Bn Cmd Battalion Commander 

 Loader Vehicle Loader 

 Gunner Vehicle Gunner 

M1 or M2 S3’s Vehicle S3 Operations Officer 

 Loader Vehicle Loader 

 Gunner Vehicle Gunner 

The combat train’s command post (CTCP) is responsible for issuing periodic status reports and 

keeping copies of maps and status boards representing the S3 data. The CTCP has two RTOs. 

One RTO monitors the brigade and the battalion administrative/logistics (A/L) net for personnel 

messages, and the other RTO monitors both A/L nets for logistics messages. Both pass information to the next senior person, who in turn, revises the boards. In the digital TOC, one RTO 

monitors the digital traffic and one operates the radio for personnel and logistics messages.

In his/her vehicle, the commander periodically scans the battlefield, looking at the synchronization 

of his/her forces against the opposing force. S/he monitors the radio and keeps a knee board (small 

map/status board). The loader jots messages from the battalion command net, while the gunner 

monitors the brigade net for the commander’s call sign. The S3 operates in a similar method in his 

or her vehicle. The commander also monitors the digital system for information in the digital TOC.

4.1 Configurations 

4.1.1 Analog 

As shown in figure 2, the battalion task force C2 consists of three “nodes” that encompass eight 

command and staff elements. The command group node consists of six Soldiers in two vehicles, 

including the commander. The C2 TOC consists of 14 Soldiers partitioned into five staff 
7 

sections (S3, S2, fire support, engineer, and ALO) and includes an executive officer (XO). 

Finally, a stand-alone support operations node consists of four Soldiers who conduct S1 and S4 

operations. Altogether, 24 Soldiers are modeled: 11 officers, five junior officers or noncommissioned officers (NCOs), and eight enlisted personnel. 

4.1.2 Digital 

As shown in figure 3, the battalion C2V configuration consists of the same three “nodes” and 

eight command and staff elements. They are, however, divided among seven vehicles 

encompassing command group M1s or M2s, three C2Vs, and two high mobility multipurpose 

wheeled vehicles (HMMWVs). The command group consists of six Soldiers in two vehicles, 

including the commander. The C2 TOC consists of 14 Soldiers using three C2Vs for operations, 

intelligence, fire support, engineering, and HMMWVs for the XO and ALO. A M577 is 

dedicated for administrative and logistics operations, with four Soldiers. Altogether, 24 Soldiers 

are modeled: 11 officers, five junior officers or NCOs, and eight enlisted personnel. Digital 

equipment has also been added. 

4.2 Personnel 

Each operator or Soldier in the TOC is listed in tables B-1 and B-2 in appendix B for the analog 

and digital models, respectively. Included in these tables are the section, person, equipment that 

the person interfaces with, and the tasks for which that person is responsible. 

4.3 Scenario 

The simulation is driven by a force-on-force operation occurring over 24 hours and consisting of 

voice messages or digital information traffic expected to occur during this type of mission. The 

scenario input includes the time each message occurs, where it is received and who receives it, as 

well as the subsequent routing and task flow initiated by the message. Tasks performed in 

response to messages that are from an external source (usually a radio or from a co-worker) are 

considered “reactive”. In addition to external voice messages, the scenario file also contains 

“internal information messages” that are mental “triggers” for personnel to periodically perform 

“proactive” (self-initiated) tasks that are an essential part of C2 operations. Examples of these 

proactive tasks are situation assessment checks, contacts and discussions with other personnel, 

and preparation of status reports. The complete message scenario list for both the digital and 

analog models is provided in appendix C. 

5. Model Development 

At the completion of the task analysis, it was necessary to develop a human performance model 

to represent this process. In order to represent this process in a flexible and useful manner for 
8 

answering the questions proposed by Operational Test and Evaluation Command (OPTEC), 

input data were characterized as described in the following sections. 

5.1 Operator Data 

Operators were categorized according to the type of tasks completed. There are 17 operator 

types in a typical battalion TOC. For example, RTOs in the S3, S2, and FS sections are all 

considered “Operator Type – RTO.” Table 2 is a list of operator types. Table 3 is a list of the 

Soldiers in the model, the identifying number of the operator in the model, and their operator 

type. 

Table 2. Operator types used in the model. 

Operator Type 

Type 

Identifier 

Commander 1 

XO 2 

S1 3 

S2 4 

S3 5 

S4 6 

BC 7 

ENO 8 

ALO 9 

FSO 10 

S1NCO 11 

S2NCO 12 

S3NCO 13 

S4NCO 14 

NBCNCO 15 

FSNCO 16 

RTO 17 

5.2 Task Data 

Every task in the model that accounts for time worked is categorized as one of 32 detailed job 

functions (DJFs). The DFJs are listed in table 4. Therefore, skill and ability data are entered in 

the model for each task, according to which operator type and DJF are associated with that task. 

Data required for each task include the operator(s) who can perform the task, time to perform the 

task, whether the task can be interrupted, and to which DJF the task corresponds. A complete list 

of tasks and associated parameters such as operator, DJF, task time, task interrupt type, and task 

weighting is given in appendix D. Task interruption types determine if a task can or cannot be 

interrupted and if interrupted, whether it will be restarted. Task weightings are used in the 

calculation of the skill and ability totals for the operator-task combination. 
9 

Table 3. Model operator and operator type assignments. 

Operator Name Operator 

Number 

Operator Type 

S1NCO 1 11 

S1 2 3 

 3 

S2RTO 4 17 

S2NCO 5 12 

S2A 6 4 

S2O 7 4 

 8 

S3RTO 9 17 

NBCNCO 10 15 

S3NCO 11 13 

BC 12 7 

XO 13 2 

 14 

S4NCO 15 14 

S4 16 6 

 17 

ALO 18 9 

 19 

FSRTO 20 17 

FSO 21 10 

 22 

 23 

ENRTO 24 17 

ENO 25 8 

 26 

CDRLDR 27 17 

CDRGNR 28 17 

CDR 29 1 

 30 

S3VLDR 31 17 

S3VGNR 32 17 

S3V 33 5 

5.3 Task Degradation Data 

Research completed at ARL indicates that task time and performance degrade over time while 

cognitive tasks are completed in a moving vehicle (Schipani, Bruno, Lattin, King, & Patton, 

1998). Data from this study were used to determine the rate at which task times would increase 

as a function of length of time that the vehicle has been moving and predominant skill demand 

required in completing that task. Predominant skill demand was determined from the DJF for 

each task. A description of the process used to calculate degradation rates in given in Schipani 

(1998). The rate at which each of the DJFs degrades by hour in a moving vehicle is given in 

appendix E. 
10 

Table 4. Detailed job functions used in the models. 

Top Level Function Detailed Job Function (DJF) 

1 – Receive and Record (Analog) 

2 – Pass Information 

3 – Listen, Receive Information 

4 – Secondary Monitor 

5 – Log Message 

6 – Route (outside the section) 

7 – Send Message 

8 – Verbal Order 

9 – Roll up Reports 

10 – Call to Conference 

26 – Receive Digital Message 

27 – Input Data into Computer 

Communicate and Report 

28 – Send Digital Information 

11 – Decide Action 

12 – Decide 

Decide and Recommend or Direct 

13 – Recommend Action 

14 – Estimate Impact 

15 – Data Gathering (Analog) 

29 – Data Gathering (Digital) 

16 – Find Options 

17 – Compare Alternatives 

Evaluate and Estimate Impact 

18 – Discuss 

19 – Read (Analog) 

30 – Read (Digital) 

20 – Scan 

21 – Update (Analog) 

22 – Check Status 

23 – Problem Definition 

24 – Listen / Monitor (Analog) 

31 – Scan Digital 

Identify or Understand Situational Picture 

32 – Monitor Digital 

Manage Resources 25 – Manage Resources 

5.4 Scenario Data 

As these messages are fed into the model, the simulation determines which tasks will be done 

and in which order. The task flow described by figure 1 is built into the model. The tasks are 

human operator tasks performed by people. The variables or attributes of the message determine 

the path that the message will take, therefore initiating the tasks associated with that path. When 

messages overlap or interrupt each other, priorities are determined by the routing characteristics 

of the message. Skill and ability demands associated with each task are then collected over time. 

Operator performance indicators such as utilization measures (number of messages processed, 
11 

number of messages dropped, number of interruptions, etc.) and task processing times can be 

compared with other simulated conditions. 

There are many fields describing each message in the scenario. Some are used in the model and 

some are used only in following the tactical situation. Fields that are of use in the simulation are 

event time, where the message enters the model, to whom the message is intended, if and whom 

should be interrupted, routing variables that indicate the path the message will take and tasks it 

will initiate, and the number of words included in the message. Other data fields such as whom 

the message is from, the text of the message and the scenario elapsed time, are used to determine 

what handling (i.e., routing variables) should be assigned to the message. A definition of the 

routing variables and the options for each are given in appendix F. 

5.5 Application Constructs and Assumptions 

The way in which multiple concurrent tasks are completed needed to be defined to best represent 

what happens during information processing. There are several different theories about how 

multiple tasks are handled by humans. In this model, an assumption was made that operators 

would only complete one task at a time, except for listening to or monitoring the radio. This task 

can be done in parallel with any other task. The model is coded so that at the completion of the 

monitoring task, if the operator is not performing any other task, s/he will continue to process the 

monitored message. If the operator is performing another task, it is assumed that s/he would 

attend to the current message and continue with that task. The new information from the 

monitored task will be passed to him or her later. 

Task interruptions happen frequently in real life and in the simulation. Rules were required to 

determine how the interruptions would be handled. Each task is assigned an “Interrupt Type”. 

Tasks of type 0 can be interrupted and do not need to be restarted. Tasks of type 1 can be 

interrupted, but the model should attempt to restart the task. Tasks of type 2 cannot be 

interrupted. Type 2 are tasks such as talking on the radio or talking to another individual. When 

an operator is interrupted, s/he will suspend the message being worked on and will receive the 

new message. At that point, the operator will compare the priority of the suspended message and 

the new message and continue with the higher priority message. The other will be suspended. If 

an operator already has a suspended message and is interrupted again, the lower priority message 

will be dropped and the higher priority message will be suspended. Once an operator has 

successfully completed the required tasks on a message, s/he will restart a suspended task if there 

is one. If not, the operator will begin working with any queued messages.

The priority of each message was determined by routing variables assigned to that message. The 

model looks at the routing variable of estimate impact and staff huddle. A message that triggers 

a staff huddle has the highest priority. A message that requires “estimate impact” but no staff 

huddle has the next highest priority. A message that does not trigger “estimate impact” or staff 

huddle has the lowest priority. If two messages have the same priority, the more recent message 

is considered to be the higher priority message.
12 

Staff huddles are triggered by messages that require group input and consensus. The operator 

who receives the message initiates a staff huddle. S/he interrupts the XO and explains the 

problem to the XO. The XO calls the commander on the radio and discusses the information 

with him or her. They decide who should be involved in the huddle, and the XO interrupts those 

staff officers and calls them to conference. A minor staff huddle consists of the XO, BC, and the 

S2O. A major huddle additionally includes the FSO, the ENO, and the ALO. The officers meet 

and perform a series of tasks that include problem definition, data gathering, finding options, 

comparing alternatives, and reaching a decision. The XO then calls the commander on the radio 

and gets his or her approval for the new course of action. The XO then gives the staff officers 

final direction, and everyone returns to their appropriate tasks.

Proactive tasks, as previously described, are called “internal triggers”. When operators use this 

type of message to communicate with other operators in the model, the originator interrupts the 

receiver. The receiver listens, discusses the information, and then returns to his or her section 

and processes the information according to the routing logic assigned to that message.

The models do not track message content. Message type, content, and context are used before 

simulation to determine how operators would handle messages. Routing variables are then 

established for input into the model. In the simulation run, the content of the message is not 

addressed. Operators are assumed to correctly perform the tasks they are triggered to perform. 

If a task is triggered, it will be finished and assumed to be finished correctly unless interrupted.

Queues are used in the model to measure the time that messages are waiting to be processed. 

Some queues represent actual physical locations such as an in-box or a stack of messages to be 

logged. Some are operators waiting to interrupt other operators and still others represent waiting 

for an operator or radio net to become available. The times for the “wait” queues are given in 

the task lists for the models (see appendix D). 

The simulation will determine the flow of messages and the interaction between each message, 

based on the routing variables. This means that messages can be delayed from their ideal path 

and processing time because of interruptions, operator availability, or radio net availability. For 

these reasons, messages or events may not be handled in a timely fashion. If a message is 

overcome by events, it is dropped from processing and the reason is recorded. The specific 

reasons are

• in a queue too long,

• taking too long to reach a specific place in the process, 

• interrupted and not restarted,

• proactive task that was not started because operator was working on other tasks.

The following diagrams (see figures 4 through 9) show the message-handling path for each of 

the sections in the model and staff huddle. The figures show the tasks that can be triggered and 
Figure 4. Command group (commander and S3 in their vehicles) task networks. 

Q - Queue existsQD - Can be dropped if in queue too longW - Waiting for Operator availabilityWD - Will be dropped if operator unavailableMessages can be dropped from any of the interruptible tasks if the operator is interrupted by two othermessages before restarting.

Receive

and

record

Secondary 

Monitor

Listen/

Monitor

Pass

Info

Scan Decide Estimate Impact Update Send Radio Message

Discuss

Decide

Internal

Trigger

D

Listen Receive

Pass

Info D

P

Q

QD

QD

WD

P - Can be dropped if in process too long - Interruptible tasks - Non-interruptible tasks - Not restarted if interruptedCommand Group

Scan

Digital

Database

See Icon

Movement

Read

Digital

Message

Estimate

Message

Impact

Send

Overlay

Compose

Digital

Message

Send

Radio

Message

Enter

Voice Data

Into Digital

Q

WD

Q

Listen

Receive Discuss

Decide Check Status

Loader’s tas

Receive

and

record

Q

Listen

Receive

Pass

Info

WD

Gunner’s tas

13 
Figure 5. S2 and S3 task networks. 

Receive

and

record

Secondary 

Monitor

Log 

Message

Listen/

Monitor

Pass

Info

Listen

Receive

Scan Decide Route Listen

Receive

Listen/

Monitor

Estimate

Impact Scan Decide

Pass

Info

Update

Listen

Receive

Pass

Info Read Decide

Read

From Staff

Huddle

Internal

Trigger

Listen Receive

Pass

Info 

P P

QD

Q

QD

Q

QD

Q

WD

WD

W

S2 and S3 Sections

Scan

Digital

Database

See Icon

Movement

Read

Digital

Message

Take Down

And Pass

Estimate

Message

Impact

Pass

Info

Listen

Receive

Send

Overlay

Compose

Digital

Message

Send

Radio

Message

Enter

Voice Data

Into Digital

Q

W

W

Q - Queue existsQD - Can be dropped if in queue too longW - Waiting for Operator availabilityWD - Will be dropped if operator unavailableMessages can be dropped from any of the interruptible tasks if the operator is interrupted by two othermessages before restarting.

P - Can be dropped if in process too long - Interruptible tasks - Non-interruptible tasks - Not restarted if interrupted

Q

Dual

Estimate

Impact

S2 Section O

14 
Figure 6. Fire support and engineer task networks. 

Q - Queue existsQD - Can be dropped if in queue too longW - Waiting for Operator availabilityWD - Will be dropped if operator unavailableMessages can be dropped from any of the interruptible tasks if the operator is interrupted by two othermessages before restarting.

Receive

and

record

Secondary 

Monitor

Log 

Message

Listen/

Monitor

Pass

Info

Listen

Receive

Scan Decide Route Estimate Impact

Update

Listen

Receive

Pass

Info Decide

Read

To Staff

Huddle

From Staff

Huddle

Internal

Trigger

Listen Receive

Pass

Info 

P

QD

Q

Q

QD

Q

WD

WD

P - Can be dropped if in process too long - Interruptible tasks - Non-interruptible tasks - Not restarted if interruptedFS and EN Sections

Scan

Digital

Database

See Icon

Movement

Read

Digital

Message

Estimate

Message

Impact

Send

Overlay

Compose

Digital

Message

Send

Radio

Message

Enter

Voice Data

Into Digital

Q

W

Call for

Fire

Estimate

Impact 

of Fire

To Update

Fire Support Only

Q

Receive

Target

Location

15 
Figure 7. XO and ALO task networks. 

Q - Queue existsQD - Can be dropped if in queue too longW - Waiting for Operator availabilityWD - Will be dropped if operator unavailableMessages can be dropped from any of the interruptible tasks if the operator is interrupted by two othermessages before restarting.

Listen/

Monitor Scan Decide Estimate Impact Send Radio Message

Internal

Trigger

Discuss Listen Receive

Pass

Info Discuss

Q

QD

QD

WD

P - Can be dropped if in process too long - Interruptible tasks - Non-interruptible tasks - Not restarted if interruptedXO and ALO Sections

Scan

Digital

Database

See Icon

Movement

Read

Digital

Message

Estimate

Message

Impact

Send

Overlay

Compose

Digital

Message

Send

Digital

Message

Send

Radio

Message

Listen/

Monitor

Pass

Info

Listen

Receive

Scan Update

Send

Radio

Message

Read

P

QD

W QD

Listen/

Monitor

XO

ALO

16 
Figure 8. Staff huddle task networks. 

Pass

Info

Listen

Receive

Listen

Receive

Pass

Info

Compare

Alternatives

Find

Options

Data

Gathering

Problem

Definition

Discuss Listen Receive

Pass

Info Discuss

W W

Staff Huddle

Pass

Info

Listen

Receive

W

Q - Queue existsQD - Can be dropped if in queue too longW - Waiting for Operator availabilityWD - Will be dropped if operator unavailableMessages can be dropped from any of the interruptible tasks if the operator is interrupted by two othermessages before restarting.

P - Can be dropped if in process too long - Interruptible tasks - Non-interruptible tasks - Not restarted if interrupted

DiscussDiscuss

Listen

Receive

Pass

Info

W

Decide

From

Above

Staff Huddle

participants

interrupted 

one at a time.

CommanderAll Participan

17 
Figure 9. CTCP task networks. 

Q - Queue existsQD - Can be dropped if in queue too longW - Waiting for Operator availabilityWD - Will be dropped if operator unavailableMessages can be dropped from any of the interruptible tasks if the operator is interrupted by two othermessages before restarting.

Receive

and

record

Listen/

Monitor

Pass

Info

Listen

Receive

Scan Decide E

Update

Send

Radio

Message

Listen

Receive

Pass

Info

Read

Internal

Trigger

Listen Receive

Pass

Info 

P

QD

Q

QD

QD

WD

WD

P - Can be dropped if in process too long - Interruptible tasks - Non-interruptible tasks - Not restarted if interruptedCTCP Section

Scan

Digital

Database

See Icon

Movement

Read

Digital

Message

Estimate

Message

Impact

Send

Overlay

Compose

Digital

Message

Send

Radio

Message

Enter

Voice Data

Into Digital

Q

Q W

Estimate

Impact

Roll-Up

Reports

Update

18 
19 

the order in which they would happen. Not all tasks are triggered by every message. Specific 

tasks triggered by individual messages are determined by routing variables. These diagrams 

display the locations of the queues and indicate where and why messages can be dropped. 

Again, messages are dropped if they have taken too long to reach a certain task in the process or 

if they have spent too much time in a queue. The maximum waiting times for the queues and the 

“in process too long” drops are given in table 5. The tasks in these figures are each assigned a 

mean time with a standard deviation of 10%. A normal distribution is used for task time 

selection. 

Table 5. Queue and “in process too long” times. 

Section Operator Location Time (seconds) 

CTCP S1 Scan “in process too long” 900 

ALO ALO Read queue 800 

ALO ALO Scan “in process too long” 900 

S3 NCO Read queue 900 

S3 NCO Scan “in process too long” 900 

S3 BC Scan “in process too long” 1200 

S2 NCO Read queue 800 

S2 NCO Scan “in process too long” 900 

S2 S20 OR S2A Scan “in process too long” 1200 

FS FSO Read queue 800 

FS FSO Scan “in process too long” 900 

EN ENO Read queue 800 

EN ENO Scan “in process too long” 900 

CMD CDR Scan “in process too long” 900 

CMD CDR Check status time 800 

S3V S3 Scan “in process too long” 900 

S3V S3 Check status time 800 

6. Conclusions 

A good task analysis is critical to good human performance modeling. Understanding the 

functions and tasks that the human is expected to perform is the core of the human performance 

model. In this case, the operators involved in the battalion TOC perform many tasks. A human 

performance model that represents 24 individuals and the multiple numbers of tasks that they 

perform is a huge undertaking, particularly in a C2 environment. The described input to the 

models shows how the characteristics of the tasks and of the people were represented in the 

models. The detailed task analysis provided the basis of the work system so that the necessary 

assumptions for this analysis could be implemented in the simulations. The issues of interest or 
20 

questions to be answered for OPTEC led to this specific application. It is important that these 

input and assumptions be documented as they apply to this use of the task analysis. The basic 

task analysis will not change if the questions to be answered change, but the means of 

representing the tasks or people in the model could change. Documentation of the applications 

helps to prevent use of the models for issues that the models cannot adequately address. 
21 

7. References 

Fleishman, E. A.; Quaintance, M. K. Taxonomies of human performance. The description of 

human tasks. Orlando, FL: Academic Press, 1984. 

Kilduff, P. W.; Wojciechowski, J. Q.; Knapp, B. G.; Barnette, B. D.; Middlebrooks, S. E.; 

Swoboda, J. A validation of the methodology used in building the command and control (c2) 

baseline model; (unpublished manuscript); U.S. Army Research Laboratory: Aberdeen 

Proving Ground, MD, 1999. 

Knapp, B.; Johnson, J.; Barnette, D.; Wojciechowski, J.; Kilduff, P.; Swoboda, J. Information 

Management and Workload Modeling for the Command and Control Vehicle (C2V) and 

Force XXI Battle Command Concepts, Vols. 1 and 2; (unpublished manuscript); US Army 

Research Laboratory: Aberdeen Proving Ground, MD, 1997. 

Micro Analysis & Design, Inc. MicroSaint 3.0. Boulder, CO: Author, 1998. 

Schipani, S. P.; Bruno, R. S.; Lattin, M. A.; King, B. M.; Patton, D. J. Quantification of 

cognitive process degradation while mobile, attributable to the environmental stressors 

endurance, vibration, and noise; ARL-TR-1603; U.S. Army Research Laboratory: 

Aberdeen Proving Ground, MD, 1998. 

Schipani, S. Rationale for the Construction of Model Weighting Coefficients, proposed for Use 

in Adjusting to Reflect (Human) Performance Degradation due to Motion while considering 

Fleishman Skill & Ability ‘Categories’, within the ARL-HRED ‘Workload’ Model. White 

paper, July 1998 
22 

INTENTIONALLY LEFT BLANK
Table A-1. Task analysis of TOC. 

Task Description Start Cue Information 

Requirements 

Skills Used and 

Operator Decisions 

Operator 

Actions 

System Feedback Informatio

Sources 

1. Acknowledge Message 

Operator responds to an incoming radio message, digital message, or person speaking to him or her. Operator records pertinent information contained in the message. 

Hear call sign on the radio or hear name called or cued that a new digital message is received. 

Operator needs to know what his or her call sign is. Operator needs to know how to operate the radio or digital equipment. Operator needs to know proper protocol for radio traffic. 

Operator uses auditory, perceptual and cognitive skills to interpret message and distinguish pertinent information. Operator used psychomotor and visual skills to operate the radio or computer and record the pertinent information. 

Operator hears call sign or name or sees indication of new digital message. Operator responds. Operator listens to or reads message and records appropriate information. Operator signs off. 

Auditory feedback from the radio and the sender. Tactile feedback from the radio controls. Visual feedback from the message record and writing or computer screen. Tactile feedback from the writing instrument or keyboard. 

Training resources. Manuals for the radio andigital systeOther personnel in the TOC. 

2. Compare to Picture 

Operator reads the message and looks at the current state of the battle-field to compare and decide what further action is required. 

Information is received from the radio, digital or verbal message. 

Operator needs to know where to look to find the current state of the battle-field. Operator needs to understand the informa-tion in the message. 

Operator uses visual, perceptual, and cognitive skills to read message, assimilate the information and compare to the current state. 

Operator reads message or listens to RTO Operator scans map and/or status board to compare to what is already known. Operator may consult additional resources such as critical events list, decision support template, etc. Operator decides what further action is required on this message. 

Visual feedback from displayed informa-tion. 

Training resources. Maps. Status BoardOther writtedocumentation. Other personnel in the TOC. 

23 
3. File 

Message 

Operator logs the incoming message. 

No further action is required for this message. 

Operator needs to know where the log is. Operator needs to know how to properly log incoming messages 

Operator uses visual, perceptual, and cognitive skills to determine what is to be entered into the log. Operator uses visual and psychomotor skills to enter that infor-mation 

Operator enters information into the logbook recording this incoming message. 

Visual feedback from the logbook and writing. Tactile feedback from the writing instrument. 

Training resources. Other personnel in the TOC. 

4. Add To Picture 

Operator revises the record of the current state of battlefield. 

Message contains information that changes the situational picture. 

Operator needs to know what part of the picture to revise. Operator needs to know how to revise picture. 

Operator uses visual, perceptual, and cognitive skills to determine what needs to be revised. Operator uses visual and psycho-motor skills to write on the map, board, or other information display or to enter data into computer database. 

Operator may erase and/or write on the status board. Operator may add a new “postit,” move one or remove one from the map. Operator may change an entry in a resource such as a collection plan. Operator may enter data into the digital system. 

Visual feedback from the information display and writing. Tactile feedback from the writing instrument or keyboard. 

Training resources. Other personnel in the TOC. 

5. Communicate Operator transmits 

information to another person(s). 

Operator determines that someone needs this information or interpreta-tion of this information. 

Operator needs to know to whom to transmit message. Operator needs to know how to com-municate this message to desired person(s). If radio message to be sent, operator needs to know how to operate the radio. If digital 

Operator uses auditory, perceptual, and verbal communica-tion skills to transmit this message. Operator uses psycho-motor skills to operate the radio or computer keyboard. 

If message transmitted by radio, operator adjusts radio, delivers call sign of desired recipient, sends message, signs off. If message verbally transmitted, operator calls recipient’s name, 

Auditory feedback from the radio and/or the receiver. Tactile feedback from the radio controls or digital controls. 

Training resources. Manuals for the radio or digital systeOther personnel in the TOC. 

24 
information to be 

sent, operator needs to know how to operate digital system. 

listens for reply and delivers message. If message transmitted digitally, operator must enter correct data and key strokes into the system. 

6. Estimate Impact 

Operator reviews the message and determines the impact of this piece of information on the battle. 

Message requires analysis of the impact on the battle. 

Operator needs to know the current state of the battle. Operator needs to know how to determine the impact of this new information. Operator needs to know where to find additional information. 

Operator uses visual, perceptual, and cognitive skills to interpret information available from many resources. 

Operator checks map and status board to compare current message with displayed state of the battle. Operator analyzes how this message changes what is known about the battle. Operator decides if further input is needed from other personnel in the TOC. Operator decides if other person(s) need this information. 

Visual feedback from the information display and written text. 

Training resources. Maps. Status BoardOther writtedocumentation. Other personnel in the TOC. 

7. Make Recommenda-tions 

Operator cognitively decides what actions should be taken or what message should be relayed. 

Operator completes estimation of the impact of this information on the battle. 

Operator needs to know how this information impacts the battle. 

Operator uses cognitive skills to make decision. 

No actions. No system 

feedback. 

Training resources. Maps. Status BoardOther writtedocumentation. Other personnel in the TOC. 

25 
8. Communicate Operator transmits 

information to another person(s). 

Operator determines that someone needs this information or interpreta-tion of this information. 

Operator needs to know to whom to transmit message. Operator needs to know how to communicate this message to desired person(s). If radio message to be sent, operator needs to know how to operate the radio. If digital information to be sent, operator needs to know how to operate digital system. 

Operator uses auditory, perceptual, and verbal communica-tion skills to transmit this message. Operator uses psychomotor skills to operate the radio or computer keyboard. 

If message transmitted by radio, operator adjusts radio, delivers call sign of desired recipient, sends message, signs off. If message verbally transmitted, operator calls recipient’s name, listens for reply and delivers message. If message transmitted digitally, operator must enter correct data and key strokes into the system. 

Auditory feedback from the radio and/or the receiver. Tactile feedback from the radio controls or digital controls. 

Training resources. Manuals for the radio or digital systeOther personnel in the TOC. 

9. Adjust Plan 

Several operators meet to determine the changes necessary, based on this message. 

An operator has determined that he or she needs input from other TOC personnel to fully analyze the changes in the battle plan required on the basis of this message. 

Need to know which operators are necessary. Need to know what input is available from each operator. Need to know who will direct and lead the discussion. 

Operators use auditory, perceptual, and verbal communica-tion skills to discuss the problem, the options, and reach a decision. Operators use visual and psycho-motor skills to gather data. Operators use visual and cognitive skills to interpret the data. 

Operators are called together by the leader. Operators collectively define the problem, gather data, discuss, find options, and make recommendations. 

Visual feedback from the information display and writing. Auditory feedback from other operators. 

Training resources. Maps. Status BoardOther writtedocumentation. Other personnel in the TOC. 

26 
10. Issue 

Order 

Operator transmits information to another person(s). 

Operator determines that someone needs this information or interpretation of this information. 

Operator needs to know to whom to transmit message. Operator needs to know how to communicate this message to desired person(s). If radio message to be sent, operator needs to know how to operate the radio. If digital information to be sent, operator needs to know how to operate digital system. 

Operator uses auditory, perceptual, and verbal communica-tion skills to transmit this message. Operator uses psycho-motor skills to operate the radio or computer keyboard. 

If message transmitted by radio, operator adjusts radio, delivers call sign of desired recipient, sends message, signs off. If message verbally transmitted, operator calls recipient’s name, listens for reply and delivers message. If message transmitted digitally, operator must enter correct data and key strokes into the system. 

Auditory feedback from the radio and/or the receiver. Tactile feedback from the radio controls or digital controls. 

Training resources. Manuals for the radio or digital systeOther personnel in the TOC. 

27 
28 

INTENTIONALLY LEFT BLANK 
29 

Appendix B: Analog and Digital Model Personnel 

Table B-1. Analog model personnel. 

Section Person Equipment Task Description 

COMMANDER’S 

VEHICLE

Commander

(Cdr) 

Monitors brigade and 

battalion command nets 

and sends messages as 

appropriate, monitors 

task force (TF) 

operations/ intelligence 

(O/I) and fire support 

(FS) nets; knee board. 

Periodically scans the battlefield (at predetermined 

intervals), looking at locations and progress of the 

operations. Listens and talks on battalion command 

net. Gets missed data from Loader. Gunner informs 

Cdr when his or her call sign comes up on the 

brigade net so Cdr can reply to brigade. Maintains 

knee board with key data. Monitors the TF O/I and 

FS nets. In communica-tion with XO on staff 

huddle information. 

Loader

(CdrLDR) 

Battalion command net 

to monitor; note pad 

Monitors the battalion command net, jotting 

information for Cdr. Gives Cdr the data. 

Gunner

(CdrGNR) 

Brigade command net 

to monitor 

Monitors the net, listening for Cdr’s call sign; 

informs Cdr when he or she hears it. 

S3 VEHICLE Operations 

Officer 

(S3 in vehicle 

or S3V) 

Brigade and battalion 

command nets to 

monitor and talk; TF 

O/I and FS nets to 

monitor; knee board 

Periodically scans the battlefield (at predetermined 

intervals), looking at locations and progress of the 

operations. Listens and talks on battalion command 

net. Gets missed data from Loader. Gunner informs 

S3 when his or her call sign comes up on the 

brigade net so S3 can reply to brigade. Maintains 

knee board with key data. Monitors the TF O/I and 

FS nets. Acts as backup to Cdr. 

Loader 

(S3VLDR) 

Battalion command net 

to monitor; note pad 

Monitors the battalion command net, jotting 

information for S3. Gives S3 the data. 

Gunner

(S3VGNR) 

Brigade command net 

to monitor 

Monitors the net, listening for S3’s call sign; 

informs S3 when he or she hears it. 

S3 SECTION Executive 

Officer (XO)

Battalion command 

nets to monitor and 

talk; boards to view 

Serves as TOC officer in charge (OIC). 

Monitors the battalion command net. 

Periodically walks to a section and reviews 

map and boards. Will initiate a discussion 

with person or other staff officers in the 

CTCP or command group. Estimates the 

impact of new information. May initiate a 

staff huddle. Directs all staff huddles. 

Communicates on the radio when appropriate. 

Assumed to be performing other non-modeled 

duties such as integration and 

synchronization of resources. 

Battle 

Captain (BC)

Brigade and battalion 

command nets to 

monitor and talk; 

boards to view 

Serves as TOC OIC during absence of the XO. 

Monitors the radios while performing other duties. 

Scans the status board, map board, decision support 

template, intelligence officer (S2) action board, and 

estimates the impact of message, performing 

analysis of defense strength and weaknesses. Has 

discussion with other staff as appropriate. Decides 

actions and has messages sent by RTO. 

Communicates directly on radio as needed. 
30 

Non-commissioned OIC 

(S3NCO)

Brigade and battalion 

command nets to 

monitor; map board and 

status board, stickies, 

marker and eraser 

Monitors the radio while performing other duties. 

When a message comes in via nets, message stack, 

or verbally from the RTO, he or she scans the map 

and status boards for changes due to message. 

Distributes messages by carrying them to 

appropriate sections and setting message on 

section’s incoming message pile. Revises the map 

by moving, changing, or adding stickies; revises 

the status boards by erasing and writing data with a 

marker. Passes appropriate messages to the BC. 

RTO for 

battalion 

command net

(S3RTO) 

Battalion command net 

to monitor and talk; TF 

O/I and FS nets for 

secondary monitoring; 

pre-formatted, multicopy message pad; log 

book 

Monitors radios and receives and records all voice 

messages on the battalion command net on a preformatted message pad, with a variable message 

length. Tears copy for log and puts on log pile; puts 

rest on the S3NCO’s incoming message pile; 

verbally tells S3NCO when specific important 

messages come in. Logs message when time is 

available. Sends messages upon direction. 

Monitors TF O/I and FS nets as time allows; 

records message. 

RTO for 

brigade 

command net

(NBCNCO) 

Brigade command net 

to monitor; 

preformatted, multicopy message pad; log 

book 

Monitors radios, receives and records all voice 

messages on the brigade command net on a preformatted message pad, with a variable message 

length. Tears copy for log and sets on log pile; puts 

rest on the S3NCO’s incoming message pile; 

verbally tells S3NCO if message is important. Logs 

message when time is available. 

INTELLIGENCE 

(S2) SECTION

Intelligence 

Officer (S2O)

Battalion and brigade 

O/I nets to monitor; 

maps and boards to 

view 

Monitors the radio while performing other duties. 

Scans the status board, map board, decision support 

template, and an S2 action board and estimates the 

impact of message, performing analysis of enemy 

potential. If assistant S2 is available, these two 

individuals will estimate the impact of the message 

and perform analysis of the enemy potential 

together. Tells XO key information, talks to other 

staff as appropriate, may initiate or participate in 

staff huddles. Decides actions and has messages 

sent by RTO. 

Assistant S2 

(S2A)

Battalion and brigade 

O/I nets to monitor; 

maps and boards to 

view 

Monitors the radio while performing other duties. 

Scans the status board, map board, decision support 

template, and an S2 action board and estimates the 

impact of message, performing analysis of enemy 

potential. If S2 is available, these two individuals 

will estimate the impact of the message and 

perform analysis of the enemy potential together. 

Decides actions and has messages sent by RTO. 

Non-commissioned 

officer in 

charge 

(S2NCO)

Battalion and brigade 

O/I nets to monitor; 

map board and status 

board, stickies, marker 

and eraser 

Monitors the radio while performing other duties. 

When a message comes in via nets, message stack, 

or verbally from the RTO, he or she scans the map 

and status boards for changes. Distributes messages 

by carrying them to appropriate sections and setting 

message on section’s incoming message pile. 

Revises the map by moving, changing, or adding 

stickies; revises the status boards by erasing and 

writing data with a marker. Passes appropriate 

messages to the S2. 
31 

RTO 

(S2RTO)

Battalion and brigade 

O/I nets to monitor and 

talk; TF command and 

FS nets to monitor; preformatted, multi-copy 

message pad; log book 

Monitors radios and receives and records all voice 

messages on both the battalion and brigade O/I nets 

on a pre-formatted message pad, with a variable 

message length. Tears copy for log and places on 

log pile; places rest of message copies on the 

S2NCO’s incoming message pile; verbally tells 

S2NCO if message is important. Logs message 

when time is available. Sends messages as directed. 

Monitors TF command and FS nets as time allows; 

records message. 

FIRE SUPPORT Fire Support 

Officer (FSO)

Battalion FD, battalion 

and brigade FS nets to 

monitor; map board and 

status board, stickies, 

marker and eraser 

Monitors the radio while performing other duties. 

When a message comes in via nets, message stack, 

or verbally from the RTO, he or she scans the map 

and status boards for changes. Distributes messages 

by carrying them to appropriate sections and setting 

message on section’s incoming message pile. 

Revises the map by moving, changing, or adding 

stickies. Revises the status boards by erasing and 

writing data with a marker. Estimates impact of 

message, handles calls for fire, and decides action; 

directs message be sent; participates in staff 

huddles. 

RTO 

(FSRTO) 

Battalion FD, battalion 

and brigade FS nets to 

monitor and talk; TF 

command net to 

monitor; pre-formatted, 

multi-copy message 

pad; log book 

Monitors radios and receives and records all voice 

messages on the battalion FD, battalion and brigade 

FS nets on a pre-formatted message pad, with a 

variable message length. Tears copy for log and 

places on log pile; places rest of message copies on 

the FSO incoming pile; verbally tells FSO if 

message is important. Logs message when time is 

available. Sends messages upon direction. 

Monitors TF command net as time allows; records 

message. 

AIR LIAISON Air Liaison 

Officer (ALO) 

Battalion command and 

Air Force nets to 

monitor; map board and 

status board, stickies, 

marker and eraser 

Monitors the radio while performing other duties. 

When a message comes in from nets, message 

stack, he or she scans the map and status boards for 

changes. Revises the map by moving, changing, or 

adding stickies: revises the status boards by erasing 

and writing data with a marker. Informs the XO if 

he or she gets information that impacts the 

operation; participates in staff huddles. 

ENGINEERING 

(EN) 

Engineer 

Officer

(ENO)

Battalion command and 

En Co nets to monitor; 

map board and status 

board, stickies, marker 

and eraser 

Monitors the radio while performing other duties. 

When a message comes in from nets, message 

stack, or verbally from the RTO, scans the map and 

status boards for changes. Distributes messages by 

carrying them to appropriate sections and placing 

message on section’s incoming message pile. 

Revises the map by moving, changing, or adding 

stickies. Revises the status boards by erasing and 

writing data with a marker. Estimates impact of 

message and decides action; directs message be 

sent; participates in staff huddles. 
32 

RTO 

(ENRTO)

Battalion and brigade 

En Co nets to monitor 

and talk; pre-formatted, 

multi-copy message 

pad; log book 

Monitors radios and receives and records all voice 

messages on both the battalion command and En 

Co nets on a pre-formatted message pad, with a 

variable message length. Tears copy for log and 

places on log pile; places rest of message copies on 

the ENO’s incoming pile; verbally tells ENO 

Officer if message is important. Logs message 

when time is available. Sends messages upon 

direction. 

COMBAT 

TRAINS 

COMMAND 

POST (CTCP) 

Logistics 

Officer (S4) 

Battalion and brigade 

A/L nets to monitor; 

map boards and status 

board, stickies 

Monitors both A/L nets for personnel and logistics 

messages while performing other duties. Receives 

information from assistant supply sergeant, revises 

map, estimates impact, makes decisions and directs 

that messages are sent. Coordinates closely with 

the XO. 

Personnel 

Officer (S1)

Battalion command net 

to monitor; map board 

and status board, 

stickies, marker and 

eraser 

Acting as a backup TOC, monitors the battalion 

command net, writing data on stickies and revising 

the map and status board, and performing an 

estimate of the message impact. Receives information from the personnel administra-tive sergeant 

(Pers/Adm Sgt), estimates impact, makes decisions, 

and directs that messages are sent. Coordinates 

closely with the XO. 

Pers/Adm Sgt 

(S1NCO) 

Battalion and brigade 

A/L nets to monitor and 

talk; log/report book 

Monitors radios, receives and records all voice 

messages on both the battalion and brigade A/L 

nets on a pre-formatted log/report , with a variable 

message length. Tears copy for report and places 

rest of message copies on S1’s incoming message 

pile; verbally tells S1 if message is important. 

Assembles a consolidated report on a blank report 

page and sends to brigade when all subordinate 

reports are in. Sends messages upon direction. 

COMBAT 

TRAINS 

COMMAND 

POST (CTCP)

Asst Supply 

Sgt (S4NCO)

Battalion and brigade 

A/L to monitor and 

talk; log/report book 

Monitors radios, receives and records all voice 

messages on both the battalion and brigade A/I nets 

on a pre-formatted log/report, with a variable 

message length. Tears copy for report and places 

rest of message copies on S4 incoming message 

pile; verbally tells S4 if message is important. 

Assembles a consolidated report on a blank report 

page and sends to brigade when all subordinate 

reports are in. Sends messages upon direction. 
33 

Table B-2. Digital model personnel.

Section Person Equipment Task Description 

COMMANDER’S 

VEHICLE

Commander 

(Cdr)

FBCB2 terminal. 

Monitors brigade and 

battalion command nets 

and sends messages as 

appropriate, monitors 

TF, O/I and FS nets; 

knee board.

Reads message traffic and reviews digital overlays 

being routed through the FBCB2 terminal. 

Monitors the radio while performing these duties. 

When a message comes in via FBCB2, he or she 

scans the map and status board for changes due to 

message. Distributes messages by forwarding them 

electronically. Composes digital messages and 

forwards them to appropriate staff. Communicates 

directly on the radio. Periodically scans the 

battlefield (at predetermined intervals), looking at 

locations and progress of the operations. Listens 

and talks on battalion command net. Gunner 

informs Cdr when his or her call sign comes up on 

the brigade net so Cdr can reply to brigade. 

Maintains knee board with key data. In 

communication with XO and TOC operations 

officer on huddle information. 

Loader 

(CdrLDR)

Battalion command net 

to monitor; note pad 

Monitors the battalion command net, jotting 

information for Cdr. Gives Cdr the data. 

Gunner 

(CdrGNR)

Brigade command net 

to monitor

Monitors the net, listening for Cdr’s call sign; 

informs Cdr when he or she hears it. 

S3 VEHICLE Operations 

Officer (S3V)

FBCB2 terminal. 

Battalion command 

nets to monitor and 

talk; knee board 

Reads message traffic and reviews digital overlays 

being routed through the FBCB2 terminal. 

Monitors the radio while performing these duties. 

When a message comes in via FBCB2, he or she 

scans the digital map for changes due to message. 

Distributes messages by forwarding them 

electronically. Composes digital messages and 

forwards them to appropriate staff. Communicates 

directly on the radio. Periodically scans battlefield 

(at predetermined intervals), looking at locations 

and progress of the operations. Listens and talks 

on battalion command net. Gets missed data from 

loader. Maintains knee board with key data. Acts 

as backup to Cdr. 

Loader 

(S3VLDR)

Battalion command net 

to monitor; note pad 

Monitors the battalion command net, jotting 

information for S3. Gives S3 the data. 

Gunner 

(S3VGNR)

Brigade command net 

to monitor 

Monitors the net, listening for S3’s call sign; 

informs S3 when he or she hears it. 
34 

S3 SECTION Executive 

Officer (XO)

FBCB2 terminal. Serves as TOC OIC. Monitors the battalion 

command net. Periodically walks to a section and 

reviews map and boards. Will initiate a discussion 

with person or with other staff officers in the CTCP 

or command group. Estimates the impact of new 

information. May initiate a staff huddle. 

Communicates on the radio when appropriate. 

Reads message traffic and reviews digital overlays 

being routed through the FBCB2 terminal. When a 

message comes in via FBCB2, he or she scans the 

digital map for changes due to message. Distributes 

messages by forwarding them electronically. 

Composes digital messages and forwards them to 

appropriate staff. Performs battlefield integration 

duties such as synchronization of resources; he or 

she is included in and directs all the staff huddles. 

Battle 

Captain (BC)

Battalion and brigade 

command nets to 

monitor and talk; 

boards to view 

Serves as TOC OIC during absence of the XO. 

Monitors the radios while performing other duties. 

Scans the status board, map board, decision support 

template, intelligence officer (S2) action board, and 

estimates the impact of message, performing 

analysis of defense strength and weaknesses. Has 

discussion with other staff as appropriate. Decides 

actions and has messages sent by RTO or via MCSP. Communicates directly on radio as needed. 

Non-commissioned 

officer in 

charge 

(S3NCO)

Battalion and brigade 

com-mand nets to 

monitor; map board 

and status board, 

stickies, marker and 

eraser 

Monitors the radio while performing other duties. 

When a message comes in via nets, message stack, 

or verbally from the RTO or NBCNCO, he or she 

scans the map and status boards for changes due to 

message. Distributes messages by carrying them to 

appropriate sections and setting message on 

section’s incoming message pile. Revises the map 

by moving, changing, or adding stickies; revises the 

status boards by erasing and writing data with a 

marker. Passes appropriate messages to the BC. 

RTO for Bn 

Cmd net 

(S3RTO)

Battalion and brigade 

command nets to 

monitor and talk; TF 

O/I and FS nets for 

secondary 

monitoring; preformatted, multi-copy 

message pad; log 

book 

Monitors radios and receives and records all voice 

messages on the battalion and brigade command 

nets on a pre-formatted message pad, with a variable 

message length. Tears copy for log and puts on log 

pile; puts rest on the S3NCO’s incoming message 

pile; verbally tells S3NCO when specific important 

messages come in. Logs message when time is 

available. Sends messages upon direction. Monitors 

TF O/I and FS nets as time allows; records message. 

NBCNCO MCS-P terminal Reads message traffic and reviews digital overlays 

being routed through the MCS-P terminal. When a 

message comes in via MCS-P, he or she scans the 

digital map for changes due to message. Distributes 

messages by forwarding them electronically. 

Composes digital messages at the command of the 

BC and forwards them to appropriate staff. 
35 

INTELLIGENCE 

(S2) SECTION

Intelligence 

Officer (S2O)

Battalion and brigade 

O/I nets to monitor; 

maps and boards to 

view 

Monitors the radio while performing other duties. 

Scans the status board, map board, decision support 

template, and an S2 action board and estimates the 

impact of message, performing analysis of enemy 

potential. Tells battalion Cdr key information; may 

initiate and participate in staff huddles. Decides 

actions and has messages sent by RTO. If S2A is 

available, these two individuals will estimate the 

impact of the message and perform analysis of the 

enemy potential together. 

Assistant S2 

(S2A)

Battalion and brigade 

O/I nets to monitor; 

maps and boards to 

view 

Monitors the radio while performing other duties. 

Scans the status board, map board, decision support 

template, and an S2 action board and estimates the 

impact of message, performing analysis of enemy 

potential. Decides actions and has messages sent by 

RTO. If S2O is available, these two individuals will 

estimate the impact of the message and perform 

analysis of the enemy potential together. 

S2NCO ASAS terminal. Reads message traffic and reviews digital overlays 

being routed through the ASAS terminal. When a 

message comes in via ASAS, he or she scans the 

digital map for changes due to message. Distributes 

messages by forwarding them electronically. 

Composes digital messages at the command of the 

S2O and forwards them to appropriate staff. 

Composes digital messages at the command of the 

S2O and forwards them to appropriate staff. 

S2RTO Battalion and brigade 

O/I nets to monitor 

and talk; preformatted, multi-copy 

message pad; log 

book 

Monitors radios and receives and records all voice 

messages on both the battalion and brigade O/I nets 

on a pre-formatted message pad, with a variable 

message length. Tears copy for log and places on 

log pile; places rest of message copies on the 

S2O/S2A incoming message pile; verbally tells 

S2O/S2A if message is important. Logs message 

when time is available. Sends messages as directed. 

FIRE SUPPORT Fire Support 

Officer (FSO)

Advanced field 

artillery tactical data 

system (AFATDS) 

terminal, map board 

and status board, 

stickies, marker and 

eraser

Monitors the radio while performing other duties. 

When a message comes in via nets, message stack, 

or verbally from the RTO, he or she scans the map 

and status boards for changes. Distributes messages 

by carrying them to appropriate sections and setting 

message on section’s incoming message pile. 

Revises the map by moving, changing, or adding 

stickies. Revises the status boards by erasing and 

writing data with a marker. Estimates impact of 

message, handles calls for fire, and decides action; 

directs message be sent; participates in staff 

huddles. Reads message traffic and reviews digital 

overlays being routed through the AFATDS 

terminal. When a message comes in via AFATDS, 

he or she scans the digital map for changes due to 

message. Distributes messages by forwarding them 

electronically. Composes digital messages and 

forwards them to appropriate staff. 
36 

FSRTO Battalion FD, 

battalion and brigade 

FS nets to monitor 

and talk; TF 

command net to 

monitor; preformatted, multi-copy 

message pad; log 

book 

Monitors radios and receives and records all voice 

messages on the battalion FD, battalion and brigade 

FS nets on a pre-formatted message pad, with a 

variable message length. Tears copy for log and 

places on log pile; places rest of message copies on 

the FSO incoming pile; verbally tells FSO if 

message is important. Logs message when time is 

available. Sends messages upon direction. Monitors 

TF command net as time allows; records message. 

AIR LIAISON Air Liaison 

Officer 

(ALO) 

Battalion command 

and Air Force nets to 

monitor; map board 

and status board, 

stickies, marker and 

eraser 

Monitors the radio while performing other duties. 

When a message comes in from nets, message stack, 

he or she scans the map and status boards for 

changes. Revises the map by moving, changing, or 

adding stickies: revises the status boards by erasing 

and writing data with a marker. Informs the XO if he 

or she gets information that impacts the operation; 

participates in staff huddles. 

ENGINEERING Engineer 

Officer

(ENO)

FBCB2 terminal, map 

board and status 

board, stickies, 

marker and eraser 

Monitors the radio while performing other duties. 

When a message comes in via nets, message stack, 

or verbally from the RTO, he or she scans the map 

and status boards for changes. Distributes messages 

by carrying them to appropriate sections and setting 

message on section’s incoming message pile. 

Revises the map by moving, changing, or adding 

stickies. Revises the status boards by erasing and 

writing data with a marker. Estimates impact of 

message, decides action, directs message be sent, 

and participates in staff huddles. Reads message 

traffic and reviews digital overlays being routed 

through the FBCB2 terminal. When a message 

comes in via FBCB2, he or she scans the digital map 

for changes due to message. Distributes messages by 

forwarding them electronically. Composes digital 

messages and forwards them to appropriate staff. 

ENRTO Battalion and brigade 

Eng Co nets to 

monitor and talk; preformatted, multi-copy 

message pad; log 

book 

Monitors radios and receives and records all voice 

messages on both the battalion command and Eng 

Co nets on a pre-formatted message pad, with a 

variable message length. Tears copy for log and 

places on log pile; places rest of message copies on 

the Eng incoming pile; verbally tells Eng Officer if 

message is important. Logs message when time is 

available. Sends messages upon direction. 

COMBAT 

TRAINS 

COMMAND 

POST (CTCP) 

Logistics 

Officer (S4) 

Battalion and brigade 

A/L nets to monitor; 

map boards and status 

board, stickies 

Monitors both A/L nets for personnel and logistics 

messages while performing other duties. Receives 

information from asst. supply sergeant and the 

pers/adm sergeant; revises map, estimates impact, 

makes decisions and directs that messages are sent. 

Coordinates closely with the XO. 

Personnel 

Officer (S1)

Battalion command 

net to monitor; map 

board and status 

board, stickies, 

marker and eraser 

Acting as a backup TOC, monitors the battalion 

command net, writing data on stickies and revising 

the map and status board, and performing an 

estimate of the message impact. Receives 

information from the pers/adm sergeant and the asst 

supply sergeant, estimates impact, makes decisions, 

and directs that messages are sent. Coordinates 

closely with the XO. 
37 

Pers/Adm Sgt 

(S1NCO) 

Battalion and brigade 

A/L nets to monitor 

and talk; log/report 

book 

Monitors radios, receives and records all voice 

messages on both the battalion and brigade A/L nets. 

Places message on S1’s or S4’s incoming message 

pile; verbally tells S1 or S4 if message is important. 

Sends messages upon direction. Passes pertinent 

information to the S4NCO for entry into CSSCS. 

Asst Supply 

Sgt (S4NCO)

CSSCS terminal Reads message traffic and reviews digital overlays 

being routed through the CSSCS terminal. When a 

message comes in via CSSCS, he or she scans the 

digital map for changes due to message. Distributes 

messages by forwarding them electronically. 

Composes digital messages at the command of the 

S1 or S4 and forwards them to appropriate staff. 

Assembles a consolidated report and sends to 

brigade when all subordinate reports are in. 
38 

INTENTIONALLY LEFT BLANK
39 
40 
41 
42 
43 
44 
45 
46 
47 
48 
49 
50 
51 
52 
53 
54 
55 
56 
57 
58 
59 
60 
61 
62 
63 
64 
65 
66 
67 
68 
69 
70 
71 
72 
73 
74 
75 
76 
77 
78 
79 
80 
81 
82 
83 
84 
85 
86 
87 
88 
89 
90 
91 
92 
93 
94 
95 
96 
97 
98 
99 
100 
101 
102 
103 
104 
105 
106 
107 
108 
109 
110 
111 
112 
113 

Appendix D. Analog and Digital Task Lists 
114 
115 
116 
117 
118 
119 
120 
121 
122 
123 
124 
125 
126 
127 
128 
129 
130 
131 

Appendix E. Time Degradation Factors 
132 
133 

Appendix F. Message-Routing Variable Definitions 

Message Path Variables

Pass - Set this variable to describe how the message is passed from level of evaluation to the next 

(i.e. from the RTO to the NCO or Officer, and from the NCO to the Officer). 

 0—None 

 1—Paper 

 2—Verbal 

Scan – Set this variable to describe what the soldier will scan to help understand the message. 

The prescribed action is done at the NCO level and the Officer level in the S2 and S3 sections. 

In other sections, it is done at the Officer level. 

 0—None 

 1—Map 

 2—Board 

 3—Map and Board 

 4—All (map, board, decision support template, and critical events list) 

Route (outside of section) – Set this variable to determine if the section receiving the message 

will route a paper copy of this message to other sections. 

 0—No 

 1—Yes 

Update (map or board) - Set this variable to determine if the map or board is updated by this 

message. 

 0—No 

 1—Yes 

Estimate Impact – Set this variable to yes if the message will cause the Officer to evaluate the 

impact of this information on the battle. 

 0—No 

 1—Yes 

Staff Huddle – If the officer will consult with the XO and Commander as a result of his impact 

estimation, set this variable appropriately. A mini staff huddle is the XO, S2O, BC and 

Commander. A Major staff huddle brings FSO, ALO, ENO into the discussion of the issue. 
134 

 0—None 

 1—Mini 

 2—Major 

Send - As a result of the incoming message, some output may be sent out of the section. If the 

output is a radio message, set the variable to one. If a digital message is to be sent, set the 

variable to two. If a digital overlay is to be forwarded to another section, set the variable to 

three. If the officer is going to interrupt the NCO and give him instructions and send a radio 

message, set the variable to four. 

 0—None 

 1—Radio 

 2—Digital 

 3—Overlay 

 4—Verbal Order and send radio message 

Enter Radio Message/Unformatted Message – Set this variable to yes if the information in a 

radio message is to be entered into the digital database, or if a digital message must be 

reformatted in order to be stored in the database. 

 0—No 

 1—Yes 

Words 

 Enter # or words in message 

Digital Message Type – This distinguishes the way a digital message is handled. Alerts will 

come into the operator and block the screen. The operator will not be able to see anything but 

this message. In AFATDS, target selection is displayed through this path. The now or later 

choices represent something on the screen changing that would indicate to the operator that he 

has a new message coming in. The operator would decide based on the situation whether to read 

now or later. The scenario must indicate the operator’s decision. Icon movements are visual 

changes on the screen other than those described above. RFI is a request for information. This 

will take the same path and a read now message but will take an alternate path after the operator 

has read the message. 

 1—Alert/CFF 

 2—Now 

 3—Later 

 4—Icon Movement 

 5—RFI 
135 

Nets 

Command 

Bde command 

Oper/Intel 

Bde Oper/Intel 

Admin/Log 

Bde Admin/Log 

Fire Spt 

Fire Direction 

Eng 

Bde Eng 

Air Force 

Air Def A 
136 

INTENTIONALLY LEFT BLANK
137 

Acronyms 

A/L administrative/logistics 

ALO air liaison officer 

ARL Army Research Laboratory 

BC battle captain 

C2 command and control 

C2V command and control vehicle 

Cdr commander 

CdrGNR gunner in the commander’s vehicle 

CdrLDR loader in the commander’s vehicle 

CTCP Combat Trains Command Post 

DJF detailed job function 

Eng engineer staff section 

ENO engineer officer 

ENRTO radio telephone operator in engineer staff section 

FS fire support staff section 

FSE 

FSNCO non-commissioned officer in fire support staff section 

FSO fire support officer 

FSRTO radio telephone operator in fire support staff section 

HMMWV high mobility multipurpose vehicle 

HPM human performance model 

M1 Abrams main battle tank 

M2 Bradley fighting vehicle 

NBCNCO nuclear, biological, chemical non-commissioned officer (operations section) 

NCO non-commissioned officer 

OPTEC Operational Test and Evaluation Command 

RTO radio telephone operator 

S1 personnel staff section (also officer in personnel staff section) 

S1NCO non-commissioned officer in personnel staff section 

S2 intelligence staff section 

S2A junior (assistant) officer in intelligence staff section 

S2NCO non-commissioned officer in intelligence staff section 

S2O officer in intelligence staff section 

S2RTO radio telephone operator in intelligence staff section 

S3 operations staff section (also officer in operations staff section) 

S3NCO non-commissioned officer in operations staff section 

S3RTO radio telephone operator in operations staff section 
138 

S3V operations officer in his command vehicle (M1 or M2) 

S3VGNR gunner in the S3V vehicle 

S3VLDR loader in the S3V vehicle 

S4 supply and logistics staff section (also officer in supply and logistics staff section) 

S4NCO non-commissioned officer in supply and logistics staff section 

TOC tactical operations center 

XO executive officer 
139 

NO. OF 

COPIES ORGANIZATION

 * ADMINISTRATOR 

 DEFENSE TECHNICAL INFO CTR 

 ATTN DTIC OCA 

 8725 JOHN J KINGMAN RD STE 0944 

 FT BELVOIR VA 22060-6218 

 *pdf file only 

 1 DIRECTOR 

 US ARMY RSCH LABORATORY 

 ATTN IMNE ALC IMS MAIL & REC MGMT 

 2800 POWDER MILL RD 

 ADELPHI MD 20783-1197 

 1 DIRECTOR 

 US ARMY RSCH LABORATORY 

 ATTN AMSRD ARL CI OK TL TECH LIB 

 2800 POWDER MILL RD 

 ADELPHI MD 20783-1197 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR M DR M STRUB 

 6359 WALKER LANE SUITE 100 

 ALEXANDRIA VA 22310 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MA J MARTIN 

 MYER CENTER RM 2D311 

 FT MONMOUTH NJ 07703-5630 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MC A DAVISON 

 320 MANSCEN LOOP STE 166 

 FT LEONARD WOOD MO 65473-8929 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MD T COOK 

 BLDG 5400 RM C242 

 REDSTONE ARSENAL AL 35898-7290 

 1 COMMANDANT USAADASCH 

 ATTN ATSA CD 

 ATTN AMSRD ARL HR ME MS A MARES 

 5800 CARTER RD 

 FT BLISS TX 79916-3802 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MI J MINNINGER 

 BLDG 5400 RM C242 

 REDSTONE ARSENAL AL 35898-7290 

NO. OF 

COPIES ORGANIZATION

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MM DR V RICE 

 BLDG 4011 RM 217 

 1750 GREELEY RD 

 FT SAM HOUSTON TX 78234-5094 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MG R SPINE 

 BUILDING 333 

 PICATINNY ARSENAL NJ 07806-5000 

 1 ARL HRED ARMC FLD ELMT 

 ATTN AMSRD ARL HR MH C BURNS 

 BLDG 1467B ROOM 336 

 THIRD AVENUE 

 FT KNOX KY 40121 

 1 ARMY RSCH LABORATORY - HRED 

 AVNC FIELD ELEMENT 

 ATTN AMSRD ARL HR MJ D DURBIN 

 BLDG 4506 (DCD) RM 107 

 FT RUCKER AL 36362-5000 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MK MR J REINHART 

 10125 KINGMAN RD 

 FT BELVOIR VA 22060-5828 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MV HQ USAOTC 

 S MIDDLEBROOKS 

 91012 STATION AVE ROOM 111 

 FT HOOD TX 76544-5073 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MY M BARNES 

 2520 HEALY AVE STE 1172 BLDG 51005 

 FT HUACHUCA AZ 85613-7069 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MP D UNGVARSKY 

 BATTLE CMD BATTLE LAB 

 415 SHERMAN AVE UNIT 3 

 FT LEAVENWORTH KS 66027-2326 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR M DR B KNAPP 

 ARMY G1 MANPRINT DAPE MR 

 300 ARMY PENTAGON ROOM 2C489 

 WASHINGTON DC 20310-0300 
140 

NO. OF 

COPIES ORGANIZATION

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MJK MS D BARNETTE 

 JFCOM JOINT EXPERIMENTATION J9 

 JOINT FUTURES LAB 

 115 LAKEVIEW PARKWAY SUITE B 

 SUFFOLK VA 23435 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MQ M R FLETCHER 

 US ARMY SBCCOM NATICK SOLDIER CTR 

 AMSRD NSC SS E BLDG 3 RM 341 

 NATICK MA 01760-5020 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MT DR J CHEN 

 12350 RESEARCH PARKWAY 

 ORLANDO FL 32826-3276 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MS MR C MANASCO 

 SIGNAL TOWERS RM 303A 

 FORT GORDON GA 30905-5233 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MU M SINGAPORE 

 6501 E 11 MILE RD MAIL STOP 284 

 BLDG 200A 2ND FL RM 2104 

 WARREN MI 48397-5000 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MF MR C HERNANDEZ 

 BLDG 3040 RM 220 

 FORT SILL OK 73503-5600 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MW E REDDEN 

 BLDG 4 ROOM 332 

 FT BENNING GA 31905-5400 

 1 ARMY RSCH LABORATORY - HRED 

 ATTN AMSRD ARL HR MN R SPENCER 

 DCSFDI HF 

 HQ USASOC BLDG E2929 

 FORT BRAGG NC 28310-5000 

 1 ARL-HRED LIAISON 

 PHYSICAL SCIENCES LAB 

 PO BOX 30002 

 LAS CRUCES NM 88003-8002 

NO. OF 

COPIES ORGANIZATION

 5 MICROANALYSIS & DESIGN 

 ATTN BETH PLOTT 

 4949 PEARL E CIRCLE STE 300 

 BOULDER CO 80301 

 1 US ARMY SAFETY CTR 

 ATTN CSSC SE 

 FORT RUCKER AL 36362 

 ABERDEEN PROVING GROUND

 1 DIRECTOR 

 US ARMY RSCH LABORATORY 

 ATTN AMSRD ARL CI OK (TECH LIB) 

 BLDG 4600 

 1 DIRECTOR 

 US ARMY RSCH LABORATORY 

 ATTN AMSRD ARL CI OK TP S FOPPIANO 

 BLDG 459 

 1 US ATEC 

 RYAN BLDG 

 APG-AA 

 1 DIRECTOR 

 US ARMY RSCH LABORATORY 

 ATTN AMSRD ARL HR M F PARAGALLO 

 BLDG 459 

 1 DIRECTOR 

 US ARMY RSCH LABORATORY 

 ATTN AMSRD ARL HR MB J NAWLEY 

 BLDG 459 

 5 DIRECTOR 

 US ARMY RSCH LABORATORY 

 ATTN AMSRD ARL HR MB 

 J WOJCIECHOWSKI 

 BLDG 459 

 5 DIRECTOR 

 US ARMY RSCH LABORATORY 

 ATTN AMSRD ARL HR SE 

 P KILDUFF 

 BLDG 459