美国首批公布的智能网标准体系

gwjhbs · 发表于 2009-5-20 11:05:16

马上加入，结交更多好友，共享更多资料，让你轻松玩转电力研学社区！

您需要登录才可以下载或查看，没有账号？立即加入

×

美国首批公布的智能网标准体系

huijf02 · 发表于 2009-5-20 11:20:58

这么快标准就出来了？

ooqixu · 发表于 2009-5-20 11:20:59

1# gwjhbs

Gap Analysis of Power System “Smart Grid” Information Standards

1. Overview of Information Standards Bodies
1.1 Standards: Meeting the Challenges of Interoperability
1.1.1 Purpose of Standards
The purpose of cyber interoperability standards is to formalize the nouns, verbs, grammar, and societal rules for exchanging information, or as stated in cyber-speak, to formalize the object model semantics, the messaging syntax, the communication profiles, and the network/security management.
1.1.2 Types of Standards
Standards come in many different flavors, with many different types of standards. Most standards focus on only specific levels (although there are not usually “clean” distinctions between levels). Broadly, there are four levels of cyber standards:
• Media-related standards specific to fiber optics, microwave, WiFi, CATV, wires, telephones and cellphones
• Transport-related standards such as Internet standards including Ethernet, IP, TCP, HTTP, OPC
• Application-related standards such as HTML, XML, IEC 61850, Common Information Model (CIM)
• Security-related standards such as AES 256, PKI, secret keys, and Certificates
Often de facto standards are developed either by a dominant corporation (e.g. IBM’s ASCII and Microsoft’s OLE) or by a consortium of interested vendors (e.g. Zigbee Alliance). These de facto standards have not been “blessed” by a standards organization, but can nonetheless be widely used. In many cases, successful de facto standards eventually become formalized into real standards. In other cases, recommended practices can help narrow the choices.
Another aspect of standards is that they cannot be too rigid, but must still leave flexibility for systems to add new functionality or select certain options. Many standards come with both mandatory requirements and optional selections, as well as with “extension rules” for expanding the standards in a consistent manner for new functions. This is often viewed as the 80/20 rule, namely that standards should address about 80% of the interoperability needs, but typically at least 20% must remain for vendor-specific requirements or utility-specific requirements, as well as the flexibility to meet unforeseen requirements in the future.
Most standards are developed by vendors and consultants, with some, but very often not enough, utility involvement.
1.2 IEC TC57 Standards
The interrelationship between IEC TC57 information modeling standards is illustrated in Figure 1.
IEC 61850 is used for field communications. This illustration shows as horizontal layers the three components to an information exchange model for retrieving data from the field, namely, the abstract information models, the service models, and the communication protocol profiles that the abstract information models are mapped into. The different IEC 61850 information models are shown as vertical bars:
• Substation automation (IEC 61850-7-4)
• Large hydro plants (IEC 61850-7-410)
• Distributed energy resources (DER) (IEC 61850-7-420)
• Distribution automation (under development)
• PHEV and additional DER (under development)
IEC 61970 and IEC 61968, the Common Information Model (CIM), is used for enterprise-level communications. The CIM is an abstract model of utility-specific data. Service models such as the GID are defined, but no mapping between the CIM to these service models is specified. The different IEC Common Information Models (CIM) are shown horizontally:
• Transmission CIM (IEC 61970)
• Distribution CIM (IEC 61968)
IEC 62351 security standards cut across the other IEC standards, and consist of:
• Protocol-specific security standards for IEC 61850, IEC 60870-5, IEC 60870-6 (ICCP), and by extension, DNP3 (IEC 62351, Parts 3-6)
• Network and System Management (NSM) (IEC 62351-7)
• Role-Based Access Control (RBAC) (IEC 62351-8)

Figure 1: IEC TC57 Information Standards

