V Corps All Source Analysis System SOP

April 25, 2001

V CORPS Analysis and Control Element

All Source Analysis System Standing Operating Procedures (SOP) V Corps All Source Analysis System SOP

SECTION I

1. PURPOSE: This SOP delineates responsibilities and outlines duties for All Source Analysis System (ASAS) operations for the Analysis and Control Element (ACE).

2. SCOPE: This SOP applies to all personnel, assigned, attached, OPCON, or supporting the ACE at its location. This SOP covers operations with the ASAS and manual analytical operations as required.

SECTION II

1. MISSION: The mission of the ACE is to provide all-source, timely and predictive intelligence to the supported commander. The ACE will plan, direct and synchronize intelligence collection operations in support of the commander’s Priority Intelligence Requirements (PIR) and targeting efforts, produce All Source (AS) intelligence products for subordinate units, and disseminate intelligence and targeting data to subordinate units.

2. CONCEPT OF OPERATIONS: The ACE will accomplish this mission by incorporating ASAS into daily operations. Operators will use ASAS in the production of threat estimates, country studies, INTSUMs, Read books, RFIs and all aspects of daily operations. ASAS will interface with a variety of communication links and intelligence organizations, providing single-source and all-source intelligence for the use of the supported commander, and for consumption by higher, lower, and lateral headquarters. ASAS will be the backbone of the ACE analytical effort. However, the ACE will use both integrated and stand-alone adjunct intelligence systems in addition to the ASAS in order to accomplish its mission. The ACE must be prepared to move at any time via air, rail or truck.

SECTION III

1. GENERAL OVERVIEW OF ASAS: ASAS is the All Source Analysis System. This system is composed of computer hardware, software and associated secure communications systems that provide seamless multi-source intelligence fusion and analysis to the US Army. ASAS does not replace the trained intelligence analyst or the trained intelligence officer. It is a tool that allows the intelligence professional to quickly collect, record and analyze vast amounts of information so that a common picture can be produced and disseminated in support of the commander. ASAS has four main components: the All Source Enclave (ASE), the Single Source Enclave (SSE), the Remote Workstation (RWS) and supporting communications devices.

a. All Source Enclave: The All Source Enclave is the heart of ASAS. The ASE is the culmination point of the ASAS where information enters and is

2 V Corps All Source Analysis System SOP

analyzed and correlated to create completed intelligence products. The ASE is capable of accessing a vast amount of data stored in its various databases using an almost endless combination of discriminating factors. The ASE provides this intelligence through its correlated database (ASCDB) and software that accesses the information stored within by time, location, level of identity or other data elements. Information flows in and out of the ASE through the CCS. Within the ASCDB, inbound information goes through a complicated process outlined in TAB _ of Appendix _ AS Information Flow. The intelligence is disseminated via the RWS to the other ACEs, collection assets, or clients. The AS workstations (ASW) have two monitors attached to each CPU. One monitor is a graphics screen used to display map data while the other is a text monitor dedicated to queries and word processing. Each workstation can create queries, overlay/map operations, generates messages, and conducts interactive message parsing. The workstations are each responsible for various functions within the ASE. These analyst-operated functions are known as Functional Identities (FI). The FIs within the ASE are Database (ALL), Situation (SIT), Targeting (TGT), Intelligence Collection Management (ICM) and Supervisor (SPV). Refer to Annex _ and its Appendices for additional details.

b. Single Source Enclave: The Single Source Enclave serves as intelligence discipline-specific information “pre-processors” for the ASE. The SSE workstations have a windows based graphic user interface (GUI) and allow the operator to point and click on menus and applications. Analysts operate workstations responsible for tracking, analyzing and reporting on a different intelligence disciplines. The SSE workstations process COMINT, ELINT, IMINT and HUMINT data for analysis. Positions within the SSE are Analyst and Senior Analyst for each of the intelligence disciplines and a System Administrator. Refer to Annex _ and its Appendices for additional details. SSE provides the current SIGINT picture of the battlefield by fusing COMINT and ELINT reports with known unit locations. It maintains a graphic depiction of the current enemy electronic order of battle (EOB). The doctrinal enclave consists of two ELINT positions, two COMINT positions, and access to INTELLINK. These databases are used to establish and maintain net and station continuity on assigned threat entities. Develops targets and correlates SS information that will then be passed to the ASE for further development, targeting or correlation. The SSE may also nominate targets directly if they have achieved TSS, and on rare occasions may send messages directly to clients. The preferred method is to send information to the ASE, correlate it with all other available information then send messages to clients (see Appendix 1 Single Source Information Flow).

c. Remote Work Station Block I: The Remote Work Station provides an ASAS link to the major subordinate units and the ACE. It can be utilized

at any level. The RWS is the tool by which units will receive and send information and intelligence. The RWS maintains multiple databases, overlay/map operations, conducts message parsing, sends E-mail, and develops/implements alarms and event criteria. The RWS has a windows based GUI, which gives the operator the ability to rapidly point and click onto an application. Refer to Annex _ for additional details.

d. Communications Devices: Text message traffic must enter the ASAS through the Communications Control Set (CCS) AN/TYQ-40/63 or a Communications Support Processor (CSP) i.e. FAST, AEPDS. Exceptions to this are of course possible. Additionally, files can be transferred into the ASAS workstations via FTP/XFTP when connected via a LAN/WAN. Each system has it’s own strengths and weaknesses. Refer to Annex _ and its Appendices for additional details.

SECTION IV

1. GENERAL OVERVIEW OF THE ACE: The ACE is divided into five main sections. Certain sections are further divided into sub-sections. The five sections include:

ACE Headquarters All Source Intelligence Section (ASIS) Targeting Section Systems Control (SYSCON) Collection Management

a. The ACE Headquarters consists of the Ace Chief and the ACE Sergeant Major.

b. The All Source Intelligence Section (ASIS) is comprised of three teams: Situation Development, CI/HUMINT and COMINT. Situation Development is responsible for IPB, database maintenance and the production of timely, accurate intelligence products. Intelligence production is a single, integrated system that merges separate single- discipline analysis and information into all source-based intelligence products / information (known as fusion). The information being created is for the commander’s maneuver, targeting, BDA, and other IEW support requirements. The process is a continuous cycle of RECEIVE- ANALYZE-SYNTHESIZE-REPORT.

c. The Targeting section is comprised of four teams: IMINT Team, Targeting Nomination Team, ELINT Team, and the CGS Team. The Targeting section provides the target intelligence data to support deep operations and achieve the commander’s objective of attriting or destroying the enemy’s capabilities. The ACE Targeting section

performs the following functions in support of deep operations. Conduct target value analysis (TVA) and intelligence preparation of the battlefield (IPB). Recommend high payoff targets (HPTs) and validate the high payoff target list (HPTL) based on threat capabilities and intentions. Nominate targets from the High Payoff Target List (HPTL) to the DOCC. Recommend engagement areas (EA), air corridors, and times for deep attacks. Locate, identify and track deep targets. Locate and track air defense artillery (ADA) and anti-aircraft artillery (AAA) along attack aviation routes and deep insertion routes. Provide input to the Air Force Air Tasking Order (ATO) for Air Interdiction (AI). Identify intelligence gaps and request collection coverage. Provide input to Situational Development Section for the ACE Intelligence Summary (INTSUM) and Battle Update Brief (BUB) slides.

d. The Systems Control section is responsible for the Trojan SPIRIT II communications system and the Communications Control Set.

e. Collection Management: The primary purpose of collection management is to answer the commander’s intelligence requirements while making the best use of scarce intelligence collection resources. The secondary purpose is to answer intelligence requirement of other intelligence users.

a. The second section is the Technical Control and Processing Section (TCPS). The TCPS is responsible for processing, conducting analysis, reporting, and doing database management by intelligence discipline. This single source section is further subdivided into three teams: SIGINT, HUMINT/CI, and IMINT. It is useful to think of this section as a “pre-processor” for the ASE; filtering the incoming information IAW the PIR/HPTL/HVTL so that focused intelligence information is sent to the ASE. The TCPS must work closely with the ASIS to maintain operational situational awareness, and to ensure that Single Source operations / priorities are in synch with the greater operational picture.

See FM 34-25-3, unit MTOE/TDA, and The Leader’s Guide to the All Source Analysis System for additional details on the ACE structure.

