The Integrated Energy and Communication Systems Architecture
Volume IV:
Technical Analysis
EPRI Project Manager
Joe Hughes
Cosponsor
Electricity Innovation Institute Consortium for Electric Infrastructure to Support a Digital Society (CEIDS)
EPRI • 3412 Hillview Avenue, Palo Alto,
California 94304 • PO Box 10412, Palo Alto, California 94303 • USA
800.313.3774 • 650.855.2121 • askepri@epri.com • www.epri.com
DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITIES
THIS DOCUMENT WAS PREPARED BY THE ORGANIZATION(S) NAMED BELOW AS AN ACCOUNT OF WORK SPONSORED OR COSPONSORED BY THE ELECTRIC POWER RESEARCH INSTITUTE, INC. (EPRI). NEITHER EPRI, ANY MEMBER OF EPRI, ANY COSPONSOR, THE ORGANIZATION(S) BELOW, NOR ANY PERSON ACTING ON BEHALF OF ANY OF THEM:
(A) MAKES ANY WARRANTY OR REPRESENTATION WHATSOEVER, EXPRESS OR IMPLIED, (I) WITH RESPECT TO THE USE OF ANY INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM DISCLOSED IN THIS DOCUMENT, INCLUDING MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, OR (II) THAT SUCH USE DOES NOT INFRINGE ON OR INTERFERE WITH PRIVATELY OWNED RIGHTS, INCLUDING ANY PARTY'S INTELLECTUAL PROPERTY, OR (III) THAT THIS DOCUMENT IS SUITABLE TO ANY PARTICULAR USER'S CIRCUMSTANCE; OR
(B) ASSUMES RESPONSIBILITY FOR ANY DAMAGES OR OTHER LIABILITY WHATSOEVER (INCLUDING ANY CONSEQUENTIAL DAMAGES, EVEN IF EPRI OR ANY EPRI REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES) RESULTING FROM YOUR SELECTION OR USE OF THIS DOCUMENT OR ANY INFORMATION, APPARATUS, METHOD, PROCESS, OR SIMILAR ITEM DISCLOSED IN THIS DOCUMENT.
ORGANIZATIONS THAT PREPARED THIS DOCUMENT
General Electric Company led by GE Global Research (Prime Contractor)
Significant Contributions made by
EnerNex Corporation
Hypertek
Lucent Technologies (Partner)
Systems Integration Specialists Company, Inc.
Utility Consulting International (Partner)
ORDERING INFORMATION
Requests for copies of this report should be directed to EPRI Orders and Conferences, 1355 Willow Way, Suite 278, Concord, CA 94520. Toll-free number: 800.313.3774, press 2, or internally x5379; voice: 925.609.9169; fax: 925.609.1310.
Electric Power Research Institute and EPRI are registered service marks of the Electric Power Research Institute, Inc. EPRI. ELECTRIFY THE WORLD is a service mark of the Electric Power Research Institute, Inc. All other trademarks are the property of their respective owners.
Copyright © 2002, 2003, 2004 Electric Power Research Institute, Inc. All rights reserved.
This document describes research sponsored by EPRI and Electricity Innovation Institute.
The publication is a corporate document that should be cited in the literature in the following manner:
THE INTEGRATED ENERGY AND COMMUNICATION SYSTEMS ARCHITECTURE, EPRI, Palo Alto, CA and Electricity Innovation Institute, Palo Alto, CA: 2003 {Product ID Number}.
To summarize, this volume discusses:
· Architectural Principles Relates the principles introduced in Volume I to the specifics of the analyses detailing them herein
· Architectural Analysis The high-level strategies used to solve the problem, the different environments, as well as common services, information models, and interfaces that were identified as the results of this analysis.
· Technology Analysis A comparative analysis of the universe of technologies available and which are most closely aligned with IECSA requirements
· Deployment Scenarios To identify common integration scenarios and detail how IECSA can be used to accomplish them.
· Benefits and Conclusions A brief summary of the benefits from a technology and interoperability standpoint.
· Appendices A..E Detailed discussions of research by the team
This section reprises the levels of abstraction framework presented in Volume I. By successively abstracting the architectural analysis via these descriptions, the dominant aspects of architectural issues were exposed and detailed.
· Business needs
· Strategic vision
· Tactical approach
· Deployment scenarios
A primary goal of the IECSA project is designing a common architecture for utilities. This section summarizes the principle modeling/analysis elements identified and applied in the IECSA
· Requirements Common industry requirements permit application constraints to be concisely and precisely defined.
· Services Refining applications into the services that can be combined in various ways to achieve functional goals.
· Information models Common building blocks of information exchanged to accomplish applications.
· Interfaces Low level primitives that act as atoms to build the molecular common services of IECSA. The definition of these atoms facilitates the conveyance of the common services across environmental boundaries that may utilize different technologies.
This section summarizes the results of detailed analysis performed on the following important but often considered independent subjects crucial to collectively achieving a robust architecture.
· Enterprise management
· Data management
· Platform
· Communications
· Security
In deploying applications using IECSA, this section identifies the issues to consider and proposed solutions in performing integration.
· Field Device Integration Shows how 61850 and DNP3 based SCADA systems can be integrated to provide unified rich model based device access and control.
· Enterprise Management Encompasses the integration of a DMTF based Enterprise Management systems with TC 57 based utility systems.
· Application Integration How a deployment of the CIM and GID can be used to create a platform for legacy application integration.
· Data Analysis As recovery of money spent on asset related operations is not guaranteed, it is critical that asset related costs be managed wisely.
· Energy Market Integration Describes how a utility might integrate Energy Market Transaction Servers with utility operational systems.
This section briefly summarizes how IECSA facilitates the realization of the following benefits:
· Reusable infrastructure
· Interoperability through standards
· Available off the shelf adaptors
· 3rd party applications
· Extensibility
· Incremental approach
The following table identifies and summarizes the major sections in this volume:
|
Section 1
Principles and Requirements |
The overall principles and requirements used to develop the architecture and a brief description of the problems it was intended to solve. |
|
Section 2
Analysis |
The high-level strategies used to solve the problem, the different environments, as well as common services, information models, and interfaces that were identified as the results of this analysis. |
|
Section 3
Technology Recommendations |
Discussion of the implementation of the common modeling elements (services, information models, and interfaces) using specific recommended technologies within the defined set of environments. |
|
Section 4
Deployment Scenarios |
Guidelines and examples of how the architecture should be deployed by utilities. |
|
Section 5
Benefits |
Summarized the benefits of IECSA from a technical standpoint |
|
Appendix A:
Security |
A comprehensive discussion of security considerations for energy industry and related communications |
|
Appendix B:
Network Management Technologies |
A discussion of network management technologies and needs |
|
Appendix C: Resilient Communication Services |
Discusses those technologies and requirements that are necessary for robust communications networks. |
|
Appendix D:
Technologies, Common Services, and Best Practices |
A detailed summary of all the individual technologies, common services, and best practices identified by the IECSA project |
|
Appendix E:
Environments |
A detailed description of the IECSA environments |
1. Architectural Principles and Requirements
1.1 Enterprise Activities
and Domain Use Cases
1.2.1 Data Management and
Exchange Issues
1.2.4 Domain Use Case
Requirements Analysis
1.2.5 Analyses of
Abstract Use Cases
1.2.6 Abstract Use Case
Requirements Conclusion
1.3.2 Technology
Independent Architecture
1.3.4 Architecture
Conclusions
2.1.2 Domain Use Case
Analysis
2.1.3 Abstract Use Case
Analysis
2.2.1 Common System and
Network Management Services
2.2.2 Common Data
Management and Exchange Services
2.2.3 Common Platform
Services
2.2.4 Common Security
Services
2.3.1 Enterprise
Management Common Information Models
2.3.2 Power Systems
Common Information Models
3. Technology and Implementation Recommendations
3.1 Enterprise Management
Technologies
3.1.1 Analysis of
Enterprise Management Technologies
3.1.2 Overlapping/
Harmonizing/ Missing Enterprise Management Technologies
3.2 Data Management and
Exchange Technologies
3.2.1 Horizontal Data
Management Technologies
3.2.2 Field Device
Technologies
3.2.3 Control
Center/Operations Technologies
3.2.4 Energy Market
Energy Market Technologies
3.3.1 Analysis of
Platform Technologies
3.4 Communications
Infrastructure Technologies
3.4.1 Analysis of
Communications Infrastructure Technologies
3.4.2 Communication
Infrastructure Integration and Federation Strategy
3.4.3 Overlapping,
Harmonizing and Missing Communications Infrastructure Technologies
3.5 Security Technology
Overview
3.5.2 Service Specific
Technological Recommendations
3.5.3 Communication
Technology Specific Recommendations
3.5.4 Technologies that
need to be created
4.2.1 Field Device
Integration Deployment Scenario
4.2.2 Enterprise
Management and Power Systems Integration Deployment Scenario
4.2.3 Application
Integration Deployment Scenario
4.2.4 Asset Management
Deployment Scenario
4.2.5 Energy Market
Integration Deployment Scenario
APPENDIX A - SECURITY....................................................................... A-1
APPENDIX B – NETWORK MANAGEMENT TECHNOLOGIES......... B-1
APPENDIX C – RESILIENT COMMUNICATION SERVICES.............. C-1
APPENDIX D – TECHNOLOGIES, SERVICES, AND BEST PRACTICES
...................................................................................................................... D-1
Appendix E - Environments............................................................ E-1
Figure 1‑1: IECSA
Reference Architecture Framework
Figure 1‑2 Domain
Use Cases From List of Business Functions
Figure 1‑3:
Integrated Energy and Communication Systems Architecture (IECSA) RM-ODP Model
Figure 1‑4 Abstract
Use Cases from Domain Use Cases
Figure 1‑5
Environments from Requirements
Figure 1‑6 The IECSA
Abstract Use Cases
Figure 1‑7 IECSA
Secure Enterprise Architecture
Figure 1‑8
Enterprise Management and Power System Management Treated Independently
Figure 1‑9
Integration of Enterprise and Power System Management
Figure 1‑10 Energy
Market Transaction Service Communication
Figure 1‑11
Integration Of Device Data
Figure 1‑12
Applications To Be Integrated
Figure 1‑13
Application Integration
Figure 1‑14 Example
Of Integrated Data
Figure 1‑15 Field
Service Integration Example
Figure 1‑16:
Representation of Security Domain Concept
Figure 1‑17
Point-to-Point Integration
Figure 1‑18 Diagram
of Components, Services, and Interfaces
Figure 1‑20
Technology-Independent Architecture
Figure 1‑21 IECSA
Analysis Logic Flow
Figure 1‑22 Utility
Integration Layering
Figure 2‑1 Example
of eCommerce Message Flow
Figure 2‑3 Exposing
Server Data
Figure 2‑4 Device
Information Exchange Model
Figure 2‑5
Application Integration Example
Figure 2‑7 Publish
and Subscribe
Figure 2‑8
Traditional Data Warehouse Architecture
Figure 2‑9 Common
Information Model Based Data Warehouse
Figure 2‑10 Example
Of A Data Warehouse Star Schema
Figure 2‑11 Data
Warehouse Connected to a Message Bus
Figure 2‑12 Data
Mart Proliferation
Figure 2‑13 Example
Of A CIM/GID Based Data Warehouse
Figure 2‑14 Example
of CIM/GID Warehouse Connected to a Message Bus
Figure 2‑15 Example
Information Model
Figure 2‑16 Use of a
Common Exchange Model
Figure 2‑17
Applications Connect to Off the Shelf Middleware Via the Standard API’s
Figure 2‑18 Applying
Technologies to Environments
Figure 2‑19 Ways
That A Generic Interface Can Be Applied
Figure 2‑21 Example
Generic Interface
Figure 2‑22 Summary
of IECSA Environments
Figure 2‑23
Technology Independent Architecture
Figure 3‑1 RDF,
RDFS, and OWL Build on Existing W3C Work
Figure 3‑2 The Tree
of Knowledge Technologies
Figure 3‑6 The
Evolution of DNP3 and IEC61850
Figure 3‑10 IEC61850
Object Model
Figure 3‑12
Simplified Fragment of CIM Power System Model
Figure 3‑13
Simplified Fragment of CIM Asset/Work Model
Figure 3‑14
Generalizations for power system resource and conducting equipment
Figure 3‑15 Defining connectivity for conducting
equipment
Figure 3‑16
Transformer model illustrating use of aggregation
Figure 3‑17:
IEC61850 Models and Connections with IEC61970 Models
Figure 3‑18 Proposed
Harmonization of 61850 and 61970 Information Models
Figure 3‑19 Example
of a Full Mesh type of Namespace
Figure 3‑20 Example
TC57PhysicalNamespace
Figure 3‑21 Example
TC57ClassNamespace
Figure 3‑22 Example
TC57ISNamespace
Figure 3‑23
Traditional view of utility data
Figure 3‑24 Customer
data within a CIM Network View