This part of IEC 61970 belongs to the IEC 61970-450 to IEC 61970-499 series that, taken as a
whole, defines at an abstract level the content and exchange mechanisms used for data
transmitted between power system analyses applications, control centres and/or control centre
components.
The purpose of this document is to rigorously define the subset of classes, class attributes, and
roles from the CIM necessary to describe the result of state estimation, power flow and other
similar applications that produce a steady-state solution of a power network, under a set of use
cases which are included informatively in this document.
This document is intended for two distinct audiences, data producers and data recipients, and
can be read from those two perspectives. From the standpoint of model export software used
by a data producer, the document defines how a producer may describe an instance of a
network case in order to make it available to some other program. From the standpoint of a
consumer, the document defines what that importing software must be able to interpret in order
to consume power flow cases.
There are many different use cases for which use of this document is expected and they differ
in the way that the document will be applied in each case. Implementers are expected to
consider what use cases they wish to cover in order to know the extent of different options they
must cover. As an example, the profiles defined in this document will be used in some cases to
exchange starting conditions rather than solved conditions, so if this is an important use case,
it means that a consumer application needs to be able to handle an unsolved state as well as
one which has met some solution criteria

  • Standard
    110 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO/IEC 10192-4-1:2022 specifies an architecture for home cluster systems and for interworking among them. It specifies a cluster-to-cluster interface to enable interworking among home cluster systems and interoperability among the applications supported by these cluster systems as well as a common user interface to these cluster-system applications. This common user interface provides input and output methods for user information exchange to access, monitor and control applications running on home cluster systems.

  • Standard
    20 pages
    English language
    sale 15% off

ISO/IEC 14165-432:2022 is one of the Fibre Channel family of standards. This standard describes the protocols used to implement security in a Fibre Channel fabric. This standard includes the definition of protocols to authenticate Fibre Channel entities, protocols to set up session keys, protocols to negotiate the parameters required to ensure frame-by-frame integrity and confidentiality, and protocols to establish and distribute policies across a Fibre Channel fabric.

  • Standard
    309 pages
    English language
    sale 15% off

This part of IEC 60958 specifies the consumer application of the interface for the inter connection of digital audio equipment defined in IEC 60958-1.
NOTE When used in a consumer digital processing environment, the interface is primarily intended to carry stereophonic programmes, with a resolution of up to 20 bits per sample, an extension to 24 bits per sample being possible.

  • Standard
    70 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    69 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of IEC 60958 describes a serial, uni-directional, self-clocking interface for the
interconnection of digital audio equipment for consumer and professional applications.
It provides the basic structure of the interface. Separate documents define items specific to
particular applications.
The interface is primarily intended to carry monophonic or stereophonic programmes, encoded
using linear PCM and with a resolution of up to 24 bits per sample.
When used for other purposes, the interface is able to carry audio data coded other than as
linear PCM coded audio samples. Provision is also made to allow the interface to carry data
related to computer software, multimedia technologies, or signals coded using non-linear PCM.
The format specification for these applications is not part of this document.
The interface is intended for operation at audio sampling frequencies of 32 kHz and above.
Auxiliary information is transmitted along with the programme.

  • Standard
    33 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of IEC 61970-600 defines the profiles included in the Common Grid Model Exchange
Standard (CGMES) that are based on IEC 61970-450-series and IEC 61968-13 profiles. This
document refers to the IEC 61970-450-series and IEC 61968-13 profiles only in cases where
they are identical. If the referenced profile is not yet published, this document includes the
profile definition and related constraints’ definitions. In the case where a CGMES profile makes
restriction on the referenced profile, the restriction is defined in this document.
The equipment boundary profile (EQBD) is the only profile that is not part of IEC 61970-450-
series and IEC 61968-13 profiles. This profile is deprecated as modifications have been made
to align between EQBP and the equipment profile (EQ). Although the updated EQBD is
addressing the requirement that boundary also can be located inside a substation, which will
be the case for many Distribution System Operators (DSOs), additional information would need
to be exchanged. For instance, system integrity protection schemes, that can be shared by
multiple utility would require another way of boundary handling. In this document EQBD is
included in CGMES only to create better backwards compatibility with previous version of the
CGMES.
The machine-readable documentation that supports model driven development of the profiles
defined in this part are generated as Resource Description Framework Schema (RDFS)
according to IEC 61970-501:2006 (with some extension) and IEC 61970-501:ED2 when
published.

  • Standard
    879 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document is one of the IEC 61970-450 to 499 series that, taken as a whole, defines at an abstract level the content and exchange mechanisms used for data transmitted between control centres and/or control centre components, such as power systems applications.
