SABRe B2.1: Design & Development. Supplier Briefing Pack.

Transcription

1 SABRe B2.1: Design & Deveopment. Suppier Briefing Pack Ros-Royce pc The information in this document is the property of Ros-Royce pc and may not be copied or communicated to a third party, or used for any purpose other than that for which it is suppied without the express written consent of Ros-Royce pc. This information is given in good faith based upon the atest information avaiabe to Ros-Royce pc, no warranty or representation is given concerning such information, which must not be taken as estabishing any contractua or other commitment binding upon Ros-Royce pc or any of its subsidiary or associated companies. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

2 Introduction 2 This brief expains the essentia requirements of the SABRe Design & Deveopment Process and how it works. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

3 Contents The briefing pack wi expain: Design and Deveopment Process Ros-Royce Requirements RRES90009 Technica Requirements Contract Specific Requirements Design & Deveopment Quaity Pan Compiance Matrix ECM Process Reationship Diagram RR Component Definition Review Process 3 SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

4 Scope 4 The Design and Deveopment process appies to suppiers authorised by Ros-Royce to create design definitions, using their own design rues and standards. Suppiers of Design and Make items. Design definitions may range from simpe mechanica components to software and compex eectronic or mechanica assembies. Note: that design definitions are compete and detaied descriptions of a product incuding its functiona characteristics, suppy chain, cost in addition to how to make, operate, maintain, support it in service and disposa. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

5 The Design & Deveopment Process 5 Ros-Royce sha initiate work with the suppier to deveop a product concept. Ros-Royce wi define any contract specific process requirements. Ros-Royce wi indicate on a compiance matrix the RRES requirements appicabe to the suppier s products/ programmes. The suppier sha assess their Quaity Management System against the appicabe requirements, and make any necessary updates. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

6 The Design & Deveopment Process 6 The suppier sha compete a Design and Deveopment Quaity Pan (DDQP), incuding a Design and Deveopment Compiance Matrix. Generic tempates for both are avaiabe from Ros-Royce via your key point of contact. Ros-Royce wi perform suppier seection: A DDQP an is expected as a prerequisite for suppier seection. Upon successfu seection and project / programme aunch the suppier and Ros-Royce sha work concurrenty to deveop the technica requirements, design definition and production component. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

7 The Design & Deveopment Process 7 The suppier sha operate as defined within the DDQP. The suppier sha adhere to the Ros-Royce Component Definition Review process through satisfaction of Design Review Requirements in RRES The suppier sha ensure the DDQP remains up-to-date and compiant. Ros-Royce wi perform reguar assessment activities to: Verify the suppiers compiance to SABRe, RRES and the DDQP Assess suppier capabiity. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

8 Seect suppier based on a baanced assessment of technica, quaity & financia criteria Deveop Product Concept The Design and Deveopment Process 8 Suppier Create & update DDQP to demonstrate compiance to RRES & contract specific requirements Submit DDQP for review / approva Operate Design & Deveopment activity in according to DDQP Ros-Royce Engineer Ros-Royce Authorised Engineering Signature Define contract specific requirements Define scope & appicabiity of RRES90009 N DDQP compies with RRES 9009 & contract specific requirements? Y Accept DDQP Ros-Royce Manufacture Engineer Purchase Ros-Royce Suppy Chain Management Team (SCMT) SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

9 Ros-Royce Requirements for Design & Deveopment Activities 9 As a resut of service and product deveopment experience, Ros- Royce recognises that rigorous and meticuous contro over a activities and organisations contributing to the product design are essentia in reducing risks to product integrity, reiabiity, quaity and business continuity. Ros-Royce requires that the design practices owned by a suppier, (incuding contro of sub-tier suppiers), are at east equivaent to its own. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

10 Ros-Royce Requirements for Design & Deveopment Activities 10 Design and Deveopment suppiers sha ensure that they and their suppy chain compy with the foowing requirements: Ros-Royce engineering standard RRES requirements for design and deveopment Activities Technica requirements - The product requirements produced by Ros-Royce through engagement with Ros-Royce customers and the suppier Any additiona contract specific process requirements SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

11 RRES RRES requirements for design and deveopment activities The suppier sha agree with Ros-Royce the appicabiity of each RRES requirement to the products/programmes of a suppier through the deveopment of the Compiance Matrix incuded within the Design and Deveopment Quaity Pan. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

12 Technica Requirements 12 The suppier sha agree with Ros-Royce the technica requirements (Product requirements produced by Ros-Royce through engagement with Ros-Royce and the suppier) Top eve requirements from Ros-Royce are expressed in a Project Requirement Document or Business Requirements Document which is used to hep deveop the technica requirements. The technica requirements may be expressed by a singe Technica Requirements Document (e.g. Component Requirements Document, Enveope Drawing, Request for Proposa, Standards Document or any combination of these) SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

13 Technica Requirements 13 Technica requirements wi incude (but are not imited to): Functiona and performance requirements Reiabiity, integrity and ife requirements Environmenta requirements (space, therma, vibration, etc) Appicabe statutory and reguatory requirements Appicabe Ros-Royce design poicies (e.g. safety) SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

