MEL - GeoXO Lightening Mapper v FINAL.pdf

Gray columns are not needed for proposals Do not populate this column

Similarity to Existing:

Is it a New

MASTER EQUIPMENT LIST (MEL)

LEVEL NAME (Mission or Payload Name) UNIT

MASS QUIESCENT

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)

Cont-gency

Total Power [W] w/

Contgcy

(MEV)

Unit Power

[W]

(CBE)

Total Power

[W]

(CBE)

Cont-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…)

DE

SI

G N

M

AN

UF

AC

TU

RE

SO

FT

W

AR

E

PR

O

VI

DE

R

US

E

O

PE

RA

TI

NG

E

NV

RE

F

PR

IO

R

US

E

N ew

D es ig n

RE

FE

RE

NC

E M

IS

SI

O N(

S)

TOTAL FLIGHT HARDWARE

1 INSTRUMENT X

2 Subassembly 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

2 Subassembly 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

2 Subassembly 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 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 0.00

1 INSTRUMENT Y

2 Subassembly 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

2 Subassembly 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

2 Subassembly 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 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 0.00

1 INSTRUMENT Z

2 Subassembly 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

2 Subassembly 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

2 Subassembly 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

INSTRUMENT Z TOTAL 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00

INSTRUMENT TOTALS 0.00

1 SPACECRAFT BUS

2 Electrical Subsystem 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

2 Attitude Control Subsystem 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

2 Command & Data Handling Subsystem 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

2 Thermal Control Subsystem 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 2 Etc. 0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 0.00 0.00 0.00 0.00 0.00 0.00 0.00

0.00 0 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 0.00

TOTAL FLIGHT HARDWARE 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00

Spacecraft Bus Subtotal (Dry Mass) 0.00 Propellant (kg) Payload Subtotal 0.00 Observatory Wet Mass (kg) 0.00

Only complete the Heritage Columns for these non-flight elements

NON-FLIGHT HARDWARE HERITAGE

System Subsystems/Components

HERITAGE JUSTIFICATION and ADDITIONAL INFORMATION

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 t t ) ti t 250MH l k

Quoted Unit

Price ($K)

Composition

TECHNOLOGY

READINESS LEVEL

Current TRL

SI

M

IL

AR

IT

Y

TO

EX

IS

TI

NG

HERITAGE SUMMARY# OF UNITS FLIGHT HARDWARE MASS NOMINAL FLIGHT HARDWARE

POWER

PEAK FLIGHT HARDWARE

POWER