1.3 Institute of Electrical and Electronic Engineers (IEEE)
The IEEE has a similar methodology to that of the IEC for developing draft and, ultimately, final standards, only IEEE voting is performed by members of the working groups, not by National Committees. Membership in working groups is much more flexible, typically requiring only that members show up for the meetings and actively participate in the work.
In addition, the IEEE working groups develop many other types of documents, including Recommended Practices, Technical Reports, Conference Papers, and other non-standards-oriented documents.
The IEEE has developed many standards, but those of greatest interest for communications and interoperability are:
• IEEE 802.3 (Ethernet)
• IEEE 802.11 (WiFi)
• IEEE 802.15.1 (Bluetooth)
• IEEE 802.15.4 (Zigbee)
• IEEE 802.16 (WiMax)
1.4 Internet Engineering Task Force (IETF)
The IETF is responsible for Internet standards, many of which are now widely implemented in private Intranets as well. A Request for Comment (RFC) document is the mechanism used by the IETF to develop, send out for comment, and finalize standards. Usually, RFC specifications must be implemented by more than one vendor before they can be fully accepted as standards.
Some of the key IETF RFCs are:
• RFC 791: Internet Protocol (IP)
• RFC 793: Transport Control Protocol (TCP)
• RFC 1945: HyperText Transfer Protocol (HTTP)
• RFC 2571: Simple Network Management Protocol (SNMP)
• RFC 3820:  Internet X.509 Public Key Infrastructure (PKI) for security
1.5 American National Standards Institute (ANSI)
Like the other standards organizations, ANSI has working groups which work on specific standards, and update them as necessary. The most relevant ANSI standards for interoperability of AMI systems include:
• ANSI C12.19 (metering “tables” internal to the meter). This document is currently under revision
• ANSI C12.22 (communications for metering tables)
1.6 National Institute of Standards and Technology (NIST)
NIST has developed Special Publications in the 800 series which provide documents of general interest to the computer security community. These are more guidelines than standards, but are very important for moving toward secure interoperability. Two documents of particular interest for the Smart Grid are:
• NIST SP-800-53: Recommended Security Controls for Federal Information Systems
• NIST SP-800-82: Guide to Industrial Control Systems (ICS) Security
1.7 North American Electric Reliability Corporation (NERC)
NERC has recently issues security standards for the bulk power system. Although these security standards are explicitly for the bulk power system, it is clear that many of the requirements also apply to distribution and AMI systems, and may eventually become standards for these systems as well. The NERC CIP 002-009 Security Standards cover:
• (2) Critical Cyber Asset Identification, (3) Security Management Controls, (4) Personnel and Training, (5) Electronic Security Perimeter(s), (6) Physical Security of Critical Cyber Assets, (7) Systems Security Management, (8) Incident Reporting and Response Planning, and (9) Recovery Plans for Critical Cyber Assets
1.8 World Wide Web Consortium (W3C)
The W3C develops interoperable technologies (specifications, guidelines, software, and tools) for the world wide web, including:
• HTML for web page design
• XML for structuring documents and other object models
• Web services for application-to-application communications, such as SOAP for transmitting data

2. Gaps in Infrastructure Information Standards
2.1 Distribution and DER Field Equipment Information Standards
Requirement for Standard Justification for Standard
1. Need to extend IEC 61850 to distribution automation. This is under development but does not have the impetus to move forward quickly. IEC 61850 is an information model, so it is widely seen as the best approach to communications with field equipment. Given that premise, the information model needs to be expanded into additional areas, including distribution automation.
Justification for distribution automation includes increased reliability, increased efficiency, increased safety, decreased on-going costs (once it is implemented), and increased environmental benefits.
2. Need to extend IEC 61850 for more Distributed Energy Resource (DER) equipment.  Currently IEC 61850-7-420 for DER covers wind (actually IEC 62400-25), photovoltaic systems, fuel cells, diesel generators, batteries, and combined heat and power (CHP). Needs extension to PHEV, additional storage devices, microturbines, gas turbines, etc. IEC 61850-7-420 for DER has just been standardized and is being implemented (primarily in Europe), but needs to be expanded to other DER so that the full suite of DER devices can be covered by one information model-based protocol.
3. Need to develop an IEC 61850-lite, in which the information models can be mapped to a protocol with less overhead than the current MMS-based mapping. Distribution automation and DER devices may have only narrowband communications channels or limited data exchanges due to data costs if telecommunication providers are providing the communication channels. In addition, some inexpensive devices (e.g. sensors, collectors, or “software agents”) may not want or need to implement the full IEC 61850 capabilities, in order to minimize compute constraints or development costs.
4. Need to ensure AMI communications systems use open standards capable of interfacing to DER and distribution automation equipment.  ANSI C12.22 is being revised, Europe uses DLMS/COSEM, and AMI vendors are frantically developing their systems over a wide range of media, from PLC, to BPL, to Zigbee meshed radios, to UtiliNet radios, to GPRS, etc, etc. Since AMI systems are going to become widespread, they will inevitably want to be used for more than meter reading or other purely metering functions. They could be used for monitoring DER at the customer site, for DA monitoring and possibly control, for access by third parties to gateways into the customer HAN, etc. Right now, AMI vendors are using proprietary or semi-proprietary communication protocols “just to get the AMI systems implemented”. The AMI systems should be able to handle, at a minimum, the IEC 61850 object models mapped to an “appropriate” protocol (possibly IEC 61850-lite when it is developed).

