Attachment 0013h - D-IBCS-0472_Adv_IDD_redacted.pdf

UNCLASSIFIED

Copyright 2020 Northrop Grumman Systems Corporation.

UNCLASSIFIED

IBCS.DM.025.25 (Jan20)

Integrated Air and Missile Defense (IAMD)

Battle Command System (IBCS)

Operator/Maintainer Course

Advanced Integrated Defense Design (IDD)

DOCUMENT NUMBER: RELEASE: DOCUMENT DATE:

D-IBCS-0472 001 06 May 2020

CDRL NUMBER: CONTRACT: CONTRACT NUMBER:

N/A IBCS W31P4Q-08-C-0418

EXPORT CONTROL WARNING DISTRIBUTION STATEMENT D

WARNING -This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751,

et. seq.) or the Export Administration Act of 1979, as amended, Title

50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

Distribution authorized to DoD and U.S. DoD contractors only;

Administrative and operational Use; 26 July 2017. Other requests for this document shall be referred to the IAMD Project Office, Bldg.

5250 Martin Road, Redstone Arsenal, AL 35898.

DISCLAIMER STATEMENT AND DISTRIBUTION

RESTRICTION

The views, opinions, and/or findings contained in this report are those of the author(s) and should not be construed as an official Department of Defense position, policy, or decision, unless so designated by other official documentation.

This document contains information EXEMPT FROM

MANDATORY DISCLOSURE under the FOIA. Exemption 3 (e) apply. (Reference: Army Regulation 25-55)

This material is based upon work supported by the U.S. Army Aviation and Missile Command under Contract No. W31P4Q-08-C-0418.

Prepared for: Prepared by:

Integrated Air and Missile Defense (IAMD)

Battle Command System (IBCS)

Northrop Grumman Defense Systems Sector

Combat Systems and Mission Readiness (CSMR)

Division

213 Wynn Drive

Huntsville, AL 35805-1928

CAGE Code 9F909

W31P4Q-20-R-0015 ATTACHMENT 0013h

D-IBCS-0472, Rel. 001

06 May 2020 iii

Northrop Grumman Defense Systems

Combat Systems and Mission Readiness (CSMR) Division

IAMD Battle Command System (IBCS)

213 Wynn Drive

Huntsville, Alabama 35805-1928

CHANGE RECORD

Release

Number Date Authority

Pages

Affected Remarks

001 06 May 2020 SOW 3.2.10.9.1 All Initial Release, DCR-6594, PCCB #587

D-IBCS-0472, Rel. 001

06 May 2020 iv

This page intentionally blank.

UNCLASSIFIED D-IBCS-0472, Rel. 001

Advanced Integrated Defense Design (IDD) 06 May 2020

Integrated Air and Missile Defense (IAMD)

Battle Command System (IBCS)

Operator/Maintainer Course

Student Guide

Advanced Integrated Defense Design (IDD)

UNCLASSIFIED

TABLE OF CONTENTS

Lesson 1: Advanced Integrated Defense Design (IDD) Course Introduction

1. Purpose

2. Scope

3. Document Conventions

4. Mouse and Keyboard

5. IBCS Reference Documents

6. Safety Information

Lesson 2: Perform Advanced Integrated Defense Design (IDD) Procedures

ELO A: Perform Area and Asset Management

1. Describe Advanced Area Manager Tasks

2. Describe Advanced Asset Manager Tasks

ELO B: Perform Task Force Configuration

1. Describe Task Force Configuration

2. Configure the Authority Settings

3. Configure the TF Configuration

4. Configure the HW ID Matrix

5. Configure the Rules of Engagement

6. Configure CID and IFF Controls

7. Configure Pre-planned Responses

ELO C: Perform Defense Plan Optimization

1. Describe the IDD Evaluator/Optimizer (IEO)

2. Optimize a Defense Plan

3. Evaluate a Defense Plan

Advanced IDD Practical Exercise

Practical Exercise (PE) Overview

PE 01: Perform Integrated Defense Design (IDD) Procedures

Appendix A: Acronyms and Abbreviations ............................................................ A-1

UNCLASSIFIED

LIST OF FIGURES

Figure 2-2. ARM Classification and Auto NCTR Settings

Figure 2-1. Evaluating vs. Optimizing a Defense Plan

LIST OF TABLES

Table 1-1. Mouse Pointer Icons

Table 2-1. Planning Task Force Manager Tabs – User Actions

Table 2-2. CID Configuration Default Settings

Lesson 1: Advanced Integrated Defense Design (IDD) Course Introduction 06 May 2020

UNCLASSIFIED

LESSON 1: ADVANCED INTEGRATED DEFENSE DESIGN (IDD)

COURSE INTRODUCTION

Terminal Learning Objective

Action: Review the scope and framework of the Advanced Integrated Defense Design (IDD) course.

Conditions: Given the IBCS, SUM, and IBCS Advanced IDD Student Guide.

Standards: Review advanced course learning objectives, document conventions, system keyboard standards, and supporting documentation locations in the CWMI software.

1. Purpose

a. The Advanced Integrated Defense Design (IDD) course instructs personnel in the operation of advanced Integrated Defense Design (IDD) procedures in the IBCS Common Warfighter Machine Interface (CWMI) software.

b. Instruction focuses on specific, task-based standards and advanced learning objectives to successfully navigate and operate the CWMI.

2. Scope

a. The Advanced IDD course instructs students on a deeper understanding of the CWMI capabilities in the following areas:

(1) Advanced Area Manager tasks.

(2) Advanced Asset Manager tasks.

(3) Advanced Task Force configuration.

(4) IDD Evaluator/Optimizer (IEO) description and capability.

(5) Advanced Defense Plan optimization.

(6) Advanced Defense Plan evaluation.

b. Practical exercises provide hands-on experience and reinforce learned tasks.

3. Document Conventions

a. Courier Font: Text an Operator types into a data entry field.

Example: At the prompt, type: adduser

b. Brackets [ ]: Text within brackets is an example or explanation of data required.

Example: At the prompt, type: adduser [username]

c. Angle brackets < >: Indicates keys pressed on a keyboard or buttons clicked on a software display.

Example: Press <Enter> (key). Select <Add> (button).

