BAA_HR0011-18-S-0013_Ocean_of_Things_-Amendment_01.pdf
PDF 31 KB Posted
- Attached to
- Ocean of Things - Broad Agency Announcement
- Solicitation number
- HR0011-18-S-0013
View the file
Other files
| File | Type | Posted |
|---|---|---|
| BAA_HR0011-18-S-0013_Ocean_of_Things.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Amendment 01 to DARPA HR001118S0013, Ocean of Things
The purpose of Amendment 01 to DARPA BAA HR001118S0013, Ocean of Things is to add additional guidance to section 1.2.1 per the below:
1. EMSS and Iridium
In BAA section 1.2.1, Technical Area One (TA 1) Float Development, the following additional guidance is provided:
Ocean of Thing TA-1 awardees will need to execute a standard Iridium Value Added Manufacturer (VAM) agreement with Iridium in order to purchase modems and development kits directly from Iridium, receive technical information, and carry out pre-deployment testing of the float's antenna at the Iridium test facility in Arizona. For the purposes of the proposal, TA-1 proposers shall assume a price of $125 per 9603 modem. Additionally, TA-1 performers will need to join with the Enhanced Mobile Satellite Services (EMSS) partner program. The EMSS Partner Program supports vendors within the community whose products provide value to EMSS customers, including the U.S. government and foreign nations. The EMSS Partner Program allows approved vendor devices (primarily Iridium Short- Burst-Data) devices to interoperate with the EMSS gateway, and become an EMSS Value Added Manufacturer (VAM). Approved EMSS Partners have access to a conversion tool kit to change the access code within commercial Iridium devices from Iridium's commercial gateway to the EMSS gateway. This allows users to leverage the benefits of EMSS that are not available through Iridium's commercial gateway. DARPA will provide procedures to become an iridium VAM and an EMSS VAM after notification of selection.
2. Float Raw Data Storage for Algorithm Validation
In BAA section 1.2.1, Technical Area One (TA 1), Float Hardware: Hardware subsection, the following additional guidance is provided:
In order to monitor and validate performance of float hosted signal processing and reporting functionality, TA-1 performers must equip 20% of delivered floats with local data storage and line-of-sight transmission capability (e.g., 802.11, ZigBee, etc.). On board storage must include a minimum of 4 weeks of the float sensor data and a means of rapid data transmission without physical connection to the float. These floats should otherwise be identical in operation to the remaining 80%. Float unit price targets only apply to the non-modified floats. Costs for the modified 20% of floats shall be included in the fixed price option but priced separately.
File details come from the government source that posted it.