Military reference books and manuals (2009-2023, Volume 7)

MOS/Skill Level Tasks-Skill Level 3

301-96U-3062

ASSIST IN FREQUENCY MANAGEMENT FOR AN UNMANNED AERIAL VEHICLE (UAV)

MISSION

Conditions: Given a mission.

Standards: Assist in frequency management for the unmanned aerial vehicle (UAV) mission in

accordance with mission requirements, FM 24-2, AR 5-12, and local frequency management

policies.

Performance Steps

1. Assist the 350U in identifying frequency requirement.

a. Determine area of operation (AO).

b. Research local frequency management policies.

2. Assist the 350U in coordinating frequency usage.

a. In garrison operations, submit request to post frequency manager.

b. In field/deployment operations, submit request to brigade S6.

3. Assist the 350U in reporting frequency interference.

a. In garrison operations, notify unit causing interference, director of information

management (DOIM) or post frequency manager.

b. In field/deployment operations, notify S6.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Assisted the 350U in identifying frequency requirements.

——

2. Assisted the 350U in coordinating frequency usage.

——

3. Assisted the 350U in reporting frequency interference.

——

3-145

MOS/Skill Level Tasks-Skill Level 3

301-96U-3063

ASSIST IN AIRSPACE COORDINATION FOR AN UNMANNED AERIAL VEHICLE (UAV)

MISSION

Conditions: Given a mission to assist in airspace coordination for an unmanned aerial vehicle

(UAV) mission in accordance with mission requirements.

Standards: Assist in airspace coordination for the UAV mission in accordance with mission

requirements, FM 3-52, JP 3-52, JP 3-56.1, and unit standing operating procedures (SOPs).

Performance Steps

1. Assist the 350U in identifying airspace requirements.

a. Determine area of operation (AO).

b. Extract UAV requirements from the collection plan.

c. Identify the commander’s priority intelligence requirements (PIR) and latest time

information is of value (LTOIV).

2. Assist the 350U in coordinating airspace.

a. In garrison operations, submit request to S3 (AIR), and range control.

b. In field/deployment operations, submit request to S3 (AIR).

3. Assist the 350U in checking for airspace approval.

a. Review air tasking order (ATO) for mission times.

b. Review airspace control order (ACO) for associated control measures.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Assisted the 350U in identifying airspace requirements.

——

2. Assisted the 350U in coordinating airspace.

——

3. Assisted the 350U in checking for airspace approval.

——

3-147

MOS/Skill Level Tasks-Skill Level 3

301-96U-3064

DIRECT UNMANNED AERIAL VEHICLE (UAV) LAUNCH AND RECOVERY (L/R)

OPERATIONS

Conditions: Given a mission, an emplaced unmanned aerial vehicle (UAV) system, associated

equipment, operations order, fragmentary orders, airspace management products, and

climatological data.

Standards: Direct personnel to perform runway launch procedures to include shelter power-up

through recovery in accordance with mission, TM 9-5895-692-10-1, TM 9-5895-692-10-2, and

TM 9-5895-692-CL without causing damage to equipment, injury to personnel, or safety

violations.

Performance Steps

1. Receive mission from local/higher command.

a. Verify availability of a UAV for the mission.

b. Verify the configuration of the UAV matches the mission requirement.

c. Verify the weather for the area and time of mission is appropriate.

d. Verify an appropriate flight crew has been assigned for the mission.

2. Direct L/R operations. Ensure that launch and recovery operations are performed in

accordance with tasks: 301-96U-1060, 301-96U-1061S, 301-96U-1063S, 301-96U-1064,

301-96U-1065, 301-96U-1066, 301-96U-1067, 301-96U-1068H, 301-96U-1069, 301-96U-

1076, 301-96U-1077, 301-96U-1078, and 301-96U-1079S.

3. Perform final inspection.

a. Verify the mission is set-up properly.

b. Report back to local/higher command with status of the mission.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Received mission from local/higher command.

——

2. Directed L/R operations.

——

3. Performed final inspection.

——

3-149

MOS/Skill Level Tasks-Skill Level 3

301-96U-3066

DIRECT UNMANNED AERIAL VEHICLE (UAV) FLIGHT/MISSION OPERATIONS

Conditions: Given a mission and unmanned aerial vehicle (UAV) system.

Standards: Direct UAV flight/mission operations in accordance with mission requirements,

TC 1-201, TC 34-212, FM 1-300, FM 6-30, FM 3-52, FM 17-98, FM 34-1, FM 57-38, unit

standing operating procedures (SOPs), and TM 9-5895-681-10 (Shadow) or TM 9-5895-692-10-

1 (Hunter)/TM 9-5895-692-10-2 (Hunter).

Performance Steps

1. Receive mission from local/higher command.

a. Verify availability of a UAV for the mission.

b. Verify the weather for the area and time of mission is appropriate.

c. Verify an appropriate flight crew has been assigned for the mission.

d. Verify the mission is set-up properly.

2. Direct mission operations.

a. Ensure that flight/mission operations are performed in accordance with tasks: 301-96U-

1060, 301-96U-1061S, 301-96U-1064, 301-96U-1067, 301-96U-1068H, 301-96U-1069,

301-96U-1070, 301-96U-1071, 301-96U-1072, 301-96U-1073, 301-96U-1074, 301-96U-

1075, 301-96U-1076, 301-96U-1078, and 301-96U-1079S.

b. Verify airspace boundaries are not crossed with the air vehicle (AV).

c. Verify known threats are avoided and targets are observed.

d. Verify specific targets and any named areas of interest (NAIs) are observed.

3. Perform final inspection.

a. Report back to local/higher command with status of the mission.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Received mission from local/higher command.

——

2. Directed mission operations.

——

3. Performed final inspection.

——

3-151

MOS/Skill Level Tasks-Skill Level 3

301-96U-3067

DIRECT UNMANNED AERIAL VEHICLE (UAV) RECONNAISSANCE, SURVEILLANCE, AND

TARGET ACQUISITION (RSTA) OPERATIONS

Conditions: Given an unmanned aerial vehicle (UAV) system and a reconnaissance,

surveillance, and target acquisition (RSTA) mission.

Standards: Direct UAV RSTA operations in accordance with TC 1-201, FM 6-30, FM 17-98,

FM 34-1, TC 34-212, and TM 9-5895-681-10 (Shadow) or TM 9-5895-692-10-1 (Hunter)/

TM 9-5895-692-10-2 (Hunter).

Performance Steps

1. Collect mission requirements for RSTA operations from higher/adjacent command.

2. Direct reconnaissance operations.

a. Verify the air vehicle operator (AVO)/mission payload operator (MPO) team knows the

reconnaissance area for the mission.

b. Verify the reconnaissance area has been appropriately marked in the controlling station.

c. Verify the entire area has been surveyed during the reconnaissance mission.

3. Direct surveillance operations.

a. Verify the AVO/MPO team knows the surveillance area for the mission.

b. Verify the surveillance area has been appropriately marked in the controlling station.

c. Verify the entire area has been surveyed during the surveillance mission.

4. Direct target acquisition operations.

a. Verify the AVO/MPO team knows the objective target area for the mission.

b. Verify the objective target area has been appropriately marked in the controlling station.

c. Verify the all targets have been surveyed during the target acquisition mission.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Collected mission requirements for RSTA operations from higher/adjacent

——

command.

2. Directed reconnaissance operations.

——

3. Directed surveillance operations.

——

4. Directed target acquisition operations.

——

3-153

MOS/Skill Level Tasks-Skill Level 3

Subject Area 3: DISPLACEMENT OPERATIONS

301-96U-3111

DIRECT UNMANNED AERIAL VEHICLE (UAV) LAUNCH AND RECOVERY (L/R) SITE

DISPLACEMENT

Conditions: Given an unmanned aerial vehicle (UAV) system, associated equipment, site plan,

and TM 9-5895-681-10 (SHADOW) or TM 9-1425-691-10 (Hunter).

Standards: Direct UAV launch and recovery (L/R) site displacement in accordance with unit

standing operating procedures (SOPs), and TM 9-5895-681-10 (Shadow) or TM 9-1425-691-10

(Hunter).

Performance Steps

Receive movement orders from local/higher command.

Assign displacement team (non-commissioned officers in charge) NCOICs.

a. Assign a NCOIC for the shelters and antennas.

b. Assign a NCOIC for the runway/launch area.

c. Assign a NCOIC for the maintenance area.

Direct displacement. Verify that displacement is performed in accordance with tasks:

301-96U-1112S, 301-96U-1113H, 301-96U-1114H, 301-96U-1115, 301-96U-1116S,

301-96U-1118, 301-96U-1119S, 301-96U-1126H, 301-96U-1127S, 301-96U-1128S,

301-96U-1129S, 301-96U-1130H, 301-96U-1131H, 301-96U-1132, and 301-96U-1133.

Perform final inspection.

a. Verify equipment is displaced properly.

b. Verify an inventory of all equipment has been completed.

c. Verify load plans have been completed.

d. Verify that equipment is prepared for movement.

(1) Verify vehicles are lined up in preparation for convoy.

(2) Verify vehicle loads are secure and ready for movement.

(3) Verify vehicles have properly licensed drivers and assistant drivers.

e. Direct a walk around inspection of the site and ensure that site is ready to be vacated.

f. Report back to local/higher command with status of site displacement.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

3-155

STP 34-96U14-SM-TG

Performance Measures

NO GO

1. Received movement orders from local/higher command.

——

2. Assigned displacement team NCOICs.

——

3. Directed displacement.

——

4. Performed final inspection.

——

Evaluation Guidance: Mark each performance measure either GO or NO GO. The soldier

must complete all substeps to receive a GO for that measure. Mark the soldier GO if all

performance measures are passed. All measures must be marked GO to receive an overall GO

on the task. Mark the soldier NO GO if any performance measure is failed. If the soldier is

marked NO GO, show him what was done wrong and how to do it correctly.

References

Required

TM 9-1425-691-10

FM 10-67-1

TM 9-1425-697-13

FM 10-67-2

TM 9-5895-681-10

TM 9-5895-681-CL

Unit SOP

3-156

MOS/Skill Level Tasks-Skill Level 3

301-96U-3112

DIRECT UNMANNED AERIAL VEHICLE (UAV) FORWARD CONTROL SITE

DISPLACEMENT

Conditions: Given an unmanned aerial vehicle (UAV) system, associated equipment, site plan,

and TM 9-5895-681-10 (Shadow) or TM 9-1425-691-10 (Hunter).

Standards: Direct UAV forward control site displacement in accordance with unit standing

operating procedures (SOPs), and TM 9-5895-681-10 (Shadow) or TM 9-1425-691-10 (Hunter).

Performance Steps

1. Receive movement orders from local/higher command.

2. Assign displacement team (non-commissioned officers in charge) NCOICs.

a. Assign a NCOIC for the shelters and antennas.

b. Assign a NCOIC for the RVT and antennas (if used onsite).

3. Direct displacement. Verify that displacement is performed in accordance with tasks:

301-96U-1114H, 301-96U-1115, 301-96U-1116S, 301-96U-1118, 301-96U-1119S, and

301-96U-1132.

4. Perform final inspection.

a. Ensure equipment is displaced properly.

b. Ensure an inventory of all equipment has been completed.

c. Ensure load plans have been completed.

d. Ensure that equipment is prepared for movement.

(1) Line up vehicles in preparation for convoy.

e. Direct a walk around inspection of the site and ensure that site is ready to be vacated.

f. Report back to local/higher command, status of site displacement.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Received movement orders from local/higher command.

——

2. Assigned displacement team NCOICs.

——

3. Directed displacement.

——

4. Performed final inspection.

——

3-157

MOS/Skill Level Tasks-Skill Level 3

301-96U-3113

PERFORM UNMANNED AERIAL VEHICLE (UAV) SITE SELECTION

Conditions: Given a mission, UAV system, associated materials, map of proposed area of

operation (AO), and TM 9-5895-681-10 (Shadow) or TM 9-1425-691-10 (Hunter).

Standards: Perform UAV site selection in accordance with operations order, site survey,

FM 57-38, unit standing operating procedures (SOPs), and TM 9-5895-681-10 (Shadow) or

TM 9-1425-691-10 (Hunter).

Performance Steps

1. Ensure site has good line-of-sight with UAV area of operation. Look for large mountains that

could potentially block the UAVs line of sight to the launch and recovery (L/R) site and

forward control site.

2. Ensure launch and recovery (L/R) site is within communications range of the forward control

site.

a. Verify L/R site is with in tactical communications range of the forward control site.

b. Verify L/R site is with in UAV data link range of the forward control site.

3. Ensure site has trafficability ingress and egress for UAV baseline system vehicles.

4. Ensure site is large enough to accommodate all UAV system equipment.

5. Ensure site is in a secure area with cover and concealment.

6. Ensure site is suitable for UAV takeoff/launch and recovery operations.

a. Ensure site has an appropriate sized area for launch and recovery operations.

b. Check the area for appropriate prevailing winds for launch and recovery operations.

c. Check the site for any high elevation terrain obstructions could potentially be hazardous

during launch and recovery operations.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

GO NO GO

1. Ensured site has good line of sight with UAV area of operation.

——

2. Ensured L/R site is within communications range of the forward control site.

——

3. Ensured site has trafficability ingress and egress for UAV baseline system

——

vehicles.

