Attachment_2_-_ASAE_FRD.pdf

H92222-15-R-0004, Attachment 2

FUNCTIONAL REQUIREMENTS DOCUMENT

FOR

DISTRIBUTED COMMON GROUND/SURFACE SYSTEM

SPECIAL OPERATIONS FORCES

ALL-SOURCE ANALYTICAL ENVIRONMENT

1.0 Scope

The Distributed Common Ground/Surface System for Special Operations Forces (DCGS-SOF) All-Source Analytical Environment

(ASAE) Functional Requirements Document (FRD) articulates Special Operations Forces (SOF) analyst needs. Each requirement listed herein maps directly back to one or more requirements found in DCGS-SOF program Capability Description Documents

(CDDs) or Capability Production Documents (CPDs). The requirements in this document apply to the ASAE software tool itself and the ability of the ASAE software tool to interface with DCGS-SOF back-end services, User Interface (UI), and data. Development and/or modification of back-end services is beyond the scope of this effort. Instead, the ASAE software tool must support capabilities offered by those services as outlined in the DCGS-SOF UI Design Documentation and the DCGS-SOF Data Layer Design

Documentation.

1.1 Document Overview

This FRD is structured in the following manner:

1. Key Performance Parameters: Mandatory requirements for the ASAE

2. Data Integration: Requirements related to the use of data

3. Search and Discovery: Requirements that relate to tools and technologies that enable the user to submit search parameters and receive results in various formats

4. Data Analysis and Visualization: Requirements that relate the user interface and interactions to the ASAE capabilities

5. Advanced Analytics: Requirements related to enhancing machine analysis

6. Knowledge Management: Requirements that relate to and enable the access and management of data and information

7. Enterprise-Wide Collaboration: Requirements related to users communicating and sharing information

8. Interoperability and Scalability: Requirements related to the ASAE ability to interact with other DCGS-SOF capabilities and adapt to future system growth

9. Security: Requirements related to obtaining certification and accreditation to install and operate the software tool on SOF networks

10. Human Machine Interface (HMI): Requirements related to human interactions with the system

2.0 Requirements

Each of the derived requirements is listed by functional area in the following tables.

Req.

Key Performance Parameters Description

Key Performance Parameters

K1

Link Analysis – The ASAE software tool shall enable identification and visualization of disparate intelligence data enabling analysts in discovering and analyzing relationships (connections) between entities such as people, places, things, and events.

K2

Entity Resolution – The ASAE software tool shall be capable of extracting entities from data sources, identify people (formal names and pronouns), places, things, events, time, locations, and translate geographically associated data into coordinates.

K3

Fusion – The ASAE software tool shall have fusion capabilities to provide intelligence support throughout the full spectrum of operations to support force generation, situational understanding, targeting, and information superiority.

K4

DCGS-SOF Data and Pre-Processing Pipeline – The ASAE software tool shall integrate with the existing

DCGS-SOF Data Pre-Processing Pipeline utilizing the appropriate APIs. The Contractor shall not duplicate existing datasets and shall access and utilize all data via the DCGS-SOF Preprocessing Data Pipeline. All data

(accessed, modified, derived, manipulated, etc.) shall remain stored in the SOF data layer only.

K5 ASAE Usability – The ASAE software tool shall be highly usable as defined by the Industry Standard Usability

Rating (usability.gov).

K6

DCGS-SOF User Interface (UI) Integration - The Contractor shall develop the ASAE software tool to integrate with the latest version of the DCGS-SOF UI utilizing the appropriate APIs. The ASAE software tool shall assimilate into the existing DCGS-SOF UI environment such that the tool deploys within the DCGS-SOF environment and all information it visualizes is integrated and embedded in the main UI workspace. The

Contractor’s solution will utilize DCGS-SOF UI as the foundation to allow users to easily access, organize, and arrange all on-line capabilities from within a web browser.

Requirement Description

1.0 Data Integration

1.1 Extract, transform, and process data

1.2 Create metadata such as source, creator, creation date, modifier, modification date, etc. for any products

1.3 Exploit and interoperate with pre-tagged and enriched data sets

1.4 Fuse various types and formats of data such as, but not limited to; FMV and imagery media, reference data, entity databases, documents, and emails.

1.5 Utilize raw intelligence products (MASINT, GEOINT, IMINT, SIGINT, HUMINT, OSINT)

1.6 Utilize external data from sources that cannot be directly ingested

1.7 Provide different types of utilization mechanisms – static; on-demand; complete and/or partial; updated (e.g., external data set has changed)

