NetOps as a Service - Mission Focused Analytics
Navy SBIR 2012.3 - Topic N123-159
SPAWAR - Ms. Elizabeth Altmann - [email protected]
Opens: August 27, 2012 - Closes: September 26, 2012

N123-159 TITLE: NetOps as a Service - Mission Focused Analytics

TECHNOLOGY AREAS: Information Systems, Sensors, Battlespace

ACQUISITION PROGRAM: PMW 790, Shore and Expeditionary Integration Program, TSw (ACAT IV)

RESTRICTION ON PERFORMANCE BY FOREIGN CITIZENS (i.e., those holding non-U.S. Passports): This topic is "ITAR Restricted". The information and materials provided pursuant to or resulting from this topic are restricted under the International Traffic in Arms Regulations (ITAR), 22 CFR Parts 120 - 130, which control the export of defense-related material and services, including the export of sensitive technical data. Foreign Citizens may perform work under an award resulting from this topic only if they hold the "Permanent Resident Card", or are designated as "Protected Individuals" as defined by 8 U.S.C. 1324b(a)(3). If a proposal for this topic contains participation by a foreign citizen who is not in one of the above two categories, the proposal will be rejected.

OBJECTIVE: Develop an operational prototype of a NetOps Analytics system that enables both Cyber and Maritime domain operators to proactively assess the impact of NetOps incidents in mission context of Mission.

DESCRIPTION: In today�s information age, access to data (both unstructured and structured), ubiquitous secure information exchange and situational awareness are critical elements to the success of organizations, especially those that support global military operations. The US Navy IT-21 tactical network that supports the warfighter globally is complex and distributed across the globe. Accessing, exposing and securing authoritative sources of data remains a challenge primarily due to the variety of systems that encompass the IT-21 network and complex interconnections between these systems. Fusing and correlating the various NetOps data sources into meaningful trusted information sources to the warfighter in context of a mission is another level of complexity. Success in this effort will require both facets to be executed and integrated seamlessly. Objectively, the goal is to ensure the delivery of accurate, relevant, trusted NetOps information derived from authoritative data sources to the warfighter operating at �the tip of the spear�. Being able to manage large amounts of disparate data geographically dispersed across the globe over many networks, servers and devices is key to this effort.

The following are attributes of the NetOps Analytical system:
� Integrates NetOps SA information into the overall Maritime Situation Awareness (SA) environment.
� Includes displays of information in the NetOps SA environment that are relevant to the unique needs of the Cyber Commander and their warfare needs.
� Stores data at (or near) point of collection.
� Tags collected data at point of collection (to begin the data provenance process).
� Enables data provenance (i.e. the method for data generation, credentialing, transmission and storage based on identity, access and user management).
� Provides for data retrieval through the use of pre-defined or on-demand crafted by *widgets* or users specifications.
� Provides for alerting based on pre-defined criteria to allow operators and analysts to be tipped to activity vice sifting through data via multiple queries.
� Conditions the data to ensure an interoperable query/response process.
� Presents the data to the user for analysis and display via common and shared mapping and/or other visual services (e.g. geographic displays, Topology maps, graphing services).

PHASE I: Identify data and information requirements of maritime and cyber operations in support of respective and representative mission areas. Produce NetOps data matrix and/or indexing capability that identifies the location and meaning of the data in context of a mission area and/or thread related to the STRATCOM Initial Capabilities Document (ICD). Provide a preliminary system design document that clearly describes the complete hardware/software architecture, user interfaces, input/output relationships and maps system functions to attributes. Describe the collection of enabling Analytics technologies in terms of its ability to access, normalize/condition and correlate/fuse the NetOps data sources into mission-relevant information. Use of automated technologies such as machine learning technologies centered around anatomic intelligence to better understand network operation patterns and overall network data ontologies, is highly encouraged. A list and description of enabling technologies and their relationship to the key system functions and attributes should be clearly articulated during this phase. Any assumptions or other system dependencies should also be clearly identified. Demonstrate limited analytics capability using the data identified and collected as an initial prototype.

PHASE II: Mature the prototype developed in Phase I to include potentially classified data (secret or SCI) and demonstrate its capabilities during a representative Fleet experiment to assess military operational utility. The phase II effort should also culminate in a system design document that clearly articulates all aspects of the design with clear traceability to user functions and system attributes. It should also include interface specifications as defined during this phase.

PHASE III: The phase II results will be evaluated and if deemed successful, a phase III may be awarded to continue the integration with government identified systems, testing, limited procurement, and deployment of the technology.

PRIVATE SECTOR COMMERCIAL POTENTIAL/DUAL-USE APPLICATIONS: Large network operations are common throughout commercial industries. Issues of network performance, operational availability, security are intrinsic to these operations. The solutions envisioned here are likely to be generic and applicable to a broad range of large commercial network operations. While there are currently many network situational awareness tools available, the objective of this program is to develop superior secure situational awareness and user efficiency that would benefit any large network operating in a cloud environment.

REFERENCES:
1. P 051535Z AUG 11 COMFLTCYBERCOM FT GEORGE G MEADE MD

2. P 201730Z SEP11 COMPACFLT PEARL HARBOR HI

KEYWORDS: Situational Awareness, Cyberspace, Cloud, SOA, Decision-Making, User Experience, Usability, Mission-Focused

** TOPIC AUTHOR (TPOC) **
DoD Notice:  
Between July 26 and August 26, 2012, you may talk directly with the Topic Authors (TPOC) to ask technical questions about the topics. Their contact information is listed above. For reasons of competitive fairness, direct communication between proposers and topic authors is
not allowed starting August 27, 2012, , when DoD begins accepting proposals for this solicitation.
However, proposers may still submit written questions about solicitation topics through the DoD's SBIR/STTR Interactive Topic Information System (SITIS), in which the questioner and respondent remain anonymous and all questions and answers are posted electronically for general viewing until the solicitation closes. All proposers are advised to monitor SITIS (12.3 Q&A) during the solicitation period for questions and answers, and other significant information, relevant to the SBIR 12.3 topic under which they are proposing.

If you have general questions about DoD SBIR program, please contact the DoD SBIR Help Desk at (866) 724-7457 .

Return