4. Ensured site is large enough to accommodate all UAV system equipment.

——

5. Ensured site is in a secure area with cover and concealment.

——

6. Ensured site is suitable for UAV takeoff/launch and recovery operations.

——

3-159

MOS/Skill Level Tasks-Skill Level 3

Subject Area 5: INTELLIGENCE OPERATIONS

301-96U-3260

DIRECT UNMANNED AERIAL VEHICLE (UAV) REPORTING

Conditions: Given a mission, commander’s critical intelligence requirement (CCIR), AR 380-5,

and combat information.

Standards: Direct UAV reporting to ensure proper format and dissemination in accordance with

unit standing operating procedures (SOPs), AR 380-5, JINTACCS, and USMTF.

Performance Steps

1. Collect reporting requirements from higher/adjacent command.

2. Disseminate reporting information to subordinates.

a. Schedule.

b. Format.

c. Context.

3. Direct subordinates to prepare written/electronic draft of the report.

4. Direct subordinates in the proper marking and handling procedures for classified material

(see AR-380-5).

5. Direct subordinates in the proper dissemination of intelligence reports for dissemination.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Collected reporting requirements from higher/adjacent command.

——

2. Disseminated reporting information to subordinates.

——

3. Directed subordinates to prepare written/electronic draft of the report.

——

4. Directed subordinates in the proper marking and handling procedures for

——

classified material (see AR-380-5).

5. Directed subordinates in the proper dissemination of intelligence reports for

——

dissemination.

3-161

MOS/Skill Level Tasks-Skill Level 4

Skill Level 4

Subject Area 1: EMPLACEMENT OPERATIONS

301-96U-4010

CONDUCT UNMANNED AERIAL VEHICLE (UAV) SITE SURVEY

Conditions: Given a mission, an unmanned aerial vehicle (UAV) system, map of proposed area

of operations (AO), associated materials, and TM 9-5895-681-10 (Shadow) or TM 9-1425-691-

10 (Hunter).

Standards: Conduct UAV site survey in accordance with airspace management products,

TC 1-201, unit standing operating procedures (SOPs), FM 57-38, and TM 9-5895-681-10

(Shadow) or TM 9-1425-691-10 (Hunter).

Performance Steps

Conduct launch and recovery (L/R) site survey.

Gather resources for possible L/R site areas.

(1) Maps of the possible sites.

(2) Weather data.

(a) Prevailing winds of the area.

(b) Overall area cloud coverage.

(d) Annual rainfall.

(3) Geological data.

(a) Soil content.

(b) Soil density.

(4) Area population data.

(a) Total of populated areas (over fly hazards).

(b) Local facilities such as airports with controlled airspace.

Review resources for the following:

(1) Areas large enough to maneuver entire UAV baseline in for set up of L/R element

and staging of the forward control site.

(2) Area large enough for runway/launch area.

(3) Terrain obstacles for line of site with airborne UAV.

(4) Ingress and egress routes.

(5) Cover and concealment.

(6) Distance from L/R site to possible forward control sites.

(7) Distance from L/R site to furthest mission objective.

(8) Lines of communications.

3-163

STP 34-96U14-SM-TG

Performance Steps

Conduct forward control site survey.

Gather resources for possible forward control site areas.

(1) Maps of the possible sites.

(2) Weather data.

(a) Prevailing winds of the area.

(b) Overall area cloud coverage.

(d) Annual rainfall.

(3) Geological data.

(a) Soil content.

(b) Soil density.

(4) Area population data.

(a) Total of populated areas (over fly hazards).

(b) Local facilities such as airports with controlled airspace.

Review resources for the following:

(1) Terrain obstacles for line of site with airborne UAV.

(2) Ingress and egress routes.

(3) Cover and concealment.

(4) Distance from forward control sites to possible L/R sites.

(5) Distance from forward control site to furthest mission objective.

(6) Lines of communications.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Conducted launch and recovery (L/R) site survey.

——

a. Gathered resources for possible L/R site areas.

b. Reviewed resources.

2. Conducted forward control site survey.

——

a. Gathered resources for possible forward control site areas.

b. Reviewed resources.

3-164

STP 34-96U14-SM-TG

301-96U-4011

SELECT AN UNMANNED AERIAL VEHICLE (UAV) LAUNCH AND RECOVERY (L/R) SITE

LOCATION

Conditions: Given a mission, site survey, associated materials, operations order, fragmentary

orders, airspace management products, climatological data, and TM 9-5895-681-10 (Shadow)

or TM 9-1425-691-10 (Hunter).

Standards: Select UAV site locations in accordance with operations order, fragmentary orders,

unit standing operating procedures (SOPs), FM 3-52, FM 57-38, TC 1-201, and TM 9-5895-681-

10 (Shadow) or TM 9-1425-691-10 (Hunter).

Performance Steps

1. Review resources listed in task 301-96U-4010.

2. Mark multiple areas on maps for potential L/R sites.

3. Review marked areas for potential L/R sites in accordance with task 301-96U-4010.

4. Select best suited location for emplacement of UAV L/R site.

a. Select an area with level ground and little vegetation.

b. Select an area that can best support the entire UAV baseline emplacement.

c. Select an area that has best terrain characteristics for UAV operations.

d. Select a location that will not be out of data link or communications range from possible

forward control site areas.

e. Select a location best suited logistically.

f. Select a location that has best lines of communications available.

g. Select a location with the least amount of hazard or impact to populated areas.

5. Designate primary and alternate L/R site location.

6. Disseminate results of site selection to higher/adjacent command.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Reviewed resources listed in task 301-96U-4010.

——

2. Marked multiple areas on maps for potential L/R sites.

——

3. Reviewed marked areas for potential L/R sites in accordance with task

——

301-96U-4010.

4. Selected best suited location for emplacement of UAV L/R site.

——

5. Designated primary and alternate L/R site location.

——

6. Disseminated results of site selection to higher/adjacent command.

——

3-166

STP 34-96U14-SM-TG

301-96U-4012

PRODUCE AN UNMANNED AERIAL VEHICLE (UAV) LAUNCH AND RECOVERY (L/R) SITE

LAYOUT

Conditions: Given a mission, site survey, associated materials, operations order, fragmentary

orders, airspace management products, climatological data, and TM 9-5895-681-10 (Shadow)

or TM 9-1425-691-10 (Hunter).

Standards: Produce UAV site layout in accordance with operations order, fragmentary orders,

unit standing operating procedures (SOPs), FM 3-52, FM 57-38, TC 1-201, and TM 9-5895-681-

10 (Shadow) or TM 9-1425-691-10 (Hunter).

Performance Steps

1. Layout emplacement location for runway/launch area.

a. Research L/R site wind directions and speeds.

b. Layout emplacement locations of runway and runway support equipment in accordance

with TM 9-5895-681-10 (Shadow) or TM 9-1425-691-10 (Hunter).

2. Layout emplacement locations for controlling shelters, antennas, and flight control boxes

(with associated equipment) in accordance with TM 9-5895-681-10 (Shadow) or

TM 9-1425-691-10 (Hunter).

3. Layout emplacement locations for mission briefing and debriefing area.

4. Layout emplacement location for POL (fuel) point.

5. Layout emplacement location for maintenance area.

6. Layout location for maintenance support equipment.

7. Layout location for air vehicle (AV) storage while not in use.

8. Layout location for support vehicle to be parked while not in use.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Produced a layout with the emplacement location for runway/launch area.

——

2. Produced a layout with the emplacement locations for controlling shelters,

——

antennas, and flight control boxes (with associated equipment) in

accordance with TM 9-5895-691-10.

3. Produced a layout with the emplacement locations for mission briefing and

——

debriefing area.

4. Produced a layout with the emplacement locations for mission briefing and

——

debriefing area.

5. Produced a layout with the emplacement location for maintenance area.

——

3-168

MOS/Skill Level Tasks-Skill Level 4

Performance Measures

NO GO

6. Produced a layout with the location for maintenance support equipment.

——

7. Produced a layout with the location for AV storage while not in use.

——

8. Produced a layout with the location for support vehicle to be parked while

——

not in use.

Evaluation Guidance: Mark each performance measure either GO or NO GO. The soldier

must complete all substeps to receive a GO for that measure. Mark the soldier GO if all

performance measures are passed. All measures must be marked GO to receive an overall GO

on the task. Mark the soldier NO GO if any performance measure is failed. If the soldier is

marked NO GO, show him what was done wrong and how to do it correctly.

References

Required

FM 3-52

FM 57-38

TC 1-201

TM 9-1425-691-10

TM 9-1425-697-13

TM 9-5895-681-10

TM 9-5895-681-CL

Unit SOP

3-169

STP 34-96U14-SM-TG

Subject Area 2: FLIGHT/MISSION OPERATIONS

301-96U-4060

COORDINATE WITH HIGHER/ADJACENT HEADQUARTERS

Conditions: Given an operations plan, operations order and intelligence annex, a higher and/or

adjacent headquarters, and references FM 34-2, FM 71-100, FM 3-0, FM 100-15, and

FM 101-5.

Standards: Identify and coordinate all requirements needed to accomplish the mission through

higher/adjacent headquarters using references FM 34-2, FM 71-100, FM 3-0, FM 100-15, and

FM 101-5.

Performance Steps

Establish communications with supported unit(s) or higher/adjacent headquarters.

Brief supported unit or higher/adjacent command on specific UAV system capabilities.

a. Brief on sensor capabilities.

b. Brief on range capabilities.

c. Brief on endurance capabilities.

d. Brief on notification time needed prior to each mission.

Receive mission/tasking information from supported unit(s) or higher/adjacent headquarters.

a. Receive approximate number of missions needed for supporting the unit or

higher/adjacent command.

b. Receive approximate timelines of missions needed for supporting the unit or

higher/adjacent command.

c. Receive overall objective of missions needed for supporting the unit or higher/adjacent

command.

d. Receive a list of objective targets being collected on during missions supporting the unit

or higher/adjacent command.

Coordinate missions/taskings for supported unit(s) or higher/adjacent headquarters.

a. Coordinate mission priorities.

b. Coordinate which mission objectives can be achieved and which objectives possibly

may not be achieved.

c. Coordinate possible forward control site locations.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

3-170

MOS/Skill Level Tasks-Skill Level 4

Performance Measures

NO GO

1. Established communications with supported unit(s) or higher/adjacent

——

headquarters.

2. Briefed supported unit or higher/adjacent command on specific UAV

——

system capabilities.

3. Received mission/tasking information from supported unit(s) or

——

higher/adjacent headquarters.

4. Coordinated missions/taskings for supported unit(s) or higher/adjacent

——

headquarters.

Evaluation Guidance: Mark each performance measure either GO or NO GO. The soldier

must complete all substeps to receive a GO for that measure. Mark the soldier GO if all

performance measures are passed. All measures must be marked GO to receive an overall GO

on the task. Mark the soldier NO GO if any performance measure is failed. If the soldier is

marked NO GO, show him what was done wrong and how to do it correctly.

References

Required

FM 100-15

FM 101-5

FM 3-0

FM 34-2

FM 71-100

3-171

STP 34-96U14-SM-TG

Subject Area 3: DISPLACEMENT OPERATIONS

301-96U-4110

PLAN UNMANNED AERIAL VEHICLE (UAV) DISPLACEMENT OPERATIONS

Conditions: Given a mission, mission required equipment, support equipment, personnel,

associated materials, operational order, fragmentary orders, and TM 9-5895-681-10 (Shadow)

or TM 9-1425-691-10 (Hunter).

Standards: Plan unmanned aerial vehicle (UAV) displacement operations in accordance with

operational order, fragmentary orders, and TM 9-5895-681-10 (Shadow) or TM 9-1425-691-10

(Hunter) to satisfy missions tasking.

Performance Steps

Receive movement orders from local/higher command.

Plan a displacement schedule.

a. Research the time and date of the last UAV mission needed to be performed from that

site.

b. Schedule the displacement of all non-essential equipment for that mission prior to end of

mission. Schedule the displacement of the following:

(1) Mobile maintenance facility (MMF) and associated equipment.

(2) Non-essential flight line support equipment.

(3) Non-essential AV’s and storage boxes.

(4) Non-essential ground support vehicles.

c. Schedule the displacement of all mission essential equipment after last mission has

been completed. Schedule the displacement of the following:

(1) Controlling shelters and antennas with associated equipment.

(2) Remaining flight line support equipment.

(3) Remaining maintenance equipment.

Implement the planned schedule.

a. Verify assignment of a (non-commissioned officer in charge) NCOIC for the shelters and

antennas.

b. Verify assignment of a NCOIC for the runway/launch area.

c. Verify assignment of a NCOIC for the maintenance area.

d. Ensure all NCOICs know the timelines of the displacement schedule.

e. Ensure all timelines of the displacement schedule are achieved.

Perform final inspection.

a. Verify scheduled timelines were achieved.

b. Verify all equipment has been displaced.

c. Verify an inventory of all equipment has been completed.

d. Verify load plans have been completed.

3-172

MOS/Skill Level Tasks-Skill Level 4

Performance Steps

e. Verify that equipment is prepared for movement.

f. Verify a walk around inspection of the site has been performed and ensure that site is

ready to be vacated.

g. Report back to local/higher command with status of site displacement.

Evaluation Preparation: Provide the soldier with the materials listed in the condition

statement.

