SOURCES SOUGHT
58 -- Sources Sought for MUOS RR&DD/A&OS effort
- Notice Date
- 2/21/2003
- Notice Type
- Sources Sought
- Contracting Office
- 4301 Pacific Highway Bldg OT4 Code 02, San Diego CA 92110-3127
- ZIP Code
- 92110-3127
- Solicitation Number
- SPAWAR Headquarters MKTSVY 245F6
- Point of Contact
- Point of Contact - Salvatore M Cianci, Contract Specialist, 619-524-7184
- E-Mail Address
-
Email your questions to Contract Specialist
(salvatore.cianci@navy.mil)
- Small Business Set-Aside
- N/A
- Description
- The Space and Naval Warfare Systems Command (SPAWAR) and its Communications Satellite Program Office (PMW 146) are seeking to identify responsible prime sources (i.e. prime contractor or contracting teams) capable of performing the Risk Reduction and Design Development and Acquisition and Operations Support (RR&DD/A&OS) efforts for the Mobile User Objective System (MUOS). MUOS is the next generation narrowband Military Satellite Communications system that will replace the currently operational UHF Follow-On (UFO) system. THIS IS NOT A NOTICE OF SOLICITATION ISSUANCE, but rather this is a request for information in order for the Government to identify interested sources that are capable of performing the MUOS RR&DD/A&OS efforts. The purpose of this sources sought is to identify potential prime sources that: (1) can adequately demonstrate their current capabilities; and (2) have a detailed plan of action that shows the ability to meet System Design Review (SDR) requirements in the timeline required to propose for the pending RR&DD/A&OS contract. If a solicitation is released, it will be synopsized under separate cover on the Federal Business Opportunities (FedBizOpps) website and the SPAWAR E-Commerce Central website. It is the responsibility of potential offerors to monitor these sites for additional information pertaining to this requirement. The information requested herein will be used to support a potential solicitation in 4th quarter FY03 and resulting contract award in the 2nd quarter of FY04. All information provided below is for planning purposes and is subject to change. The MUOS required Initial Operational Capability (IOC) is 2008 and Full Operational Capability (FOC) is 2013. SPAWAR plans to competitively award, on the basis of best value, one contract containing: o A firm cost-reimbursement effort for the design, development, test and fielding of the initial MUOS satellite and associated ground infrastructure; o Options for fixed-price production & launch of the remaining MUOS satellites, network control & satellite control ground equipment and; o An optional cost-reimbursement effort for in-service support of the system from IOC to FOC. The project timeline for this acquisition is: o Draft in April 2003 solicitation (see summary Attachment 1); o Final solicitation in August 2003; and o Proposals in November 2003. Currently, MUOS is in the Component Advanced Development (CAD) phase. Two contractor teams, Lockheed Martin Space Systems Company in Sunnyvale, CA and Raytheon Company in St. Petersburg, FL, are performing this requirement under contracts awarded via full and open competition, N00039-02-C-3295 and N00039-02-C-3296, respectively. The critical outcomes of each CAD phase contract are risk reduction and a successful System Design Review (SDR) with the Government MUOS team with subsequent delivery of an SDR package (i.e. detailed design documentation and plans). The completion of such SDR requirements (see summary Attachment 2) for the current CAD contracting teams is scheduled for October and November 2003. Any offeror for the MUOS RR&DD/A&OS efforts will be required to successfully complete an SDR, similar to that required of the CAD contracting teams, with the Government MUOS Team and incorporate the resulting SDR package into its proposal for the RR&DD/A&OS contract. Any prime sources (i.e. prime contractor or contracting teams) shall reply to this synopsis if they are interested in proposing for the MUOS RR&DD/A&OS phase contract. Potential offerors shall present their demonstrated capabilities and detailed plan of action in a Qualification Package to the SPAWAR MUOS Government Team via a face-to-face meeting not to last longer than four hours per potential offeror. Potential offerors shall submit the Qualification Package (via electronic means to the SPAWAR E-commerce website) no later than three business days prior to the scheduled face-to-face meeting. The Qualification Package shall contain the contents for briefing the Government Team in the face-to-face meeting. The Government Team is available to meet with such offerors (four hours per offeror) from March 24th-28th, 2003. One of these four hours shall be considered reserved for questions and answers. Interested offerors shall arrange exact dates/times with the SPAWAR contracts point of contact Mr. Sal Cianci via e-mail only at Salvatore.Cianci@navy.mil. Acknowledgment of receipt will be made by e-mail. Telephone inquiries will not be honored. Mr. Cianci must by contacted by 4:00 p.m. (Pacific Time) on Tuesday, March 11th, 2003. In lieu of a Qualification Package, each of the current CAD contracting teams shall submit a written response (no longer than two pages) by 5:00 p.m. (Pacific Time) on Monday, March 17th, 2003 clearly stating: (a) whether or not it plans to compete for the RR&DD/A&OS contract; and (b) the status of its teaming arrangement (both current and future members and their roles). This is NOT a request for proposals. Proprietary data in responses will be protected where so designated. All respondents should indicate their company size status and the extent to which they can include small business participation (of all small business categories listed in FAR 19.7). Contractor size status is based on NAICS Code 334220 with an SBA size standard of 750 employees. Partnering between small and large businesses is encouraged. Responses received in reply to this notice may, in part, be used to make a determination of the level of competition for the resulting solicitation (e.g., full and open competition, SB set-aside, 8(a) set-aside, etc.). Evaluation of proposals submitted in response to the MUOS RR&DD/A&OS solicitation (planned for August 2003 release) will include a evaluation of proposed MUOS designs, risks, costs, estimated ownership costs, and offerors' plans, organization, facilities, and capabilities to satisfy the requirements of the solicitation while achieving IOC and FOC within schedule. This following list provides a summary of critical requirements for the RR&DD/A&OS efforts. This list is neither a complete nor a final listing of such requirements. More detailed requirements will be provided with the draft solicitation(s) and a final listing of requirements will be provided with the final solicitation. The RR&DD/A&OS solicitation will require offerors to: 1) define a system architecture that meets the MUOS performance requirements and affordability constraints at verifiable and acceptable levels of risk; 2) identify and define MUOS internal and external interfaces; 3) describe the specifics of system production, deployment, and operations processes; 4) describe the associated system development, deployment, and operation processes that must be used in the RR&DD and production phases; 5) identify high technical risk items and key cost drivers and demonstrate how they will be managed; 6) demonstrate the capability of significant risk MUOS components, technologies, and subsystems in a relevant environment; 7) identify the complete set of components/subsystems to be integrated into the full system; and 8) demonstrate the capability to achieve MUOS IOC in 2008 and FOC by 2013. The following paragraphs provide a summary of SDR requirements. This summary is not a complete listing of requirements for the SDR. More specific SDR requirements may be obtained by reviewing the CAD phase solicitation posted under this sources sought synopsis for "MUOS RR&DD/A&OS effort" at the SPAWAR E-commerce website (www.e-commerce.spawar.navy.mil ) under the "Headquarters" and "Market Surveys" folders. SDR requirements include: 1) an architecture overview that describes the architectural implementation and includes architectural diagram(s) defining all segments and segment interfaces, both internal and external, that clearly identifies frequency bands used for each segment, and clearly identifies all terrestrial site locations, function and number of personnel (excluding user segment), and functional/physical connectivity; 2) detailed descriptions of all segments of the MUOS architecture, including detailed internal and external MUOS interface descriptions, sufficient to substantiate architecture performance and feasibility; 3) spacecraft information including satellite size, weight and power breakdowns to the payload and bus unit level with sufficient detail to demonstrate how spacecraft weight and power consumption estimates were derived; minimum baseline design power, weight, and space margins that must be maintained for risk mitigation; technical descriptions of key spacecraft hardware and software components such as antennas, deployment mechanisms, feeds, filters, receivers, transmission lines, processors, and transmitter subsystems; detailed frequency plans clearly identifying all frequencies employed for all RF links, plus detailed channelization, frequency reuse, and filtering designs, including filing status for all proposed frequencies; and spacecraft reliability estimates demonstrating the system meets required availability and lifetime. 4) payload information including functional block diagrams of the MUOS payload and technical descriptions of key payload subsystems in adequate depth to clearly demonstrate technical feasibility and requirements satisfaction; end-to- end signal analysis showing derivation of critical technical parameters such as required and achievable gain, noise figure, dynamic range, linearity, efficiency, isolation, G/T, EIRP, intermodulation products, out of band emissions, signal processing, and any other key technical parameters affecting performance; 5) bus architecture information including functional block diagrams of the MUOS satellite bus and technical descriptions of key bus subsystems that clearly demonstrate technical feasibility and requirements satisfaction; technical descriptions of all key bus subsystems including power, attitude control, propulsion, TT&C, thermal control and any other bus subsystems required for proper spacecraft operation; 6) constellation information including the total number of satellites including spare satellites for each orbit type; a satellite launch and replenishment schedule that identifies the satellite design, production and deployment schedule and indicates start of initial operating capability, full operational capability, and end of life; clear and unambiguous definitions of the orbits for all proposed satellites, specified in terms of epoch times and orbit elements or other industry standard methods; identification of the intended launch vehicle and provide an analysis of weight and fairing clearance margins; an assessment of individual satellite life and overall MUOS system life that shows that MUOS system life requirements are met; clear and unambiguous displays of satellite geometric coverage for MUOS users, connectivity to ground elements, connections to both the network control center and the satellite control center, minimum elevation angles and coverage overlay ability; and clear definition of all crosslink connectivity between satellites, if any are proposed to meet MUOS Performance Requirements 7) ground element descriptions including block diagrams and clear descriptions of all ground hardware and software elements, transport ownership (government and/or commercial), latency requirements, and security provisions required for information transport. 8) satellite control segment information describing the proposed satellite control segment implementation and identifying how the associated requirements stated in the MUOS Performance Specification (MPS) are proposed to be satisfied. 9) network management segment information including a description of both the MUOS Common Air Interface (CAI) User and LAN/WAN network management architecture, the distribution of network control functions between ground and space elements, a description of any proposed automated network management system (tools), high level user and data ownership profiles, security profiles and data protection, descriptions of all interfaces to between ground sites and any external network management systems, and descriptions of all proposed methods of planning and operations between MUOS-capable terminals and legacy terminals; detailed descriptions of required hardware and software to support the network management architecture in sufficient detail to demonstrate how MUOS network management requirements are satisfied; software descriptions including functional description of significant software components, contents of significant databases, sizing estimates for significant software components and basis for estimates that include a reuse analysis of any available commercial-off-the-shelf (COTS) and non-developmental items (NDIs) network management software; and physical block diagrams that clearly identify all sites and estimate space requirements. 10) user entry segment information describing the new user segment interface, referred to as the common air interface, in terms of the five-layer model plus any additional necessary descriptions that account for the MPS requirements such as access time, priority and preemption, queuing, and system optimization, and any proposed elements that will require encryption and a proposed encryption method; and describing how the user entry segment provides for service to legacy UHF DAMA users. 11) MUOS ground infrastructure segment information including functional block diagrams identifying all elements of the MUOS ground infrastructure required to implement the concept, including any necessary equipment, facilities or communication lines needed for connectivity between the satellite control, network management and transport ground elements. 12) MUOS system performance information describing the performance of the proposed MUOS architecture against the requirements described in the MPS, with all necessary supporting analysis to substantiate performance claims. This information must also describe how the concept provides: (a) for the service types and quality requirements described in the MPS; (b) a calculation of the MUOS Operational Availability using the definition of availability provided in the MPS Appendix D; (c) an availability analysis with sufficient details to support its assumptions and parameters; (d) clear identification of link impairments in the form of losses or otherwise; (e) link budgets for each link employed in the concept (including user links, net management links, crosslinks, and ground transport element links); (f) UHF link budget propagation effects considered in link design as described in the MPS Appendix D and for other frequencies employed a similar description of prominent propagation effects for that band; (g) link budget calculations of the received Eb/N0 and the resultant probability distribution of this parameter based on the uplink or downlink noise statistics; (h) and an assessment of the overall MUOS capacity in sufficient level of detail showing the method applied to calculate capacity and comparison against the threshold and objective capacity requirements identified in the MPS and Communications Services Requirements document. 13) user equipment information describing the requirements levied upon the user equipment based upon the proposed MUOS architecture, consistent with terminal hardware and software costs provided in the associated Life Cycle Cost estimates; 14) teleport interface implementation description in sufficient detail to clearly describe hardware, software, and facilities; 15) schedule information describing all development and production ac tivities in sufficient detail to substantiate the efficacy of the offeror?s plan to fulfill MUOS IOC and FOC schedule requirements; 16) management information describing how the offeror will allow real-time government insight into work progress, system information, and risk management and how the offeror proposes to allow government participation in functional team and IPT deliberations; 17) system engineering management information in sufficient detail to fully describe the offerors' processes for completing the detailed system design and production planning; 18) life cycle cost estimates for all post-SDR design, development, production (assuming both a multiyear procurement and procurement by annual options), and support costs through FY2023; logistics planning information in sufficient detail to describe an effective and efficient support system through design, production, and system operation, and to justify the life cycle cost estimates; 19) test planning information in sufficient detail to describe an integrated test regime that fully describes a system integration approach; system performance verification process; system characterization plans; system demonstrations and tests including in-factory segment, ground segment, transport segment, end user segment, inter-segment integration, satellite pallet, payload and integration, software, system, and on-orbit testing; Modeling and Simulation (M&S) approach and schedule; test documentation requirements; training requirements review and validation; test support and resource requirements; and a detailed test schedule that includes integration, verification, and characterization testing; 20) a Concept of Operations for the system describing interoperability with and concurrent use of the UFO constellation, legacy terminals, legacy waveforms, and legacy controllers (e.g., JMINI), as well as transition from the legacy systems; 21) a detailed preliminary system specification describing the specifics of system production, deployment, and operations processes; 22) Interface Control Documents (ICDs) based on the ?Mobile User Objective System Five (5)-
- Web Link
-
Click on this link to access the SPAWAR E-Commerce Central Web Site
(https://e-commerce.spawar.navy.mil/command/02/acq/navhome.nsf/homepage?readform&db=navbusopor.nsf&whichdoc=7E620111BC28503E88256CD50000EC07&editflag=0)
- Record
- SN00263239-W 20030223/030221213727 (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 |