N00014-16-S-BA09.pdf

ONR BAA N00014-16-S-BA09 1

ONR BAA Announcement # N00014-16-S-BA09

INTRODUCTION:

This publication constitutes a Broad Agency Announcement (BAA) as contemplated in Federal Acquisition Regulation (FAR) 6.102(d)(2) and 35.016, the Department of Defense Grants and Agreements regulations (DoDGARS) 22.315(a) and DoD’s Other Transaction Guide for Prototypes Projects, USD(AT&L), OT Guide, Jan 2001. A formal Request for Proposals (RFP), solicitation, and/or additional information regarding this announcement will not be issued.

The Office of Naval Research (ONR) will not issue paper copies of this announcement. The ONR reserves the right to select for award all some or none of the proposals in response to this announcement. The ONR reserves the right to fund all, some or none of the proposals received under this BAA. ONR provides no funding for direct reimbursement of proposal development costs. Technical and cost proposals (or any other material) submitted in response to this BAA will not be returned. It is the policy of ONR to treat all proposals as sensitive competitive information and to disclose their contents only for the purposes of evaluation.

Hyperlinks have been embedded within this document and appear as underlined, blue-colored words in the midst of paragraphs. The reader may “jump” to the linked section within this document by “clicking” (CTRL + CLICK, or CLICK).

ONR BAA N00014-16-S-BA09 2

Table of Contents

I. GENERAL INFORMATION

A. Agency Name – B. Research Opportunity Title – C. Program Name – D. Research Opportunity Number – E. Response Date – F. Research Opportunity Description – G. Point(s) of Contact (POC) – H. Instrument Type(s) – I. Catalog of Federal Domestic Assistance (CFDA) Numbers - J. Catalog of Federal Domestic Assistance (CFDA) Titles - K. Other Information –

II. AWARD INFORMATION

A. Amount and Period of Performance- B. Peer Reviews- C. Production and Testing of Prototypes-

III. ELIGIBILITY INFORMATION

IV. APPLICATION AND SUBMISSION INFORMATION

A. Application and Submission Process - B. Content and Format of White Papers/Full Proposals -

a. White Papers

b. Full Proposals C. Significant Dates and Times – D. Submission of Late Proposals – E. Submission of Grant Proposals through Grants.gov. N/A F. Submission of Full Proposals for Contracts

V. EVALUATION INFORMATION

A. Evaluation Criteria – B. Commitment to Small Business C. Options- D. Evaluation Panel -

VI. AWARD ADMINISTRATION INFORMATION

VII. OTHER INFORMATION

A. Applies to Grant, Cooperative Agreement and Other Transaction Agreement applications only:

B. Applies to Contracts only:

C. Applies to Contracts, Grants, Cooperative Agreements and Other Transaction Agreements:

ONR BAA N00014-16-S-BA09 3

I. GENERAL INFORMATION

A. Agency Name -

Office of Naval Research, One Liberty Center 875 N. Randolph Street Arlington, VA 22203-1995 Ship Systems and Engineering Division, Code 331

B. Research Opportunity Title -

Automated Offboard Refueling and Data Transfer for Unmanned Surface Vehicles

C. Program Name -

Autonomous Unmanned Surface Vehicles for Navy Missions

D. Research Opportunity Number - N00014-16-S-BA09

E. Response Date -

White Papers: 15 JUL 2016

Full Proposals: 20 SEP 2016

F. Research Opportunity Description

Background:

The Navy is developing Unmanned Surface Vehicles (USVs) that are launched and recovered from a host ship. A refueling and data transfer system that is remote from the host ship and proximate to the USV operating area will allow a substantially greater fraction of a Navy USVs’ endurance to be spent on performing the mission rather than on non-mission activities associated with refueling, including transiting to and from the host ship and being deployed and recovered on the host ship. The USV to be refueled is a “Fleet-class USV” as defined in the Navy USV Master Plan.1 It is approximately 38.5 ft in length, 10.5 ft beam and full load displacement 21,400 lbs. It can carry between 400 and 650 gallons of diesel fuel marine (DFM) and uses fuel at a rate between 25 and 40 gallons/hr. The refueling port of the USV is located on the starboard side of the craft, above the waterline, about midships. There will be up to 2 terabytes of data to be offloaded from the USV, per refueling iteration. There is currently no data port on the USV.

The fuel source platform (FSP) is envisioned to be another USV, a barge, a small vessel, a bladder or other platform or system. The FSP’s function is to bring fuel from an existing land or shore-based source (such as a fuel depot, port or a ship) to the operating area (the operating area is the area in which the USVs perform operations). The USVs will approach the FSP, align to a connection mechanism, connect to the FSP, make fuel and data connections, receive fuel and

ONR BAA N00014-16-S-BA09 4

transfer data, disconnect from the FSP and resume its mission: this sequence shall be automated and require only the supervision of a remote human operator. For an individual USV, refueling and data transfer should occur simultaneously to save time.