Performance Measures

NO GO

1. Received movement orders from local/higher command.

——

2. Planned a displacement schedule.

——

3. Implemented the planned schedule.

——

4. Performed final inspection.

——

Evaluation Guidance: Mark each performance measure either GO or NO GO. The soldier

must complete all substeps to receive a GO for that measure. Mark the soldier GO if all

performance measures are passed. All measures must be marked GO to receive an overall GO

on the task. Mark the soldier NO GO if any performance measure is failed. If the soldier is

marked NO GO, show him what was done wrong and how to do it correctly.

References

Required

TM 9-1425-691-10

TM 9-1425-697-13

TM 9-5895-681-10

Unit SOP

3-173

Chapter 4

Duty Position Tasks

4-1. MAJOR DUTIES. The TUAV operator supervises or operates the TUAV, to include

mission planning, mission payload operations, launching, remotely piloting, and recovering the

air vehicle. The following describes duties for MOS 96U at each skill level—

a. MOSC 96U1O. Prepares and conducts reconnaissance, surveillance, and target

acquisition

(RSTA) missions. Operates mission payload. Prepares and analyzes mission

plans. Deploys and redeploys the TUAV system. Operates and performs operator level

maintenance on communications equipment, power sources, light and heavy wheel vehicles.

Launches and recovers the air vehicle, performs pre-flight, in flight, and post-flight checks and

procedures.

b. MOSC 96U2O. Performs and supervises duties shown in the preceding skill level and

provides guidance to subordinate soldiers. Supervises launch/recovery site operations.

Provides navigational assistance to, and control of, Army aircraft in designated areas.

Participates in mission planning, using maps, terrain studies, and intelligence reports.

Supervises operator level maintenance and crew procedures performed on TUAV system,

communications equipment, vehicles, power sources, and other assigned equipment.

Supervises operations and activities of the team.

c. MOSC 96U3O. Performs duties shown in the preceding skill levels and provides

guidance to subordinate soldiers. Performs site selection and supervises site setup of TUAV

ground equipment using maps, aerial photographs, terrain studies, and intelligence reports.

Performs as mission commander during flight operations. Coordinates methods of employment

to higher and adjacent units. Creates and maintains a mission database. Supervises

operations and activities of the squad.

d. MOSC 96U4O. Performs duties shown in the preceding skill levels and provides

guidance to subordinate soldiers. Directs TUAV flight operations. Supervises navigational

assistance to and control of Army aircraft in designated areas. Applies military intelligence

collection processes and RSTA planning to TUAV operations. Supervises operations and

activities of the platoon.

4-2. PHYSICAL DEMANDS RATING AND QUALIFICATIONS FOR INITIAL AWARD OF

MOS.

a. Physical demands rating and qualifications for initial award of MOS. UAV operators

must possess the following qualifications.

(1) A physical demands rating of medium.

(2) A physical profile of 222221.

(3) Normal color vision.

(4) A minimum score of 105 in the aptitude area of SC.

(5) A security clearance of secret. (An interim secret meets this requirement.)

(6) A U.S. citizen.

(7) Meet career management and development criteria contained in AR 614-200 and

DA Pam 351-4.

(8) A high school graduate or equivalent.

(9) Formal training (completion of MOS 96U course conducted under the auspices of

USAIC&FH, Ft Huachuca, AZ is mandatory).

4-1

STP 34-96U14-SM-TG

(10) Never been a member of the U.S. Peace Corps, except as specified in

AR 614-200, chapter 1.

(11) No information in military personnel, provost marshal, intelligence, or medical

records, that would prevent the granting of a security clearance under provisions of AR 380-67

(paragraph 3.401.b).

(12) No record of conviction by court martial.

(13) No record of conviction by a civil court for any offense other than minor traffic

violations.

b. Additional skill identifiers.

(1) P5—Master fitness trainer.

(2)

2S—Battle staff operations (skill level 3 and above only).

(3)

4A—Reclassification training.

(4) F7—Pathfinder.

(5) Q8—Air operations specialist.

c. Physical requirements and standards of grade. Physical requirements and SG relating

to each skill level are listed in the following tables:

(1) Table 10-96U-1. Physical requirements.

(2) Table 10-96U-2. Standards of grade TOE/MTOE.

(3) Table 10-96U-3. Standards of grade TDA.

4-2

Glossary

amps

avenue of approach; assembly area

active component; assistant commandant; alternating current

ACD

altitude compensation device

ACO

airspace control order

ADR

airborne data relay

adjutant general; arresting gear

air interdiction; area of interest

AIT

advanced individual training

alt

altitude; alternate

annually

ant

antenna

antipersonnel; application processor; autopilot

Army regulation; armor

assy

assembly

ATO

air tasking order

attn

attention

audiovisual; air vehicle

AVO

air vehicle operator

AVT

air vehicle transport

biannually

battalion

BNC

see BNCOC

BNCOC

basic noncommissioned officer course

biweekly

chemical (graphics); celsius

command and control

command, control, and communications

CCA

circuit card assembly; console computer assembly

CCIR

commander’s critical information requirements

chemical defense; counterdrug; chad; capacitor discharge, compact

disk

cmd

command

comp

complete, completed

Department of the Army; direct action

DACM

data adapter communication module

Glossary-1

STP 34-96U14-SM-TG

direct current

Department of Defense (form)

directed energy; data exploiter

DSVT

digital subscriber voice terminal

DTED

digital terrain elevation data

egress route

The route used to exit enemy territory after the conclusion of a

mission (such as a deep attack or raid).

EMP

electromagnetic pulse; enhanced mission planner

electronic protection; external pilot

EPE

electrical power equipment

ESD

engine shut down; electro static discharge

Fahrenheit

FCB

flight control box

field manual; frequency modulated/modulation

FOC

flight operations center; fiber optic cable

FOD

foreign object damage

FOV

field of view

feet; fort

GCS

ground control station

GDT

ground data terminal

gpm

gallons per minute

GPS

global positioning system

GTA

graphic training aid

HMMWV

high mobility multipurpose wheeled vehicle

IET

initial entry training

IMINT

imagery intelligence

INC

increase; incorporated

indirect fire

(JP 1-02) Fire delivered on a target that is not itself used as a point

of aim for the weapons or the director. (Army) - Fire delivered on a

target characterized by a relatively high trajectory and where the

weapon operator normally does not have visual contact with the

target.

(See also direct laying.) See FM 6-20-series and FM 7-90.

Individual task

The lowest behavioral level in a job or duty that is performed for its

own sake. It should support a collective task; it usually supports

another individual task. Individual tasks include common soldier

tasks, leader tasks, common tasks, organizational level tasks.

Glossary-2

Glossary

Information

The protection of information systems against unauthorized access

systems

to, or modification of, information, whether in storage, processing, or

security (ISS)

transit, and against denial of service to authorized users or the

providing of access to unauthorized users, including those

measures necessary to detect, document, and counter such threats.

See FM 100-6.

Insp

inspection

instructional site

A physical location where specific instruction is to be accomplished

(school, unit, job site). Despite semantic preferences, a recognition

of basic distinction between form of training (self-study, supervised

on-the-job training) and location of training (resident or job site) is

important. In this context, site and setting are designations of

training location, not training form. In analysis the analyst is

concerned with site (location) selection, not training form selection,

which is the task of the designers and developers. See “training site

selection.”

JINTACCS

joint interoperability of tactical command and control systems

joint publication

kilometer

lat

latitude

L/R

launch and recovery

lau

launcher

line of sight

The unobstructed path from a soldier, weapon, weapon sight,

electronic-sending and -receiving antennas, or piece of

reconnaissance equipment from one point to another point.

lines of

(JP 1-02) All the routes, land, water, and air, that connect an

communications

operating military force with a base of operations and along which

supplies and military forces move. [See also communications zone

(COMMZ)].

lubrication order; law and order, low

load plan

A document that presents, in detail, all instructions for the

arrangement of personnel and equipment aboard a given type

aircraft or vehicle.

(See also combat loading.)

LOC

lines of communications

long

longitude

LOS

line of sight

LRS

long-range surveillance; launch and recovery station

LRT

launch and recovery terminal

mechanized (graphics); moment

Glossary-3

STP 34-96U14-SM-TG

map

(JP 1-02, NATO) A graphic representation, usually on a plane

surface and at an established scale, of natural or artificial features

on the surface of a part or whole of the Earth or other planetary

body. These features are positioned relative to a coordinate

reference system. See FM 3-25.26. (Army).

a. large-scale map. A map having a scale of 1:75,000 or larger

used for tactical planning.

b. medium-scale map. A map having a scale between

1:1,000,000 and 1:75,000 used for operational planning.

c. small-scale map. A map having a scale smaller than

1:1,000,000 used for general planning and strategic studies.

max

maximum

mission commander

MCU

mission control unit

METL

mission essential task list

MGRS

military grid reference system (pertains to maps)

MMF

mobile maintenance facility

MMP

modular mission payload

monthly

moc

maintenance operational check

MOS

military occupational specialty

MOSP

multimission optronic stabilized platform

MPO

mission payload operator

MPS

mission planning station

MPU

mobile power unit

MSE

multiple subscriber equipment; mission support element

MTF

maintenance test flight

NAI

named area of interest

nav

navigation; naval

NCO

noncommissioned officer

NCOIC

noncommissioned officer in charge

NOTAM

notice to airman

NSN

nonstandard number; national stock number

power amplifier

pam

pamphlet

PGCS

portable ground control station

PGDT

portable ground data terminal

PIR

priority intelligence requirements

provost marshal; preventive maintenance; project/program manager

PMCS

preventive maintenance checks and services

POL

petroleum, oil, and lubricants

Glossary-4

Glossary

PPE

personnel protective equipment

pwr

power

quarterly

RISTA

reconnaissance, intelligence, surveillance, and target acquisition

(see RSTA also).

ROC-V

recognition of combat vehicles

ROM

refuel on the move; read-only memory

ROZ

restricted operations zone

RSTA

reconnaissance, surveillance, and target acquisition

RVT

remote video terminal

battalion intelligence officer

battalion operations officer

battalion supply officer

SALUTE

size, activity, location, unit, time, and equipment

SERU

servo elerudder units

SITMAP

situation map

skill level; sea level

soldier's manual; service member; statute mile

SMU

shelter mounted unit

SNR

signal-to-noise ratio

SOJT

supervised on-the-job training

SOI

signal operating instructions

SOP

standing operating procedures

start point; strongpoint; self-propelled; Spain

SPA

stabilized platform assembly

supply route; short range

SRC

SSM

surface-to-surface missile

STAB

stabilizer

STBY

standby

STU

servo throttle unit

suppl

supplement

SUT

single unit transceiver

southwest; sector width

SWU

servo wheel unit

SYS

system

TALS

tactical automated landing system

TAMMS

The Army Maintenance Management System

technical coordinator; training circular

Glossary-5

References

REQUIRED PUBLICATIONS

Required publications are sources that users must read in order to understand or to comply with

this publication.

ARMY REGULATIONS

AR 5-12, Army Management of the Electromagnetic Spectrum, 1 October 1997.

AR 380-5, Department of the Army Information Security Program, 29 September 2000.

DEPARTMENT OF THE ARMY PAMPHLETS

DA Pam 738-750, Functional Users Manual for The Army Maintenance Management System

(TAMMS), 1 August 1994.

DA Pam 738-751, Functional Users Manual for the Army Maintenance Management System-

Aviation (TAMMS-A), 15 March 1999.

FIELD MANUALS

FM 1-300, Flight Operations Procedures, 15 July 1998 (will be revised as FM 3-04.300).

FM 3-0 (FM 100-5), Operations, 14 June 2001.

FM 3-25.26 (FM 21-26), Map Reading and Land Navigation, 20 July 2001.

FM 3-52 (FM 100-103), Army Airspace Command and Control in a Combat Zone,

1 August 2002.

FM 3-55 (FM 100-55), Operations, 14 June 2001.

FM 6-30, Tactics, Techniques, and Procedures for Observed Fire, 16 July 1991 (will be revised

as FM 3-09.3).

FM 17-98, Scout Platoon, 9 September 1994 (will be revised as FM 3-20.98).

FM 24-2, Spectrum Management, 21 August 1991 (will be revised as FM 6-02.70).

FM 34-1, Intelligence and Electronic Warfare Operations, 27 September 1994 (will be revised as

FM 2-0).

FM 34-2, Collection Management and Synchronization Planning, 8 March 1994 (will be revised

as FM 2-33.3).

FM 57-38, Pathfinder Operations, 9 April 1993 (will be revised as FM 3-21.38).

FM 71-100, Division Operations, 28 August 1996 (will be revised as FM 3-91).

FM 100-15, Corps Operations, 29 October 1996 (will be revised as FM 3-34.226).

FM 101-5, Staff Organization and Operations, 31 May 1997 (will be revised as FM 5-0).

GRAPHIC TRAINING AIDS

GTA 5-2-12, Coordinate Scale and Protractor, 2 January 1981.

JOINT PUBLICATIONS

JP 3-52, Doctrine for Joint Airspace Control in the Combat Zone, 22 July 1995.

JP 3-56.1, Command and Control for Joint Air Operations, 14 November 1994.

References-1

STP 34-96U14-SM-TG

TECHNICAL MANUALS

TM 5-4930-230-13, Operator’s, Organizational, and Direct Support Maintenance Manual for