14 Contract Specific Requirements 14 The suppier sha agree with Ros-Royce any additiona contract specific process requirements and sha ensure that these requirements are detaied in the suppier s contract with Ros-Royce and referenced in the Design and Deveopment Quaity Pan SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

15 The Design & Deveopment Quaity Pan 15 The suppier sha produce and agree a Design and Deveopment Quaity Pan with Ros-Royce which incudes the competed RRES compiance matrix. The Design and Deveopment Quaity Pan (incuding the compiance matrix) must: Demonstrate that the suppier s design practices give a satisfactory means of compiance to RRES Demonstrate means of compiance to any additiona requirements over and above RRES Describe interfaces, communications and imits authority between the suppier and Ros-Royce SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

16 Design & Deveopment Quaity Pan - Update 16 The DDQP must be updated as a resut of: New or evoving requirements. Suppier quaity system deveopment. Additiona scope or new business. The DDQP shoud cover as many Ros-Royce goba projects / appications as possibe. Encourage process commonaity across a Suppier s Ros- Royce projects / programmes, minimising differences. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

17 The Compiance Matrix. 17 In the compiance matrix, the suppier sha: Reference the suppier procedure that demonstrates compiance to each appicabe RRES requirement. Record a forma response against each appicabe RRES requirement to describe how compiance is demonstrated. Detai any mitigating actions where compiance is not demonstrabe. Identify the eve of compiance / aignment. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

18 Exchange Of Engineering Communications (inc. Technica Data) Between Ros-Royce & Suppiers: Using Engineering Coordination Memorandums (ECM) 18 Purpose To define the process for the exchange of forma engineering communications (incuding technica data) between Ros-Royce, and suppiers, by means of Engineering Co-ordination Memorandum (ECM). The purpose of the ECM format is: To provide a consistent and traceabe document. Forma transfer of information between Suppiers and Ros- Royce. A discipined channe for communications. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

19 Using Engineering Coordination Memorandums (ECM) Process Description This process provides the means for the forma management (receipt, issue, tracking, monitoring, traceabiity and progression) of an ECM, together with a ibrary system and ong term storage as defined by SABRe, aowing traceabiity and retrieva of information. Exchange of an ECM between RR and suppier companies is either via eectronic or physica media with the suppier. Within the framework of engineering communications with the suppier there are many forms of data exchange, e.g technica carification and instruction, design anaysis and review, programme definition and contro etc. A these forms of engineering communication by the suppiers wi ony have forma standing if conducted in accordance with an agreed co-ordination memo procedure. Transfer of data etc by person to person emai is not considered to be formay binding. 19 SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

20 Using Engineering Coordination Memorandums (ECM) Process Description (continued) An ECM is not a contractuay binding document; however it is admissibe evidence in the event of a ega dispute. 20 Advice on the appicabiity of this process can be obtained from the Ros-Royce ECM Co-ordinator (Process Owner). If an ECM process has aready been set up and agreed within the Design and Deveopment Quaity Pan (DDQP) then this can be used as an aternative to this process. It is expected that both the customer and suppier respond to incoming ECM s in a timey manner, i.e. ess than 10 days. Exception to this is where a response date is requested on the incoming ECM. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

21 Using Engineering Coordination Memorandums (ECM) Fow Chart 21 SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

22 Using Engineering Coordination Memorandums (ECM) Records - Current Documents Outgoing ECM - A fuy signed hard copy (either origina or scanned) is stored by ECM Co-Coordinator in a retrievabe fiing system. 22 Incoming ECM - A copy is printed and stored in a retrievabe fiing system. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

23 Using Engineering Coordination Memorandums (ECM) Records - Archive Documents 23 Records are retained in accordance with category A requirements as described beow: - The generic retention period for category A records reating to products is ten years after the product type is withdrawn from use (For civi aerospace products this means ten years from withdrawa of the type certificate and for miitary aerospace products this means ten years from the date that Ros-Royce notifies customers that Ros-Royce wi no onger support the product). Other category A records need to be retained permanenty. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

24 Using Engineering Coordination Memorandums (ECM) Joint Decaration A ECMs transmitted between the suppier and Ros-Royce sha have the foowing statement added: This document contains Suppier Name and Ros-Royce (RR) PROPRIETARY INFORMATION and sha at a times remain the property of the Suppier and/or Ros-Royce as appropriate; no inteectua property right or icense is granted by the Suppier or Ros-Royce in connection with any information contained in it. It is deivered on the express condition that said document and the information contained in it sha be treated as confidentia, sha not be used for any purpose other than that for which it is hereby deivered, sha not be discosed in whoe or in part to third parties and sha not be dupicated in any manner, without prior written consent from the Suppier and/or Ros-Royce as appropriate. 24 Ros-Royce wi not accept any charge as the soe resut of the contents of a ECM. Any Suppier action invoving a charge to Ros-Royce wi ony be authorised by a Ros-Royce purchase order. Incude appropriate export contro rues/reguations. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