ONR previously demonstrated an at-sea refueling system for a USV, which provided an initial demonstration of a technical approach, significant lessons learned about operational requirements, technology limitations, and expected costs to field this new class of system in the challenging maritime environment2,3,4,5. The ONR demonstration used a towed sponson/refueling probe prototype system for refueling connection and demonstrated feasibility on the 39 ft ONR Unmanned Sea Surface Vehicle (USSV) in sea state (SS)-0 through SS-2. Specifically, a USV with a bow-mounted refueling probe made a connection to the refueling device (in this case, a drogue towed from a fuel source vessel) in SS-0, but had difficulty in performing this operation in SS-2. The SS-2 issue was due to wave-induced relative motions between the USV and the towed drogue that inhibited the USV’s ability to connect to the drogue. When driven by a human operator, the capture success rate was 45% in SS-2 and 71% in SS-0. This USV was a similar size, but is not the same design as the USV that is the subject of this solicitation. Other approaches for refueling USVs have been pursued6,7,8. All of these concepts should be considered by Offerors to be examples of possible approaches; however, the Government is not predisposed to any particular design. ONR evaluates the current TRL level of its system as 4 (component or breadboard validation in laboratory environment). Although at-sea testing was conducted as described above, the sea states were modest compared to Navy requirements and the refueling system was not integrated with the USV nor was integration with the ashore/afloat fuel infrastructure considered. Additional development is needed for the approach, alignment and connection of the USV to the FSP in SS-3 (threshold) SS-4 (objective) and to automate the system; this is within scope of the BAA. A particular challenge in the ONR at-sea test was hydrodynamics: the wave-induced relative motions between sponson and USV. In the future, this might be mitigated by sponson design, location of the probe on the USV relative to the USV’s center of gravity (CG), and modeling and simulation (via computational fluid dynamics) of FSP/USV wave-induced motions to clarify system design.

Scope:

Under this BAA, the Offeror will design, build, test, and demonstrate a prototype Offboard Refueling and Data Transfer System (ORADTS). The ORADTS design must improve on previous designs by providing a more robust system that enhances system usability in higher sea states, reliability, and maintainability for implementation in Navy operations. This could be via a new and different design or via multiple technology and architecture improvements to the previous design. The program goal is to achieve a Technology Readiness Level (TRL) of 6 for the system in order to support the Navy’s potential consideration of the ORADTS technology in a Program of Record (PoR) milestone decision.

Overview.

The product for this contract is a prototype ORADTS (hardware and software). The metric for the at-sea test is the ability of the ORADTS to refuel 650 gallons of fuel and transfer 2 terabytes of data with zero errors from a USV within 45 minutes (threshold)/30 minutes (objective) in

ONR BAA N00014-16-S-BA09 5

NATO SS-3 (threshold)/ SS-4 (objective)9. The 45/30 minute timeframe includes the last 50 meters of USV transit to the FSP, the automated approach, alignment and connection of the USV to the FSP, the automated transfer of fuel and data, disconnection of the USV, and 50 meters transit of the USV away from the FSP. The time required for refueling and transfer of data is of critical importance since the less time spent performing these functions, the more time the USV can spend performing the mission. The FSP should be capable of refueling and data transfer for 1 USV (threshold) and 8 USVs (objective).

The Government is interested in a modular ORADTS, which will include, at a minimum the following components: (1) automated alignment sub-system that aligns the USV to the FSP prior to physical connection and which manages wave-induced motion between USV and the FSP to permit connection in the required sea states, (2) connection sub-system for automated physical connection between USV and FSP, (3) fuel transfer sub-system including automated transfer of fuel between USV and the FSP, (4) data transfer sub-system for automated transfer of data between the USV and FSP, and (5) the FSP. It is possible that the function of some of the components listed above be combined into a single component. Items (1) through (4) will consist of elements on the USV and the FSP. It is critically important to minimize size, weight and power consumption impacts of the ORADTS on the USV. The ORADTS shall be capable of operation in manual mode (remote human operation) or automated mode (remote human supervision). It shall be capable of data transfer during refueling.

The Offeror shall consider the benefits and drawbacks of an ORADTS that can refuel multiple USVs simultaneously, to maximize the time the USVs spend performing the mission and minimize the time spent refueling. Time savings resulting from simultaneous refueling of multiple USVs might be beneficial, or it is possible that time savings might be offset by increased size, weight, complexity and cost of an ORADTS and FSP that can refuel multiple USVs simultaneously. If the ORADTS is capable of refueling multiple USVs simultaneously, easy addition and removal of additional USV connection stations on the FSP, as required for a particular operation, will be beneficial.

It is expected that a primary technical challenge in this program will be in accomplishing automated refueling and data transfer in higher sea state conditions, due to wave and wind-induced relative motions between the USV and the FSP that the USV is connecting to. Systems that enable refueling and data transfer to take place through SS-3 (threshold) and SS-4 (objective) are a critical goal of this solicitation. For this reason, modeling and simulation (computational fluid dynamics) of wave-induced motions and the hydrodynamic aspects of USV and FSP is expected to be a key part of the technical approach proposed by the Offeror.

The Government anticipates that data transfer from the USV to the FSP will be accomplished using existing technology that is appropriately modified for this particular application. The development of new technology for data transfer is outside the scope of this BAA. The subsequent transfer of data from the FSP to the host ship or other platform is in-scope for the demonstration and testing under this contract and must be accomplished using existing technology. The data transfer capability should be modular: the data transfer capability must be able to be optionally added to or removed from the ORADTS system. Data transfer must be accomplished with zero errors.

ONR BAA N00014-16-S-BA09 6