2.2 Customer Site – AMI, Gateways, and HAN Information Standards
Requirement for Standard Justification for Standard
1. Review possible constraints in the current finalizing of ANSI C12.22 for communications with the meter. ANSI C12.22 is being revised, but there are concerns that the results may not meet the requirement to base standards on broader information models – the results may be too metering-only focused (i.e. too focused on ANSI C12.19 metering). Since AMI systems are going to become widespread, they will inevitably want to be used for more than meter reading or other purely metering functions. (see above)
2. Move toward AMI/HAN standards, based on the OpenHAN specification. The OpenHAN specification (not a standard) was recently developed, but currently there is no actual standard for this interface between the AMI system and the HAN The AMI systems have their own (often proprietary or based on ANSI C12.22) communication standards to the meter. Within the HAN, HomePlug and Zigbee have standards, but are now working together to develop Zigbee Smart Energy Profile
3. Work with Zigbee Smart Energy Profile working group to ensure the information model is complete or can utilize the IEC 61850 information model and/or the CIM information model. Zigbee Smart Energy Profile for the HAN environment is being developed, but may not yet understand the breadth of requirements that it may ultimately have to handle. This means that the requirements across the AMI/HAN gateway need to be understood, described, and converted into information models.
2.3 Transmission Field Equipment Information Standards
Requirement for Standard Justification for Standard
1. Complete Wide-Area Phasor Measurement monitoring standards. Work is on-going in this area but is not complete. Wide area phasor measurements can provide early warning of potential problems as well as input to make rapid (~ 4 ms) control actions to mitigate emergency conditions.
2. Extend IEC 61850 between substations. Some protective relaying and certain other functions require communications between substations, for which 61850 should be used. IEC 61850 is designed to be used within substations. However, functions such as protective relaying need to communicate between substations. The same protocol should be used for this function.
3. Extend IEC 61850 from the substation to the control center. Since the data in the substation uses the 61850 information model, this data should be reported to the control center using the same information model. IEC 61850 models all the equipment and functions in the substation. If those models could be brought back to the control center, then this same powerful information model would be used for SCADA and other applications, thus minimizing translations and expensive and data maintenance activities that sometimes lead to insecure and/or unsafe situations.
2.4 Utility Enterprise Information Standards
Requirement for Standard Justification for Standard
1. Develop Interoperability Standards for the IEC 61970 Common Information Model (CIM). The CIM for transmission (IEC 61970) does not specify formats or messaging methods for exchanging CIM information, thereby requiring each implementation to develop their own formats and messaging requirements. The IEC 61970 CIM for transmission is strictly an abstract model with no standardized mechanism for mapping the information model to communication formats and messages, thus making different implementation not interoperable. If CIM format and messaging standards were developed, then CIM implementations could be interoperable.
2. Revise and update parts of IEC 61968 Common Information Model (CIM) for distribution. CIM for distribution has recently developed some messaging schemes for exchanging CIM information interoperably. However, earlier parts of IEC 61968 do not yet have interoperable messaging schemes. The IEC 61968 CIM for distribution is currently not usable except for the very latest part (Part 9), since the messaging schemes and the CIM model were not well enough defined to allow vendors to implement them. However, if these older parts are revised, then interoperability of the messages may be achieved. These revisions are in the IEC TC57 WG14 roadmap, but will need significant effort to achieve.
3. Expand IEC 61968 CIM for DER and PHEV. Although IEC 61850-7-420 for DER has been completed (with more DER models still pending, including PHEV), no CIM models for any DER or PHEV have yet been developed. IEC 61850 is designed for field communications, while CIM is for enterprise communications. Therefore, CIM models need to carry the 61850 models of DER into the enterprise.
4. Expand MultiSpeak. MultiSpeak, developed by NRECA and very successfully implemented for many smaller utilities, is being expanded as version 4, with more updates to come. MultiSpeak meets the requirements of the smaller utilities very effectively, but needs to be expanded to meet additional requirements for more functionality, more flexibility, more use of information modeling techniques, and more compatibility with IEC 61968.