25 Using Engineering Coordination Memorandums (ECM) 25 Authorisation A ist of approved signatories sha be maintained by both Ros-Royce and the design sub-contractor and kept up to date as necessary. Seria Numbering A Engineering Coordination Memorandums sha be uniquey identified by a seria number. Bocks of numbers to be used by the suppier and Ros-Royce sha be mutuay agreed. The suppier and Ros-Royce sha aocate a seria number from within the aocated bocks as necessary. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

26 Using Engineering Coordination Memorandums (ECM) Revision Numbers Each ECM sha have a revision identifier aong with the seria number. The recommended revision number process is as foows: 1) An ECM initiated by Ros-Royce wi start with R0. The suppier response to a R0 ECM wi be *1. Ros-Royce response to a *1 ECM wi be R2 and the suppier response to a R2 ECM wi be *3. etc. 26 2) An ECM initiated by suppier wi start with *0. The Ros- Royce response to a*0 ECM wi be R1. The suppier's response to a R1 ECM wi be *2 and the Ros-Royce response to a *2 ECM wi be R3. etc. * Suppier code etter SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

27 Using Engineering Coordination Memorandums (ECM) 27 ECM Format The format for an ECM sha at east contain the foowing: Compiing - Be dated - Be uniquey identified - Carry appicabe part numbers where appropriate - Identify the correspondence initiator - Be sent/received through identified points of contact - Estabish and meet agreed targets for communication responsiveness. The ECM can be either a compete message in itsef, or be used as a cover sheet to formaise the transmission of separate documents, incuding the minutes of meetings. Use must be made of the revisions to answer and maintain continuity of discussion on a subject. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

28 Using Engineering Coordination Memorandums (ECM) 28 Transmission of an ECM ECMs sha be transmitted either directy between the nominated ECM approver(s) or the agreed points of transmission/distribution. ECM Addressee Register Ros-Royce and the suppier sha nominate the primary addressee to whom a respective ECM sha be sent. An ECM sha be sent via a designated point of contact. Both Ros-Royce and the suppier sha maintain a register that records the creation, transmission and cosure (when actions are requested) of each ECM. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

29 Using Engineering Coordination Memorandums (ECM) ECM tempate 29 SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

30 X-Ref X-Ref Reationship Diagram 30 The reationships between the management contros (Requirements, DDQP, Compiance Matrix etc), within the scope of the design and deveopment process, are detaied in the reationship diagram. Technica Requirements Contract Specific Process Requirements Design and Deveopment Output Product Design Technica Data Package RRES for Design & Deveopment Activities Design & Deveopment Quaity Pan Suppier Process Interface Description Design & Deveopment Compiance Matrix SABRe Design and Deveopment Process SABRe Compiance SABRe Requirements SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

31 Ros-Royce Definition Review Process 31 This Ros-Royce Definition Review (DR) process is used to assure the quaity of new components, component packages and / or sub-system definitions by means of review gates. The process assumes an integrated team approach and that the activities to create the component and / or sub-system are being conducted in accordance with a Programme Management Pan deveoped coaborativey and agreed by both the Suppier and Ros-Royce. The Ros-Royce DR consists of nine possibe Design Reviews. The appicabiity of each Design Review (to the scope of product / programme) wi be agreed with the Suppier and detaied in an integrated Programme Management Pan. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

32 Ros-Royce Definition Review Process 32 Within RRES there is a description of each design review, information regarding the Ros-Royce Design and Deveopment inputs and a set of design review checkists, which wi be used with the Suppier each appicabe review. The Suppier shoud be aware however, that each Ros-Royce business may taior the checkists for the specific product or programme scope. The Suppier sha detai how its own NPI process aigns with this Definition Review in the Suppiers Design and Deveopment Quaity Pan. The diagram shown on the next page is a generic representation of the aignment of Suppier / Ros-Royce New Product Introduction (NPI) / Modification processes through the Ros-Royce Definition Review. SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

33 Ros-Royce Component Definition Review Process (RR CDRP) 33 Ros-Royce NPI / Modification Process TECHNICAL REQUIREMENTS COMPONENT DEFINITION REVIEW PROCESS DR 0 DR 1 DR 2 DR 3 DR 4 DR 5 DR 6 DR 7 DR 8 DESIGN DESIGN VERIFICATION VALIDATION PROGRAMME MANAGEMENT ORGANISATION AND RESOURCE MANAGEMENT RRES REQUIREMENTS FOR DESIGN AND DEVELOPMENT ACTIVITIES DESIGN AND DEVELOPMENT QUALITY PLAN Suppier NPI / Modification Process SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012

34 Questions. 34 Shoud you have any further questions regarding this matter, pease contact your norma Ros-Royce purchasing contact (buyer) from the business unit pacing the purchase order(s). SABRe : Design & Deveopment Process Suppier Briefing Pack : Issue 3.0 Nov 2012