January 16, 2012

Test Readiness Review - PA-15

Give the green light to start testing

A. Scope

A Test Readiness Review (TRR) is a formal meeting the purpose of which is to authorise the start of a test or sequence of tests contributing to the validation, acceptance or qualification of all or part of the components making up a space system and it products.

The specific rules that apply to the Test Readiness Review for software are set out in the document "Software Quality (see PA-7)".

This document is based on the CNES Standards Reference (RNC) document "RNC-CNES-Q-ST-20-100 Bilan technique (BT)".

B. Fundamentals

The TRR is a milestone which precedes the test, consisting in checking that the test is ready to be carried out and that it will be performed under the requisite conditions.

These conditions include the following:

  • the configuration of the product (hardware, software) to undergo the test, and the configuration of the test facilities are recorded and in conformity with a baseline definition ;
  • any configuration deviations are well-known and accepted (modifications, deviations, repairs, non-closed non-conformities, technical events currently being processed, etc.) and these configuration deviations will not compromise the validity of the planned tests ;
  • the test plans and procedures are written and accepted by the next level up ;
  • the objectives of the test (in particular the pass and stop criteria) are well identified and well-known ;
  • the test facilities exist, they comply with the test plans and procedures and have been validated ;
  • the parties involved possess the appropriate skills and knowledge for their role and their mission during the test proceedings ;
  • all the preliminary actions (or ACRS) have been performed ;
  • a suitable system (involving as much as possible the Quality function (Integration Quality Assurance supervisor )) has been set up to monitor the tests and ensure:
    • that the procedures are indeed followed (protection of the integrity of the flight elements tested) and also ;
    • that the means required for ensuring that the test and any significant events are monitored (in particular, the traceability of all unexpected results and events) (Log Book, Non-conformance Report), are indeed available and applied.


Minutes are drafted for the TRR and they must conclude that the start of the test by its instigators is authorised, as a requisite for initiating the activity.

C. Organising and implementing the Test Readiness Review

1. Notification

The party responsible for the supply suggests a date for convening the TRR, giving sufficient notice for those at the next level up (CNES, laboratories, etc.) to make sure they are available.

2. Location

The TRR is, in principle, held on the premises of the laboratory or manufacturer responsible for the supply.

The test room must be accessible on request during the TRR.

3. Participants

The participants whose presence is recommended include:

On behalf of the party responsible for the supply (laboratory or manufacturer):

  • the Project Manager and/or product technical manager and/or test manager;
  • the Product Assurance engineer (or Integration Quality Assurance supervisor).


On behalf of the party in charge at the Customer's (CNES, laboratory or manufacturer):

  • the Project Manager and/or product technical manager and/or test manager;
  • the Product Assurance engineer (or Quality);
  • In cases where he/she is mandated, the Product Assurance customer representative (Delegation of task, DGA-SQ support, etc.).


4. Equipment and available documentation

a) The product and the implementation and testing means forming the subject of the TRR must be available for presentation on request during the TRR.

b) All the documentation relative to the following must be available for examination:

  • the As Designed Configuration or reference configurations and applicable configurations:
    • complete production file,
    • list of applicable modifications (accepted modification proposals);
  • the As Built Configuration or actual configuration:
    • . list of the elements constituting the supply along with all the related control documents,
    • list of the other elements and/or sub-assemblies of different individual responsibility along with their control documents,
    • list of major and minor deviations / waivers and repairs,
    • complete file of major deviations / waivers and repair requests,
    • list of non-conformance reports or open technical events (open works).
  • the tests to be performed: test plans and procedures, including safety and security constraints identified in the equipment User Manual
  • the test (EGSE and MGSE) and environmental control means: validation and calibration procedures; inspection and calibration reports.
  • the AIV operations during the tests: handling, storage and cleaning procedures.
  • the previous tests (if any), and in particular, the Test Review Board (TRB) minutes with the list of open points and actions identified during the test proceedings.


c) All the documentation relative to the manufacturing history as defined by the Product Assurance Specification or the approved corresponding plan must be available for consultation:

  • Inspection report and/or certificate of conformance for the constituents,
  • EIDP and LB (hardware and software) from lower levels.


d) The End-Item Data Package (EIDP) (see PA-13) and the Log Book (LB) (see PA-14) of the product shall be presented (configured blank formats).

5. Minutes and decisions

Minutes of the TRR drafted in session must be issued at the end of the meeting and signed by the relevant parties with responsibilities.

The minutes must clearly indicate:

  • if starting the tests is authorised or not;
  • any actions to be conducted before starting these tests or a given test sequence;
  • if intermediate TRR or TRB are required during test proceedings. If so, the content and dates of these intermediate stages shall be specified.
  • If the test team and decisional team are identified and available.


6. Conducting Test Readiness Reviews for equipment tests

The following is checked during a TRR for equipment tests:

  • the key points planned during manufacture have indeed been carried out and that the resulting actions are closed;
  • the test facilities have been calibrated for the entire duration of the test;
  • the environmental conditions comply with the project requirements, or, if none exist, according to the rules and standards;
  • the safety and security constraints identified in the equipment User Manual are applied
  • the means required to check the quality of this environment exist (cleanness indicators, temperature, pressure and humidity recorders), and they are calibrated in conformity with written procedures;
  • the test, handling or storage procedures necessary for the operations planned during the tests exist;
  • the test personnel has adequate knowledge of the procedures to carry out, the particularities of the supply, the associated test means, and the environment, handling, storage and safety clauses.


7. Proposed Test Readiness Review agenda

The "recommended" agenda is presented in chronological order:

  • recapitulation of the objectives and issues at stake concerning the test to be performed;
  • examination of the As Designed configuration or reference configuration;
  • examination of the As Built configuration or actual configuration, any deviations and waiver and the corresponding requests (RFD, RFW);
  • examination of the supply;
  • review of manufacturing history;
  • review of test documents;
  • review of proceeding documents;
  • review of the team organisation
  • presentation of test sites and means if necessary.



RisksNon-representative tests (configuration, procedures, facilities, etc.)
Technical Readiness Review Board (TRRB)


Activities / documentation

Published in: