CHANGES, DEVIATIONS & WAIVERS PROCESSES

PROCEDURE CHANGES, DEVIATIONS & WAIVERS PROCESSES This document is stored electronically. Printed version might not be the latest. SAOCOM PROJECT COMISION NACIONAL DE ACTIVIDADES ESPACIALES BUENOS AIRES ARGENTINA

SAOCOM PROJECT Number Title Summary CHANGES, DEVIATIONS AND WAIVERS PROCESSES Procedure that defines the processes to employ for changes, deviations and waivers of configuration baseline. Secondary Reference Circulation Level 1 This document is digitally signed Workflow Summary State Assignee Action Completed Date Review mpetruccioli Approved 11-may-2012 Review hmartirena Approved 27-mar-2012 Approve jmedina Approved 11-may-2012 Changes Record Issue Date Author PARA Description A 12/03/2012 P. QUINTELA ALL CREATION Comisión Nacional de Actividades Espaciales (CONAE) from Argentina owns the copyright of this document which is supplied in confidence and which shall not be used for any purpose other than that for which it is supplied and shall be only reproduced, copied or communicated, in whole or in part, for internal use of CONAE, directly or by third parties holding confidentiality agreements with CONAE. Any person other than the authorised holder obtaining possession of this document by finding or otherwise, should send it, together with his name and address, in a sealed envelope to: Comisión Nacional de Actividades Espaciales (CONAE) SAOCOM Project Av. Paseo Colón 751 (C1063ACH) Capital Federal ARGENTINA Letter postage need not be prepaid. Other postage will be refunded. Page 2 of 12

INDEX INDEX... 3 1. OBJECTIVE... 4 2. SCOPE... 4 3. APPLICABLE AND REFERENCE DOCUMENTS... 4 3.1. APPLICABLE DOCUMENTS... 4 3.2. REFERENCE DOCUMENTS... 4 4. DEFINITIONS AND ABBREVIATIONS... 4 4.1. DEFINITIONS... 4 4.2. ABBREVIATIONS AND ACRONYMS... 5 5. ROLES AND RESPONSABILITIES... 5 6. ENGINEERING CHANGE PROCESS... 6 7. DEVIATIONS AND WAIVER PROCESS... 8 8. ANNEX: PAPER FORM... 10 Comisión Nacional de Actividades Espaciales (CONAE) Page 3 of 12

1. OBJECTIVE The purpose of this document is to define the processes to manage changes, deviations and waivers of configuration baseline in SAOCOM project. 2. SCOPE This procedure applies to configuration items and released baseline documentation, and shall be employed by internal (CONAE) and external (Suppliers) personnel working in SAOCOM project to manage changes and/or deviations/waivers of agreed baseline. 3. APPLICABLE AND REFERENCE DOCUMENTS 3.1. APPLICABLE DOCUMENTS SAO-SYS-PR-00001 Information/Document Management System 3.2. REFERENCE DOCUMENTS SAO-SYS-PL-00001 SAO-PAS-PR-00001 CONFIGURATION AND DOCUMENTATION MANAGEMENT PLAN Non Conformances Management System 4. DEFINITIONS AND ABBREVIATIONS 4.1. DEFINITIONS Engineering Changes: An engineering change is a modification or evolution of the product that have his configuration, and therefore their specifications of design, approved or "frozen". An engineering change supposes re-work in the design documentation and could concern parameters like period, costs and quality. Engineering changes can take place in any stage of the life-cycle of the product. There are two ways to request and engineering change: Engineering Change Request or Change Request (ECR/CR): When the process of change is initiated in CONAE or from CONAE towards their suppliers. Engineering Change Proposal or Change Proposal (ECP/CP): When the need of the change is detected by a supplier and submits a proposal to approval for CONAE. Departures: A departure is an impossibility of a product to reach its functional performance or fulfill with its technical requirements. Being the product next the stage of manufacture, in manufacture, or already made. A departure is always limited, and does not imply realizing a change in the engineering documentation. There are two categories of departures: Comisión Nacional de Actividades Espaciales (CONAE) Page 4 of 12

Planned departure, that is to say that one in which there is known in advance the inability to fulfill with the requirements. It is requested by a Request for Deviation (RFD) Unexpected departure, that is to say that one that knows itself once produced the departure. It is requested by a Request for Waiver (RFW) SAOCOM PLM Software: Is a data base contained in a Product Life-cycle Management software that employ the SAOCOM project to manage all project related information. 4.2. ABBREVIATIONS AND ACRONYMS Explanation of abbreviations and acronyms are self-contained in the text of document. 5. ROLES AND RESPONSABILITIES Internal personnel and suppliers of SAOCOM project shall request Engineering Changes and Request for Waiver/Deviation that explains the paragraphs 7 and 8 of this procedure. Suppliers shall replicate this procedure to their subcontractors. Processing of changes and departures on subassemblies and components of the project SAOCOM is on the responsibility of the Configuration Control Board (CCB). This board has as purpose: To process the Change Request / Proposal and the Request for Waiver / Deviation To verify its integrity in terms of information and documentation of reference To evaluate and dispose (to approve or to reject) each of them To authorize the use of configuration documents. CCB is compound by: The project manager The configuration management responsible The project planning responsible The system manager The contract representantive (who processes contractual impacts) The product assurance manager Additional members can participate, according requirement. CONAE and Suppliers shall assure the integrity of project information after changes and departures dispositions: o Configuration baselines shall be updated in conformance with the disposition of approved changes and deviations. Configuration controlled documents shall be revised to incorporate approved changes. CONAE and Suppliers shall record the status of interface definition data and shall ensure that all data is consistent with its product configuration. Suppliers shall identify and control the internal interfaces of its product and those interfaces for which he has received delegated authority. Comisión Nacional de Actividades Espaciales (CONAE) Page 5 of 12

6. ENGINEERING CHANGE PROCESS Change Request CONAE Process Flow Transfer to Tech. Resp. Configuration Control CHANGE REQUEST Explanation The configuration state of the product can evolve due the need of a change detected by CONAE's engineering. The change can be motivated by: a modification in the necessity imperfect translation of the necessity insufficiency of the product or function against the expressed necessity an improvement or optimization of product a technical problem or anomaly a fall in disuse experience feedback The engineer who detects the need of the change, initiates a Change Request in the SAOCOM PLM Software. Control of Configuration transfers the change request towards the technical responsible according to the application area. Impact Evaluation Technical responsible Analysis Technical specialist The technical responsible incorporates technical specialists to evaluate the impact of the change and to generate the analyses and necessary reports. Disposition CCB The CCB dispose the acceptance or rejection of change. Implement Change Reject Change Control of Configuration closes the Change Request and assures the baseline update. If it is necessary the issue the alert to the affected suppliers in order that they issue a Change Proposal in response to the approved Change Request. Comisión Nacional de Actividades Espaciales (CONAE) Page 6 of 12

Change Proposal Supplier Process Flow Transfer to Tech. Resp. Configuration Control CHANGE PROPOSAL Explanation The configuration state of the product can evolve due a change requested by CONAE or a change proposed by the supplier. Any change to a configuration item, in relation with a baseline of approved configuration, will be described, welljustified and pre-classified by the supplier before sending the request for review and disposition. The supplier initiates the process sending a change proposal employing the SAOCOM PLM Software. Control of Configuration transfers the change request towards the technical responsible according to the application area. Impact Evaluation Technical responsible Analysis Technical specialist The technical responsible incorporates technical specialists to evaluate the impact of the change and to generate the analyses and necessary reports that allow classify the proposal. Based on a CR And Minor Classification Technical responsible Not based on a CR Or Major If the Change Proposal is classified as Minor and is based in a Change Request of CONAE the technical responsible implement the change. If the change proposal is classified as Major or is not an answer of a CR, the technical responsible involves the CCB to define the disposition. The CCB dispose the acceptance or rejection of change. Disposition CCB Implement Change Reject Change Control of Configuration closes the Change Proposal and assures the baseline update. Comisión Nacional de Actividades Espaciales (CONAE) Page 7 of 12