d. Right angle bracket >: Indicates submenu selections.

Example: At the XYZ window menu bar, select File > New > Folder.

e. <Enter> is pressed after entering text or issuing a command in terminal windows.

UNCLASSIFIED

4. Mouse and Keyboard

a. The CWMI pointing device is a standard two- or three-button mouse.

b. The CWMI uses a standard QWERTY keyboard and provides hot-key alternatives to the mouse.

(1) Reorient the map: press <R>

(2) Zoom in: press <Ctrl> + <Up Arrow>

(3) Zoom out: press <Ctrl> + <Down Arrow>

(4) Rotate clockwise: press <Shift> + <Right Arrow>

(5) Rotate counter-clockwise: press <Shift> + <Left Arrow>

(6) Tilt view up: press <Shift> + <Up Arrow>

(7) Tilt view down: press <Shift> + <Down Arrow>

(8) Pan the map: press Up, Down, Left, or Right Arrow keys

c. Mouse Pointer icons help operators interact with the CWMI user-interface.

Table 1-1. Mouse Pointer Icons

Icon Indicated Action

Single-click

Double-click

Right-click

Mouse Hover/ Mouseover

Drag

5. IBCS Reference Documents

a. Refer to the IBCS Software User Manual (SUM) for complete guidance on system functions and capabilities.

(1) The SUM is a portable document format (PDF) file accessed through the Help tab on the CWMI Ribbon bar.

(2) Request a copy of the SUM from the IAMD Project Office.

b. Refer to the Interactive Electronic Technical Manual (IETM): DRAFT TM-11-5895- 567-13&P.

(1) The IETM is accessible from a Windows-based IBCS Collaborative Environment (ICE) workstation with the IADS4 application and the IETM software installed.

UNCLASSIFIED

(2) Open only four Virtual Windows simultaneously in an ICE.

6. Safety Information

a. Students must be familiar with the safety briefing provided in Module A, IBCS Operator/Maintainer Course Overview (Lesson A02).

b. Ask the instructor about safety concerns.

c. Refer to DRAFT TM 11-5895-567-13&P (IETM) for complete safety information.

Lesson 2: Perform Advanced Integrated Defense Design (IDD) Procedures 06 May 2020

UNCLASSIFIED

LESSON 2: PERFORM ADVANCED INTEGRATED DEFENSE DESIGN

(IDD) PROCEDURES

Terminal Learning Objective

Action: Perform advanced Integrated Defense Design (IDD) tasks.

Conditions: Given the IBCS, SUM, and IBCS Advanced IDD Student Guide.

Standards: Review area and asset management tasks, configure the task force; and optimize and evaluate a defense plan.

ELO A: PERFORM AREA AND ASSET MANAGEMENT

Action: Perform advanced area and asset management tasks.

Conditions: Given the IBCS, SUM, and IBCS Advanced IDD Student Guide.

Standards: Describe advanced Area Manager and Asset Manager tasks.

1. Describe Advanced Area Manager Tasks

a. Area of Interest (AOI)

(1) Only one AOI can be created in the defense plan.

(a) The AOI defines the area/volume used for the Rule of Engagement (ROE) view within Task Force Configuration.

(b) AIR category tracks will not be eligible for engagement planning unless within this volume.

(2) A user can perform an “Add Track to Target Dataset” via the Track Table to add a track manually (even if outside the AOI), unless the identity of the track is Friend or Assumed Friend.

(3) SPACE category tracks are not restricted by this volume.

(4) Ideally the AOI should encompass an area representative of the capability of the weapons available.

(5) AOI is consumed and sent out from IBCS as reference point for Link 16 as J3.0 Defended Area. The reference is visualized on the CWMI map via a yellow box with a yellow “X” inside.

b. Task Force Area

(1) Only one Task Force Area can be created in the defense plan.

(a) Create the Task Force Area to encompass the area/region where blue force entities can be emplaced.

(b) The area should not extend over large bodies of water or enemy territory.

(2) When utilizing the Resource Palette, entities added are randomly placed inside the Task Force Area.

(3) When the defense plan is optimized, the Task Force Area and exclusion zones define the regions where placement is allowed (Task Force Area)/disallowed (Exclusion Zones).

UNCLASSIFIED

(4) Other manager views, such as Sensor Manager, require the Task Force Area be generated prior to use/adding an entity.

c. Exclusion Zones

(1) Multiple exclusion zones can be entered.

(2) Exclusion Zones are used by the Optimization process for laydown planning purposes. The zones indicate areas NOT to place resources, and are not restricted from placement outside the Task Force Area.

(3) Exclusion Zones are NOT utilized by Mission Control for engagement planning purposes.

d. Use the Map selection, Map Overlays, and Area to hide the AOI, Task Force Area, or Exclusion Zones from the map by toggling OFF as a group or as individual items.

NOTE: The nomenclature listed in the Map Overlays for Area of Interest for the J3.0 Defended Area is altered to DEFENDED_AREA. The defense plan entries are listed as UNDEFINED and include AO for Task Force Area and AOI for Area of Interest.

2. Describe Advanced Asset Manager Tasks

a. Pre-Planned Responses (PPR) are specified by a defended asset.

b. From Settings, Type is selectable, however this is not used operationally by Mission Control (MC) software.

c. Defended Assets are displayed on the CWMI Map.

d. Defended Assets are sent via Link 16 as J3.0s Defended Assets. The regions are displayed on the CWMI map with a yellow box with a yellow “X” inside. Link 16 transmission accounts for the conversion of polygons or circles to a point area.

(1) A Priority setting is sent via Link 16 that is based on the Defended Asset List (DAL). Priority cannot exceed 7.

(2) Priority is based upon the DAL, set from 1 to 7 directly, and then truncated to 7 for any DAL larger than 7.

e. Patriot only accepts x number of defended assets, and only that number is sent via the DefendedAssetInstructions message—the remaining are not transmitted. IDD allows for a greater number of assets—for TailoredSearchInstructions, IDD adheres to the limit of x TBM assets and y ABT assets.

f. Patriot accepts x number of polygon points—IDD converts to the Patriot number.

g. Mission Control software treats a point asset with a default (small in size) radius, and is still visualized as a point on the CWMI map.

