Attachment 0006 - Product Demonstations Event_17 September 2021.pdf

This document contains information that may be exempt from mandatory disclosure under the Freedom of Information Act.

September 17 2021

Product Demonstration Event Plan For

All-Source 2

PRODUCED BY

Product Manager Data and Analytics

PRODUCED FOR

All-Source 2 Contractors Contract No:

Delivery Order No:

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure or reconstruction of the document.

NOTE: The use of a trade name or the name of the manufacturer or a contractor in this report does not constitute an official endorsement or approval of the use of such commercial hardware or software or of service. The report may not be cited for purposes of advertisement.

Version Initial Final

PM Intelligence Systems & Analytics

Signature Page

Approved by:

Deputy Product Manager, PdM Data and Analytics Project Manager (PM), Intelligence Systems and Analytics

1 Purpose The Intel Apps Product Demonstration Event Plan describes the specific event details associated with the All-Source 2 Product Demonstration.

The following appendices are enclosed with this document:

• Appendix A. Execution Threads and PRD Mappings

• Appendix B. Acronyms and Abbreviations

1.1 Product Demonstration Details

The purpose of Product Demonstration (PD) is for the Government to verify the All- Source 2 software meets core capabilities within the Performance Requirements Document (PRD). During the PD, vendor personnel, with assistance by the Government, will conduct the PD threads. The PD execution will be conducted in accordance with the Threads contained in the PD Event Plan for All-Source 2. Prior to the start of Thread execution the vendor will be provided time to provide an oral/visual presentation of their system. Attributes specific to PD:

Location: Virtual observation for Contractor personnel not specified in the following;

Government, in conjunction with (2 or more) vendor representatives will execute on-site at Booz Allen Hamilton Software Integration Laboratory (BSIL), 4692 Millennium Drive, Suite 200, Bel Camp, MD

Environment: Unclassified, closed-network

Host: Unclassified commercial Cloud host

Data Source: Government-provided data sets

Data Injection: SharePoint, Flat files, SMTP, OGC Services (WMS, WFS, WCS), IS&A api (through CD2)

Data Reduction: XML output; Video capture; Manual observations, IS&A api queries

All Source 2 Operators: Vendors

Event Moderation: Conducted by the Government

Data Collection: Conducted by the Government

Technical Criteria:

1. (Technical Criteria #1) ASII Deployment - The All Source 2 Application must deploy within the allotted resource allocations and be accessible via a web client.

2. (Technical Criteria #2) Receipt of Mission Tailored Data - The All Source 2 Application must demonstrate interoperability with the SSGF via the ingest and display of WMS, WFS and WCS data, and the ability to ingest mission tailored threat characteristics data.

3. (Technical Criteria #3) Data Retrieval and Visualization - The All Source 2 Application must demonstrate Interoperability with DCGS-A v3.2.5 and CD1 via the ingest and extraction of a Virtual Cabinet (VCAB) file, demonstrate the ability to ingest data from CD2 via the IS&A api, demonstrate the ability to do simple and complex queries, and visualize data on the map, a link diagram and in a tabular format.

4. (Technical Criteria #4) Mission Planning – The All Source 2 Application must demonstrate an automated Route-Projection (COA(s)) of a threat Unit, Leveraging Supporting Data Elements (e.g., COO, Equipment Parameters), and Generate Potential Routes (Minimum of 3), develop a MCOO and Threat COAs, with an Event Template, Event Matrix and HVT List for each Threat COA and publish appropriate data to CPCE.

5. (Technical Criteria #5) Data Analytics - The All Source 2 Application must demonstrate the Content Extraction and Normalization of Semi-Structured (e.g., USMTF) data and Correlation of Structured data.

6. (Technical Criteria #6) Threat Model Management and Matching - The All Source 2 Application must demonstrate the ability to create, update and delete threat composition and disposition models and to designate composition models and provide user alerts for pattern matching.

7. (Technical Criteria #7) Cyber Hardening - The All Source 2 Application must demonstrate only authorized access though login credentials on a secure web link.

1.2 Location

All-Source 2 Product Demonstration will be conducted primarily remotely. The Government and the Contractor will be remote from each other with exception of the two (2) Contractor representatives collocated with the Government. All interaction between the Government and the Contractor will occur over WebEx. The Government will provide remote participation opportunities through WebEx for an additional eight (8) Contractor persons.

1.3 Schedule

1.3.1 Schedule by Day/Hour

The Government plans for the Product Demonstration is to span approximately four (4) hours with the following distinct events. The Government plans for PD Threads to generally adhere to the following hourly schedule for Day one (1). The Government and the Contractor may agree to slight variations in the hourly schedule should it enable the execution of a required PD Step. Prior to the PD execution, the Government will provide access to AWS and BSIL related systems to perform integration and configuration.

Table 1. Schedule by Day

Week Planned Dates

Item Description

Day #1

Hours 0-1 Oral/Visual System Presentation

The vendor may present an overview of their system to include capabilities, workflow, screen shots, etc.

Hours 1-3 Deployment, Configuration and Checkout

The vendor (assisted by the Government) will configure and execute pre-condition steps, and execute a functional checkout within the BSIL environment.

Hours 3-4 Receipt of Mission Tailored Data Thread Execution

The execution of the Product Demonstration Threads.

Hours 4-5 Data Retrieval and Visualization Thread Execution

The execution of the Product Demonstration Threads.

Hours 5-7 Mission Planning Thread Execution

The execution of the Product Demonstration Threads.

Hours 7-8 Data Review and Collection

The data discovery and data egress from the All Source 2 Application for post analysis.

Day #2

Hours 0-2 Data Analytics Thread Execution

The execution of the Product Demonstration Threads.

Hours 2-4 Threat Model Management and Matching Thread Execution

The execution of the Product Demonstration Threads.

Hours 4-5 Cyber Hardening Thread Execution

The execution of the Product Demonstration Threads.

Hours 5-6 Data Review and Collection

The data discovery and data egress from the All Source 2 Application for post analysis.

1.4 Rules of Engagement

The following rules of engagement (ROE) apply for the All-Source 2 Product Demonstration:

• The Vendor will interact only with the Government (or Government's agents) to configure, execute necessary pre-conditions, and verify integration on the environment.

• The Vendor should only take instruction from representatives of the Government.

• The Vendor may communicate as required directly with Government staff.

• The Vendor may take notes and make their observations regarding the operation of their software.

• The Vendor may request the Government skip any step(s). The Government will consider any skipped step(s) that is not demonstrated over the course of Product Demonstration as a "fail".

2 PD Architecture/Environment

2.1 Client Computers

The Government will provide the required number of client systems for access to the All-Source 2 software during Thread execution. The Government will provide Dell 6800 laptops running the Army Gold Master, Windows 10 suite with the latest approved version. At a minimum, this will include Microsoft Edge; Google Chrome; and Mozilla Firefox browsers; Microsoft Office (Word, Excel, PowerPoint); and Adobe Acrobat Reader.

2.2 Cloud Environment

The Government will provide Cloud access to the Contractor to host their All-Source 2 Solution for the Product Demonstration. The Contractor will have reasonable agency to determine the AWS EC2 instance types that will best host their software. The Government reserves the right to assess if the performance of the vendor’s chosen EC2 instances greatly exceeds the current (or near future) capabilities of the Tactical Server Infrastructure V2 Hardware.

The aggregate of these Amazon Web Services (AWS) instances should not exceed the following resources:

• 24 Cores

• 96GB RAM

• 1 TB Storage

The Contractor may identify their preferred AWS configuration which may include:

• AMI Types, S3 configuration

• Operating system

• Network/VLAN configuration

• Ports/protocols for remote access

The Government will not provide any additional AWS services.

2.3 Architecture

Figure 1 depicts the high-level architecture of Product Demonstration. Figure 2 depicts the staffing/location profile during the event execution.

Figure 1. Product Demonstration High-Level Architecture

Figure 2. Product Demonstration Staffing Architecture

2.4 Event Rooms

The Government will provide space for PM IS&A personnel and two (2) Vendor Representatives at Booz Allen Hamilton. All other participants will be remote.

3 Product Demonstration Procedures The Contractor operator will be on-site at Booz Allen Hamilton. Other Government participants may be remote. The Contractor is permitted up to eight (8) remote observers. Remote Contractor observers may assist execution as required by the Government.

3.1 Event Conduct Roles

At minimum, the Government expects the following roles represented:

Table 4. Product Demonstration Roles

Role Description Planned Physical

Location during Product Demonstration

Government Moderator

The Moderator will chair event execution and serve as the Government's lead liaison to the Contractor personnel.

On-site

Government Contractor Support

Government contractors will operate external systems (CPCE, CD2) and will assist with any troubleshooting of these systems during the event.

On-site

Vendor Personnel

The Contractor will provide Operator(s) that will perform the intended functions. The Contractor may swap the Operator role at any time during the event.

When required the Contractor may use multiple Operators.

On-site

Vendor Personnel

The Contractor may participate remotely; up to eight

(8) persons may participate by WebEx.

Remote

User Analyst SME The Analyst SME will serve as a subject matter expert (SME) in the analysis and data functions.

Remote

Army Capabilities Manager - Foundation

The Army Capabilities Manager- Foundation (ACM- F) serves as a requirements SME.

Remote

Other members of the Government Project Manager Intelligence Systems and Analytics (IS&A) Team will be virtually present at all, or portions, of the PD they are not required to execute. They may be tasked to address concerns or questions that arise during event conduct. Other Government agency observers may virtually witness all, or portions, of event. They will not have interactions with the Contractor unless permitted by a person from the Government PM IS&A Team.

3.2 General Conduct

The Government will moderate the PD threads and steps contained in Appendix A. The Government will not deviate from the PD threads unless the contractor is unable to use the All-Source 2 Application to execute the step. The Government and the Contractor will mutually agree on any modification, or workaround, in order to execute the intended step.

4 Data Sets The Government will provide the Contractor with all input/stimulus data required to conduct a Product Demonstration event. The data included (but are not limited to):

• Entities, relationships, and attributes

• Messages

• Maps, Geospatial Data - Combined Obstacles Overlay (COO)

4.1 Data

As part of the Product Demonstration the All Source 2 solution will be required to (1) ingest static data types, (2) ingest data from external sources, (3) leverage SSGF data. These include:

• Map and Geo layers - Raster (e.g., CADRG and CIB), Vector (e.g., Civil Consideration, Hydrology Layer, DTED, CCM)

• Virtual Cabinet (VCAB) file (static file)

• USMTF (static file) ingest of IIR, ENSIT, EOBSREP

• MS Excel files ingest of MinERG data

Static files will be made available via access to a common file Window-based file share.

5 Data Collection The Government may collect the following types of data during the Product Demonstration:

• Screen captures (discrete)

• WebEx recording of the operator’s screen

• Exports of the All-Source 2 database

• Manual data such as:

o Observations o Notes o Product Demonstration Incidents - to include the following fields; date, time, category, status, summary, description, and Thread step during occurrence

The Government will provide a file storage location where the Contractor will be provided access to place screen captures and database exports.

5.1 Screen Capture

The Government will use WebEx to record the audio and video of the operator’s screens as well as any questions that are logged through the WebEx "Chat" feature. The "WebEx Moderator" will push control of the screen to the "operator" of any individual Thread step. The Contractor operator will capture screen shots of available screens at the Government discretion.

5.1.1 Data Extraction

At the conclusion of the Thread Steps, the Government requires the Contractor to export their database to a non-proprietary format such as XML.

The Government expects, at a minimum to retrieve:

• The content of ingested messages (pre-extraction)

• The uncorrelated entity layer to include entities, attributes, relationships (entities pre-correlation), and history

Using this data, the Government intends to:

• verify the ability of the All Source 2 solution to accurately ingest and maintain the integrity of those ingest messages

• verify content extraction, entity creation (including entities, attributes, and relationships), and normalization

5.1.2 Terms and Definitions

The following terms and definitions are provided:

Entity Store – The data store of all ASII entities regardless of source or ingress DTG.

This data store is available for other applications to query and update through the IS&A api.

Publish to CPCE – Publishing data to CPCE refers to publishing entity or graphics data to a CPCE layer using the CPCE REST api defined in the CPCE SDK. It does not refer to publishing data to DDS.

6 Reference Documentation

1. ENSIT.UF.pdf

2. IIR.UF.pdf

3. EOBSREP.UF.pdf

4. DCGSA-REST-SUM-TEDRestURLGuide.docx

5. MinERG Schema

Appendix A. Product Demonstration Threads

Thread Step # Thread Steps Expected Results PRD Mapping ASII Deployment

1 The vendor deploys and configures their prospective ASII application.

The time and number of unique steps is recorded.

2 The ASII application deploys on a hardware resource footprint of 24 Virtual CPU Cores, 96 GB of RAM, and 1TB of storage.

The deployment configuration does not exceed the specified amounts.

11.1.1

3 The ASII application shall runs from resources stored on a central server (Thin Client)

The ASII application does not download any files or executables to the client workstation.

11.1.8

4 The ASII application provides a browser-based approach to using a thin client.

The ASII application runs in a browser. 11.1.9

Receipt of Mission Tailored Data 1 Ingest and display all government-stipulated map layer data via the provided WMS.

Ingest should be validated as successful without significant delay or error.

WMS map data can be displayed.

11.1.29

2 Ingest and display all other government-stipulated geospatial data via the provided WFS.

Ingest should be validated as successful without significant delay or error. WFS map data can be displayed.

11.1.29

3 Select WFS civil considerations on the map and convert to entities.

The entities are stored in the database with name, location and symbol at a minimum.

4.1.7, 4.1.8

4 Change the map display to display to appropriate data (e.g., change from 2D to 3D, zoom in to display terrain, zoom out to display paper maps).

Map data can be displayed appropriately.

11.1.29

5 Change the map scale to the following:

1:25K 1:50K 1:100K 1:250K

The map scales appropriately.

11.1.29

6 Ingest mission tailored threat characteristics data (e.g., composition, disposition, tactics (threat models)) provided by the user’s higher headquarters.

Ingest should be validated as successful without significant delay or error. The model can displayed on the map and in tabular form.

1.1.1

7 Ingest updated mission tailored characteristics data (e.g., composition, disposition, tactics (threat models)) provided by the user’s higher headquarters.

Ingest should be validated as successful without significant delay or error. The model can displayed on the map and in tabular form.

1.1.2

8 Ingest mission tailored environmental data (e.g., slope, land cover, hydrology, current and forecast weather, climatical, civil consideration) data provided by the user’s higher headquarters.

Ingest should be validated as successful without significant delay or error. The data can displayed on the map.

1.1.3

Data Retrieval and Visualization 1 Import government provided VCAB from DCGS-A

3.2.5. The VCABs is imported without error. 11.1.29

2 Display imported entity data on the map, as a link diagram and as a tabular listing of entities with key attributes.

The imported data is complete (all entities and relationships are present) and accurate (location and attribute values) and displays properly in all formats. Entities/Labels can be toggled on/off from the map.

3.1, 3.2

3 Import government provided VCAB from CD1. The VCABs is imported without error. 11.1.29 4 Display imported entity data on the map, as a link diagram and as a tabular listing of entities with key attributes.

The imported data is complete (all entities and relationships are present) and accurate (location and attribute values) and displays properly in all formats. Entities/Labels can be toggled on/off from the map.

3.1, 3.2

5 Import entity and relationship data from CD2 using the IS&A api. The data is imported without error. 11.1.29

6 Display imported entity data on the map, as a link diagram and as a tabular listing of entities with key attributes.

The imported data is complete (all entities and relationships are present) and accurate (location and attribute values) and displays properly in all

3.1, 3.2 formats. Entities/Labels can be toggled on/off from the map.

7 Select entities (from each source) and view entity history. The entity history is displayed. 3.2.3, 3.2.4, 3.2.5

8 Create, Update (to include multiple location updates of at least one entity) and Delete Entity and Relationship data (from the entity store) from map and link diagram.

Entity and Relationship Data is updated.

3.1

9 Query all the data from the imported VCABs. The query results show the updated data based on the edits and deletes.

3.1

10 Select updated entities (from previous step) and view entity history from both a timeline and map perspective.

The entity history is displayed as both a timeline and on the map over time.

3.2.1, 3.2.3, 3.2.4, 3.2.5

11 Drill down to the source from the entity history. The source document is listed and displayed.

3.2.4, 3.2.5

12 Demonstrate the ability for a user to query and retrieve data with user specified queries based on the following:

Entity Type Entity Attributes (Hostility, Name with wildcard, Tank versus Artillery vs Mosque) Time Period Geographic Location (bounding box) Source

The user is able execute the queries. 2.1.1

13 Display the query results on the map, as a link diagram and as a tabular listing. The results are properly displayed. 2.1, 3.2.1

14 Demonstrate the ability for a user to develop and save a compound search to include AND/OR operators on Attribute Values.

The results are properly displayed.

2.1.3

15 Demonstrate the ability for a user to save query criteria. Users are able to save queries. 2.1.4

16 Export all data in an .xml format for post-analysis Export should occur without significant delay or error.

Mission Planning

1 Demonstrate the ability to automatically evaluate the operational environment (e.g., terrain (natural, man-made), hydrology, weather effects, civil considerations) and classify where severely restricted, restricted, and unrestricted terrain exists on the Map.

Severely restricted, restricted, and unrestricted terrain is displayed on the map based on the available mission data.

6.1

2 Allow the user to modify (Delete, Adjust, Add Polygon Mid Points) the restricted and severely restricted terrain from the Map.

Restricted terrain can be updated by the user.

3.3, 6.1.2

3 Allow the user to create and delete restricted and severely restricted terrain from the Map.

Restricted terrain can be created and deleted by the user.

3.3, 6.1.3

4 Automatically identify terrain mobility classifications, avenues of approach and mobility corridors that a user can modify within the specified mission focused area using a user selected disposition Threat Model.

Possible avenues of approach and mobility corridors are automatically identified.

6.2.1, 6.2.2, 6.2.3

5 Automatically identify man-made and natural obstacles on the Map IAW USAS standard MIL STD 2525 symbology.

Obstacles are identified on the map.

6.2.4

6 Enable a user to modify obstacles on a map IAW USAS standard MIL STD 2525 symbology.

The user is able to modify obstacles. 3.3, 6.2.2

7 Automatically identify key terrain based on mission parameters on the Map.

Key terrain (e.g., gaps, observation points, supply routes controlling passages, economic and political centers, landing zones, etc.) are identified with symbology on the map.

A count anf type of identified key terrain is taken.

6.2.6

8 Enable a user to modify key terrain on the Map. 6.2.3 9 Publish the MCOO to CPCE. CPCE receives the MCOO on the

“MCOO” layer.

4.2.3, 11.1.11, 11.1.14

10 Demonstrate an automated route analysis capability that determines routes that an entity or formation can take based on a user specified movement area

Possible routes are displayed based on entry of user parameters.

6.5, 6.5.1, 6.5.2, 6.5.3 boundary, movement projection calculation (MCOO) data and presents them to the user on the map.

User will specify a Threat disposition Model, number of potential route(s), Start Point, Time of Departure, Light Data, and End Point.

11 The user updates number of potential routes. An updated display of possible routes are displayed based on entry of user parameters.

6.5, 6.5.1, 6.5.3

12 The user updates the Start Point, Time of Departure, and End Point

An updated display of possible routes are displayed based on entry of user parameters.

6.5, 6.5.1, 6.5.3

13 Display calculated potential routes on the map with Distance, Speed and Travel duration.

Routes are displayed with appropriate data.

6.5.1, 6.5.11

14 Select the routes on which the automated time-phase line threat march rate analysis will be performed, allow user to specify the desired time-phase line interval and generates Time Phase Lines for each selected route.

The routes can be selected. 6.6.3

15 Display the distance between each time-phase line on the map with the ability to toggle on/off the time-phase line (singular, group) on the map.

The distances can be displayed and time-phase lines can be toggles off/on.

6.6.6

16 Generate a situation template at each Time Phase Line that adjusts each component’s location within the model based upon the calculated MCOO data, allowing the user to manually adjust the components of the situation template on the Map. Real entity data is displayed with Solid Line vs planned Status as a Dashed Line.

A situation template at each Time Phase Line is displayed.

6.7

17 Create an event template for each threat COA allowing the user to:

• place a Decision Point (DP) on a map where the threat is projected to make a COA decision.

The event templates are created. A user is able to place a DP and NAI on the map and associate the two.

The event matrix is automatically created.

6.8.1, 6.8.2, 6.8.3, 6.8.4, 6.8.5, 6.8.10

• place an NAI on a map where information collection is desired

• allow a user to associate NAI(s) with a DP on the map

The event matrix is automatically created using the NAI/DP association and can be viewed concurrently with the event template.

18 Publish each threat COA and event template to

CPCE.

CPCE receives the data on the appropriate COA and Event Template layers.

4.2.3, 11.1.11, 11.1.14

19 Create an High Value Target (HVT) Matrices for each threat COA. HVT Matrix will include:

a. Priority

b. HVT Designation

c. HVT Type

d. HVT Role/Function

e. HVT Strength(s)

f. HVT Limitation(s)

The HVT matrices are created. 7.1.1

20 Modify the event matrix by changing the DP and NAIs on the map. The event template should automatically update.

The event matrix is updated which automatically updates the event template.

6.8.1, 6.8.10

21 Modify the event matrix by changing the DP and NAIs on the event matrix. The event template should automatically update.

The event matrix is updated which automatically updates the event template.

6.8.1, 6.8.11, 6.8.12

22 Re-publish the Event Template to CPCE. The data is republished to the appropriate CPCE layer to include the removal of any obsolete data.

4.2.3, 11.1.11, 11.1.13, 11.1.14

23 Modify the HVT Matrix for the threat COAs where the event template was modified.

The HVT matrices are updated. 7.1.1

24 Delete an Event Template. The Event Template is deleted and also removed from CPCE.

4.2.3, 6.8.6, 11.1.11, 11.1.13, 11.1.14

Data Analytics

1 Ingest ENSIT messages and display as a link diagram. Entities (with appropriate attributes) and relationships are automatically created and stored in the entity store.

3.2.1, 11.1.29

2 View entities to display pedigree information. The pedigree following pedigree is displayed: source, DTG created, DTG received.

4.1.13, 4.1.14, 4.1.15, 4.1.16

3 View the source product from the entity description. The source product can be selected and displayed from the created entity.

3.2.4

4 Ingest IIR messages and display as a link diagram. Entities (with appropriate attributes) and relationships are automatically created and stored in the entity store.

3.2.1, 11.1.29

5 View entities to display pedigree information. The pedigree following pedigree is displayed: source, DTG created, DTG received.

4.1.13, 4.1.14, 4.1.15, 4.1.16

6 View the source product from the entity description. The source product can be selected and displayed from the created entity.

3.2.4

7 Ingest EOBSREP messages and display as a link diagram.

Entities (with appropriate attributes) and relationships are automatically created and stored in the entity store.

3.2.1, 11.1.29

8 View entities to display pedigree information. The pedigree following pedigree is displayed: source, DTG created, DTG received.

4.1.13, 4.1.14, 4.1.15, 4.1.16

9 View the source product from the entity description. The source product can be selected and displayed from the created entity.

3.2.4

10 Ingest the MinERG excel spreadsheets. Entities (with appropriate attributes) and relationships are automatically created and stored in the entity store. Data is transformed (e.g., Time(Local to 11Zulu), Measurements (Inches to Meters), Distance (Miles to Kilometers), Location (latitude/ longitude to MGRS) and displayed based on the MinERG. Data.

4.2.1, 4.2.2

11 Ingest the Correlation excel spreadsheets. The duplicate entities in the Correlation spreadsheet are combined and the entity history log is updated.

4.4.1, 4.4.2, 4.4.3, 4.4.4

12 For the two Field Artillery Batteries, move one very close (<500m) to the other.

The Correlation should identify these entities as possible duplicates with a high similarity score.

4.4.1, 4.4.2, 4.4.3, 4.4.4

13 For the two Field Artillery Batteries, move one very close (<100m) to the other.

The Correlation should identify these entities as possible duplicates with a higher similarity score.

4.4.1, 4.4.2, 4.4.3, 4.4.4

Threat Model Management and Matching 1 Create and save a new BDE level composition models that includes how each threat organization is structured and equipped. The model should go down to the PLT level. The Model should include Unit, Equipment, Organizations, Individual, and Relationships between Entities.

The composition model is created and saved.

5.1.2, 5.1.3, 5.1.5

2 Create and save a new BN level composition models that includes how each threat organization is structured and equipped. The model should go down to the PLT level. The Model should include Unit, Equipment, Organizations, Individual, and Relationships between Entities.

The composition model is created and saved.

5.1.2, 5.1.3, 5.1.5

3 For the existing BN level composition model, “Save- As” to a new model name and edit the model to change armor units and equipment to mechanized infantry. Save when changes are compete.

The Save-As feature allows a new composition model to be created, updated and saved.

5.1.4

4 Display the composition model and then drag a drop a PLT from one CO to another. Save the model.

The composition model is displayed, updated and saved.

5.1.2, 5.1.3, 5.1.8

5 Edit the first BN level composition model by updating equipment quantities, adding and removing equipment. Save when changes are compete.

The composition model is displayed, updated and saved.

5.1.2, 5.1.3

6 For the existing BDE level composition model, “Save- As” to a new model name and add a BN unit. Save when changes are compete.

The Save-As feature allows a new composition model to be created, updated and saved.

5.1.4

7 Delete the composition model from the previous step.

The composition model is deleted. 5.1.3

8 Create and save a new BDE level disposition threat models that specifies model width and depth illustration, specifying orientation and distance between components within the disposition Threat Model.

The disposition model is created and saved.

5.1.15, 5.1.7

9 Display the BDE level disposition threat model on a map. Change the map scale to the following:

1:25K 1:50K 1:100K 1:250K

The display of the disposition model scales appropriately based on the selected map scale.

5.1.18

10 Create and save a new BN level disposition threat models that specifies model width and depth illustration, specifying orientation and distance between components within the disposition Threat Model.

The disposition model is created and saved.

5.1.15, 5.1.7

11 For the existing BN level disposition model, “Save- As” to a new model name.

The Save-As feature allows a new composition model to be created and saved.

5.1.16

12 Display the disposition model and then drag a drop units to move locations. Save the model.

The disposition model is displayed, updated and saved.

5.1.19

13 Update the disposition model to specify Tactical movement rates. Save when changes are compete.

The disposition model is displayed, updated and saved.

5.1.20

14 For the existing BN level disposition model, “Save- As” to a new model name and then drag a drop units to move locations. Save the model.

The Save-As feature allows a new composition model to be created, updated and saved.

5.1.16

15 Delete the disposition model from the previous step. The disposition model is deleted. 5.1.15 16 Select the threat composition model from step 5 to notify the user when the pattern is matched.

The user is able to activate a composition model for pattern matching.

10.1.1

17 Build a Threat COP (top down) to exactly match the threat composition model from step 5. Pause briefly after each unit is added.

The threat COP is continually built until either complete or the user receives an alert that a pattern has been matched. The alert includes likeness information for the match (e.g., "80% Pattern Matched", "5 Key Pieces of Equipment found in the 40% Match").Record the point when the alert is generated.

10.1.1, 10.1.3

18 De-activate the selected composition model for pattern matching. Activate the composition model from step 3 for pattern matching.

The user is able to activate and de-activate a composition model for pattern matching.

10.1.1, 10.1.3

19 Draw a AOI on the map and designate it as the designated Geospatial Area (Polygon) for composition pattern matching.

The user is able to designate a geospatial are for composition model matching.

10.1.4

20 Build a Threat COP (top down) to exactly match the threat composition model from step 3 outside of the selected Geospatial Area. Pause briefly after each unit is added.

No pattern matching alert is generated.

10.1.1, 10.1.3

21 Activate both composition models for pattern matching.

The user is able to activate multiple composition models for pattern matching.

10.1.1, 10.1.3

22 Move the units from the threat COP in step 20 individually, one by one, into the selected Geospatial Area.

The threat COP is continually built until either complete or the user receives an alert that a pattern has been matched. The alert includes likeness information for the match (e.g., "80% Pattern Matched", "5 Key Pieces of Equipment found in the 40% Match").Record the point when the alert is generated.

10.1.1, 10.1.3

Cyber Hardening 1 Ensure all urls are https and not http. Record any web pages that are http.

11.1.22

2 Copy urls for places in the application past the login page. Log out of the application and then paste the urls directly into the browser.

The user is unable to gain access to the web page without logging in.

11.1.22

CUI // FEDCON 15

Appendix B. Acronyms and Abbreviations AO Authorizing Official API Application Programming Interface ATO Authorization to Operate AWS Amazon Web Services BSIL Booz Allen Hamilton Systems Integration Laboratory CCDC Combat Capabilities Development Command CD Capability Drop CDF Common Data Fabric CDS Cross Domain Solution CRUD Create, Read, Update, Delete CVI Cooperative Vulnerability Identification DAC Data and Analysis Center (CCDC subordinate) DATE Decisive Action Training Environment DCGS-A Distributed Common Ground System – Army DDS Data Dissemination Service DEN Deployable Edge Node DEVOPs Development Operations DIB DCGS Integrated Backbone DO Delivery Order FORSCOM Forces Command IAT Intelligence Analyst Test INSCOM Intelligence and Security Command IS&A Intelligence Systems and Analytics MinERG Minimum Entity Relationship Graph PdM Product Manager PRD Performance Requirements Document PM Program Manager PMO Program Management Office REST Representational State Transfer ROE Rules of Engagement SME Subject Matter Expert SOW Statement of Work TBD To Be Determined TED Tactical Entity Database TH Test Harness TPM Technical Performance Measures TRADOC Training and Doctrine Command TRR Test Readiness Review TSI Tactical Server Infrastructure TT Technical Test USASOC U.S. Army Special Operations Command

1.4 Rules of Engagement

6 Reference Documentation