1.8 Provide functionality for “real-time” streaming data (e.g., data that analytics would be applied to, before storing in a repository)

1.9 Support for 3rd party developers & integrators – open and documented API(s); computer languages supported

(e.g., Java, JSON, C++); Scripting Tools

1.10 Support for common interchange formats (e.g., OGC KML)

1.11 Implement dynamic data models and ontologies

1.12 Provide for data access via open API(s)

1.13 Provide support for Web Service Interfaces

1.14 Provide support for various Replication Topologies such as, but not limited to; hub-spoke & peer-peer

2.0 Search and Discovery

2.1 Provide search and discovery mechanisms through the use of published DCGS-SOF APIs

2.2 Provide real-time quick search capability

2.3 Provide for searches such as: fuzzy matching, strings, wildcard searches, term modifiers, range searches, Boolean logic and operators, logical operators, comparative operators, grouping, geospatial searches, temporal searches

2.4 Provide tips, alerts, notifications, and feeds

2.5 Provide persistent and metadata searches

2.6 Provide ability to save and share search profiles

2.7 Provide ability to filter searches

2.8 Provide ability to conduct path searches

2.9 Provide ability to conduct document searches

2.10 Provide ability to conduct federated searches

2.11 Enable single or multiple search criteria

2.12 Provide a preview of search results received from the SOF Data Layer

3.0 Data Analysis & Visualization

3.1 Provide capability to enable algorithmic analysis

3.2 Provide social network analysis capability

Requirement Description

3.3 Provide link analysis capability

3.4 Provide behavioral analysis capability

3.5 Provide pattern matching and analysis capability

3.6 Leverage existing elevation mapping capability

3.7 Provide text analysis capability

3.8 Provide temporal analysis capability

3.9 Provide density analysis capability

3.10 Leverage existing heatmap visualization capability

3.11 Provide geospatial analysis capability

3.12 Provide statistical analysis capability

3.13 Leverage existing basic graphing functions such as but not limited to; (plots, bar charts, column charts, pie charts, etc.)

3.14 Provide social media analysis capability

3.15 Provide Multi-iterative analysis capability

3.16 Provide enhanced relationship discovery capability

3.17 Provide ability to annotate products

3.18 Provide visualization of information such as geo-spatially, temporally, 3-D, Business Intelligence (BI) – charts/graphs, dashboards

3.19 Provide for “drop-and-drag” capability and sharing of information across applications

3.20 Provide data analysis & visualization capability for “desktop”-based applications

3.21 Provide data analysis & visualization capability for web-based applications

3.22 Provide data analysis & visualization capability for “native” mobile-device applications (e.g., tablet and/or smartphone apps based on Blackberry visualization functions)

3.23 Provide support for 3rd party developers & integrators – open and documented API(s); computer languages supported (e.g., Java, JSON, C++); Scripting Tools

3.24 Provide Multi-language support and machine translation capability

3.25 Perform automated entity resolution and disambiguation from data pipeline products

4.0 Advanced Analytics

4.1 Provide the ability to support searching of all size data sets and repositories up to and including 100,000,000 records.

4.2 Provide documentation/API(s)/development tools to support 3rd party developers & integrators deploying additional analytic capabilities

4.3 Provide computer-assisted, human-driven algorithms which enhance machine analysis of large stores of data in order to allow users to meaningfully draw conclusions about the data at their disposal

5.0 Knowledge Management

5.1 Provide a mechanism that will track intelligence history across enterprise nodes

5.2 Provide a capability to allow users to understand how data objects, properties, relationships, products have been altered, edited, modified, annotated, or enhanced over time

5.3 Provide data cleansing tools to include but not limited to; validators, parsers, and makers, data/entity resolution rules, and index parameters

Requirement Description

5.4 Provide a capability to allow for the management of discoveries and insights and to enable new and future users to understand the problem set quickly

5.5 Provide a capability to allow analysts to easily build off of prior analysis

5.6 Provide verifiable audit logs and system activity tracking

5.7 Enable comprehensive metadata tagging of products created

5.8 Provide a capability to enable leadership with the ability to understand and determine the sourcing of information

5.9 Provide an analytic repository to allow users to re-create their thought process and analysis methods, test out hypotheses, and explore alternate scenarios

5.10

Provide a capability to generate finished intelligence products such as but not limited to; (e.g. DISUM, INTSUM, Baseball Cards, etc.) Any visualization product produced by the tool shall be easily incorporated into the finished intelligence product.

5.11 Provide a capability to support “state save”, i.e., the analyst can save the current state of an investigation, and return to that state at a later time.