h. Combat ID utilizes defended assets. If the Ground Impact Point (GIP) is in close proximity to an asset, there is evidence of hostile added—this only impacts/affects recommended identity.

UNCLASSIFIED

i. Mission Control utilizes defended assets as it impacts the following:

(1) Specific PPR settings

(a) The “Assets” column in the Engagement Queue signifies which asset is targeted

(b) The Residual Pre-Planned Response is used IF the target displays with a dash (-) for the Asset in the Engagement Queue—meaning the target is not deemed to be intersecting/impacting any defended asset.

(2) Threat Assessment (TA) shown to users (in the Engagement Queue) as:

(a) CON – Concerning

(b) THR – Threatening

(c) ATT – Attacking

(d) QKR – Quick Reaction Time

(3) Threat Priority regarding resources takes into account various factors to include DAL, and is displayed in the Engagement Queue in the Priority column.

(4) Protective Keepout, specified in PPR, is a per Asset and per Threat database entry:

(a) Keepout Range is from a defended asset boundary: If the asset size is 5,000 meters (m) and the keepout range is 5,000 m, the keepout range would be 10,000 m in total.

(b) Keepout Altitude is above the center of the asset and assumes relative to 0 m AGL.

NOTE: Keepout Altitude entries are allowed for specific attributes to include anti-radiation missiles (ARM_x).

j. DAL is used to set the priority for the Tailored Search defended assets sent in mission planning messages (aka buffer transfer) for a Patriot radar.

(1) The Tailored Search Asset Threat Category (ATC) cannot be greater than 8.

(2) ATC is based on the DAL, set from 1 to 8 directly, and then truncated to 8 for any DAL larger than 8.

k. For Patriot:

(1) Per Technical Manual (TM) 9-1430-1600-10-1, Patriot ABT assets may be point assets or radial assets (no polygons).

(2) Per TM 9-1430-1600-10-1 manual, Patriot TBM assets may be point assets, radial assets, or polygon assets.

(3) Whether or not a defended asset is an ABT or TBM asset within IDD is not distinguished, except for the Threats area populated from the Threat Area Origins (TAO) manager with Ballistic Missile Operating Areas (BMOA), Cruise Missile Operating Areas (CMOA), Airstrips, and Unknown.

UNCLASSIFIED

ELO B: PERFORM TASK FORCE CONFIGURATION

Action: Configure the Task Force.

Conditions: Given the IBCS, SUM, and IBCS Advanced IDD Student Guide.

Standards: Configure the following: Authority Settings, TF Configuration, HW ID Matrix, Rules of Engagement, CID and IFF Controls, and Pre-planned Responses

1. Describe Task Force Configuration

Use the Planning Task Force Manager window to set the following parameters: ID Authority, Engagement Authority, Task Force (TF) Configuration, Hardware (HW) IDs, Rules of Engagement (ROE), Combat Identification (CID) Rules, IFF Controls, and Pre-planned Responses. Table 2-1 lists user actions available in each tab.

NOTE: The arrow icon on the top-right corner of the window is a disabled placeholder for future software capabilities.

Table 2-1. Planning Task Force Manager Tabs – User Actions

Planning Task Force Manager Tab

User Actions

Authority Select ID and engagement authority, external higher echelon units (HEU) and subordinate hierarchies, reset to default layouts, and edit lists.

Task Force (TF) Configuration

Select support control, mode control, engagement-tasking control, and initialization control.

HW ID Matrix Select units, sensors, weapons, and relays.

R.O.E. Determine engagement planning and processing eligibility, volume selection, identity selection, and create existing plan area.

CID Config/IFF Cntrl Control rules used to identify tracks, determine mode priority, and reaction to IFF response.

Pre-planned Response

(PPR)

Select assets per threats. Define generic PPRs at the Air and Space level.

2. Configure the Authority Settings

a. Open the Task Force Manager window.

(1) Click the IDD tab on the Ribbon bar.

(2) Click <Task Force Configuration> in the Blue Force group. The Planning Task Force Manager window opens.

(3) Click the Authority tab on the window to access the following sub-tabs: ID Authority, Engagement Authority, CDO Authority.

UNCLASSIFIED

b. Configure the Task Force Authority.

(1) ID Authority and Engagement Authority tabs – TBM and ABT threat types display in both tabs.

(a) IBCS hierarchy starts below the HEU designator.

(b) Each hierarchy consists of all EOCs at the same level.

(c) Users designate EOCs as subordinate to one another. The hierarchy goes one level—a subordinate EOC cannot have a subordinate.

(d) Edit the list by dragging and dropping the EOCs to create a hierarchy.

(e) Designate an EOC as subordinate by dragging and dropping the EOC on top of the higher-echelon EOC.

(f) Click <Reset> to return all of the EOCs to the default hierarchy.

(g) ID Authority

1) The ID Authority setting, if ON, relates to having an actionable “Accept Recommendation” and “Override” button.

2) ID authority functionality issues:

(h) Engagement Authority

1) Engagement Authority designates an EOC as authorized for an engagement and associated shots.

2) Does not equate to whether or not the user has an actionable “Commit” button—that is related to Engagement Tasking Control in Task Force Configuration.

(2) CDO Authority tab – The <TDL CDO Authority> is switched ON (green) or OFF (grey).

(a) Change Data Order (CDO) Authority is Task Force wide.

(b) CWMI is restricting the CDO button in the Track ID View based on this setting. If toggled ON, the Track ID View has an actionable CDO button.

(c) The ON setting allows the TDL JU (JTIDS/MIDS Units) of the IBCS task force the authority to transmit a J7.0 Change Data Order (CDO) over the Link 16 network.

3. Configure the TF Configuration

a. Open the Planning Task Force Manager window.

(1) Click the IDD tab on the Ribbon bar.

(2) Click <Task Force Configuration> in the Tools (Blue Force) section. The Planning Task Force Manager window opens.

UNCLASSIFIED

(3) Click the TF Configuration tab on the window to access the following sub-tabs:

Support Control, Mode Control, and Engagement Tasking Control.

(a) Support Control – Define the resources each EOC supports.

1) Initially, the control was intended to indicate logistical, administrative, and personnel functions, but has evolved.

