17Q80105_SOW.pdf
PDF 30 KB Posted
- Attached to
- Twelve (12) months of Satellite AIS Data coverage Federal contract opportunity
- Solicitation number
- DTRT5717Q80105
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| DTRT5717Q80105a_Instructions.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Request for Quotation (RFQ) No. DTRT5717Q80105 Procurement Request No. V3321077
Statement of Work
1. BACKGROUND
The sharing of unclassified maritime information is a fundamental enabler to multiple Department of Defense (DoD) missions, and both the Naval Component Commands (NCC) and Numbered Fleet Commands (NFC) have a requirement for an unclassified information sharing capability accessible by mission partners. In 2012, the Office of the DoD Executive Agent for Maritime Domain Awareness (EAMDA) was charged with defining unclassified Maritime Domain Awareness (MDA) requirements and capabilities, and for locating a system that conducted analytics and generated/shared alerts based upon predefined and user-customizable rules. In 2013, the US Fleet Forces Command (COMUSFLTFORCOM) articulated a similar requirement concerning the need to develop both near and long-term solutions for an unclassified MDA capability.
As a result, a “MDA Capabilities Requirements Working Group” was created in order to codify MDA unclassified capability requirements, which led to new requirements being mandated by the Commander, US Fleet Forces Command to N2/N6. A Fleet requirement for enterprise access to maritime data, automated analytics and information sharing capabilities to support operational level MDA in an unclassified/non-PKI environment was henceforth defined.
In 2015, a revision to the Office of the Chief of Naval Operations (OPNAV) Intelligence (N2) and Communications Networks (N6) Core Baseline (CB) and Mission Builds (MB) was released to establish the approved Maritime Operation Center (MOC) CB/MB, and the previously used trial system was deemed to be inadequate as a long-term solution.
OPNAV N2N6 was tasked with identifying and funding a program to provide a long-term solution for the Fleet-wide requirement, turning to the Volpe Center-developed and hosted—US Naval Forces Africa (NAVAF) funded— MDA information web tool, SeaVision.
SeaVision was originally created to help countries on the western coast of Africa improve vessel traffic management and navigation safety, increase maritime situational awareness and security, reduce illegal fishing, illicit trading, human smuggling, and piracy, among many other MDA efforts. The AIS data that is presently utilized (and is required for future consumption) is produced by a constellation of satellites operated by the Orbcomm Satellite Data Communications Company (ORBCOMM). The satellite AIS data that is produced by ORBCOMM has been ingested and processed by the Volpe Center’s Situational Awareness and Logistics Division (V332) since SeaVision’s inception, enabling SeaVision development and testing, as well as providing sufficient data coverage, reporting and access to SeaVision and its vast and ever-growing user community. In previous years, OPNAV N2N6 tasked the Space and Naval Warfare Systems Command (SPAWAR) Systems Center Pacific (SSC PAC) with procuring and renewing the annual ORBCOMM satellite AIS data contract, for use in SeaVision.
In 2015, OPNAV N2N6 sponsored SeaVision as the long-term solution to the Fleet-wide requirement, selecting SeaVision to serve as the Navy-wide capability implemented regionally to provide the ability to operate in a low-bandwidth and unclassified PKI/non- PKI environment. This new sponsorship and project focus resulted in the addition of two new technical teams onto the project, establishing a development team consisting of the Volpe Center, the Data Engineering Sciences Center (DESC), and SPAWAR’s SSC PAC. Additionally, SeaVision was tasked with evolving from its current state (1.0) as a partnership-building tool to an enterprise-wide capability (2.0) that went “live” to the US Navy in March 2017.
While SSC PAC was the contract recipient of ORBCOMM prior to 2016, in the summer of 2016, OPNAV N2N6 tasked the Volpe Center with acquiring and managing this vital service for the future and health of SeaVision. OPNAV N2N6 requires the continuation of ORBCOMM data as SeaVision has ingested ORBCOMM data since 2012, is easily ingested into and displayed in SeaVision, is a required redundant form of AIS data that is central to the function of SeaVision, and as ORBCOMM integrates and provides AIS data from other sources, including terrestrial systems.
The Volpe Center has managed SeaVision’s ORBCOMM contract since August 2016, and OPNAV N2N6 has requested the continuation of the Volpe Center’s procurement and management of such services. While SeaVision currently utilizes AIS from other AIS providers with similar satellite networks and with similar AIS message capabilities and latencies, a SeaVision requirement is AIS redundancy, and as such an additional source of AIS is required. As a result, and to ensure that there is no lapse in coverage, the data must be live in SeaVision beginning on August 14, 2017, and access must extend for 12 months.
2. OBJECTIVE
The objective of this effort is to acquire AIS data from ORBCOMM for a period of 12 months for use by the Volpe Center-developed maritime domain awareness (MDA) information web tool, SeaVision, accessed by both domestic and international military and government agencies globally. The satellite and terrestrial AIS data that is produced by ORBCOMM will be ingested and processed by the Volpe Center’s V332 to develop, test and provide sufficient data coverage, reporting and access to both SeaVision and its vast and ever-growing user community.
The goal of the acquisition is to acquire one year’s worth of satellite and terrestrial AIS service from ORBCOMM, as SeaVision’s redundant AIS data source.
3. REQUIREMENTS
The key requirements of this procurement are that all AIS message types be provided as a raw data-stream (i.e. NMEA 0183 or NMEA 2000) and that data be provided as fast as possible (real-time delivery with a high re-visit rate and low latency) throughout the area of interest, which includes the equatorial region. Both satellite and terrestrial AIS data are required through this contract, and the contractor must presently have a network of greater than seventeen (17) satellites and over sixteen (16) ground earth stations to ensure maximum coverage.
4. TASKING
4.1. Task 1: Acquisition of Services
The Contractor must provide coverage of services to the Volpe Center by August 14, 2017. The Contractor must meet with the SeaVision Development Team upon contract award (via a telephone conference call and/or video conferencing software) to supply the Team with any necessary account and/or service-related information.
4.2. Task 2: Maintenance of Services
The Contractor and the SeaVision Development Team will be jointly responsible for monitoring and tracking the AIS coverage. The Contractor shall alert the Project Manager via an email when and if any service degradation or technical issues are expected or reported.
5. DELIVERABLES
The Contractor shall provide the Volpe Center with a raw combined global satellite/terrestrial AIS data feed (connection methods to be outlined within their proposal). Data will be made available via SeaVision, and SeaVision users shall be primarily US Navy personnel at numbered fleets and area commands. Users may also be from other US agencies and organizations (e.x. NOAA), as well as partner nation maritime agencies (e.x. Navy, Coast Guard, etc.) who are working with US agencies.
6. PERIOD OF PERFORMANCE
The period of performance is from August 14, 2017 to August 14, 2018.
7. TECHNICAL POINT-OF-CONTACT (POC)
For all questions and inquiries, please contact:
Lauren Gentile Program Analyst Situational Awareness and Logistics, V332 55 Broadway, Cambridge, MA 02142 Office: 617-494-4542 | Email: Lauren.Gentile@dot.gov mailto:Lauren.Gentile@dot.gov
| 1. BACKGROUND |
| 2. OBJECTIVE |
| 3. REQUIREMENTS |
| 4. TASKING |
| 4.1. Task 1: Acquisition of Services |
| 4.2. Task 2: Maintenance of Services |
| 5. DELIVERABLES |
| 6. PERIOD OF PERFORMANCE |
| 7. TECHNICAL POINT-OF-CONTACT (POC) |
| Lauren Gentile |
File details come from the government source that posted it. Updated .