VDA 4965-0-2010 Engineering Change Management (ECM) - Part 0 ECM Version 3 0《工程变更管理(ECM) 第0部分 工程变更管理(ECM) 3 0版本》.pdf

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

1、A Joint PublicationECM RecommendationPart 0 (ECM) Version 2.0, issued Aug. 2009 Replacements: Version 1.0 VDA 4965 Part 0 Version 3.0, issued Jan. 2010 Replacements: Version 2.0 ECM RecommendationPart 0 - ECMVersion 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 0 - ECMVersion 2.0, Issued: Aug. 2009 Replaces: Version 1.0 v Table of Contents 1

8、 Abstract1 1.1 Preface. 1 1.2 Objectives of the recommendation . 2 1.3 Structure of the recommendation 2 1.4 Notational conventions . 3 1.5 Abbreviations 3 1.6 Definitions. 4 1.7 References to standards. 8 2 Scope and Field of Application11 2.1 Engineering change management tasks. 11 2.2 Application

9、 scenarios 12 2.2.1 Data oriented integration .12 2.2.2 Process oriented integration13 2.2.3 Combinations of data and process oriented integration 14 2.3 Recommendations for use 15 3 ECM Reference Process Fundamentals17 3.1 ECM process modeling. 17 3.2 ECM Reference Process 18 3.3 ECM partner model

10、20 3.4 Global rules 22 3.4.1 ECM Reference Process rules 22 3.4.2 Interaction rules for the partners involved .23 3.4.3 Data content rules23 4 Overview of the Modelling Concept and the Notation .25 4.1 ECM process notation 25 4.2 ECM Interaction Scenario notation . 26 4.3 ECM Interaction Scenario Pr

11、otocol Specification notation 26 4.4 ECM Data Model notation. 27 5 Cross-Sub-Process Dependencies and Relationships between Different Phases29 5.1 Dependencies between different ECM Reference Sub-Processes . 29 5.2 Dependencies between ECM Interaction Scenarios of different ECM Reference Sub-Process

12、es 29 5.3 Dependencies between the partial ECM Data Models of different ECM Reference Sub-Processes 29 ECM Recommendation Part 0 - ECM vi Replaces: Version 1.0 Version 2.0, Issued: Aug. 2009 6 Procedural Model for the Application of this Recommendation 31 7 Common Resources for ECM 35 7.1 Common ECM

13、 Messages. 35 7.1.1 Administrative messages 35 7.1.2 Acknowledgement, Warning, and Error Messages. 36 7.1.3 ECM Message header and control information 37 7.2 ECM Data Model 41 Appendix A: ECM Process and Protocol Notation 43 Appendix B: Data Model Notation 49 B.1 ECM Data Model notation. 49 B.2 Intr

14、oduction to EXPRESS-G . 49 Appendix C: IT-Architecture . 53 C.1 Overview 53 C.2 Reference architecture for ECM integration 53 C.3 General decisions regarding integration 54 C.4 Implementation alternatives for integration solutions. 55 C.5 Types of integration 55 C.5.1 Back-end data integration . 56

15、C.5.2 Back-end process integration . 56 C.5.3 Front-end data integration. 56 C.5.4 Front-end process integration . 57 Appendix D: Description of Common Messages 59 D.1 Request_permissive_values. 59 D.2 Respond_permissive_values 59 Appendix E: ECM Data Model and Data Dictionary 63 E.1 ECM Data Model

16、EXPRESS-G 63 E.2 ECM Data Model - Data Dictionary. 73 E.2.1 Acceptance . 73 E.2.2 Acceptance_relationship. 74 E.2.3 Activity. 75 E.2.4 Address . 75 E.2.5 Attachment 76 E.2.6 Boolean_value 78 E.2.7 Change_description 78 E.2.8 Class . 78 E.2.9 Class_attribute 79 E.2.10 Class_hierarchy 80 E.2.11 Class_

17、system 80 ECM RecommendationPart 0 - ECMVersion 2.0, Issued: Aug. 2009 Replaces: Version 1.0 vii E.2.12 Comment .81 E.2.13 Comment_relationship.83 E.2.14 Cost_property 83 E.2.15 Date .85 E.2.16 default_language_string_select.85 E.2.17 description_select 85 E.2.18 Detail85 E.2.19 Document.87 E.2.20 D

18、uration .88 E.2.21 event_or_date_select 88 E.2.22 event_periode_or_date_select 88 E.2.23 event_context_select .88 E.2.24 Event_reference 88 E.2.25 Explicit_scope89 E.2.26 explicit_scope_select.90 E.2.27 Functional_element .90 E.2.28 Functional_element_hierarchy.90 E.2.29 functional_element_select .9

