Establishing Readiness for Customer Use

1. Define what ready means

Consider an evaluation valve supplied so a customer can investigate command timing with a candidate controller. The work must remain within established electrical, pressure, temperature and fluid-service limits. Environmental qualification or mission-life testing may still be incomplete, but those gaps must be identified. Calling the unit evaluation hardware does not establish its suitability for the proposed experiment or remove the need for appropriate safety and handling provisions.

NASA's product-transition guidance recognizes deliveries at different development stages, from models and prototypes to flight units. The accompanying information and preparation depend on the product, its destination and the receiving team's needs. NASA: Product Transition

For the valve example, four questions provide a practical starting point:

• What is being supplied? The hardware configuration, included electronics and relevant interfaces.
• What use is supported? The operating conditions and limitations, distinguished from conditions still under evaluation.
• What establishes acceptance? The agreed requirements, acceptance criteria and evidence accompanying the unit.
• What remains to be done? The outstanding investigations or integration checks, and who is responsible for completing them.

These decisions belong early enough to influence development and verification planning. NASA calls for defined requirements and acceptance criteria, with the verification approach tailored to the project. NASA: Product Verification

The supplier might provide evidence supporting operation within a stated interface envelope, while the spacecraft developer evaluates compatibility with its controller and completes the agreed system-level checks. Accepting the component does not, by itself, establish readiness of the integrated propulsion system.

2. Separate the questions different evidence answers

Readiness involves related but distinct questions: whether the design is adequate, whether the delivered unit conforms to that design, and whether it works within the customer's installation.

ECSS's space-equipment testing standard distinguishes qualification and acceptance objectives and addresses protoflight testing separately. It is cited here for those distinctions, not to prescribe valve test levels; its scope excludes tests below equipment level. ECSS-E-ST-10-03C Rev.1, sections 1 and 4.5

These activities are distinguished by purpose; the project plan still controls their sequencing and permitted test hardware. The same leakage measurement may guide a design change during development, contribute to qualification after environmental exposure, or support acceptance of a production unit. Its configuration, conditions and criteria determine what it establishes.

Verification can combine analysis, inspection, demonstration and testing. It does not necessarily require separate hardware for every purpose. NASA describes a protoflight approach in which hardware intended for flight receives a tailored qualification test program rather than using a separate qualification unit. The selected exposures must account for its subsequent flight use. NASA: Verification Planning and Product Forms

Earlier results are not automatically discarded—or automatically accepted as formal verification. NASA permits credit from lower-fidelity hardware when its relevant similarity to the flight configuration is demonstrated and the responsible project authorities approve that use. NASA: Verification Planning

3. Represent the installation and operating sequence

A test result applies to the hardware and the conditions established around it. The setup needs to represent the interfaces that materially affect the requirement being assessed.

For the illustrative valve, those interfaces can include:

• Electrical: the drive waveform and voltage available at the valve, including relevant wiring effects.
• Fluid: inlet and outlet conditions, fluid state and the response of the connected supply and downstream passages.
• Mechanical and thermal: mounting constraints, support temperature and available heat-transfer paths.

Matching nominal settings is not necessarily enough. A pressure measured at a supply regulator may differ from the pressure at the valve during operation. A laboratory fixture may remove heat differently from the intended spacecraft support. The test definition should identify where conditions are established and measured. NASA's integrated-engineering guidance calls for traceability between test and flight hardware, including configuration, fidelity and boundary conditions. NASA: MSFC-HDBK-3701, section 5.18.1

Depending on the requirements, the assessment may need to represent an initial opening after storage, repeated pulses, sustained operation, shutdown or a later restart. Select sequences that exercise relevant behavior; not every component needs every possible sequence. NASA's end-to-end verification guidance includes startup, normal operation, contingencies and shutdown within representative operational scenarios. NASA: Product Verification

A useful precedent is the Sample Analysis at Mars instrument suite on Curiosity. Its environmental chamber was designed to reproduce both conductive and radiative thermal interfaces with the rover; the conductive interface plate was built to rover flight drawings. Representative experiment sequences were exercised under controlled environmental conditions. Where ground testing could not reproduce sample delivery under Martian gravity, the team used analysis to support verification. Mahaffy et al.: The Sample Analysis at Mars Investigation and Instrument Suite, sections 7–8

This precedent illustrates a practical distinction: a representative test need not replicate the entire spacecraft, but substitutions and simplifications need justification for the behavior being assessed. Differences can require additional analysis or testing before results apply to the intended installation.

4. Turn results into a defensible acceptance decision

An acceptance decision connects requirements to valid evidence. Measurement uncertainty, discrepancies and authorized exceptions affect that decision.

Interpret measurements against an agreed rule