Ideally, the FSP will be based on an inexpensive, readily available maritime vessel or platform that already exists in the Navy inventory or commercially. A self-propelled FSP is desirable (both for the transit to the operating area at the beginning of a mission and for repositioning within the operating area during a mission), but this self-propulsion must be traded off against the additional cost and complexity required to attain it. The FSP will have to transit or be transported distances of up to 1500 nm. If the FSP is not self-propelled, the issue of avoiding drift in currents must be addressed. If the FSP is not self-propelled and has to be towed to the operating area, it is acceptable for the platform providing the tow to be manned. The FSP should provide fuel to the operating area at a rate at least equal to the rate the USVs are consuming it.

Up to eight USVs may be simultaneously performing a mission in proximity to each other require refueling and data transfer. Therefore, a scalable FSP capability is preferred. The costs and benefits of a single, larger FSP should be traded off against multiple, smaller FSPs. A Government study found that FSPs carrying at least 15,000 gallons of fuel are optimal since smaller amounts of fuel necessitate an unreasonably large number of FSPs; however, the Offeror should perform its own analysis. The FSP should be capable of transmitting its position and status to the USV. Development of a new platform for the FSP is outside the scope of this BAA and is not consistent with the overall goals of the program. For the purposes of this program, a surrogate FSP can be used to demonstrate the ORADTS in the Phase II and III demonstrations, but Offerors shall make clear in their proposals what actual FSP platform is envisioned.

The Government seeks balanced in the proposed approaches between use of existing sub-systems and components where appropriate, and technical maturation of components or designs where mature solutions do not exist. The Government will use a three-phased acquisition structure, with an overall 40-month timeline from contract award to project completion (completion of Phase 3). This BAA calls for fully integrated system level proposals for ORADTS. Proposals that only address partial solutions or component level technologies will not be considered for award.

Program Objectives:

The following objectives are provided to assist Offerors in developing their ORADTS design approach:

• Cost-effective trade-offs between hydrodynamic performance, mechanical robustness, and system size, weight and cost;

• Hydrodynamic modeling and simulation, for example computational fluid dynamics (CFD) of relative motions in required sea states, as a necessary and integral part of system design for hydrodynamic optimization;

• System design and performance that enable a substantially greater fraction of the USV’s endurance to be spent performing the mission, rather than in activities associated with refueling such as time spent connecting to the FSP, transferring fuel and data; minimize time to refuel and transfer data;

• Fuel source platform (FSP) must be an existing platform that is readily available and inexpensive, no new platform required;

• FSP is capable of carrying DFM, JP-5 or JP-8, but only one of these fuels at a time;

ONR BAA N00014-16-S-BA09 7

• The ORADTS components that are installed on the USV must have minimal size, weight and power consumption impact to the USV;

• Mechanically robust systems, for example, able to withstand wave-induced collisions between USV and FSP in required sea states, at the USV refueling speed determined by the Offeror;

• System configurations that can sustain long-term exposure to a maritime environment and the Navy’s operating environment (e.g., corrosion, shock, vibration, moisture, electromagnetic, environmental effects);

• Operates for at least one month of daily at-sea testing with minimal manpower and maintenance requirements;

• Information assurance/anti-tamper (IA/AT) shall be considered in the system design; however, the Government may elect to delay implementation of IA/AT aspects until after this contract is completed;

• Capability to be installed and tested on an Offeror-provided USV in Phase II and a Navy USV in Phase III;

• Meets all relevant safety requirements for installation and operation;

• Meets all relevant environmental requirements, for example, system design minimizes or eliminates chance of a fuel spill into the water. The Offeror is expected to be well-versed in the applicable environmental regulations and laws;

• Integrates with Government Furnished USV in Phase III.

Throughout the program, the Offeror is expected to employ a tailored (to a science and technology program) yet rigorous systems engineering process (both hardware and software) in order to successfully execute Initial Design Review (IDR), Final Design Review (FDR), risk reduction testing, component and sub-assembly verification testing, and system demonstration.

The level of detail in the design documentation should be appropriate to a science and technology program in which a prototype system is being developed, rather than an acquisition program that is developing the final production version. The contractor’s systems engineering process should ensure the capture of technical knowledge acquired in the execution of the project as well as a configuration management approach for managing the design. The extent of the knowledge captured will enable the assessment of adequacy of the analytical methods and design practices, and their correlation with test results. The contractor’s process should include a series of tracking tools that enable efficient assessment of program progress to include:

• Technical Performance Measures (TPMs). The contractor should provide a manageable set of TPMs that relate to and are consistent with all levels of the system configuration, tracks the maturity of key risk areas, and forecasts the achievement of systems requirements.

• Risk Management Approach. As part of a Risk Management and Mitigation Plan (RMMP) the contractor is expected to identify key technical risk areas consistent with achieving project objectives against the Integrated Master Schedule (IMS).

Program Phases:

The Government plans a logical progression from design and risk reduction through fabrication and assembly, with initial sub-system and component-level testing, and culminating in meeting the program objective in a test or set of tests at-sea. This three-phased plan includes: Phase I (Base Period), Phase II (Option I) and Phase III (Option II):

ONR BAA N00014-16-S-BA09 8

Phase I (Base Period): System Design and Risk Reduction

Activities and Deliverables. Estimated period of performance is approximately 15 months.

