Loren Data Corp.

'

 
 

COMMERCE BUSINESS DAILY ISSUE OF JANUARY 22,1998 PSA#2016

Office of Naval Research, 800 North Quincy St., Arlington, VA 22217-5660

A -- DUAL USE APPLICATIONS PROGRAM SOL BAA 98-005 DUE 031798 POC Glynis Fisher ONR, 251 (703) 696-2602 BAA 98-005 1. The Industrial Programs Department of ONR announces a program in the area of Dual Use Science and Technology (S&T). This program is being conducted in cooperation with DOD's Dual Use Applications Program (DUAP). ONR seeks projects to create and develop new product or process technologies which have potential for both Navy and commercial applications. If successfully developed, the technology will have both Navy relevance and sufficient potential commercial applications to support a viable production base. Approximately $20M of Government funds will be available for this Broad Agency Announcement (BAA). The proposer must be a for-profit company or have at least one for-profit firm on its team. The proposer must bear at least 50% of the cost of the proposed effort. Proposals should include schedules and budgets for a base term not to exceed 24 months. Costed options for an additional period of up to 36 months may be submitted. There is no guarantee that awards will be made in each of the identified topic areas. The Government may make awards on several proposals in a topic area depending in part on the cost of individual proposals and available funding. 2. Topic areas, with technical points of contact, which will be considered in this BAA are found at the end of this announcement. 3. Proposals that involve either basic research or final product development beyond the stage of product prototype or feasibility demonstration are outside the scope of this BAA competition and will not be acceptable. Readers should note that this is an announcement to declare ONR's intent to competitively fund dual use technology projects and that no request for proposals, solicitation or other announcement of this opportunity will be made. This notice constitutes ONR's BAA as contemplated by FAR 6.102(d)(2). Small businesses and historically black colleges and universities (HBCUs) and minority institutions (MIs) are encouraged to participate. Teaming arrangements among companies are encouraged when the result is a technically stronger proposal. Teaming with a DOD or national laboratory may also be advantageous in many instances. Due to limited funding, the Government reserves the right to limit awards under any topic, and only proposals considered to be of superior quality will be funded. Awards will be made using a class of nonprocurement instruments called Technology Investment Agreements, (i.e., Cooperative Agreements and Other Transactions). 4. This announcement is open until 1400 EST 17 March 1998. Any interested offeror should send five (5) copies of its technical and cost proposals to: Office of Naval Research, ATTN: ONR 362 DUAP, 800 North Quincy Street, Arlington, VA 22217-5660. To be considered for award, the full proposal must be received by ONR by the time and date indicated above. 5. Any interested company or institution is encouraged, but not required, to submit a white paper synopsis of the planned dual use S&T proposal including a rough cost estimate. White papers should address the selectioncriteria wherever possible and must identify which topic area it is being submitted under. The white paper should not exceed five (5) pages and should be submitted anytime during the first 15 days from date of this CBD announcement. The white paper may be emailed to the appropriate technical point of contact. Those submitting white papers are encouraged to continue to work on drafting a full proposal during the white paper evaluation process. The technical point of contact for the specified topic area will contact the white paper submitter and provide feedback on the Navy's level of interest in the proposed project. Based upon the degree of encouragement received, companies and institutions can better decide whether to continue the preparation of full technical and cost proposals for the described project. Offerors may submit full proposals without going through the white paper process. 6. Award decisions will be based on a competitive selection of proposals resulting from a peer and/or scientific review. Non-Government employees (under appropriate non-disclosure agreements) may be participating as reviewers in the evaluation of proposals. A committee chaired by Director, Defense Research and Engineering will have the final award authority. Evaluations will be conducted using the following evaluation criteria: 1) Technical Merit & Management Approach -- including impact on the cost or performance of current and/or future naval/defense systems; 2) Military Benefit -- including potential naval/defense relevance and contributions of the effort to the agency's specific mission; 3) Commercial Viability of Technology; 4) Quality and Amount of Cost Share (the proposer must bear at least 50% of project costs and at least 50% of the cost share must be high quality). B. TECHNICAL PROPOSAL Technical proposals should be a maximum of forty (40) pages and should include the four sections listed below. Offerors who include information in their proposals that they consider proprietary shall clearly delineate this restriction on both the title page and on each page containing information they wish to restrict and clearly mark the section which is considered proprietary. Section 1 -- Executive Summary: Provide a brief technical and business description of the contents of the proposal. The technical area should be written to cogently define your proposal's technical goals, the technical approach you are taking, and the expected technical result. Its purpose is to provide technical reviewers an overview of the technologies proposed. The business area should be written to explain strategic alliance, business, and market issues which successful commercialization and production will involve. It should reflect that the proposers have thought through the potential business, market, and economic implications if the technical goals of the project are achieved. If a consortia of performers are submitting the proposal, they should demonstrate that there is, indeed, a shared or common team vision. Section 2 -- Technical andManagement Issues: Give a detailed explanation of the technical approach, objectives, staffing and resources relating to the development of the proposed technology for both military and commercial use. This should include all of the following: A technical description of the technology which offers a superior, innovative or unique solution to a military problem, challenge or need. A technical description in sufficient detail to provide clear, quantifiable technical objectives and a technical approach with a schedule showing definite decision points and endpoints. A discussion that clearly lays out project risks and plans for dealing with them, including a statement of time-to-market considering available resources and the existing state-of-the-art. Note: technical risks are expected and acceptable provided they are well understood and realistic approaches are presented to mitigate them. A project team that includes all the resources needed to successfully develop the technology and turn it into a product or process. A project team that is organized for efficient and effective execution of the project. There should be clear, complementary roles for all members and clear lines of responsibilities and authority in the management of tasks and cost control. Section 3 -- Business Issues: Discuss the business issues that the proposer is facing and proposed commercialization development activities. This section should include all information necessary for evaluators to make an informed judgment regarding the business aspects of the proposed project as they relate to the selection criteria. While a formal business plan is not required, it is believed that the most readily accessible form for presenting a discussion of pervasive impact and commitment to production is to provide a business plan. Proposers should insure that their discussions at a minimum address the following points: a. Military Benefit: Projects should focus on technologies that will have a major impact on the cost, performance or sustainability of defense systems. In general, technologies that will have the greatest impact on the Nation's defense as well as those that will have a pervasive impact across a range of defense systems will be rated higher. Discuss how the ultimate product or process of this effort will benefit DON/DOD. Describe the technology's impact on the cost, performance or sustainability of defense systems. Lay out a clear path (specifically, the need and timing for planned system or upgrade) for the technology to be incorporated into the defense system(s). b. Commercial Viability of Technology -An objective of the DUAP is to obtain the economies of scale, accelerated product improvements, and increased sustainability inherent in the commercial marketplace for defense procurements. Thus, it is essential that a commercialization path for the proposed technology be identified and that potential commercial applications be sufficient to support a production base that would be capable of meeting future defense requirements. To be avoidedis a technology that would not be economically viable without significant military buys. Discuss the intended commercial markets. This should include a discussion of primary customers and the specific advantages accruing from this effort which will ensure an advantage over competitors. When lower cost is the basis for the competitive advantage of the proposed product or process, sufficient pricing data should be presented to permit evaluation of the claim. Discuss the long-term, commercial value of the proposed effort, in terms of both market share and the establishment of high quality job opportunities. This discussion will demonstrate how this commercial value justifies the proposed government investment. c. Cost Share and Risk: The technical proposal should demonstrate a commitment to share the cost and risk of the proposed effort with the Government. The proposal should include the following: Describe in detail the cost share for this effort, including the sources and the quality/type (cash, in-kind).High Quality Cost Share -- These are financial resources that will be expended on the proposed project's SOW and will be subject to the direction of the project management team. This basically means the funds the non-federal participants will spend for man-hours, materials, new equipment (prorated if appropriate) and subcontractor efforts expended on the project's SOW, and restocking the parts and material consumed. High quality cost share can include new IR&D effort, but only if those funds are offered by the proposers to be spent on the SOW and subject to the direction of the project management team. Low Quality Cost Share -- These are non-financial resources that will be expended on the proposed project's SOW and will be subject to the direction of the project management team. This is typically wear-and-tear on in-place capital assets like machinery or the prorated value of space used for the project. Unacceptable Cost Share -- This is a resource that either (1) will not be expended on the proposed project's SOW or (2) will not be subject to the direction of the management team as discussed above. Unacceptable cost share should be subtracted from the proposer's claimed total cost for the project, and the required industry cost share recalculated. Unacceptable cost share examples include: -- sunk costs, i.e., costs incurred before the start of the proposed project; -- foregone fees or profits; -- bid and proposal costs; -- value claimed for intellectual property or prior research; -- parallel research or investment, i.e., research or other investments that might be related to the proposed project but which will not be part of the SOW or subject to the direction of the project management team. Typically these activities will be undertaken regardless of whether the proposed project proceeds. -- Off-Budget Resources -- These are resources that will not be risked by the proposer on the SOW, and should not be considered when evaluating cost share. Provide the actual dollar values for the cost shared items in the separate cost proposal, not in the technical proposal. Discuss the business risks, if any, incurred by the proposer (or team member) other than the cost share described above. This could include any changes to corporate strategies, long-term commitment of resources or other consequential changes. Section 4 -- Selection Criteria Index: Provide a one page index showing the pages of the technical proposal on which each of the selection criteria are addressed. C. COST/FUNDING PROPOSAL Cost/funding proposals are not restricted in length, have no specific page layout requirements, and should address funding periods of performance. Work breakdown structures and certified cost or pricing data are neither required nor desired. Cost/funding proposals should be organized to include four sections in the following order: total project cost, cost sharing and in-kind contributions, cost to the Government, and off-budget supporting resources. These are described in more detail below. Section 1 Total Project Cost: This section will give a detailed breakdown of costs of the project. Cost should also be broken down on a task-by-task basis for each task appearing in the statement of work. This should include all of the proposed cost to the Government and cost sharing by the proposer. The following information should be presented in your proposal for each phase of the effort: total cost of the particular project phase; total proposer cost share; funding requested from the Government; and elements of cost (labor, direct materials, travel, other direct costs, equipment, software, patents, royalties, indirect costs, and cost of money). Sufficient information should be provided in supporting documents to allow the Government to evaluate the reasonableness of these proposed costs, including salaries, overhead, equipment purchases, fair market rental value of leased items, and the method used for making such valuations. Profit should not be included as a cost element. Section 2 -- Cost Sharing and In-Kind Contributions: This section will include: (1) the sources of cash and amounts to be used for matching requirements; (2) the specific in-kind contributions proposed, their value in monetary terms, and the methods by which their values were derived; and (3) evidence of the existence of adequate cash or commitments to provide sufficient cash in the future. Affirmative, signed statements are required from outside sources of cash. Proposals should contain sufficient information regarding the sources of the proposer's cost share so that a determination may be made by the Government regarding the availability, timeliness, and control of these resources. For example: How will the funds and resources be applied to advance the progress of the proposed effort? What is the role of any proposed in-kind contributions? What is the time phasing of the proposed cost sharing? (Cost sharing phasing which calls for disproportionately early funding by the Government with industry cost sharing being inserted late in the program is subject to renegotiation). Section 3 -- Cost to the Government: This section will specify the total costs proposed to be borne by the Government and any technical or other assistance including equipment, facilities, and personnel of Federal laboratories, if any, required to support these activities. The cost to the Government should be that portion of the proposed effort which is not covered by cost share. The costs incurred and work performed by any DOD or national laboratory "partnering" with the offeror under the proposal shall normally be considered costs of the Government and not costs of the proposer for purposes of the cost-sharing requirement. Proposals should contain sufficient information regarding the resources to be provided by the Government so that an evaluation of their availability, timeliness, and control may be made. Section 4 -- Off-Budget Supporting Resources: This section will show cash or in-kind resources which will support the proposed activity but which are not intended to be included in the total project cost. Items in this category do not count as cost share nor as Federal funds which must be matched. Examples of items to place in this category include: Commitments of cash or in-kind resources from other Federal sources, such as national laboratories, and projections of fee-based income where there is substantial uncertainty about the level which will actually be collected and where the income is not needed to meet cost-share requirements. D. PROPOSAL PAGE FORMATS All proposals should be printed such that pages are single-sided, with no more than fifty-five (55) lines per page. Use 21.6 x 27.9 cm (8 1/2 x 11 ) paper or A4 metric paper. Use an easy-to-read font of not more than about 5 characters per cm (fixed pitch font of 12 or fewer characters per inch or proportional font of point size 10 or larger). Smaller type may be used in figures and tables, but must be clearly legible. Margins on all sides (top, bottom, left and right) should be at least 2.5 cm. (1"). E. ORALS, INTERVIEWS, AND SITE REVIEWS During the proposal review and final stages of the selection process, some proposers may be asked to provide clarification and/or oral presentations to members of the selection panel or to travel to Washington D.C. or other location for an interview. ONR also reserves the right to conduct site reviews prior to award of assistance agreements. F. REPORTING REQUIREMENTS AND METRICS All awardees receiving agreements under this BAA will be required to develop a commercialization plan for the activity stimulated by the award. Awardees will be required to make periodic reports on technical progress and financial outlays associated with their project(s), and, in addition, awardees will report on the progress towards the stated project goals. The awardees may be requested to continue these periodic reports beyond the conclusion of the actual term of the agreement. G. TOPIC AREAS The twelve topic areas under consideration are listed below. All questions should be directed to the Navy technical point of contact identified under the specific topic area. 1. Topic Area: SHIP SERVICE FUEL CELL POWER SYSTEM Significant advances in commercial fuel cell technology in non-marine applications have occurred in the 1990's which now make fuel cells an attractive option for Naval ship service electrical power. The objective of the Ship Service Fuel Cell Power System (SSFC) project is to demonstrate that this commercially developed technology can be adapted to marine applications and provide the fleet with an affordable alternative source for ship service electrical power. The project will address the specific issues required to apply the commercially developed fuel cell technology for Naval shipboard applications; such as, Naval logistics diesel fuel (NATO F-76), compact fuel reformer and desulfurizers, power density and packing, duty cycle and operating requirements, control issues and interface with shipboard load requirements, overload capability, marine environmental contaminants (salt laden environment, etc.), ship motion, shock and vibration, signatures (thermal, magnetic and acoustic) and reliability, maintainability and cell life. The technical approach is to demonstrate that commercially developed fuel cell technology can operate on navy logistic fuel in a marine environment. A conceptual design for a (0020)

Loren Data Corp. http://www.ld.com (SYN# 0008 19980122\A-0008.SOL)


A - Research and Development Index Page