2) CWMI is utilizing Support Control for assignment of Integrated Fire Control Network (IFCN) Relays in the EOC Manager Equipment list.

3) CWMI restricts operator actions at the Sensor Manager for Emplacement/Geodetic Registration based upon Support Control settings.

4) Network Manager (NM) uses Support Control because it affects the amount of Simple Network Management Protocol (SNMP) traffic going over the IFCN for black-side relay monitoring.

UNCLASSIFIED

(b) Mode Control – Identify the EOCs having state and mode control.

1) Multiple EOCs can have Mode Control of an EOC or Sensor, or a single EOC can have Mode Control of an EOC or Sensor—launcher state/mode transitions are not restricted.

2) Command and Control nodes (EOCs), have restrictions for state only.

3) For Sensors, UI is only restricting a Patriot radar for the capability to select the “Proceed” option in the State/Mode Transition request.

4) UI is not restricting any actions specific to a Sentinel based upon Mode Control, despite the fact that they are listed within this control.

(c) Engagement Tasking Control – Define the sensors and weapons each EOC commands for local planning during Engagement Operations.

1) Engagement Tasking Control can be specified so that multiple EOCs have Engagement Tasking Control of a Sensor or Weapon—or a single EOC can have Engagement Tasking Control of a Sensor or Weapon.

Carefully consider additions to an EOC based on geographical locations.

2) Only resources (sensors and weapons) assigned via Engagement Tasking Control are utilized for that particular EOC to generate engagement plans.

3) Mission Control software only plans with Sentinel and Patriot sensors. A Generic Sensor added using Sensor Planning Manager displays, but is not utilized for engagement planning purposes.

4) Add Sentinel radars as necessary—Mission Control requires they are listed as taskable for calculations of sensor access to occur. Launch on remote cases can occur with Patriot Advanced Capability (PAC-3 CRI) and Missile Segment Enhancement (MSE) interceptor types.

UNCLASSIFIED

(4) Observe a similar window interface displayed in all three sub-tabs:

(a) Task Force Actual Resources section.

1) Displays the list of resources added to the open defense plan.

2) The resource icons display MIL-Standard symbols based on resource type.

3) A resource icon disables while the resource is associated with an EOC—removing the association to an EOC enables the icon.

(b) Selected Resources section.

1) The window section on the right, above the <Add Resource> button, refreshes with a specific resource list when selecting different EOCs from the drop-down menu.

2) The selected resource list is collapsible and includes headers displaying the number of items in each resource group.

(c) <Add Resource> button – Moves resources from the actual to the selected resource list.

(d) <Remove> button – Removes a selected resource from the list, making the resource icon active and available in the actual resource list.

b. Perform resource allocation in each TF Configuration sub-tab window.

(1) Click on a TF Configuration sub-tab.

(2) Click the drop-down menu arrow in the Selected Resource section and select an

EOC.

(3) Select one or more resources in the Task Force Actual Resources section by holding down the <Ctrl> key and clicking an icon.

(4) Click <Add Resources> to allocate resources to the selected EOC, or drag and drop an icon into the Selected Resources section.

4. Configure the HW ID Matrix

a. Open the Planning Task Force Manager window.

(1) Click the IDD tab on the Ribbon bar.

(2) Click <Task Force Configuration> in the Tools (Blue Force) section. The Planning Task Force Manager window opens.

(3) Click the HW ID Matrix tab to access the following Major End Item (MEI) sub-tabs: Units, Sensors, Weapons, and Relays.

b. Establish the HW ID Matrix by correlating hardware parameters.

(1) Observe the following set of user-defined parameters in the sub-tabs: Logical ID, Hardware ID, Link 16 Track #, Echelon, HEU, and User Role Distribution Control.

(2) Users are prevented from entering a duplicate Hardware ID (displayed with a red “X” next to the entry).

UNCLASSIFIED

(3) Correlate the list of parameters found in the MEI sub-tab windows to build the HW ID Matrix.

(a) Logical ID column – Configured during other IDD view entry and cannot be modified in this window.

(b) Hardware ID – A drop-down menu displays a list of Hardware IDs to correlate to the Logical ID, or operators manually input an ID.

1) Radar Interface Unit (RIU) HW ID

1. ECS PN = 8 digits.

2. RS PN = 8 digits.

3. SN = 6 digits.

1. ECS PN = 11453251

2. RS PN = 11476100

3. RS SN = 590482

4. Reported UUID = 001145325111476100590482

2) Launcher HW ID

1. PN = 64059_83-82880

2. SN = _1

3. Reported UUID = 64059_83-82880_1

(c) Link16 Track # – Manually input a correlating Link 16 Track number.

1) The default value is 0.

2) Value is a 5 digit octal (and alphanumeric is not allowed).

3) The values should come from the Operational Tasking Data (OPTASK) Link, providing a higher and lower track block.

4) A J2.0 Indirect Precise Participant Location and Identification (PPLI) Land is sent for each IBCS MEI, and a corresponding J13.5 Land Platform System Status containing data specific to the MEI.

5) Equating the Task Force JU located in Plan Settings as an entry is NOT recommended. IDD allows the user to duplicate the Task Force JU with a Link16 Track #, however ADSI/MIDS Terminal sends J2.5 Land Point with the Tasks Force JU as well as a corresponding J13.5 Land Platform System Status containing rollup data i.e. total missile count, etc.

(d) Echelon

1) Select from the list of menu options to associate the Echelon with the Logical ID.

2) Echelon selection has no bearing on the operational software and is only visualized on CWMI map during planning/while viewing an open defense plan.

(4) Correlate the list of parameters applicable to Units only.

(a) Higher Echelon Unit (HEU) – Has no bearing on the operational software and does not need completion.

(b) User Role Distribution Control – Checking the box allows the EOC to distribute user roles.

1) On the workstation:

2) Currently, the script only functions in operational mode, not training mode.

3) For proper functioning, an activated defense plan, and a defined User Role Distribution Control—in the HW ID Matrix—is required.

4) All EOCs in the task force must be operational for role distribution.

5) The script functions correctly only at the EOC designated as the Role Distribution Control per the HW ID Matrix.