F(Full) P(Partial) N(None) NA(Not Applicable

New Technology or Engineering Change Options

NT

EC

Identical

Heritage Level Options F P N

NA

Unit Type Definitions for MEL Additional definitions to support the Unit Type Definitions NPR 7120.8, Appendix J Definitions

Cold (Backup) Units

Cold Units and Hot Units are both flown, and the sum of units is the total Flight Units in Column F.

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

Cold Units and Hot Units are both flown, and the sum of units is the total Flight Units in Column F.

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 Test Unit (ETU) / Qual Unit

Engineering Test Units (ETUs) are flight-like qualification units that are tested to flight environmental levels. If your ETU should not be costed as like full flight spare, then discuss it in additional information or put it in the EM / EDU / Prototype 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 Model (EM) / Engineering Demonstration (EDU) / Prototype Unit

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

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.

NASA NPR 7123.1C

Procedural Effective Date: February 14, 2020

Requirements Expiration Date: February 14, 2025

Subject: NASA Systems Engineering Processes and Requirements (w/Change 1)

Responsible Office: Office of the Chief Engineer

Appendix E. Technology Readiness Levels Short summary of Technology Readiness Levels

TRL Definition Hardware Description Software Description Success criteria Basic principles observed and reported.

Scientific knowledge generated underpinning hardware technology concepts/applications.

Scientific knowledge generated underpinning basic properties of software architecture and mathematical formulation.

Peer reviewed documentation of research underlying the proposed concept/application.

Technology concept and/or application formulated.

Invention begins, practical application is identified but is speculative, no experimental proof or detailed analysis is available to support the conjecture.

Practical application is identified but is speculative; no experimental proof or detailed analysis is available to support the conjecture. Basic properties of algorithms, representations, and concepts defined. Basic principles coded. Experiments performed with synthetic data.

Documented description of the application/concept that addresses feasibility and benefit.

Analytical and experimental proof-of-concept of critical function and/or characteristics.

Research and development are initiated, including analytical and laboratory studies to validate predictions regarding the technology.

Development of limited functionality to validate critical properties and predictions using non-integrated software components.

Documented analytical/experimental results validating predictions of key parameters.

Component and/or breadboard validation in a laboratory environment.

A low fidelity system/component breadboard is built and operated to demonstrate basic functionality in a laboratory environment.

Key, functionality critical software components are integrated and functionally validated to establish interoperability and begin architecture development.

Relevant environments defined and performance in the environment predicted.

Documented test performance demonstrating agreement with analytical predictions.

Documented definition of potentially relevant environment.

Component and/or brassboard validated in a relevant environment.

A medium-fidelity component and/or brassboard, with realistic support elements, is built and operated for validation in a relevant environment so as to demonstrate overall performance in critical areas.

End-to-end software elements implemented and interfaced with existing systems/simulations conforming to target environment. End-to-end software system tested in relevant environment, meeting predicted performance. Operational environment performance predicted. Implementations.

Documented test performance demonstrating agreement with analytical predictions.

Documented definition of scaling requirements. Performance predictions are made for subsequent development phases.

System/sub-system model or prototype demonstration in a relevant environment.

A high-fidelity prototype of the system/subsystems that adequately addresses all critical scaling issues is built and tested in a relevant environment to demonstrate performance under critical environmental conditions.

Prototype implementations of the software demonstrated on full-scale, realistic problems. Partially integrated with existing hardware/software systems.

Limited documentation available.

Engineering feasibility fully demonstrated.

Documented test performance demonstrating agreement with analytical predictions.

System prototype demonstration in an operational environment.

A high-fidelity prototype or engineering unit that adequately addresses all critical scaling issues is built and functions in the actual operational environment and platform (ground, airborne, or space).

Prototype software exists having all key functionality available for demonstration and test. Well integrated with operational hardware/software systems demonstrating operational feasibility. Most software bugs removed. Limited documentation available.

Documented test performance demonstrating agreement with analytical predictions.

Actual system completed and "flight qualified" through test and demonstration.

The final product in its final configuration is successfully demonstrated through test and analysis for its intended operational environment and platform (ground, airborne, or space). If necessary*, life testing has been completed.

All software has been thoroughly debugged and fully integrated with all operational hardware and software systems. All user documentation, training documentation, and maintenance documentation completed. All functionality successfully demonstrated in simulated operational scenarios. Verification and Validation completed.

Documented test performance verifying analytical predictions.

Actual system flight proven through successful mission operations.

The final product is successfully operated in an actual mission.

All software has been thoroughly debugged and fully integrated with all operational hardware and software systems. All documentation has been completed. Sustaining software support is in place. System has been successfully operated in the operational environment.

Documented mission operational results.

Note: In cases of conflict between NASA directives concerning TRL definitions, NPR 7123.1 will take precedence.

Note:

*"If necessary" refers to the need to life test either for worn out mechanisms, for temperature stability over time, and for performance over time in extreme environments. An evaluation on a case-by-case basis should be made to determine the system/systems that warrant life testing and the tests begun early in the technology development process to enable completion by TRL 8. It is preferable to have the technology life test initiated and completed at the earliest possible stage in development. Some components may require life testing on or after TRL 5.

Examples:

a.The level is reached when the final product is qualified for the operational environment through test and analysis. Examples are when Cassini and Galileo were qualified, but not yet flown.

b.Interim Cryo Propulsion Stage (ICPS): A Delta Cryogenic Second Stage modified to meet Space Launch System requirements for Exploration Mission-1 (EM-1). Qualified and accepted by NASA for flight on EM-1.

Examples:

a. Flown spacecraft (e.g., Cassini, Hubble Space telescope).

b. Technologies flown in an operational environment.

c. Nanoracks CubeSat Deployer: Commercially developed and operated small satellite deployer on-board the ISS.

c. In-space demonstration missions for technology (e.g., autonomous robotics and deep space atomic clock). Successful flight demonstration could result in use of the technology in a future operational mission

d. Robotic External Leak Locator (RELL): Originally flown as a technology demonstrator, the test article was subsequently put to use to help operators locate the likely spot where ammonia was leaking from the International Space Station (ISS) External Active Thermal Control System Loop B.

6 Examples:

a. A remote sensing camera includes a large 3-meter telescope, a detection assembly, a cooling cabin for the detector cooling, and an electronics control unit. All elements have been demonstrated at TRL 6 except for the mirror assembly and its optical performance in orbit, which is driven by the distance between the primary and secondary mirrors needing to be stable within a fraction of a micrometer. The corresponding critical part includes the two mirrors and their supporting structure. A full-scale prototype consisting of the two mirrors and the supporting structure is built and tested in the relevant environment (e.g., including thermo-elastic distortions and launch vibrations) for demonstrating the required stability can effectively be met with the proposed design.

b. Vacuum Pressure Integrated Suit Test (VPIST): Demonstrated the integrated performance of the Orion suit loop when integrated with human-suited test subjects in a vacuum chamber.

7 Examples:

a. Mars Pathfinder Rover flight and operation on Mars as a technology demonstration for future micro-rovers based on that system design.

b. First flight test of a new launch vehicle, which is a performance demonstration in the operational environment. Design changes could follow as a result of the flight test.

5 Examples:

a. A 6.0-meter deployable space telescope comprised of multiple petals is proposed for near infrared astronomy operating at 30K. Optical performance of individual petals in a cold environment is a critical function and is driven by material selection. A series of 1m mirrors (corresponding to a single petal) were fabricated from different materials and tested at 30K to evaluate performance and to select the final material for the telescope.

Performance was extrapolated to the full-sized mirror.

b. For a launch vehicle, TRL 5 is the level demonstrating the availability of the technology at subscale level (e.g., the fuel management is a critical function for a re-ignitable upper stage). The demonstration of the management of the propellant is achieved on the ground at a subscale level.

c. ISS Additive Manufacturing Facility: Characterization tests compare parts and material properties of polymer specimens printed on ISS to copies printed on the ground.

Examples:

a.Fiber optic laser gyroscope: A breadboard model is built including the proposed laser diode, optical fiber and detection system.

The angular velocity measurement performance is demonstrated in the laboratory for one axis rotation.

b.Bi-liquid chemical propulsion engine: A breadboard of the engine is built and thrust performance is demonstrated at ambient pressure. Calculations are done to estimate the theoretical performance in the expected environment (e.g., pressure, temperature).

c.A new fuzzy logic approach to avionics is validated in a lab environment by testing the algorithms in a partially computer-based, partially bench-top component (with fiber optic gyros) demonstration in a controls lab using simulated vehicle inputs.

d.Variable Specific Impulse Magnetosphere Rocket (VASIMR): 100 kW magnetoplasma engine operated 10 hours cumulative (up to 3 minutes continuous) in a laboratory vacuum chamber.

Examples:

a. High efficiency Gallium Arsenide solar panels for space application is conceived for use over a wide temperature range. The concept critically relies on improved welding technology for the cell assembly. Samples of solar cell assemblies are manufactured and submitted to a preliminary thermal environment test at ambient pressure for demonstrating the concept viability.

b. A fiber optic laser gyroscope is envisioned using optical fibers for the light propagation and Sagnac Effect. The overall concept is modeled including the laser source, the optical fiber loop, and the phase shift measurement. The laser injection in the optical fiber and the detection principles are supported by dedicated experiments.

c. In Situ Resource Utilization: Demonstrated the application of a cryofreezer for CO2 acquisition and microwave processor for water extraction from soils.

Examples:

a. Carbon nanotube composites were created for lightweight, high-strength structural materials for space structures.

b. Mini-CO2 Scrubber: Applies advanced processes to remove carbon dioxide and potentially other undesirable gases from spacecraft cabin air.

Examples:

a. Initial Paper published providing representative examples of phenomenon as well as supporting equations for a concept.

b. Conference presentations on concepts and basic observations presented within the scientific community.

| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | AppendixK | ALL |

COMPLIANCE IS MANDATORY FOR NASA EMPLOYEES

Printable Format (PDF) https://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_7123_001C_&page_name=AppendixE&format=PDF https://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_7123_001C_&page_name=AppendixE&format=PDF

Heritage Summary

Full Heritage Partial Heritage No Heritage Design Identical Minimal modifications Major modifications

Manufacture Identical Limited update of parts and processes necessary

Many updates of parts or processes necessary

Software Identical Identical functionality with limited update of ft d l

Major modifications (>=50%)

Provider Identical provider and development team

Different however with substantial involvement of original team

Different and minimal or no involvement of original team

Use Identical Same interfaces and similar use within a novel overal context

Significantly different from original

Operating Environment

Identical Within margins of original

Significantly different from original

Referenced Prior UIn operation Built and successfully ground tested

Not yet successfully ground tested

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 description/characteristics. Certain items should include additional details, sufficient to assess functionality and/or cost, to identify and separate individual elements.

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), and how what amount of heritage will be used in the design.

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.), and (5) development language

Instructions for software (can be included under the heading for HERITAGE JUSTIFICATION and ADDITIONAL INFORMATION)