5.12 Provide support for an editable/extensible ontology

6.0 Enterprise-Wide Collaboration

6.1 Provide a capability to allow for version control of products

6.2 Provide the capability to create a private workspace for analysts to communicate and collaborate in prior to publishing to the larger enterprise

6.3 Provide a capability for users to publish analyses, conclusions, and annotations to others across the enterprise

6.4 Provide a capability to allow sharing of analyses and finished products with other users with the ability to redact information based on user’s permissions

6.5 Provide a capability for the automatic generation of presentations

6.6 Provide a capability for the automatic generation of reports and provide customizable templates

6.7 Provide a dashboard capability with customizable fields, charts, and tabulations

6.8

Provide a capability for users to manage their work products with an integrated process that allows for special folders, notes, associations, and attachments, customizable forms, and which allows users to track, review, and approve work items as work products are built

6.9 Provide a capability for sharing of information and collaboration across users (e.g., sharing data, workspaces, charts, investigations)

6.10

Provide support for data provenance. At a minimum, provenancing will associate with each document, the metadata containing a history of all modifications to include time/date stamp, identification of analyst and analyst organization, and content of modification. The document metadata will also provide support for reliability measures such as competence, veracity, objectivity, and observational sensitivity.

6.11 Provide a capability for workflows, to include workflow automation as well as document status marking (e.g.

Draft, Reviewed, Approved, etc.)

7.0 Interoperability and Scalability

7.1 Provide an open and flexible architecture in order to seamlessly interoperate with the DCGS-SOF backend architecture and XML pipeline.

7.2 Provide a capability for the utilization and export of various files types to include but not limited to: PPT, HTML, XLS, ANB, Palantir, Word, KML, XML

7.3 Provide a capability to allow for the discovery utilization, and exposure of data through the DIB and the SOF Data

Layer

7.4 Leverage any existing capability for cross domain data sharing

7.5 Leverage any existing capability for partner nation data sharing

Requirement Description

7.6 Provide a capability for data sharing and information collaboration across the enterprise

7.7 Provide a capability to scale to mobile devices, disconnected or low bandwidth environments

7.8 Provide a capability to scale to accommodate increasingly large data sets

7.9 Provide a capability to implement a full spectrum of plug-ins from helpers to entire applications

7.10 Provide a capability to ensure extensibility, allowing for the addition of applications, helpers, servers, and ontology elements on top of the existing capability suite

7.11 Comply with MIL-STD-2525 iconography

7.12 Provide a capability to support disconnected intermittent limited bandwidth (DIL) users (local data sets, data re-synchronization, etc.)

7.13 Provide the capability to interoperate with SOCOM Collections Management tools.

7.14 Provide the capability for 3rd party developers & integrators – integrate additional applications within the DCGS-

SOF architecture

8.0 Security

8.1 Comply with all relevant DISA STIG and SOF Group Policy requirements, as well as Information Assurance (IA) performance, certification, and accreditation requirements

8.2 Utilize existing role-based access; Allow users to see the subset of information they have permission based on clearance level, system defined group memberships, or compartments

8.3 Provide a capability to enable secure collaboration and information sharing

8.4 Provide a function which integrates with the DCGS-SOF back-end, to allow for an audit trail to determine what data was accessed, where, when, and by whom as well as how the data has changed over time.

8.5 Utilize any existing capability for “data-at-rest” encryption

8.6 Utilize any existing capability for “data-in-transit” encryption

8.7

Provide a capability for “Security tagging” of all data exported and utilized to include metadata indicating the security classification of the data. The labelling will be CAPCO compliant, and compliant with the IC's "XML

Data Encoding Specification for Information Security Marking Metadata

8.8 Utilize any existing capability to implement Attribute-Based-Access-Control (ABAC)

8.9 Provide a capability for enforcing Access & Privacy Control Policies

9.0 HMI

9.1 Ensure that the UI is consistent with Microsoft products (mouse actions, function keys, shortcuts, iconography, message boxes, etc.)

9.2 Provide a capability for Multi-level “undo”; The user shall be able to undo at least 10 previous actions

9.3 Provide a capability for Audible as well as visual alerts

9.4 Provide a capability for Multi-monitor support

9.5 Provide a capability for Moveable/Detachable/Customizable menu ribbons

9.6 Provide a capability for User customizable displays

9.7 Provide a capability for Adjustable fonts (size, style, color)

9.8 Provide a capability for “Macro” capability, i.e., repetitive actions can be stored and replayed by the user

9.9 Provide a capability for Context Sensitive Help