AIDP - Product Demo Plan.docx

AIDP Detailed Product Demonstration Plan – DRAFT AIDP Product demonstrations will be hands-on, collaborative, and designed to validate the claims made in the white papers. The Government’s evaluation will be based on the following principles:

· Evidence-Based Verification: Demonstrations will serve as the primary means of verifying the solution’s capabilities. Offerors should be prepared to conduct live demonstrations of cloud-hosted and edge-hosted capabilities.

· Hands-On Scenarios: The Government will provide sample data sets, operational scenarios, or specific tasks to be performed during the demonstration. This may include, but is not limited to, ingesting government-furnished data or having government personnel interact directly with the system.

This AIDP Product Demonstration Plan outlines ten areas to be examined at time of demonstration. Each step provides a detailed description of each area for evaluation, associated PACE plan for the associated data, tasks to be executed as well as intended GFI data to be provided. The final product demonstration plan will be provided at time of final CfS along with the associated GFI data. GFI data will vary depending on area to be evaluated. This includes, but not limited to, geospatial data (SHP/KMZ/KML) for evaluating tactical graphics abilities and Office products for handling threat characteristics data. Video clips (https://lib.ikn.army.mil/products/35f10/) summarizing several doctrine-based Army Intelligence tasks will also be provided as GFI for operational context. Additional details are noted below.

Format for AIDP Demo Plan For each area, the following format will be used:

1. A brief description of the high-level capability for demonstration, whether this should be demonstrated at cloud and/or edge, and rough time estimate for task completion.

2. (Optional PACE PLAN – only for tasks that need external data)

· P- This is the primary way the government will provide data or services to support the high-level capability demonstration

· This is the alternative way the government will provide data to see this capability or alternative means to show the capability

3. Specific tasks to execute

4. Data Required / Government Furnished Information (GFI)

Areas for Evaluation

1. Ability to stage Geo data for terrain analysis (on edge) Demonstrate the ability of your system to stage geospatial data to be used in future terrain analysis capabilities. This is an Edge only exercise. Time estimate: 15 minutes

P – The government will provide Geospatial products via OGC services on a GWS-T for the Edge systems A – If vendor cannot connect to the GWS-T, vendor should bring their own map tiles, features, and elevation data to be used for the following...

TASKS

a. Stage geospatial data: Ingest / manipulate map tile data (digital maps, imagery data)

i. The vendor will be evaluated on their ability to ingest geospatial products with an emphasis on the timeliness of ingestion, usability, and support for smooth map interactions across resolutions and scales.

b. Stage geospatial data: Provided feature sets (Hydrology, Lines of Communication, Urban Areas, Airports)

i. The vendor will be evaluated on their ability to ingest geospatial feature data that can be used in follow on terrain analysis capabilities. For example, natural/man-made obstacles should be considered during route/movement projection. Points of interest should be easily convertible into searchable objects in the vendors database.

c. Stage geospatial data: Provided Elevation data (terrain grade)

i. The vendor will be evaluated on their ability to ingest terrain elevation data as a consideration and precursor for movement projection, intervisibility analysis, Key terrain generation, SITTEMP development, etc...

DATA REQUIRED/Government Furnished Information (GFI):

Provide digital maps/imagery stitched in an area that also has the feature and elevation data described above.

2. Ingest and Maintain Threat Models (C & E) Demonstrate the ability of your system to ingest and maintain threat models on both the Cloud and Edge. Time estimate: 15 minutes P- The government will provide the vendors with an office product of threat template (i.e. composition, disposition, and activities of an enemy force). Templates to be created in the cloud instance of their software.

A – There is no alternative way to get this data... Vendors are expected to read a PowerPoint and manually generate the models in the vendors UI.

TASKS

a. Generate Threat Templates in the cloud

i. Vendors will be evaluated on their ability to create threat templates from previously generated unit composition. It is expected that many threat templates can be created from a single unit composition and that they are able to be leveraged in future SITTEMP development. The ingestion, modification and sharing of these templates will be evaluated on how streamlined the process is.

b. Import Threat Templates from the Cloud into the edge system without needing to recreate them.

DATA REQUIRED/Government Furnished Information (GFI):

Provide threat templates: enemy template with an offensive/defensive disposition to meet evaluation criteria

3. Demo CRUD capabilities for map layers containing tactical graphics and share (C&E) Demonstrate the CRUD capabilities on layers containing tactical / warfighting graphics on both the cloud and edge. Enable sharing of these products. Time estimate: 30 minutes P- The government will provide vendors with point/line/polygon details (coordinates/modifiers). The evaluation team expects the vendor on the cloud and the edge to create graphics manually with provided coordinates for point/line/polygon tactical graphics (DP, FLOT, AOs, friendly unit PLI). Additionally, the government will provide point/line/polygon graphics via KML/KMZ/SHP files to ensure that these products can be created programmatically. File formats include, but not limited to, graphics data (SHP, KML, KMZ file types) for tactical graphics evaluation, MS Office products (PPT, Excel) for Threat Characteristics and entities data in JSON files for:

TASKS

a. CRUD with tactical graphics in cloud/edge

i. Vendors will be evaluated on their adherence to MIL-STD 2525 (C and greater) for tactical graphic symbology and modifier visualization. The creation of complex multipoint tactical graphics should be accessible and easily managed across overlays.

b. CRUD with warfighting symbology in cloud/edge

i. Vendors will be evaluated on their adherence to MIL-STD 2525 (C and greater) for warfighter symbology and modifier visualization. Validation for enumerated fields such as Affiliation, Unit Organization Type and Equipment Type should be supported with general quality of life considerations creating complex force dispositions (copy and paste, drag and drop, templating, etc...)

c. Programmatically share layers between nodes (e.g cloud, edge)

i. Vendors will be evaluated on their ability to share layers between their edge and node systems. Conflict management rules will be evaluated when multiple users across cloud and edge systems are actively modifying the same shared overlays.

d. Manually export/import layers between nodes (e.g cloud, edge) to demonstrate no data loss.

i. Vendors will be evaluated on their ability to export and import overlays in an offline manner without data loss.

DATA REQUIRED/Government Furnished Information (GFI):

Provide point/line/polygon details (coordinates/modifiers) for import.

4. Enable CRUD on and share the OOB Demonstrate CRUD capabilities on, and share enemy order of battle. Time estimate: 15 minutes P- Ingest ODIN order of battle via programmatic API pull A - Ingest ODIN order of battle via flat file excel import (format provided ahead of time) C – Manually create order of battle during the event from image / ppt of ODIN link diagram

TASKS

a. Demonstrate OOB pipeline / flat file import

i. Vendors will be evaluated on their ability to import order of battle information. The accessibility of this process, and the machine-assisted field mappings from the OOB to entity attributes will be considered.

b. Display the OOB

i. Vendors will be evaluated on their ability to display OOB in link-diagram view with MIL-STD-2525C (and future) specifications.

c. Demonstrate modifications to both nodes and links in the OOB

i. Vendors will be evaluated on how easily changing relationship types and directionality between nodes in the OOB is.

d. Ability to collapse, rearrange nodes, copy sections, create new OOBs etc...

e. Ability to programmatically/manually share the OOB to between nodes, e.g. cloud and edge.

DATA REQUIRED/Government Furnished Information (GFI):

Provide sample enemy order of battle and maneuver BDE.

5. Battle Tracking Demonstrate BDA workflows and its relations to the enemy OOB. Time estimate: 15 minutes Data needed: Data already ingested in step 4 Tasks

a. Ensure correlation rules or conflict management rules exist

i. Vendors will be asked to display any correlation / conflict management rules that could trigger modifications to existing objects when new data is ingested in the system.

b. Vendor receives a will tactical observation of equipment previously identified in the Order of Battle

i. Vendors will be evaluated on the machine-assisted processes that handle the ingestion of this data and its downstream effects on the existing corpus of data.

c. Visualization of BDA attributes.

i. Vendors will be evaluated on their visualization of battle damage assessments (i.e. slant charts / kill-charts / symbology health bars etc...). User adjustable weighted BDA fields will also be taken into consideration.

d. Demonstrate the ability to relate tactical observations, documents, events, etc... back to the OOB for machine assisted battle tracking.

i. Vendors will be evaluated on their ability to combine BDA related attributes from tactical observations, documents, events into an existing Order of Battle. This should be done without incurring data loss. Vendors should be able to provide strength and combat effectiveness scoring with the ability to modify the means by which they are calculated.

DATA REQUIRED/Government Furnished Information (GFI): Ingested in previous step.

6. Ingest Hydra Entities Demonstrate the ability to ingest Intelligence entities (Units, Equipment, Facilities, Events). Tested at both the Edge and Cloud. Time estimate: 45 minutes P- Provide the edge system a connection to the Hydra X server locally running in the integration lab.

A- Provide JSON files of hydra entities to be loaded in the case that the API cannot be used (Cloud instance can’t connect) or if the vendor cannot programmatically request objects.

TASKS

a. Present the integration pipeline leveraged to connect to the Hydra API data source

i. Vendors will be evaluated on their ability to create new data ingestion pipelines with custom data mappings. User experience during this process is a key consideration (low-code / no-code pipelines? Metrics dashboards? Logging / Troubleshooting considerations?)

b. Demonstrate the capability to query for Hydra objects utilizing DocumentDB operators.

i. Vendors will be evaluated on the complexity of the queries, adhering to the DocumentDB operator’s list, that their system is able to support.

c. Demonstrate the CRUD ability on Hydra objects.

i. Vendors will be evaluated on their UX workflow for creating, retrieving, updating, and deleting intelligence objects in an external Hydra server (Utilizing Auth2.0 client IDs and secrets) DATA REQUIRED/Government Furnished Information (GFI):

Provide Hydra API specification and sample JSON files and JSON flat files of sample units, equipment, facilities and events.

7. Demo 3rd party APIs/SDKs Demonstrate your system’s 3rd Party APIs/SDK capabilities. Vendor determined environment (cloud/edge). Time estimate: 45 minutes

TASKS

a. Demonstrate the ability to query your system for entities/graphics.

i. The vendor will be evaluated by their ability to process entities/graphics queries, their query response times and their data content accuracy at the attribute level

b. Demonstrate the ability to accept 3rd party CRUD requests for populating data

i. The vendor will be evaluated by their ability to accept 3rd party CRUD requests and the ability to validate it through their system UI

c. Demonstrate the ability to respond to complex query operators (or, and, like, geo-within etc...)

i. The vendor will be evaluated by their ability to respond to complex query operators and on their supported list of operators and attributes that can be queried

d. Demonstrate the ability to deploy the evaluation team’s simple “Hello World” application onto your system and be utilized.

i. The vendor will be evaluated by their ability to deploy a 3rd party application. This evaluation will consider the system services that the 3rd party app can leverage, the availability of any vendor-provided style guides, and any limitations that the 3rd party app may have when accessing system-housed mission data.

DATA REQUIRED/Government Furnished Information (GFI):

After receiving vendor SDK, Government will provide a sample application (hello world) to be deployed in vendor system. This requires vendor developer documentation at least 2 weeks prior to their scheduled demonstration to run 3rd party scripts (not deployed in their ecosystem).

8. Demo "What-if" analysis workspace for intel product creation Demonstrate the system’s ability to create intel products in a “what-if” analysis workspace that is unaffected by the continual changes in global persistent datastore. The user should be able to perform modifications and analysis in this staging environment without affecting the original data and only be affected by updates to the original objects by exception. Time estimate: 30 minutes

TASKS

a. Geospatial Intelligence Products. Place entities and tactical graphics on a geospatial layer that is logically separate from the database objects.

i. The vendor will be evaluated by their ability to construct a separate workspace for a geospatial layer. This layer should be able to be initially populated with objects from the global persistent datastore. Areas to be explored include the manner with which geospatial layers can be shared and the vendor’s ability to manage conflict resolution.

b. Link Diagram Products. Place entities on a link diagram that is logically separate from the persistent database.

i. Assessing vendor’s approach to construct a custom link diagram layer, for what-if analysis, using entities from the global persistent datastore as a starting point where any modifications to objects are kept local and synchronization to main datastore is intentional. Other areas to explore include the ability to share internally/externally and approach to manage conflict resolution.

DATA REQUIRED/Government Furnished Information (GFI): N/A

9. Terrain Analysis: movement projection and route planning Demonstrate the following terrain analysis capabilities: Movement projection, Route planning, Intervisibility Analysis, SITTEMP Laydown. Time estimate: 30 Minutes

TASKS

a. Confirm the vendor has all the components necessary to automatically perform terrain analysis.

i. Areas for considerations include Elevation Data, Natural/Man-made obstacles, passable features, Unit’s rates of march, equipment parametric and sensor characteristics.

b. At the start or end of a potential route, select a piece of equipment and identify all potential locations that it could travel in a period of time (i.e. 2 hours, 1 day, vendor determined)

i. Vendor will be evaluated on their ability to calculate and visualize a movement projection overlay. Calculations should consider the effects of terrain on the selected equipment and display those effects with visual elements such as heatmaps and isochrones.

c. Considering a start time/location and end location, conduct automated route analysis that determines potential routes equipment can take to arrive at its end point.

i. Vendor will be evaluated on their ability to automate the discovery of potential routes / courses of action that a specific enemy force could adopt. These calculations should be easily modifiable as updates to parameters (e.g. on- ad speeds, off-road speeds, gradeability) occur.

d. At the end location conduct intervisibility analysis and provide viewshed overlays.

i. Vendor will be evaluated on the types of parameters they are able to consider for intervisibility analysis (horizontal/vertical viewing angles, target/sensor height, bearing/pitch) as well as the visualization techniques for overlaying this information in an intuitive manner.

e. At the end location, create an enemy defense threat template and plot it on the map

i. The vendor will be evaluated on their ability to develop a SITTEMP with consideration for terrain data in the operational environment. Key components such terrain elevation and obstacles will be expected to have effects on the threat's doctrinal formation DATA REQUIRED/Government Furnished Information (GFI):

Provide Elevation / Obstacles / passable feature as well as Units Rate of March / Equipment Parametric / Sensor Characteristics.

10. Demo Chat, multi-user editing of products Demonstrate the following collaboration services: Chat, Product repository/multi-user editing of products (documents, maps, link analysis, table etc...). Time estimate: 15 Minutes

TASKS

a. Demonstrate Chat Capabilities

i. The vendor will be evaluated on how well their collaboration capabilities are integrated within their solution. This includes fundamental features such as support for both direct messaging and group chats. The assessment will also cover the ability to integrate and link data products within the chat interface and overall user experience, examining usability features like @mentions commonly available in other Chat services.

b. Demonstrate Product repository Capabilities

i. Evaluation will include assessing vendor’s ability to provide user the workspace for storing office products, and the ability to organize intelligence work products (maps, link diagrams, matrixes) in support of the workflow. Account management and version control will also be discussed.

DATA REQUIRED/Government Furnished Information (GFI): N/A

11. Vendor Selected Capability Demo Opportunity to provide the evaluation team with a demonstration of any vendor capability that falls within scope of Call For Solutions paragraph 4. Time: 30 Minutes

Appendix A: Product Demo Plan Acronyms

AIDP - Army Intelligence Data Platform

AO – Area of Operations

API – Application Programming Interface

BDA – Battle Damage Assessment

BDE – Brigade

CfS – Call for Solutions

CRUD - Create/Read/Update/Delete

DocumentDB – document-like format for storing data

DP – Decision Point

Edge – Edge Device at boundary of network that processes data locally

FLOT – Forward Line of Troops

GFI – Government Furnished Information

GWS-T - Geospatial-Intelligence Workstation – Tactical

HYDRA - Set of Government Managed REST (Representational State Transfer) APIs that support system-to-system interoperability

JSON – JavaScript Object Notation

MIL-STD-2525 – NATO Joint Military Symbology

OAuth2.0 – Authentication and Authorization protocol

ODIN – Operational Environment Data Integration Network

OGC – Open Geospatial Consortium

OOB – Order of Battle

PACE – Primary, Alternate, Contingency, and Emergency

PLI – Position Location Information

SDK – Software Development Kit

SHP/KMZ/KML – ESRI vector data format / Keyhole Markup Zip / Keyhole Markup Language

SITTEMP – Situational Template – Army graphical visual tool

UX – User Experience

CUI