VDA 4965-1-2010 Engineering Change Management (ECM) - Part 1 ECR Version 3 0《工程变更管理(ECM) 第1部分 有效客户反应(ECR)》.pdf

《VDA 4965-1-2010 Engineering Change Management (ECM) - Part 1 ECR Version 3 0《工程变更管理(ECM) 第1部分 有效客户反应(ECR)》.pdf》由会员分享，可在线阅读，更多相关《VDA 4965-1-2010 Engineering Change Management (ECM) - Part 1 ECR Version 3 0《工程变更管理(ECM) 第1部分 有效客户反应(ECR)》.pdf（97页珍藏版）》请在麦多课文档分享上搜索。

1、A Joint PublicationECM RecommendationPart 1 (ECR) Version 2.0, Issued Aug. 2009 Replacements: Version 1.0 VDA 4965 Part 1 Version 3.0, issued Jan. 2010 Replacements: Version 2.0 ECM RecommendationPart 1 - ECRVersion 2.0, Issued: Aug. 2009 Replaces: Version 1.0 iii SASIG Automotive Industry Action Gr

2、oup (U.S.), Groupement pour lAmelioration des Liaisons dans lIndustrie Automobile (France), Japan Automobile Manufacturers Association (Japan) / Ja-pan Auto Parts Industries Association (Japan), Odette Sweden AB (Sweden), and Verband der Automobilindustrie (Germany) are members of the Strategic Auto

3、motive product data Standards Industry Group- SASIG. These organisations are cooperating in the creation, dis-tribution and use of joint documents, including PDQ (Product Data Quality), PDM Assembly Data Exchange, XMTD (Exchange and Management of Technical Data), DEV (Digital Engi-neering Visualizat

4、ion). SASIG Publications A SASIG publication reflects a consensus of those substantially concerned with its scope and provisions. A SASIG publication is intended as a guide to aid the manufacturer, the con-sumer and the general public. The existence of a SASIG publication does not in any respect pre

5、clude anyone from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the publication. Cautionary Notice SASIG publications are subject to periodic review and users are cautioned to obtain the lat-est editions. Maintenance Procedure Recognizing that th

6、is joint publication may not cover all circumstances, SASIG has estab-lished a maintenance procedure. Please refer to the Maintenance Request Form at the back of this document to submit a request. Contact information Contacts information to SASIG is available on http:/. Copyright and Trademark Notic

7、e The contents of this publication is copyrighted by members of SASIG, i.e. AIAG, GALIA, JAMA/JAPIA, Odette Sweden, and VDA. Copyright is not claimed as to any part of an origi-nal work prepared. ECM RecommendationPart 1 - ECRVersion 2.0, Issued: Aug. 2009 Replaces: Version 1.0 v Table of Contents 1

8、 ECR Reference Process Fundamentals 1 1.1 ECR models and messages related to ECM. 1 1.2 ECR specific rules 1 2 Communication and the ECR Reference Process3 2.1 Overview of the modelling concept and the notation used 3 2.2 Overview of the ECR Reference Process . 4 2.2.1 Purpose4 2.2.2 Phases of the E

9、CR Reference Process 4 2.2.3 Normal flow and status 5 2.2.4 Special flow variants and exceptions.7 2.3 ECR organization model and roles . 12 2.4 ECR Reference Process. 15 2.4.1 Inquiry of ECR phase.15 2.4.2 Creation of ECR phase18 2.4.3 Technical Analysis of ECR phase21 2.4.4 Commenting on ECR phase

10、25 2.4.5 Approval of ECR phase .30 3 ECR Interaction Scenarios and ECR Messages .37 3.1 Description method. 38 3.2 ECR Interaction Scenarios . 39 3.2.1 ECR Interaction Scenario IS1 Participant proposal for a change.39 3.2.2 ECR Interaction Scenario IS2 Participant comments.41 3.2.3 ECR Interaction S

11、cenario IS3 Participant approval44 3.2.4 ECR Interaction Scenario IS4 Participant detailing and comments .47 3.3 ECR Messages 50 3.3.1 Data-oriented ECR Messages.50 3.3.2 Process-oriented ECR Messages52 3.3.3 Use of ECR Messages within the predefined ECR Interaction Scenarios 60 3.3.4 ECR Message he

12、aders and control information62 4 ECR Data Model.63 4.1 Description method. 63 4.2 Usage of the ECM Data Model for the ECR Reference Process. 63 4.3 Usage of ECM Data Model objects within ECR Messages . 69 Appendix A: ECR Interaction Scenario Protocol Specifications71 A.1 Purpose instead it describe

13、s the ECM Recommendation Part 1 ECR Communication and the ECR Reference Process 4 Replaces: Version 1.0 Version 2.0, Issued: Aug. 2009 primary activities in a way which is easy to understand. Appendix A of Part 0 contains notes on the notation used. The following should be noted with respect to the

14、terms “phase“ and “activity“: In the descrip-tion of the phase diagrams, the term “phase“ is used throughout to refer to the processing steps; in the descriptions of the activity diagrams, the term “activity“ is used throughout. For each of the phases described in detail, there is either one activit

