SOLICITATION NOTICE
A -- Topical BAA for ?Analysis and Technical Assessment of High Energy Aluminum/Seawater Combustion Systems for Undersea Propulsion? (Part 2 OF 2)
- Notice Date
- 8/26/2005
- 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
- 055428-2
- Response Due
- 10/12/2005
- Archive Date
- 10/27/2005
- Description
- D. TECHNICAL/MANAGEMENT PROPOSAL CONTENTS. Format of Part I of the proposal shall be as follows (page limit of 20 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 the previously described 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 one page. 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. 1.1 Application and Technical Discussion nature of the work: The preferred technical approach should be described in as much detail as is necessary 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. 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 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. A listing of these reports/papers, with a short description of the subject matter, is usually adequate. Do not provide commercial product advertising brochures. 6.0 Past Performance: Past performance data for the entity?s five most recent research contracts. E. OFFEROR?S STATEMENT OF WORK. 1. It is the intent of the Government to attach the offeror?s SOW, as written, into the resulting award document. This will occur only if the offeror?s SOW accurately describes the work to be performed, is enforceable, and is void of inconsistencies. The proposed SOW must contain a summary description of the technical methodology as well as the task description, but not in so much detail as to make the SOW inflexible. Do not include any proprietary information in the SOW. 2. The following is offered as a recommended format for the SOW. Please limit the SOW to a maximum of three (3) pages. Begin this section on a new page. Start your SOW at Paragraph 1.0. 1.0 Objective: This section is intended to give a brief overview of the technology effort and should describe why it is being pursued, what you are trying to accomplish, and what aspect of this BAA Section A, ?Scope of Requirement? is being addressed. 2.0 Scope: This section should include the technology area(s) to be investigated, objectives/goals, and major milestones for the effort. 3.0 Background: This section includes any information, explanations, or constraints that are necessary in order to understand the requirements. It may include relationships to previous, current and future operations. It may also include techniques previously tried and found ineffective. The offeror shall identify appropriate specifications, standards, and other documents that are applicable to the effort to be performed. 4.0 Tasks/Technical Requirements: 4.1 The detailed description of tasks which represent the work to be performed, are contractually binding. Thus, this portion of the SOW should be developed in an orderly progression and in enough detail to establish the feasibility of accomplishing the overall program goals. The work effort should be segregated into major tasks and identified in separately numbered paragraphs according to the decimal system as described herein. Each numbered major task should delineate, by subtask, the work to be performed, deliverables and CDRL items. The SOW must contain every task to be accomplished. The tasks must be definite, realistic, and clearly stated. Use ?shall? whenever the work statement expresses a provision that is binding. Use ?should? or ?may? whenever it is necessary to express a declaration of purpose. Use ?will? in cases where no offeror requirement is involved; e.g., power will be supplied by the Government. Use active voice in describing work to be performed. 4.2 If presentations/meetings are identified in your schedule, include the following paragraph in your SOW: ?Conduct presentations/meetings at times and places specified in the award document.? 5.0 Exit Criteria and Deliverables: Propose criteria for establishing or indicating that a specific milestone or phase has been completed. List the deliverables that result from that milestone or phase. 6.0 Contract Data Requirements List (CDRL) Items: Submit required information per blocks on DD Form 1423. F. EVALUATION CRITERIA: Proposals will be evaluated by a scientific review. Per FAR 35.016(e), the primary basis for selecting proposals for award shall be technical competence (includes past performance); importance to NUWCDIVNPT programs; and, funding availability. Cost realism and reasonableness shall also be considered. Proposal risk will be individually assessed for the technical, cost, and schedule areas. Proposal risk relates to the identification and assessment of the risks associated with an offeror's proposed approach as it relates to accomplishing the proposed effort. Tradeoffs of the assessed risk will be weighed against the potential payoff. (END PART 2 OF 2) 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.
- Record
- SN00880905-W 20050828/050826213151 (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 |