GSFC Common MEL Template.xlsx
XLSX spreadsheet 829 KB Posted
- Attached to
- AOS Access to Space Study. Federal contract opportunity
- Solicitation number
- 80NSSC22779076Q1
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| RFQ 80NSSC22779076Q1 Questions and Answers.pdf | ||
| NASA-STD-8719.14B.pdf | ||
| GSFC-STD-1000G.pdf | ||
| GSFC-STD-1001A.pdf | ||
| AOS-I-ATS-RFP-3.pdf | ||
| NPR7123.1C.pdf | ||
| GPR7120.4D.pdf | ||
| GSFC Common MEL Guidance.pdf | ||
| AOS-I-ATS-RFP-2 SOW.pdf | ||
| NPR-8705.4A.pdf | ||
| GSFC-STD-7000A.pdf | ||
| RFQ 80NSSC22779076Q1.pdf |
Show all 12
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
MEL
Please see the companion document "Common MEL Guidance" for instructions prior to completing this MEL template.
Grey columns are not required for proposals. They are optional. Delete these columns if not used.
If you need to add sheets, add them at the end... adding them before the "DoNotDelete" tab will break automated pull-downs. These Power Columns are recommended but not required in the MEL for proposals. Delete these columns if not used. Power Summary Table by Mode may be more useful for proposals. Composition:
Structure Example: Tantalum, Tin, Lead Electronics Examples:
- Instrument mechanism controller board, 1 FPGA RTG4, usage 500K System gates (25% of 2M system gates), operating at 250MHz clock
- Main Electronics box Data processor board, 32-bit SPACRC CPU, 2 RT ProASIC3 FPGAs, each with usage of 1 M system gates (33% of 3M system gates), CPU operating at 25MHz & FPGAs operating at 175MHz1 FPGA RTG4
- 1 SRAM 16 Mbit, 1 EEPROM 128kx8, 3 ADC 12 bit, 2 DAC 12 bit TRL is for MEL & Heritage; decide if you will show TRL rollup for each 'system' in MEL or leave blank. See AO Requirements Tab for Heritage Instructions for each column (F, P, N, NA). New Technology or Engineering Change?
o NT: New Technology, never flown before.
o EC: Change in engineering approach/design, workmanship, manufacturing processesm unless these employ radically new technology that has never been used before. Proven technology in a new size or configuration, unless that new configuration is such a substantial deviation from what has been previously qualified/validated/tested/proven that it materially affects the performance limits of the technology.
| o Neither: This element has flown before, and full heritage is leveraged. | Cost Modelers may complete these columns for inclusion in the proposal. | ||||||||
| MASTER EQUIPMENT LIST (MEL) | |||||||||
| LEVEL | NAME (Mission or Payload Name) | UNIT MASS | # OF UNITS | FLIGHT HARDWARE MASS | NOMINAL FLIGHT HARDWARE POWER | PEAK FLIGHT HARDWARE POWER | QUIESCENT | Quoted |
Unit Price ($K) Composition TECHNOLOGY
READINESS
LEVEL
| TRL | SIMILARITY TO EXISTING | HERITAGE SUMMARY | HERITAGE JUSTIFICATION and ADDITIONAL INFORMATION | |
| PRICE COST MODELING DATA | Add Columns to the |
right if needed.
| Subassembly / Component | Unit Mass [kg] | ||
| (CBE) | Cold Units | Hot Units | Flight |
| Units | Flight Spares | ETU / Qual Unit | EM / |
EDU / Proto-type Total Mass [kg] (CBE) Contin-gency [%] Total Mass [kg] w/ Contgcy
| (MEV) | Unit Power [W] | |||||||||||||||
| (CBE) | Total Power [W] (CBE) | Contin-gency [%] | Total Power [W] w/ Contgcy (MEV) | Unit Power [W] | ||||||||||||
| (CBE) | Total Power [W] (CBE) | Contin-gency [%] | Total Power [W] w/ Contgcy (MEV) | Total Power [W] (CBE) | ADDITIONAL INFORMATION | |||||||||||
| (As applicable: Vendor, make, model, part #, volume, quote information, notation of identical items, instrument / component characteristics, ETU approach...) | DESIGN | MANUFACTURE | SOFTWARE | PROVIDER | USE | OPERATING ENV | REF PRIOR USE | REFERENCE MISSION(S) | Structure Mass (Kg) | Electronic Complexity Factor | Structure Complexity Factor | Electronic Remaining Design (1.00 = 100%) | Structure Remaining Design (1.00 = 100%) | Engineering Complexity Mod. Level (Simple, |
New)
| TOTAL FLIGHT HARDWARE | 0.00 | 0.00 | F(Full) P(Partial) N(None) NA(Not Applicable) | WS | MCPLXE | MCPLXS | NEWST | NEWST | ECMPLX | |||||||||||||||
| 1 | INSTRUMENT X | |||||||||||||||||||||||
| 2 | Subassembly | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||||||||||||||||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 6 | EC | F | F | NA | N | P | P | P | |||||||||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 4 | NT | N | N | N | N | N | N | N | This new widget has been fully tested in mission environment. It is built by the same team that built XXX, but has a significantly improved design, optimized for this new environment/use. | ||||||||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 5 | NT | F | F | P | F | P | P | P | |||||||||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 7 | EC | F | F | F | F | F | P | F | This new widget does a new function and we haven't tested it in the environment yet. | |||||||||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 8 | Identical | F | F | F | F | F | F | F | This is the exact same thing by a different provider. We used the same exact design and it has been fully verified in the target environment. We own the IP. | |||||||||
| 2 | Subassembly | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||||||||||||||||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||||||||||||||||||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||||||||||||||||||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||||||||||||||||||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||||||||||||||||||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||||||||||||||||||
| 2 | Subassembly | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||||||||||||||||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||||||||||||||||||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||||||||||||||||||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||||||||||||||||||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| INSTRUMENT X TOTAL | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |
| 1 | INSTRUMENT Y | |||||||
| 2 | Subassembly | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 2 | Subassembly | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 2 | Subassembly | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| INSTRUMENT Y TOTAL | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |
| 1 | OTHER PAYLOAD OR ELEMENT Z | |||||||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| OTHER PAYLOAD OR ELEMENT Z TOTAL | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |
| 1 | SPACECRAFT BUS | |||||||
| 2 | Electrical Subsystem | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 2 | Attitude Control Subsystem | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 2 | Command & Data Handling Subsystem | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 2 | Thermal Control Subsystem | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 3 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | ||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| Etc. | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | |||
| SPACECRAFT BUS TOTAL | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| TOTAL FLIGHT HARDWARE | 0.00 | 0.00 | |
| Spacecraft Bus Subtotal (Dry Mass) | 0.00 | 0.00 | |
| Propellant (kg) | |||
| Payload Subtotal | 0.00 | 0.00 | |
| Observatory Wet Mass (kg) | 0.00 | 0.00 | |
| Only complete the Heritage Columns for these non-flight elements | |||
| NON-FLIGHT HARDWARE HERITAGE | |||
| System | |||
| Subsystems/Components |
Unit Type Definitions
| Unit Type Definitions for MEL | NPR 7120.8, Appendix J Definitions | ||||
| Cold (Backup) Units | |||||
| (not needed for proposals) | This column is used by the IDL, and may be hidden for a proposal. Cold Units and Hot Units are both flown, and the sum of units is the total Flight Units in Column D. If an engineer is looking for savings, he/she may want to consider the need for the Cold Units. | Proof of Concept | Analytical and experimental demonstration of hardware/software concepts that may or may not be incorporated into subsequent development and/or operational units. | ||
| Hot (Primary) Units | |||||
| (not needed for proposals) | This column is used by the IDL, and may be hidden for a proposal. Cold Units and Hot Units are both flown, and the sum of units is the total Flight Units in Column D. If an engineer is looking for savings, he/she may want to consider the need for the Cold Units. | Breadboard | A low fidelity unit that demonstrates function only, without respect to form or fit in the case of hardware, or platform in the case of software. It often uses commercial and/or ad hoc components and is not intended to provide definitive information regarding operational performance. | ||
| Flight Units | A Flight Unit is the actual model that will be launched. It either undergoes protoflight testing if a qualification model has not been tested, or it undergoes flight acceptance testing if a qualification model has been successfully tested. This total should include Engineering Test Units (ETU's), which will be fully flight qualified. This column includes everything planned for flight - the primary & backup flight units or ETU's. This includes flight units that must fly to provide redundancy (ie. hot or cold spares). | Brassboard | A medium fidelity functional unit that typically tries to make use of as much operational hardware/software as possible and begins to address scaling issues associated with the operational system. It does not have the engineering pedigree in all aspects, but is structured to be able to operate in simulated operational environments in order to assess performance of critical functions. | ||
| Flight Spares | A Flight Spare is a duplicate of either a component, subsystem, or the entire Flight Unit. Flight Spares are preassembled, tested and ready to swap with the corresponding Flight Unit, or they are spare flight-qualified parts ready for assembly and subsequent acceptance level testing when a need arises. Flight units that must fly to provide redundancy are NOT included in the flight spares column. The flight spares column includes hardware on the ground that is intended to replace a non-functioning flight item. | Proto-type Unit | The proto-type unit demonstrates form, fit, and function at a scale deemed to be representative of the final product operating in its operational environment. A subscale test article provides fidelity sufficient to permit validation of analytical models capable of predicting the behavior of full-scale systems in an operational environment. | ||
| Engineering Model (EM) / Engineering Demonstration Unit | |||||
| (EDU) / Prototype | Engineering Model (EM) and Engineering Demonstration Unit (EDU) are generally different names for the same model. These engineering units are flight-like in terms of fit, form, and functionality. They are used to reduce risk, or perform life-testing on parts that can degrade over time and/or with use, provided flight-like parts are used for life test unit. | ||||
| A prototype is generally a non-flight like model that is used to demonstrate functionality early in the project. It is not used for environmental testing or flight qualification. Also known as “breadboard”. Prototypes are included in the Engineering Model column | Engineering Unit | A high fidelity unit that demonstrates critical aspects of the engineering processes involved in the development of the operational unit. Engineering test units are intended to closely resemble the final product (hardware/software) to the maximum extent possible and are built and tested so as to establish confidence that the design will function in the expected environments. In some cases, the engineering unit will become the final product, assuming proper traceability has been exercised over the components and hardware handling. | |||
| Engineering Test / Qual Units (ETU) | |||||
| (optional) | Engineering Test Units (ETUs) are qualification units that are tested to flight environmental levels, and can be flown if necessary; they can serve as flight spare units. Cost Modelers will cost the ETUs the same as flight spares, which is why the AO does not ask for this column. A separate ETU column may help with clarity. The "Additional Information" column can also be used. If your ETU should not be costed as a full flight spare, then discuss it in additional information or put it in the EM / EDU / Prototype column. | Mission Configuration | The final architecture/system design of the product that will be used in the operational environment. If the product is a subsystem/component, then it is embedded in the actual system in the actual configuration used in operation. | ||
| Laboratory Environment | An environment that does not address in any manner the environment to be encountered by the system, subsystem, or component (hardware or software) during its intended operation. Tests in a laboratory environment are solely for the purpose of demonstrating the underlying principles of technical performance (functions), without respect to the impact of environment. | ||||
| Relevant Environment | Not all systems, subsystems, and/or components need to be operated in the operational environment in order to satisfactorily address performance margin requirements. Consequently, the relevant environment is the specific subset of the operational environment that is required to demonstrate critical "at risk" aspects of the final product performance in an operational environment. It is an environment that focuses specifically on "stressing" the technology advance in question. | ||||
| Operational Environment | The environment in which the final product will be operated. In the case of space flight hardware/software, it is space. In the case of ground-based or airborne systems that are not directed toward space flight, it will be the environments defined by the scope of operations. For software, the environment will be defined by the operational platform. |
TRL Definitions
| TRL Definitions from NPR 7123.1C, Appendix E |
| For additional assistance in determining TRL, refer to SP-20205003605, [NASA] Technology Readiness Assessment Best Practices Guide |
AO Requirements Heritage Summary
AO Flight System Capabilities Reqt: (f) Flight software, including (i) logical lines of code by Computer Software Configuration Item (CSCI), (ii) description of the functionality for each CSCI, (iii) code counts categorized as either New, Modified, Full Reuse, or Auto-generated, (iv) development method (spiral, waterfall, agile, etc.), and (v) development language.
AO MEL Requirements:
- The breakouts 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, identification of engineering models and prototypes with their fidelities, required deliveries for simulators and testing, contingency allocations for individual components, and other component description/characteristics. Certain items should include additional details, sufficient to assess functionality and/or cost, to identify and separate individual elements.
- List each electronic board separately, identify the functionality of each board (either in the MEL or in the Mission Implementation section), and provide the speed the board will be running at. 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 logic cells, logic elements), the board the chip(s) will be integrated onto, and how much heritage will be used in the design.
DoNotDelete SpreadsheetCodes
| New Technology or Engineering Change Options |
| NT |
| EC |
| Identical |
| Yes/No Options |
| Yes |
| No |
| Possibly |
| Heritage Level Options |
| N |
| P |
| F |
| NA |
| Ownership Options |
| Own IP |
| Own GSE |
| Own All |
| External |
| NA |
TrackChanges
| Version Tracking | |
| Version Date | Description of Changes |
| 7/3/14 | First Attempt to have standard MEL carry from IDL/MDL through proposal submission |
| 9/2/14 | Added clarifications for MDL/IDL - leveling, unit definitions, lessons learned from first use |
| 9/26/16 | Added Heritage columns to address reduction in Heritage page allocation in AOs |
| 11/1/16 | Updated based on feedback from first use |
| 5/19/17 | Updated based on use for New Frontiers; several columns never used and/or weaken story |
| 6/1/17 | Updated to put back the ETU column - even though not used by cost modelers, it is important information (note, cost modelers include these as flight spares); deleted software tab to keep as separate file |
| 6/9/17 | Added sub-total rows at the bottom of each element to mirror the AO template (vs top), and changed NT/EC column to better terminology for clear & positive message in proposal |
| 8/20/21 | TRL Definitions Tab: Updated TRL Definitions reference from NPR 7123.1B to 7123.1C; Added SP-20205003605 [NASA] Technology Readiness Assessment Best Practices Guide; AO Requirements Tab: Removed redundant MEL template |
image1.png image2.png image3.png image4.png image5.png image6.png image7.png
File details come from the government source that posted it. Updated .