This part of IEC 62699 describes mapping rules and exchange methods for the development of general and extendable integrated services utilizing heterogeneous multi-national or multi- enterprise electronic parts library data. The scope of this technical report is as follows:<\/p>\n
identification and classification of mapping types for mapping heterogeneous electronic parts libraries;<\/p>\n<\/li>\n
definition of general mapping rules and specific mapping rules commonly applying to various mapping types.<\/p>\n<\/li>\n<\/ol>\n
The following aspects are out of the scope of this technical report:<\/p>\n
schematic definition and management of the electronic parts libraries to be mapped;<\/p>\n<\/li>\n
maintenance process for the parts libraries during changes.<\/p>\n<\/li>\n<\/ul>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 1 Scope 2 Application architecture 2.1 General 2.2 Interoperability system <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | Figures Figure 1 \u2013 Interoperability system status <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 2.3 Architecture Figure 2 \u2013 Application architecture <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 2.4 Data flow diagram Figure 3 \u2013 Data flow diagram <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 2.5 Sequence diagram 2.6 Message block Figure 4 \u2013 Sequence diagram Figure 5 \u2013 Message block <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | Figure 6 \u2013 Message control block Figure 7 \u2013 Message contents block <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | Figure 8 \u2013 Message contents block (query request) <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | Figure 9 \u2013 Message contents block (detail request) <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | Figure 10 \u2013 Message contents block (query response) <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | Figure 11 \u2013 Message contents block (detail response) <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 3 Format of the utilized dictionary 3.1 General 3.2 Format configuration of utilized dictionary 3.3 Rules for description of utilized dictionary 3.4 UD_Class format 3.4.1 General Figure 12 \u2013 Message contents block (error response) <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 3.4.2 Utilized class dictionary column Figure 13 \u2013 Example of UD_Class format <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 3.4.3 Standard dictionary column <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 3.5 Root property format 3.5.1 General 3.5.2 Utilized root property dictionary column Figure 14 \u2013 Example of root property format <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 3.6 Property format 3.6.1 General 3.6.2 Utilized property dictionary column Figure 15 \u2013 Example of property formats <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 4 Mapping types 4.1 General <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 4.2 Identification of mapping types Figure 16 \u2013 Example of a case of integration of two parts libraries <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | Figure 17 \u2013 Example of mapping table between SD1 and SD2 Figure 18 \u2013 Example of mapping the properties of the classes <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 4.3 Classification of mapping types 5 Mapping rules 5.1 General mapping model Figure 19 \u2013 Example of cases of each mapping type on the utilized dictionary <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 5.2 Mapping rules for mapping types 5.2.1 Mapping rule for the 1:1 type 5.2.2 Mapping rule for a 1:N, N:1 type Tables Table 1 \u2013 Example of a case of a 1:1 mapping type Table 2 \u2013 Example of a case of a 1:N, N:1 mapping type <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 5.2.3 Mapping rule for a 1:0, 0:1 type 6 Interfaces and information processing 6.1 Information exchange Table 3 \u2013 Example of a case of a 1:0 mapping type <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 6.2 Message types 6.2.1 General 6.2.2 Message for exchange of parts list information Figure 20 \u2013 Example of a case of user interface through a utilized dictionary Figure 21 \u2013 Example of request and response on information exchange <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 6.2.3 Message for detailed parts information exchange 6.2.4 Message for indicating an error or a warning state Table 4 \u2013 Types of message <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Mapping rules and exchange methods for heterogeneous electronic parts libraries – Building an integrated search system<\/b><\/p>\n |