SOURCES SOUGHT
A -- REQUEST FOR INFORMATION FOR COMMERCIAL OFF-THE-SHELF GOVERNMENT OFF-THE-SHELFTOOLS FOR SPACECRAFT-BASED GROUND DATA SYSTEM FOR JPL
- Notice Date
- 9/10/2009
- 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-09-08
- Response Due
- 9/28/2009
- Archive Date
- 9/10/2010
- Point of Contact
- Mary Helen Ruiz, JPL Business Opportunities Office, Phone 818-354-7532, Fax 818-393-1746, Email maryhelen.ruiz@jpl.nasa.gov
- E-Mail Address
-
Mary Helen Ruiz
(maryhelen.ruiz@jpl.nasa.gov)
- Small Business Set-Aside
- N/A
- Description
- The California Institute of Technologys Jet Propulsion Laboratory, located inPasadena, California, operating under a prime contract with the National Aeronautics andSpace Administration (NASA), is seeking industry interest and product information to aRequest for Information (RFI) for providing various COTS or GOTS tools specificallyfocusing on spacecraft-based GDS development through operational phases of JPLspacecraft.BACKGROUND: JPL is currently in the design phase of implementing newer GDS capabilitiesto further enhance current capabilities while also reducing overall operations cost andproject risk. The purpose of this RFI is to invite your company to provide your capabilities and bestengineering practices to JPL and to provide information for JPLs consideration in ourdesign phase. REQUIREMENTS: At a minimum, this RFI is searching for COTS and GOTS tools that cansupport a JPL GDS architecture and design with tools that can plug-and-play with anyConsultative 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 capabilitiesassociated with the Project during mission operations.JPL MISSION OPERATION SYSTEM (MOS) DEFINITION: Functionally, there are two aspects to theMOS: (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 documentationrequired to conduct mission operations; and (2) Ground-based communications and computinghardware and associated documentation required to conduct mission operations.THE PURPOSE OF THE GDS: Provide an integrated suite of multi-mission and mission specificsubsystems that enable mission activities for a flight system that is conducting scienceobservations or technology demonstrations.SUBSYSTEM FUNCTIONALITY: (1) Mission planning; (2) Sequencing; (3) Command processing;(4) Telemetry and tracking data processing; (5) Mission monitoring; (6) Data managementand archiving; (7) Navigation; (8) Science data processing; and (9) Flight systemanalysis.JPLs current GDS is comprised of the following functional areas and JPL is requestinginformation from companies that can provide tools, services and engineering for one moreof 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-levelintegration of science and engineering plans for Flight System activities; and (5)Contingency planning.SEQUENCING: (1) Translation of mission plan and specific activity requests into sequencesof Flight System commands and sequence of events for Project and multi-missioncapabilities; (2) Integration and resolution of any conflicts in integrated sequences;(3) Verification of integrated sequences; (4) Safety: Compliance with flight rules andconstraints and resolution of any non-compliance; (5) Effectiveness: Ability to carryoutintended activities; and (6) Generation of DSN predicts and configuration instructionscorresponding to each sequence.COMMAND PROCESSING: (1) Staging and transport of Flight System commands and DSN predictsand configuration instructions to transmitting DSN antennas; (2) Radiation of commandsignal to Flight System; and (3) Radiation of uplink tracking signals to Flight System.TELEMETRY DATA PROCESSING: (1) Capture of telemetry data from Flight System telemetrysignals; (2) Collection of monitor data from DSN subsystems; (3) Staging and transport oftelemetry and monitor data from receiving DSN antennas to JPL; and (4) Reconstruction offiles created on Flight System.TRACKING DATA PROCESSING: (1) Capture of radio metric data (e.g., doppler, ranging) andradio science data; (2) Staging and transport of radio metric and radio science data fromreceiving DSN antennas to JPL; and (3) Data reduction and formatting of radio metricdata.MISSION MONITORING: (1) Decommutation, channelization, and limit checking of telemetryand monitor data; (2) monitoring health and status of Flight System; (3) Monitoringstatus 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., sciencedata, 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 ofmission 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) Qualityassessment/control of science data products.FLIGHT SYSTEM ANALYSIS: (1) Decommutation and channelization of engineering telemetry;(2) Performance assessment and calibration analysis for instruments and engineeringsubsystems; (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 responseto 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 theywill meet the subsystem solutions.3. PROPOSED TOOLS AND SUPPORT: (a) Provide a description of the tools and services andlist of core products lines that your company can provide; (b) Discuss how the tools andservices meet the applicable JPL functional area descriptions; (c) Describe theplug-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 specificarea? (b) How developed is your product line? and (c) Your experience in deep spacemissions.5. RELATIONSHIP WITH JPL: (a) Discuss your collaboration on any missions with JPL in thepast; (b) Discuss any experience working with the Deep Space Network (DSN); and (c) Whatkind of practices do you plan for working with JPL?6. RELATIONSHIP WITH NASA OR OTHER CUSTOMERS: Describe experience base or lessons learnedwith other NASA Centers, ESA, or other institutions or companies.7. PRODUCT DEFINITION AND CCSDS COMPLIANCE: (a) Is your product CCSDS compliant and towhat level? (b) Describe how your company as a whole follows CCSDS guidelines and plansto follow them in the future; and (c) How does the product define the spacecrafttelemetry 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 JPLmissions (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 offuture development is available and can JPL be part of the process?10. TECHNICAL SUPPORT: (a) What kind of engineering support does your company supply forintegration, testing, implementation, and other technical support? (b) What technicalsupport is there for updates?11. ADAPTABILITY/EASE OF USE: (a) How well can the product move from differentenvironments? (b) Discuss MTBF. (c) How much glueware is required?12. DELIVERY COST: (a) What is the initial purchase and estimation of integration cost toJPL? (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) Howmuch are upgrades? (c) Are we required to update with product line? (d) What is yourlicensing scheme?RESPONSES DUE: Please submit the above requested information and comments by September27, 2009 via Email to Mary Helen Ruiz (Email: maryhelen.ruiz@jpl.nasa.gov) no later thanSeptember 27, 2009. Please limit your response to ten (10) pages. POINT OF CONTACT: Stuart Imai, Project/Program Acquisition Manager; Phone: (818)354-2070; FAX (818) 393-4168; Email: stuart.t.imai@jpl.nasa.govEXPORT CONTROL REGULATIONS: This document has been reviewed for export control and itdoes not contain controlled technical data.COPYRIGHT: This document is Copyright 2009 California of Institute of Technology,Government sponsorship acknowledged. The research described in this RFI was carried outat the Jet Propulsion Laboratory, California Institute of Technology, under a contractwith the National Aeronautics and Space Administration. DISCLAIMER: It is emphasized that the requested information is for preliminary planningpurposes only and does not constitute a commitment, implied or otherwise, that JPL willsolicit a procurement in the future. Neither JPL nor the Government will be responsiblefor any costs incurred by you in furnishing this information. Be advised that anyinformation provided shall be deemed to be furnished with unlimited rights to JPL, withJPL assuming no liability for the disclosure, use, or reproduction of such data.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/NASA/HQ/OPHQDC/SI-09-08/listing.html)
- Record
- SN01948652-W 20090912/090911000037-7b1532df2c450222bfaa7b47444e2b45 (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 |