IEEE

This standard extends IEEE 1872-2015 Standard for Ontologies for Robotics and Automation to represent additional domain-specific concepts, definitions, and axioms commonly used in Autonomous Robotics (AuR). This standard is general and can be used in many ways - for example, to specify the domain knowledge needed to unambiguously describe the design patterns of AuR systems, to represent AuR system architectures in a unified way, or as a guideline to build autonomous systems consisting of robots operating in various environments.

This trial-use standard defines a standardized method for the design of quantum algorithms. The defined methods apply to any type of algorithm that can be assimilated into quantum primitives and/or quantum applications. The design of the algorithms is done preceding quantum programming.

The standard covers quantum computing performance metrics for standardizing performance benchmarking of quantum computing hardware and software. These metrics and performance tests include everything necessary to benchmark quantum computers (stand alone and by/for comparison) and to benchmark quantum computers against classical computers using a methodology that accounts for factors such as dedicated solvers.

This standard addresses quantum technologies specific terminology and establishes definitions necessary to facilitate clarity of understanding to enable compatibility and interoperability.

This standard defines the Software-Defined Quantum Communication (SDQC) protocol that enables configuration of quantum endpoints in a communication network in order to dynamically create, modify, or remove quantum protocols or applications. This protocol resides at the application layer and communicates over Transmission Control Protocol/Internet Protocol. The protocol design facilitates future integration with Software-Defined Networking and Open Networking Foundation OpenFlow. The standard defines a set of quantum device configuration commands that control the transmission, reception, and operation of quantum states. These device commands contain parameters that describe quantum state preparation, measurement, and readout.

This guide provides the technical background, rationale and guidance to support the application of the substantially revised IEEE 1547, Standard for Interconnection and interoperability of Distributed Energy Resources (DER) with Electric Power Systems (EPS) and Associated Interfaces. The document will describe how the requirements and default settings specified in 1547 have been carefully chosen to balance distribution and bulk system needs for increasing penetration of DER. It further expands IEEE 1547 by addressing certain DER integration issues that are not fully addressed by the base standard, e.g. reclosing coordination and limitation of over-voltage in the Area EPS. The guide will address (1) the concept of the newly-introduced performance categories and their assignment to specific DER by an Authority Governing Interconnection Requirements (AGIR); (2) the new requirements for voltage and reactive power control, frequency control, response to abnormal conditions including ride-through; (3) the flexibility provided by the newly-introduced ranges of adjustability for control settings as well as for voltage and frequency trip settings to fully exploit the revised IEEE 1547's potential and to account for specific system characteristics; (4) the interoperability and communication interface requirements; and (5) the test and verification practices, including design and as-built installation evaluations for utility-scale DER, that have not been included in the previous version of the standard. Presented in the document are technical descriptions and schematics, applications guidance and interconnection examples to enhance the use of IEEE 1547.

Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.

This guide describes recommended practices for the physical security of electric power substations. It is designed to address a number of threats, including unauthorized access to substation facilities, theft of material, and vandalism. It describes options for positive access control, monitoring of facilities, and delay/deter features which could be employed to mitigate these threats. This guide also establishes options for different levels of physical security for electric power substations. The guide does not establish recommendations based on voltage levels, size or any depiction of criticality of the substation. The user will make these decisions based on threat assessment and criticality assignment by the substation owner. Overt attacks against the substation for the purpose of destroying its capability to operate, such as explosives, projectiles, vehicles, etc. are beyond the scope of this guide.

This standard defines a method for data sharing, interoperability, and security of messages over a network, where sensors, actuators and other devices can interoperate, regardless of underlying communication technology. The backend of such a globally scalable, secure and interoperable network would be based on the eXtensible Messaging and Presence Protocol (XMPP), and rely on infrastructural components, or bridges, with standardized interfaces that provide real-time conversion of other IoT and M2M protocols, such as those based on CoAP (Constrained Application Protocol), HTTP (Hypertext Transfer Protocol), MQTT (Message Queuing Telemetry Transport Protocol), AMQP (Advanced Message Queuing Protocol), etc., and other interoperability interfaces, such as those provided by the IEEE 1451 Smart Transducer Interface, oneM2M, OMA LWM2M (Open Mobile Alliance Lightweight M2M), OIC (Open Internet Connection), UPnP (Universal Plug and Play), IPSO (Internet Protocol for Smart Objects) Alliance, etc. The standard utilizes the advanced capabilities of the XMPP protocol, such as providing globally authenticated identities, authorization, presence, life cycle management, interoperable communication, IoT discovery and provisioning. Descriptive meta-data about devices and operations will provide sufficient information for infrastructural components, services and end-users to dynamically adapt to a changing environment. Key components and needs of a successful Smart City infrastructure will be identified and addressed. This standard does not develop Application Programming Interfaces (APIs) for existing IoT or legacy protocols.

The wireless access in vehicular environments (WAVE) architecture and services necessary for WAVE devices to communicate in a mobile vehicular environment are described in this guide. It is meant to be used in conjunction with the family of IEEE 1609 standards as of its publication date. These include IEEE Std 1609.2(TM), IEEE Standard Security Services for Applications and Management Messages; IEEE Std 1609.3(TM), Networking Services; IEEE Std 1609.4(TM), Multi- Channel Operation; IEEE Std 1609.11(TM), Over-the-Air Electronic Payment Data Exchange Protocol for Intelligent Transportation Systems (ITS); IEEE Std 1609.12(TM), Identifiers; and IEEE Std 802.11(TM) in operation outside the context of a basic service set.

Wireless Access in Vehicular Environments (WAVE) is specified in the IEEE 1609 family of standards, within which certain identifiers are used. The use of these identifiers is described, and identifier values that have been allocated for use by WAVE systems are indicated.

The DNP3 protocol structure, functions, and interoperable application options (subset levels) are specified. The simplest application level is intended for low-cost distribution feeder devices, and the most complex for full-featured systems. The appropriate level is selected to suit the functionality required in each device. The protocol is suitable for operation on a variety of communication media consistent with the makeup of most electric power communication systems.