2. INFORMATION ENGINEERING CONCEPT: Information engineering is the systematic methodology to employing and supporting ASAS in an operational environment. There are three components to the Information Engineering Concept: Communications Architecture (CA), Information Architecture (IA) and Information Shaping (IS).

a. Communications Architecture: The three components of CA are: systems, protocols and capacity. What systems will be used to collect and process data, and produce intelligence? What protocols are required to

have connectivity with required systems? Will we get a Trojan line or will MSE be the only connection (capacity)?

b. Information Architecture: The three components of IA are: databases, database elements and intelligence reports. To which system in the ASAS suite do we want collectors reporting? What type of data and which databases need to be populated (data element)? What external intelligence reports will be required to provide the warfighter with the best picture of the battlefield?

c. Information Shaping: The three components of IA are: products, detail and fusion parameters. What are the product requirements? What specific products are required and what are the timelines? What level of specificity is required and in what context (detail)? Adjust fusion algorithms so that the consumer receives the proper level of detail.

SECTION V

1. GENERAL OVERVIEW BY POSITION

a. ACE CHIEF: Responsible for the overall direction of the ACE. Prioritizes work and supervises data flow between communication nodes and the workstations. This position is administrative and supervisory in nature. Primary liaison to outside agencies, commands and resources. Task organizes ACE personnel and automation to meet the needs of the mission and analytical demands. Responsible to the G2 for timely, relevant, accurate and predictive intelligence to answer the commander’s PIR. Coordinates the IEW Synchronization Matrix (ISM) and asset availability. Screens and tracks incoming requirements and reviews and approves outgoing products before they are released to clients when appropriate. Briefs VIPs on ACE structure and activity as well as the current enemy situation. Relies heavily on the Battle Captains to accomplish the mission.

b. SENIOR ANALYST: Responsible for the immediate direction of the AS and SS analysts. This position is administrative and supervisory in nature. Focuses ACE on current priorities and is responsible for refocusing ACE as mission requirements change. Shifts and reorganizes the work effort during operations to ensure continuous flow of information and intelligence to clients. Maintains the ACE status board. Assists the ACE Chief in preparing and delivering briefs. Monitors near real time SS activities and ensures that the proper information is passed to AS and is correlated correctly. Ensures all analysts know the most current PIR, HVTL and HPTL.

c. MASTER ANALYST: Plan and supervise ASAS operations and integration of automation into the units mission; supervise instruction of ASAS training management – to include ASAS skills test; evaluate unit and individual performance; troubleshoot hardware faults and software anomalies; direct and supervise the conduct of ASAS analytical tasks and mission requirements supporting the ACE.

d. ALL SOURCE ANALYSIS TECHNICIAN: Supervises and synchronizes the efforts of the ASE. Cross talks with the SSE to ensure that the ASCDB is populated with all relevant and current information. Resident expert on the enemy threat. Provides order of battle products to aid all analysts. Creates all graphic Intelligence Summaries (INTSUMs) and Intelligence Reports (INTREPs). Responsible for maintaining the current enemy situation and if the ASAS fails the manual SITMAP. Briefs current enemy situation during the Tactical Decision Making process or ACE huddles.

e. COLLECTION MANAGER (CM): Plans and synchronizes the collection plan. Validates, tracks and forwards RIs and requests to higher and monitors dissemination of intelligence products. Coordinates with the ASE and targeting cell to support the common picture of the battlefield. Develops PIR, SIR, SOR, ISM, and NAIs and briefs them at the Skunk Works. Works with the Asset Manager to coordinate the employment of assets and requesting asset support from higher. Works with both the ASE and SSE.

7 ANNEX A (ACE Chief) to ACE SOP

1. General.

Controls and directs operation of the ACE. Responsible to the G2 for timely and accurate intelligence products. Ensures ACE operations focus on and support mission requirements.

2. Responsibilities.

a. Overall ACE operations.

b. Coordinate intelligence collection, processing and analysis to create useable products.

c. Focus and redirect collection and analysis efforts as required.

d. Brief VIPs on current situation and ACE operations.

3. Pre Operations.

a. Coordinate for administrative support and supplies.

b. Brief ACE on supported unit mission.

c. Approve initial collection plan.

d. Inspect ACE equipment for mission readiness.

4. Operations.

a. Refocus analysts and assets as required.

b. Keep abreast of the current battlefield situation and brief VIPs.

c. Approve final collection asset allocation if conflicts arise.

d. Quality control products as they leave the ACE.

e. Supervise all ACE activity.

f. Conducts battle update brief every 4 hours. (See Appendix 1 to this Annex for format).

5. POST OPERATIONS

a. Coordinate for resupply.

b. Conduct After Action Reviews (AAR).

(1) Ensure that improvements for shortcomings are implemented (2) Ensure the tasks identified to sustain are implemented into the training program if they do not already exist.

d. Inspect ACE equipment for garrison operation and contingency planning. .

9 APPENDIX 1 (Battle Update Brief Format) to ANNEX A (ACE Chief)

1. General Situation:

a. Enemy Disposition and Strength. Include known and unlocated; deep, close, and rear.

b. Estimate of Future Enemy Activities. Include an IPB update; identify the full range of ECOAs 6-12 hrs, 12-24 hrs, 24-48 hrs.

c. Friendly Disposition. At least down to maneuver bde; lower for specialized units.

d. Friendly Operations. Present and Planned.

2. Intelligence Synchronization. Present by decision point (DP):

DP# : Status of Collection: Status of Analysis: Estimated Time of Satisfaction:

Repeat for all upcoming DPs

3. Status Reports (Personnel, Equipment, Misc Operations (not already briefed with DP-Synch), etc):

All Source Enclave Single Source Enclave Communications (NIPR, SIPR, JWICS) Targeting Collection Management: Friendly Disposition Asset Status

4. ACE Shift Focus/Schedule (Oncoming Shift):

DP-PIR/IRs ACE Operations Meetings Suspenses Admin

5. Administrative Information

Maintenance and Power Meals

10 APPENDIX 1 (Battle Update Brief Format) to ANNEX A (ACE Chief)

Security Details Etc

11 ANNEX B (Battle Captain) to ACE SOP

1. General.

Supervises ACE analysis, target nomination, collection management, technical control, and dissemination operations during daily operations. Ensures subordinate supervisors and analysts are constantly focused on the commander’s PIR. Assumes the duties of the ACE Chief as required.

a. Focus ACE on current priorities.

b. Conduct meetings with key personnel within the ACE as necessary to ensure synchronization.

c. Ensure continuous flow of intelligence focused IAW the commander’s priorities.

d. Ensure the ACE status board is updated as necessary. See Appendix 1 to this Annex for specifics.

e. Assists the ACE Chief in preparing and delivering briefings.

f. Provides continuous direction of mission requirements.

g. Ensures ACE workstations are monitoring and processing the correct information.

h. Ensures the ACE is updated with the most current PIR, HVTL, and HPTL.

i. Ensures the ACE Chief is kept abreast of the current situation.

3. Pre Operations

a. Ensure the ACE is set up to conduct daily operations IAW the SOP.

b. Ensure ASE and SSE are operational IAW their pre-operations tasks.

c. Ensure All Source and Single Source Chiefs, Collection Manager, and FAIO conduct pre-operations tasks.

4. Operations.

a. Coordinate with other G-2 elements (Plans, Operations, etc.) as well as higher and lower intelligence sections/staffs.

12 ANNEX B (Battle Captain) to ACE SOP

b. Ensure workstation operators are kept situationally aware.

c. Implement the degraded operations plan as necessary. See Annex _, Degraded Operations Plan.

d. Maintain awareness of the status of ACE operations, communications, equipment, etc.

e. Oversee the dissemination of combat information and intelligence to users.

f. Identify and track required reports (ensure EDC is disseminated per the distribution schedule).

g. Supervise the control and management of ACE internal operations.

(1) Supervise the development of the Intelligence Synchronization Matrix (ISM).

(2) Coordinate with G-3/S-3 to ensure the friendly situation and commander’s intent are incorporated into the synchronization effort, along with G-3/S-3 personnel.

h. Supervise the performance of SSE and ASE analysis.

i. Recommends to Collection Management updates to the PIRs and the collection plan as necessary.

j. Performs quality control on all products that leave the ACE.

