SOURCES SOUGHT
18 -- JPL COMMERCIAL-GOVERNMENT OFF-THE-SHELF TOOLS FOR SPACECRAFT-BASED GROUND DATA SYSTEM REQUEST FOR INFORMATION
- Notice Date
- 5/17/2007
- Notice Type
- Sources Sought
- NAICS
- 423430
— Computer and Computer Peripheral Equipment and Software Merchant Wholesalers
- Contracting Office
- NASA Management Office, Jet Propulsion Laboratory, 4800 Oak Grove Drive, Pasadena, CA 91109
- ZIP Code
- 91109
- Solicitation Number
- SI-07-05
- Response Due
- 6/11/2007
- Archive Date
- 5/17/2008
- Small Business Set-Aside
- N/A
- Description
- The California Institute of Technology?s Jet Propulsion Laboratory, operating under a prime contract with the National Aeronautics and Space Administration (NASA), is seeking industry interest and product information to a Request for Information (RFI) for providing various Commercial Off-the-Shelf (COTS) or Government Off-the-Shelf (GOTS) tools specifically focusing on spacecraft-based Ground Data Systems (GDS) development through operational phases of JPL spacecraft. BACKGROUND: JPL is currently in the design phase of implementing newer GDS capabilities to further enhance current capabilities while also reducing overall operations cost and project risk. REQUEST FOR INFORMATION (RFI): The purpose of this RFI is to invite your company to provide your capabilities and best engineering practices to JPL and to provide information for JPL?s consideration in our design phase. REQUIREMENTS: At a minimum, this RFI is searching for COTS and GOTS tools that can support a JPL GDS architecture and design with tools that can plug-and-play with any Consultative Committee for Space Data Systems (CCSDS) Space Link Extension (SLE) compliant Ground Tracking Network to support deep space missions. (Refer to the attached FIGURE 1. Ground System - All the ground-based capabilities associated with the Project during mission operations.) JPL MISSION OPERATION SYSTEM (MOS) DEFINITION: Functionally, there are two aspects to the MOS: (1) the flight team (the people, processes, procedures, and interfaces); and (2) the GDS (the hardware, software, networks, and facilities). WHAT IS INCLUDED IN THE GDS? (1) Ground-based software and associated documentation required to conduct mission operations; and (2) Ground-based communications and computing hardware and associated documentation required to conduct mission operations. THE PURPOSE OF THE GDS: Provide an integrated suite of multi-mission and mission specific subsystems that enable mission activities for a flight system that is conducting science observations or technology demonstrations. SUBSYSTEM FUNCTIONALITY: (1) Mission planning; (2) Sequencing; (3) Command processing; (4) Telemetry and tracking data processing; (5) Mission monitoring; (6) Data management and archiving; (7) Navigation; (8) Science data processing; and (9) Flight system analysis. JPL?s current GDS is comprised of the following functional areas and JPL is requesting information from companies that can provide tools, services and engineering for one more of the following areas: (Refer to FIGURE 2 - A typical decomposition of an MOS into Functional Elements is shown.) MISSION PLANNING: (1) Establishment of major science and engineering objectives; and (2) Establishment of guidelines and constraints for the use of resources during operations; (3) Long-range planning for Deep Space Network (DSN) antenna resources; (4) High-level integration of science and engineering plans for Flight System activities; and (5) Contingency planning. SEQUENCING: (1) Translation of mission plan and specific activity requests into sequences of Flight System commands and sequence of events for Project and multi-mission capabilities; (2) Integration and resolution of any conflicts in integrated sequences; (3) Verification of integrated sequence?s; (4) Safety: Compliance with flight rules and constraints and resolution of any non-compliance; (5) Effectiveness: Ability to carryout intended activities; and (6) Generation of DSN predicts and configuration instructions corresponding to each sequence. COMMAND PROCESSING: (1) Staging and transport of Flight System commands and DSN predicts and configuration instructions to transmitting DSN antennas; (2) Radiation of command signal to Flight System; and (3) Radiation of uplink tracking signals to Flight System. TELEMETRY DATA PROCESSING: (1) Capture of telemetry data from Flight System telemetry signals; (2) Collection of monitor data from DSN subsystems; (3) Staging and transport of telemetry and monitor data from receiving DSN antennas to JPL; and (4) Reconstruction of files created on Flight System. TRACKING DATA PROCESSING: (1) Capture of radio metric data (e.g., doppler, ranging) and radio science data; (2) Staging and transport of radio metric and radio science data from receiving DSN antennas to JPL; and (3) Data reduction and formatting of radio metric data. MISSION MONITORING: (1) Decommutation, channelization, and limit checking of telemetry and monitor data; (2) monitoring health and status of Flight System; (3) Monitoring status of DSN antennas and telemetry and command processing capabilities; and (4) Controlling Flight System command sessions. DATA MANAGEMENT AND ARCHIVING: (1) Storage and management of mission data (e.g., science data, ancillary data, engineering data); (2) Making mission data available to users; (3) Archiving of all mission data for lifetime of mission; and (4) Preparation and staging of mission data for NASA archiving. NAVIGATION: (1) Generation of predicted and reconstructed ephemeris of Flight System; and (2) Maneuver design and analysis. SCIENCE DATA PROCESSING: (1) Generation of science data products; and (2) Quality assessment/control of science data products. FLIGHT SYSTEM ANALYSIS: (1) Decommutation and channelization of engineering telemetry; (2) Performance assessment and calibration analysis for instruments and engineering subsystems; (3) Detailed planning of instrument and engineering subsystem activities; and (4) Flight software maintenance. RFI RESPONSE CONTENT: Your company is requested to provide your capabilities in response to this RFI by providing the following: 1. COMPANY INFORMATION: (a) Name and address of company; and (b) Name of contact person, phone, email and fax number. 2. TECHNICAL: Provide a technical description of your proposed COTS/GOTS tools how they will meet the subsystem solutions. 3. PROPOSED TOOLS AND SUPPORT: (a) Provide a description of the tools and services and list of core products lines that your company can provide; (b) Discuss how the tools and services meet the applicable JPL functional area descriptions; (c) Describe the plug-and-play capabilities; and (d) Discuss how the product can reduce costs and risks. 4. VENDOR INFORMATION: Discuss: (a) How long your company has worked in this specific area? (b) How developed is your product line? and (c) Your experience in deep space missions. 5. RELATIONSHIP WITH JPL: (a) Discuss your collaboration on any missions with JPL in the past; (b) Discuss any experience working with the Deep Space Network (DSN); and (c) What kind of practices do you plan for working with JPL? 6. RELATIONSHIP WITH NASA OR OTHER CUSTOMERS: Describe experience base or lessons learned with other NASA Centers, ESA, or other institutions or companies. 7. PRODUCT DEFINITION AND CCSDS COMPLIANCE: (a) Is your product CCSDS compliant and to what level? (b) Describe how your company as a whole follow CCSDS guidelines and your plans to follow them in the future; and (c) How does the product define the spacecraft telemetry and command subsystem? 8. PERFORMANCE: (a) Describe how your product supports real-time information; and (b) Discuss how your product handles the wide range of performance requirements for JPL missions (processing time characteristics, telemetry rate, throughput time, etc.) 9. PRODUCT LINE: (a) Does your product have other items that could be purchased as well? (b) Are we required to purchase this product along with an entire suite? (c) What kind of future development is available and can JPL be part of the process? 10. TECHNICAL SUPPORT: (a) What kind of engineering support does your company supply for integration, testing, implementation, and other technical support? (b) What technical support is there for updates? 11. ADAPTABILITY/EASE OF USE: (a) How well can the product move from different environments? (b) Discuss MTBF. (c) How much glueware is required? 12. COST: (a) What is the initial purchase and estimation of integration cost to JPL? (b) How much integration will be required to work with JPL missions? 13. OPERATIONAL/MAINTENANCE COST: (a) What kind of operational support is needed? (b) How much are upgrades? (c) Are we required to update with product line? (d) What is your licensing scheme? RESPONSES DUE: Submit the above requested information to Mary Helen Ruiz (Email: maryhelen.ruiz@jpl.nasa.gov) no later than June 11, 2007. Please limit your response to ten (10) pages. POINT OF CONTACT: Please direct questions and/or comments to Gerald O'Connell at (818) 354-4884 or via Email: gerald.t.oconnell@jpl.nasa.gov COMPLIANCE WITH EXPORT CONTROL REGULATIONS: This RFI may contain Caltech/JPL proprietary information and be subject to export control; comply with all applicable U.S. export regulations. DISCLAIMER: It is emphasized that the requested information is for preliminary planning purposes only and does not constitute a commitment, implied or otherwise, that JPL will solicit a procurement in the future. Neither JPL nor the Government will be responsible for any costs incurred by you in furnishing this information. Be advised that any information provided shall be deemed to be furnished with unlimited rights to JPL, with JPL assuming no liability for the disclosure, use, or reproduction of such data.
- Web Link
-
Click here for the latest information about this notice
(http://prod.nais.nasa.gov/cgi-bin/eps/bizops.cgi?gr=D&pin=54#124680)
- Record
- SN01297232-W 20070519/070517221732 (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 |