1.1 General<\/b><\/p>\n
This part of IEC 61850, which is a Technical Specification, specifies a way to model the code components of IEC 61850 data model (e.g., the tables describing logical nodes, common data classes, structured data attributes, and enumerations) in an XML format that can be imported and interpreted by tools. The following main use cases are supported:<\/p>\n
Generation of SCL data type templates for system specification or ICD files.<\/p>\n<\/li>\n
Validation of SCL data type templates.<\/p>\n<\/li>\n
Definition of private extensions by following the rules of the standard.<\/p>\n<\/li>\n
Adapting rapidly the whole engineering chain as soon as a new version of IEC 61850 data model (an addendum, a corrigenda or a Tissue) affects the content of the standard.<\/p>\n<\/li>\n
Provide tool-neutral textual help to users of tools on the data model contents.<\/p>\n<\/li>\n
Supporting multi-language publication, i.e., enabling the expression of the data model in different languages, through a machine processable format.<\/p>\n<\/li>\n<\/ul>\n
The purpose of this proposal is limited to the publication of the XML format which should support the data model part of any IEC 61850 related standard. The publication of code components themselves will be part of the related IEC 61850 part.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\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 1.1 General 1.2 Namespace name and version <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 1.3 Code Component distribution <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 4 Abbreviated terms 5 Use cases 5.1 Generation of SCL data type templates for system specification 5.1.1 Description of the use case <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 5.1.2 Technical details Figures Figure 1 \u2013 Generation of SCL data type templates for system specification diagrams <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 5.1.3 Information exchanged 5.2 Generation of SCL data type templates for ICD files 5.2.1 Description of the use case <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 5.2.2 Technical details Figure 2 \u2013 Generation of SCL data type templates for ICD files diagrams <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 5.2.3 Information exchanged 5.3 Validation of data model conformity 5.3.1 Description of the use case <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 5.3.2 Diagrams of use case <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 5.3.3 Technical details Figure 3 \u2013 Validation of data model conformity diagrams <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 5.4 Definition of private data model extensions by following the rules of the standard 5.4.1 Description of the use case <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 5.4.2 Diagrams of use case <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 5.4.3 Technical details Figure 4 \u2013 Definition of private data model extensionsby following the rules of the standard diagrams <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 5.4.4 Information exchanged 5.5 Supporting the IEC 61850 data model change management 5.5.1 Description of the use case <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 5.5.2 Diagrams of use case <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | Figure 5 \u2013 Supporting the IEC 61850 data model change management <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 5.5.3 Technical details <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 5.5.4 Information exchanged <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 5.5.5 Common terms and definitions 6 Namespace file breakdown 6.1 General 6.2 Namespace dependencies <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | Figure 6 \u2013 Namespace dependencies <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 6.3 Namespace types 6.3.1 General 6.3.2 Core namespace 6.3.3 Domain namespace 6.3.4 Technical report namespace Figure 7 \u2013 Service Namespace usage <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 6.3.5 Private namespace 7 Overview of the format 7.1 General 7.2 File types 7.2.1 NSD <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | Figure 8 \u2013 Abstract LNClass hierarchy example <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 7.2.2 SNSD <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 7.2.3 AppNS <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 7.2.4 NSDoc 7.3 NSD usage convention 7.3.1 General <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 7.3.2 Element identification 7.3.3 Inheritance and extension <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 7.3.4 DataObject parameterization <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 7.3.5 CDC variants 7.4 Naming convention 7.4.1 File extension 7.4.2 File name <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 7.5 Example 7.5.1 General 7.5.2 NSD file example 7.5.3 SNSD file example <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 7.5.4 AppNS file example 7.5.5 NSDoc file example 8 File usage 8.1 General 8.2 System specification creation <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 8.3 Manufacturer IED creation 8.4 Creation of a non-standard name space Figure 9 \u2013 Specification type creation example <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | 8.5 IED data model validation 8.6 Data model update management <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | Annex A (normative)Schema NSD.xsd <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | Schema IECCopyright.xsd <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Communication networks and systems for power utility automation – Machine-processable format of IEC 61850-related data models for tools<\/b><\/p>\n |