Tank and Pump Unit, Liquid Dispensing; for Truck Mounting, Military Design Tank and

Pump Units, Gasoline Engine Driven, Model (97403); Electric Motor Driven, Model

(97403), 17 July 1984.

TM 9-1425-691-10, Operator's Manual for the Setup, Teardown, and Loadout of the Hunter

Short Range System, 1 March 1996.

TM 9-1425-697-13, Operator's, Organizational, and Direct Support for the Mobile Maintenance

Facility (MMF), 1 March 1996.

TM 9-1720-694-23, Launcher/Arresting Gear Maintenance, 1 December 1996.

TM 9-5895-681-10, Shadow 200 Tactical Unmanned Aerial Vehicle (TUAV) Operator’s Manual,

1 October 2001.

TM 9-5895-681-20, Maintenance Manual Organizational and Direct Support for Shadow 200

Tactical Unmanned Aerial Vehicle (TUAV) w/Change 4, 11 February 2002.

TM 9-5895-681-CL, Shadow 200 Tactical Unmanned Aerial Vehicle (TUAV) Crewmembers

Checklist, 1 October 2001.

TM 9-5895-692-10 Vol 1, Operating Procedures for the RQ-5A Short Range System Volume 1,

1 January 2000.

TM 9-5895-692-10 Vol 2, Operating Procedures for the RQ-5A Short Range System Volume 2,

1 January 2000.

TM 9-5895-692-CL, Operator's and Crewmember's Checklist, 1 January 2000.

TM 9-5895-696-13, Remote Video Terminal (RVT) Operation and Maintenance, 1 March 1996.

TM 9-6115-642-10, Operator's Manual for Generator Set Skid Mounted, Tactical Quiet, 10kW,

MEP-803A (60 Hz) (NSN 6115-01-275-5061), 30 December 1992.

TM 11-5810-329-10, Operator's Manual For Digital Subscriber Voice Terminal TSEC/KY-68

(NSN 5810-01-082-8404) and Auxiliary Power Supply HYP-71/TSEC (NSN 5810-01-

082-8412), 3 June 1996.

TM 11-5820-890-10-1, Operator's Manual SINCGARS...ICOM, 1 September 1992.

TM 11-5820-890-10-3, Operator for Radio Set AN/PRC 119 VRC 87-92, 1 September 1992.

TRAINING CIRCULARS

TC 1-201, Tactical Flight Procedures, 20 January 1984.

TC 34-212, Unmanned Aerial Vehicle Aircrew Training Manual, 1 May 2000.

OTHER PRODUCT TYPES

Identification Keys, Applicable Identification Keys, 30 September 2002.

Unit Signal Operation Instructions (SOI)

Unit Standing Operating Procedures (SOP)

References-2

References

RELATED PUBLICATIONS

Related publications are sources of additional information. They are not required in order to

understand this publication.

Except where otherwise indicated below, the following forms are available as follows: DA forms