19、1 E.2.30 General_detail91 E.2.31 Header .92 E.2.32 Id 95 E.2.33 Id_or_detail_select.96 E.2.34 Id_relationship96 E.2.35 Implicit_scope 97 E.2.36 Language.97 E.2.37 Mass_property .98 E.2.38 Model_type 98 E.2.39 Module .99 E.2.40 Multi_language_string99 E.2.41 Numerical_value 99 E.2.42 Object.100 E.2.4

20、3 Object_relationship 101 E.2.44 object_select102 E.2.45 Organization.102 E.2.46 Organization_relationship 102 E.2.47 Part 103 E.2.48 Part_instance.103 E.2.49 Person104 E.2.50 PersInOrg_or_Org .104 E.2.51 Person_in_organization .104 E.2.52 Person_in_organization_relationship 105 E.2.53 Person_organi

21、zation_assignment .106 E.2.54 person_organization_assignment_select 107 E.2.55 Person_organization_with_timestamp.107 E.2.56 Platform107 E.2.57 Project108 ECM Recommendation Part 0 - ECM viii Replaces: Version 1.0 Version 2.0, Issued: Aug. 2009 E.2.58 Project_hierarchy 109 E.2.59 project_select 109

22、E.2.60 Property. 109 E.2.61 property_select 110 E.2.62 Property_value 110 E.2.63 Property_value_association 110 E.2.64 Property_value_representation. 111 E.2.65 Property_value_representation_relationship 111 E.2.66 Scheduled_task. 112 E.2.67 Scope_relationship 113 E.2.68 scope_select . 114 E.2.69 Se

23、ries 114 E.2.70 Simple_property_association 114 E.2.71 simple_property_select . 114 E.2.72 Specific_detail . 115 E.2.73 Specific_detail_relationship 117 E.2.74 Status 117 E.2.75 Status_relationship 118 E.2.76 string_select 118 E.2.77 String_with_language 118 E.2.78 String_value 119 E.2.79 Unit 119 E

24、.2.80 Value_range 119 Appendix F: ECM Conformity Requirements 121 F.1 Introduction. 121 F.2 General conformity statement. 121 F.3 ECM conformity classes . 121 F.3.1 ECM Data conformity 121 F.3.2 ECM Message conformity. 121 F.3.3 ECM Interaction Scenario conformity . 122 Appendix G: Handling of Error

25、s, Warnings and Acknowledgements . 123 G.1 Introduction, scope and overview 123 G.2 Message header and control information 124 G.3 Error handling. 128 G.3.1 Message usage and error handling 128 G.3.2 Cooperation-specific input parameters . 129 Appendix H: Message Headers and Control Information. 131

26、 H.1 EXPRESS-G representation. 131 H.2 Data dictionary 132 H.2.1 ECM_context. 132 H.2.2 ECR_context . 133 H.2.3 ECO_context. 133 ECM RecommendationPart 0 - ECMVersion 2.0, Issued: Aug. 2009 Replaces: Version 1.0 ix H.2.4 Message_kind133 H.2.5 Data_oriented_message133 H.2.6 Process_oriented_message 1

27、33 H.2.7 Status_message 134 H.2.8 Message_header .135 H.2.9 Notify_message_header136 H.2.10 Request_message_header136 H.2.11 Respond_message_header.136 H.2.12 Acknowledgement_header 136 H.2.13 Warning_header 136 H.2.14 Error_header137 Appendix I: ECM XML Schema 139 Maintenance Form.141 ECM Recommend

28、ationPart 0 - ECMVersion 2.0, Issued: Aug. 2009 Replaces: Version 1.0 xi Figures Figure 1: Schematic representation of the “data-oriented integration“ application scenario. 12 Figure 2: Schematic representation of the “process-oriented integration” application scenario. 13 Figure 3: Schematic repres

29、entation of the combination of “process-“ and “data-oriented integration” 15 Figure 4: Strategic process synchronization as a fundamental principle in ECM communication 17 Figure 5: ECM Reference Process: Phase overview 18 Figure 6: Harmonized synchronization, e.g., via the ECR Reference Process 20

30、Figure 7: Cascading ECM communication in a cooperative ECM network 21 Figure 8: Communication breakdown in a partner network using an ECR as an example. 22 Figure 9: Using the ECM Reference Sub-Processes and ECM Interaction Scenarios 31 Figure 10: Example illustrating the use of the message header d

31、ata. . 41 Figure 11: Symbols used in the phase diagrams 43 Figure 12: Notation used in UML 2 activity diagrams and state machine diagrams (1/4). 44 Figure 13: Notation used in UML 2 activity diagrams and state machine diagrams (2/4). 45 Figure 14: Notation used in UML 2 activity diagrams and state m