5. POST OPERATIONS

a. Ensures all sections conduct PMCS on all systems.

b. Ensure reestablishment of garrison environment in support of operations.

13 APPENDIX 1 (Status Boards) to ANNEX _ (Battle Captain)

1. The Battle Captain is responsible for ensuring the following items are updated every two hours or as needed:

a. PIR by Phase: Ensure satisfied PIR are removed and assets are re- tasked to cover other PIR.

b. High Payoff Target List (HPTL): Produced by the FAIO and the targeting analysts, with ACE Chief or Battle Captain approval.

c. ISM: Produced by the CM and Asset Manager with ACE Chief or Battle Captain approval.

d. ACE status: Use Green, Amber, and Red to indicate status:

(1) AS Enclave. (2) SS Enclave. (3) RWS. (4) Communications (NIPR, SIPR, JWICS) (5) Other key automation.

e. Posted Products:

(1) EDC (2) INTSUM (3) Graphic INTSUM

14 APPENDIX 1 (Status Boards) to ANNEX _ (Battle Captain)

2. ACE Status Charts:

Equipment Status Problem ASE SSE RWS CCS TS II NIPR Product Latest Output SIPR EDC JWICS INTSUM GRINTSUM COP

15 ANNEX _ (Collection Management)

1. General.

Plans and synchronizes collection operations and communications architecture. Coordinates the intelligence collection effort with AS and Technical Control sections to fuse the effort in ASAS.

a. Responsible for developing, briefing and updating PIR, IR, the ISM and Collection Plan. Develops the initial NAIs for the R&S plan. Tracks all RIs and disseminates intelligence products while safeguarding Special Intelligence. Attends all Skunk Works and targeting briefings.

b. Responsible for products at mission analysis, OPLAN, and Skunk Works briefings as well as all targeting meetings. Briefs collection assets available across echelons and potential collection strategies during mission analysis. Briefs the Collection Plan as part of the OPLAN, and highlights changes in Collection Asset Status and PIR and goes over the collection focus for the next x number of hours at the Skunk Works briefing. Uses a variety of products in support of the targeting process at targeting meetings, e.g. IEW Synch Matrix, Collection Plan, etc. Articulates the acquisition capability of assets vs. HVTs, HPTs and BDA requirements. Focuses and synchronizes collection assets to support the targeting effort. Identifies positions of collection assets (if available) to allow plotting by the SS station. As targeting is a fluid process, the CM must constantly focus the collection effort to meet the needs of the changing battlefield. The CM and Asset Manager do not task; appropriate unit S3s does tasking.

c. Acts as the POC for all outgoing intelligence products. The CM must constantly be aware of the status of products to be disseminated and focus the effort in the ACE to get them out on time.

d. Maintains constant communication with the FAIO due to the fluid nature of the targeting process.

e. Constantly coordinates the intelligence collection effort with appropriate S3s so appropriate tasking and re-tasking of assets can be made, e.g. shifting UAV ROZs, SIGINT baselines and or flight times of QF.

f. Maintains awareness of the status of collection assets to maximize the synchronization effort and plan future missions. Coordinates with the BDEs and BNs who own the assets and establishes reporting procedures.

16 ANNEX _ (Field Artillery Intelligence Officer)

g. Acts as the central POC for intelligence coordination in the ACE.

(1) Ensures products produced by the AS are disseminated IAW with established guidelines.

(2) Ensures the other section chiefs and the Battle Captain have the latest PIR and IR.

(3) Ensures the AS and Technical Control have the proper NAIs loaded in the ASAS.

(4) Coordinates with the AS and SS to constantly update changing Threat Alarm Criteria in ASAS to answer the commander’s PIR.

(5) Coordinates with Army Aviation Command and Control (A2C2) to change ROZs and flight tracks for UAV, QF, Guardrail etc. During Prairie Warrior coordination will be made with the appropriate agency at Leavenworth.

3. Pre Operations.

a. Develop PIR and IR.

b. Develop ISM.

c. Develop Collection Plan.

d. Develop NAIs (work in conjunction with the FSE and FAIO).

e. Develop Division R&S Plan (an extension of the Collection Plan).

f. Conduct requirements management (If the requirement cannot be answered internally, it is passed to higher; RIs are logged and assigned a number).

4. Operations.

a. Update PIR and IR and the Asset Status Report every two hours in order to keep the collection effort focused.

b. Ensure ACE status boards are accurate.

1. General.

The FAIO is not a member of the ACE but works in close coordination with both the ACE and the Division’s Fire Support Element (FSE). He provides the ACE with a detailed understanding of the targeting process, attack system information requirements, and target acquisition system capabilities (Q-36 and Q- 37). He uses available ACE resources to rapidly identify and recommend attack of High Payoff Targets (HPTs), and nominates potential targets to the fire support cell. The FAIO is responsible for working with the ACE Collection Manager to develop a collection plan that supports targeting and BDA related PIR.

a. Participate with the ACE during the Intelligence Preparation of the Battlefield (IPB) process concentrating on enemy Fire Support and Air Defense systems.

b. Understand enemy OB, including artillery and air defense systems, how the enemy uses artillery in battle, and how to detect, attack, and defeat potential HVTs and HPTs.

(1) Disposition of Fire Support units

(2) Fire Support C2 systems and relationships

(3) Resupply operations and locations of supply points

(4) Enemy use of artillery for preps, counter fire, etc.

(5) Enemy target acquisition systems and employment

(6) Enemy observer positioning and composition of observer teams

(7) Enemy doctrinal movement and distances

c. Provide input to pre-hostility artillery IPB to develop the most accurate picture of enemy artillery.

d. Provide input for targeting meetings. Base recommendations on information from ASE regarding changes in the tactical situation and BDA on current HPTs.

e. Assist the FSE in the development of the TSS, HPTL, and AGM and disseminate within the ACE.

f. Coordinate with the CM to convert targeting time requirements into LTIOV for PIR and IR to collect against HPTs, and to assist the FSE with BDA analysis.

g. Nominate targets for immediate engagement with available fire support.

h. Assist the ACE in tracking HPTs and analyzing patterns using the ASAS.

i. Pass recommendations on Fire Support Coordination measures, updates on hostile artillery locations, and current intelligence read to the FSE.

j. Provide support to the deep attack. Provide intelligence on known enemy ADA and associated radars along deep attack flight routes and engagement areas (within four km) to the FSE during mission planning and directly to the FSCOORD during deep attacks.

k. Act as the targeting link in the ACE. Provide targets for support fire plans. Use the resources available in the ACE to rapidly identify and recommend attack of HPTs to the FSE.

l. Record and verify targets based on the following:

(1) Support HPTL and PIR

(2) Grid location

(3) DTG of information

(4) Unit ID and equipment type

(5) Activity

(6) Targetability (within range of friendly systems)

(7) Accuracy of reported location and conformance to TSS

n. Receive printed messages on HPTs from SS during degraded operations or to enhance timeliness.

o. Ensure friendly artillery units are displayed on OPS map and targeting workstation along with range fans for organic artillery.

3. Pre Operations.

a. Assist in the development and dissemination of the TSS, AGM, and HPTL.

b. Assist the targeting section in the development of alarm criteria.

4. Operations.

a. Target selection and attack:

(1) Visit the appropriate ASAS terminal operator as required for specific target types and analysis updates.

(2) Evaluate the targets IAW target selection criteria which include the TSS matrix, timeliness of reports, source (imagery is the preferred source), target size, HPTL, and commander’s guidance.

(3) Assist the G2 and DivArty S2 in the development of TSS for each q enemy system or target set. During development, consider:

(a) Target Location Error (TLE) (location accuracy required for each target on the HPTL, based on the capabilities of each friendly attack system)

(b) Size (based on OB and G2 analysis, the minimum size of target worth attacking)

(c) Posture (moving or stationary)

(d) Dwell time for acquisition (how old the information can be and still represent a viable target).

(4) Update, post, and disseminate HPTL, AGM, and TSS.

b. Intelligence Fusion.

(1) Develop targetable information from the various intelligence sources with the Targeting Section.

(2) Act as a focal point for targeting immediate HPTs within the ACE and provide the ACE with the AGM and TSS for execution of target attack.

c. Deep Operations.

(1) Provide input for use during targeting meetings. Targeting meetings focus on the deep operations in accordance with these time frames:

(a) 0-24 hours - execute attacks and provide refinement information.

(b) 24-48 hours - develop the plan for attack.

(c) 48-72 hours - nominate targets for attack, assist in COA development for targeting process.

(2) Ensure appropriate alarms are set in the ASAS database to enhance mission planning and to provide early warning for deep attack missions.

d. Information Processing.

(1) Send updates to the FSE using phones or faxes as the primary means of communication.

(2) Send the following information to the FSE:

(a) Current intelligence picture.

(b) FAIO analysis of the situation.

(c) Recommended changes to Fire Support Coordination Measures based on intelligence reports of artillery positions.

(d) Other updates requested by the S2.

(3) Receive the following:

(a) Current intelligence estimate from AS.

(b) RIs as needed from the FSE.

(c) Requests to track specific targets from the FSE.

(d) All target grids from the TPQ-37s from the FSE.

(e) BDA from the CM and FSE.

(f) Updates for HPTL, TSS, and AGM from the FSE and the G2.

(g) Friendly artillery unit locations from the FSE.

22 ANNEX _ (All Source Analysis Technician)

1. General.

The All Source Analysis Technician is the ACE’s subject matter expert on the enemy. He/she creates and distributes all necessary products on the enemy to the entire ACE to assist with analysis. Ensures the ASE is focused and understands the current enemy situation. Ensures all products are relevant and maintains a system to track the battle during degraded operations.

a. Prepare line and block charts with strengths and key weapon systems.

b. Prepare equipment charts.

c. Develop association tables connecting equipment to individual units.

d. Prepare and brief detailed IPB products and working aids for analysts as needed.

e. Verify appropriate correlation parameters, queries, and alarms.

f. Obtain appropriate national and below databases and manuals as needed.

g. Prepare a Graphic INTSUM with narrative every 4 hours, and INTREPs as needed.

h. Oversee production of All Source intelligence products (e.g. EDC’s, TIDAT’s, THALT’s, graphics) to the user.

i. Supervise AS intelligence fusion, target nomination, and database management within the ACE.

j. Ensure ASE maintains situation awareness.

k. Participate in the Tactical Decision Making Process.

l. Ensure Situation Development prepares a query every hour or as needed to update the situation map.

3. Pre-Operations.

a. Coordinate with SS analysts who will provide technical data to assist with preparing the line and block charts, equipment charts, and association tables.

23 APPENDIX _ (Situation Analyst) to ANNEX _ (All Source Enclave)

b. Ensure the ASE has:

(1) Input operational graphics.

(2) Input STARTEX/initial enemy unit locations.

(3) Input doctrinal templates.

(4) Properly set all correlation parameters.

(5) Input SIT alarms (based off PIR).

(6) Input TGT alarms (based off HPTL/AGM).

c. Prepare the situation map with the unit icons as identified in the OB.

4. Operations.

a. Brief IPB products as necessary as it pertains to the current and enemy situation.

b. Build the Graphic INTSUM and INTREP:

(1) Validate that the EDC criteria built by the Database Manager accurately portrays the ACE view of the battlefield and ensure transmission to RWS.

(2) Supervise and assist the RWS in building intelligence products.

c. Ensure the dissemination of the Graphic INTSUM every 4 hours, and INTREPs as needed.

d. Ensure the ASE is focused on the current situation and future activities of the enemy with respect to intelligence fusion, target nomination, and collection management.

e. Provide a focus during Tactical Decision Making Process briefs or quick huddles based on key reads of the enemy situation.

f. Participate in the Tactical Decision Making Process:

(1) Brief current enemy situation: maneuver regiment and above, ARTY and ADA battalions, Reconnaissance and Anti-Tank company/battery down to platoons.

(2) Provide predictive analysis and update enemy courses of action.

(3) Do not exceed 10 minutes.

g. Ensure AS prints out a query concerning battalion and above elements of maneuver, ARTY, and AT, and company elements of ADA and Recon every hour or as required.

h. Maintain and update a file and situation map with AS printouts as necessary. These items are the backup system during degraded operations.

25 ANNEX _ (All Source Enclave)

1. The All Source Enclave supports the ACE with all-source intelligence. The enclave develops and maintains the intelligence databases, identifies gaps in the intelligence collection effort, accomplishes situation and target development functions through Intelligence Preparation of the Battlefield (IPB). It maintains the situation map, displays and overlays, and produces Intelligence Summaries (INTSUMs), Read books, and Intelligence Reports (INTREPs) as required.. The ASE processes information collected from all available sources to include organic and subordinate collection assets, other agencies, services, and allied forces. The All Source Enclave provides the ACE with order of battle (OB) information to support the operations of the single source intelligence disciplines. The enclave is responsible for analysis and reporting of intelligence and combat information, which supports higher, internal or subordinate units’ EEI/PIR. The functional areas of the All Source enclave are:

a. Supervisor: The System Supervisor is responsible for the ASE functionality. Establishes enclave accounts for personnel operating the ASAS workstations. Responsible for updating inbound and outbound routing tables, creating RLAGS and YLAGS, verifying Plain Language Addresses (PLAs), and establishing parser requirements. Maintains the operational status of the enclave and communications for the ACE. Coordinates connectivity with the CCS and the RWS, trouble shoots system problems and holds Message Release Authority (MRA) for the ACE. The System Supervisor also monitors how information is distributed within the ASE and is responsible for the regular EDC traffic sent to clients. The System Supervisor will have four FIs assigned: SPV, FMR, ALL and SIT.

b. Situation Analyst: Works with the All Source Analysis Tech to maintain the current enemy situation. Attempts to answer commander’s PIR by using situation alarms. Nominates targets to the targeting cell. Maintains current friendly operational graphics. Queries the ASCDB as directed by the All Source Analysis Tech to answer specific Requests for Information (RIs) and maintain the common picture of the battlefield. Creates External Database Coordination messages (EDCs) as necessary and disseminates TACREPs to clients as required. Tracks deep, close and rear battle. Operates in the ASE. The Situation Development workstation will have two FIs assigned: FMR and SIT.

c. Targeting: Disseminates HPTL and Attack Guidance Matrix (AGM) to the analysts. Develops Target Selection Standards (TSS) and works with the Collection Manager to achieve them for each target. Establishes target alarms and processes targets. Liaison to the FSO, FSE and firing units. Plots and tracks targets on both the ASE and SSE. Focuses all analysts on the HPTL and works with them to nominate and track targets. SS will acquire targets and unless the data is targetable they will hand the target off to AS for further development. Briefs HPTL and AGM during the

Tactical Decision Making process or ACE huddles. Coordinates with the CM and Database Manager for Battle Damage Assessment (BDA), reflect BDA in the database, and re-nominate targets that need to be attacked again. The AS Targeting will have three FIs assigned: TGT, FMR and SIT.

d. Database Manager: Responsible for the information flow, database structure and message flow through the ASAS. Specific responsibilities include interactive message parsing, ASCDB file maintenance, establishing correlation parameters, interactive correlation, monitoring high interest criteria and text message processing. The Database Manager also maintains normalization tables and entity hierarchy tables. Operates in the ASE. The Database Manager will have three Functional Identities (FIs) assigned: ALL, FMR and SIT (see Annex A Glossary).

27 APPENDIX _ (System Supervisor) to ANNEX _ (All Source Enclave)

1. General.

a. The System Supervisor (SPV) manages or ‘supervises’ the smooth operation of the ASAS-All Source Enclave by ensuring all analysts have fully functional workstations, which can process intelligence in a timely manner. The System Supervisor also has the responsibility for the security of the enclave and the data, which it holds. Typically, the SPV coordinates for connectivity with the supporting communications devices, and other intel systems, troubleshoots problems, acts as shift POC for maintenance, and communications, and provides query and display support for staff planners.

b. System Supervisor functions are spread out over five different FI’s.

(1) System Supervisor (SPV) which deals primarily with system initialization and configuration.

(2) Security Audit Trail (SAT) to handle the security requirements for all machine processing of classified information.

(3) Message Release Authority (MRA) to release system and analyst generated message traffic.

(4) Functional Manager (FMR) ensures that ASAS is physically capable of processing inbound and outbound intelligence messages.

(5) Automated Data Processing Operations (ADP) which enables the operator to perform backups periodically and to restore the backups if an on-line system has been lost.