7. DEVIATIONS AND WAIVER PROCESS Request for Deviation Supplier Transfer to Tech. Resp. Configuration Control REQUEST FOR DEVIATION Process Flow Explanation When is detected that an item will not fulfill with the requirements or the configuration baseline of the product, there begins a Request for Deviation, being this departure planned on having be detected before its occurrence. Any departure in relation with a baseline of approved configuration, will be described, well-justified and preclassified for the supplier, before sending the request for review and disposition. The supplier initiates the process sending a Request for Deviation employing the SAOCOM PLM Software. Control of Configuration transfers the Request for Deviation towards the technical responsible according to the application area. Impact Evaluation Technical responsible Analysis Technical specialist The technical responsible incorporates technical specialists to evaluate the deviation and define if continue or not with the process. No Acceptable Technical responsible Yes The technical responsible decides if the request for deviation is acceptable giving place to the definition by the CCB. In case of be considering as unacceptable, the RFD is rejected in this step. The CCB dispose the acceptance or rejection of change. Disposition CCB RFD Rejected RFD Approved Control of Configuration closes the Request for Deviation and assures the baseline update. Comisión Nacional de Actividades Espaciales (CONAE) Page 8 of 12

Request for Waiver Supplier Transfer to Tech. Resp. Configuration Control REQUEST FOR WAIVER Process Flow Explanation When is detected that an item does not fulfill with the requirements or the configuration baseline of the product, there begins a Request for Waiver, being this unexpected departure on having be detected after its occurrence. Any departure in relation with a baseline of approved configuration, will be described, well-justified and preclassified for the supplier, before sending the request for review and disposition. The supplier initiates the process sending a Request for Deviation employing the SAOCOM PLM Software. Control of Configuration transfers the Request for Waiver towards the technical responsible according to the application area. Impact Evaluation Technical responsible Analysis Technical specialist The technical responsible incorporates technical specialists to evaluate the deviation and define if continue or not with the process. No Acceptable Technical responsible Yes The technical responsible decides if the request for deviation is acceptable giving place to the definition by the CCB. In case of be considering as unacceptable, the RFW is rejected in this step. Disposition CCB The CCB dispose the acceptance or rejection of change. It involves the NRB depending on the disposition of the associate Nonconformance Report. RFW Rejected RFW Approved Control of Configuration closes the Request for Waiver and assures the baseline update. Comisión Nacional de Actividades Espaciales (CONAE) Page 9 of 12

8. ANNEX: Paper form (To employ only in case of temporary unavailability of PLM Software, and to remit digitalized by e- mail.) Document Number Project Title Date of Request CHANGE REQUEST FORM Description Affected Items Implemented Items Reason for Change Requested Change Resolved AI/RFA/NCR Approvals AUTHORITY NAME DATE SIGNATURE Comisión Nacional de Actividades Espaciales (CONAE) Page 10 of 12

CHANGE PROPOSAL FORM Document Number Project Title Date of Request Description Requester Organization Effectivity Classification Minor Major Limitation of Use Impacted Parameters Cost Schedule Performance Interfaces Interchangeability Mechanical Electrical Thermal Qualification Maintainability Support Training Other Detail of Impact Affected Items Implemented Items Reason for Change Requested Change Resolved ECR/NCR AUTHORITY NAME Approvals DATE SIGNATURE Comisión Nacional de Actividades Espaciales (CONAE) Page 11 of 12

REQUEST FOR WAIVER / DEVIATION Type Waiver Deviation Document Number Project Title Date of Request Description Item Designation Reason For Request Requester Organization Contract /PO Effectivity Adverse Effects Classification Minor Major Limitation of Use (RFW Only) Affected Items Resolved AI/RFA/NCR AUTHORITY NAME Approvals DATE SIGNATURE Comisión Nacional de Actividades Espaciales (CONAE) Page 12 of 12