Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF AUGUST 04, 2016 FBO #5368
MODIFICATION

A -- RESEARCH AND DEVELOPMENT OF NEXT GENERATION NAVAL INTEGRATEDPOWER SYSTEMS

Notice Date
8/2/2016
 
Notice Type
Modification/Amendment
 
NAICS
335311 — Power, Distribution, and Specialty Transformer Manufacturing
 
Contracting Office
N00024 Naval Sea Systems Command, DC 1333 Isaac Hull Avenue S.E.Washington Navy Yard, DC
 
ZIP Code
00000
 
Solicitation Number
N0002410R4215
 
Archive Date
2/24/2017
 
Point of Contact
Joseph Tannenbaum, Phone: 202-781-2629, Jessie Rehwoldt, Phone: 2027815282
 
E-Mail Address
joseph.tannenbaum@navy.mil, jessie.rehwoldt@navy.mil
(joseph.tannenbaum@navy.mil, jessie.rehwoldt@navy.mil)
 
Small Business Set-Aside
N/A
 
Description
Synopsis: I. ADMINISTRATIVE INFORMATION This publication constitutes a Broad Agency Announcement (BAA) as contemplated in Federal Acquisition Regulation (FAR) 6.102(d)(2). A formal Request for Proposals (RFP), solicitation, and/or additional information regarding this announcement will not be issued or further announced. This announcement will remain open for approximately one year from the date of publication or until extended or replaced by a successor BAA. Initial responses to this announcement must be in the form of White Papers. Proposals shall be requested only from those offerors selected as a result of the scientific review of the White Papers made in accordance with the evaluation criteria specified herein. White Papers may be submitted any time during this period. Awards may take the form of contracts, cooperative agreements, or other transactions agreements. The Naval Sea Systems Command (NAVSEA) will not issue paper copies of this announcement. NAVSEA reserves the right to select for proposal submission all, some or none from among the white papers submitted in response to this announcement. For those who are requested to submit proposals, NAVSEA reserves the right to award all, some or none of the proposals received under this BAA. NAVSEA provides no funding for direct reimbursement of white paper or 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 NAVSEA to treat all white papers and proposals as competition sensitive information and to disclose their contents only for the purposes of evaluation. This announcement formally cancels the Advanced Research and Development in Naval Integrated Power Systems BAA issued under announcement N0002405R4201. White papers submitted under N0002405R4201 that have not resulted in a request for a proposal are hereby considered closed-out and no further action will be taken on them. Unsuccessful Offerors under N0002405R4201 are encouraged to review this BAA for relevance and resubmit if the technology proposed meets the criteria below. II. GENERAL INFORMATION 1. Agency Name Naval Sea Systems Command (NAVSEA) 1333 Isaac Hull Ave SE Washington, DC 20376 2. Research Opportunity Title Research and Development of Next Generation Naval Integrated Power Systems 3. Response Date This announcement will remain open for approximately one year from the date of publication or until extended or replaced by a successor BAA. White Papers may be submitted any time during this period. 4. Research Opportunity Description The Naval Sea Systems Command (NAVSEA) is interested in White Papers for long and short term Research and Development (R&D) projects that offer potential for advancement and improvements in the implementation of shipboard Integrated Power Systems (IPS) and Integrated Power and Energy Systems (IPES) at the major component, subsystem and system level. IPS provides total ship electric power including electric propulsion, power conversion and distribution, energy storage, combat system support and ship mission load interfaces to the electric power system. IPES adds integrated energy storage and advanced controls to IPS in order to accommodate future High Energy Weapons and Sensors. The IPES Energy Magazine is available to multiple users, and provides enhanced power continuity to the power distribution system. The flexibility of electric power transmission allows power generating modules with various power ratings to be connected to propulsion loads and ship service in any arrangement that supports the ship's mission at the lowest total ownership cost (TOC). Systems engineering in IPS/IPES is focused on increasing the commonality of components used across ship types and in developing modules that will be integral to standardization, zonal system architectures, and generic shipbuilding strategies with standard interfaces that are Navy controlled. The modules or components developed will be assessed for applicability both to next generation shipboard electrical architectures and combat systems and to back-fit opportunities that improve the energy efficiency and mission effectiveness in the current fleet. NAVSEA wishes to continue to improve IPS/IPES by performing analysis, modeling and simulation, life cycle cost analysis, producibility studies, module development, ship integration, architecture design, ship electric architectures and support for high power weapons systems requirements, and related efforts. An evaluation of emerging technologies for ship applications (such as fuel cells, support for high energy weapons, support for high power radars, high-speed generators, and advanced power electronics) to determine future feasibility and development requirements will be conducted. The approach to hardware developed under this BAA is that it fosters modularity and scalability (so that families of products may be leveraged to multiple potential applications) and shall accommodate an open system architecture where interfaces are well defined and mutually accepted. Electric Ships Office: The Navy has initiated the Next Generation Integrated Power Systems (NGIPS), Naval Power Systems (NPS) and Naval Power and Energy Systems (NPES) efforts with centralized leadership by the Electric Ships Office (ESO). The mission of the ESO (PMS 320, organizationally a part of the Program Executive Office - Ships) is to develop and provide smaller, simpler, more affordable, and more capable ship's power systems for all Navy platforms by defining open architectures, developing common components, and focusing Navy and industry investments. The ESO will provide leadership of the developments identified as part of this BAA, will direct the transition of associated technologies developed by the Office of Naval Research (ONR), and will manage the technology portfolio represented by Program Element (PE) 0603573N (Advanced Surface Machinery Systems) for transition into existing and future Navy ships. The guiding document that will be used to define the module developments that advance the NGIPS vision is the Next Generation Integrated Power System (NGIPS) Technology Development Roadmap, Naval Sea Systems Command Ser 05D/349 of 30 Nov 2007, which is publicly available under announcement N0002408R4123. The latest edition is the 2015 Naval Power and Energy Systems Technology Development Roadmap (NPES TDR), which is available publicly on the NAVSEA web site. The areas of focus for White Papers and Proposals submitted in response to this BAA should include, but are not limited to, the analysis, development, risk reduction and demonstration of future shipboard electric power systems and components, emphasizing shipboard power generation, electric propulsion, power conversion, energy storage, distribution and control; power quality, continuity, and system stability; electric power system/component level modeling and simulation; energy storage technologies; electrical system survivability; simplicity and ruggedness. The Integrated Power and Energy System Architecture provides the framework for partitioning the equipment and software into modules and defines functional elements and the power/control and information relationships between them. For power generation, high power distribution, propulsion, and large loads, the architecture includes Medium Voltage AC power (with emphasis on affordability), High Frequency AC power (with emphasis on power density), and Medium Voltage DC power (with emphasis on power density and fault management). For ship service electrical loads, the architecture includes zonal electrical distribution which may be either AC or DC, depending upon the specific application. In addition to a full IPS implementation, modules that support a partially integrated power system, or Hybrid Electric Drive (HED) where mechanical propulsion is augmented by rotating electric machinery, or additional power generation or energy storage shall be considered. Also of particular interest are technologies that result in significant energy efficiency, power density improvements and/or carbon footprint improvements over existing propulsion and power system technologies. The NGIPS roadmap partitions the power system components functionally into modules. Those modules, subsystems and systems of interest include the following. Power Generation Module (PGM): A Power Generation functional element converts fuel into electrical power. The electrical power is transferred to one or more Power Distribution functional elements. An associated Power Generation module might typically consist of a gas turbine or diesel engine (prime mover), a generator, a rectifier (either active or passive), auxiliary support sub-modules and module controls. Other possible technologies include propulsion derived ship service (PDSS), fuel cells, or other direct energy conversion concepts. Power Generation concepts include 60 Hz wound rotor synchronous generator driven directly by a marine gas turbine (up to 30 MVA rating); 4 pole, 120 Hz, commercially derived or militarized design variants of the above; and higher speed, higher frequency, high power density variants of the above with high speed or geared turbine drive. Navy interests are in the area of innovative approaches to Power Generation concepts rated in the 5 to 30 MW range, utilizing gas turbine, diesel engines and other emerging power technologies that address challenges associated with achieving reduced fuel consumption, decreased life cycle and acquisition cost, support of ship integration, and improved environmental compliance. The specific design issues to be considered include fuel efficiency, module level power density, machine insulation system characteristics, size, weight, cost, maintainability, availability, harmonic loading, voltage, power, system grounding approaches, fault protection, response to large dynamic (step) or pulse type loading originated from ship propulsion or directed energy/electromagnetic weapons, interface to main or ship service bus, and commercial availability. Near term (2016-2017) interest is focused on the 20-30MW (nominally 25MW) output power rating and the power generation source able to supply two independent (where abnormal conditions on one bus does not impact the other bus) electrical buses at 12 kVDC. The Navy is interested in developing a knowledge bank of information on potential generator sets; the generator's electrical interface requirements; and the impacts of those requirements on generator set performance and size, as a logical next step from the Request For Information released under announcement N0002416R4205. A long-term goal for this effort is to maximize military effectiveness through design choice and configuration option flexibility when developing next-generation distribution plants. The power generation source must fit within the length of a typical DDG 51 Class engine room (46 feet, including allowances for any needed maintenance and component removal). The PGM is expected to have the ability to control steady-state voltage-current characteristic for each interface; ability to maintain stability; and the ability to adjust control set-points from system level controllers. For any proposed design approach, initial efforts would include conceptual design trade studies that inform the performance level that can be achieved. Trade studies may address Pulsed Load Capability (generator/rectifier design to increase pulse load capability, engine speed variation limits, and impact of cyclic pulse load on component life); Power Density (cost vs. benefits of high speed or high frequency, mounting on common skid, and advanced cooling concepts); Single vs. Dual Outputs (continuous vs. pulse rating for each output, voltage regulation with shared field, and control of load sharing); Efficiency (part load vs. full load optimization, flexible speed regulation, impact of intake and exhaust duct size/pressure drop on engine efficiency); Power Quality (voltage transient, voltage modulation for step, pulse loads, impact of voltage and current ripple requirements, and common mode current); PGM Controls (prime mover speed vs. generator field vs. rectifier active phase angle control, and pulse anticipation); Stability when operating in parallel with other sources; Short Circuit Requirements; and Dark Ship start capability (self-contained support auxiliaries). Trade studies may also address how rotational energy storage can be built into the design of the generator and what parameters need to be defined in order to exploit this capability. Power Distribution Module (PDM): A Power Distribution functional element transfers electrical power between other functional elements. Fault protection systems should be designed, if possible, to not require the power distribution modules to communicate control signals with any functional element other than system control. An associated Power Distribution module might typically consist of bus duct, cables, switchgear and fault protection equipment. Power Conversion Module (PCM): A Power Conversion functional element converts electrical power from one form to another. An associated Power Conversion module might typically consist of a solid state power converter and/or a transformer. Advanced topologies and technologies, such as the application of wide band gap devices, will be considered. Navy interests are in the area of innovative approaches to address 4160 VAC or 450 VAC to 1000 VDC Power Conversion Module development with power levels on the order of 3MW (analogous to the PCM-1A on the NGIPS Technology Development Roadmap). The specific design issues to be considered include modularity, open architecture, reliability, cost, and conversion efficiency. The current baseline is 32,800 lbs and 168"W x 54"D x 81"H. Target space and weight for a PCM-1A are 3,500 lbs and 60"W x 60"D x 60"H, with a threshold of a two-times improvement to the baseline power density. Power Load Module (PLM): A Power Load functional element is a user of electrical power received from one or more Power Distribution functional elements. The area of interest for the Power Load is the load interface definition and the provision of specialty power to optimize that load interface. Among the special load interfaces that would require development are support for pulsed power weapons and sensors such as radar power supplies, electromagnetic launchers (for example EM Railgun), and advanced laser systems, all of which would benefit from optimized integration with the shipboard power system. This would enable real time data and asset management and reconfiguration based on demand. The Navy has an interest in initiating the development of a capacitor based rep-rate pulsed power system with similar capabilities to that described in Office of Naval Research (ONR) announcement 10-RFI-0001. Concepts that align with the technology development required for the Electromagnetic (EM) Railgun and also support shipboard energy storage needs will be considered by both the Electric Ships Office and ONR for award. As an update to the industry caucus on December 2, 2009 under ONR solicitation 10-RFI-0001, the nominal module rating of 250 kilo-joules (kJ) and an energy density of 1.3 mega-joule-per-cubic-meter (1.3MJ/m^3) is contemplated. The energy density goal for the pulsed power component (excluding bus-work to launcher) is 1.3 MJ/m^3 or better. Reducing system volume is important, but this has to be balanced with system fault tolerance and cost. The Electric Ships Office (PMS 320) in conjunction with ONR is interested in both near term solutions that have the potential for rapid transition to a high Technology Readiness Level (TRL) as well as longer term technology pushes that advance the science and would enable a future compact shipboard system. Risk reducing technology prototype demonstrations in the near term are encouraged. Propulsion Motor Module (PMM): Electric propulsion motors and propulsion motor drives are large electrical loads as well as NGIPS modules. Candidate propulsion motor concepts include Permanent Magnet Motors (radial air gap, axial air gap, or transverse flux), Induction Motors (wound rotor or squirrel cage), Superconducting field type (homopolar DC or synchronous AC). The drivers and issues associated with these designs include acoustic signature, noise (requirements, limitations, modeling, sources, and mitigation methods), shock, vibration, thermal management, manufacturing infrastructure, machine insulation system characteristics, commercial commonality, platform commonality, cost, torque, power, weight, diameter, length, voltage, motor configuration, and ship arrangements constraints. Motor drives that may be explored include cycloconverter (with variations in control and power device types), pulse width modulated converter/inverter (with many variations in topology), switching (hard switched, soft switched), and matrix converter (with variations in control, topology, cooling, power device type). Technologies for drives and rotating machines which allow the ability to operate both as a motor and a generator to facilitate a propulsion derived ship service (PDSS) installation or on a fully integrated power system to leverage the inherent energy storage in the ship's motion may be explored. Integrated motor/propulsor concepts may be considered either as aft-mounted main propulsion or as a forward propulsor capable of propelling a ship at a tactically useful speed. Energy Storage Module (ESM): An Energy Storage functional element stores energy. A number of alternative energy storage technologies and/or configurations (location within the distribution system and capacity) may be considered for future ship applications, such as battery, capacitor-based, fly wheel, or superconducting energy storage. Shipboard power quality and continuity along with examination of the implications of future high power/pulse power loads on configuration/technology alternatives is critical. Energy storage modules may consist of short duration (micro/milli second), mid duration (5 to 30 minutes), or long duration (>30 minutes/hours) energy storage applications which utilize a combination of technologies to minimize power quality and continuity impacts across the system. For the short duration energy storage applications, the ESM should provide hold-up power to uninterruptible loads for fault clearing and transient isolation, as well as load leveling for pulse power loads. For the mid duration, the ESM should provide up to approximately 3MW of standby power for pulse power loads while also providing continuity of operations for a subset of equipment between uninterruptible and full ship's load (including emergency power generation starting in a dark ship condition). For long duration applications, ESMs should provide the required power as an emergency backup system or to provide increased stealth for specialty equipment. The required duration for this type of application may extend up to days or longer, and may be intermittent or continuous. Near term interests are in the area of common and scalable hardware and software elements which enable advanced weapons and sensors while reducing risk of single generator operations and increasing fuel savings. The specific design issues to be considered include reliability, volumetric and gravimetric power and energy densities, differentiating between high levels of stored energy and high energy density. The relevant information required for characterizing technology performance include: production capability (number of cells produced per year, kWh/MWH per year); Technology Readiness Level (TRL) of components and systems; safety evaluation and qualifications performed on relevant subsystems or components (any hazard analyses of systems designs as relevant to notional applications); other military application of the devices; energy storage management system approach; thermal characteristics, constraints, and cooling requirements; auxiliary requirements (load); device impedance (heat generation characteristics); and device efficiency (discharge/recharge). Power System Control (PCON): A System Control functional element consists of the software necessary to coordinate multiple other functional elements. A System Control Functional Element receives information from other functional elements and external (non-IPS) systems. Similarly, a System Control functional element may receive control commands from or negotiate control actions with external systems and other functional elements. System Control manages the power and energy flow within the ship to ensure power is delivered to the right load in the right form at the right time. While various forms of power control have been implemented on commercial IPS ships, the survivability requirements for military ships combined with the pulse load characteristics for some of the loads described above will require more sophisticated algorithms than are commercially available. A System Control functional element resides on an external distributed computer system and therefore typically does not include hardware elements (unless specialized hardware is required). Energy Efficiency Enabling Technologies (E3T): Improving energy efficiency and energy management aboard ship by application of advanced electrical distribution and propulsion system related technologies is a Navy priority. E3T submissions may include technologies, modifications, and/or new components to existing and future ship systems that will increase the efficiency of electrical systems or facilitate the utilization of renewable energy sources to lower fuel and energy consumption on US Navy Ships. The areas of interest include but are not limited to propulsion, electrical distribution systems, electrical equipment, power conversion, and power generation. The Navy will consider approaches that modify systems and/or operations to affect quantifiable energy conservation in the Fleet. Emphasis is placed on technologies with an identified transition path capable of making near-term, measurable improvements to Navy energy conservation. This effort will be in conjunction with the requirements provided in the Naval Surface Warfare Center announcement N00167-11-BAA-01, which looks at similar technologies for application to Military Sealift Command vessels, and ideas will be shared with sponsors in both applications. Included in the scope of the BAA are development activities as described further in the Naval Power Systems Technology Development Roadmap (NPS TDR) available on the NAVSEA web site and released to industry under announcement N0002413R4217. A revision of the Technology Development Roadmap is presently in draft and will be released by separate announcement. Included in the scope of the BAA are development activities as described further in the Naval Power and Energy Systems Technology Development Roadmap (NPES TDR) available on the NAVSEA web site. 5. Point(s) of Contact Questions of a technical nature should be submitted to Mr. Joseph Tannenbaum, NAVSEA PMS 320, on 202-781-2629 or email at joseph.tannenbaum@navy.mil. Questions related to procurement issues shall be addressed to Ms. Jessie Rehwoldt, NAVSEA 024 on 202-781-5282 or email at jessie.rehwoldt@navy.mil. Prior to preparing White Papers/Proposals, potential Offerors are strongly encouraged to contact the NAVSEA points of contact to determine the reasonability and interest in the proposal topic. III. AWARD INFORMATION The amount and period of performance of each selected proposal will vary depending on the research area and the technical approach to be pursued by the selected Offeror. IV. ELIGIBILITY INFORMATION All responsible sources from academia and industry may submit white papers under this BAA. V. APPLICATION AND SUBMISSION INFORMATION 1. Application and Submission Process "White Papers" are desired by NAVSEA in response to this solicitation. Those offerors with white papers considered to have merit will be requested to prepare full proposals for the planned effort as specified below. There will be no notification of an unsuccessful white paper. Receipt of all white papers will be acknowledged by the Technical Point of Contact listed above. White papers will be retained by the Navy and, should an application and associated funding be identified for the concept proposed, additional responses will be requested of the Offeror. 2. General Information for White Papers/Full Proposals The white papers and proposals submitted under this BAA are expected to be unclassified. The proposal submissions will be protected from unauthorized disclosure in accordance with FAR 15.207, applicable law, and Department of Defense (DoD)/Department of Navy (DoN) regulations. Offerors are expected to appropriately mark each page of their submission that contains proprietary information. 2.1. White Papers 2.1.1 White Paper Format The page limit for white papers shall not exceed five (5) pages. Paper size shall be no larger than 8.5" x 11" paper with no less than 1" margins on all sides. The font shall not be less than12 point. The format of the submission shall be one electronic copy on a CD-ROM, in Microsoft TM Word or Excel compatible or.PDF format, and may be accompanied by one (1) original paper copy. Electronic submission may also be made directly by sending an e-mail to joseph.tannenbaum@navy.mil. 2.1.2 White Paper Content 2.1.2.1 Cover Page The Cover Page shall be labeled "WHITE PAPER," and shall include the BAA number, proposed title, and technical/administrative points of contact with telephone numbers and e-mail addresses. 2.1.2.2 Technical Concept The Technical Concept shall include a description of the technology innovation and associated technical risk areas. This section also includes a description of the potential naval relevance and contributions of the proposed effort to improvement in the performance of an IPS. This section may include a plan for demonstrating and evaluating the operational effectiveness of the Offeror's proposed products or processes in field experiments and/or tests in a simulated environment. The Technical Concept section shall clearly identify the applicability of the concept to the modules described in the NGIPS Technology Development Roadmap. 2.2 Full Proposals 2.2.1 Full Proposal Format The page limit for Volume 1 of Full Proposals shall not exceed thirty (30) pages, excluding resumes and examples of past performance. There are no page limitations to Volume 2. Paper size for Volume 1 shall be no larger than 8.5" x 11" paper with no less than 1" margins on all sides. The font shall not be less than12 point. The format of the submission shall be one electronic copy on a CD-ROM, in Microsoft TM Word or Excel compatible or.PDF format, and may be accompanied by one (1) original paper copy. Electronic submission may also be made directly by sending an e-mail to joseph.tannenbaum@navy.mil. 2.2.2 Full Proposal Content 2.2.2.1 Volume 1: Technical Proposal 2.2.2.1.1 Cover Page The Cover Page shall be labeled "TECHNICAL PROPOSAL," and shall include the BAA number, proposed title, the Offeror's Commercial and Government Entity (CAGE) Code, a complete list of subcontractors, and technical/administrative points of contact with telephone numbers and e-mail addresses. The Cover Page shall also include cognizant Defense Contract Audit Agency (DCAA) and Defense Contract Management Agency (DCMA) points of contact, addresses, phone numbers, and electronic mail addresses. 2.2.2.1.2 Table of Contents 2.2.2.1.3 Technical Concept The Technical Concept shall be a reiteration of the Technical Concept provided in the White Paper and may include any updated or amplifying information. The Technical Concept section shall clearly identify the applicability of the concept to the modules described in the NGIPS Technology Development Roadmap. No references shall be made to documents other than the NGIPS Technology Development Roadmap. 2.2.2.1.4 Statement of Work A Statement of Work (SOW) clearly detailing the scope and objectives of the effort and the technical approach. If a SOW is provided as part of the request for Full Proposal, the SOW included in the proposal shall be a red-line of that SOW, highlighting and changes recommended by the Offeror. Proposals shall include a severable self-standing SOW without any proprietary restrictions, which can be included in the contract or agreement award. When options are contemplated, the SOW must clearly identify separate optional task areas. The Offeror shall include as an aspect of all phases of development in the SOW the provision of characterization data for use by the Navy design team in conduct of NGIPS indicative ship design studies. The data shall be provided for any point design and/or as parametric data over a range of application requirements. The Navy will provide the list of design parameters required for the proposed technology as Government Furnished Information after contract award. Point design data will be used as a benchmark for comparison for demonstration equipment developed under the contract. Executable computer models shall be provided for the Navy to conduct modeling of equipment performance parameters and control algorithms. Upon completion of the development and testing of any demonstration equipment, the point design and/or parametric data and/or computer models shall be updated to reflect lessons learned. To support Navy return on investment analysis, the Offeror may be required to provide rough order of magnitude cost estimates for cost elements such as Development Cost; Software Development Cost; Procurement Cost; Unit Production Cost; and Maintenance Cost. In order to make further use of any product of this development, the Navy will own the interface specification for the component or module tobe developed and would need independent industry and academia validation of that interface. The Offeror shall include as an aspect of all phases of development in the SOW the development and provision of a stand alone technical specification for the component or system being developed. This specification shall comply with Navy standards for such specifications and shall completely describe the performance characteristics of the technology development in such a manner as to allow for future procurement of the item. The specification shall not be marked with any restrictive markings. 2.2.2.1.5 Project Schedule and Milestones Include here a summary of the schedule of events and milestones. 2.2.2.1.6 Assertion of Data Rights Include here a summary of any proprietary rights to pre-existing results, prototypes, or systems supporting and/or necessary for the use of the research, results, and/or prototype. Any rights claimed in other parts of the proposal that would impact the rights in this section must be cross-referenced. If there are proprietary rights, the Offeror must explain how these affect its ability to deliver subsystems for integration. Additionally, Offerors must explain how the program goals are achievable in light of these proprietary and/or restrictive limitations. If there are no claims of proprietary rights in pre-existing data, this section shall consist of a statement to that effect. In order for a data rights assertions list to be accepted by the Government and included as an Attachment to a contract, the DFARS (252.227-7013 and 252.227-7014) requires that the information be listed in a table having four columns. In the first column, technical data to be furnished with restrictions, for non-commercial technical data items, both the item and the technical data pertaining to that item must be listed. Also, the assertion must be made at the lowest component level. And since technical data is defined as "recorded information of a scientific or technical nature", a document where the technical data is recorded must also be listed. This is usually, but not always, a drawing number. Non-commercial computer software items should similarly be listed at the lowest practicable subroutine level and should also list a version number. 2.2.2.1.7 Deliverables Include here a detailed description of the products to be delivered in hardware and paper/electronic form. The SOW shall include a summary listing of these deliverables. The deliverables list shall minimally include a Program Plan/Integrated Master Schedule, Technical and Financial Progress Reports, Meeting Minutes, and Technical Documents/Reports. 2.2.2.1.8 Management Approach A discussion of the overall approach to the management of this effort, including brief discussions of the total organization; use of personnel; subcontractor relationships; Government research interfaces; and planning, scheduling and control practices. Identify which personnel and subcontractors (if any) will be involved. Submit resumes/curriculum vitae for the key personnel identified. Include a description of the facilities that are required for the proposed effort with a description of any suggested Government furnished equipment, hardware, software, and/or information required, by version and/or configuration. 2.2.2.1.9 Past Performance Offerors shall provide all relevant past performance for similar or related work under contracts currently being performed or completed during the last three (3) years. The Offeror may include Federal, State and Local Government and private sector contracts. Offerors that represent newly formed entities, without prior contract experience, should identify previous contract and subcontract experience for all key personnel identified in the proposal. The following information for each such contract shall be provided: 1. Contract Number 2. Customer/Agency 3. Contracting Officer and Technical Point of Contact (names and phone numbers) 4. Brief Description of Scope of Work and Deliverables 5. Contract Type 6. Award Price/Final Price 7. Period of Performance 2.2.2.2 VOLUME 2: Cost Proposal 2.2.2.2.1 Cover Page The submission of cost or pricing data in accordance with FAR 15.403.4 is mandatory if the Offeror's proposed cost exceeds $550,000.00. The words "COST PROPOSAL" shall appear on the cover page in addition to the following information: 1. BAA number. 2. Title of Proposal. 3. Identity of prime Offeror and complete list of subcontractors. 4. Technical contact (name, address, phone, e-mail address) 5. Administrative/business contact (name, address, phone, e-mail address). 6. Summary statement of proposed costs. 7. Cognizant DCAA and DCMA point of contact, address, phone, e-mail address. 8. The Offeror's CAGE Code 2.2.2.2.2 Part 1 Include here a detailed breakdown of all costs by cost category and by calendar/fiscal year (when options are contemplated, options must be separately identified and priced by calendar/fiscal year). Cost categories include: a. Direct Labor - Individual labor category or person, with associated labor hours and unburdened direct labor rates; b. Indirect Costs - Fringe Benefits, Overhead, G&A, COM, etc. (must show base amount and rate); c. Proposed contractor acquired equipment and/or materials shall be specifically itemized with associated costs (unit costs, quantities, and total costs). An explanation of the basis of estimates (including derivation from previous purchase orders, supplier quotes, or engineering estimates) shall be provided. Where possible, indicate purchasing method (competition, price comparison, market review, etc.). d. Travel - Number of trips, destinations, duration, etc; e. Subcontract - A cost proposal as detailed as the Offeror's cost proposal will be required to be submitted by the subcontractor. The subcontractor's cost proposal can be provided in a sealed envelope with the Offeror's cost proposal or will be requested from the subcontractor directly at a later date; f. Consultant - Provide consultant agreement or other document which verifies the proposed loaded daily/hourly rate; g. Other Direct Costs and; h. Fee/Profit including fee percentage. 2.2.2.2.3 Part 2 Cost breakdown by task/sub task corresponding to the same task numbers (or work breakdown structure) in the SOW. When options are contemplated, options must be separately identified and priced by task/sub-task corresponding to the same task numbers in the SOW. 2.2.2.2.4 Associated Engineering Services The Offeror shall, at the option of the Government, also furnish the services of qualified engineers/technicians and management functions to perform engineering support for follow-on investigations, additional trade studies, and hardware evaluations to determine the effectiveness of the new technologies developed under the basic effort. The nature of the services to be performed shall be non-severable from the scope of the remaining aspects of the contract and shall be integrally related to the core scope of the contract, shall form a logical extension of the work otherwise performed (such as completion of testing of articles developed or extending the performance capability of the articles developed), or shall provide amplifying details of the articles or technologies beyond that otherwise required and shall result in a specific end-product, such as a report. The services shall cover the investigation of potential alternative technologies on suitable demonstration vehicles, working in support of Navy objectives. The Offeror shall furnish materials and subcontracting incidental to the engineering services and as necessary to perform the efforts specified. If the basic efforts prove that the technology proposed would be beneficial and warrant continued development, additional phases like preliminary design, detail design, prototype fabrication, and factory and Navy testing may be initiated making use of the Engineering Services. The full scope of follow-on phases may be implemented by the inclusion of additional Contract Line Items (CLINs) separately negotiated post basic contract award following customary contracting procedures. Funding for Engineering Services may be from R&D, Ship Construction, Operation & Maintenance; or Other Procurement sources as may be appropriate for the follow-on activity required, but shall not be used for production of any technology proposed. VI. EVALUATION INFORMATION 1. Evaluation Criteria 1.1. White Papers Evaluation of the "White Papers" will be based on a competitive selection resulting from a scientific review using the following evaluation criteria: (1) overall scientific and technical merits of the concept; and (2) potential Naval relevance and contributions of the effort to the improved performance of NGIPS modules and architectures. Selection of the Offeror(s) from which Full Proposals will be requested, will be based upon the Government's assessment of Items (1) and (2) and the availability of funds to accomplish the proposed effort. 1.2. Full Proposals Award decisions will be based on a competitive selection of proposals resulting from a scientific review. Evaluations will be conducted using the following evaluation criteria: (1) overall scientific and technical merits of the proposal; (2) potential naval relevance and contributions of the improved performance of NGIPS modules and architectures; (3) the Offeror's capabilities, related experience, past performance, facilities, the qualifications/capabilities and experience of the proposed Principal Investigator, team leader and key personnel who are critical in achieving the proposal objectives; and (4) the realism of the proposed cost and availability of funds. The degree of importance of the Offeror's cost will be evaluated based on the assessment of the overall technical merit of the proposal and the funds available for the technology area proposed. 2. Evaluation Panel - Technical and cost proposals submitted under this BAA will be protected from unauthorized disclosure in accordance with FAR 3.104-5 and 15.207. The cognizant Government experts will perform the evaluation of technical proposals. Cost proposals will be evaluated by Government business professionals. VII. SECURITY CLASSIFICATION In order to facilitate intra program collaboration and technology transfer, the Government will attempt to enable technology developers to work at the unclassified level to the maximum extent possible. If access to classified material will be required at any point during performance, the Offeror must clearly identify such need prominently in their proposal. If Offerors use unclassified data in their deliveries and demonstrations regarding a potential classified project, they should use methods and conventions consistent with those used in classified environments. Such conventions will permit the various subsystems and the final system to be more adaptable in accommodating classified data in the transition system. Contracting Office Address: N00024 NAVAL SEA SYSTEMS COMMAND, DC 1333 Isaac Hull Avenue S.E. Washington Navy Yard, DC Point of Contact(s): Joseph Tannenbaum (202)781-2629 Jessie Rehwoldt (202)781-5282 This is a modification to the Broad Agency Announcement (BAA) N00024-10-R-4215 posted on 1 February 2010. This modification extends the date for receipt of white papers and full proposals to 9 February 2016. Any white papers that have already been submitted do not need to be resubmitted. Included in the scope of the BAA are development activities as described further in the Naval Power Systems Technology Development Roadmap (NPS TDR) available on the NAVSEA web site and released to industry under announcement N0002413R4217. A revision of the Technology Development Roadmap is presently in draft and will be released by separate announcement. All other information contained in the original announcement remains unchanged. Added: <input type="hidden" name="dnf_class_values[procurement_notice][description][1][added_on]" value="2016-01-07 07:55:20">Jan 07, 2016 7:55 am Modified: <input type="hidden" name="dnf_class_values[procurement_notice][description][1][modified_on]" value="2016-08-02 16:01:19">Aug 02, 2016 4:01 pm Track Changes
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVSEA/NAVSEAHQ/N0002410R4215/listing.html)
 
Record
SN04205011-W 20160804/160802235108-c544d121a888e6551c632b0baa157983 (fbodaily.com)
 
Source
FedBizOpps 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.