a. Initialize the system.

b. Establish enclave accounts.

c. Update inbound routing tables.

d. Update outbound routing tables.

e. Maintain the operational status of the enclave.

f. Maintain positive control over software and hardware functions.

g. Retain release authority for all outgoing messages.

h. Establish EDC measures.

i. Conduct a Security Audit Trail (SAT).

j. Terminates the system software.

3. Pre Operations.

a. Initialize the system.

b. Establish enclave analyst accounts for personnel operating the workstations.

c. Update/establish inbound routing tables in FMR (see Appendix 1 Inbound Routing Tables):

(1) Review requirement for parsable message types to parse automatically or interactively.

(2) Route INTSUMs and any other messages as directed by the NCOIC/OIC to the correct printer.

(3) Ensure that the existing Key Word Search (KWS), and Online Message Journal are purged of all old data.

(4) Perform Cold Start to purge queues and purge the Communications Message File.

d. Update/establish outbound routing tables in FMR (see Appendix 2 Outbound Routing Tables):

(1) Create RLAGS and YLAGS for THALTs, TIDATs and other messages/distributions as needed.

(2) Verify PLAs (exact matches) with those in the CSP.

(3) Establish new outbound routing tables.

e. Determine EDC criteria:

(1) Coordinate with Database Manager, All Source Analysis Technician, the Collection Manager and RWS for guidelines.

(2) Confirm entity code assignment. (3) Once parameters are established, conduct a query of the database (FMR) to ensure the initial EDC will adequately populate the RWS database.

(4) Standardize information in the EDC (see Appendix 3 External Database Coordination).

f. Inventory and identify all ASAS hardware being deployed (if applicable) and run a systems check prior to deployment.

g. Backup databases.

4. Operations.

a. Maintain positive communications status.

(1) Monitor “NOTICES” window for any deficiencies.

(2) Periodically check CMP status (in FMR).

b. Maintain the operational status of the enclave.

(1) Monitor Security Alarms. Watch SPV alarms queue and maintain a “zero” status.

(2) Monitor NOTICES windows. Take corrective action as indicated.

(3) Run daily Security Audit Trail operations.

(4) Perform daily ADP operations back up.

c. Perform EDC updates as required by the chain of command.

d. Perform MRA responsibility:

(1) Check all outgoing messages for format, proper PLAs, classification and content.

(2) Release all messages correctly formatted.

(3) Execute release priorities and coordinate with ACE Chief for guidelines on THALTs, TIDATs, EDCs, and freetext messages.

(4) Reject or edit all improperly formatted messages.

(5) Check MRA Released Message queue to make sure messages were acknowledged by the CSP. Any messages with a “no” next to them failed. Check CMP status, check with supporting communications device, and check notices to find out why the message was not released.

e. Prepare specific intelligence products as directed by the NCOIC/OIC.

f. Process RIs passed from the collection management section and prepare RRIs as required.

g. Help maintain manual SITMAP with information required by the NCOIC/OIC.

h. Run a security audit trail every 24 hours, archive all existing data to the SAT drive and delete the old SAT data from the system.

i. Backup databases as required.

5. Post Operations/Maintenance.

a. Purge all unnecessary data from system. Ensure that the existing CMF, OMJ, ASCDB, ASHDB, KWS, FOB, Target history file and queries are purged of all old data.

b. Do a Cold start.

c. Run a Security Audit Trail, archive all existing data to the SAT drive and delete the old SAT data from the system.

d. Inventory and identify all ASAS hardware.

e. Reestablish system and run a systems check upon return.

f. Perform all necessary PMCS and report any problems to supervisor.

1. General.

The SIT Analyst is responsible for the IPB function of the enclave through template and overlay development, situation development, and maintenance of the commander’s situation display. Inputs all friendly control measures and operational graphics into the ASE. Monitors the current enemy situation, recommends targets from the HPTL to the targeting station, and notifies the All Source Analysis Technician when PIR have been satisfied. The SIT Analyst is responsible for assisting the All Source Analysis Technician in updating the current enemy situation on the ASAS electronic battlefield map, the physical 1:50,000 map, and the 1:100,000 map. Tracks both the close fight and deep battle.

a. Analyze current situation and assist the All Source Analysis Technician in predictive analysis.

b. Answer the Commander’s PIRs through a combination of standard queries and situation alarms.

c. Create situation alarm criteria sets and graphic overlays.

d. Develop queries.

e. Report intelligence through Threat Alerts (THALTS), Graphic INTSUMs, or INTREPs, and Responses to Request for Information (RRI).

f. Maintain “paper” current situation map.

g. Recommend targets.

3. Pre Operations.

a. Review Annex B to the Operations Order, enemy COA overlays, and event template.

b. Create an AOI.

c. Create AOQs to cover locations of significance to operations.

d. Build Pre-Operation overlays:

(1) Friendly Graphic

(2) Event Template (3) Doctrinal templates

e. Build appropriate standard queries.

(1) Near Real Time Query (NRTQ) to represent SITMAP (2) Maneuver unit (MR/TK) (3) ADA (4) Artillery (5) Recon (6) Anti-tank (7) Area (8) MTI

f. Set alarms to support requirements from higher (DST, ISM, HPTL, ATGM, PIR, NAI, TAI, indicators, etc.).

g. Create message masks:

(1) Utilizing JAMH, create message masks for all messages to be transmitted by situation analyst.

(2) Make copies of message masks prior to transmission. (Once a message is transmitted, it is deleted and can no longer be used to build upon. DO NOT USE THE MASK TO TRANSMIT.)

h. Check inbound/outbound routing tables for SIT FI: Coordinate with system supervisor to ensure the inbound and outbound routing tables contain the appropriate data for current operations.

i. Check with database manager to ensure critical OB data is loaded and correlation is occurring accurately.

j. Send a copy of the SIT alarms to the TGT and ALL analysts via FI mail, and the SSE via hardcopy so they are aware of the “key reads” for situation development.

4. Operations.

a. Develop the enemy situation by querying and displaying requested ASCDB holdings on an electronic SITMAP overlay and print a graphic INTSUM every two hours or when requested. (Submit product to All Source Analysis Technician.)

b. Print query results for all standard queries every 30 minutes to assist in manual situation map updates.

c. Using established queries, confirm the enemy’s present COA and indicators of future operations.

d. Recommend threat entities to the Target Analyst for target nomination.

e. Identify intelligence gaps and inform the CM.

f. Generate THALTS to subordinate units based on PIR and changes to the situation.

g. Respond to Requests for Information (RI) as soon as possible. Provide response to the Collection Manager through the All Source Analysis Technician.

h. SIT Analyst will be prepared to brief the current situation at all times.

5. Miscellaneous.

a. SIT analysts will maintain a shift journal to supplement the data contained in the OMJ for significant events/actions/messages. All actions completed will be logged in journal and reference copies of messages will be retained in journal as needed.

b. Continuous coordination is required in the following areas:

(1). Obtain current and accurate HVTL from TGT or FAIO.

(2) Provide feedback to the Database Manager on the integrity of the ASCDB. Coordinate for development of ODEs based on templated locations per direction from the All Source Analysis Technician and the SSE.

(3) Coordinate with the SPV for EDCs updates in response to specific RIs.

(4) Obtain quick reference Order of Battle and tactics information from the All Source Analysis Technician.

(5) RI messages will be routed to SIT through the ICM.

a. Purge all unnecessary data from system.

b. Inventory and identify all ASAS hardware.

c. Reestablish system and run a systems check upon return.

d. Perform all necessary PMCS and report any problems to supervisor.

35 APPENDIX _ (Targeting Analyst) to ANNEX _ (All Source Enclave)

1. General. The Target (TGT) Analysis analyst is responsible for target development within the ASE and for providing the rapid turnaround of potential targets to the FAIO and the FSE. The FAIO and the All Source Analysis Technician supervise him. The High Payoff Target List is the principal document used by the TGT Analyst to determine timely and accurate targets. The Targeting Cell using the Commander’s Intent, the Attack Guidance Matrix, EEI, and PIRs to guide the selection process develops the HPTL.

a. Develop and set target alarm criteria from the AGM and HPTL (see TAB 1 Proposed High Payoff Target List Worksheet).

b. Develop, track, refine, and nominate targets.