The objectives of Phase I include development and refinement of the design package and risk reduction efforts from the System Requirements Review (SRR) through the Initial Design Review (IDR) and completes after the Final Design Review (FDR). The level of detail in the design documentation should be appropriate to a science and technology program in which a prototype system is being developed, rather than an acquisition program that is developing the final production version. Long-lead items are expected to be identified in proposals and finalized by the IDR. There is additional time allocated in Phase I for post FDR design actions and final documentation.

Phase I activities shall address:

• Conduct hydrodynamics modeling and simulation (computational fluid dynamics) to determine wave-induced motions for USV and FSP and design and performance trade studies to develop a refueling system design;

• Conduct integration design of the ORADTS with Navy USV design (requires Government-furnished information (GFI));

• Documentation of design and interfaces throughout the program;

• Conducting a Systems Requirements Review (SRR);

• Conducting an Initial Design Review (IDR);

• Conducting a Final Design Review (FDR);

• Establishing and executing a Risk Management and Mitigation Plan (RMMP) to identify plans to address highest risk technology areas and validate performance capabilities;

• Conducting Phase II planning based on the TDP;

The Government requires the following deliverables, in contractor format, during the performance of Phase I:

• Set of drawings to be used for the fabrication of ORADTS

• Interface Control Documents (ICD) and Interface Functional Documents (IFD);

• Results of modeling and simulation (M&S) and other technical activities conducted during Phase 1;

• SRR Briefing Charts and Documentation*;

• RMMP, updated quarterly to reflect results of design evolution and any risk reduction activities;

• Quarterly update of the IMS, Review materials, and any adjustments to anticipated technical activities in Phase II and Phase III with associated cost-level adjustments to cost and schedule;

• All test reports from sub-system, system, and risk reduction activities;

• Phase II and III demonstration plans (including cost and schedule), updated quarterly;

• IDR Briefing Charts and Documentation, including Long Lead Item/Critical Hardware Parts List and Procurement Schedule*;

ONR BAA N00014-16-S-BA09 9

• FDR Briefing Charts and Documentation*;

• Monthly Progress Reports (Technical and Financial), written and meeting or telcon.

*The tailored SRR, IDR, and FDR deliverables are described in Appendix A.

Phase II (Option 1): System Fabrication and Contractor at-sea Testing

Activities and Deliverables: The period of performance is anticipated to be approximately 15 months.

The conclusion of Phase II and the start of Phase III may overlap for several months depending on the results from the Phase II TRR and the scale of modifications required after the TRR to support the test activities during Phase III.

The objectives of Phase II include sub-assembly, assembly, and system level testing as well as residual risk reduction activities. Phase II contractor activities shall address:

• Procurement, fabrication, assembly, and integration with other sub-systems including the USV and fuel source platform to complete the fully functional system;

• Continue to execute the RMMP and collaborate with the Government to develop a System Demonstration Plan that covers all system level demonstration activities;

• Support a Government Test Readiness Review (TRR) to validate that the system is ready for Phase III testing and demonstration;

• Implement minor system alterations as identified in the TRR;

• Deliver the system pierside, ready for testing and demonstration;

• Perform at-sea testing and demonstration of system using contractor-provided surrogate USV. Confirm ORADTS system meets the performance criteria described in “Overview” section.

The Government envisions testing will be performed by the Offeror in the latter stages of Phase II, to validate the performance of the system, including approach of the USV to the FSP, alignment with the connection mechanism, connection of USV to FSP, refueling of a USV and data transfer from a USV. Readiness reviews will be conducted by the Government to ensure the system is ready for testing, meeting all check out, range safety and environmental requirements.

In order to ensure adequate testing preparation, initial versions of operating and maintenance manuals shall be developed prior to the test. The Government envisions that the test will last four weeks. Proposals may offer alternative test schedules, however they shall include rationale based on significant comparative technical, cost, or schedule improvements. It is envisioned that the contractor will be primarily responsible for operating the system during Phase II testing, using the contractor’s USV. However, the Government may elect to operate the system during a portion of Phase 2 testing as a training opportunity in preparation for Phase III. A successful TRR for Phase 3 testing is required prior to proceeding with final delivery of the system. The Government will take

ONR BAA N00014-16-S-BA09 10

possession of the system at the conclusion of Phase II, with pier-side delivery to the test range.

The Government requires the following deliverables, in contractor format, during the performance of Phase II:

• System delivery in sea based configuration, including all hardware and software, operating instructions and limitations;

• System cost information including bill of materials, material and labor costs to build a system;

• Final operating and maintenance manuals;

• Diagnostic, test, and support equipment needed to support system testing;

• Integrated Master Schedule (IMS), updated monthly;

• Test reports for all tests;

• Phase III demonstration plans (including cost and schedule), updated quarterly;

• RMMP, updated quarterly to reflect results of design evolution and any risk reduction activities;

• System Demonstration Plan, updated quarterly;

• TRR presentation and documentation;

• Interim Quarterly Review Briefing Charts;

• Monthly Progress Reports (Technical and Financial), written and meeting or telcon;

• Final “As Built” set of drawings used for the fabrication of ORADTS, and ICDs and IFDs;

• Logistics footprint, including spares and maintenance requirements;

• Test reports documenting the technical performance of the during the at-sea tests;

• Final Report.

Phase III (Option 2): Integration with Navy USV and Government Testing

Activities and Deliverables: The period of performance is anticipated to be approximately 10 months.

The conclusion of Phase II and the start of Phase III may overlap for several months depending on the results from the Phase II TRR and the scale of modifications required after the TRR to support the test activities during Phase III.

