SOURCES SOUGHT
A -- The Naval Sea Systems Command (NAVSEA) seeks information from firms capable of providing Littoral Combat Ship(LCS) Mission Module development, integration and test capability in support of the United States Navy.
- Notice Date
- 9/24/2004
- Notice Type
- Sources Sought
- Contracting Office
- N00024 1333 Isaac Hull Avenue S.E. Washington Navy Yard, DC
- ZIP Code
- 00000
- Solicitation Number
- N0002404R6333
- Response Due
- 10/25/2004
- Description
- REQUEST FOR INFORMATION THIS IS A REQUEST FOR INFORMATION ONLY. The Naval Sea Systems Command (NAVSEA) seeks information from firms capable of providing Littoral Combat Ship(LCS) Mission Module development, integration and test capability in support of the United States Navy. THIS IS NOT A NOTICE OF SOLICITATION ISSUANCE, BUT RATHER A REQUEST FOR INFORMATION from industry that will allow the Government to support and validate the government?s development of a long term contract strategy for LCS Mission Modules. The information sought herein is for planning purposes only and should not be construed as a Request For Proposal (RFP) or as any obligation or commitment on the part of the Government to acquire any product or service. There shall be no basis for claims against the Government as a result of any information submitted in response to this RFI. THIS IS NOT A REQUEST FOR PROPOSALS. The Government does not intend to award a contract on the basis of this RFI or otherwise to pay for any inform! ation submitted by respondents to this request. To get the Littoral Combat Ship (LCS) and focused mission capability to the warfighter as fast as possible, an evolutionary acquisition strategy, driven by an accelerated schedule and today?s available technology will be used. LCS Mission Packages will be optimized for flexibility in the littorals. Mission package capabilities are currently focused on three primary mission areas: Mine warfare (MIW) - emphasizing mine countermeasures Anti-submarine warfare (ASW) ? emphasizing the shallow water submarine threat Anti-surface warfare (SUW) - emphasizing prosecution of small boats (SUW) The requirements are structured to incrementally deliver capabilities through spiral development. Integration with the ship will be achieved by compliance to the PEO Ships Interface Control Document (ICD) and through close coordination with the ship design agent. The focused Mission Packages are developed and procured as a separate acquisition from the Seaframe (i.e., the ship). The first Mission Package spiral increment provides capability for the LCS Flight 0 Seaframe with the government performing as system integrator. PMS 420, the Mission Module Program Office, is responsible for integration, testing, certification, delivery and life cycle support of Mission Packages. PMS 420 plans to involve Industry for spiral development. The desired outcome of this RFI is to obtain Industry?s ideas for their role in supporting the LCS Mission Module Program. The information obtained through this RFI will form the basis of discussions for an Industry day. Details of the Industry Day, scheduled for November 3, 2004, are provided with this RFI. The purpose of the Industry Day is to provide an opportunity for government and industry to collaborate on innovative contract strategies for the development, procurement and integration of mission modules/packages. Requested Input from Industry. Industry is encouraged to submit information to PEO LMW (PMS420). The following items are provided for guidance only in submitting input. Information shall be submitted to PEO LMW (PMS420) via email to PMS420Calendar@navsea.navy.mil. All responses are due by 18 October 2004. In the event that industry provides information to the government that it does not want disclosed to the public, it shall mark the title page with the following legend: ?This document 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 provide information to the government. This restriction does not limit the Government?s right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets].? Industry shall mark each sheet of data it wi! shes to restrict with the following legend: ?Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this document.? 1. Propose alternative contract strategies and business models, including the following: a. Pros and Cons of single/multiple contractor(s) as Mission Package integrator b. Innovative contract approaches that address the Navy?s desire to foster open architecture, open systems, and technology re-fresh and insertion. c. Show why your alternative provides value to the U.S. Navy. This is best done by proven benchmarks and metrics, where you can demonstrate achieving the required performance for the minimum amount of dollars. d. Government/Industry Partnering. 2. Answer the following questions: a. As a Mission Package Integrator, how would you accommodate the development, integration, test and certification of new systems/capabilities from a variety of small and large companies? Within the U.S.? Outside the U.S.? b. Outline the ?scope? of a Mission Package Integrator and its relationship to the Seaframe contractor and the Government Laboratories? c. As the Mission Package Integrator, how would you apply lean processes in your business model to ensure Best Value to the Government? d. What are the benefits to the Government for continuing to use the Government Laboratories as the lead system integrator and how do you see industry playing a role in that construct? e. If not the primary Mission Package Integrator, describe how, as an innovative company, you would desire to work with the Navy to integrate your product into a mission module. f. Describe performance metrics that should be applied to a Mission Package Integrator and could be used for a basis of award fee. g. How does the Navy determine that it is getting best value for spiral development? h. How should a Mission Package Integrator and PMS420 collaborate to decide what development occurs for each spiral increment? 3. Provide Industry questions for the U.S. Navy to answer. Industry Day details. The Program Executive Officer for Littoral and Mine Warfare and the Littoral Combat Ship Mission Module Program Manager, PMS420, will host a LCS Mission Module/Package Industry Day on November 3, 2004, starting at 0830, at the Anteon Corporation, 1100 New Jersey Ave., SE, Washington, DC. Registration information shall be sent to lcsmm-industryday@anteon.com. Deadline for registration is 25 October 2004. Seating is limited, and therefore only individuals who pre-register will be guaranteed seating. NAVSEA reserves the right to limit attendance. Registration information must include the following information: company name and address, and the name, e-mail address, telephone number, and facsimile number for each attendee. Only registrations from companies registered on the Central Contractor Registry (CCR) will be accepted. This is an unclassified meeting. The format for the Industry Day will include briefs from PEO LMW, PMS420 and OPNAV representatives. Industry inputs from this RFI (if not restricted) will be consolidated and briefed at the conference followed by a panel discussion. Information exchanged may be used in preparation of one or more Request(s) For Proposal (RFP). Supplemental Information. Definitions: ?Mission Package? = Mission Modules + Mission Crew ?Mission Modules? combine ?Mission Systems? (vehicles, sensors & weapons), their support equipment, and standard interfaces. Mission Modules ?plug into? Seaframe?s standard interfaces to provide focused mission capability. Potential roles for industry partners. Serve as overall technical agent supporting PMS 420 in developing Mission Module open architecture to facilitate rapid, flexible implementation of new technology. Serve as primary technical agent to develop interface specifications and standards for Mission Systems within Mission Packages and between Mission Packages and the Seaframe Combat System. Serve as the primary integration agent supporting PMS 420 in certifying Mission Packages meet Navy operational requirements and standards. The integration agent should utilize existing test and engineering centers and infrastructure to the maximum extent possible. Serve as the primary agent supporting PMS 420 in the management of an aggressive spiral development process that provides fair and open access to commercial, government and academia-developed technology from both domestic and international sources. Manage the Configuration baseline (and changes), integration testing, certification and tracking of all mission systems, mission modules and mission packages for PMS 420.
- Record
- SN00681617-W 20040926/040924212319 (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 |