This Part of IEC 61968 series, is the first in a series that, taken as a whole, define interfaces for the major elements of an interface architecture for distribution management.<\/p>\n
This International Standard identifies and establishes recommendations for standard interfaces based on an Interface Reference Model (IRM). Subsequent clauses of this standard are based on each interface identified in the IRM. This set of standards is limited to the definition of interfaces. They provide for interoperability among different computer systems, platforms, and languages. Methods and technologies used to implement functionality conforming to these interfaces are recommended in IEC 61968-100.<\/p>\n
As used in IEC 61968, distribution management consists of various distributed application components for the utility to manage electrical distribution networks. These capabilities include monitoring and control of equipment for power delivery, management processes to ensure system reliability, voltage management, demand-side management, outage management, work management, automated mapping, facilities management, and metering. The IRM is specified in Clause 3.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 6<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | Figure 1 \u2013 Distribution management with IEC\u00a061968 compliant interface architecture <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | Figure 2 \u2013 Example utility implementation of IEC\u00a061968 <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | Table 1 \u2013 Document overview for IEC\u00a061968-1 <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 1 Scope 2 Normative references 3 Interface reference model 3.1 Domain <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 3.2 Business functions <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 3.3 Interface reference model Figure 3 \u2013 Typical functions mapped to interface reference model <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | Table 2 \u2013 The Interface Reference Model (IRM) <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 4 Integration infrastructure recommendations 4.1 General 4.2 Requirements analysis methodology 5 Interface profile 5.1 General <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 5.2 Abstract components Figure 4 \u2013 Overview of the interface profile and corresponding subclause numbers <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 5.3 Component adapters 5.4 Interface specification 5.5 Middleware adapter <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 5.6 Middleware services 5.7 Communication services 5.8 Platform environment 6 Information exchange model 6.1 General requirements <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 6.2 Message structures 6.2.1 General recommendation <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | 6.2.2 Message header 6.2.3 Message type payload Figure 5 \u2013 Logical view of an IEC\u00a061968 message <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | Figure 6 \u2013 Example of a message type payload <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | 6.2.4 Explanation of associations Figure 7 \u2013 Example of how message elements are derived from the CIM Figure 8 \u2013 Navigating associations in CIM (UML notation) <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 6.2.5 Compliance philosophy 6.2.6 Extension 6.2.7 Request message Figure 9 \u2013 Navigating associations in message type schemas Figure 10 \u2013 Logical view of a request message <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 6.2.8 Response message 6.2.9 Event message 6.2.10 Fault message Figure 11 \u2013 Logical view of a response message Figure 12 \u2013 Logical view of an event message <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 6.2.11 Signature element 7 Component reporting and error handling (informative) 7.1 Component reporting 7.2 Error message handling Figure 13 \u2013 Logical view of a fault message <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 8 Security and authentication (informative) 9 Maintenance aspects (informative) <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | Annex A (informative) Use of IEC 61968 series of standards <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | Figure A.1 \u2013 Process A: Application of IEC\u00a061968 series by a utility <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | Figure A.2 \u2013 Process B: application of IEC\u00a061968 series by a utility <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | Table A.1 \u2013 Use case template <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | Table A.2 \u2013 Commonly used verbs <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | Annex B (informative) Inter-application integration performance considerations Table B.1 \u2013 Typical load scenario <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | Annex C (informative) Views of data in a conventional electric utility <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | Figure C.1 \u2013 Database views depend on the time and user <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Application integration at electric utilities. System interfaces for distribution management – Interface architecture and general recommendations<\/b><\/p>\n |