6) If the script is executed from an EOC that is not designated as the Role Distribution Control per the HW ID Matrix, it will not function properly/be successful.

c. HW ID Alerts.

(1) Invalid Component Connection Attempt

(a) Conflict: An A-side (sensor or weapon), not included in the defense plan, is attempting to join the network.

(b) Message: “Invalid Connection Attempt, Component abc is attempting to Connect at 5wxyzB.”

UNCLASSIFIED

(c) Resolution: Edit the defense plan—if the A-side is appropriate for the task force—with the correct HW ID for the component.

(2) Duplicate Connection Attempt

(a) Conflict: More than one A-side has the same HW ID, indicating a personalization issue.

(b) Message: “Duplicate Connection Attempt, Component abc is attempting to connect at 5wxyzB.”

5. Configure the Rules of Engagement

The ROE determine when an AIR object is eligible for engagement planning and processing, and is task force wide.

a. Click the IDD tab on the Ribbon bar.

b. Click <Task Force Configuration> in the Tools (Blue Force) section. The Planning Task Force Manager window opens.

c. Click the ROE tab.

d. Check the Identities to apply to the AOI ROE: UNKNOWN, NEUTRAL, and

SUSPECT.

e. Observe that the HOSTILE identity is always eligible (checked) for engagement.

(1) If a target is not eligible per the Rules of Engagement, the operator can “Add Track to Target Dataset” (referred to as “Manage by Exception” (MBE)).

(2) Operators cannot add a track with a declared identity of Friend or Assumed Friend to the target set—a Non Compliance Message with “cannot process” (CANTPRO) generates in both cases.

f. AIR tracks - the software only assesses engagement based on the declared identity—not recommended identity—of a track.

g. Software assesses AIR tracks based on instantaneous trajectory.

h. SPACE tracks, regardless of position in/out of the AOI, are eligible for engagement.

NOTE: On the CWMI toolbar, the Weapon Control State (WCS) can be set per workstation—the control is workstation specific, not EOC or task force wide—and has no bearing on Mission Control Software.

6. Configure CID and IFF Controls

a. Describe CID Declarations, Recommendations, and Rules.

(1) CID Declaration – The ID assigned to a track by the Operator or Controlling Authority.

(a) Declaration values: PENDING (default), UNKNOWN, NEUTRAL, ASSUMED FRIEND, FRIEND, SUSPECT, or HOSTILE.

(b) Operator knowledge of the Battle space determines the declarations.

UNCLASSIFIED

(c) Declarations are made when:

1) The Operator accepts a recommendation, or overrides the recommendation, to set a different ID.

2) IBCS auto-declares the ID of a track when the track meets the specific circumstances of a CID configuration rule.

(d) IBCS uses CID Declarations to determine which tracks are eligible for engagement.

1) Engagement planning functionality depends on the Declared ID setting.

2) Declarations populate Link 16 messages about a track that the system sends.

(2) CID Recommendation – The ID that the CID Evaluation process determines is the most likely ID of a track based on accumulated evidence.

(a) Recommendation values: UNKNOWN (default), NEUTRAL, ASSUMED FRIEND, FRIEND, SUSPECT, or HOSTILE.

(b) Recommendations rely on the probability of tracks being FRIEND, NEUTRAL, or HOSTILE as computed by CID based on accumulated evidence.

(c) By definition, a probability is never 100% certain.

(d) CID gathers evidence from multiple sources to generate Recommendations, including sensors, kinematics, IFF responses, Link 16 external tracks, etc.

1) CID continuously re-evaluates track ID Recommendations as new evidence develops.

2) Recommendations help the Operator to declare the proper ID for a track.

3) The current Declared ID of a track does not affect Recommendations.

(3) CID Configuration – The specific set of conditions a track must meet for IBCS to auto-declare the ID, instead of forcing the Operator to manually accept or override the ID.

(a) The Operator enables or disables CID Configurations in the Planning Task Force Manager window during defense planning. The exceptions are a set of rules (Table 2-2) mandated by MIL-STD-6016 that are always set to ON and cannot be disabled by the operator.

(b) Rules only affect CID Declarations and never affect CID Recommendations.

(c) CID Configuration enables the system to auto-manage many uncertain Declarations, freeing the Operator to focus on more certain cases.

(d) The conflict entries in Table 2-2 apply when two IBCS nodes determine that different identities or platforms for the same track exist. The attempt is to achieve Classification, Categorization, Typing, Discrimination, & Identification (CCTDI) alignment. The rules alleviate issues with a late-joiner or dropped message over the network.

UNCLASSIFIED

Table 2-2. CID Configuration Default Settings

Rule Text ON or OFF

1 If platform is a TBM, recommend identity is Hostile or Suspect, the declared identity is Pending, Unknown, Suspect or No Statement, and the identity has not been overridden, then auto-accept recommendation.

ON

(Can be set to OFF)

2 If global track is an IBCS interceptor and the recommended identity is Neutral, and the identity has not been overridden, then auto-accept recommendation. (Previously rule N2)

ON

(Can be set to OFF)

3 If category is Clutter or Spurious, the recommended identity is Neutral, and the identity has not been overridden, then auto-accept the recommendation.

(Previously rule N1)

ON

(Can be set to OFF)

4 If associated with PPLI source track, the recommended identity is Friend, and the identity has not been overridden, then auto-accept.

(Previously rule N7)

ON

(Can be set to OFF)

5 If associated with a Mode 5 Squitter source track, the recommended identity is Friend, and the identity has not been overridden, then auto-accept the recommendation.

(Previously rule N9)

ON

(Can be set to OFF)

6 If associated with a BFT source track, the recommended identity is Friend, and the identity has not been overridden, then auto-accept the recommendation.

(Previously rule N9)

ON

(Can be set to OFF)

7 If track has valid IFF Mode 5 response, the recommended identity is Friend, and the identity has not been overridden, then auto-accept the recommendation.

(Previously rule N15)

ON

(Can be set to OFF)

8 If track has a valid IFF Mode 4 response, the recommended identity is Friend, and the identity has not been overridden, then auto-accept recommendation.

(Previously rule N16)

ON

(Can be set to OFF)