The purpose of this document is to define the subset of classes, class attributes, and roles from the CIM necessary to execute state estimation and power flow applications. The North American Electric Reliability Council (NERC) Data Exchange Working Group (DEWG) Common Power System Modelling group (CPSM) produced the original data requirements, which are shown in Annex E. These requirements are based on prior industry practices for exchanging power system model data for use primarily in planning studies. However, the list of required data has been extended starting with the first edition of this standard to facilitate a model exchange that includes parameters common to breaker-oriented applications. Where necessary this document establishes conventions, shown in Clause 6, with which an XML data file must comply in order to be considered valid for exchange of models.
This document is intended for two distinct audiences, data producers and data recipients, and may be read from two perspectives.
From the standpoint of model export software used by a data producer, the document describes a minimum subset of CIM classes, attributes, and associations which must be present in an XML formatted data file for model exchange. This standard does not dictate how the network is modelled, however. It only dictates what classes, attributes, and associations are to be used to describe the source model as it exists.

  • Standard
    277 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document is based on requirements from ETSI TS 102 656 [2].
The present document contains handover requirements and a handover specification for the data that is identified in
national legislations on Retained Data.
The present document considers both the requesting of retained data and the delivery of the results.
The present document defines an electronic interface. An informative annex describes how this interface may be
adapted for manual techniques. Apart from in annex I, the present document does not consider manual techniques.

  • Technical specification
    143 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of IEC 60958 enhances the consumer application of the interface for the
interconnection of digital audio equipment defined in IEC 60958-1 and IEC 60958-3, introducing:
– multichannel;
– multi-stream;
– high-resolution;
– multimedia extension;
– related applications.
NOTE IEC 60958-3 specifies a consumer application to carry stereophonic programmes with a resolution of up to
24 bits per sample. This part of IEC 60958 enhances the application, allowing programmes with up to 64 channels,
64 bits per sample, and two simultaneous streams.

  • Standard
    23 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    20 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This specification is intended as a supplement to the existing USB 2.0, USB 3.2, USB4™ and USB Power
Delivery specifications. It addresses only the elements required to implement and support the USB
Type-C receptacles, plugs and cables

  • Standard
    367 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This specification is intended as an extension to the existing [USB 2.0], [USB 3.2], [USB Type-C 2.0] and
[USBBC 1.2] specifications. It addresses only the elements required to implement USB Power Delivery. It
is targeted at power supply vendors, manufacturers of [USB 2.0], [USB 3.2], [USB Type-C 2.0] and [USBBC
1.2] Platforms, Devices and cable assemblies.
Normative information is provided to allow interoperability of components designed to this specification.
Informative information, when provided, illustrates possible design implementation.

  • Standard
    644 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    683 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of IEC 63245 specifies requirements for spatial wireless power transfer based on
multiple magnetic resonances (SWPT-MMR), which is a non-radiative wireless power transfer
(WPT). This document contains two categories of requirements: general requirements and
functional requirements. The general requirements cover charging procedures and charging
zones. The functional requirements cover each component of a SWPT-MMR system, such as
transmitter coils.

  • Standard
    18 pages
    English language
    sale 10% off
    e-Library read for
    1 day

Specifies mid-span power insertion into generic cabling as specified in ISO/IEC 11801, the location and allocation requirements in case of the replacement of a generic cabling component or components.

  • Technical report
    1 page
    English language
    sale 15% off

This document provides detailed mapping information between Z-Wave and OCF defined Resources.

  • Standard
    35 pages
    English language
    sale 15% off
  • Draft
    35 pages
    English language
    sale 15% off