c. Update and process targets as either Immediate, Developing, or Recommended. Include input from SS and RWS.

d. Generate Target Data (TIDAT) messages.

e. Assist the FAIO in BDA tracking.

3. Pre Operations.

a. Meet with members of the targeting team to wargame the plan and develop the High Value Target List.

b. Obtain copy of High Payoff Target List from FAIO or G2 Operations.

c. Using the OPLAN, analyst continues developing the HPTL.

d. Using the targeting priorities in conjunction with the previous two items, the analyst begins to establish an alarm criteria set.

e. Ensure that all target files have been purged of all non-applicable information following past exercises/operations.

f. Using the Target Analysis Defaults function, establish default settings.

(1) To provide for automatic target nomination and re-nomination, set nomination and re-nomination defaults to 5.00 (km).

(2) Coordinate with System Supervisor for addresses in order to set inbound/outbound routing indicators/PLAs.

Example PLA and RLAG:

FROM: CDR 52 ID ASE TO: RLAG TARGET

(3) Set purge time and target history file default to ensure that target files do not exceed capacity.

(4) Set automatic procedure defaults, within 15 minutes: auto display of immediate target; auto delete of suspected duplicates.

g. Using Target Alarm Criteria Development, establish a target alarm criteria set that alerts the target analyst to reported targets of interest.

(1) Use entity codes making them as specific as possible.

(2) Use HPTL as a guide.

(3) Focus on signature equipment and key unit types from the OB.

(4) Assign priority numbers to each element in the criteria set using the current high payoff target list.

(5) Activate the criteria set unless there is going to be updated data introduced into the system. If so, then wait until the operational phase to activate the set.

h. Coordinate with situation development for receipt of NAIs.

i. Pre-build standard queries by activity and signature equipment, as required.

j. Send HPTL to ALL and SIT analysts via FI mail, and the SSE via hardcopy or electronic message so that they are aware of target requirements and can forward specific targets as they are encountered.

k. Using the print screen option for system utilities, make a hard copy of the criteria set for use if the computer erases the memory.

4. Operations.

a. Process Targets.

(1) Analyze target information.

(2) Coordinate with FAIO to nominate valid targets (HPTL).

(3) Generate TIDAT message.

(4) Release TIDATs to MRA.

(5) Delete useless targets.

(6) Save needed information for target development.

(7) Create and run queries on possible HPTs.

(8) Review the “IN” message queue to find additional targets that have not been parsed into the system as database records. Extract these targets and create records using the Target Development function.

(9) Coordinate with FAIO to update Target Alarm Criteria Set as necessary.

b. Coordinate with CM and FAIO to achieve TSS on developing targets.

c. Receive recommended targets from SSE for future development.

d. Receive immediate targets from Situation Development for nomination process.

e. Assist the System Supervisor in releasing TIDATs from MRA to supporting communications device.

f. Assist the FAIO and ALO with BDA and TDA.

(1) Coordinate with the FAIO, ALO, and FSE to develop complete BDA and TDA plans.

(2) Re-nominate targets for re-strike if necessary.

(3) Recommend changes to the HPTL.

(4) Update alarms as needed.

(5) Review IN message queue for BDA

(6) Track and maintain BDA manually.

g. Adjust queries based upon standing requirements and specific target requirements. Create additional queries as required.

5. Post Operations/Maintenance:

a. Deactivate/delete the criteria set.

b. Delete the target history file.

c. Delete the target analysis file.

d. Delete the message queues.

e. Delete any old overlays, SITMAPs, etc. that can’t be used again.

f. Maintain queries and AOIs that are generic in nature and may have applicability during future operations.

g. Inventory and identify all ASAS hardware.

h. Reestablish system and run a systems check upon return.

i. Perform all necessary PMCS and report any problems to supervisor.

39 APPENDIX _ (Database Manager) to ANNEX _ (All Source Enclave)

1. General.

The primary goal of the Database Manager is to ensure the ASCDB is maintained with the most current intelligence available. Timeliness is ensured through rapid interactive message processing and configuring the ASAS system to perform automatic parsing. Accuracy is ensured by automatic and interactive correlation and nodal analysis. If parsing difficulties arise, ASCDB accuracy is eroded. The secondary goal of the Database Manager is to assist the Situation and Target Analysts, and the ACE Chief in answering the commander’s PIR, IR, and RI(s) from subordinate echelons. Thirdly, the Database Manager creates and maintains the EDC criteria set. The Situation Analyst, Target Analyst, and Intelligence Collection Manager are all dependent on an accurate and current ASCDB. In turn, the Database Manager depends upon input (identification of errors) from the other analysts/Functional Identities as they review and use the ASCDB. The Database Manager uses the ALL and FMR FIs.

Responsible for the information flow, database integrity and message flow through the ASE. Specific responsibilities include:

a. ASCDB file maintenance (culling) b. ASCDB queries c. Interactive message parsing d. Text Message Processing e. Normalization and Entity Code Synchronization f. Parser table updates g. Correlation h. Node analysis i. High Interest Criteria

3. Pre Operations.

a. Load external databases:

(1) Coordinate with the System Supervisor to load national data tapes. If initial data is not available on data tapes, it must be manually entered. Manual entry will take from three to five days, or longer, depending on the mission.

(2) Determine Area of Operations and Area of Interest (AOI). Build an Area of Query (AOQ).

(3) Build Query, in Reference Database Operations, with AOQ limits for Ground Order of Battle (OB), Electronic OB, and Air OB. Load each as required (creating ODEs) into the ASCDB.

b. Check, load, and modify Geographic Reference Tables as required, based on the area of concern. Geographic Reference Tables store declination data and allow proper conversion of reported LOB and location data.

c. Perform Entity Code Assignment and to update Normalization Tables and Entity Code Synchronization.

(1) Unit Normalization: Research enemy OB to identify unique designations. Determine unique unit designations by unit number (Arabic number designators require no modification), organization type, and echelon. If a new unit designator is identified, determine the appropriate entity code using the TDM-20. Proceed to update the database as follows:

(a) Create a unit in Entity Code Assignment.

(b) Make necessary changes in Unit Number, Organization and Echelon Normalization Tables, if required.

(c) Update Unit Alias Tables to ensure autoparsing and creation of ODEs.

(d) Update Parsing Tables.

(e) Update Entity Hierarchy Tables.

(2) Equipment Normalization: Research OB and Table of Organization and Equipment (TO&E) of enemy forces to determine unique equipment holdings. Consult the Reference Integrated Database (RIDB) to determine proper Equipment Entity Code.

(a) Create the equipment in entity code assignment.

(b) Make needed changes in Equipment and Unit Normalization Tables.

(c) Update Equipment and Unit Normalization Tables to ensure autoparsing and creation of ODEs.

(d) Update Parsing Tables.

(e) Update Entity Hierarchy Tables.

(f) Provide selected normalization table to other AS analysts.

d. Establish High Interest Criteria Alarms (APAF) using commander’s guidance and EEI.

e. Set up interactive criteria:

(1) Interactive Correlation Criteria

(2) Node Analysis/Inference Criteria

f. Pre-build standard queries:

(1) By area and weapon systems

(2) By area and enemy unit activity

g. Establish templates for Node Analysis.

h. Obtain support references:

(1) Technical Data Library containing radio and radar references

(2) Technical Data on any enemy unique equipment associated with the ASCDB

(3) Enemy OB charts with primary weapon systems and numbers

(4) Other ASAS operation references as needed.

4. Operations.

a. Conduct interactive message parsing.

(1) Determine error that prevented automatic parsing.

(2) Correct recurring errors by:

(a) Adding entity that caused “error” to the parser error table.

(b) Update parser tables.

(c) Review hierarchy tables and make required changes.

b. Conduct text message processing.

(1) Create ODE(s) from text message content.

(2) Process created ODE(s) to the ASCDB.

(3) Review text message for information pertinent to Targeting or Situation Development. Inform FA(s) as needed by voice, printer, or internal mail.

c. Perform Process Queue Processing and analysis of the following:

(1) High Interest: Inform SIT analyst of alarm. Evaluate report and determine enemy intent if possible.

(2) Input Evaluation: Review message to determine error, correct error if possible, and submit for further processing.