Consider a specified upper leakage limit $L$. Let $y$ be the measured leakage and $U$ its expanded measurement uncertainty, expressed in the same units and with the coverage basis stated.

One possible guarded acceptance rule is:

This places the upper end of the stated uncertainty interval at or below the limit. It is an illustrative rule, not a universal valve requirement or a guarantee of zero decision risk. Guard bands trade the risk of accepting nonconforming hardware against the risk of rejecting conforming hardware. JCGM 106: Measurement uncertainty in conformity assessment, sections 8.3.1–8.3.2

If the inequality is not satisfied, this acceptance condition has not been met. That does not, by itself, establish that actual leakage exceeds the specification. The agreed rule determines rejection or further assessment; it should not be selected afterward to obtain a preferred outcome.

Resolve discrepancies without erasing their history

Unexpected behavior may originate in the hardware, test equipment, procedure or conditions achieved. NASA calls for discrepancies to be recorded and assessed, distinguishing product nonconformance from problems with verification. A successful retest belongs alongside the original result and its resolution, not in place of that history. NASA: Verification results and discrepancy closure

For example, an unexpected valve response time warrants investigation of both the assembly and the measurement and drive conditions. The findings determine the correction and further verification needed.

Distinguish conformity from an authorized exception

A requirement may remain unmet even when the responsible authority permits acceptance under a waiver. The record should identify the nonconformance, its approved disposition and any restrictions. NASA distinguishes corrective verification work from accepted waivers for nonconforming products. NASA: Product Verification

5. Deliver the hardware with usable information

The receiving team must be able to connect the delivered unit to its configuration, supporting evidence and permitted use. For the illustrative valve, that includes any supplied driver and applicable settings—not just the valve's serial number.

A practical delivery package should answer four questions:

• What arrived? Part and serial identification, configuration, supplied accessories and applicable document revisions.
• What evidence applies? Unit-specific acceptance results, references to relevant qualification evidence, and approved exceptions or restrictions.
• How is it integrated and operated? Controlled interface information, operating limits, installation instructions and required checks.
• What condition is it in? Relevant test and handling history, preservation status, and events affecting remaining life or supported use.

For programs applying it, ECSS-Q-ST-20C Rev.2 formalizes these connections through an end-item data package and product logbook. These include configuration information, test records, nonconformances and outstanding activities. ECSS-Q-ST-20C Rev.2, Annexes B and C

Consider a valve leakage report. The customer needs to know whether the result concerns internal or external leakage, the test fluid and conditions, and the units and reference conditions used. A result obtained with one test fluid does not independently establish performance with another or demonstrate broader propellant compatibility.

Evidence references should lead to information the customer can review under the agreed arrangement. That does not necessarily require transferring the supplier's proprietary design archive; accessible evidence and interface information should be agreed before delivery.

Packaging, cleanliness protection, storage and handling must preserve the condition on which acceptance was based. NASA's transition guidance addresses these provisions alongside documentation and preparation of the receiving site. Receiving inspections, any required functional checks and outstanding integration work should have clearly assigned responsibilities. NASA: Product Transition

6. Preserve that basis after delivery

A supplier may revise a component, a customer may change its operating plans, or later testing may uncover a concern with an unchanged configuration.

For the illustrative valve, extending storage duration or increasing planned operating cycles raises a new question even without a hardware change: does the existing evidence cover that use? Replacement hardware also needs review; physical fit alone does not establish interchangeability.

The change assessment discussed in Article 6 continues after delivery: identify affected evidence and necessary work, obtain appropriate approval and verify implementation. That review determines the scope of any requalification. NASA: Configuration Management

Change communication should distinguish affected configurations, the proposed action and its approval status. Notifying a customer of a revision does not authorize its use in that customer's installation.

If a valve exhibits unexpected behavior, the investigation should connect the observation to its configuration, operating conditions and relevant history. Common parts, processes or production lots may identify other potentially affected units. ECSS's definition of product traceability encompasses material and part origins, processing history and distribution after delivery. ECSS: Traceability

Those connections help establish the investigation's scope; they do not prove that the problem is isolated—or that every related unit is defective. Agreed reporting and escalation arrangements should identify who investigates, who communicates interim restrictions and who authorizes any revised basis for use.

The series began with the maneuvers a spacecraft needs to accomplish its mission. Customer readiness closes that chain: requirements become hardware, and applicable evidence supports its intended operation.

The continuing question is whether the delivered configuration still supports the intended mission capability, within known limits and with remaining responsibilities clearly assigned.

Reference scope

NASA guidance and ECSS standards are cited for specific practices, not as universal contractual requirements or evidence of Aeterna compliance. The valve examples and measurement rule are educational. The SAM precedent demonstrates its reported test approach, not qualification of the illustrative valve. No test levels, leakage limits, product guarantees or supplier support commitments are established here.