This document defines mechanisms supported by an OCF Onboarding Tool (OBT). This document contains security normative content for the OBT and may contain informative content related to the OCF base or OCF Security Specification other OCF documents.

  • Standard
    11 pages
    English language
    sale 15% off
  • Draft
    11 pages
    English language
    sale 15% off

This document defines functional extensions to the capabilities defined in ISO/IECÂ 30118-1 to meet the requirements of the OCF Cloud. This document specifies new Resource Types to enable the functionality and any extensions to the existing capabilities defined in ISO/IECÂ 30118-1.

  • Standard
    37 pages
    English language
    sale 15% off
  • Draft
    37 pages
    English language
    sale 15% off

This document provides detailed mapping information between Zigbee defined Clusters and OCF defined Resources.

  • Standard
    61 pages
    English language
    sale 15% off
  • Draft
    61 pages
    English language
    sale 15% off

This document provides detailed mapping information between UPlus (U+) and OCF defined Resources.

  • Standard
    16 pages
    English language
    sale 15% off
  • Draft
    16 pages
    English language
    sale 15% off

This document specifies a framework for translation between OCF Devices and other ecosystems, and specifies the behaviour of a Bridging Function that exposes servers in non-OCF ecosystem to OCF Clients and/or exposes OCF Servers to clients in non-OCF ecosystem. Translation per specific Device is left to other documents (deep translation). This document provides generic requirements that apply unless overridden by a more specific document.

  • Standard
    17 pages
    English language
    sale 15% off
  • Draft
    17 pages
    English language
    sale 15% off

The OCF Core specifications are divided into a set of documents: Core specification (this document): The Core specification document specifies the Framework, i.e., the OCF core architecture, interfaces, protocols and services to enable OCF profiles implementation for Internet of Things (IoT) usages and ecosystems. This document is mandatory for all Devices to implement. Core optional specification: The Core optional specification document specifies the Framework, i.e., the OCF core architecture, interfaces, protocols and services to enable OCF profiles implementation for Internet of Things (IoT) usages and ecosystems that can optionally be implemented by any Device. Core extension specification(s): The Core extension specification(s) document(s) specifies optional OCF Core functionality that are significant in scope (e.g., Wi-Fi easy setup, Cloud).

  • Standard
    132 pages
    English language
    sale 15% off
  • Draft
    132 pages
    English language
    sale 15% off

This document provides detailed mapping information between EnOcean defined EEPs and OCF defined Devices and Resources.

  • Standard
    74 pages
    English language
    sale 15% off
  • Draft
    74 pages
    English language
    sale 15% off

The Device definitions use Resource definitions from ISO/IEC 30118-4. This document is built on top of ISO/IEC 30118-1. ISO/IEC 30118-1 specifies the core architecture, interfaces protocols and services to enable the implementation of profiles for IoT usages and ecosystems. ISO/IEC 30118-1 also defines the main architectural components of network connectivity, discovery, data transmission, device & service management and ID & security. The core architecture is scalable to support simple devices (constrained devices) and more capable devices (smart devices).

  • Standard
    60 pages
    English language
    sale 15% off
  • Draft
    60 pages
    English language
    sale 15% off

The OCF Core specifications are divided into a series of documents: Core specification: The Core specification document specifies the Framework, i.e., the OCF core architecture, interfaces, protocols and services to enable OCF profiles implementation for Internet of Things (IoT) usages and ecosystems. This document is mandatory for all Devices to implement. Core optional specification (this document): The Core optional specification document specifies the Framework, i.e., the OCF core architecture, interfaces, protocols and services to enable OCF profiles implementation for Internet of Things (IoT) usages and ecosystems that can optionally be implemented by any Device. Core extension specification(s): The Core extension specification(s) document(s) specifies optional OCF Core functionality that are significant in scope (e.g., Wi-Fi easy setup, Cloud).

  • Standard
    100 pages
    English language
    sale 15% off
  • Draft
    100 pages
    English language
    sale 15% off