(3) Identification: Evaluate ODE to determine which required data set is vacant or improperly populated. Review messages in OMJ to determine if required data was reported. Correct ODE and submit for further processing.

(4) LOB Resolution: Select ODE to determine if LOB candidates exist. Evaluate candidates’ parametric data. Review messages in OMJ to determine if required data was reported. Correct ODE and submit for further processing.

(5) Interactive Correlation: Allows the ALL analyst to evaluate candidates, expand search areas, review producer reports and then determine if the ODE should be correlated with another ODE in the ASCDB. Correlation provides the SIT and TGT analysts with an accurate picture of the battlefield.

(6) Node Analysis: Allows the AS analyst to infer units from equipment reports and link equipment to the unit. Another application is the linking of reported units to equipment in its area. Linking units to units is also performed.

(7) FRENSIT Processing: Allows the processing of friendly unit SITREPs into the system, thereby allowing the analyst to evaluate the disposition of forces.

d. Perform Situation Development and ASCDB Maintenance.

(1) Set queries to support SIT and TGT efforts based on commander’s EEI, IR and the current enemy and friendly situation.

(2) Evaluate query results to ensure the ASCDB is accurate. Perform correlation and nodal analysis to resolve ASCDB anomalies.

(3) Identify intelligence gaps and request CM&D initiate procedures to fill them.

a. Purge all unnecessary data from system.

b. Archive data from each exercise or mission if space is available.

c. Inventory and identify all ASAS hardware.

d. Perform all necessary PMCS and report any problems to supervisor.

44 ANNEX _ (Single Source Enclave)

1. General.

The Single Source Enclave (SSE) is a series of Sun Sparc computers that serve as intelligence discipline specific "pre-processors" for the ACE. Single Source Workstations are windows based and allow the operator to point and click onto menus and applications of interest. Configurations are based on mission requirements and the number of workstations available. However, regardless of the number of workstations, the functions of the Senior Analyst, System Administrator, File Server and Communications Server must be performed whether this is done at a stand-alone terminal or in conjunction with another function or task. There are typically two field configurations, two workstations or six workstations.

(1) Two workstation configuration: (a) Senior Analyst/System Administrator/File Server/ELINT (b) Communications Server/COMINT

(2) Six workstation configuration: (a) Communications Server (b) File Server/System Administrator (c) Senior Analyst (d) COMINT (e) ELINT (f) IMINT

a. The Single Source Enclave will be task/functionally organized based on METT-T. This can mean each workstation being responsible for tracking, analyzing, and then reporting on a different intelligence discipline, or each workstation can be responsible for a portion of the battlefield (i.e. deep or current operations).

b. Communications. Reports from the available communications device passes to the SSE via its communications server and is parsed by the file server. The message is kept in the SS database. Every station has access to all working databases. The communications server is the only terminal that physically receives and transmits all messages.

c. Software. The software on the SSE is designed to give the operator a wide variety of analytic tools. Each workstation is capable of plotting and manipulating all loaded maps, creating overlays, manipulating databases, setting alarms, and generating messages. The software also allows certain file and user utilities as well as Systems Administration utilities. The workstations enable the

45 ANNEX _ (Single Source Enclave)

operator to develop a view of the battlefield as seen by the specific intelligence discipline. d. Alarms. Each workstation develops its own alarms tied to PIR, DPs, HPTL and SIRs; the analyst will need to better analyze the situation. When tripped, an alarm notice window and a system audible chirp notify the analyst.

e. Reporting time-sensitive intelligence information is reported using the appropriate reporting vehicle, in accordance with the United States SIGINT Intelligence Directives (USSID). In the event an update is needed prior to the scheduled summaries, an INTREP will be drafted and sent.

f. Information Requests. The SSE supports the issuance of RIs and Responses to Requested Information (RRIs) in a timely manner depending on priority. Priority is determined by the Battle Captain and is posted and announced when this is modified due to battle progressions.

g. ASE Support. The SSE provides updated SIGINT and IMINT to the ASE via Tactical Reports (TACREPs) as required. SSE provides immediate intelligence to the ASE for targeting purposes and to support the fusion process.

46 APPENDIX _ (Communication Intelligence) to ANNEX _ (Single Source Enclave)

1. General.

The COMINT workstation is designed to develop a view of the battlefield from the COMINT intelligence discipline. The COMINT analyst will further develop this view by conducting quality control on the displayed information, querying the database to develop a more accurate picture and conducting analysis based on this refined view. This view can be fused with intelligence from other disciplines and disseminated as necessary.

a. Conduct analysis of COMINT specific message traffic received from the Communications Device. Analysis is conducted to answer PIR and/or as directed by the Single Source Chief.

b. Provide targeting data on HPT to the targeting officer as it is developed.

c. Transmit TACREPs to AS, RWS and other ACEs as required.

d. Identify gaps in the COMINT database and inform the Single Source Chief.

e. Compare ASE/SSE battlefield pictures to identify gaps in coverage (plot EDC)

3. Pre Operations.

a. Power up the system.

b. Log on.

c. Set PLAs and Routing Indicators.

d. Set Address To and Address From databases.

e. Establish communications. Receive and transmit test messages as necessary.

g. Review and Print Cross Reference Index for Enemy Order of Battle (EOB).

(1) Report A: Frequency, Call Sign, Unit, and Parent Unit.

(2) Report B: Call Sign, Frequency, Unit, and Parent Unit.

(3) Report C: Unit, Parent Unit, Frequency, and Call Sign.

(4) Report D: Parent Unit, Unit, Frequency, Call Sign.

h. Establish Event Alarms to support PIR, HPTs, and Single Source Chief.

i. Construct base net diagram working notes.

j. Set map to area of operations and load/create control measures overlay.

k. There are three primary techniques to plot entities to create a more coherent picture of the enemy’s disposition on the battlefield.

(1) Plot units by color. For example, all subordinate units of a specific division are green.

(2) Plot date-time group periods by color. For example, everything six hours or older is gray.

(3) Plot threat BOS by color. Use the same color scheme as the ASE.

(a) Infantry: Red

(b) Armor: Yellow

(c) Artillery: Gray

(d) Air Defense Artillery: Blue

(e) Anti-Tank: Black

(f) Engineer: Orange

(g) Reconnaissance: Green

(h) Aviation: Black.

l. Set common features for the map: As a minimum, set major roads, major rivers, terrain, and elevation. m. Establish Standard Queries List (SQL) by criteria.

4. Operations.

a. Update communications routers as necessary.

b. Ensure Communications/Queue Status is on screen at all times.

c. Parse all COMINT messages and ensures other stations are aware of non-parsed messages relevant to their database.

d. Update Cross Reference Index EOB as necessary.

e. Review event alarms as necessary.

f. Review and update net diagrams as necessary.

g. Review SQLs by criteria as necessary.

h. Plot entities from KL database.

i. Fuse ELINT or IMINT data with COMINT to confirm unit locations or identity.

j. Generate TACREPs to populate AS database.

k. Inform the ASE Situation Analyst of critical pieces of information.

l. Purge map overlay of unneeded entities as necessary.

m. Compact database at the end of the duty day or at shift change.

49 APPENDIX _ (Electronic Intelligence) to ANNEX _ (Single Source Enclave)

1. General.

The ELINT workstation is designed to develop a view of the battlefield from the ELINT intelligence discipline. The ELINT analyst will further develop this view by conducting quality control on the displayed information, querying the database to develop a more accurate picture and conducting analysis based on this refined view. This view can be fused with intelligence from other disciplines and disseminated as necessary.

a. Conduct analysis of ELINT specific message traffic received from the Communications Device. Conduct analysis to answer PIR and provide fusion with COMINT.

b. Provide targeting data on HPT to the targeting officer as it is developed.

c. Transmit TACREPs to AS and other ACEs as required. Pass data verbally to the targeting officer and follow up with a TACREP.

d. Identify gaps in the ELINT database and coordinate with the CM for collection.

e. Develop all friendly control measures for the SS enclave.

3. Pre Operations.

a. Power up the system.

b. Log on.

c. Load AOI map to scale.

d. Develop friendly control measures using black lines including boundaries, phase lines and NAIs.

e. Save the overlay by name and category (SYSAD NAI).

f. Set common labels for the ELINT database.

g. Establish event alarms to support PIR, HPTs, and the OB Tech by phase.

I. Ensure communications have been established by the COMINT workstation.

