Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF JANUARY 01, 2005 FBO #1132
SOLICITATION NOTICE

A -- Topical BAA (# 050997) for ?Sonar Solutions for High-Resolution Bottom Mine Detection and Classification for Unmanned Undersea Vehicle (UUV) Applications? (Part 1 of 2)

Notice Date
12/30/2004
 
Notice Type
Solicitation Notice
 
NAICS
541710 — Research and Development in the Physical, Engineering, and Life Sciences
 
Contracting Office
Department of the Navy, Naval Sea Systems Command, NUWC Division Newport, Simonpietri Drive, Newport, RI, 02841-1708
 
ZIP Code
02841-1708
 
Solicitation Number
050997
 
Response Due
2/14/2005
 
Archive Date
3/1/2005
 
Description
?This synopsis is being posted to both the Federal Business Opportunities(FBO) page located at http://www.eps.gov and the Navy Electronic Commerce on Line(NECO) site located at http://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 the Navy Sea Systems Command.? This synopsis constitutes a Broad Agency Announcement (BAA) per FAR 6.102; there will be no formal request for proposals (RFP) or other solicitation in regard to this announcement. Competition is unrestricted. A. INTRODUCTION. The Naval Undersea Warfare Center Division Newport, Autonomous Vehicle Division, acting as the Technical Direction Agent for the Program Manager, Unmanned Undersea Vehicles, PMS403, is soliciting advanced technology proposals for the development of components, subsystems, and systems to provide sonar solutions for high-resolution bottom mine detection and classification for use in unmanned undersea vehicle applications. A one-step sequence is established for offerors contemplating submission of a proposal under this BAA. The proposal may be for projects or investigations that can be completed within 20 months of award, or may be for multiyear projects as long as each subsequent phase can be funded as individual options with clearly defined milestones and deliverables. NUWCDIVNPT strongly encourages well-coordinated, interdisciplinary research and development activities that take into consideration previous and current relevant work, and significant relevant engineering tradeoffs and optimizations. Project must have a direct relevance to identified military needs relating to military utility or cost reduction potential. Proposals should indicate potential transition paths to subsequent development or procurement phases. A technology insertion plan is encouraged and research that holds promise of insertion into Navy UUV mine detection and classification is of primary interest. B. GOALS. Detection and classification of bottom mines in littoral regions is a key requirement for future naval operations. One method postulated to support this requirement is the use of unmanned systems, specifically a UUV sized to enable operations from a submarine torpedo tube, a nominal 21-inch diameter and 240-inch length. While this has the benefit of clandestine operations and minimizing risk to personnel, it increases the already difficult challenges of mine detection and classification by limiting the allocations (weight, power, volume, heat dissipation, etc.) available to the mine detection and classification sensor system. Because of the limited allocations on a 21-inch UUV, the sonar solution is required to support a bottom-mounted, conformal implementation and can meet the system requirements in the harsh submarine undersea environments. The sonar solution must be designed to be able to withstand a full impulse launch. The peak axial acceleration during full impulse launch has been measured to be between 3 and 10g, with an exit velocity between 12 and 24 m/s. The purpose of this BAA is to obtain innovative solutions that advance the state of the art of sonar solution for high-resolution bottom mine detection and classification within the limitations imposed by operations onboard a 21-inch diameter, 240-inch long UUV. High-resolution in this context is defined as an area of 1.5-inch by 1.5 inch with a goal of 1 inch by 1 inch. Detection and classification ranges of up to 375 yards (threshold) and 500 yards (objective) in a Very Coarse Sand and Muddy Sand Bottom are required to support military needs. A sonar solution with multiple vertical elements is required to provide range-dependent receive beam narrowing for acoustic multi-path rejection. The specific developmental goals of this effort are to accomplish one or more of the following: a. Develop algorithms that enable detection and classification of bottom mine contacts within the constraints of a 21-inch diameter UUV platform. These algorithms include beam formation, image formation, motion compensation, and navigation. b. Develop hardware components, sub-systems, or systems that support detection and classification of bottom mine contacts within the constraints of a 21-inch diameter UUV platform. c. Develop system solutions (hardware, algorithms, and software) systems that support detection and classification of bottom mine contacts within the constraints of a 21-inch diameter UUV platform. d. Develop an interface and perform tests with a government 21-inch diameter UUV to validate the sonar system solution support detection and classification of bottom mine contacts 1. Scope of Requirement: Sonar Solutions for High-Resolution Bottom Mine Detection and Classification for Unmanned Undersea Vehicle (UUV) Applications is the focus of this BAA, but proposals will be considered for technology developments, demonstrations, and evaluations in the following areas (not prioritized) a. Sonar projectors, arrays, transducers b. Algorithms supporting beam forming, image forming, vehicle motion compensation, automatic target detection and classification c. Miniaturization of systems d. Data collection and reduction e. Manufacturing processes f. Survivability of systems, sub-systems, and components in harsh environments g. Test and evaluation of systems Proposals will be evaluated in part by their contribution to one or more of these areas of interest. These do not preclude submission in other areas considered by the offeror to have a high probability of interest to the UUV community. The government is not interested in funding enhancements to proprietary products, architectures or networks that may already exist in the commercial domain. 2. Projected Characteristics (NOTE: TABLE 1 AND TABLE 2 CAN BE OBTAINED BY CONTACTING MARIA GOULART): The following paragraphs describe some desired characteristics of future bottom mine detection and classification systems, sub-systems or components. The sponsor is interested in ensuring that funded projects are directly related to systems that ensure the success and welfare of the warfighter. Assumptions: For the purpose of this BAA, a 21-inch diameter UUV platform is assumed. To assist the offeror, notional system components are described in Table 1 to bound available platform resources and desired performance parameters. Additionally, desired overall performance parameters are provided. The Sonar solution shall be designed to perform per Table 1 as specified under any and all possible combinations of environmental conditions specified in Table 2. The Sonar solution shall meet Submarine Loading and Unloading requirements that involve transferring the UUV from the submarine main deck to the torpedo room. The Sonar solution shall meet the Submarine Shipboard shock environment which is the result of shock loadings associated with non-contact underwater explosions that the submarine may experience during attack conditions. The Sonar solution shall meet the shipboard shock requirements of MIL-S-901 at the Grade B level. The Sonar solution shall withstand unregulated flooding of the submarine torpedo tube at test depth of 1500 feet. The Sonar solution shall withstand impact with recovery systems. C. SUBMITTAL INSTRUCTIONS. 1. Potential vendors must submit their technical/management proposal (3 hardcopy) and cost proposal (1 hardcopy) with one CD-ROM no later than 1400 hours on 14 February 2005 to the following address: Commercial Acquisition Department - Building 11, Naval Undersea Warfare Center Division, Newport, Code 5911 ? M. Goulart, Simonpietri Drive, Newport, RI 02841-1708. 2. Proposals must be valid for 180 days from submission. Any classified information up to the SECRET level should be separated and forwarded to the Naval Undersea Warfare Division, Attn: Pamela Raposa, Code 10C, Building 990/1, 1176 Howell St., Newport, RI 02841-1708. The label should refer to BAA 050997. 3. Multiple awards may be made in response to this announcement. 4. All routine communication concerning this acquisition should be directed to Maria Goulart, (401) 832-6379, e-mail goulartmf@npt.nuwc.navy.mil. All technical related issues should be directed to Christos Agoros, email: agorosc@npt.nuwc.navy.mil; mail address Naval Undersea Warfare Center, Newport Division, 1176 Howell Street, Code 82201, Building 103, Newport, RI 02840. 5. Proposal length, exclusive of cost and pricing data, should not exceed twenty-five (25) 8? x 11 inch typewritten pages and should specify the technical area of concern addressed (i.e., Sonar Projectors, Algorithms, etc.) 6. Offerors should identify proposed costs with a breakdown of cost elements such as direct labor, overhead, G&A, fee or profit, and any other significant cost factors, with separate pricing provided for each proposed SOW Work Breakdown Structure (WBS). Pricing should be based upon the assumption that work would begin no sooner than 60 days after proposal submission. The proposal should also contain offeror?s point of contact information. 7. Subcontracting Plan Requirements: Offerors submitting proposals requiring a Subcontracting Plan in accordance with FAR 19.702 shall include a draft plan as an attachment to their price volume. If an offeror has a comprehensive subcontracting plan, the offeror shall so state in their price volume and provide a copy of the signature page of the Comprehensive Subcontracting Plan and any supplements to the plan, the identification number thereof and any pages identifying the subcontracting goals. Submitted plans must be approved by the PCO prior to contract award. 8. Proposals containing data that is not to be disclosed to the public for any purpose or used by the government except for evaluation purposes shall include the following statement on their title pages: ?The 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 this 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 these data to the extent provided in the resulting contract. This restriction does not limit the government?s right to use the information contained in this data if they are obtained from another source without restriction. The data subject to this restriction is contained on sheets (insert page numbers or otherwise identify the sheets)?. Each restricted data sheet should be marked as follows: ?Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal.? This statement may be in a small font and should be at the bottom only of each applicable page. 9. All material submitted to NUWCDIVNPT under this announcement shall be considered Government property. The Government requires unlimited data rights with regard to any procurement, with the possible exceptions of (1) a negotiated position for data rights to existing concepts that may be further developed under a procurement and (2) for efforts conducted under a procurement with leveraged funds. 10. For purposes of this solicitation, offerors should anticipate that contract awards will require a Contract Data Requirements List (CDRL) A that will vary depending on the nature of the contract award. For planning purposes, all awards will require the following data items as a minimum: DI-MISC-80508A - Scientific and Technical Reports (Contractor format); DI-MGMT-80368 - Status Report. Depending on what the contractual end items and deliverables are to be, the following may also be required as applicable: DI-DRPR-81002A - Developmental Design Drawings and Associated Lists; DI-MCCR-80700 - Computer Software Product End Items. 11. Contractor?s format and report consolidation are highly encouraged. Although not required, the government would prefer that offerors use electronic/digital media for report draft and publishable submittals. Microsoft Word 6.0 or above will be acceptable for submittal of draft documents, and the use of a CD-ROM is acceptable for the submittal of the final copy. The use of this media is primarily focused on documents that are to receive wide dissemination, such as final reports, but the offeror should consider proposing the use of electronic/digital media for any report for which this media is appropriate. Submittals on CD-ROM should be in a format that is compatible for any PC or Macintosh user. Reporting requirements will be identified per DD Form 1423. D. TECHNICAL/MANAGEMENT PROPOSAL CONTENTS. Format of Part I of the proposal shall be as follows (page limit of 25 single-sided pages): i. Cover Page. The cover page should include the BAA title and reference number, name and telephone number, fax and email for the principal points of contact (both technical and contractual), and the page should also contain the proprietary data disclosure statement, if applicable. ii. Table of Contents. It is highly recommended that the offeror follow this proposal outline format in the table of contents and use it for a final quality-control checklist. iii. List of Illustrations/Tables. This list is a quick reference of charts, graphs, tables, and other important information. iv. Executive Summary. The summary should present an organized progression of the work to be accomplished, without the technical details, so that the reader can grasp the core issues of the proposed program. The Executive Summary should rarely exceed two pages. 1.0 Technical Approach. In this section, the offeror should provide as much technical detail and analysis as is necessary or useful to support the technical approach they are proposing. The offeror must clearly identify the embedded instrumentation issue or challenge being addressed, and the technologies, (basic, applied research or exploratory development) to be leveraged or applied to form the ?new and creative? solution(s) proposed. It is not effective to address a variety of possible solutions to the technology problems unless each alternative is described in detail and the selection plan is fully discussed. 1.1 Application and Technical Discussion nature of the work: The preferred technical approach (including the advanced technology development nature of the work) should be described in as much detail as is necessary or useful to establish confidence in the approach. Every issue should be identified and compared with the successes/failures of previous approaches. A tradeoff analysis is a good way to make this comparison and should be supported by theory, simulation, modeling, experimental data, or other sound engineering and scientific practices. If the offeror has a ?new and creative? solution to the problem(s), that solution should be developed and analyzed in this section such that its feasibility can be assessed. 1.2 Technical Program Summary: This section summarizes the above technical discussion in an orderly progression through the program, emphasizing the strong points of the proposed technical approach, and how the proof of concept will be demonstrated and/or tested. 1.3 Risk Analysis and Alternatives: The proposal evaluator(s) will formulate a risk assessment and it is in the best interest of the offerors to have their own understanding of the risk factors presented. Critical technologies should be identified along with their impact on the overall program as well as risk mitigation strategies. 1.4 Transition or Insertion Plan: Discuss possible uses/users for this technology development, and suggestions for its production and dissemination. 1.5 References: Include the basis for, and reference, the findings cited in the technical discussion. 2.0 Special Technical Factors. In this section, the offeror should describe any capabilities the offeror has that are uniquely supportive of the technology to be pursued. The following items are offered as possible areas to be addressed. 2.1 Capabilities and relevant experience 2.2 Previous or current relevant R&D work and points of contact 2.3 Related contracts and points of contact 2.4 Facilities/resources 3.0 Schedule. The schedule represents the offeror?s commitment to perform the program tasks in an orderly, timely manner. 3.1 Time Line Chart by Task: Each major task identified in the SOW should appear as a separate WBS element on the program schedule. Decision gates and planned meetings, such as kick-off, presentations (including final presentation on the effort), design reviews, technical interchange meetings, demonstrations, tests, etc., should be included in the Time Line. The Time Line should also indicate the anticipated meeting sites. 3.2 Identify Milestones: Describe specific one-time events that would occur during the course of the project that would signify a decision point, government review, demonstration or test, or deliverable. 4.0 Program Organization. In this section, the offerors should present how they will be organized to conduct this project, and to address difficult technical issues. Any pertinent or useful information may be included in this section, but a minimum recommended response should address the following: 4.1 Organization Chart(s) with Key Personnel: Include prime offeror and team member organization charts. 4.2 Management and Technical Team: This should specifically identify what tasks will be performed by each party and why each subcontractor or team member, if any, was selected to perform its task(s). 4.2.1 Offeror Responsibilities 4.2.2 Subcontractor(s) or Team Member Responsibilities 4.2.3 Consultant(s) Responsibilities 4.3 Labor Mix Schedules (See http//www.ecraft.npt.nuwc.navy.mil/documents for a list of eCRAFT labor categories. 4.4 Resumes of Key Personnel: Include the resumes of the Key Personnel, be they offeror, subcontractor, team member, and/or consultant personnel. 5.0 Appendix(es). Appendices may include technical reports, published papers, and referenced material. Submission of commercial product advertising brochures as part of the Appendix(es) is not desirable. 6.0 Past Performance data for the company?s five most recent research contracts. (End Part 1 of 2 - BAA 050997)
 
Record
SN00728250-W 20050101/041230211941 (fbodaily.com)
 
Source
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.