This document specifies the Resources that have been defined by OCF that may be exposed by an OCF Device. Application profile device documents (for example those created for Smart Home or Healthcare) specify device types appropriate to the profile; such documents use Resource Type definitions from this document. This document is built on top of ISO/IEC 30118-1. ISO/IEC 30118-1 specifies the OCF Framework that enables the implementation of profiles for IoT usages and ecosystems. The OCF Core Framework is scalable to support simple devices (constrained device) and more capable devices (smart device).

  • Standard
    616 pages
    English language
    sale 15% off
  • Draft
    616 pages
    English language
    sale 15% off

The OCF Cloud specifications are divided into a series of documents: OCF Cloud security specification (this document): The cloud security specification document specifies the security recuirements and definitions for OCF devices and OCF clouds implementations. OCF Device to Cloud Specification: The OCF Device to Cloud Specification document defines functional extensions and capabilities to meet the requirements of the OCF Cloud. This document specifies new Resource Types to enable the functionality and any extensions required to connect an OCF device to an OCF cloud. OCF Cloud API for cloud services specification: The Cloud API for cloud services specification defines the OCF cloud API.

  • Standard
    27 pages
    English language
    sale 15% off
  • Draft
    27 pages
    English language
    sale 15% off

This document provides detailed mapping information to provide equivalency between oneM2M defined Module Classes and OCF defined Resources. A oneM2M Bridge is Asymmetric Client Bridge, therefore this document provides unidirectional mapping for Device Types (oneM2M Devices to OCF Devices), identifies equivalent OCF Resources for specific oneM2M Module Classes, and defines the detailed Property by Property mapping using OCF defined extensions to JSON schema to programmatically define the mappings.

  • Standard
    115 pages
    English language
    sale 15% off
  • Draft
    115 pages
    English language
    sale 15% off

This document provides detailed mapping information to provide equivalency between AllJoyn defined Interfaces and OCF defined Resources. This document provides mapping for Device Types (AllJoyn to/from OCF), identifies equivalent OCF Resources for both mandatory and optional AllJoyn interfaces and for each interface defines the detailed Property by Property mapping using OCF defined extensions to JSON schema to programmatically define the mappings.

  • Standard
    69 pages
    English language
    sale 15% off
  • Draft
    69 pages
    English language
    sale 15% off

This document provides detailed mapping information between BLE (Bluetooth Low Energy) and OCF defined Resources.

  • Standard
    48 pages
    English language
    sale 15% off
  • Draft
    48 pages
    English language
    sale 15% off

This document defines functional extensions to the capabilities defined in ISO/IEC 30118-1 to meet the requirements of Wi-Fi Easy Setup. It specifies new Resource Types to enable the functionality and any extensions to the existing capabilities defined in ISO/IEC 30118-1.

  • Standard
    35 pages
    English language
    sale 15% off
  • Draft
    35 pages
    English language
    sale 15% off

This document defines functional requirements for the OCF Cloud to Cloud Application Programming Interface (API).

  • Standard
    63 pages
    English language
    sale 15% off
  • Draft
    63 pages
    English language
    sale 15% off

This document defines security objectives, philosophy, Â Resources and mechanism that impacts OCF base layers of ISO/IEC 30118-1. ISO/IEC 30118-1 contains informative security content. The OCF Security Specification contains security normative content and may contain informative content related to the OCF base or other OCF documents.

  • Standard
    187 pages
    English language
    sale 15% off
  • Draft
    187 pages
    English language
    sale 15% off