are available on the Army Publishing Directorate’s (APD) website (http://www.apd.army.mil/);

DD forms are available on the OSD website (http://web1.whs.osd.mil/icdhome/icdhome.htm).

FIELD MANUALS

FM 10-67-1, Concepts and Equipment of Petroleum Operations, 2 April 1998 (will be revised as

FM 4-20.12).

FM 10-67-2, Petroleum Laboratory Testing and Operations, 2 April 1997.

FM 20-3, Camouflage, 14 November 1990 (will be revised as FM 3-58.1).

FM 34-2, Collection Management and Synchronization Planning, 8 March 1994 (will be revised

as FM 2-33.3).

FM 34-2-1, Tactics, Techniques, and Procedures for Reconnaissance and Surveillance and

Intelligence Support to Counterreconnaissance, 19 June 1991.

FM 34-25 (FM 34-22) Corps Intelligence and Electronic Warfare Operations,

30 September 1987.

FM 34-43, RECCE-J Multiservice Procedures for Requesting Reconnaissance Information in a

Joint Environment, 7 June 1996 (will be revised as FM 2-40.4).

FM 34-80, Brigade and Battalion Intelligence and Electronic Warfare Operations, 15 April 1986

(will be revised as FM 2-19.4).

STANAGS

STANAG 3377, Air Recognition Intelligence Carry Forward Forms—Forms of Reports of Air

Recognition, 16 June 1980 (Change 7, 21 October 1993).

TECHNICAL MANUALS

TM 750-244-2, Procedures for Destruction of Electronics Material to Prevent Enemy Use

(Electronics Command), 14 March 1972.

TRAINING CIRCULARS

TC 34-55 (FM34-55), Imagery Intelligence, 3 October 1988.

DA FORMS

DA Form 2408, Equipment Log Assembly.

DA Form 2408-12, Army Aviator’s Flight Record.

DA Form 2408-13, Aircraft Status Information Record.

DA Form 2408-13-1, Aircraft Maintenance and Inspection Record.

DA Form 2408-13-2, Related Maintenance Actions Record.

DA Form 2408-13-3, Aircraft Technical Inspection Worksheet.

DA Form 2408-14, Uncorrected Fault Record.

DA Form 2408-18, Equipment Inspection List.

DA Form 2408-31, Aircraft Identification Card.

References-3

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

7^th Signal Command

Enterprise Email - Spiral 1

Concept of Operations

2012

March 3, 2010

Version 1.30

THIS DOCUMENT SUPERSEDES ALL PREVIOUS VERSIONS

DISTRIBUTION:

This document is intended for use by US Government agencies and their Contractors doing business with the United States Army

CIO/G6. This document is for information purposes only and is not to be construed as directive in Nature or official policy. This

document is available by request from the 7^th Signal Command (Theater) G3, ATTN: NETC-SFC, Fort Gordon, GA 30905-5832.

DISTRUBUTION STATEMENT C:

Distribution authorized to U.S. Government agencies and their contractors to protect technical information from automatic

dissemination under the International Exchange Program or by other means. Other requests for this document shall be referred to

7^th Signal Command (Theater) G3, ATTN: NETC-SFC, Fort Gordon, GA 30905-5832.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

DISCLAIMER

The contents of this document are not to be construed as an official Department

of the Army position unless so designated by other authorized documents. The

use of trade names in this document does not constitute an official endorsement

or approval of the use of such commercial hardware or software. Do not cite this

document for the purpose of advertisement.

CHANGES

Refer requests for all changes that affect this document to: G3 (Plans), 7^th Signal

Command, ATTN: NETC-SFC-O, Fort Gordon, GA 30905-5832.

DISPOSITION INSTRUCTIONS

Destroy this document when no longer needed. Do not return it to the

organization. Safeguard and destroy this document with consideration given to

its classification or distribution statement requirements.

Prepared by

Mr. Herman Wells

Enterprise Services Chief, 7^th Signal Command

__________________ Date____________

Prepared by

Mr. Tom Duke

Engineering Services Chief, 7^th Signal Command

__________________ Date____________

Reviewed by

Mr. Richard Breakiron

Deputy G3, Future Operations, 7^th Signal Command

__________________ Date____________

Released by

xxxxx

__________________ Date____________

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

CHANGE NOTICE

Date of Change

Version

Description

Number

of Change

1 Oct 2009

0.1

Initial draft

20-Nov 2009

0.2

2^nd draft

4 Dec 2009

0.3

Review with CTNOSC and

AGNOSC

7 Dec 2009

0.4

Additional clarification and removal

of non-spiral 1 issues.

14 Dec 2009

1.0

Final questions resolved and

document submitted for staffing and

signature

18 Feb 2010

Original author: LTC Peter Barclay,

CIO/G6

19 Feb 2010

1.05

Changed from DA directed

CONOPS to 7^th Signal Command

CONOPS

22 Feb 2010

1.06

Implemented changes from Tom

Duke and Richard Breakiron

23 Feb 2010

1.07

Implemented changes from LTC

Barclay

24 Feb 2010

1.08

Implemented changes from Roger

Loeb, Steve Simpkins, and Herman

Wells

24 FEB 2010

1.09

Implemented changes from meeting

with Richard Breakiron, Tom Duke,

Steve Simpkins, and Herman Wells

25 FEB 2010

1.1

Implemented changes from

PHONECON with Roger Loeb, MAJ

Moore, LTC Barclay, Keith Lowry,

Mr. Boyle, LTC Watkins, and

Herman Wells

1 MAR 2010

1.15

Incorporated comments from latest

GO level IPR

1 MAR 2010

1.20

Roger Loeb, CTNOSC, PMO, LTC

Barclay comments added

2 MAR 2010

1.25

Donald Greenlee and Joan Tracy

comments added

3 MAR 2010

1.30

Ensured document was publicly

releasable

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

(U) EXECUTIVE SUMMARY

(U) BACKGROUND

The strategic environment has changed significantly since the end of the Cold War, and

events since September 11, 2001 have dramatically demonstrated that we have entered

a new era of conflict with difficult challenges to overcome. To meet these challenges,

the Department of the Army requires enterprise services to create an information

advantage by providing seamless collaboration and moving the power of information to

the tactical edge. Implementing an Army Enterprise Email Service (EMCS) is a major

step towards meeting these needs.

(U) PROBLEM

Today’s joint force operations require extensive collaboration across organizational

boundaries and rapid deployments to world-wide locations. To operate across

organizational boundaries, our forces are hamstrung with excessive equipment (e.g.,

multiple user access devices), inefficient operations (e.g., multiple user email

addresses), and suffer the consequences of reduced capabilities (e.g., unable to quickly

find contact information for non-organizational personnel). Our current environment of

disparate, loosely connected organizational email systems has inherent deficiencies

that prevent net-centric operations and hinder cross-organizational collaboration.

(U) WAY FORWARD (VISION STATEMENT)

The Army plans to eventually consolidate existing email systems into a single enterprise

email service. The ultimate end state of the Army EMCS is to provide operational

forces with the ability to access email from any terminal attached to a DoD network in

any operational environment. Forces can easily discover the contact information for,

and exchange messages with, anyone in the DoD enterprise. Virtual teams, spanning

organizations and geographical locations, can create dynamic distribution lists and

share calendars. Deploying forces can seamlessly disconnect from the home station

and reconnect at forward locations without the need for intensive, manual administrative

processes. Distributed nodes at the tactical edge can operate as an integrated part of

the Amy EMCS when network connectivity is available or operate stand-alone, providing

local user email services when disconnected from the enterprise network. Forces have

stable identities allowing full collaboration to leverage the collective knowledge of U.S.

forces to defeat any enemy. The current acquisition effort is the first step in that

direction. This initial effort is a learning opportunity for the Army. Future acquisitions

may or may not be built on this foundation.

(U) BENEFITS

The Army EMCS will improve mission effectiveness; reduce vulnerabilities to cyber

attacks posed by adversaries, and save millions of dollars. In summary, those who

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

support the goals of our nation require robust global connectivity and email in a wide

variety of environments. The DoD must operate collaboratively across the collective

enterprise to seamlessly facilitate information-enabled operations. Army EMCS is the

first step.

NOTE: The Executive Summary and throughout this document, the desired end-state of

a consolidated email system is provided. In this way, leaders working on Spiral 1

understand the Army’s vision for the future. It in no way guarantees or is meant to imply

this will be the final end-state.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

(U) TABLE OF CONTENTS

TABLE OF CONTENTS

(U) INTRODUCTION

1.1

(U) Purpose

1.2

(U) Scope

1.3

(U) overarching Mission needs

1.4

(U) current ARMY EMAIL environment

1.5

(U) SPIRAL 1 ARMY EMAIL ENTERPRISE SERVICES (EMCS)

1.6

(U) acronyms, key terms, and references

(U) SPIRAL 1 ROLES AND RESPONSIBILITIES

2.1

(U) Army Chief Information Officer /G6

2.2

(U) Program Manager Army Knowledge On-line (PM-AKO)

2.3

(U) enterprise service desk

2.4

(U) 9th Army Signal Command

2.5

(U) Army global network opeRations and security center (agnosc)

2.6

(U) 7^th signal command (theater)

2.7

(U) conus theater network operations and security center (C-tnosc)

2.8

(U) Signal Brigades

2.9

(U) Network enterprise center (nec)

2.10

(U) information management officeR (imo)

2.11

(U) EMAIL MANAGED SERVICE PROVIDER (msp)

(U) CONCEPT OF OPERATIONS

3.1

(U) Operational Environments

3.1.1

(U) Home Station Operational Environment

3.1.2

(U) Established (semi-permanent) Operational Environment

3.1.3

(U) Austere Operational Environment

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

iii

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

3.2

(U) Users

3.3

(U) level of service

3.4

(U) Migration of users to EMCS

3.4.1

(U) Conditions

3.4.2

(U) Site Activities Concepts to be Performed by The Army

3.5

Operations and maintenance of ees

3.5.1

(U) CONOPS

3.5.2

(U) Level of Service

3.5.3

(U) Enterprise Service Desk

3.6

(U) Enterprise Email Administration

3.6.1

(U) Account Provisioning/De-provisioning

3.6.2

(U) Contract Personnel

3.6.3

(U) Group/Role Based Mailboxes

3.6.4

(U) Resource Mailboxes

3.6.5

(U) Distribution Lists

3.6.6

(U) Naming and Addressing

3.6.7

(U) System Administration

3.6.8

(U) NETOPs Oversight and Situational Awareness

3.6.9

(U) Individual Transfer/Deployment

3.6.10

(U) Organizational Deployment

3.7

(U) architecture

3.7.1

(U) Email Processing Nodes

3.7.2

(U) Tactical Processing Nodes (Distributed Nodes at Tactical Edge)

3.7.3

(U) Access Methods

3.8

(U) Interdependence

3.9

(U) Enterprise email service

3.9.1

(U) Message Generation, Exchange, Storage, and Search

3.9.2

(U) Army Global Address List

3.9.3

(U) Global Calendaring

3.9.4

(U) Task Management

3.9.5

(U) Security Features

3.9.6

(U) Security / Mission Assurance

3.9.7

(U) Governance

(U) SUMMARY

APPENDIX A - (U) ACRONYMS

APPENDIX B - (U) GLOSSARY

APPENDIX C - (U) REFERENCES

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

(U) INTRODUCTION

1.1

(U) PURPOSE

This document, 7^th

Signal Command Enterprise Email Spiral 1 (EMCS) Concept of

Operations (CONOPS), describes the concept of operations for initial managed service

enterprise email capabilities, which will:

 Operate in a fully networked, global collaborative environment.

 Initially address the full spectrum of Army email mission requirements at the non-

tactical level.

 Establish a baseline e-mail service in order to evaluate the EMCS on its ability to

support Army organizations within CONUS.

 Set the stage for ongoing operations and maintenance of the system after full

operational capability of Spiral 1 is complete.

1.2

(U) SCOPE

This CONOPS specifies the full operational capability (FOC) required to execute spiral 1

enterprise email operations across the Army enterprise and will set the stage for

expanded email capability for future requirements. The CONOPS describes the end

state for spiral 1 Army enterprise email service (EMCS) consistent with current joint

warfighting and intelligence community operations. Spiral 1 only applies to the

unclassified (NIPRNet) network within the Continental United States (CONUS) and will

have the capability to support up to 230,000 users.

1.3

(U) OVERARCHING MISSION NEEDS

To keep pace with the ever changing strategic global landscape, the Department of

Defense is pursuing the most comprehensive transformation since World War II. The

Army transformation efforts underway in support of the DoD are both evolutionary and

revolutionary in nature and intended to improve our national capabilities to meet the

demanding requirements of a nation at war, as well as future, full spectrum national

security requirements. National security transformation will attain a force capable of full

spectrum operations in a joint/inter-agency, network-enabled, and global collaborative

environment.

To meet national security challenges, the Army community requires enterprise

capabilities that provide an information advantage through network-enabled,

commander-centric operations and seamless collaboration across the entire enterprise,

while moving the power of information to the tactical edge. These enterprise

capabilities must be configured to achieve the appropriate balance between information

sharing and information security.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

The primary mission drivers for the Army EMCS are improved mission effectiveness by

using common, standard enterprise services; unification (e.g., improved security,

enterprise directory services, and identity management services), and significant cost

savings. A user’s email address should not change as the user moves between home

station, mission rehearsal or exercise, en route, and deployment. This includes

providing access to email from any location (using client software or a web-browser), a

complete global address list, universal calendar functionality, and similar enterprise

email capabilities. The objective is to improve U.S. Army operations by enhancing

communication across the Army enterprise. Military, civilian, and contractor personnel

supporting U.S. Army missions require the ability to:

 Access email capabilities from anywhere, at anytime, and from any place, whether

stationary or mobile.

 Find and validate the identity of, and securely exchange information with, people

within the Army enterprise and external entities (e.g., federal agencies, mission

partners, and coalition partners) with whom they must interact to perform missions.

 Coordinate efforts by sharing individual, organizational, and resource calendars

across the Army enterprise.

 Easily and effectively share information among virtual groups that are

geographically dispersed and organizationally diverse.

 Continue critical mission operations at a local level when disconnected from the

enterprise email network.

The Army community must:

 Improve the effectiveness of mission planning and execution by integrating and

extending email capabilities.

 Reduce the vulnerability of email to the growing cyber security threats by

eliminating unnecessary seams between the thousands of current heterogeneous

local networks.

 Reduce the cost of email by eliminating unnecessary administration and inefficient

network configurations to free up resources for other Army priorities.

The initial effort of implementing Army enterprise email as a managed service is the first

step towards ultimately achieving the overarching needs. It fulfills some of the

objectives completely, some of them partially, and some of them not at all, while

allowing the Army to understand both the value and the complexity of implementing

managed services.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

1.4

(U) CURRENT ARMY EMAIL ENVIRONMENT

Army organizations have independently implemented and optimized email capabilities

for effective use within their respective organizational boundaries. Consequently, the

Army enterprise contains multiple, disparate stove-piped email systems and processes

that prevent net-centric operations and hinder cross-organizational/mission

collaboration. Further, the multiple organizational email systems employ user access

devices that are uniquely configured to limit access to authorized users. In this current

environment users are unable to:

 Easily find and exchange information with personnel across operational

environments and across the DoD.

 View calendars and reserve shared resources external to respective local

organization.

 Send signed and encrypted email to many DoD personnel.

Linking islands of organizational networks with dissimilar security capabilities and

processes creates vulnerabilities. Unless corrected, these cross-organizational

vulnerabilities provide opportunities for enemies to apply increasingly sophisticated

cyber attacks. Collectively, sustaining the plethora of organization-specific email

systems within the Army enterprise consumes significant resources with estimated

annual operating costs in excess of $400 million. Dominant cost factors are the

administrative and technical support staffs required to support each organizational email

system at the post, camp, base, station and current APC.

The Army’s Active Directory (AD) structure is based on multiple generating forces’ forest

implementations of Microsoft Active Directory 2003 or in some cases 2008 in both the

Non-secure Internet Protocol Routing (NIPR) Network and the Secure Internet Protocol

Routing (SIPR) Network. Currently the Army’s NIPR AD environment consists of fifteen

(15) approved forests supporting approximately 300 sites and 950,000 users around the

world. The approved forests are: Space and Missile Defense Command (SMDC),

Continental United States (CONUS), Inspector General Network (IGNET), the Army

Reserves, Medical Command (MEDCOM), Military Entrance Processing Station

100

Command (MEPCOM), Accessions Command, Military Academy (EDU), Intelligence

101

and Security Command (INSCOM), National Guard, Corp of Engineers, Europe, Pacific,

102

Korea, and Southwest Asia. The Army’s SIPR AD is similar to the NIPRNet except at a

103

much smaller scope due to smaller user population.

104

Of special note is the current reliance of email on Army Knowledge Online (AKO). All

105

Army personnel are required to have an AKO email address, and this is the default (or

106

universal) address that all personnel use. All email destined for Army mail servers

107

external to the users enclave flows through AKO (see Figure 1 below). The figure

108

demonstrates the flow of email from logical enclaves (CONUS, the Managed Service

109

Provider (MSP), or Europe) to various users. It does not necessarily indicate which

110

Active Directory (AD) forest someone logs into (despite the triangles), but rather which

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

111

logical email enclave a user gets service from. Any use of Exchange within the Army

112

must take this fact into consideration when implementing user accounts. In addition,

113

local email user addresses are linked to a single email address registered with AKO.

114

Though this allows individuals in the Army to maintain one email username, it does not

115

provide transparency when existing users move from one location to another.

116

Usernames must be decoupled from the existing installations Exchange server and

117

paired with the receiving installation’s Exchange server.

118

119

Figure 1. (U) Depiction Email Routing Flow (LTC Peter C Barclay, 2010)

120

Today’s joint operations require extensive collaboration across organizational

121

boundaries and rapid deployment to world-wide locations. Currently, email users who

122

must operate across organizational boundaries are hamstrung with multiple user access

123

devices and/or hindered by reduced capabilities when interacting with non-

124

organizational Army and DoD personnel. Deployed forces must carry extensive support

125

equipment to temporary operating locations or lose connectivity with supporting

126

networks for extended periods of time.

127

The initial effort of implementing Army enterprise email as a managed service is not

128

intended to address every issue raised in this description of the current Army email

129

environment.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

130

1.5

(U) SPIRAL 1 ARMY EMAIL ENTERPRISE SERVICES (EMCS)

131

Army personnel will not experience any reduction in capability or service level from the

132

email service. They will be able to access email and a fully-populated DoD global

133

address list, and calendaring from any location (using client software or a web-browser).

134

Military members without access to their own thick client or desktop will be able to

135

manipulate email via a rich Exchange based web client with features such as drag-and-

136

drop, drop down buttons, pop-up windows (with editing), and tool bars. The email

137

service will provide support for mobile/wireless platforms such as RIM Blackberry or

138

Windows Mobile. The service will continue to support S/MIME for encrypting and

139

signing messages.

140

(U/FOUO) The EMCS will be operated by a managed service provider using Microsoft

141

Exchange 2010. They will provide a workable strategy and automated tools to lead in

142

the migration of users and mail based data from the current installation to the EMCS

143

location in an expedient and efficient manner with minimal direct touch labor assistance

144

from the local Network Enterprise Center. The MSP will comply with all relevant DoD

145

and Army policies, including DIACAP and DoD policy (DoD STD 5015.2) for retention

146

and archiving. The managed service provider will have a 24x7 Tier II service desk that

147

is electronically integrated with the Army’s Tier I Enterprise Service Desk (ESD). Army

148

personnel will contact the ESD, and the ESD will elevate relevant email problems to the

149

Tier II service desk for resolution. Metrics that provide a clear view of IT systems

150

performance and customer quality of service will be provided that detail email

151

availability and enable an enterprise strategy for service level agreements (SLAs).

152

1.6

(U) ACRONYMS, KEY TERMS, AND REFERENCES

153

(U//FOUO)Acronyms and key terms used in this document are contained in Appendices

154

A and B. Required and related publications and prescribed and referenced forms are

155

listed in Appendix C.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

156

(U) SPIRAL 1 ROLES AND RESPONSIBILITIES

157

2.1

(U) ARMY CHIEF INFORMATION OFFICER /G6

158

(U//FOUO) The CIO/G-6 is responsible to the Secretary of the Army and to the Chief of

159

Staff of the Army for all Information Technology activities of the Department of the Army.

160

The CIO/G-6 acts as the system owner and proponent by validating operational and

161

functional requirements for IT services, providing initial lifecycle development and

162

sustainment through replacement costs of these services, as well as funding

163

deployment and operations of these services.

164

(U//FOUO) From a managed service provider perspective, CIO/G-6 activities include:

165

a. Provide Army policies.

166

b. Establish Army operating rules and guidelines.

167

c. Provide enterprise level resources (funds).

168

d. Control the Decision Point to conduct Spiral 2 of the EMCS initiative.

169

2.2

(U) PROGRAM MANAGER ARMY KNOWLEDGE ON-LINE (PM-

170

AKO)

171

(U//FOUO) PM-AKO is the product developer and integrator for the intended EMCS

172

acquisition. PM-AKO will work with CIO/G-6 and the 9^th and 7^th

Signal Command to

173

consolidate operational and functional requirements to provide necessary capabilities

174

within the delivered service.

175

(U//FOUO) Within PM-AKO, the Product Manager for Area Processing Centers (PdM

176

APC) will:

177

a. Provide overall project oversight and responsibility for the migration process.

178

b. Develop the EMCS interface requirements.

179

c. Serve as the enterprise material developer for design and development of EMCS

180

capabilities.

181

d. Integrate future Global Network Enterprise Construct (GNEC) initiatives with

182

enterprise business systems including Army Knowledge Online, Windows Server

183

and Exchange migration, and others as appropriate.

184

e. Provide engineering support relative to GNEC messaging systems design and

185

deployment.

186

f. Establish and manages integration of the EMCS Global Address List and the

187

Joint Enterprise Directory Service (JEDS).

188

g. Implement interfaces for the GNEC environment.

189

h. Ensure all migration tools, software systems and scripts are approved (CoN,

190

ATO…etc).

191

Provide a list of credentialed individuals from the EMCS provider that will have

192

Top Level OU elevated privileges to support migration tasks.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

193

Provide for the establishment and implementation of the Army Tier 1 Enterprise

194

Service Desk.

195

2.3

(U) ENTERPRISE SERVICE DESK

196

(U//FOUO) The Enterprise Service Desk allows for the widest window of coverage using

197

the most efficient level of staffing. It leverages the skills of customer-centric analysts to

198

log, categorize, prioritize, and in some cases resolve incidents; thus freeing the more

199

technically focused Tier II help desk from routine issues. Army business users also

200

benefit from having a "single point of contact" to report problems, ask questions, request

201

information, and provide feedback. The ESD will:

202

a. Ensure a representative is on site for the acceptance meeting conducted after

203

migration is complete. This individual will assist the local NEC staff with initial

204

calls to the ESD for email support.

205

b. Accept responsibility for Tier 1 Help Desk issues after installation migration is

206

complete.

207

2.4

(U) 9TH ARMY SIGNAL COMMAND

208

(U//FOUO) The 9^th

Signal Command (Army), also known at Network Enterprise

209

Technology Command (NETCOM) establishes the standards and configuration

210

management and is the technical Command and Control (C2) authority for the Army’s

211

messaging system. NETCOM is responsible for implementing Army IT operational and

212

management policy as established by CIO/G-6. Consistent with these broad IT

213

responsibilities, NETCOM is the central manager for all enterprise messaging

214

operations. NETCOM manages and controls the system and service within operational

215

and functional requirements and reports the status of the system as necessary to

216

ensure nominal service levels are maintained across the enterprise.

217

(U//FOUO) NETCOM will:

218

a. Provide oversight over the execution of Managed Services and delivery for the

219

Enterprise.

220

b. Ensure that the Army’s consolidated active directory is the authoritative source

221

for Army GAL information.

222

c. Ensure DoD enterprise naming conventions are followed.

223

d. Resource 7^th

Signal Command to execute Spiral 1 of EMCS.

224

2.5

(U) ARMY GLOBAL NETWORK OPERATIONS AND SECURITY

225

CENTER (AGNOSC)

226

(U//FOUO) The AGNOSC supports Army NETOPS with status reporting, situational

227

awareness, and operational support for the Army's portion of the Global Information

228

Grid (GIG). The AGNOSC also provides technical direction to, and obtains status from

229

the CONUS Network Operations and Security Center (CNOSCs) with regard to CONUS

230

based Enterprise services. (U//FOUO) The AGNOSC:

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

231

a. Identifies, tracks, and manages all security areas relative to Enterprise

232

messaging servers within all Army AD forests IAW current policies and

233

procedures.

234

b. Directs the CTNOSC implementation of security programs, procedures, policies,

235

and IAVA patches concerning interconnection to Spiral 1 EMCS

236

c. Notifies and directs remediation actions to appropriate organizations

237

d. Develops and publishes technical guidance, procedures, and standards such as

238

TECHCON Implementing Memorandums

239

e. Expands security monitoring and management supporting spiral 1 EMCS to Army

240

white pages

241

f. Provide operational oversight and management of theaters of operation and

242

delivery of services throughout the enterprise environment.

243

g. Establish NETOPs and execute oversight of managed services

244

2.6

(U) 7^TH

SIGNAL COMMAND (THEATER)

245

(U//FOUO) The Signal Command (Theater) (SC(T)) is responsible for operating,

246

managing, and defending the LWN within theater in accordance with the Army’s Global

247

Network Enterprise Construct (GNEC). The SC(T) provides situational awareness/

248

Network Common Operational Picture (NETCOP), assigns restoration priorities,

249

directs/coordinates restoration activities, and ensures compliance with NetOps policy,

250

direction, and processes for all IT services in the theater to include managed services.

251

The SC(T)’s major mission components are life cycle management and operation of

252

theater LWN assets, command and control (C2) of theater NetOps, CND of the LWN,

253

and direct and general support to NECs and deployable units (e.g., Brigade Combat

254

Teams) stationed in the theater. The 7^th

Signal Command will:

255

a. Serve as the Army Signal Command (Theater) user proponent for the delivery of

256

enterprise services and provide C2 for the Network Operations and Security

257

Center during Spiral 1

258

b. Advise the Mail Service Provider of priorities of service. The priorities will be

259

consistent with the ARFORGEN model and Army priorities of work.

260

c. Ensure the on boarding NEC Director and Principal Staff understand the

261

procedures for migrating email accounts and follow on O&M responsibilities.

262

d. Ensure the on boarding NEC Director understands that security of the email

263

system will be ensured by the Mail Service Provider during the migration

264

process.

265

266

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

267

2.7

(U) CONUS THEATER NETWORK OPERATIONS AND SECURITY

268

CENTER (C-TNOSC)

269

(U//FOUO) The C-TNOSC is responsible for providing the Theater Signal Commands

270

with status reporting, situational awareness, and operational support for their portion of

271

LandWarNet. For spiral 1 of the Army EMCS, the C-TNOSC will:

272

Execute NETOPs within the regional Domains.

273

Provide oversight of delivery of services from the Network Enterprise Centers

274

(NECs) within their regions.

275

Provide MSP with outage information that might affect their service.

276

Receive and distribute MSP outage information to the affected AOR.

277

Coordinate the execution of spillage reports from the MSP via secure channels

278

(SIPRNet).

279

Perform operation, management, and defense of the TCP/IP networks that

280

provide wide area network connectivity.

281

Manage, direct and/or coordinate all resolution of all incidents and

282

attendant restoration actions.

283

Provide situational awareness of the LandWarNet hosted applications to

284

include performance, availability, Computer Network Defense (CND), and

285

network perimeter security.

286

Execute a change management process to ensure the prompt and

287

efficient handling of all changes to the operational environment while

288

minimizing risk and impact to the delivery of service. Also, provide

289

configuration management capability to record, maintain, store and audit

290

changes to an asset, device, application, operating system, etc.

291

Direct and ensure backups, exercise of disaster recovery plans and

292

disaster recovery in accordance with the Continuity of Service Plans.

293

Provide near real time reports regarding the performance of the MSP and

294

the availability of the messaging service. Report on compliance within

295

SLA provisions and performance.

296

2.8

(U) SIGNAL BRIGADES

297

(U//FOUO) Signal Brigades operate, manage, and defend a portion of the Army's IT

298

services within the Theater. Brigades consist of multiple components to include:

299

Regional Operation Centers (ROCs), Network Operation Centers (NOCs), and Network

300

Enterprise Centers (NECs).

301

2.9

(U) NETWORK ENTERPRISE CENTER (NEC)

302

(U//FOUO) The Network Enterprise Center (NEC) is responsible for operation of the

303

installation information technology infrastructure and is the provider of services at the

304

installation. This includes situational reporting activities, planning and engineering,

305

enforcement of local NetOps and IA policies, and Service Request support for

306

installation tenants.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

307

(U//FOUO) Prior to migration of user accounts, the NECs will:

308

a. Conduct C2 to assist in the provider migration effort.

309

b. Serve as a liaison between the customer support base and the on-site contact

310

team.

311

c. Provide a dedicated primary point of contact for the MSP during migration.

312

d. Grant permissions to MSP and AD User Objects so the MSP can perform

313

migration actions.

314

(U//FOUO) Upon completion of provider migration actions, the NECs will:

315

a. In conjunction with the service provider and TNOSC, coordinate and conduct Tier

316

II touch labor support.

317

b. Provide support for client configuration to support connectivity to the MSP

318

service.

319

c. Provide the MSP with outage information that might affect their service.

320

d. Receive and distribute MSP outage information to the installation users.

321

e. Receive and assist in spillage reporting and event handling with the MSP via

322

secure channels (SIPRNet).

323

f. Ensure network throughput and capacity is sufficient to support remote mail

324

capability.

325

2.10 (U) INFORMATION MANAGEMENT OFFICER (IMO)

326

(U//FOUO) The IMO is the office/individual who reports to a commander/director/chief

327

for coordination service. It includes management oversight, advice, planning, and

328

funding coordination of all IM/IT requirements (business and mission) for their

329

organization. The IMO assists the commander/director/chief in effectively managing the

330

organization’s IM/IT processes and resources that enable the organization’s business

331

and mission processes(U//FOUO) Information Management Officers will:

332

a. Serve as the primary interface between the NEC and the supported organization.

333

b. Serve as the organization interface to the NEC for troubleshooting of IT

334

equipment, software or process failures.

335

2.11 (U) EMAIL MANAGED SERVICE PROVIDER (MSP)

336

(U//FOUO) The MSP is responsible for:

337

a. Configuration and operation of the email service using MS Exchange 2010

338

in a manner that achieves or exceeds defined service levels.

339

b. Collaborate with TNOSC, ESD, and NEC in troubleshooting and

340

developing solutions for email incidents.

341

c. Monitoring the operating status of production systems and system logs.

342

d. Ensuring compliance with DOD and Army security policies to include

343

Security Technical Implementation Guides (STIG), Information Assurance

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

344

Vulnerability Management (includes IAVA reporting to the TNOSC) and

345

computing facility security certification and accreditation.

346

e. Performing disaster recovery per continuity of service plan.

347

f. A Tier II Service Desk for resolution of email problems.

348

g. Maintaining a “self help” website for common email problems. The website can

349

be integrated into the ESD Tier-0 (Knowledge Base) if required.

350

h. Continually providing the C-TNOSC and ESD with current server and connection

351

status information.

352

Execution of spillage recovery actions IAW proper policy under the direction of

353

the C-TNOSC.

354

Providing an on-site technical representative during migration to support the

355

migration process.

356

k. Providing specific guidance on how to interact with the MSP after migration is

357

complete. This can be a “smart book,” technical guide, procedures book, etc. but

358

must contain the information required for the NEC to connect to the mail servers,

359

decommission/create/request user email accounts, etc.

360

Executing a process to recover/remedy accounts that fail to migrate.

361

m. Begin cutover process only on an organization that has ESD deployed at their

362

site.

363

n. Not departing the migration site until all required accounts have been

364

successfully migrated to the service providers email servers.

365

o. As part of the design plan, creating a DRAFT CONOPS for O&M of the email

366

system for review by stakeholders. The DRAFT O&M CONOPS will detail how

367

the NECs will interface with the ESD/MSP operations and maintenance of the

368

email system. The CONOPS will address the responsibilities and actions of all

369

stakeholders in the O&M of the email system.

370

371

(U//FOUO) NOTE: This is not designed to be an all encompassing list of actions

372

provided by the MSP. Detailed information is provided in the Performance Work

373

Statement.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

374

375

(U) CONCEPT OF OPERATIONS

376

3.1

(U) OPERATIONAL ENVIRONMENTS

377

(U//FOUO) The ultimate end state of the Army EMCS (Figure 1) will support users

378

located at home station, established, and austere operational environments. Spiral 1

379

capabilities requirements are focused at supporting approximately 230k users in a

380

CONUS h

381

382

Figure 2. (U) Depiction of Operational Environments

383

3.1.1

(U) HOME STATION OPERATIONAL ENVIRONMENT

384

The home station operational environment encompasses users that operate from

385

continental United States (CONUS) locations and strategic locations outside the

386

continental United States (OCONUS) such as U.S. installations in Europe, Korea, and

387

Japan. These CONUS and OCONUS locations have well-established, robust

388

infrastructures - military forts, bases, camps, and stations, as well as other fixed

389

national defense and intelligence facilities, such as the Pentagon.

390

3.1.2 (U) ESTABLISHED (SEMI-PERMANENT) OPERATIONAL ENVIRONMENT

391

The established operational environment encompasses users that operate from fixed

392

and established operational environments outside the U.S., such as Kuwait or Bahrain.

393

The infrastructure at these locations is constrained by limitations of the local site and

394

hosting country, as well as geographical separation from CONUS operations, but

395

normally consists of permanent infrastructure and connectivity.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

396

3.1.3 (U) AUSTERE OPERATIONAL ENVIRONMENT

397

The austere operational environment encompasses users that operate from forward

398

deployed locations, such as battle groups, forward operating bases, and other

399

temporary locations in hostile areas (e.g., Iraq and Afghanistan), in response to events

400

around the world. The deployed forces carry the required supporting infrastructure to all

401

operating locations to accomplish required missions. It is imperative that forward

402

deployed forces have the ability to operate for extended periods of time, independent of

403

external infrastructure capabilities, and without reach-back to sustaining base support.

404

These forces also need the ability to dynamically reconfigure assets to optimize mission

405

operations such as shutting down non-essential communication.

406

NOTE: The Operational Environment paragraph and throughout this document, details

407

the desired end-state of a consolidated email system. In this way, leaders working on

408

Spiral 1 understand the Army’s vision for the future. It in no way guarantees or is meant

409

to imply this will be the final end-state.

410

3.2

(U) USERS

411

Users of the EMCS have full enterprise email capabilities. These users depend on

412

email to perform their daily mission functions. Typically, users are active military (or

413

reservists activated for duty/deployment), civilian employees, and designated support

414

contractors that support U.S. Army mission operations from long-term duty locations in

415

the home station environment. When working from their office desktop (or using a

416

portable computer with a VPN connection), users have the option to access the Army

417

EMCS using either a thick client application (e.g., Outlook or Entourage) or directly,

418

using a web-browser (e.g., Internet Explorer, Firefox, or Safari). In addition, these users

419

can access Army EMCS using a wireless handheld device (e.g., Blackberry or Windows

420

Mobile).

421

3.3

(U) LEVEL OF SERVICE

422

Although the Army desires varying levels of service, especially responsiveness for

423

senior personnel, Spiral 1 may only have a single level of service with an ability of the

424

service desk to escalate issues for general officers and senior executive service

425

personnel.

426

3.4

(U) MIGRATION OF USERS TO EMCS

427

3.4.1 (U) CONDITIONS

428

Army EMCS Spiral 1 provider will be responsible for the migration plan of users from

429

existing Army exchange servers to the EMCS servers.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

430

Depending on the migration plan, the Migration Team will be granted OU Admin rights

431

for each installation requiring migration but will not receive Forest or Domain admin

432

privileges.

433

There will be windows when the users/machines are available at the selected sites. Up

434

to 24hrs in advance a standard site migration can be terminated for emergency

435

reasons.

436

While the majority of the migrated clients will exist on the agreed to support baseline

437

EMCS, the Migration Team will be prepared to deal with exceptions.

438

Migration reporting and help desk issues will not fall on or use the ESD. The EMCS

439

provider will provide direct help desk for migration issues.

440

The 7th SC (T) will assist in the establishment of a single phone number for use by the

441

Migration Team for onsite needs.

442

The Migration Team shall establish procedures for problem accounts and all lessons

443

learned shall be incorporated into a knowledge base for use as the migration continues

444

from site to site.

445

The Migration Team shall develop a plan for reverse migration should the need arise.

446

3.4.2 (U) SITE ACTIVITIES CONCEPTS TO BE PERFORMED BY THE ARMY

447

(U//FOUO) A Draft Warning Order will be issued to the Signal BDEs and the C-TNOSC

448

at the release of the RFP. This WARNORD will identity the pilot sites and provide 14

449

days for the sites to answer the data call included in the Site Notification. The below

450

steps are expected to be repeated until all sites have migrated. Stakeholders Meetings

451

and AAR will only be conducted as necessary after the initial sites have migrated. It is

452

expected that the overall migration timeline will decrease from site notification to site

453

completion as the migration matures.

454

3.4.2.1

(U) PILOT SITE AND FOLLOW ON SITES

455

3.4.2.2

(U) STEP 1 - SITE NOTIFICATION (TO BE RELEASED WITH THE DRAFT

456

MIGRATION PLAN)

457

The Army will issue a site notification that outlines and includes the following items:

458

1. Data Call (all items of information necessary for provider to understand the

459

scope of the effort at the site, user break down by Tiers for migration (Tier

460

1 (Generals/SES/VIPs) and Standard users). The PILOT NEC will be

461

given 30 days to respond to the data call. All other site NECs will be given

462

14 days to respond.

463

2. Initial Project Timeline.

464

3. POC list for the Migration Team, EMCS Provider and PdM APC.

465

personnel.

466

4. Equipment list and software being delivered to the site.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

467

5. On site resources required by the PdM APC the EMCS Provider and the

468

Migration Team (office space, network drops, etc.).

469

3.4.2.3

(U) STEP 2 - STAKE HOLDER MEETING (5 DAYS AFTER RECEIPT OF

470

DATA CALL INFORMATION FROM PILOT SITE)

471

1. Members include: EMCS provider, PM AKO, 7^th

SC (T), Pilot Site Key

472

Stakeholders, BDE email support teams and Migration Team.

473

2. The purpose of the meeting is to resolve any information gaps, resource

474

issues, and technical issues. A finalized timeline including user availability

475

will be developed. Finalized set of procedures shall also be developed.

476

3.4.2.4

(U) STEP 3 - SITE SPECIFIC MIGRATION PLAN

477

The Migration Team publishes the site migration plan 30 days prior to the start of the

478

pilot site migration. The plan will include:

479

1. The approved and tested tools/scripts to support migration.

480

2. The migration schedule for standard users.

481

3. The migration schedule for Tier 1 users.

482

4. Required TTPs, User Guides and training material.

483

5. Last minute changes.

484

6. Required Government resources.

485

7. Specific required subject matter expertise (e.g. Tumbleweed, DoD

486

PKI…etc).

487

3.4.2.5

(U) STEP 4 - MATERIAL FIELDING BRIEF/MEETING (7 DAYS PRIOR TO

488

SITE MIGRATION START)

489

This meeting serves as the final checkpoint before the Migration Team’s travel to the

490

site. The 7^th

SC (T), BDEs and NEC will confirm that the organization is on track for the

491

migration and all tasks and preparations have been completed in accordance with the

492

site-specific migration plan. The NEC will provide the PdM APC and the Migration

493

Team with a dedicated phone number for their use and the building number and

494

location of required resources. The NEC will map users to the timeline slots provided

495

by the site-specific migration plan.

496

3.4.2.6

(U) STEP 5 - MIGRATION TEAM ARRIVES AND BEGINS MIGRATION

497

3.4.2.7

(U) STEP 6 - PAUSE AT THE 500 ACCOUNT MIGRATION POINT

498

After the first 500 user accounts are migrated at each site there will be a pause and

499

customer feedback will be gathered by at least 10% of the migrated users. Once the

500

feedback is collected and organized, a meeting between the 9^th SC (A), 7^th

SC (T),

501

BDE, NEC, PdM APC, and the Migration Team will occur to assess the data. The

502

decision to continue migration will be made if the migration is viewed as successful. If

503

the migration of the 500 users is not successful, the PdM APC will provide guidance as

504

to a way ahead.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

505

3.4.2.8

(U) STEP 7 CONTINUE MIGRATION

506

During migration the following reports shall be provided to the PM, 7^th

SC (T) and the

507

NEC.

508

a. Planned versus Execution of migration

509

b. Trend analysis of issues

510

c. User created issues (top 5 items)

511

d. NEC created issues (top 5 items)

512

e. Provider created issues (top 5 items)

513

f. Unknown issues (top 5 items)

514

The trend data will provide real time feedback and recommendations for changes to the

515

migration guide, future plans and the ESD call trees used to assist with the O&M tasks.

516

3.4.2.9

(U) STEP 8 MIGRATION COMPLETION

517

The 7^th

SC (T) as described in the Material Fielding regulations shall conduct a formal

518

acceptance. The provider will be required to remove all tools or scripts used for the

519

migration.

7thSC (T) reserves the right to verify that no trace is left. If applicable, 7^th

520

(T) will issue guidance on the disposition of the existing exchanges servers. The

521

CTNOSC will provide input to the acceptance decision based on the

522

reporting/performance of the provider with respect to migration and service to the users

523

migrated.

524

3.4.2.10

(U) PILOT AAR

525

Upon completion of the PILOT site, an AAR will be conducted with all key stakeholders.

526

All issues and process changes will be discussed and a final timeline for future

527

migrations shall be presented and agreed to. A back brief will be provided to 9^th

SC and

528

the CIO/G6 Senior leadership.

529

3.5 OPERATIONS AND MAINTENANCE OF EES

530

3.5.1 (U) CONOPS

531

A DRAFT CONOPS for O&M will be published by the provider as part of the design

532

plan. The DRAFT CONOPS will be reviewed by 7^th

Signal Command (T) and

533

associated Stakeholders for acceptance into the final plan for delivery of additional

534

services.

535

3.5.2 (U) LEVEL OF SERVICE

536

Army EMCS Spiral 1 shall function as a MAC II capable system. (U) Upgrades of

537

Storage

538

The monitoring of the mail box storage capability is reported in accordance with the

539

performance management plan and SLA established for the program. It is expected

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

540

that communications between the EMCS provider and the CTNOSC will facilitate

541

proactive management of the EMCS for its users. The elevation of the average mailbox

542

size storage limit is tightly controlled by the 7^th

SC (T) and the PM AKO for EMCS.

543

3.5.3 (U) ENTERPRISE SERVICE DESK

544

(U//FOUO) A centralized Army Enterprise Service Desk (ESD) provides the first level of

545

service to all enterprise email users across the Army community to ensure quality

546

service delivery to all Army users, at all levels, and across all operational environments.

547

The ESD monitors the system and provides the supported user base with the status of

548

email services:

549

 The focal point for enterprise email operations and decisions involving service and

550

restoration priorities and the first tier of Army customer support.

551

 Support on a 24 x 7 basis where all users are able to contact the ESD via a single

552

phone number, a web form, live chat, or email to report all problems or inquiries

553

related to the service.

554

 A user “self-help” web site.

555

 A disciplined process to receive customer contacts, catalog all requests in a

556

centralized database, and resolve issues as appropriate.

557

 A mechanism to elevate unresolved trouble calls to the system administration

558

response team.

559

The ESD provides for common policies, tools, and training related to email and

560

enhances the ability to comply with security auditing and reporting requirements. A

561

centralized ESD provides for a dramatic reduction in the number of service desk

562

personnel distributed around the globe. Where a physical presence is required

563

(primarily hardware related and life-cycle maintenance) local NECs perform component

564

replacement and on-site support to respond to service requests and system problems

565

that cannot be resolved remotely by the ESD center.

566

The current ticketing system for the ESD is ITSM/Remedy and CA. The EMCS

567

provider should use tools to minimize or eliminate any swivel chair operations to allow

568

for trouble ticket tracking and resolution and archiving and seamless communications

569

between the ESD and the EMCS provider. The EMCS will have the tools required to

570

integrate into the ESD objective ticketing system.

571

The EMCS shall provide a Tier 2 service desk in order to solve mail related issues that

572

are above the ESDs capabilities. It is desirable for the EMCS Provider to coordinate

573

with the ESD and provide troubleshooting guides to support maximum possible first call

574

resolution by the ESD. Also the EMCS Provider will have web based troubleshooting

575

guides or tools available to the users, IMOs at the organizations and NECs for locations

576

migrated to the EMCS.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

577

578

3.6

(U) ENTERPRISE EMAIL ADMINISTRATION

579

3.6.1 (U) ACCOUNT PROVISIONING/DE-PROVISIONING

580

The Army EMCS uses the enterprise identity management service and the DoD

581

Enterprise Username. The Army EMCS GAL is not the authoritative source for

582

attributes in the enterprise email directory. The primary method of provisioning and de-

583

provisioning an enterprise email account is automated and is initiated by Army

584

processes. The secondary method is manual provisioning and de-provisioning of the

585

email account by an enterprise administrator. In the case of manual provisioning and

586

de-provisioning (such as a group mailboxes) the “user” is vetted by a standard process.

587

Military members and Army Civilian member are provisioned with an account when

588

required by their position.

589

3.6.2 (U) CONTRACT PERSONNEL

590

Personnel employed by the Army under contract will be provisioned with an account

591

upon the start of work under an Army contract (that requires email). Contract personnel

592

will retain their account only for the duration of their contract.

593

3.6.3 (U) GROUP/ROLE BASED MAILBOXES

594

The Army EMCS provides mailboxes with names that are based on an organizational

595

group and mailboxes that are based on a role. For example, a particular command may

596

want an organizational (or group) mailbox which several people have permission to read

597

and action the emails that arrive in that mailbox. There are also operational instances

598

where a particular role or "position" must have a mailbox which several people must be

599

able to both read and send as in order to accomplish the mission. An example of this is

600

a battle captain or watch officer.

601

The request and approval process for these mailboxes will be defined by the CIO/G-6

602

and executed IAW procedures to be released in a future Technical Authority

603

Implementation Memorandum. The Army Operations Oversight Board will create an

604

approval board (the Army Email Change Management Approval Board) for group and

605

resource mailbox requests. Consideration from an organizational operations (S3/G3)

606

element for support and service will define an organizational requirement.

607

Determination concerning whether this is a baseline service is still being researched

608

and will be documented in a process defined by the CIO/G-6 and executed IAW

609

procedures to be released in a future Technical Authority Implementation Memorandum.

610

3.6.4 (U) RESOURCE MAILBOXES

611

Requests for creation of a resource mailbox (e.g. conference room calendar or shared

612

vehicle calendar) will be approved by the first O-6 in the chain of command, and will

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

613

then flow through the Enterprise Service Desk to the Email Service Desk for

614

implementation. Requests for creation of a distribution list must identify the individual(s)

615

who will be responsible for managing that resource mailbox (i.e. receiving/responding to

616

requests for the resource).

617

3.6.5 (U) DISTRIBUTION LISTS

618

Requests for creation of a distribution list will be approved by the first O-6 in the

619

chain of command, and will then flow through the Enterprise Service Desk to the

620

Email Service Desk for implementation. Requests for creation of a distribution

621

list must identify the individual(s) who will be responsible for managing that

622

distribution list (i.e. adding/removing membership in the list).

623

3.6.6

(U) NAMING AND ADDRESSING

624

3.6.6.1

(U) MAILBOXES WITHIN THE ENTERPRISE SYSTEM

625

The Army EMCS uses an underlying email domain name that is applicable to all users

626

(e.g. @mail.army.mil) however each of the military services uses an aliased email

627

domain name for their service (e.g. @us.army.mil, @navy.mil, etc) mailboxes in

628

deployed organizations.

629

The Army EMCS will comply with the provisions listed in ALARACT 021-2010 with

630

regard to naming conventions and mailboxes.

631

An intent of enterprise email is to provide a single email address for soldiers, no matter

632

where they are, whether deployed or not. The enterprise email system will be

633

configured to forward mail to tactical Exchange servers for those users who are getting

634

service from a tactical unit’s Exchange server. In order to retain the appearance of a

635

single email, the Exchange servers of deployed and tactical forces must be properly

636

configured. Specific configuration details will be defined by the CIO/G-6 and executed

637

IAW procedures to be released in a future Technical Authority Implementation

638

Memorandum.

639

3.6.7 (U) SYSTEM ADMINISTRATION

640

The Army EMCS employs a centralized system administration function that operates

641

twenty-four hours per day, seven days a week. The System Administration function

642

spans both the enterprise data center network and the distributed nodes at the tactical

643

edge. The use of a single email service:

644

 Greatly reduces diverse breadth of knowledge required for effective email system

645

administration relative to that required to sustain multiple disparate organizational

646

email systems.

647

 Allows for increased depth of expertise through enterprise-wide focused training

648

and certification programs.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

649

 Significantly reduces the number of system administrators required to support the

650

Army enterprise.

651

While centralized enterprise email system administration has many advantages, it

652

presents some continuity of operations challenges. The following enterprise email

653

actions mitigate continuity of operations risks:

654

 Establish safeguards to protect from inadvertent and malicious damage;

655

 Establish a rigorous vetting process to select system administrators;

656

 All email administrator accounts will be configured/provisioned with a smart card,

657

and accessed only using smart card authentication.

658

 Require system administrators to meet increased training and certification levels;

659

 Allocate roles and functions to ensure redundancy, i.e., ”second set of eyes” for

660

critical operations;

661

 Increase restricted access and limit authorizations - no single system administrator

662

has total access or is authorized to perform all functions; and

663

 Enhance monitoring and recording of system administration actions.

664

3.6.8

(U) NETOPs Oversight AND SITUATIONAL AWARENESS

665

Currently, the Army’s ITSM is BMC ITSM (Remedy 7.6) and CA Unicenter, used by the

666

AGNOSC and TNOSCs. The Enterprise Email Managed Service Provider is

667

encouraged to identify, and eventually implement, an optimum approach for

668

interoperation between their ITSM and the Army’s ITSM. This will allow the ESD to

669

seamlessly interface with the email service provider. As stated in 3.5.8, the EMCS

670

provider should use tools to minimize or eliminate any swivel chair operations to allow

671

for trouble ticket tracking and resolution, and archiving and seamless communications

672

between the ESD and the EMCS provider.

673

674

3.6.9 (U) INDIVIDUAL TRANSFER/DEPLOYMENT

675

The Army EMCS has administrative tools that enable user mailboxes to easily and

676

quickly move to accommodate user transfers and deployments. An individual transfer

677

and/or deployment is a simple process whereby a user’s email moves from an email

678

server in one location to another email server in a different location (i.e. different data

679

center) that is more efficient for network access because the user has physically

680

relocated. This mailbox move is accomplished by central system administrators and is

681

invisible to the average user. The Enterprise Email Managed Service Provider will

682

provide a method in which user email data stores can me migrated/moved between

683

forests or individual enclaves as necessary.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

684

3.6.10

(U) ORGANIZATIONAL DEPLOYMENT

685

In the same fashion as individual transfers, the Army EMCS has administrative tools

686

that enable the transfer (and pre-positioning) of groups of user mailboxes to easily and

687

quickly move to accommodate organizational deployments. When a remote node is

688

required (for the organization), mailbox information must be copied/pre-positioned onto

689

the remote node to minimize WAN bandwidth consumption upon re-connection and

690

synchronization. When an organization is deploying and requires the stand up of their

691

own remote node with copied/pre-positioned mailbox information, the 7^th

Signal

692

Command will work with the MSP (and the PdM APC) to coordinate the transfer of data.

693

3.7

(U) ARCHITECTURE

694

(U//FOUO) The architecture for the ultimate end state Army EMCS (Figure 2) includes

695

an enterprise data center network, Wide Area Network (WAN), and distributed nodes

696

that extend enterprise email to the tactical edge. The architecture must provide email

697

service for all types of users across all operational environments. The architecture is

698

configured to link the sustaining base to the tactical edge, and optimized for conducting

699

joint and interagency operations. Data centers work as a synchronized enterprise email

700

capability to optimize user responsiveness. As mentioned above, Spiral 1 is expected

701

to support only CONUS based users.

702

3.7.1 (U) EMAIL PROCESSING NODES

703

(U//FOUO) In the ultimate end state of Army enterprise email, there will be four types of

704

email processing nodes However, Spiral 1 only consists of enterprise processing nodes

705

and correct configuration to support forwarding to tactical processing nodes. It is

706

expected there will be two enterprise processing nodes located in CONUS. The

707

managed service provider is not responsible for any operation of email in tactical

708

processing nodes; however they will be responsible for ensuring that the managed

709

service is correctly configured to allow the forwarding of email for users in those nodes.

710

3.7.1.1

(U) ENTERPRISE PROCESSING NODES

711

(U//FOUO) Enterprise Processing Nodes are data centers, located either in Defense

712

Enterprise Computing Centers ((DECCs) or in commercial facilities that meet DoD

713

security requirements and are services by an Army Top Level Architecture (TLA) stack.

714

3.7.1.2

(U) INSTALLATION PROCESSING NODES

715

(U//FOUO) Installation Processing Nodes (IPNs) are operated in Army data processing

716

centers and are logical extensions of the Area Processing Centers. These are located

717

on large bases and exist to minimize WAN traffic. IPNs are not part of the Spiral 1.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

718

3.7.1.3

(U) REMOTE INSTALLATION PROCESSING NODES

719

(U//FOUO) Remote IPNs are also operated in Army data processing centers, but are

720

located on remote bases that have limited connectivity. Remote IPNs exist to minimize

721

the impact of the limited connectivity by reducing WAN traffic. Remote IPNs are not a

722

part of Spiral 1.

723

3.7.2

(U) TACTICAL PROCESSING NODES (DISTRIBUTED NODES AT TACTICAL

724

EDGE)

725

Enterprise email users in the austere operational environment at the tactical edge must

726

be equipped to continue their mission functions when disconnected from the WAN.

727

.Tactical Processing Nodes are operated by Brigade Combat Teams (BCTs), other

728

Army brigades, or higher level Army organizations for the purposes of retaining local

729

functionality, and the nodes move with the brigade from training to deployment and

730

back. Local authentication and directory services will be used when a distributed node

731

is operating in disconnected mode. Each tactical processing node has a local email

732

server that:

733

 Operates in “stand-alone” mode when disconnected from the WAN.

734

 Preserves full enterprise email functionality among tactical edge users at

735

disconnected nodes.

736

When deployed, tactical edge user mailboxes move to the tactical processing node

737

servers supporting the deployed users. The Army EMCS will be configured to allow

738

users to forward email to the deployed node so that there is no need to change the

739

primary email addresses of deployed users.

740

3.7.3

(U) ACCESS METHODS

741

3.7.3.1

(U) THICK CLIENT METHOD

742

Users can access the Army EMCS using a thick client application (Outlook 2007 or

743

newer, or Entourage) on their desktop. This access method enables users to

744

experience all available functionality and operate in cached mode so they can still

745

access email and calendars locally when disconnected from the WAN.

746

3.7.3.2

(U) WEB CLIENT METHOD

747

Users can access the Army EMCS using a web browser (e.g., Internet Explorer, Firefox,

748

Safari) when connected to the appropriate network (NIPRNet or SIPRNet).

749

3.7.3.3

(U) WIRELESS HANDHELD DEVICE METHOD

750

Users can access the Army EMCS using Army issued/approved wireless handheld

751

devices (e.g., Blackberry, Windows Mobile). Wireless access is more limited than the

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

752

web client. Since there are two main handheld devices - one operating in a push

753

delivery method and the other operating in a pull method - offline access is determined

754

by the delivery method as well as the type of device used. Wireless handhelds must

755

have the capability to sign and encrypt/decrypt email messages.

756

3.8

(U) INTERDEPENDENCE

757

The Army EMCS relies on DoD and interagency capabilities to maximize

758

complementary and reinforcing effects while, at the same time, minimizing

759

vulnerabilities. Key enablers for the Army EMCS are identity management (including

760

Public Key Infrastructure (PKI)) and security services, authoritative directory services,

761

and the Global Information Grid (GIG).

762

3.9

(U) ENTERPRISE EMAIL SERVICE

763

The Army EMCS supports the Army enterprise by enabling the exchange of information

764

required to keep commanders and leaders informed worldwide and achieve the

765

information advantage. It is an important medium used to exchange information among

766

those supporting and executing the U.S. Defense missions. The Army EMCS enables

767

the following key operational capabilities:

768

 Discovery - users can use enterprise directory services to easily discover the

769

contact information for anyone in the Army enterprise.

770

 Ubiquitous Access - users have the ability to access their enterprise email from

771

any terminal attached to the DoD network in any operational environment without

772

loss of features or service level (using PKI certificate authentication); and from their

773

Army laptop/wireless handheld device when traveling.

774

 Stable Contact Information - user contact information is available and accurate so

775

that users can quickly and easily contact others that have information or

776

knowledge required to solve a problem.

777

3.9.1 (U) MESSAGE GENERATION, EXCHANGE, STORAGE, AND SEARCH

778

The Army EMCS provides standard email functionality to include sending, receiving,

779

storing, and archiving messages to ensure compliance with an enterprise

780

document/record management system; transporting multi-media file attachments and

781

rich text; accessing contact information for all Army users regardless of location; and

782

performing full text search of email messages and attachments. The Army EMCS

783

requirements are specified in the Army Enterprise Email Requirements Specification

784

Spiral 1, Version 2.0, dated 7 December 2009.

785

3.9.2 (U) ARMY GLOBAL ADDRESS LIST

786

The Army EMCS provides a global address list (GAL) that contains all Army non-

787

sensitive personnel and shared resources. The GAL must use standard, consistent

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

788

metadata for naming conventions, be easy to use, and support distribution lists.

789

Specific GAL requirements are specified in the Army Enterprise Email Specification

790

Spiral 1. The managed service provider takes authoritative data from the Army’s AD

791

forests (via EDS-Lite) and provides it to the GAL.

792

3.9.3

(U) GLOBAL CALENDARING

793

The Army EMCS provides calendaring capabilities to include enterprise-wide sharing of

794

individual, organization, and resource calendars. Specific global calendaring

795

requirements are identified in the Army Enterprise Email Requirements Specification for

796

Spiral 1. When the Army migrates to Exchange 2010, the MSP will federate its

797

Exchange with the Army to allow cross-forest visibility of calendars.

798

3.9.4 (U) TASK MANAGEMENT

799

The Army EMCS provides task management capabilities to include creating, editing,

800

deleting, sorting, and grouping tasks, as well as displaying task deadlines within the

801

calendar. Specific task management requirements are identified in the Army DoD

802

Enterprise Email Requirements Specification for Spiral 1.

803

3.9.5 (U) SECURITY FEATURES

804

The Army EMCS provides security capabilities to include the ability to sign and encrypt

805

messages and attachments; perform email classification markings in accordance with

806

DoD security policies; and filter email transmissions. Specific security requirements are

807

specified in the Army Enterprise Email Requirements Specification for Spiral 1.

808

3.9.6 (U) SECURITY / MISSION ASSURANCE

809

The Army EMCS is envisioned to be an essential U.S. National, Defense, and

810

Intelligence asynchronous communication capability. Therefore, it is imperative that no

811

potential adversary is capable of disabling the Army EMCS or exploiting the service in

812

order to deceive. The Army enterprise email architecture includes distributed data

813

centers that are configured with no single point of failure or vulnerability - human,

814

physical, network, or technology. Robust continuity of operations plans (COOP) and

815

disaster recovery plans are in place. The Army EMCS is configured to preclude any

816

potential adversary from intruding on national Army email communications or inflicting

817

any harm by Army EMCS exploitation. Army EMCS transmissions and data at rest are

818

secure and protected against any unauthorized access.

819

3.9.6.1

(U) POLICY AND GPO IMPLEMENTATION

820

The Army sees value in retaining the ability to implement policy and GPOs on its

821

schedule however, the Army also understands the need to implement controls on

822

policy implementation. The EMCS and the government will develop a “GPO

823

implementation schedule”, based on geographical time, in order to implement

824

GPOs within 24 hours of receipt, but to implement those only during the times

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

825

that will have the least operational impact, unless the government directs

826

immediate implementation due to a severe security risk. Most policies, such as

827

the requirement to edit using plain text format and a policy to enforce editing in

828

plain text only, will be determined by the AGNOSC.

829

3.9.6.2

(U) FILTERING AND IRONPORTS

830

The Army will operate Ironport devices at the routing hubs in order to ensure

831

consistent filtering across the CONUS, and provide anti-spam services for email

832

into and out of CONUS Exchange. The filtering rule sets will be routinely

833

provided by the AGNOSC. Changes to the filtering rule sets will be approved by

834

the AGNOSC IAW Technical Authority Implementation Memorandum TA 2006-

835

003, 15 Sept 2009.

836

3.9.6.3

(U) MAIL RELAYS AND ROUTING HUBS

837

Mail relays and routing hubs will be operated by the Army. All email inbound

838

email will traverse Exchange Routing Hubs, all outgoing email from the

839

enterprise email servers will traverse the Routing Hubs.

840

3.9.6.4

(U) DNS

841

The Army CONUS TNOSC will manage the DNS records for the enterprise email

842

system. The managed service provider will coordinate with the CTNOSC for any

843

changes as they are required.

844

845

3.9.7 (U) GOVERNANCE

846

Army governance structure is employed for enterprise email and other enterprise

847

information services. Consistent with DoD and IC policy, this governance structure

848

consists of a governance board whose membership includes senior leadership from

849

Office of the Secretary of Defense, Director of National Intelligence, IC Agencies, the

850

Military Departments, the Chairman of the Joint Chiefs of Staff, the Commanders of the

851

Combatant Commands, and Defense Agencies (hereafter referred to collectively as the

852

“DoD Components”). Consumers of enterprise services are represented in the

853

governance structure.

854

The Army governance structure addresses DoD enterprise email requirements,

855

architecture, services determinations, and service level agreements in coordination with

856

the Executive Agent (EA) for the Army EMCS. The EA is established to execute Army

857

EMCS day-to-day operations with oversight by the Army enterprise service governance

858

structure, consistent with other Army enterprise information services. The EA

859

addresses unresolved issues with the Army EMCS governance board.

860

The governance structure is supported by the DoD Rate Management Council (RMC),

861

which identifies the fair method of cost sharing by determining the cost per user based

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS

Military reference books and manuals (2009-2023, Volume 7) - page 5