9 If both the **TDL identity and the recommended identity are HOSTILE, and the declared identity is PENDING, then auto-accept the recommendation.

ON

(Can be set to OFF)

10 If the Anti-Radiation Missile attribute is True, the platform is Air-to-Surface Missile, the track is targeting a sensor, the recommended identity is HOSTILE, the declared identity is PENDING, UNKNOWN, SUSPECT, or NO STATEMENT, and the identity has not been overridden, then auto-accept the recommendation.

ON

(Can be set to OFF)

UNCLASSIFIED

Rule Text ON or OFF

11 If (1) the ASM carrier attribute is true, (2) there is a recognized air launch from this track, (3) the missile launched from this track has been declared Hostile, ( 4) the recommended identity is Suspect or Hostile, and (5) the identity has not been overridden, then auto-accept the recommendation.

ON

(Can be set to OFF)

12 If (1) declared identity has a stale auto-accepted state from rule AA001_hostile_tbm/TBM01, (2) the recommended identity is not Suspect or Hostile, and (3) the recommended identity is not Suspect or Hostile, and (4) the recommended platform is not a TBM, then auto-accept the recommendation.

ON

(Can be set to OFF)

13 If TDL identity is Friend, the local identity is Pending, Unknown, or Assumed Friend, and the identity has not been overridden, then accept the TDL identity.

(See MIL-STD-6016D Table 4.4-2)

(Cannot be set to OFF)

(Rule not optional; mandated by

MIL-STD-6016D)

14 If TDL Identity is Assumed Friend, and local identity is Pending, Unknown, or Assumed Friend, and the identity has not been overridden, then accept the TDL identity.

(See MIL-STD-6016D Table 4.4-2)

ON

(Cannot be set to OFF)

(Rule not optional; mandated by

MIL-STD-6016D)

15 If TDL Identity is Neutral, and local identity is Pending, Unknown, or Assumed Friend, and the identity has not been overridden, then accept the TDL identity.

(See MIL-STD-6016D Table 4.4-2)

ON

(Cannot be set to OFF)

(Rule not optional; mandated by

MIL-STD-6016D)

16 If TDL Identity is Suspect, and local identity is Pending or Unknown, then accept the TSL identity.

(See M IL-STD-6016D Table 4.4-2)

ON

(Cannot be set to OFF)

(Rule not optional; mandated by

MIL-STD-6016D)

17 If TDL Identity is Unknown, and local identity is Pending or Unknown, and the identity has not been overridden, then accept the TSL identity.

(See M IL-STD-6016D Table 4.4-2)

ON

(Cannot be set to OFF)

(Rule not optional; mandated by

MIL-STD-6016D)

18 If (1) there is a Task Force Identity conflict, (2) primary node identity is Unknown, (3) local node identity is Pending, and (4) platform labels are compatible, then accept the primary node CCTDI values.

ON

(Cannot be set to OFF)

19 If (1) there is a Task Force identity conflict, (2) primary node identity is Assumed Friend, (3) local node identity is Pending, Unknown, or Assumed Friend, and (4) platform labels are compatible, then accept the primary node CCTDI values.

(Cannot be set to OFF)

UNCLASSIFIED

Rule Text ON or OFF

20 If (1) there is a Task Force identity conflict, (2) primary node identity is Friend, (3) local node identity is Pending, Unknown, or Assumed Friend, and (4) platform labels are compatible, then accept the primary node CCTDI values.

ON

(Cannot be set to OFF)

21 If (1) there is a Task Force identity conflict, (2) primary node identity is Neutral, (3) local node identity is Pending, Unknown, or Assumed Friend, and (4) platform labels are compatible, then accept the primary node CCTDI.

ON

(Cannot be set to OFF)

22 If (1) there is a Task Force identity conflict, (2) primary node identity is Suspect, (3) local node is Pending, or Unknown, and (4) platform labels are compatible, then accept the primary node CCTDI values.

ON

(Cannot be set to OFF)

23 If (1) there is a Task Force identity conflict, (2) primary node identity is Hostile, (3) local node is Pending, or Unknown, and (4) platform labels are compatible, then accept the primary node CCTDI values.

ON

(Cannot be set to OFF)

*CCTDI: Classification, Categorization, Typing, Discrimination, & Identification.

**TDL: Tactical Data Link

b. Set anti-radiation missile (ARM) Classification.

(1) Click the CID Config / IFF Cntrl tab on the Planning Task Force Manager window.

(2) Set the ARM Class Auth. Command switch to ON to enable ARM classification authority command for the task force.

(a) The toggle indicates that ARMs are in theatre.

(b) The property is global and is applied across the task force.

(c) Enabling the feature allows for a declaration of:

1) Platform Air to Surface Missile

2) Subclass of ARM_x

3) Specific Types of ARMs supported by IBCS software

(d) The toggle ON allows for a declaration based on Track Feature Data from a supporting sensor indicating ARM, or evidence based upon the ARM Classification/Extrapolation (ACE) algorithm.

(3) Set the ARM Class Auth. Command switch to OFF to disable ARM classification authority command for the task force.

(4) Observe the following if ARM Class Auth. Command is OFF and Combat ID has evidence that supports an ASM:

(a) The platform is changed to GENERAL AIR.

(b) The subclass is changed to ABT_NOMINAL.

(c) Specific Types are replaced with No Statement.

Figure 2-1. ARM Classification and Auto NCTR Settings

c. Set Auto Non-Cooperative Target Recognition (NCTR).

The Auto NCTR drop-down menu is not available if Auto NCTR is enabled for one or more individual sensors in the Sensor Planning Manager window. Enabling Auto NCTR in the Planning Task Force Manager window also prevents Auto NCTR from being set at individual sensors.

(1) Click the Auto NCTR drop-down menu button.

(2) Select the NCTR option:

(a) Off – Disable automatic NCTR.

(b) On ABT – Automatic NCTR is enabled for ABT tracks only.

(c) On All – Automatic NCTR is enabled for all tracks.

d. Activate and deactivate CID Configuration.

(1) Click <CID Configuration>.

(2) Click CID rule buttons to ON (green) or OFF (grey).

(3) Click <Apply> to save changes.

e. Configure the IFF Control settings.

(1) Click <Final IFF Control> on the CID Config / IFF Cntrl tab.