This part of IEC 61970, which covers the definition of Common Grid Model Exchange Standard
(CGMES), defines the main rules and application’s requirements to meet business requirements
for assembled and merged model to fit relevant business services. This document does not
define the business requirements, business processes nor how applications are implemented.
This document defines how relevant Common Information Model (CIM) standards work together
so that specific business requirements can be resolved.
It also includes extensions to the Common Information Model (CIM). The current extensions are
defined in IEC 61970-301:2020 and will be covered in its future Amendment 1, but additional
extensions can be defined in other standards in the IEC 61970-600-series. The extensions can
be used to define additional profiles or to expand IEC 61970-450-series or IEC 61968-13
profiles. However, primary CGMES includes additional constraints on existing profiles and
validation of assembled and merged models that is based on existing profiles. This can be done
by making optional attributes and associations mandatory (required).
In addition, this document includes the specification of the serialisation that must be supported
by referring to an existing standard defined in IEC 61970-550-series, e.g., IEC 61970-552, and
making relevant constraints related to it.
The goal is to achieve interoperability between applications using CGMES in a highperformance
environment with combined minimum effort so that relevant business processes
are satisfied.
An overview of IEC 61970-600 series is provided in the following table, which also presents
identified needs that are not yet addressed.

  • Standard
    50 pages
    English language
    sale 10% off
    e-Library read for
    1 day

Per the IEC 61968 Interface Reference Model, the Network Operations function defined in this part of IEC 61968 provides utilities the means to supervise main substation topology (breaker and switch state), feeder topology and control equipment status through SCADA, AMI and other data sources. It also provides the means for handling network connectivity and loading conditions. Finally, it makes it possible for utilities to locate customer telephone complaints and coordinate activities of field crews with respect to planned and unplanned outages.
IEC 61968-3 specifies the information content of a set of message payloads that can be used to support many of the business functions related to network operations. Typical uses of the message payloads defined in IEC 61968-3 include data acquisition by external systems, fault isolation, fault restoration, trouble management and coordination of the real-time state of the network.
The scope diagram shown in [Figure 1] illustrates the possibility of implementing IEC 61968-3 functionality 51 as either a single integrated advanced distribution management system or as a set of separate functions - OMS, DMS and SCADA. Utilities may chose to buy these systems from different vendors and integrate them using the IEC 61968-3 messages. Alternatively, a single vendor could provide two or all of these components as a single integrated system. In the case of more than one system being provided by the same vendor, the vendor may chose to use either extensions of the IEC 61968- messages or a proprietary integration mechanism to provide enhanced functionality over and above what is required/supported by the IEC 61968-3 specification. While this is a possible implementation, clause 4.3 defines the scope in terms of business functions that are implemented in common vendor offerings.
Annexes in this standard document integration scenarios or use cases, which are informative examples showing typical ways of using the message payloads defined in this document as well as message payloads to be defined in other parts of the IEC 61968 series.

  • Standard
    374 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document contains requirements and measurements methods for the physical interface "A3" that is situated
between the power supply system(s) and the power consuming ICT equipment:
• the nominal voltage at power interface "A3" of ICT equipment defined in the present document is DC voltage up
to 400 V;
• the output performance of the power equipment including the cable network at the interface "A3";
• the input of the ICT equipment connected to interface "A3".
The DC power can be supplied by a DC output power system e.g. via on-grid AC rectifiers, from DC/DC converters in
solar systems, fuel cells, standby generators including a battery backup.
The present document aims at providing compatibility at interface "A3" between the power supply equipment and different
ICT equipment (including/monitoring, cooling system, etc.) connected to the same power supply.
The requirements are defined for the purpose of the present document:
• to identify a power supply system with the same characteristics for all ICT equipment defined in the area of
application; the area of application may be any location where the interface "A3" is used i.e.
telecommunication centres, Radio Base Stations, datacentres and customer premises;
• to facilitate interworking of different loads;
• to facilitate the standardization of power supply systems for ICT equipment;
• to facilitate the installation, operation and maintenance in the same network of ICT equipment and systems
from different origins;
• to secure robustness against temporary voltage deviations and transients during abnormal conditions.
General requirements for safety and EMC are out of the scope of the present document series unless specific
requirement not defined in existing safety or EMC standards.

  • Standard
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    31 pages
    English language
    sale 15% off
  • Standard
    31 pages
    English language
    sale 15% off
  • Draft
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the command set host systems use to access storage devices. It provides a common command set for systems manufacturers, system integrators, software suppliers, and suppliers of intelligent storage devices. This document maintains compatibility with the ACS-2 standard, ISO/IEC 17760-102, while providing additional functions.

  • Standard
    554 pages
    English language
    sale 15% off

