Attachment 0005 - Competitive Range Event Plan_17 September 2021.pdf

UNCLASSIFIED // FOR OFFICIAL USE ONLY

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

16 September 2021

Competitive Range Event Plan For

All-Source 2

PRODUCED BY

Product Manager Data and Analytics

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.

PM Intelligence Systems & Analytics

Version 1.1

Competitive Range Event Plan for the IS&A Intel Apps, All-Source 2

This page is intentionally blank.

Signature Page

Approved by:

Mr. Robert Czajkowski Chief Engineer for Intel Apps Project Manager, Intelligence Systems and Analytics

1 Purpose

1.1 Competitive Range Details

1.2 Location

1.3 Schedule

1.4 Rules of Engagement

2 CR Architecture/Environment

2.1 Client Computers

2.2 Cloud Environment

2.3 Architecture

2.4 Event Rooms

3 Competitive Range Procedures

3.1 Event Conduct Roles

3.2 General Conduct

4 Competitive Range Threads

4.1 Initialization (Day #1)

4.2 Execution of CR Threads (Day #1)

5 Data Sets

5.1 Data

6 Data Collection

6.1 Screen Capture

7 Reference Documentation

UNCLASSIFIED // FOR OFFICIAL USE ONLY 15

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

The following appendices are enclosed with this document:

• Appendix A. Execution Threads

• Appendix B. PRD Mappings

• Appendix C. Acronyms and Abbreviations

1.1 Competitive Range Details

The purpose of Competitive Range (CR) is for the Government to verify the All-Source 2 software meets core capabilities within the Performance Requirements Document (PRD). During the CR, Contractor personnel, with assistance by the Government, will conduct the CR threads. The CR execution will be conducted in accordance with the Threads contained in the CR Event Plan for All-Source 2. Attributes specific to CR:

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

Government, in conjunction with (2) 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, OGC Services (WMS, WFS, WCS)

Data Reduction: XML output; Video capture; Manual observations

All Source 2 Operators: Contractors

Event Moderation: Conducted by the Government

Data Collection: Conducted by the Government

Technical Criteria:

1. (Technical Criteria #1) The All Source 2 Application must demonstrate Interoperability with DCGS-A v3.2.5 via the ingest and extraction of a Virtual Cabinet (VCAB) file

UNCLASSIFIED // FOR OFFICIAL USE ONLY 13

2. (Technical Criteria #2) 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)

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

4. (Technical Criteria #4) The All Source 2 Application must demonstrate the ability to leverage and display the SSGF data provided via Geospatial services (e.g., WMS, WFS, and WCS).

1.2 Location

All-Source 2 Competitive Range 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 Hour

The Government plans for the Competitive Range is to span approximately four (4) hours with the following distinct events. The Government plans for CR 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 CR Step. Prior to the CR execution, the Government will provide access to AWS and BSIL related systems to perform integration and configuration.

Table 1. Schedule by Day

Week Planned Times Item Description

Day #1

(Hours 0-1) Configuration and Checkout

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

(Hours 1-3) Thread Execution

The execution of the Competitive Range Threads.

(Hours 3-4) 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 Competitive Range:

During Day #1:

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

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

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

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

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

2 CR 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 Competitive Range. 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 Competitive Range. Figure 2 depicts the staffing/location profile during the event execution.

Figure 1. Competitive Range High-Level Architecture

Figure 2 Competitive Range 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 Competitive Range 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. Competitive Range Roles

Role Description Planned Physical

Location during Competitive Range

Government Moderator

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

On-site

Contractor Personnel

The Operator 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

Contractor 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 CR 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 CR threads and steps contained in Appendix A. The Government will not deviate from the CR 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 Competitive Range Threads Appendix A contains the CR Thread Steps.

4.1 Initialization (Day #1)

The Government has included "Initialization" steps to be executed with the Contractor and the PM IS&A engineers during the first hour of execution.

4.1.1 00 CR Thread 1 – Initialization Pre-Condition: The Contractor system has no pre-processed data prior to CR execution. The Contractor will be provided documentation by the Government which outlines the Initialization process in finer detail; including specific IP addresses, ports, and other pertinent setup information.

Description: Contractors will work with Government-appointed personnel to install and configure their All-Source 2 software and also ensure connections to all external architecture needed to demonstrate the capabilities found in the Competitive Range.

4.2 Execution of CR Threads (Day #1)

The Contractor will execute the following Thread Steps during Day #1 of CR.

4.2.1 01 Data Centric Thread Pre-Condition: Contractor system has no pre-processed data and the interface to bring in data which was created in the Initialization thread. Erroneous or anomalous data may be embedded within the ingest data in order to demonstrate error resolution within the Contractor system. Contractor has completed setup of all equipment necessary to properly demonstrate all tasks.

Description: All-Source 2 must be able to ingest (Flat Files *.txt) a variety of USMTF messages in order to create a shared understanding with regard to thread in the operational environment. Information integrity is of the utmost importance across the breadth of all received data.

4.2.2 02 Imagery and Geospatial Centric Thread Pre-Condition: Contractor system has no pre-processed data. Contractor has completed setup of all equipment necessary to properly demonstrate all tasks.

Description: Accurate visualization is amongst the most important features required of a system in order to generate a Common Intelligence Picture. Layer data, entity data, and tactical graphics must all be rendered without error in order to conduct the projections and planning activities needed for day to day operations within a given AO.

As such, Thread 02 will demonstrate the successful visualization of a variety of Imagery/Geospatial data, and then conduct a series of projections in order to showcase the system’s ability to account for factors like terrain when planning the possible positioning/movement of hostile forces.

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

• Entities, relationships, and attributes

• Messages

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

5.1 Data

As part of the Competitive Range 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

As noted in section 5.1, if data is provided in static files, they will be made available via access to a common file Window-based file share.

6 Data Collection The Government may collect the following types of data during the Competitive Range:

• 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 Competitive Range 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.

6.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.

6.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

7 Reference Documentation

1. ENSIT.UF.pdf

2. IIR.UF.pdf

3. EOBSREP.UF.pdf

4. DCGSA-REST-SUM-TEDRestURLGuide.docx

5. TED REST Documentation Final.docx

Appendix A. Competitive Range Threads Refer to separate attachment for the Government’s update to Appendix A

Data Centric Thread Step # Thread Steps Expected Results PRD

Mapping

Ingest government-stipulated semi-structured data (IIR, ENSIT, EOBSREP)

USMTF Messages will be delivered via Shared Drive (Flat Files). Content Extraction and Normalization should be conducted without error.

Conduct a query for entities (Data to be Provided at the Event)

Query should return results indicating successful content extraction and normalization of the entities reported on in the USMTF Messages.

3 Display all extracted data for entities (Data to be Provided at the Event). Display includes the map, link analysis tool and tabular/table form.

Data should be consistent with internals of the USMTF Messages and Normalize correctly

4 Ingest Structured data (VCAB) containing Entities, Attributes and Relationships

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

5 Display the entity data extracted from the ingested VCAB. Display includes the map, link analysis tool and tabular/table form

Data should be visible and consistent across all three viewing methods.

6 Export all data in an .xml format for post-analysis

Export should occur without significant delay or error.

Imagery and Geospatial Centric 1 Ingest and display all government-stipulated map layer data via the provided

WMS

Ingest should be validated as

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

Ingest should be validated as

3 Ingest and display all Elevation data (DTED) via the provided WCS

Ingest should be validated as

4 Select unit (Data to be Provided at the Event) and conduct an Omni-directional movement projection within (Data to be Provided at the Event) Hours.

Unit movement should be consistent with time interval and provided COO data set.

Conduct a route analysis (Minimal 3 Routes), leveraging the provided Combined Obstacle Overlay (COO) data provided by the Government of Equipment type (Data to be Provided at the Event), Echelon Width (Data to be Provided at the Event) and End/Start Point (Data to be Provided at the Event)

The system should generate three separate routes, accounting for obstacles delivered in the COO data set.

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

7 Reference Documentation