3. Cross-Domain Standards
3.1 Cyber Security Standards
Requirement for Standard Justification for Standard
1. Extend NERC CIP 002-009 to Distribution and AMI. Although explicitly for transmission, and using an asset-based approach which may not always be applicable, the NERC CIP still has very powerful requirements. In particular, these requirements can be used by utilities to develop the security policies that are critical for true security.
2. Complete the IEC 62351-8 Role-Based Access Control (RBAC). RBAC is a general security concept for managing access to information and assets. The RBAC model for utilities is being standardized in the IEC. RBAC should be used for managing access to all information and assets, but needs both standards and guidelines for clarity and interoperability particularly across different security domains.
3. Complete the IEC 62351-7 Network and System Management (NSM). NSM monitors not only communication networks, but also systems, applications, and databases. The main purpose of NSM is to detect anomalies which could be intrusions, mistakes, or failures, but which could adversely affect the operation of the grid. In the August 2003 blackout, although the initial cause was equipment failure, the real cause was lack of information flowing to where it was supposed to flow due primarily to mistakes.
4. Develop Key Management Strategies. Key management of the millions of devices and meters is becoming a critical issue, since truck rolls are too expensive for manual key entry, and some communication infrastructures may not be adequate for handling key updates. Cyber security is only as good as the secrecy of the cyber keys used not only for encryption but also just for authentication. Key management over narrowband communication channels to inexpensive end devices needs resolution and standardization.
5. Develop more detailed security requirements for AMI systems. AMI-SEC has developed high level security requirements for AMI systems, but these are not detailed enough to provide explicit security requirements for different functions using the AMI systems. AMI systems are becoming an enormous communications infrastructure that reach into all customer sites. Ensuring that these AMI systems are truly secure enough for the different functions that can be performed across them, is critical. That assurance can only come from more detailed security requirements linked to the different functions.

3.2 Standards Interoperability and Conformance Testing
Requirement for Standard Justification for Standard
1. Perform interoperability testing for IEC 61968-9. Interoperability testing is planned for this part in late 2009. Interoperability testing, along with conformance testing, is the best method for confirming that a standard is performing correctly and actually doing what it is supposed to do. These tests can also feed back to the standards group on issues where the standards are unclear, missing, or incorrect.
2. Perform conformance and interoperability testing of IEC 62351 security standards. Testing is the most effective way to ensure that these security standards actually provide the level of security expected. Any issues, such as security holes or inconsistencies, can be fed back to the standards group.
4. Smart Grid Applications – Guidelines and Metrics
4.1 Smart Grid Definition
The Energy Independence and Security Act of December 2007 defines the Smart Grid as follows:
“It is the policy of the United States to support the modernization of the Nation's electricity transmission and distribution system to maintain a reliable and secure electricity infrastructure that can meet future demand growth and to achieve each of the following, which together characterize a Smart Grid:
(1) Increased use of digital information and controls technology to improve reliability, security, and efficiency of the electric grid.
(2) Dynamic optimization of grid operations and resources, with full cyber-security.
(3) Deployment and integration of distributed resources and generation, including renewable resources.
(4) Development and incorporation of demand response, demand-side resources, and energy-efficiency resources.
(5) Deployment of `smart' technologies (real-time, automated, interactive technologies that optimize the physical operation of appliances and consumer devices) for metering, communications concerning grid operations and status, and distribution automation.
(6) Integration of `smart' appliances and consumer devices.
(7) Deployment and integration of advanced electricity storage and peak-shaving technologies, including plug-in electric and hybrid electric vehicles, and thermal-storage air conditioning.
(8) Provision to consumers of timely information and control options.
(9) Development of standards for communication and interoperability of appliances and equipment connected to the electric grid, including the infrastructure serving the grid.
(10) Identification and lowering of unreasonable or unnecessary barriers to adoption of smart grid technologies, practices, and services.”

4.2 Smart Grid Applications
Applications actually drive the requirements for the infrastructure information standards. However, they themselves should not be standardized, since standards should apply across interfaces, not within software applications. However, many guidelines could be developed on what functions will benefit the Smart Grid by:
• Improving power system reliability
• Improving power system efficiency
• Improving cyber security and safety
• Decreasing costs within a defined timeframe
• Minimizing the impact on the environment
Metrics should be developed to determine the “smart gridedness” of different functions which claim to further these goals.

p0o9i8u7 · 发表于 2009-5-20 14:47:37

感谢斑竹，非常好的资料

ghostspider · 发表于 2009-5-20 15:28:28

这英文看的我是两眼发花啊，谢谢分享啊

tornader · 发表于 2009-5-20 15:54:53

哈哈，谢谢你。

pchen · 发表于 2009-5-20 18:10:33

标准的中文翻译

gwjhbs · 发表于 2009-5-21 21:55:50

最完整的标准体系规划。
比较透彻

gwjhbs · 发表于 2009-5-21 21:58:58

在传个资料

gwjhbs · 发表于 2009-5-21 21:59:44

我的资料下载怎么就是不增加那，晕的我都急死了

账号		自动登录	找回密码
密码			立即加入

美国首批公布的智能网标准体系

马上加入，结交更多好友，共享更多资料，让你轻松玩转电力研学社区！

评分

相关帖子

评分