This part of IEC 61970 specifies a standard interface for exchanging dynamic model information
needed to support the analysis of the steady state stability (small-signal stability) and/or
transient stability of a power system or parts of it. The schema(s) for expressing the dynamic
model information are derived directly from the CIM, more specifically from IEC 61970-302.
The scope of this document includes only the dynamic model information that needs to be
exchanged as part of a dynamic study, namely the type, description and parameters of each
control equipment associated with a piece of power system equipment included in the steady
state solution of a complete power system network model. Therefore, this profile is dependent
upon other standard profiles for the equipment as specified in IEC 61970-452, CIM static
transmission network model profiles, the topology, the steady state hypothesis and the steadystate
solution (as specified in IEC 61970-456, Solved power system state profiles) of the power
system, which bounds the scope of the exchange. The profile information described by this
document needs to be exchanged in conjunction with IEC 61970-452 and IEC 61970-456
profiles’ information to support the data requirements of transient analysis tools. IEC 61970-456
provides a detailed description of how different profile standards can be combined to form
various types of power system network model exchanges.
This document supports the exchange of the following types of dynamic models:
• standard models: a simplified approach to exchange, where models are contained in
predefined libraries of classes interconnected in a standard manner that represent dynamic
behaviour of elements of the power system. The exchange only indicates the name of the
model along with the attributes needed to describe its behaviour.
• proprietary user-defined models: an exchange that would provide users the ability to
exchange the parameters of a model representing a vendor or user proprietary device where
an explicit description of the model is not described in this document. The connections
between the proprietary models and standard models are the same as described for the
standard models exchange. Recipient of the data exchange will need to contact the sender
for the behavioural details of the model.
This document builds on IEC 61970-302, CIM for dynamics which defines the descriptions of
the standard dynamic models, their function block diagrams, and how they are interconnected
and associated with the static network model. This type of model information is assumed to be
pre-stored by all software applications hence it is not necessary to be exchanged in real-time
or as part of a dynamics model exchange.

  • Standard
    460 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO/IEC 11760-103:2021 specifies the command set host systems use to access storage devices. It provides a common command set for systems manufacturers, system integrators, software suppliers, and suppliers of intelligent storage devices. This standard maintains compatibility with the ACS-2 standard, ISO/IEC 17760-102, while providing additional functions.

  • Standard
    576 pages
    English language
    sale 15% off

IEC 63002:2021 defines common charging interoperability guidelines for power sources (external power supplies (EPSs) and other Sources) used with computing and consumer electronics devices that implement IEC 62680-1-3 (USB Type-C Cable and Connector Specification).
This document defines normative requirements for an EPS to ensure interoperability; in particular, it specifies the data communicated from a power source to a device and certain safety elements of the EPS, cable, and device. While the requirements focus of this document is on the EPS and the behaviour at its USB Type-C connector interface, it is also important to comprehend cable assembly and device capabilities and behaviours in order to assure end-to-end charging interoperability. This document does not apply to all design aspects of an EPS. This document does not specify regulatory compliance requirements for aspects such as product safety, EMC or energy efficiency.
This document provides recommendations for the behaviour of a device when used with a power source compliant with this document. It specifies the minimum hardware specification for an EPS implementing IEC 62680-1-3. This document also specifies the data objects used by a charging system utilizing IEC 62680-1-2 to understand the identity, design and performance characteristics, and operating status of an external power supply. IEC 62680-1-2 focuses on power delivery applications ranging to 100 W for a variety of computing and consumer electronics devices including notebook computers, tablets, smartphones, small form-factor desktops, monitor displays and other related multimedia devices.
This document relies on established mechanical and electrical specifications, and communication protocols specified by IEC 62680-1-2 and IEC 62680-1-3. These specifications support methods for establishing the best performing interoperability between untested combinations of EPS and devices with the aim of improving consumer satisfaction.
Information describing the USB charging interoperability model, overview of USB Type-C and USB Power Delivery specifications, and factors for charging performance are also provided to support implementation of this document.
IEC 63002:2021 cancels and replaces the first edition published in 2016. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) title is changed from Identification and communication interoperability method for external power supplies used with portable computing devices;
b) Clause 4, EPS interoperability based on USB technologies, is added;
c) Clause 5, EPS specification, adds hardware and protection requirements; overvoltage protection is changed from optional to normative;
d) Annex B and Annex C are added, providing an explanation of the design features in USB Power Delivery that enhance reliability and an explanation of the concepts of charge rate and power.

  • Standard
    76 pages
    English and French language
    sale 15% off

