Attachment O-MEL_v0_R.pdf

MAS ER EQUIPMEN L S (MEL)

V AM M ss on o ay oad Name) T

MA

T

Subassemb y Component

Un t Mass [kg]

(CBE)

Co d Uni s

Hot Uni s igh Uni s ight Spa es

E U Qual Un t

EM

EDU

oto ype o al Mass [kg]

(CBE)

Con in-gency otal Mass kg] w

Contgcy

MEV)

Un t owe W]

CBE)

o al owe [W]

CBE)

Cont n-gency otal owe W] w Contgcy

MEV)

Unit owe [W]

(CBE)

otal owe W]

CBE)

Cont n-gency o al owe

W] w Contgcy

MEV)

otal owe

W] (CBE)

A T A AT

(As app icab e Vendo make model pa t # vol me quote n o mat on nota ion o iden ical tems inst ument component cha acte is ics E U app oach )

A A

T

TW

A

V

AT

V e es

M

T TA T A WA

A A T

2 e a s s em 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 A e s s em 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 mma a a a s s em 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 T e ma s s em 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

A A T T TA

Spacec a t Bus Subto al (D y Mass) 0 00 0 00 ayoad Subto al 0 00 0 00

On y comp e e he He age Co umns o hese non- gh e emen s

- T A WA TA

s em

Subs stems Components

TA T AT a A T A AT

T A

V e T

# T T A WA MA M A T A WA

W AK T A WA W

Quo ed Un t ce ($K)

Compos t on

M A

T

X

TA M A

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

Unit Type Definitions for MEL

Cold (Backup) Units Cold Units and Hot Units are both flown, and the sum of units is the total Flight Units in Column D.

Hot (Primary) Units Cold Units and Hot Units are both flown, and the sum of units is the total Flight Units in Column D.

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).

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.

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

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.

NPR 7120.8, Appendix J Definitions

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.

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.

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.

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 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.

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 from NPR 7123.1B, Appendix E