In Phase III, the contractor shall support the installation and integration of the system with the Navy USV or a Government-specified surrogate USV. If a Navy USV is used, the Government will provide the contractor with necessary information and drawings.

The contractor will also be expected to provide support for check-out testing of the integrated system. Following installation, the contractor will provide on-board support and technical service representatives during Phase III testing. These personnel will provide technical, operations and maintenance support for the system throughout the deployment. It is currently anticipated that Phase III testing will be of two-week duration.

ONR BAA N00014-16-S-BA09 11

The contractor may also be required to participate in test data collection, analysis, post-test performance assessments, and documentation development.

The Government requires the following deliverables in contractor format, during the performance of Phase III:

• Monthly Progress Reports (Technical and Financial), written and meeting or telcon;

• Revisions and edits to Final “As Built” Technical Data Package (TDP), including ICDs and IFDs resulting from Phase III installation and integration activities.

References:

1. “The Navy USV Master Plan”, http://www.navy.mil/navydata/technology/usvmppr.pdf, last accessed 4 FEB2016.

2. R.J. Galway and D.B. Harris, “Unmanned Sea Surface Vehicle (USSV) Motion Data and Refueling Equipment Design”, ASNE Launch & Recovery Symposium 2010, www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA532549, last accessed 18 JAN 2016.

3. D B. Harris and R.J. Galway, “Sea surface vessel recovery and fueling system”, US Patent 8,568,076, 2013.

4. R.J. Galway, “Contemporaneous latching and fueling arrangement for fueling a water vessel”, US Patent 8,225,735, 2012.

5. R.J. Galway, “Probe receiver device for recovering surface water vessels”, US Patent 8,020,505, 2011.

6. S.M. Petersen, “Ship or Air Deployable Automated Refueling Station for Multiple Unmanned Surface Vessels”, US Patent 8,991,447 B1, 2015.

7. G. Henshaw, “NRL Tests Robotic Fueling of Unmanned Surface Vessels”, http://www.nrl.navy.mil/media/news-releases/2012/nrl-test-robotic-fueling-of-unmanned-surface-vessels, last accessed 18 JAN 2016.

8. “Offboard Refueling Support System for Unmanned Surface Vehicles” Navy SBIR Topic N08-177, http://www.navysbir.com/n08_2/N082-177.htm, last accessed 18 JAN 2016.

9. NATO STANAG 4194 “Standardized Wave and Wind Environments and Shipboard Reporting of Sea Conditions” (1983)

G. Point(s) of Contact

Comments or questions submitted should be concise and to the point, eliminating any unnecessary verbiage. In addition, the relevant part and paragraph of the Broad Agency Announcement (BAA) should be referenced.

http://www.navy.mil/navydata/technology/usvmppr.pdf http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA532549 http://www.nrl.navy.mil/media/news-releases/2012/nrl-test-robotic-fueling-of-unmanned-surface-vessels http://www.nrl.navy.mil/media/news-releases/2012/nrl-test-robotic-fueling-of-unmanned-surface-vessels http://www.navysbir.com/n08_2/N082-177.htm

ONR BAA N00014-16-S-BA09 12

Questions of a business nature, and suggestions for improvement, should be submitted to the following Code 252 Staff:

Elizabeth Bray Contract Specialist ONR Code 252

C4ISR AND SEA WARFARE CONTRACT BRANCH

One Liberty Center 875 N. Randolph Street Arlington, VA 22203-1995 Elizabeth.Bray@navy.mil

Tracy Scott Contracting Officer ONR Code 252

C4ISR AND SEA WARFARE CONTRACT BRANCH

One Liberty Center 875 N. Randolph Street Arlington, VA 22203-1995 Tracy.Scott1@navy.mil

Questions of a technical nature should be submitted to:

Point of Contact Name: Robert Brizzolara Point of Contact Occupation Title: Program Office; Division: Ship Systems and Engineering Division Division Code: 331 Address: 875 N. Randolph St. Arlington, VA 22203 Email Address: robert.brizzolara@navy.mil

Questions of a Security nature should be submitted to:

Torri Powell Industrial Security Specialist Office of Naval Research Security Department, Code 43 One Liberty Center 875 North Randolph St.

Arlington, VA 22203-1995 Email Address: torri.powell@navy.mil

Note: All communications shall be UNCLASSIFIED and shall be submitted via e-mail to the Technical Point of Contact (POC) with a copy to the designated Business POC(s).

Questions submitted within 2 weeks prior to a deadline may not be answered, and the due date for submission of the white paper and full proposal will not be extended.

mailto:tracy.scott1@navy.mil mailto:Tracy.Scott1@navy.mil mailto:robert.brizzolara@navy.mil

ONR BAA N00014-16-S-BA09 13

Amendments to this BAA will be posted to one or more of the following web pages:

-Federal Business Opportunities (FedBizOpps) Webpage – https://www.fbo.gov/ -ONR Broad Agency Announcement (BAA) Webpage - http://www.onr.navy.mil/en/Contracts- Grants/Funding-Opportunities/Broad-Agency-Announcements.aspx

H. Instrument Type(s) -

The award will take the form of a contract.

Any contract award resulting from this BAA will incorporate the most current FAR, DFARS, NMCARS and ONR clauses.

Examples of model contracts can be found on the ONR website at the following link:

http://www.onr.navy.mil/Contracts-Grants/submit-proposal/contracts-proposal/contract-model-awards.aspx. ONR Contract specific representations and certifications can be accessed on the following page of the ONR website: http://www.onr.navy.mil/en/Contracts-Grants/submit-proposal/contracts-proposal.aspx.

I. Catalog of Federal Domestic Assistance (CFDA) Numbers -

12.300

J. Catalog of Federal Domestic Assistance (CFDA) Titles -

Department of Defense (DOD) Basic and Applied Scientific Research

K. Other Information -

Work funded under a BAA may include basic research, applied research and some advanced technology development research. With regard to any restrictions on the conduct or outcome of work funded under this BAA, ONR will follow the guidance on and definition of “contracted fundamental research” as provided in the Under Secretary of Defense (Acquisition, Technology and Logistics) Memorandum of 24 May 2010.

As defined therein the definition of “contracted fundamental research,” in a DoD contractual context, includes research performed under grants and contracts that are (a) funded by Research, Development, Test and Evaluation Budget Activity 1 (Basic Research), whether performed by universities or industry or (b) funded by Budget Activity 2 (Applied Research) and performed on campus at a university. The research shall not be considered fundamental in those rare and exceptional circumstances where the applied research effort presents a high likelihood of disclosing performance characteristics of military systems or manufacturing technologies that are unique and critical to defense, and where agreement on restrictions have been recorded in the contract or grant.

Pursuant to DoD policy, research performed under grants and contracts that are a) funded by https://www.fbo.gov/ http://www.onr.navy.mil/en/Contracts-Grants/Funding-Opportunities/Broad-Agency-Announcements.aspx http://www.onr.navy.mil/en/Contracts-Grants/Funding-Opportunities/Broad-Agency-Announcements.aspx http://www.onr.navy.mil/en/Contracts-Grants/Funding-Opportunities/Broad-Agency-Announcements.aspx http://www.onr.navy.mil/Contracts-Grants/submit-proposal/contracts-proposal/contract-model-awards.aspx http://www.onr.navy.mil/Contracts-Grants/submit-proposal/contracts-proposal/contract-model-awards.aspx http://www.onr.navy.mil/en/Contracts-Grants/submit-proposal/contracts-proposal.aspx http://www.onr.navy.mil/en/Contracts-Grants/submit-proposal/contracts-proposal.aspx

ONR BAA N00014-16-S-BA09 14

Budget Activity 2 (Applied Research) and NOT performed on-campus at a university or b) funded by Budget Activity 3 (Advanced Technology Development) does not meet the definition of “contracted fundamental research.” In conformance with the USD (AT&L) guidance and National Security Decision Directive 189, ONR will place no restriction on the conduct or reporting of unclassified “contracted fundamental research,” except as otherwise required by statute, regulation or Executive Order. For certain research projects, it may be possible that although the research being performed by the prime contractor is restricted research, a subcontractor may be conducting “contracted fundamental research.” In those cases, it is the prime contractor’s responsibility in the proposal to identify and describe the subcontracted unclassified research and include a statement confirming that the work has been scoped, negotiated, and determined to be fundamental research according to the prime contractor and research contractor.

Normally, fundamental research is awarded under grants with universities and under contracts with industry. Non-fundamental research is normally awarded under contracts and may require restrictions during the conduct of the research and DoD pre-publication review of such research results due to subject matter sensitivity.

FAR Part 35 restricts the use of Broad Agency Announcements (BAAs), such as this, to the acquisition of basic and applied research and that portion of advanced technology development not related to the development of a specific system or hardware procurement. Contracts and grants and other assistance agreements made under BAAs are for scientific study and experimentation directed towards advancing the state of the art and increasing knowledge or understanding.

THIS ANNOUNCEMENT IS NOT FOR THE ACQUISITION OF TECHNICAL,

ENGINEERING AND OTHER TYPES OF SUPPORT SERVICES.

II. AWARD INFORMATION

The Government anticipates either a single award, or multiple awards based on this announcement.

A. Funded Amount and Period of Performance-$6M, 40 months

B. Peer Reviews- N/A

C. Production and Testing of Prototypes-

In the case of funded proposals for the production and testing of prototypes, ONR may modify the contract to add a contract line item or contract option for the provision of advanced component development or for the delivery of additional prototype units. However, such a contract addition shall be subject to the limitations contained in Section 819 of the National Defense Authorization Act (NDAA) for Fiscal Year 2010, as modified in Section 811 of the NDAA for Fiscal Year 2015.

ONR BAA N00014-16-S-BA09 15

III. ELIGIBILITY INFORMATION

A. All responsible sources from academia and industry may submit proposals under this BAA.

Historically Black Colleges and Universities (HBCUs) and Minority Institutions (MIs) are encouraged to submit proposals and join others in submitting proposals. However, no portion of this BAA will be set aside for HBCU and MI participation, due to the impracticality of reserving discrete or severable items of this research for exclusive competition among such entities.

B. Federally Funded Research & Development Centers (FFRDCs), including Department of

Energy National Laboratories, are eligible to receive awards under this BAA. However, teaming arrangements between FFRDCs and eligible principal Offerors are allowed so long as such arrangements are permitted under the sponsoring agreement between the Government and the specific FFRDC.