This part of IEC 61968 specifies profiles that can be used to exchange Network Models in a
Utility or between a Utility and external applications to the utility. This document provides a list
of profiles which allow to model balanced and unbalanced distribution networks in order to
conduct network analysis (Power flow calculation). Therefore, it leverages already existing
profiles (IEC 61970-45x based on IEC 61970-301 (CIM base) or profiles based on
IEC 6196811
CIM extension for Distribution). This document reuses some profiles without any
change, or eventually extends them or restricts them. Moreover, it proposes other profiles to
reflect Distribution needs.
Use of CIM in Distribution is not a new topic. Several documents can be of interest
[13][17][18][19][20]. This document includes informative parts, as CIM model extensions, which
could be integrated in future versions of the IEC CIM Model. These extensions have been used
by some utilities for utility internal information exchange use cases and to support information
exchanges between different market participants like Transmisstion System Operators (TSO),
Distributed System Operators (DSO), Distributed Network Operators (DNO) and Significant Grid
Users (SGU) including generators and industry (see Annex J for example).

  • Standard
    374 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document is based on requirements from ETSI TS 102 656 [2].
The present document contains handover requirements and a handover specification for the data that is identified in
national legislations on Retained Data.
The present document considers both the requesting of retained data and the delivery of the results.
The present document defines an electronic interface. An informative annex describes how this interface may be
adapted for manual techniques. Apart from in annex I, the present document does not consider manual techniques.

  • Standard
    141 pages
    English language
    sale 15% off
  • Technical specification
    141 pages
    English language
    sale 10% off
    e-Library read for
    1 day

Storage Management Technical Specification, Part 2 Common Architecture, 1.8.0 Rev 4 defines the core architecture and protocols in SMI-S. The components of SMI-S architecture include: Transport - communicating management information between constituents of the management system Health and fault management - detecting failures through monitoring the state of storage components General information about the object model Names - how SMI-S uses names to allow applications to correlate across SMI-S and to other standards Standard messages - how exceptions are presented to client applications Service discovery - techniques clients use to discover SMI-S services Installation and upgrade - recommendations for implementations Compliance - requirement for compliance to the standard

  • Standard
    192 pages
    English language
    sale 15% off
  • Draft
    192 pages
    English language
    sale 15% off

The host-base storage portion of the Storage Management Technical Specification defines management profiles for autonomous, component and abstract profiles for management of host-based storage devices. The autonomous profiles describe the management of a stand-alone host-based storage entity. The component profiles describe management of aspects of host-based storage entities that may be used by other autonomous profiles. Finally, this section describes abstract profiles that may be used as a basis for creating additional Host-based autonomous profiles. This version of the Host-based Storage portion of the Storage Management Technical Specification includes autonomous profiles: "The Host Discovered Resources Profile This profile defines the model for the storage devices presented to an operating system running on a host computer system. In addition, this profile describes the map of storage associated to a host-computer system that a client application can discover. "The Fibre Channel HBA Profile This profile defines the model and functions of a Fibre Channel HBA that exports block storage to a host computer system from a SAN device (Fibre Channel switch, array, tape library, etc.). iSCSI Initiator Profile This profile defines the model and functions necessary to manage an iSCSI initiator. Component profiles used by autonomous profiles to describe aspects of host-based storage elements and services. The component profiles defined in this version of the specification include: Host Hardware RAID Controller Profile This profile defines the model and functions of a host-based RAID controller that exports block storage to a host computer system from locally attached storage devices (internal hard drives, JBODs, etc.) Storage HBA Profile This profile defines the model and functions of a SAS, SATA, SPI, or Fibre Channel HBA that exports storage to a host computer system from a SAN device (Fibre Channel switch, array, tape library, etc.). Disk Partition Profile The Disk Partition profile models partition (or slice) configuration services provided by operating systems on some platforms. SB Multipath Management Profile The SB Multipath Management Profile models paths (connections between host controllers and device ports) for environments supporting the SB (Single Byte) command protocol. SCSI Multipath Management Profile The SCSI Multipath Management profile models paths (connections between host controllers, device ports, and logical units) for environments supporting the SCSI command protocol.

  • Standard
    165 pages
    English language
    sale 15% off
  • Draft
    165 pages
    English language
    sale 15% off

