1© 2005 Electric Power Research Institute, Inc. All rights reserved.
Industry-Level Architecture Development: Integrating the Developing InfrastructuresJoseph Hughes
Electric Power Research Institute Palo Alto, CA
2© 2005 Electric Power Research Institute, Inc. All rights reserved.
Developing System Architecture
• Definition of an “Architecture”– Defines the overall structure, organization,
performance and management of a distributed computing system
– Enables: • Analysis of system-wide technical and business issues such
as interoperability, scaleability, management, security and related technical infrastructure
• Communications among stakeholders
3© 2005 Electric Power Research Institute, Inc. All rights reserved.
What is an Industry Level Architecture?
Architecture: The Structure of Components, their relationships, and the principles and guidelines governing their design and
evolution over time*.
*DoD Integrated Architecture Panel, based on IEEE Std 610.12
4© 2005 Electric Power Research Institute, Inc. All rights reserved.
Drivers behind Architecture Development
• Systems development lack an overall enterprise-wide implementation perspective
• Infrastructure is underspecified – Unable to scale up from demonstration “pilots”– Major issues not addressed systematically
• Integration across the enterprise• Integration across the industry• Data sharing, hardware resource sharing• No Integrated System Management • “Stovepiped” systems• Disparate Standards Initiatives
5© 2005 Electric Power Research Institute, Inc. All rights reserved.
Need For Architecture Level Development
• Applications cut across traditional technical domains:– Real Time Systems and Information Technology– Generation, Transmission, Distribution, Consumer
Systems Integration– Standards need to be more rigorously integrated as
they develop– Cross Industry Integrations are necessary:
• Communications and Advanced Automation• T&D operations and Building Automation• In Building Integration, HVAC, Appliance, Consumer
Electronics
6© 2005 Electric Power Research Institute, Inc. All rights reserved.
Architecture Challenges
• Technical Discipline of Architecting Large Scale systems still seeking to mature
• Standards for Architecture Development in development• Standardized Notation(s) known as “Architecture
Definition Language” are still under development• Developing Standards at a component level is
inadequate for future higher levels of integration
7© 2005 Electric Power Research Institute, Inc. All rights reserved.
ZigbeeAlliance
Sample of Key Standards Development Organizations and Consortia
ISOIECInternationalStandards-DevelopmentOrganizations (SDO’s)
National Organizations
Trade, technical,and government
Consortia anduser groups
JTC 1
ANSI(US)
EIA IEEE
GermanyFrance
API ASHRAE NIST
BritishCanada
UCAInternational
Utility AMI
Metering Group
AEIC
CENCENELEC
IEC 61970/68CIM Users
IEC 61850Users Open AMI
ITU
BACnet™Manufacturers
BACnet™Users
RolesCategories
International Collaboration,
Technical Stability
National Representation
Specific Domain Standards
Issues Resolution,
Testing, Support
8© 2005 Electric Power Research Institute, Inc. All rights reserved.
IEC TC57 Working Groups
• WG 3: Telecontrol protocols • WG 10: Power system IED communication and associated data models• WG 13: Energy management system application program interface (EMS -
API) • WG 14: System interfaces for distribution management (SIDM) • WG 15: Data and communication security• WG 16: Deregulated energy market communications• WG 17: Communications Systems for Distributed Energy Resources (DER) • WG 18: Hydroelectric power plants - Communication for monitoring and
control• WG 19: Interoperability within TC57 for the Long Term• WG20: Planning of (single band) power line carrier systems (IEC 60495),
Planning of (single sideband) power line carrier systems (IEC 60663)
9© 2005 Electric Power Research Institute, Inc. All rights reserved.
Revenue Metering Standards Development Initiatives: “The Radar Screen”
IEEE SCC-31
ANSI X3EDI UIG
IEC TC 57 WG 9DLMS
UCA International Users Group
ANSI C12.x
EIA 600/721
GTI UCAAWWA
AEIC(Users Group)
IEC TC 57WG 10,19,15,16
IEC TC 13 WG 14
IndustryCanada
CIM UsersGroup
AMRA
Open AMI UsersGroup
10© 2005 Electric Power Research Institute, Inc. All rights reserved.
Home “Automation” Standards...
• HES• SNAP• HOP• UPnP• ATM RBB• Jini/Java• HAVi• OSGi• IRDA• VESA• WLIF• SOAP
• X-10™• CEBus©• Lonworks™• Smarthouse• Firewire• CAL/HPnP• Home RF• Bluetooth• SWAP• WLIF• Home PNA• Home API
1985 2007
X-10™CEBus©LonWorks™Smarthouse™
“DigitalConvergence”
HomePlug
Zigbee
UWB
AHAM CHA
Ethernet
IPvX
WSDL
UDDI
XML
EIB
Konnex
BACnet
HomeGate
11© 2005 Electric Power Research Institute, Inc. All rights reserved.
Examples of Intelligrid Architecture Recommendations
Apply ASHRAE
BACnet™ for Building
Automation
Apply ANSI C12/COSEMfor Revenue
Metering
Apply IEC 61850 for Real-Time Controls
Apply IEC 61970 and 61968 (CIM,
GID) for Enterprise Data
Sharing
R&D:Harmonize IEC 61850 and 61970Standards
Develop and implement consistent systems management and security policies
12© 2005 Electric Power Research Institute, Inc. All rights reserved.
A Standards Development Model
Standards Developed by Formal Standards Development Organizations (SDO’s)
Interoperability Agreements
from Consortia
End-Users Desired Interoperability (Plug and Work)
Universe of networking and distributed computing options
IEEE SCC-31, ANSI C12.X, IEC TC 13
AEIC Metering, Open AMI, Others
13© 2005 Electric Power Research Institute, Inc. All rights reserved.
Example 1: EPRI P 137.018 Project: Enable integration between Advanced Automation and Information Technology Environments
OMSCIS
AM/FM/GIS
DistributionAutomation
Message Broker “Integration Bus”
Event History WorkManagement
EMS
Logical Device Servers
LN: XCBR
LN: CSWI
Substation IED Servers
kV = 11.8kV = 11.8kV = 11.8 LN: XCBR
LN: CSWI
UCA/IEC 61850
Real-Time Environment
Gateway/Security
SubstationAutomation
Gateway/Security
Common Information Model (CIM) Application Integration Environment
14© 2005 Electric Power Research Institute, Inc. All rights reserved.
Energy Service Client
C12.22 Comm Module
C12.22 C&I
Meter
61850 to BacNet
Gateway
CustomerEnergy Mgmt S t
10 Base T TCP/IP/
ACSE/MMS(61850)
Logic level C12.22
End Device / COMM Module
RS485 BACnet w/
StructuedView object
Example Project (2002) “Gateway”Implementation: Integrating Major Metering, Utility
and Building Automation
AEIC Meter and Service Committee
15© 2005 Electric Power Research Institute, Inc. All rights reserved.
Three Necessary Ingredients for Successful Interoperable Systems Development
Three Legged Stool: For Interoperable Products
2) Involved User Group: Interoperability Agreements, Labeling, Testing, Marketing
UCA International, BACnet Mfgs. Assoc. Assoc. of Edison Illuminating Cos3) Reference implementations
and Designs: Developer Tools, Standards Implementations and test implementations
AMRTools, openAMI, …
1) Open standards: Protocols, test schemas, object models
IEC TC57, ANSI C12, ASHRAE SPC135, Other
16© 2005 Electric Power Research Institute, Inc. All rights reserved.
Examples of Intelligrid Architecture Recommendations
Apply ASHRAE
BACnet™ for Building
Automation
Apply ANSI C12/COSEMfor Revenue
Metering
Apply IEC 61850 for Real-Time Controls
Apply IEC 61970 and 61968 (CIM,
GID) for Enterprise Data
Sharing
R&D:Harmonize IEC 61850 and 61970Standards
Develop and implement consistent systems management and security policies
17© 2005 Electric Power Research Institute, Inc. All rights reserved.
IEEE1549
IEEE1471
Other
IEEE SCC 36
IEC TC 13ASHRAESSPC 135
ISO TC 184
IECTC 57
ANSIC12
ISO 10746
Maturing
Partial
Missing
Industry-Level Architecture Seeks to Integrate Standards
Integrationbetween Standards
Common Languagefor Communications between different systems
Framework for Management and SecurityPolicy Implementation
EIA 600
Architecture Development and
Systems Engineering Methods
“Glue”
Architecture
18© 2005 Electric Power Research Institute, Inc. All rights reserved.
Several Disciplines Need to Come Together
?
19© 2005 Electric Power Research Institute, Inc. All rights reserved.
Work is needed in key areas:
• System Operation and Protection Applications: Necessary to operate closer to limits, need to integrate data and applications across Gen,T&D, Consumer Comm
• Need to integrate Dynamic Consumer Energy and Demand Response
• Need for a robust application level common language that can cut across the major technical domains
• Need advanced Systems Engineering Methods that are capable of massively scaled and robust systems
• Need a Roadmap• Need to work Cooperatively