C. Navy laboratories and warfare centers as well as other Department of Defense and civilian agency laboratories are also not eligible to receive awards under this BAA and should not directly submit either white papers or full proposals in response to this BAA. If any such organization is interested in one or more of the programs described herein, the organization should contact the ONR Technical POC to discuss its area of interest. The various scientific divisions of ONR are identified at http://www.onr.navy.mil/. As with FFRDCs, these types of federal organizations may team with other responsible sources from academia and industry that are submitting proposals under this BAA.

D. University Affiliated Research Centers (UARCs) are eligible to submit proposals under this BAA unless precluded from doing so by their Department of Defense UARC contract.

E. Teams are also encouraged and may submit proposals in any and all areas. However, Offerors must be willing to cooperate and exchange software, data and other information in an integrated program with other contractors, as well as with system integrators, selected by

ONR.

F. Offerors should be aware of recent changes in export control laws. Offerors are responsible for ensuring compliance with all International Traffic in Arms Regulation (ITAR)(22 CFR §120 et. seq.) requirements, as applicable. In some cases, developmental items funded by the Department of Defense are now included on the United States Munition List (USML) and are therefore subject to ITAR jurisdiction. Offerors should address in their proposals whether ITAR restrictions apply or do not apply, such as in the case when research products would have both civil and military application, to the work they are proposing to perform for ONR.

The USML is available online at http://www.ecfr.gov/cgi-bin/text-idx?node=pt22.1.121.

Additional information regarding the President's Export Control Reform Initiative can be found at http://export.gov/ecr/index.asp.

G. Cost sharing is not expected and will not be used as a factor during the merit review of any proposal hereunder. However, the Government may consider voluntary cost sharing if proposed.

http://www.onr.navy.mil/ http://export.gov/ecr/index.asp

ONR BAA N00014-16-S-BA09 16

IV. APPLICATION AND SUBMISSION INFORMATION

Section IV: Table of Contents A. Application and Submission Process B. Content and Format of White Papers/Full Proposals

a. White Papers

b. Full Proposals

i. For non-Grants

ii. For Grants –N/A

C. Significant Dates and Times D. Submission of Late Proposals E. Submission of Grant Proposals through Grants.gov – N/A F. Submission of White Papers and Full Proposals for Contracts, Cooperative Agreements, and Other Transaction Agreements

* Click on the above hyperlinks to navigate directly to your desired section

A. Application and Submission Process -

White Papers and Full proposals are required for submission.

White Papers: The due date for white papers is no later than 3:00 PM (EST) on 15 JUL 2016. If an Offeror does not submit a white paper before the specified due date and time, it is not eligible to participate in the remaining Full Proposal submission process and is not eligible for funding.

White Paper Evaluation/Notification: Navy evaluations of the white papers will be issued via email notification on or about 15 AUG 2016. Offerors whose white papers are judged to be of insufficient value to the Navy and Offerors who did not submit a white paper may not submit a final proposal under this BAA.

Full Proposals: The due date for receipt of Full Proposals is 3:00 PM (EDT) on 20 SEP 2016. It is anticipated that final selections will be made about 5 weeks after full proposal submission. As soon as the final full proposal evaluation process is completed, PI’s will be notified via email of their project’s selection or non-selection for FY17 funding. Full proposals received after the published due date and time will not be considered for funding.

B. Content and Format of White Papers/Full Proposals -

White Papers and Full Proposals submitted under this BAA shall be unclassified.

A non-proprietary version of the Statement of Work must also be submitted. Do not put proprietary data or markings in or on the Statement of Work. For proposals containing data that the offeror does not want disclosed to the public for any purpose, or used by the Government except for evaluation purposes, the contractor shall mark the title page with the following legend:

“This proposal includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed--in whole or in part--for any purpose other than to evaluate

ONR BAA N00014-16-S-BA09 17

the proposal. If, however, a contract is awarded to this offeror as a result of--or in connection with-- the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting contract. This restriction does not limit the Government’s right to use information contained in this data if is obtained from another source without restriction. The data subject to this restriction are contained in (insert numbers or other identification of sheets).”

Also, mark each sheet of data that the offeror wishes to restrict with the following legend:

“Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal.”

All proposal submissions will be protected from unauthorized disclosure in accordance with FAR Subpart 15.207, applicable law, and DoD/DoN regulations. Offerors are expected to appropriately mark each page of their submission that contains proprietary information.

STATEMENT OF WORK (SOW): A non-proprietary version of the SOW must also be submitted.

IMPORTANT NOTE: Titles given to the White Papers/Full Proposals should be descriptive of the work they cover and not be merely a copy of the title of this solicitation.

a. WHITE PAPERS

White Paper Format

− Paper Size – 8.5 x 11 inch paper − Margins – 1 inch − Spacing –single-spaced − Font – Times New Roman, 12 point − Page limit: 8 pages (excluding cover page, resumes, bibliographies, and table of contents)

White Paper Submission

White papers are to be submitted as a pdf file via electronic mail (email) only to robert.brizzolara@navy.mil. The subject line of the email shall read “N00014-16-S-BA09” White Paper Submission”. The white paper must be a Microsoft Word 2007 compatible, or PDF format attachment to the email. There is an email size limit of 5MB per email.

NOTE: Do not send:

1) Hardcopies of White Papers (including Facsimiles) as only electronic submissions will be accepted and reviewed;

2) ZIP files; and

3) Password protected files.

White Paper Content

ONR BAA N00014-16-S-BA09 18

• Cover Page: The Cover Page shall be labeled “WHITE PAPER” and shall include the BAA Number N00014-16-R-BA09, proposed title, technical points of contact, telephone number, facsimile number, and e-mail address.

• Technical Concept: There is considerable freedom to formulate the main body of the white paper as the Offeror sees fit. Here is some general guidance on what may be included in the technical concept: a description of the proposed ORADTS, technical approach, what's new and what leverages previous work, relevance to Navy, the concept of operation for the new capabilities to be delivered, a plan for demonstrating and evaluating the Offeror's product including evaluation metrics, transition potential, proprietary aspects of the project and any assertions of data rights applicable to the results of this effort. The white paper must address ORADTS system attributes and performance, including:

• Physical configuration

• Estimates of size, weight and power consumption impacts to USV

• Approach to achieving operations in SS-3 and SS-4 including hydrodynamic modeling and simulation

• Estimates of key time durations (approach/alignment/connection time, refueling time, data transfer time, disconnection time) and indicate limiting design element(s)

• Estimate of data transfer performance

• Approach to automation of the ORADTS system.

• Approach to human supervision that is required for operation of the ORADTS system

• FSP: if a surrogate FSP is used, information regarding the level of fidelity of the surrogate to the actual FSP

• Modularity of the proposed ORADTS

• Ability of ORADTS to service multiple USVs simultaneously, if applicable, or to be scaled up to multiple USVs

• Rough Order of Magnitude (ROM) Cost: Cost information is needed, although not at the level of detail as required with the full proposal. White paper submissions shall include a cost summary showing requested funding per year. The cost summary (not to exceed one (1) page) shall be segregated by both task and year.

b. FULL PROPOSALS

i. INSTRUCTIONS FOR CONTRACTS

Proposal Package:

The following five documents with attachments comprise a complete proposal package:

(1) Proposal Checklist (pdf)

(2) Technical Proposal Template (Word), Technical proposals shall not exceed 150 pages. Proposals submitted in response to this BAA shall address the following attributes, to the greatest degree possible, consistent with the maturity of the proposed design. Proposals must address conceptual design overviews, descriptions, and system

ONR BAA N00014-16-S-BA09 19

block diagrams in sufficient detail to illustrate design considerations, enable ease of understanding, and provide context for any salient features or configurations. At a minimum the technical proposal should address the following:

Overall scientific and technical merits of the proposal: Address system attributes and performance, including:

• Physical configuration, estimated shapes, dimensions, weights, centers of gravity, and location relationships between structure, containers, pumps, radios, housings, and modules

• Size, weight and power consumption impacts to USV

• Approach to achieving operations in SS-3 and SS-4 including hydrodynamic modeling and simulation

• Key time durations (approach/alignment/connection time, refueling time, data transfer time, disconnection time) and indicate limiting design element(s)

• Data transfer performance

• Details of the approach to automation of the ORADTS system.

• Details of the human supervision that is required for operation of the

ORADTS system, for example the nature of the information the human needs to be provided about the status of the system and the type of interaction the human will have with the ORADTS system

• FSP: if a surrogate FSP is used, information regarding the level of fidelity of the surrogate to the actual FSP

• Details regarding modularity of the proposed ORADTS

• Ability of ORADTS to service multiple USVs simultaneously, if applicable, or to be scaled up to multiple USVs

Program Execution Plan - Offerors must demonstrate a credible plan for achieving the objectives of Phase I, Phase II, and Phase III as outlined in the paragraphs entitled Scope, Overview, Program Objectives, and Program Phases, stated above. Offerors must describe the systems engineering approach that will be used to focus engineering efforts among multiple sub-systems and developers, including their proposed process, analytic methodologies, technical analysis or simulation efforts, validation approach, and any Model-Based Systems Engineering. The Offeror shall provide a Statement of Work (SOW) and Integrated Master Schedule (IMS). The SOW, IMS, and cost proposal shall be consistent and fully integrated employing a common work breakdown structure and numbering scheme.

Potential Naval relevance, contribution to ONR’s mission and transitionability: The Government seeks information that describes the relevance of the proposed approach for future Navy operational employment. Examples of such information include:

• Design Maturity and Risk Reduction Approach: The Office of Naval Research has defined an aggressive, three phase program for achieving successful testing and demonstration. It is therefore critical that the system and sub-systems have adequate maturity and an acceptable level of technical and integration risk inherent in their design. Proposals should address an Initial RMMP containing the following information:

ONR BAA N00014-16-S-BA09 20

i. Risk areas and risk mitigation plans for all three phases, with mitigation plan detailed through the use of risk matrix charts and detailed, time-oriented, schedule and risk waterfalls with a goal to be below the "high" thresholds by IDR.

ii. Methodology for decomposing risks through the system architecture and design to the Configuration Item (CI) level.

• Use of the proposed design on alternate fuel supply platforms (FSP)

• The scalability of the proposed system and sub-system elements to support the operation of up to eight USVs

• Elements of the design which provide cost effective future upgrade options by following

Modular Open Systems Architecture (MOSA) principles and practices

• Design features at the system and sub-system level which address environmental protection

(for example, fuel spill prevention), reliability, maintenance and information assurance/anti-tamper. Provide rationale and supporting information

• Manufacturing readiness and production rate capability of existing industry base to fabricate special…