The Integration Quality Assurance Plan PAQI (IQAP) describes all the quality provisions that the Integration Quality Assurance Responsible(RAQI) has to implement for a scientific project in order to produce an item of equipment or an instrument for integration into a payload or a satellite. It describes the substance of these activities and the integration methods applied.
Quality Assurance (QA)
All those planned and systemic actions in a quality system required to provide adequate confidence that an entity will satisfy customer quality requirements.
Product Assurance (PA)
Function consisting in studying, planning and implementing activities to guarantee that a project's design, control, methods and techniques will result in a product compliant with the required standards of quality and levels of confidence.
Integration Quality Assurance Responsible(RAQI)
Person responsible for quality monitoring during the Assembly, Integration and Testing (AIT) phase on behalf of the Product Assurance (PA).
Reports to the integration team on a functional level, checks that quality measures are applied and reports in particular on all major events: non-conformance, departures from procedure, non-conformance investigation.
The PAQI is prepared by the RAQI, and approved by the product Project Responsible. It must be coherent with the Assembly Integration and Testing Plan (PAIE).
It covers quality monitoring for all the assembly, integration and testing tasks, and the campaign tasks (launch preparation) for a given product.
It is drawn up before the activities kick off.
C. Typical content (what to expect)
Presentation of general information defining the purpose and scope of the plan and its subject. Indication of the product concerned and of the associated project.
Perimeter (of the project and/or the product) for which the integration quality plan gives the quality provisions for monitoring the assembly, integration and testing.
3. Organisation and allocation of responsibilities
Description of how the team and AIT activities are organised, as well as the description of the interface with the project authority (e.g. Integrated team, CNES in-house AIT or external).
4. RAQI role and responsibility
Identification of the RAQI's scope of action and responsibility within the project team.
5. AIT activity flow chart
Work breakdown structure and schedule of all AIT activities.
6. Documentation architecture
Definition of the main document formats such as operational procedures, the Events Log (EL), End-Item Data Package (EIDP) and the Log Book (LB).
7. AIT preparation monitoring and execution
Detailed description of QA/RAQI tasks in the AIT preparation and execution phases: monitoring the configuration of resources, the safety plan, the qualification of processes and personnel, checking activities, managing external resources involved.
8. Interface inspection and settings
This section defines how the RAQI ensures that all the interfaces of equipment, instruments, structures and subassemblies are verified, including interfaces with ground facilities that have to be validated (electrical, mechanical and optical ground facilities, and measuring apparatus) to guarantee the expected validation.
9. Functional tests
This testing validates the functioning of integrated equipment before, during and after their tests of resistance to environmental conditions.
10. Tests of resistance to environmental conditions
These tests are for the ground qualification or acceptance of a sub-system or system for the environmental conditions to which it will be subjected on the launcher and in orbit during its mission.
11. Acceptance, handling, storage, relifing, shipping and delivery
Description of the quality provisions implemented for flight equipment and ground equipment in all the phases mentioned above, up to delivery of the integrated product, possibly up to the launch campaign (major activity requiring, on behalf of the project and AIT team, lengthy preparation of the programming, documentation, ground facilities and logistics which must be available at the launch site).
12. Rules of cleanliness and associated provisions
Regular inspections are necessary in order to maintain the required levels of cleanliness. Cleanliness is generally evaluated by an airborne particle count in activity zones and, depending on the type of project, by checking for molecular and/or biological contamination on the surfaces of sensitive equipment. This paragraph recapitulates the requisite levels of cleanliness and describes how the RAQI ensures compliance with these rules.
13. Safety rules
Safety applies to all components of AIT activities, i.e. personnel, premises, equipment, ground facilities and even flight hardware.
This paragraph describes the specific instructions for guaranteeing the expected levels of safety: checking authorisations, appointing a safety manager, etc.
14. Personnel qualifications
The RAQI (and the Assembly, Integration and Testing Responsible -RAIT) must make sure that all the people involved in AIT operations do in fact have the requisite training and qualifications.
This section sets out how training is organised and how the list of authorised personnel is kept up-to-date.
15. Anomaly management and processing
Controlling the procedure for processing anomalies encountered during integration is one of the RAQI's main tasks. The paragraph describes the reporting and processing of anomalies (data entry tool, anomaly processing boards, etc.).
In general and as a reminder, in the AIT phase, for any element on which an anomaly has been observed but which is already assembled or integrated into the instrument, there shall be no intervention performed (after securing) without the approval of the RAITRAIT and the RAQI.
16. Definition of key points and AIT test reviews
This section identifies the types of key points and reviews which punctuate the schedule of AIT activities, the participants and the RAQI's role in the organisation of these meetings.
17. Lessons Learned
Once the integration and tests have been performed and before final delivery, it is essential to go over the lessons learned during the AIT activities.
For this purpose, those responsible for an activity are requested to write an end-of-integration report on all the technical events encountered within their speciality.