15、y which has the same name, or the phase comprises a number of activities. Similarly, the milestones used in the phase diagrams have corresponding states in the activity diagrams. 2.2 Overview of the ECR Reference Process The purpose of the phase will first be described, followed by an overview of ea

16、ch phase. This is then followed by more detailed descriptions of the activities in the course of the normal flow and of special flow variants and exceptions (cancellation, fast-track execution, rollback). 2.2.1 Purpose The objective of the ECR Refernece Process is to determine the extent and impact

17、of the planned change, its feasibility (with regard to design, manufacturing), affected persons or departments, affected parts/documents, the collection of comments and assessments by ex-perts concerning costs, dates, quality, weight, preparation time, and others, and finally the decision to accept

18、or reject the planned change. 2.2.2 Phases of the ECR Reference Process In the context of the overall ECM Reference Process the Specification and Decision on Change phase begins after milestone M3, Potential Solution Defined, has been reached. It starts with the Inquiry of ECR phase, in which a prop

19、osal for a change is received and checked to see whether it will be pursued (see Figure 1). If the change proposal is to be pur-sued further, milestone M3.1, ECR Initiated, is reached and the proposal for a change is cre-ated as a change request in the Creation of ECR phase and is prepared for furth

20、er evalua-tion. Inquiryof ECRCreationof ECRTechnical Analysisof ECRCommentingon ECRApprovalof ECRM3.1:ECRInitiatedM4:ECR ApprovedM3:PotentialSolutionDefinedM3.2:ECRCreatedM3.3:ECRDetailedM3.4:ECRCommentedFigure 1: Phases of the ECR Reference Process If the ECR is to be pursued further, then mileston

21、e M3.2, ECR Created, is reached and tech-nical analysis and evaluation of the ECR is carried out in the Technical Analysis of ECR phase. After finishing the analysis milestone M3.3, ECR Detailed, is reached and the ECR is evaluated from the point of view of other specialist departments in the Commen

22、ting on ECR phase. After finishing commenting milestone M3.4 ECR Commented, is reached, and a deci-sion is made with respect to the ECR in the Approval of ECR phase. If the ECR is approved, ECM RecommendationPart 1 ECRCommunication and the ECR Reference ProcessVersion 2.0, Issued: Aug. 2009 Replaces

23、: Version 1.0 5 the Specification and Decision on Change phase ends and milestone M4, ECR Approved, of the overall ECM Reference Process is reached. 2.2.3 Normal flow and status The ECR Reference Process starts with the status pending when a proposal for an ECR is received from one of the possible i

24、nitiators of an ECR in the activity Inquiry of ECR (see Fig-ure 2). The proposal for an ECR may be accepted or rejected (documented in ACCEPTANCE.decision as shown). In the case of rejection, the ECR Reference Process is terminated with the status disapproved (documented in the value STATUS.status),

25、 otherwise the intermediate status initiated is reached. This is followed by the activity Creation of ECR, in which the regular change request is created, described in more detail and prepared for the subsequent steps. This results in a decision on whether the ECR is accepted or rejected for further

26、 detailing, commenting and approval. If the ECR is rejected, the ECR activity is again terminated in the status disapproved; otherwise the intermediate status created is reached. Creation of ECR is followed by the activity Technical Analysis of ECR, in which the technical aspects and the impact of t

27、he potential change are examined in greater detail and evaluated. In particular, the scope of the change is determined with respect to the parts/documents affected etc. Once the change request has been described in detail, the intermediate status detailed is reached and the activity Commenting on EC

28、R follows, in which the change request is evaluated from other points of view. Once this activity is completed, the intermediate status commented is reached, and the ECR is prepared for the activity Approval of ECR, in which the change re-quest is finally accepted for implementation and the process

29、reaches the status approved. Alternatively, the ECR can ultimately be rejected, in which case the status disapproved is again reached. The individual activities are described in more detail in section 2.4. From the time the activity Technical Analysis of ECR starts until the time the activity Com-me

30、nting on ECR ends, the list of those involved in the ECR Reference Process can be changed (several times if necessary) by carrying out the optional activity Modify Distribution List. Depending on the results of the activities Technical Analysis of ECR or Commenting on ECR, participants can be added,

31、 for example to process analyses or make comments, or removed because they are not affected by the change. ECM Recommendation Part 1 ECR Communication and the ECR Reference Process 6 Replaces: Version 1.0 Version 2.0, Issued: Aug. 2009 joinSpec = (main_path1)main_path1Inquiryof ECRCreation of ECRApp

32、roval of ECROPTIONAL_ITERATIVEOPTIONAL_ITERATIVEStatus.status=disapprovedOPTIONALjoinSpec = (main_path2)Status.status=approvedAcceptance.decision=acceptedAcceptance.decision=rejectedCommentingon ECRTechnicalAnalysis of ECRRAcceptance.decision=rejectedRAcceptance.decision=rejectedRR main_path2Status.