32、achine diagrams (3/4). 46 Figure 15: Notation used in UML 2 activity diagrams and state machine diagrams (4/4). 47 Figure 16: Reference architecture for integrated Engineering Change Management 53 Figure 17: Back-end data integration 56 Figure 18: Back-end process integration 56 Figure 19: Front-end

33、 data integration 57 Figure 20: Front-end process integration 57 Figure 21: Sample instantiation of the Request_permissive_values ECM Message . 59 Figure 22: Sample instantiation of the Respond_permissive_values ECM Message 61 Figure 23: Header definition . 63 Figure 24: Detail definition 64 Figure

34、25: Comment definition 64 Figure 26: Acceptance definition. 65 Figure 27: Status definition. 65 Figure 28: Class definition 66 Figure 29: Instantiation example for using Class data type. 66 Figure 30: Scheduled task definition. 67 Figure 31: Affected object definition 67 ECM Recommendation Part 0 -

35、ECM xii Replaces: Version 1.0 Version 2.0, Issued: Aug. 2009 Figure 32: Data type Scope definition . 68 Figure 33: Hierarchy of structuring categories. 69 Figure 34: Organizational data types 70 Figure 35: Attachment definition . 71 Figure 36: Property data types 72 Figure 37: Multi-language data ty

36、pes 73 Figure 38: EXPRESS-G representation of the message header and control information 132 ECM RecommendationPart 0 - ECMVersion 2.0, Issued: Aug. 2009 Replaces: Version 1.0 xiii Tables Table 1: Message header data for messages of the types request or notify: . 37 Table 2: Message header data for

37、messages of the type respond: 40 Table 3: Description of the elements used in the Data Model diagrams (1/3) 49 Table 4: Description of the elements used in the Data Model diagrams (2/3) 50 Table 5: Description of the elements used in the Data Model diagrams (3/3) 51 Table 6: Message headers and cont

38、rol information for ECM Messages 124 ECM RecommendationPart 0 ECMAbstractVersion 2.0, Issued: Aug. 2009 Replaces: Version 1.0 1 1 Abstract 1.1 Preface Today, considerable effort is expended in the automobile development value chain to con-stantly reduce throughput times in the development processes

39、and to enhance the quality of digital product and process descriptions. Simultaneous engineering in product development and manufacturing planning and intensive cooperation between the various divisions within a company and with external partners are key factors for success in this context. One of t

40、he key challenges to be surmounted when shortening development times and ramp-up times in series manufacturing is to successfully and rapidly implement the changes which occur dur-ing these phases in a joint effort with partners from the fields of development, planning and manufacturing. Some factor

41、s which regularly motivate the wish to initiate changes include: Legislative changes Changes to market conditions or the competitive situation Internal inadequacies in development, planning or manufacturing Quality or safety problems Exploitation of additional optimization potential The desire to ma

42、ke changes also necessitates corresponding changes to the cross-company engineering change management processes between the partners, suppliers and service providers to achieve greater dynamism and flexibility. Thus, mastery of engineering change management processes is increasingly becoming a cruci

43、al factor in the success of coopera-tive ventures in the automotive industry. Suppliers are today integrated into the development and planning process at an early stage. Differences which result from the nature of the part-ners and the projects in which they are involved mean that it is a challengin

44、g task to integrate partners into engineering change management. Small changes can, however, often have a significant impact on costs, processes, and development and manufacturing times. This means that standards and recommendations for structuring and implementing cross-company engineering change m

45、anagement processes and engineering change management data right down to the level of defining company-specific interfaces are indispensable if inte-gration is to be efficient. According to estimates of the ECM project group, cost savings of up to around 40% can be expected as a result of reducing t

46、he times involved in retrieval, coor-dination and processing during the course of cross-partner engineering change management processes. Harmonization of private (i.e. partner-specific) ECM processes is one key contribution to-wards exploiting the potential for improvement during development and whe

47、n starting up se-ries manufacturing. This current recommendation is based on the requirements and experi-ences of the partners in the joint SASIG ECM workgroup. This recommendation has been validated by means of pilot projects in the companies involved. ECM Recommendation Part 0 ECM Abstract 2 Repla

48、ces: Version 1.0 Version 2.0, Issued: Aug. 2009 1.2 Objectives of the recommendation The objective of the recommendation is to provide support for ECM processes with respect to the communication of change data between customers and suppliers. Use of the recom-mendation allows more efficient integrat

49、ion of all the partners involved in a proposed change as a result of: a reduction in the variety of communications methods used in the partner network a reduction in the throughput time for a proposed change improvements in the quality and reliability of the process improvement with respect to the transparency of changes for all those involved the reusability of process agreements, interfaces and tools 1.3 Structure of the recommendation The recommendation is subdivided into individual parts reflecting the ECM Reference Sub-Process (3.3) involved dur