50 APPENDIX _ (Electronic Intelligence) to ANNEX _ (Single Source Enclave)

j. Establish Standard Queries List (SQL) by criteria.

4. Operations.

a. Plot entities from ELINT database (use specific color for unanalyzed entities).

b. Focus efforts on entities within or near NAIs, Artillery units and HPTs.

c. Change analyzed unit entity symbols and color.

d. Responsible for parsing all non-parsed ELINT messages.

e. Review Event Alarms as necessary.

f. Review SQLs by criteria as necessary.

i. Fuse COMINT entities with ELINT to confirm unit locations.

j. Generate TACREPs to populate AS database.

k. Inform the Situation Developer of critical pieces of information.

l. Purge the map overlay of unneeded entities as necessary.

m. Compact the database at the end of the duty day or at shift change.

n. Compare ELINT picture to ASE picture (EDC) to identify gaps in coverage.

51 ANNEX _ (Remote Workstation)

1. General.

a. The Remote Workstation will be used for database exchanges, analysis, and ASAS interface. Several different software programs and applications will be either directly entered or “air gapped” to the Remote Workstation. The Remote Workstation provides ASAS linkage between major subordinate units and higher ACEs. It allows these units to receive and send information and intelligence. The Remote Workstation’s biggest limitation is that it can receive and send information only up to secret collateral. It can be accredited for SCI but it would have to be housed in a SCIF or TSCIF. If the RWS is configured as SCI, it can be LANed to the AS/SS allowing for the use of FTP between the systems.

b. The Remote Workstation combines almost all the capabilities of the old CWS, SS, and Warrior terminals. The Remote Workstation can maintain multiple databases, conduct message parsing, sending E-mail and develop and implement alarms and event criteria. It can also create and display multi-media presentations using text, images, snapshots, and animation. It can also receive, parse, display, manipulate, and transmit NITF imagery (it cannot take an NITF image and draw on it). The Remote Workstation is not capable of conducting AS tasks such as message correlation and normalization. The Remote Workstation runs windows based software, which gives the operator the ability to rapidly point and click onto an application of interest. The Remote Workstation terminal is based on the SUN SPARC 20 computer which has a 4.2 gigabyte hard drive and 256 megabytes of RAM.

c. Remote Workstations receive the ACE’s view of the battlefield through the EDC. The EDC can be modified by the Remote Workstation to tailor the information to the supported unit’s mission. Additionally, the Remote Workstation can query the information within in the EDC. The EDC can provide a complete ACE SITMAP (sanitized of SCI data) to the Remote Workstation. All EDCs must pass through the AS’s MRA before being sent to the Remote Workstation. There are numerous EDC formats (initial, update, resynch, etc.). The EDC provides a common picture of the battlefield to major subordinate units of the division. It also enables analysts at both the ACE and the Remote Workstation to quickly identify and deconflict differences of view.

d. Remote Workstations can also receive information is these formats: USMTF, SALUTE, and KL messages; NITF, GIF, TIFF, and PBM images; and MIIDS/IDB Transaction Files. Correct format will increase the speed the information is processed at the SS, AS, and Remote Workstation. Improperly formatted messages are rejected by the parser and must be fixed by the operator before the system accepts the input.

e. The operator can overcome the main challenges associated with the Remote Workstation by:

(1) Developing a communications architecture, which allows rapid dissemination of the current battlefield picture and other intelligence to all subordinate units and confirmation of receipt.

(2) Developing briefing techniques the Remote Workstation can support. Standard queries can be developed to automatically update and quickly bring up situation maps used for recurring briefings.

2. Pre Operations.

a. Create graphic overlays that include:

(1) Boundaries (2) FLOT (3) Objectives (4) DAGs and RAGs (5) Obstacles (6) AAs

b. Create Queries.

c. Input RIs and PLAs.

d. Set alerts for EDCs and TIDATs.

e. Create and send EDC requirements.

f. Generate symbols as required.

3. Operations.

a. Receive EDCs from AS. (Care should be taken to balance the need for timeliness with the time required to review and release collateral EDCs from the AS.)

b. Build graphic INTSUMs from EDCs.

c. Add and modify records in tables.

d. Send friendly DB.

e. Forward EDC tables to other RWS, which do not have GGP comms via TPN and/or dial-up.

f. Receive and forward to the AS/SS SALUTEs and other messages received from subordinates via TPN, Dial-up, email, the web browser, etc.

54 ANNEX _ (Communications Control Set)

1. General.

a. The Communications Control Set (CCS), AN/TYQ-40 provides a communications front end interfacing the ASAS and the ACE with the Area Communications System--principally dial up over Mobile Subscriber Equipment (MSE) or direct wire line connection to the AN/TYC-39 message switch. The CCS receives and relays information from adjacent, superior, and subordinate units to and from the intelligence processing enclaves. At Division level, it also connects multiple sensors and collectors directly to the ASAS workstations.

b. The (V)2 variant is employed at division level and, when connected with two AN/TYQ-36 Data Processing Sets (DPS), provides up to twelve external serial communications channels supporting a variety of communications protocols including AUTODIN Mode I, Generic Gateway (DDCMP/FDMP), Net Radio Protocol (NRP), and a unique AN/PSC-2 Digital Communications Terminal (DCT) protocol. Data rates supported range from 1200 to 16,000 BPS according to the protocol and equipment string employed. The heart of the CCS is the Common User Baseline Intelligence Community (CUBIC) Communication Support Processor (CSP) running software version 3.4. This allows the CCS to function as an R/Y store and forward switch. It is accredited to handle both Special Compartmented Information (SCI) and Collateral traffic; the classification allowed is determined on a port-by-port basis during system setup and configuration. The (V)2 is also equipped with two AN/VRC 92A SINCGARS VHF radio relay sets as well as an ARC-164 UHF line of sight radio for sensor and ground-to-air communications.

c. The (V)3 variant is employed at corps level and has no radio capability. It does have twelve serial communications channels with associated cryptographic and modem/signaling equipment. Neither the (V)2 nor the (V)3 can support network (LAN or WAN) at this time.

a. Primarily responsible for routing of all traffic into and out of the ACE.

b. Responsible for correlating message errors during processing.

c. Establish RIs and PLAs between all ACE enclaves and RWSs.

d. Ensure link between TACSIM (during simulations) is operational and up at all times. Establish LNO system between divisions.

e. Ensure communications is established between all ACE enclaves, RWS, and any adjunct Intelligence systems.

55 ANNEX _ (Communications Control Set)

3. Pre Operations.

a. Ensure all communications links between ACE and RWS enclaves is up and functional.

b. Verify RI and PLAs between ACE (AS/SS/RWS) enclaves are in concert with CCS settings.

c. Ensure queues are clear and functional for any new mission.

4. Operations.

a. Maintain message routing, and communication links with all enclaves.

b. Correct message errors and re-send messages with minimal delay.

56 APPENDIX _ (Communications Support Processor) to ANNEX _ (Communications Control Set)

1. General.

a. The Communications Support Processor (CSP), provides a flexible and scaleable ASAS communications interface capability. The CSP is hosted on the CHS-2(V1) or (V2) platform and is COE compliant. The CSP interfaces with MSE, AUTODIN, Trojan SPIRIT, TYC-39, and other DoD command and control systems. Communications connectivity from the CSP to the ASAS workstations is achieved via the Communications Network Server (CNS) 6200.

b. Like the CCS and the CAMPS, the CSP receives and relays information from adjacent, superior, and subordinate units to and from the intelligence processing enclaves.

a. Primarily responsible for routing of all traffic into and out of the ACE.

b. Responsible for correlating message errors during processing.

c. Establish RIs and PLAs between all ACE enclaves and RWSs.

d. Ensure link between TACSIM (during simulations) is operational and up at all times. Establish LNO system between divisions.

e. Ensure communications is established between all ACE enclaves, RWS, and any adjunct Intelligence systems.

3. Pre Operations.

a. Ensure all communications links between ACE and RWS enclaves is up and functional.

b. Verify RI and PLAs between ACE (AS/SS/RWS) enclaves are in concert with CSP settings.

c. Ensure queues are clear and functional for any new mission.

4. Operations.

a. Maintain message routing, and communication links with all enclaves.

b. Correct message errors and re-send messages with minimal delay.