View the file

Other files for this federal contract opportunity

Other files attached to 80GSFC22R0009 -Geostationary Extended Observations Spacecraft Solicitation, newest first.
File Type Posted
SF33.pdf PDF
Amendment 3.pdf PDF
GeoXO Spacecraft Study RFP Amendment 2.pdf PDF
GeoXO Spacecraft Study RFP Questions and Answers Set 3.pdf PDF
GeoXO Spacecraft Study RFP Questions and Answers Set 2.pdf PDF
GeoXO Spacecraft Study RFP Quest and Answer.pdf PDF
REV Table A5 Attachment I.pdf PDF
RFP Cover Letter.pdf PDF
Attachment A- SOW.pdf PDF
Attachment B- PSPEC.pdf PDF
Attachment E-1 GXIUIID.pdf PDF
Attachment E-5 ACXUIID.pdf PDF
Attachment E-6 -ABIUIID.pdf PDF
Attachment J- GRDDP.pdf PDF
Enclosure 1-IT Security Management Plan Template (1).pdf PDF
Attachment C - GIRD.pdf PDF
Attachment E-3 GXSUIID.pdf PDF
Attachment E-4 OCXUIID.pdf PDF
Attachment I- Radiation Environment for Electronic Devices .pdf PDF
Attachment K-CONOPS-0004 draft.pdf PDF
RFP 80GSFC22R009 Final.pdf PDF
Attachment F- IRD-SS-DCS.pdf PDF
Attachment G- IRD- SS-C3S.pdf PDF
Attachment N-TAM_Table_R.pdf PDF
Attachment E-2 LMXUIID.pdf PDF
Attachment D - PRAD.pdf PDF
Attachment H -SCMAR.pdf PDF
Attachment L- IT Security Management Plan.pdf PDF
Attachment M- App Doc List Final.pdf PDF
Attachment O-MEL_v0_R.pdf PDF
Show all 30

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

New Technology or Engineering Change Options

NT

EC

Identical

Heritage Level Options F P N

NA

1. The flight elements and components entered on each row should be traceable to block diagrams and heritage claims provided in other parts of the proposal. For each major component, current best estimates (CBE) and contingency for mass and power, number of flight units required, and some description of the heritage basis must be provided. Power values should represent nominal steady-state operational power requirements. Information to be provided includes identification of planned spares, indentification of engineering models and prototypes with their fidelities, required delieveries for simulatiors and testing, contingency allocations for individual components, and other component

2. List each electronic board separately, identify the functionality of each board (either in the MEL or in the proposal), and provide the operational speed of the board. If proposing Field-Programmable Gate Arrays (FPGAs) or Application Specific Integrated Circuits (ASICs), or Radio Frequency Integrated Circuits (RFICs), list the design size (in the appropriate sizing parameter such as number of logic cells or logic elements), the board that will include the chip(s), MEL Supplemental Instructions:

Provide the following data for Software elements: (1) the number of logical lines of code by Computer Software Configuration Item (CSCI); (2) description of the functionality for each CSCI; (3) code counts categorized as either New, Modified, Full Reuse, or Auto-generated; (4) development method (spiral, waterfall, agile, etc.), Instructions for software (can be included under the heading for HERITAGE JUSTIFICATION and ADDITIONAL INFORMATION)

File details come from the government source that posted it. Updated .