(2) Select the ABT option in the Final IFF section.

(3) Click the Priority 1 drop-down menu and select a sensor IFF mode. Repeat the step for the Priority 2, Priority 3, and Priority 4 drop-down menus.

NOTE: Currently, IDD allows duplication of mode selections across different Priorities.

Future software versions will resolve the issue.

(4) Select options from the drop down menu under Required Final IFF, designating final IFF responses for ABT tracks.

(a) Not Interrogated – The track is not interrogated.

(b) Interrogated No Response – The track is interrogated with no response.

(c) Interrogated, Invalid – The track is interrogated, but is invalid.

(d) Interrogated Valid no Ambg – The track is interrogated, response is valid, with no ambiguity.

(e) Interrogated Valid w Ambg – The track is interrogated, response is valid, with ambiguity.

UNCLASSIFIED

(5) Add a Final IFF Plan.

(a) Click <Add> in the Final IFF Control option box.

(b) Select an option to add to the list.

(c) Type a name for the Final IFF plan in the Name field.

(d) Click <Apply> to save changes.

(6) Remove a Final IFF Plan.

(a) Select a plan under Final IFF Control.

(b) Click <Delete>. The plan disappears from the list.

(7) Configuring IFF is not applicable to routine or operator initiated IFF interrogations.

(8) The entries from this view are available via a drop down when completing Pre- Planned Responses—if Final IFF is required.

(9) When “Final IFF Required” is OFF, Mission Control will NOT execute a Final IFF prior to executing automatic or operator committed engagements.

(10) There is a classified value (CV) for a time allocation to complete Final IFF.

(11) With 2.3 software, behaviors include:

(a) Mission Control (MC) may simultaneously command different sensors for Final IFF up to system adjustable parameters (SAP).

(b) MC commands the sensors simultaneously, meaning that if the priority IFF mode is "mode 5 format 3" then sensors that are reporting on the track, have IFF coverage of the track, and support mode 5 format 3, will be commanded to perform IFF at the same time up to a SAP max.

(c) After interrogation of priority 1 is completed, and MC finds no evidence to stop engagement, the system proceeds to priority 2, etc. Whether this is the desired behavior given that priority 1 was executed successfully is questionable, and subject to change in a future build.

(d) If no sensor can support Priority 1, then MC moves to the next priority (Priority 2).

(e) A priority mode can be attempted again if MC determines sufficient time remains before launch is commanded.

(f) If a response maps to “CHECK_ID_PRIOR_TO_EXECUTE”, MC will continue to interrogate for the allotted Final IFF time. When Final IFF time is complete, MC verifies the track is still eligible prior to publishing a committed shot.

(g) Final IFF changes shot(s) selection:

The following is not currently configurable via CWMI in a defense plan, but provides an explanation of current behaviors.

1) The software determines the timeline associated with Final IFF tasking based upon Threat Assessment.

UNCLASSIFIED

2) For both AIR and SPACE:

3) Stated another way, MC software will use lead time to support sequential Final IFF.

f. Configure Authorized IFF Interrogation.

(1) Click <Authorized IFF Interrogation> on the CID Config / IFF Cntrl tab.

(2) Observe that the Automatically Request IFF checkbox is OFF (unchecked) by default.

(3) Enter a value in the No IFF Received Interval (seconds) field. The default is 40.

(4) Enter a value in the IFF Received Interval (seconds) field. The default is 600.

(5) Observe that seven Modes are ON (checked) by default under the Authorized IFF Modes Allowed section.

(6) If Authorized IFF Interrogation is OFF, Combat ID (CID) should not perform automatic interrogations of any kind.

(7) Generally, one sensor is tasked, however multiple sensors could be tasked. Any sensor that is reporting on a track can be tasked, but is minimized by a random wait time before the request is sent.

(a) If two sensors are reporting on a track and IBCS attempts an IFF request, then CID receives a response before the 2nd sensor is tasked—based on the random wait.

(b) Typically the response is received before the 2nd sensor is sent a request. If a response is received, the 2nd sensor is not sent the request. However based the random wait time, it is possible that both requests could be sent.

7. Configure Pre-planned Responses

Operators define a set of logic parameters called pre-planned responses (PPR) that dictate how the IBCS system reacts to different types of threats. PPR configuration in a defense plan includes the ability to specify Final IFF execution.

a. Associate a track-type threat to a defended asset.

(1) Click the Pre-planned Responses tab on the Planning Task Force Manager window.

(2) Select an asset from the defense plan in the Select Asset drop-down menu.

(a) The menu is populated with all Defended Assets and RESIDUAL.

(b) RESIDUAL applies when the threat is not targeting an asset. If no defended asset is targeted, the Assets column in the Engagement Queue contain a dash (-).

(3) Observe that two track type option boxes display: <Air> or <Space>

UNCLASSIFIED

(4) Select the <Air> option box.

(5) Click the plus sign (+) at the top-left corner of the box to expand the Air track decision tree to the next tier. A minus (-) sign contracts the tree.

(6) Select the plus sign (+) in the <General Fixed Wing> option box. The tree expands displaying the next tier of general fixed wing track options.

(7) Select a general fixed wing option.

(8) Observe that a list of designators, specific to the selected option, display on the right side of the Pre-planned Responses tab window.

(9) An asterisk symbol (*) indicates a PPR contrary to default settings.

b. Set the responses and additional attributes for the track type.

(1) Select <Edit> at the bottom-left of the Pre-planned Responses tab window after selecting a designator.

(2) Observe that all parameters for the selected designator are now editable under the General tab.

(a) Set Engagement Modes

1) Engagement Mode default value is semi-automatic for both Air and Space.

2) Click <Automatic> to specify the automatic engagement of the threat type.

3) Click <Semi-Automatic> to disable automatic engagement of the threat type.

(b) Set Allocation Type: Computed or Directed

1) Computed Allocation - Specifies Psuccess, Min PK Per Shot, and Maximum Count.

UNCLASSIFIED

2) Directed Allocation - Specifies First Count, Subsequent Count, Maximum Count, Min PK Per Shot, Min PK Engage Now, and Interceptor Diversity.