33、status=initiatedStatus.status=createdStatus.status=detailedStatus.status=commentedStatus.status=pendingFigure 2: Normal flow of ECR Reference Process In addition, from the time the activity Technical Analysis of ECR starts until the time the activ-ity Commenting on ECR ends, a list of those involved

34、 in the process (notification list) can be optionally notified of any updates to the ECR by carrying out the activity Distribute ECR Up-date (see also Figure 3). To do this, a subset of those involved in the process can be se-ECM RecommendationPart 1 ECRCommunication and the ECR Reference ProcessVer

35、sion 2.0, Issued: Aug. 2009 Replaces: Version 1.0 7 lected in the activity Select Notification List and the message Notify_ECR_update containing updated ECR data can be sent to the selected people. ReceiveNotify_ECR_updateconcurrentNotificationListSelectNotification ListSendNotify_ECR_updateNotifica

36、tionListNotify_ECR_updateChange TeamDistribution List MemberFigure 3: Activity Distribute ECR Update If external partners are requested to approve the change request during the Approval of ECR phase, these partners can transfer the ECR identifier of the partner if this has been agreed using the mess

37、age Notify_ECR_id_assigned. This identifier is then used in subsequent communication with the partner (see Figure 4). Change TeamExternal ApprovalPerformerReceiveNotify_ECR_idSendNotify_ECR_idNotify_ECR_id_assignedFigure 4: Activity Get External ECR ID 2.2.4 Special flow variants and exceptions In a

38、ddition to the linear process flow described above, it is also possible to exit the process early, to carry out fast-track execution and to roll back the flow. These variants are described below and are partly illustrated in Figure 5. ECM Recommendation Part 1 ECR Communication and the ECR Reference

39、 Process 8 Replaces: Version 1.0 Version 2.0, Issued: Aug. 2009 Commentingon ECRApproval of ECRStatus.status=created Creation of ECRTechnicalAnalysis of ECRSelectNotific. ListNotify ECR rolled backto analysisSelectNotific. ListNotify ECRrolled backto commentingR1R2Acceptance.decision=revision_needed

40、_back_to_analysis Notify_ECR_canceledR1R2R3R3Acceptance.decision=rejectedRRAcceptance.decision=rejectedInquiryof ECRRAcceptance.decision=rejectedStatus.statusdisapprovedRStatus.statusapprovedAcceptance.decision=acceptedStatus.statuscanceledCancelECRRollback ECR toAnalysisRollback ECR toCommentingAac

41、ceptance.decision =revision_needed_back_to_commentingAcceptance.decision =revision_needed_back_to_approvalAcceptance.decision INrevision_needed_back_to_analysisrevision_needed_back_to_commentingrevision_needed_back_to_approvalAcceptance.decision=acceptedFigure 5: Flow variants of the ECR Reference P

42、rocess ECM RecommendationPart 1 ECRCommunication and the ECR Reference ProcessVersion 2.0, Issued: Aug. 2009 Replaces: Version 1.0 9 Cancellation of the ECR The ECR Reference Process can be canceled by means of Cancel ECR during the activities Technical Analysis of ECR through Approval of ECR if the

43、 planned change no longer ap-pears to have sufficient potential benefit during the course of the process, for example as a result of outlay or deadline considerations. In this case, persons on the Distribution List can be notified of this by means of the Notify_ECR_canceled message (see Figure 6). R

44、eceiveNotify_ECR_canceledconcurrentSendNotify_ECR_ canceledDistributionListNotify_ ECR_canceledChange Team Distribution List MemberFigure 6: Activity Cancel ECR Fast-track execution Fast-track execution is a variant of the ECR Reference Process in which special measures are taken compared with the n

45、ormal process with the objective of reducing the throughput time of the ECR or of implementing the change earlier than usual. The following types of fast-track execution are recommended: 1. Fast run: This variant does not involve a special process; those responsible for performing the activities sim

46、ply execute them more quickly than in the normal process. This variant is indicated by a CLASS instance with CLASS.id = fast run referenced by HEADER.change_process_type. 2. Estimation-based approval: With the “estimation-based approval“ variant, it is laid down in the first three activities (Inquir

47、y of ECR, Creation of ECR or Technical Analysis of ECR) that the decision regarding the ECR will be taken on the basis of the estimated value as specified in the activity Technical Analysis of ECR and that review-evaluation comments during the activity Commenting on ECR (see 2.4.4) will be skipped.

48、In this case, only technical comments etc. are exchanged during Commenting on ECR. Estimation-based approval can be selected if, in the opinion of the EC Manager, the estimated evaluation of the ECR from the activity Technical Analysis of ECR is adequate or if time constraints ne-cessitate a shorter

49、 throughput time for the ECR. This variant is indicated by a CLASS instance with CLASS.id = estimation based approval referenced by HEADER.change_process_type. ECM Recommendation Part 1 ECR Communication and the ECR Reference Process 10 Replaces: Version 1.0 Version 2.0, Issued: Aug. 2009 3. Requests approved in advance: The early start of the activity Realization of Change, in particular if provisional approval of the ECR is available