The Storage Management Technical Specification, Part 6 Fabric defines management profiles for Autonomous (top level) profiles for programs and devices whose central function is providing support for storage networking. This version of Storage Management Technical Specification, Part 6 Fabric includes these autonomous profiles: Fabric This profile defines the model and functions of a storage network including topology and zoning control. Switch This profile defines the model and functions of a Fibre Channel Switch including state, status, and control of the device and it’s connections and product information, Extender This profile defines the model and functions of a networking device that allows for fibre channel to be extended over other networks, and specifically over IP (FCIP).

  • Standard
    186 pages
    English language
    sale 15% off
  • Draft
    186 pages
    English language
    sale 15% off

This version of the specification models various details of the following objects of the media library for monitoring. Library Drives Changer Devices Slots IO Slots SCSI Interfaces and SCSI and FC Target Ports Physical Tapes Physical Package Magazines In general, a CIM client can monitor the health and status of the above objects as well as get alert, status change and lifecycle CIM indications. In addition, a client can control the movement of media in a library using this specification.

  • Standard
    55 pages
    English language
    sale 15% off
  • Draft
    55 pages
    English language
    sale 15% off

Thie ISO/IEC 24775-4:2021 defines an interface for the secure, extensible, and interoperable management of a distributed and heterogeneous storage system. This interface uses an object-oriented, XML-based, messaging-based protocol designed to support the specific requirements of managing devices and subsystems in this storage environment. Using this protocol, this e ISO/IEC 24775-4:2021 describes the information available to a WBEM Client from an SMI-S compliant WBEM Server.

  • Standard
    946 pages
    English language
    sale 15% off
  • Draft
    946 pages
    English language
    sale 15% off

Storage Management Technical Specification, Part 3 Common Profiles, 1.8.0 Rev 4 defines profiles that are supported by profiles defined in the other parts of this standard. The first few clauses provide background material that helps explain the purpose and profiles. Common port profiles are grouped together since they serve as transport-specific variations of a common model. The port profiles are followed by other common profiles.

  • Standard
    352 pages
    English language
    sale 15% off
  • Draft
    352 pages
    English language
    sale 15% off

The ISO/IEC 24775-1:2021 defines an interface for the secure, extensible, and interoperable management of a distributed and heterogeneous storage system. This interface uses an object-oriented, XML-based, messaging-based protocol designed to support the specific requirements of managing devices and subsystems in this storage environment. Using this protocol, this ISO/IEC 24775-1:2021Â describes the information available to a WBEM Client from an SMI-S compliant WBEM Server

  • Standard
    21 pages
    English language
    sale 15% off
  • Draft
    21 pages
    English language
    sale 15% off

Storage Management Technical Specification, Part 2 Common Architecture, 1.8.0 Rev 4 defines the core architecture and protocols in SMI-S. The components of SMI-S architecture include: Transport - communicating management information between constituents of the management system Health and fault management - detecting failures through monitoring the state of storage components General information about the object model Names - how SMI-S uses names to allow applications to correlate across SMI-S and to other standards Standard messages - how exceptions are presented to client applications Service discovery - techniques clients use to discover SMI-S services Installation and upgrade - recommendations for implementations Compliance - requirement for compliance to the standard

  • Standard
    377 pages
    English language
    sale 15% off
  • Draft
    377 pages
    English language
    sale 15% off