ECSS Test Readiness Reviews
Fast, Flexible & Accessible, Your Test Facilitator, not simply a Test facility
A Test Readiness Review, or TRR, is the formal assessment completed before a planned space-hardware test begins. Its purpose is not to demonstrate hardware performance. Its purpose is to confirm that the article, configuration, facility, documentation, personnel and controls are ready for safe and effective testing.
ECSS-E-ST-10-03C Rev.1 requires each agreed test block to include a Test Readiness Review, Post-Test Review and Test Review Board. The TRR must be held before the test activity to verify that all conditions allow the programme to proceed.
The review considers far more than the Test Procedure. It addresses the approved AIT Plan, Test Specification, predictions, measurement plan, facility readiness, configuration, instrumentation, calibration, cleanliness, safety, nonconformances, waivers, personnel, responsibilities, schedule and pass or fail criteria.
Engineers should care because many disrupted or invalid tests result from preparation failures rather than weaknesses in the test article. A disciplined TRR protects hardware, people, facilities, schedule and verification evidence.
The required output is unambiguous: a decision to proceed with the test or not to proceed.
A Test Readiness Review is a formal review held before a test activity to verify that all required conditions allow testing to proceed.
It examines the readiness of the complete test system, not only the item under test.
That system can include:
The test article.
Hardware and software configuration.
Fixtures and mounting arrangements.
Electrical and mechanical interfaces.
The test facility.
Instrumentation.
Data acquisition.
Ground support equipment.
Controlled documentation.
Trained personnel.
Safety controls.
Cleanliness controls.
Contingency arrangements.
Verification evidence requirements.
The engineering purpose is to identify unresolved issues before they affect the article, facility, programme or validity of the evidence.
The TRR should answer one central question:
Can the planned test be executed safely and effectively, using the approved configuration and documentation, while generating valid verification evidence?
A TRR can support:
Development testing.
Qualification testing.
Acceptance testing.
Protoflight testing.
Environmental testing.
Functional and performance testing.
Equipment-level testing.
Space-segment element testing.
Final preparation activities.
ECSS-E-ST-10-03C Rev.1 structures the test programme into agreed test blocks. Each block includes formal reviews. TRRs for several blocks may be combined where appropriate. A TRR may also be combined with the Post-Test Review for the previous block.
Combining reviews should not reduce the required evidence or weaken the decision.
A TRR identifies readiness gaps before the point of exposure.
Typical findings can include:
An unapproved procedure.
An unresolved interface.
An incorrect software version.
Unsuitable fixture assumptions.
Incomplete calibration.
Unavailable personnel.
Missing safety controls.
Open nonconformances.
Unclear abort criteria.
Incomplete pass or fail criteria.
Finding these issues before testing is normally faster and less expensive than managing them during a live campaign.
ECSS-E-ST-10-03C Rev.1 requires a TRR before the start of the applicable test activity.
The review supports controlled implementation of the Test Specification, Test Procedure and AIT Plan. It also supports configuration control, product assurance, safety, traceability and the generation of credible test evidence.
The requirement applies through the project’s contractually applicable and tailored baseline.
A technically successful exposure can still produce weak evidence.
Evidence may be challenged where:
The configuration was not controlled.
The wrong procedure was used.
Instrumentation was unsuitable.
Calibration was incomplete.
The facility was not ready.
Acceptance criteria were unclear.
The data chain was not controlled.
Deviations were not recorded.
The TRR reduces these risks by confirming the evidence route before execution.
Qualification Models, Protoflight Models and Flight Models can be expensive, scarce or irreplaceable.
A TRR helps protect them from avoidable test-related harm. It cannot remove all programme risk, but it can prevent risks created by poor preparation.
The principal standards can include:
| ECSS document | Typical relevance |
|---|---|
| ECSS-E-ST-10 | System engineering framework and overall technical process |
| ECSS-E-ST-10-02 | Verification requirements, methods and evidence |
| ECSS-E-ST-10-03C Rev.1 | Testing |
| ECSS-Q-ST-20 | Quality assurance requirements |
| ECSS-Q-ST-20-07 | Quality assurance requirements for test centres |
| ECSS-Q-ST-10-09 | Nonconformance Control |
| ECSS-Q-ST-40 | Safety |
| ECSS-Q-ST-70-01 | Cleanliness and Contamination Control |
| ECSS-S-ST-00 | ECSS system application |
| ECSS-S-ST-00-02 | Tailoring |
Only standards applicable to the product, organisation, activity and project should be invoked.
The test programme is divided into blocks agreed between the customer and supplier.
Typical blocks can include:
Integration.
Alignment.
Leak or proof-pressure testing.
Mechanical testing.
EMC testing.
Thermal testing.
Functional and performance testing.
Final preparation.
Each test block includes:
Test Readiness Review.
Post-Test Review.
Test Review Board.
The detail required at a general programme TRR may differ from a specific test-block TRR.
The TRR requirement and its implementation should be considered through the approved project baseline.
The scope can reflect:
Test complexity.
Product level.
Hardware value.
Model type.
Test severity.
Facility risk.
Mission consequence.
Heritage.
Customer involvement.
The number of participating organisations.
The evidence required.
Tailoring should make the review proportionate. It should not convert the TRR into an administrative formality.
Customers can define additional entry criteria, participants, approval gates and evidence.
Examples include:
Customer witnessing.
Launcher-authority participation.
Approval of notching strategies.
Cleanliness declarations.
Software release evidence.
Simulation or prediction review.
Independent safety approval.
Configuration audits.
Formal closure of selected actions.
The approval authority should be identified before the review begins.
The project defines:
The review objective.
The applicable test block.
The review authority.
The chairperson.
Participants.
Entry criteria.
The evidence package.
The agenda.
The decision process.
Exit criteria.
The review date should allow enough time for meaningful document review and action closure.
The responsible teams compile and assess the evidence.
Preparation should confirm that:
The AIT Plan is approved.
The Test Specification is approved.
The Test Procedure is approved.
The test configuration is defined.
The facility has completed its readiness activity.
Calibration remains valid.
Predictions are available where required.
Pass or fail criteria are complete.
Safety controls are approved.
Open points are visible.
The review pack should be distributed early enough for participants to examine it.
The review board assesses the planned activity against the defined criteria.
The meeting should focus on evidence and unresolved risk. It should not become the first reading of documents that should already have been reviewed.
Findings are recorded and classified.
Each open point should have:
A clear description.
An owner.
Required closure evidence.
A closure authority.
A target date.
A defined effect on permission to proceed.
Residual risks should be explicit.
The TRR produces one of two decisions:
Proceed with the test, subject to any authorised conditions.
Do not proceed with the test.
Actions must be clearly identified and assigned closure dates before execution.
Conditional approval should be used carefully. Critical readiness evidence should not remain unresolved when the test begins.
Entry criteria confirm that the review itself is ready to begin.
If critical entry criteria are not met, the review should be postponed or its objective formally redefined.
Hazards identified.
Risk controls implemented.
Emergency arrangements confirmed.
Cleanliness status acceptable.
Contamination controls available where required.
Handling and lifting arrangements approved.
Stored-energy controls established.
Approved AIT Plan available.
Approved Test Specification available.
Approved Test Procedure available.
Predictions available where relevant.
Measurement-point plan approved.
Facility readiness report approved.
Test schedule approved.
Contingency and emergency procedures approved.
Lower-level acceptance data available where applicable.
Previous review actions addressed.
Item under test correctly identified.
Configuration status available.
Hardware and software versions recorded.
Inspection status confirmed.
Functional baseline completed.
Known limitations identified.
Relevant nonconformances visible.
Waivers and deviations recorded.
Test facility available.
Facility configuration defined.
Fixture or set-up approved.
Instrumentation identified.
Calibration valid.
Maintenance status acceptable.
Environmental conditions suitable.
Data acquisition available.
Ground support equipment ready.
Required infrastructure available.
Chairperson identified.
Test director identified.
Operators available.
Personnel qualifications confirmed.
Product assurance participation confirmed.
Project engineering participation confirmed.
Facility representative available.
Customer or specialist attendance confirmed where required.
A successful TRR should establish that:
The planned test is authorised.
The reviewed configuration is confirmed.
Approved documentation is available.
Facility readiness is demonstrated.
Personnel and responsibilities are confirmed.
Pass or fail criteria are complete.
Safety and cleanliness controls are acceptable.
Critical actions are closed.
Remaining actions are controlled.
Residual risks are accepted by the proper authority.
Verification objectives remain achievable.
The proceed decision is recorded.
The exit decision should identify exactly which article, configuration, procedure, facility, set-up and test window have been approved.
A material change after the TRR may require a reconvened review or an authorised delta review.
From thermal vacuum cycling tests and operational TVAC testing to bakeout and contamination assessment, we support complete environmental verification programmes from concept through qualification and acceptance.
For customers requiring a complete space hardware testing campaign, thermal vacuum testing can be combined with Vibration Testing, Shock Testing and broader Environmental Testing services through a single engineering team.
ECSS identifies core participants for the review.
These normally include:
The chairperson.
Product assurance representatives.
Project engineers.
AIT representatives.
Relevant specialists.
The facility representative.
Other parties where necessary.
The chairperson is the Product Assurance Manager for the authority responsible for the test.
Additional participants may include:
Customer representatives.
Launcher authority.
Safety specialists.
Cleanliness specialists.
Software specialists.
Configuration management.
The test-item owner.
Logistics or handling specialists.
The organisation taking custody of the hardware after delivery.
Attendance should be driven by decision relevance. A large audience does not automatically create a stronger review.
The Facility Readiness Review, or FRR, and the TRR are related but distinct.
ECSS-Q-ST-20-07 requires the space test centre to assess the readiness of the facility and test set-up before each applicable test.
The FRR addresses:
Test methods and procedures.
Facility configuration.
Data handling.
Measurement equipment.
Calibration.
Environmental conditions.
Cleanliness.
Maintenance.
Safety.
Facility nonconformances.
Personnel.
Ground support equipment.
Pre-test results.
Final preparation actions.
The facility then provides a declaration of facility readiness to the TRR board.
The TRR considers the wider project decision.
It combines the facility-readiness evidence with the status of the article, configuration, test documentation, verification objectives, personnel, nonconformances, waivers, schedule and customer requirements.
A successful FRR does not automatically approve the project test. It provides essential evidence to the TRR.
The Test Procedure must align with the Test Specification and AIT Plan.
It should define:
The test sequence.
Expected results.
Tolerances.
Pass or fail criteria.
Facility and set-up.
Instrumentation.
Operational constraints.
Safety controls.
Procedure-change rules.
Anomaly handling.
Sign-off requirements.
The board should know exactly what will be tested.
Configuration review covers:
Hardware identification.
Software version.
Installed components.
Interfaces.
Fixtures.
Test tools.
Instrumentation.
Deviations from the intended configuration.
Relationship to the qualification or flight design.
Open actions should not be hidden within meeting minutes.
Each action should be dispositioned as:
Closed.
Accepted with defined residual risk.
Mandatory before test.
Requiring postponement.
The review decision should be explicit and recorded.
A vague conclusion such as “generally ready” is not sufficient authority for exposing valuable hardware.
Incorrect configuration, fixtures, instrumentation or operating modes can invalidate the test or damage the article.
Late procedure review, missing hardware information or unresolved facility interfaces can delay the campaign.
An interrupted or repeated test can create additional facility, engineering, logistics and reporting costs.
Evidence may be rejected where the test was not performed using approved requirements, configurations or processes.
Obsolete, incomplete or unapproved documents can cause teams to execute different instructions.
The review can fail if nobody has clear authority to accept residual risk or approve progression.
A date in the schedule does not create readiness. The review should move if the evidence is not mature.
The TRR should confirm readiness, not perform the initial technical review of every procedure.
Open points must be visible, owned and controlled. Critical actions should close before execution.
The approval only applies to the configuration reviewed. Changes after the TRR require assessment.
Software, facilities, instrumentation, people, safety, cleanliness and evidence controls are equally important.
The facility may be ready while the product, procedure or customer approvals are not.
A test should not begin if the team cannot explain how success will be assessed.
Avoid subjective statements such as “nearly ready”. Criteria should be factual and reviewable.
Use the meeting to resolve findings and make the decision.
Record hardware, software, fixture, instrumentation and procedure versions.
Each test objective should connect to an applicable requirement and intended evidence.
Valid calibration alone is not enough. The measurement method, range and uncertainty must remain suitable for the intended decision.
Identify who chairs, who approves and who accepts residual risk.
Conditional approval should not become a route around critical readiness gaps.
Retain the agenda, evidence pack, attendance, findings, actions, decisions and closure evidence.
Use Post-Test Reviews and Test Review Boards to improve future TRRs.
| Document | TRR relevance |
|---|---|
| Verification Plan | Defines the verification strategy, methods, levels and stages. |
| Verification Control Document | Connects requirements to planned and completed evidence. |
| AIT Plan | Defines the assembly, integration and test programme. |
| Test Specification, TSPE | Defines what the test must achieve. |
| Test Procedure, TPRO | Defines the controlled step-by-step execution. |
| Test Report, TRPT | Records execution, results and conclusions after testing. |
| Facility Readiness Report | Declares readiness of the facility and test set-up. |
| Measurement-Point Plan | Defines approved instrumentation and measurement locations. |
| Configuration Status Records | Identify the reviewed product and test configuration. |
| Nonconformance Records | Document conditions that do not meet requirements. |
| Requests for Deviation or Waiver | Record authorised departures from the baseline. |
| Safety and Risk Assessments | Define hazards, controls and residual risks. |
| Review Minutes and Action Log | Record findings, ownership, decisions and closure. |
TPRO means Test Procedure. TRPT means Test Report.
A successful TRR is not measured by holding the meeting on time.
Success is indicated when:
Entry criteria were satisfied.
The correct evidence was reviewed.
The configuration was confirmed.
Critical risks were identified.
Responsibilities were clear.
Pass or fail criteria were complete.
Actions were assigned and controlled.
The decision was recorded.
Testing proceeded without avoidable disruption.
Hardware integrity was protected.
The resulting evidence remained usable for verification.
The TRR supports qualification, acceptance and flight-readiness activity. It does not itself approve the product for flight.
Resonate can help identify the practical readiness inputs needed before an agreed test campaign.
This can include:
Facility information.
Fixture requirements.
Instrumentation.
Hardware interfaces.
Safety information.
Monitoring.
Functional checks.
Reporting expectations.
Our engineering team can review the facility-facing aspects of the Test Specification and Test Procedure within the agreed scope.
The customer retains ownership of its project requirements, Verification Plan and approval decisions.
Subject to technical review, Resonate can support preparation for:
Vibration testing.
Shock and SRS testing.
Thermal vacuum testing.
Selected environmental testing.
Functional monitoring during exposure.
Resonate can contribute test-specific information for:
AIT Plans.
Test Specifications.
Test Procedures.
Facility readiness records.
TRR evidence packs.
As-run records.
Test Reports.
Responsibilities and approval routes should be agreed before the campaign.
Resonate personnel can participate in TRRs as the facility representative and provide evidence concerning the facility, instrumentation, set-up, safety and operational readiness.
Resonate does not replace the customer’s review authority or Product Assurance Manager.
Testing and review evidence can support customer qualification, acceptance and flight-readiness decisions.
The final decision remains with the customer or appointed project authority.
These FAQs explain how ECSS applies to Test Readiness Reviews and what teams should prepare.Requirements vary by project and approved tailoring. If anything needs clarification, please contact us. We welcome feedback and are happy to discuss your programme.
A credible TRR begins before the review meeting.
Bring Resonate Testing your controlled requirement, Test Specification, draft procedure, article information, drawings, configuration, fixture assumptions, instrumentation needs, safety information, functional checks and reporting expectations.
We can review the facility-facing readiness inputs and identify practical issues before the campaign is committed.
Whether you’re looking to contact us for the first time or have another testing requirement, we’d love to hear from you.