This synopsis is being posted to both the Federal Business Opportunities (FBO) page located at http://www.fbo.gov/ and the Navy Electronic Commerce on Line (NECO) site located at https://www.neco.navy.mil/ While it is understood that FBO is the single point of entry for posting of synopsis and solicitations to the internet, NECO is the alternative in case FBO is unavailable. Please feel free to use either site to access information posted by NSWC Crane. MARKET RESEARCH: The Government is issuing this sources-sought announcement as part of a market survey. Naval Surface Warfare Center, Crane Division located at the Naval Support Activity, Crane, IN is looking for companies with the capabilities to provide anomalous activity detection (AAD) software (AADS) for multisensor persistent surveillance systems. The AADS will need to provide alerting of possible anomalous activities automatically detected in the field of view (FOV) of the non-static persistent surveillance Electro-Optical (EO), Infrared (IR), and/or Short Wave Infrared (SWIR) sensor(s) while the anomaly is still visible. The AADS needs to detect motion and scene change based events within an operator(s) defined inclusion zone, exclusion zone, and/or crossing of a tripwire. Motion based anomalies comprise directly observable activities (e.g., a person running, a vehicle speeding) while scene change anomalies include detecting objects of interest that exist, entered, changed position in, or left a scene (e.g., stacked rocks, small arms/weapons). Many anomalous activities are composite events including both motion and scene-change based events. On the other hand, some activities or objects are of interest without being anomalous (e.g., Be On the Lookout [BOLO] or reading license plates). The persistent surveillance system operator will decide and tailor the criteria of anomalous activity with the AADS. The AADS will need to provide a Software Development Kit (SDK) with a documented Application Program Interface (API) for integration with existing C2ISR Software. The C2ISR Software will provide audible and visual alerts on the operator(s) graphic user interface (GUI) and utilize the C2(s) native slew-to-cue functions to employ other additional persistent surveillance sensors to the area of interest. Submission of information regarding AADS scene-based and/or motion-based features may include but not be limited to the detection of: Improvised Explosive Device (IED) Holes/disturbed earth Change in pattern of life Digging Small arms/weapons Infiltration/enemy set to ambush String wire Stacked rocks or marking objects Running Package left behind BOLO Indirect fire Wires Loitering Entering/leaving exclusion area Vehicle Speed Erratically moving vehicle Lines Change detection at night Appearance of a vehicle Stopped vehicle Read license plate At a minimum the AADS RFI responses should include the following: Summary on the technical principles of how the software/technology functions Rationale and/or tactical advantages of the system Current Technology Readiness Level (TRL) Software architecture and interoperability standards (e.g. SEIWG ICD-101a/b, XML-based, or proprietary) Adherence to MIL-STD-961E, Defense and Program-Unique Specifications Format and Content, 2003 Application Programming Interface (API) that supports full integration with third-party C2 systems Acceptable imagery formats (e.g. MPEG-4, H.264, H.265, MPEG-2 TS, etc.) Use with dynamic sensors (e.g. pan tilt zoom or gimbal) Sensor stabilization needed or mitigation tools Ability of accepting a buffer of raw pixel data Metadata format(s) supported such as MISB 0601.X Ability to accept metadata including platform, sensor, timestamp, geo-rectified center and corner pixels, orientation, zoom, and slant range Time for detection and alert to include minimum sensor dwell time required Probability of detection (PD) False alarm rate and any mitigation tools Central processing unit (CPU) needed Software Development and Operating System Environments supported (e.g. C/C++, Java, Red Hat Enterprise Linux, Windows, etc.) Ability to accept line-in-screen coordinates defining tripwires Ability to accept operator feedback to parameterize alerts according to mover size, movement rate, and direction Ability of operators to provide feedback or filters on alerts to avoid further alerts for a given tracked object while it remains visible in the area of interest Can operators provide feedback or set rules to parameterize scene change detection sensitivity Ability to provide activity alerts via a software call When detections occur are the associated bounding box and alert type returned and supported in the API Ability to detect objects moving within the area of interest while the sensors FOV is unchanged Ability to determine scene change when the cameras FOV changes and comes back to the same location How many simultaneous events are supported Process of removing alerts Minimum and maximum speeds, size, or direction for needed for detection of a target (e.g. personnel or vehicle) Ability to classify a mover as a vehicle, person, or other At the current time, NO FUNDING IS AVAILABLE for contractual efforts. This request for information does not constitute an Invitation for Bids (IFB), a Request for Quote (RFQ), or a Request for Proposal (RFP) and it should not be construed as a commitment of any kind by the Government to issue a formal solicitation or ultimately award a contract. The US Government is in no way liable to pay for or reimburse any companies or entities that respond to this announcement. Any costs incurred by interested companies in response to this announcement will NOT be reimbursed. All interested parties are encouraged to submit company and product literature, white paper, and/or other pertinent information for the Government(s) consideration by 2:00 PM Eastern Standard Time on 10 JUN 2013. Electronic or hard-copy submissions will be reviewed if received by the closing date and time. All information marked as proprietary information will be safeguarded to prevent disclosures to non-government personnel and entities. Electronic submissions regarding this announcement may be directed to both the Contracting Officer, Mr. Jordan Schnarr,
contact@example.gov,
+1 (555) 000-0000 and technical point of contact, Mr. John Whelan,
contact@example.gov. Hardcopy submissions should be mailed to the following: NAVSURFWARCENDIV Crane, ATTN: Mr. Jordan Schnarr, Code CXPP, Bldg 3422, 300 Highway 361, Crane IN 47522-5001. Please refer to announcement number N00164-13-SNB23 in all correspondence and communication. All questions regarding this announcement should be directed in electronic mail to the Contracting Officer, Mr. Jordan Schnarr,
contact@example.gov.