1. Similar to the Patriot mixed ripple setting—applies to the selection logic and not firing order, and is applied only to the first two shots in the first phase. For example:

Case: First shot = 2, subsequent shots = 0, and max = two.

Multiple interceptor preferences are provided.

Interceptor diversity is enabled.

Result: The 2 highest preference interceptor types are used to formulate the two shots

2. If interceptor diversity is enabled with only one interceptor type in inventory, Mission Control will continue to perform engagement planning.

(c) Set PPR Interceptor Preferences

1) Priority

2) Preferred Intercept Altitude (PIA)

3) TBM No Engage Zone (TNEZ)

4) Select the priority for the available interceptor types.

5) Use the scroll bar on the right side of the window to view all types.

(d) Set Final IFF

1) When “Final IFF Required” = false, Mission Control will NOT execute Final IFF prior to executing auto or operator committed engagement.

2) Final IFF Reaction table specifies the Mode(s) and the resulting action taken in response to the IFF interrogation.

3) The drop down selection is populated with all Final IFF rules generated from the IFF Cntrl view—the default rule is ABT.

(e) PPR Protective Keepout

1) Nominal engagement plan represents the system best engagement considering factors such as keepout.

2) Engage Now also takes into account protection score—how far is the intercept from keepout.

3) Keepout Range

4) Keepout Altitude

5) If no Keepout is defined, a shot is considered to have violated the boundary if inside the defended asset radius.

6) For AIR category, Altitude is only displayed for attributes ARM_A, B, etc.

7) For AIR category, Range is always listed and in meters.

8) The goal is to choose shots that do NOT violate keepout. If no shots are available outside the keepout, the operator gets a bounda

(3) Select <Done>.

(4) Select the plus sign (+) tab next to the General tab to open the Air-Add Attributes window.

(5) Check the box next to a listed attribute to add the attribute to the specific designator.

UNCLASSIFIED

(6) Review additional capabilities:

(a) After editing PPR (selecting <Done>), the user has the capability to <Select Assets> to apply to all defended assets and RESIDUAL—realize that the "Select Assets" listing incorporates RESIDUAL.

(b) <Remove> eliminates the unique PPR settings for that specific threat tree selection only—does not remove unique PPR settings below that threat tree selection.

(c) The user has the capability operationally to select <Edit PPR> in the engagement queue on a per track basis. The options currently are shot counts and interceptor preference only.

(7) Click <Apply> to save changes. All pre-planned response parameters are set for the track-type threat associated to the selected asset.

ELO C: PERFORM DEFENSE PLAN OPTIMIZATION

Action: Perform defense plan optimization and evaluation.

Conditions: Given the IBCS, SUM, and IBCS Advanced IDD Student Guide.

Standards: Optimize a defense plan; evaluate the effectiveness of the plan, and describe advanced Area Manager and Asset Manager tasks.

1. Describe the IDD Evaluator/Optimizer (IEO)

The IDD Evaluator/Optimizer (IEO) is an IBCS CWMI software component that can both evaluate the effectiveness of a defense plan and optimize the placement of task force units, Engagement Operations Centers (EOC) and relays, Patriot and Sentinel sensors, weapons, and comm nodes within the Task Force Area (Error! Reference source not found.).

Figure 2-2. Evaluating vs. Optimizing a Defense Plan

UNCLASSIFIED

a. Running the optimizer moves resources within the defense plan and cannot be undone. The recommendation is to perform a “Save As” on the defense plan prior to running the optimizer if maintaining the current deployment is desired.

b. Running the evaluator does NOT move any resources.

c. The Optimizer now takes line-of-site (LOS) into account. After running the optimizer, users still have a forming network.

d. Optimization can be run without a Task Force Configuration. The service uses algorithms associated with Level of Protection (LOP) to determine shot counts, and does not take into account the defense plan Pre-planned Responses (PPR), etc.

2. Optimize a Defense Plan

The Integrated Defense Designer (IDD) Evaluator Optimizer (IEO) provides the capability to evaluate an Integrated Air and Missile Defense (IAMD) deployment against a non-reactive threat scenario and to optimize the placement of defense assets (sensors, weapons, and comm nodes) in order to maximize the ability to defend against that threat. The optimization method and the quantity of resources and threats in the defense plan determine the time required for optimization—large defense plans may take hours.

● Any launcher-uplinker pairings made before optimization are broken when the Optimization service moves the radar and/or launchers. Refer to “Manage Patriot Sensors” for instructions on pairing launchers with uplinkers.

● Only one EOC workstation at a time can run optimization. The alert “Cannot run optimization, server is busy” displays when a second workstation on the same server attempts optimization.

● Users cannot edit selections when optimization is running.

CAUTION: Optimization permanently changes the defense plan and is not reversible. Before running the service, use the <Save Plan As> button on the IDD tab to save a copy of the plan to the local hard disk.

a. Verify Optimization Service minimum requirements.

(1) The defense plan has a valid Task Force Area located in a part of the world covered by the Digital Terrain Elevation Data (DTED) loaded on the system.

(2) One of each resource below is in the defense plan and located inside the Task Force Area:

(a) Comm node

(b) Sensor

(c) Weapon

(d) Defended Asset

(3) No defended asset or task force resource is located outside of the Task Force Area.

(4) The defense plan has at least one threat associated with a Threat Area Origin (TAO), and the threat meets the following criteria:

(a) Has sufficient range to reach a defended asset from the TAO containing the threat.

UNCLASSIFIED

(b) Flight Path Manager evaluated the threat flight path, and the corresponding trajectory or flight path displays on the map.

b. Open the Optimization window.

(1) Click the IDD tab on the Ribbon bar.

(2) Click <Optimization> in the Tools group. The Optimization window opens.

c. Set asset allocations.

(1) Review Surveillance, Fire Control Track Quality, and Engagement weight values given to area sub-scores in the Set Allocations screen.

(a) Surveillance Quality Track: Weight given the Surveillance Quality subscore of the deployment.

1) Threat trajectory segments with very low composite track positional error—relative to the Surveillance Accuracy input—receive almost full credit, while those that are untracked or have especially large composite track positional errors receive little to no credit.

2) The Surveillance subscore is normalized from zero to one, but typically ranges…