Ieee Standard For Power Electronics Open System Interfaces in Zo

IEEE Standard for Power Electronics
Open System Interfaces in Zonal

Electrical Distribution Systems Rated
Above 100 kW
IEEE Industry Applications Society
Sponsored by the
Petroleum and Chemical Industry Committee
IEEE
3 Park Avenue IEEE Std 1826™-2012
New York, NY 10016-5997
USA
22 June 2012
Authorized licensed use limited to: The University of Utah. Downloaded on June 17,2014 at 10:30:56 UTC from IEEE Xplore. Restrictions apply.
IEEE Std 1826™-2012

Above 100 kW
Sponsor
Petroleum and Chemical Industry Committee

of the
IEEE Industry Applications Society
Approved 8 June 2012
IEEE-SA Standards Board
Abstract: Open system interfaces for high power electronics equipment used in zonal electrical
distribution systems rated above 100 kW are identified in this standard. The required power,
monitoring, information exchange, control, and protection interfaces are based on technological
maturity, accepted practices, and allowances for future technology insertions. Also, rigorous
assessment mechanisms, interface control management, and proactive conformance testing that
shall be used to verify and validate open systems to enable plug-and-play operability
independently of the components’ origin are defined.
Airports, hospitals, major data processing centers (especially those using uninterruptible power
supply), broadcast systems, and maritime vessels and platforms are applications covered by this
standard. Existing terrestrial utility power systems that do not yet contain the electronic power
interfaces and high-speed communication networks that are essential to use this standard shall
be upgraded by its application.
Keywords: IEEE 1826, open system interfaces, PEEB, plug-and-play, power electronics, power
electronics building blocks, quality of service, verification and validation, zonal electrical
distribution system
•
The Institute of Electrical and Electronics Engineers, Inc.

3 Park Avenue, New York, NY 10016-5997, USA
Copyright © 2012 by The Institute of Electrical and Electronics Engineers, Inc.

All rights reserved. Published 22 June 2012. Printed in the United States of America.
IEEE is a registered trademark in the U.S. Patent & Trademark Office, owned by The Institute of Electrical and Electronics
Engineers, Incorporated.
PDF: ISBN 978-0-7381-7283-5 STD97258

Print: ISBN 978-0-7381-7389-4 STDPD97258
IEEE prohibits discrimination, harassment, and bullying. For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html.
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission
of the publisher.
Notice and Disclaimer of Liability Concerning the Use of IEEE Documents: IEEE Standards documents are developed
within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA)
Standards Board. IEEE develops its standards through a consensus development process, approved by the American National
Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product.
Volunteers are not necessarily members of the Institute and serve without compensation. While IEEE administers the process
and establishes rules to promote fairness in the consensus development process, IEEE does not independently evaluate, test, or
verify the accuracy of any of the information or the soundness of any judgments contained in its standards.
Use of an IEEE Standard is wholly voluntary. IEEE disclaims liability for any personal injury, property or other damage, of
any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the
publication, use of, or reliance upon any IEEE Standard document.
IEEE does not warrant or represent the accuracy or content of the material contained in its standards, and expressly disclaims
any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that
the use of the material contained in its standards is free from patent infringement. IEEE Standards documents are supplied "AS
IS."
The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or
provide other goods and services related to the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a
standard is approved and issued is subject to change brought about through developments in the state of the art and comments
received from users of the standard. Every IEEE standard is subjected to review at least every ten years. When a document is
more than ten years old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of
some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the
latest edition of any IEEE standard.
In publishing and making its standards available, IEEE is not suggesting or rendering professional or other services for, or on
behalf of, any person or entity. Nor is IEEE undertaking to perform any duty owed by any other person or entity to another.
Any person utilizing any IEEE Standards document should rely upon his or her own independent judgment in the exercise of
reasonable care in any given circumstances or, as appropriate, seek the advice of a competent professional in determining the
appropriateness of a given IEEE standard.
Translations: The IEEE consensus development process involves the review of documents in English only. In the event that
an IEEE standard is translated, only the English version published by IEEE should be considered the approved IEEE standard.
Official Statements: A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board
Operations Manual shall not be considered the official position of IEEE or any of its committees and shall not be considered to
be, nor be relied upon as, a formal position of IEEE. At lectures, symposia, seminars, or educational courses, an individual
presenting information on IEEE standards shall make it clear that his or her views should be considered the personal views of
that individual rather than the formal position of IEEE.
Comments on Standards: Comments for revision of IEEE Standards documents are welcome from any interested party,
regardless of membership affiliation with IEEE. However, IEEE does not provide consulting information or advice pertaining
to IEEE Standards documents. Suggestions for changes in documents should be in the form of a proposed change of text,
together with appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is
important to ensure that any responses to comments and questions also receive the concurrence of a balance of interests. For
this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant
response to comments or questions except in those cases where the matter has previously been addressed. Any person who
would like to participate in evaluating comments or revisions to an IEEE standard is welcome to join the relevant IEEE
working group at http://standards.ieee.org/develop/wg/.
Comments on standards should be submitted to the following address:
Secretary, IEEE-SA Standards Board

445 Hoes Lane
Piscataway, NJ 08854
USA
Photocopies: Authorization to photocopy portions of any individual standard for internal or personal use is granted by The
Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center.
To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive,
Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for educational
classroom use can also be obtained through the Copyright Clearance Center.
Notice to users
Laws and regulations

Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with
the provisions of any IEEE Standards document does not imply compliance to any applicable regulatory
requirements. Implementers of the standard are responsible for observing or referring to the applicable
regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not
in compliance with applicable laws, and these documents may not be construed as doing so.
Copyrights
This document is copyrighted by the IEEE. It is made available for a wide variety of both public and
private uses. These include both use, by reference, in laws and regulations, and use in private self-
regulation, standardization, and the promotion of engineering practices and methods. By making this
document available for use and adoption by public authorities and private users, the IEEE does not waive
any rights in copyright to this document.
Updating of IEEE documents

Users of IEEE Standards documents should be aware that these documents may be superseded at any time
by the issuance of new editions or may be amended from time to time through the issuance of amendments,
corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the
document together with any amendments, corrigenda, or errata then in effect. In order to determine whether
a given document is the current edition and whether it has been amended through the issuance of
amendments, corrigenda, or errata, visit the IEEE-SA Website at http://standards.ieee.org/index.html or
contact the IEEE at the address listed previously. For more information about the IEEE Standards
Association or the IEEE standards development process, visit IEEE-SA Website at
http://standards.ieee.org/index.html.
Errata
Errata, if any, for this and all other standards can be accessed at the following URL:
http://standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata
periodically.
iv
Copyright © 2012 IEEE. All rights reserved.
Patents
Attention is called to the possibility that implementation of this standard may require use of subject matter
covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to
the existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant
has filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the
IEEE-SA Website at http://standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may
indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without
compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of
any unfair discrimination to applicants desiring to obtain such licenses.
Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not
responsible for identifying Essential Patent Claims for which a license may be required, for conducting
inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or
conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing
agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that
determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely
their own responsibility. Further information may be obtained from the IEEE Standards Association.
v
Participants
At the time this IEEE standard was completed, the Power Electronics Working Group had the following
membership:
Yuri Khersonsky, Chair

Norbert Doerry, Vice Chair
Roger Dougal, Vice Chair
Terry Ericsen, Vice Chair
Joseph Piff, Secretary
John Amy Narain Hingorani Kevin Peterson

Sharon Beerman-Curtin Boris Jacobson Michael Roa
Paul Bishop Hans Krattiger George Robinson
Dushan Boroyevich Steven Ly Charles Smith
Joseph Borraccini Earl MacDonald Zareh Sogohomonian
Robert Cuzner Alan Mantooth Michael “Mischa” Steurer
Omar Farugue Michael Moodie Giorgio Sullogoi
Herbert Ginn Albert Tucker
The following working group members finalized the development of this standard with working group
inputs and provided technical editing of this standard:
John Amy Herbert Ginn Joseph Piff

Paul Bishop Narain Hingorani George Robinson
Norbert Doerry Yuri Khersonsky Michael “Mischa” Steurer
Roger Dougal Earl MacDonald Albert Tucker
The following members of the individual balloting committee voted on this standard. Balloters may have
voted for approval, disapproval, or abstention.
Dwight Alexander Mohammed Islam Iulian Profir

Thomas Basso Geza Joos Li Qi
Paul Bishop Yuri Khersonsky Michael Roberts
Gustavo Brunello Michael Knauff George Robinson
Mark Bushnell Joseph L. Koepfinger Charles Rogers
William Byrd Jim Kulchisky Randall Safier
Paul Cardinal Roger Lawrence Bartien Sayogo
David Cartes Greg Luri Gil Shultz
Keith Chow Wayne Manges Veselin Skendzic
Robert Cuzner William McBride Jerry Smith
Norbert Doerry Jerry Murphy Zareh Soghomonian
Roger Dougal Ryan Musgrove Michael “Mischa” Steurer
Neal Dowling Michael S. Newman Giorgio Sulligoi
Gary Engmann Lorraine Padden Joseph Sullivan
Randall Groves Donald Parker Albert Tucker
Narain Hingorani Dev Paul John Vergis
Werner Hoelzl Kevin Peterson Ahmed Zobaa
Joseph Piff
vi
When the IEEE-SA Standards Board approved this standard on 8 June 2012, it had the following
membership:
Richard H. Hulett, Chair

John Kulick, Vice Chair
Robert M. Grow, Past Chair
Satish Aggarwal Alex Gelman Oleg Logvinov

Masayuki Ariyoshi Paul Houzé Ted Olsen
Peter Balma Jim Hughes Gary Robinson
William Bartley Joseph L. Koepfinger* Jon Rosdahl
Ted Burse Young Kyun Kim Mike Seavey
Clint Chaplin David J. Law Yatin Trivedi
Wael Diab Thomas Lee Phil Winston
Jean-Philippe Faure Hung Ling Yu Yuan
*Member Emeritus
Also included are the following nonvoting IEEE-SA Standards Board liaisons:
Richard DeBlasio, DOE Representative

Michael Janezic, NIST Representative
Patrick Gibbons
IEEE Standards Program Manager, Document Development
Lisa Perry
IEEE Standards Program Manager, Technical Program Development
vii
Introduction
This introduction is not part of IEEE Std 1826-2012, IEEE Standard for Power Electronics Open System Interfaces in
Zonal Electrical Distribution Systems Rated Above 100 kW.
The IEEE P1826 Working Group has been sponsored by the Petroleum & Chemical Industry (IAS/PCI)
Committee of the IEEE Industry Applications Society and the Standards Committee (PEL/SC) of the IEEE
Power Electronics Society to provide a uniform standard for high power electronics open system interfaces
in zonal electrical distribution systems rated above 100 kW. This standard applies in cases where power
electronics are the interface between the zones. This standard defines how openness of system should be
verified and validated through rigorous assessment mechanisms, interface control management, and
proactive conformance testing to enable plug-and-play operability independently of components origin.
Interfaces are grouped by functions and are based on technological maturity, accepted practices, and
allowances for future technology insertions.
This standard applies to electrical power distribution systems in airports, hospitals, major data processing
centers (especially those using uninterruptible power supply), broadcast systems, and maritime vessels and
platforms. Existing terrestrial power systems generally do not yet contain the electronic power interfaces
and high speed communication networks that are essential to use of this standard; however, it shall be
applied to upgrade these legacy systems.
viii
Contents
1. Overview .................................................................................................................................................... 1
1.1 Scope ................................................................................................................................................... 1
1.2 Purpose ................................................................................................................................................ 1
1.3 Application and limitations.................................................................................................................. 2
1.4 Intent .................................................................................................................................................... 2
2. Normative references.................................................................................................................................. 2
3. Definitions, abbreviations, and acronyms .................................................................................................. 3

3.1 Definitions ........................................................................................................................................... 3
3.2 Abbreviations and acronyms ............................................................................................................... 4
4. Zonal electrical distribution system (ZEDS) fundamentals ........................................................................ 4

4.1 Introduction ......................................................................................................................................... 4
4.2 Zonal distribution system elements ..................................................................................................... 6
4.3 Quality of service (QoS) ...................................................................................................................... 8
4.4 Power system equipment general requirements ................................................................................... 9
4.5 Architectural principles ......................................................................................................................11
5. Monitoring, information exchange, control, and protection interfaces ......................................................11

5.1 Introduction ........................................................................................................................................11
5.2 Functionality .......................................................................................................................................12
5.3 Interfaces ............................................................................................................................................13
6. Electric power interfaces ...........................................................................................................................15

6.1 Introduction ........................................................................................................................................15
6.2 Power interface standards ...................................................................................................................15
6.3 Electrical power interface ratings .......................................................................................................16
6.4 Power interfaces at the zonal boundary ..............................................................................................17
6.5 Power interfaces for the in-zone distribution bus ...............................................................................18
7. Verification and validation (V&V) ............................................................................................................18

7.1 General ...............................................................................................................................................18
7.2 Activity: Concept Verification ...........................................................................................................19
7.3 Activity: Requirements Verification ...................................................................................................20
7.4 Activity: Design Verification..............................................................................................................22
7.5 Activity: First Article V&V ................................................................................................................24
7.6 Activity: Integration Testing ...............................................................................................................26
7.7 Activity: Qualification Testing ...........................................................................................................27
7.8 Activity: Commissioning Testing .......................................................................................................28
7.9 Activity: Acceptance Testing..............................................................................................................29
8. Maintenance of open systems interfaces ...................................................................................................30
Annex A (informative) Examples of applications of zonal electrical distribution systems (ZEDS) ............31
A.1 Naval Destroyer ZEDS ......................................................................................................................31
A.2 Distributed resources islands in the terrestrial power grid .................................................................32
Annex B (informative) Bibliography............................................................................................................33
ix
Above 100 kW
IMPORTANT NOTICE: IEEE Standards documents are not intended to ensure safety, health, or
environmental protection, or ensure against interference with or from other devices or networks.
Implementers of IEEE Standards documents are responsible for determining and complying with all
appropriate safety, security, environmental, health, and interference protection practices and all
applicable laws and regulations.
This IEEE document is made available for use subject to important notices and legal disclaimers.
These notices and disclaimers appear in all publications containing this document and may
be found under the heading “Important Notice” or “Important Notices and Disclaimers
Concerning IEEE Documents.” They can also be obtained on request from IEEE or viewed at
http://standards.ieee.org/IPR/disclaimers.html.
1. Overview
1.1 Scope
This standard identifies open system interfaces for high power electronics equipment used in zonal
electrical distribution systems rated above 100 kW. Interfaces are grouped into key and non-key interfaces
and are based on technological maturity, accepted practices, and allowances for future technology
insertions. This standard defines how openness of system should be verified and validated through rigorous
assessment mechanisms, interface control management, and proactive conformance testing to enable plug-
and-play operability independently of the components origin. It also formulates specific interface
requirements for open zonal electrical distribution systems on ships and platforms.
1.2 Purpose
The purpose of this document is to provide a uniform standard for high power electronics open system
interfaces in zonal electrical distribution systems rated above 100 kW. The stated specifications and
requirements are universally applied to maintain total power system performance and efficiency under
1
IEEE Std 1826-2012
IEEE Standard for Power Electronics Open System Interfaces
in Zonal Electrical Distribution Systems Rated Above 100 kW
changing mission and loads conditions. They will be sufficient for most installations, including ships and
platforms. This standard complements IEEE Std 1662TM.
1.3 Application and limitations
A zonal electrical distribution system (ZEDS) consists of power system elements serving a group of loads
and is part of a larger power system. A ZEDS plus the loads it serves comprise a zone. A ZEDS has a
limited number of power and control interfaces with the larger encompassing system and has the property
that faults within the zone do not propagate outside the zonal boundaries.
This standard is intended to apply in cases where power electronics are the interface between the zones. It
is not intended to apply where mechanical circuit breakers are the only means of isolating a zone. Possible
applications include airports, hospitals, major data processing centers (especially those using
uninterruptible power supply), broadcast systems, and maritime vessels and platforms.
Existing terrestrial power systems generally do not yet contain the electronic power interfaces and high-
speed communication networks that are essential to use this standard; a long phase-in period will thus exist
before this standard can be generally applied to these legacy systems.
1.4 Intent
This document applies open system concepts to zonal electric power systems controlled by power
electronics. For a zonal power system to be “open,” each device attached to the power bus shall meet these
criteria:
a) Each device shall implement certain functionality that lets it “play well” with the other system
components, including implementation of power control and safety features
b) Each device shall conform to standard control and information interfaces
c) Each device shall conform to standard power interfaces
This standard defines the functionality, control and information interfaces, and power interfaces. This
document references and extends the application of IEEE Std 1662 and IEEE Std 1676 TM 1.
Guidance on implementing open systems is provided by Levine et al. [B19] and Abbott et al. [B1] 2.
2. Normative references
The following referenced documents are indispensable for the application of this document (i.e., they must
be understood and used, so each referenced document is cited in text and its relationship to this document is
explained). For dated references, only the edition cited applies. For undated references, the latest edition of
the referenced document (including any amendments or corrigenda) applies.
IEC 60038:2009, IEC Standard Voltages. 3

IEC 61850, Communication Networks and Systems in Substations.
1
Information on references can be found in Clause 2.
2
The numbers in brackets correspond to those of the bibliography in Annex B.
3
IEC publications are available from the Sales Department of the International Electrotechnical Commission, 3 rue de Varembé, PO
Box 131, CH-1211, Geneva 20, Switzerland (http://www.iec.ch/). IEC publications are also available in the United States from the
Sales Department, American National Standards Institute, 25 West 43rd Street, 4th Floor, New York, NY 10036, USA
(http://www.ansi.org).
2
IEEE Std 1826-2012
IEEE Std 493TM, IEEE Recommended Practice for the Design of Reliable Industrial and Commercial
Power Systems. 4, 5
IEEE Std 1012TM-2012, IEEE Standard for System and Software Verification and Validation.
IEEE Std 1547.1TM-2005, IEEE Standard Conformance Test Procedures for Equipment Interconnecting
Distributed Resources with Electric Power Systems.
IEEE Std 1547.4TM, IEEE Guide for Design, Operation, and Integration of Distributed Resource Island
Systems with Electric Power Systems.
IEEE Std 1662TM, IEEE Guide for the Design and Application of Power Electronics in Electrical Power
Systems on Ships.
IEEE Std 1676TM, IEEE Guide for Control Architecture for High Power Electronics (1 MW and Greater)
Used in Electric Power Transmission and Distribution Systems.
IEEE Std 1709TM-2010, IEEE Recommended Practice for 1 kV to 35 kV Medium-Voltage DC Power

Systems on Ships.
IEEE Std 2030TM, IEEE Guide for Smart Grid Interoperability of Energy Technology and Information
Technology Operation with the Electric Power System (EPS), End-Use Applications, and Loads.
IEEE Std 3007.2TM, IEEE Recommended Practice for the Maintenance of Industrial and Commercial
Power Systems.
3. Definitions, abbreviations, and acronyms
3.1 Definitions
For the purposes of this document, the following terms and definitions apply. The IEEE Standards
Dictionary Online should be consulted for terms not defined in this clause. 6
community: a logical and physical grouping of neighborhoods.
neighborhood: a geographic or physical service area, a plant or grouping of buildings, a ship or a marine
platform, or other similar entity.
power grid: an assembly of normally interconnected power systems arranged to meet the power generation
and consumption needs of a relatively large geographic area.
power system: an assembly or grouping of generation, storage, and consumption assets arranged in a
common community.
4
IEEE publications are available from The Institute of Electrical and Electronics Engineers, 445 Hoes Lane, Piscataway, NJ 08854,
USA (http://standards.ieee.org/).
5
IEEE standards or products referred to in this clause are trademarks of The Institute of Electrical and Electronics Engineers, Inc.
6
IEEE Standards Dictionary Online subscription is available at: http://www.ieee.org/portal/innovate/products/standard/
/standards_dictionary.html.
3
IEEE Std 1826-2012
zone: a logical and physical grouping of generation, storage, or consumption assets arranged in a common
neighborhood. Zones with generation or storage may be operated for periods of time independently from
the power system. A zone is the smallest logical and physical grouping of assets.
3.2 Abbreviations and acronyms
HDD hardware design description
HMI human-machine interface
HRS hardware requirements specification
IDD interface design document
IRS interface requirements specification
MTBSI mean time between service interruptions
QoS quality of service
SRS systems requirements specification
TRA threat and risk assessment
VVP verification and validation plan
V&V verification and validation
ZEDS zonal electrical distribution system
4. Zonal electrical distribution system (ZEDS) fundamentals
4.1 Introduction
A zone is a logical and physical grouping of generation, storage, or consumption assets arranged in a
common neighborhood. Zones with generation or storage may be operated for periods of time
independently from the power system. A zone is the smallest logical and physical grouping of assets
covered by this standard and is characterized by the following attributes:
 Contains one or more independent power device, i.e., converter, load, storage, generator
 Normally operates as an integral part of a larger system
 May operate independently of the zonal system for limited periods of time under special operating
conditions
A ZEDS consists of power system elements serving a group of loads and is part of a larger power system.
A ZEDS plus the loads it serves comprise a zone. A ZEDS has a limited number of power and control
interfaces with the larger encompassing system and has the property that faults within the zone do not
propagate outside the zonal boundaries. Furthermore, a design objective of a ZEDS and the larger system
containing it is that loads served by it are provided with the type of power, quality of power, and quality of
4
IEEE Std 1826-2012
service (QoS) specified by a customer-supplier agreement. Loads served by the ZEDS only receive power
via the ZEDS. The power system elements comprising a ZEDS include power conversion equipment,
controls, switchgear, cabling, and, optionally, energy storage and generation.
In many applications, the boundaries of the zone will correspond to geographical boundaries. From a power
system perspective, this is not strictly required. Furthermore, even if geographical boundaries are
employed, not all power system equipment within the geographical boundaries is necessarily part of the
ZEDS. Likewise, not all loads within the geographic boundaries are necessarily part of the zone. Examples
of applications of ZEDS are provided in Annex A.
If required by the customer, a ZEDS has the capability to operate when isolated from the rest of the power
system for either a limited period of time or continuously. In this case, the ZEDS shall have energy storage
and/or generation. Specific guidance for understanding how distributed resources (both generators and
energy storage systems) may be established as ZEDs that are isolated from the rest of the power system is
provided in IEEE Std 1547.4.
In some applications, a ZEDS can be designed without the use of power electronics to achieve the ZEDS
objectives. This standard does not apply to these applications. This standard applies to ZEDS employing
power electronics and the loads served by the ZEDS aggregate to at least 100 kW.
Figure 1 shows a zonal power system as an element of a larger power system. Figure 2 shows the elements
of a zonal power system and their power interfaces.
Figure 1 —Power system versus zone (graphic)
5
IEEE Std 1826-2012
Figure 2 —Electrical power block diagram
4.2 Zonal distribution system elements
4.2.1 External-to-bus conversion
The external-to-bus conversion element has the following functions:
a) Prevent fault propagation to the external power system or other zone(s) due to faults within the
zone
b) Prevent faults observed on the external interface from propagating to the in-zone distribution bus
c) Convert power received through the external interface from the external power system or other
zone(s) to the power type needed for the in-zone distribution bus
d) Convert power from the in-zone distribution bus originating from in-zone energy storage or in-zone
generation to the power type needed by the external power system or other zone(s) via the external
interface (optional)
6
IEEE Std 1826-2012
A ZEDS may have multiple external-to-bus conversion elements to interface with one or more external
power systems or other zone(s).
4.2.2 In-zone distribution bus
The in-zone distribution bus provides a means for the exchange of power among external-to-bus
conversion, in-zone energy storage, in-zone generation, and bus-to-internal conversion. The in-zone
distribution bus may be totally enclosed within the boundaries of a single equipment cabinet or distributed
throughout the zone. The in-zone distribution bus may be segmented into multiple buses.
4.2.3 In-zone energy storage
An in-zone energy storage element stores electrical energy received from the in-zone distribution bus that
later may be used to provide power back to the in-zone distribution bus. An in-zone energy storage element
is an optional element of the ZEDS. In-zone energy storage is typically employed to achieve QoS
requirements but may also fulfill power quality and other system requirements. An in-zone energy storage
element shall protect the in-zone distribution bus from faults internal to the in-zone energy storage element.
4.2.4 In-zone generation
An in-zone generation element converts fuel into electrical energy to provide power to the in-zone
distribution bus. An in-zone generation element is an optional element of the ZEDS. An in-zone generation
element shall protect the in-zone distribution bus from faults internal to the in-zone generation element.
4.2.5 Bus-to-internal conversion
A bus-to-internal conversion element converts electrical power from the type and quality of the in-zone
distribution bus to the type, power quality, and QoS required by end-use devices or distribution panel
elements. A bus-to-internal conversion element shall protect the distribution panel from faults internal to
end-use devices, connected power cables, and distribution panel elements.
A power system designer may optionally design the bus-to-internal conversion element to provide
regenerative power produced by end-use devices to the in-zone distribution bus.
4.2.6 Distribution panel
A distribution panel element accepts power from the bus-to-internal conversion element and distributes the
required type, power quality, and QoS to multiple end-use devices. The distribution panel element shall
protect the bus-to-internal conversion element from faults internal to end-use devices and power cables.
The distribution panel may include power conditioning.
4.2.7 End-use device
An end-use device is typically an electrical load. It does not connect directly to the in-zone distribution bus.
It also may be a source. It is provided power from or may provide power to one or more distribution panel
elements or bus-to-internal conversion elements. To prevent catastrophic failure due to the end-use device
fault, a back-up disconnect system may be necessary.
7
IEEE Std 1826-2012
4.3 Quality of service (QoS)
QoS is a metric of how reliably the power system provides energy to the loads. It is calculated as a mean-
time-between-service-interruption (MTBSI) (IEEE Std 493). QoS takes into account equipment failures
and normal system operation transients.
In this standard, loads are categorized into four QoS categories: uninterruptible, short-term interrupt, long-
term interrupt, and exempt.
4.3.1 Service interruption
A service interruption is any interruption in service, or power quality degradation outside of acceptable
parameters, for a period of time that results in the parent system of the load not being capable of meeting its
requirements. The duration of service interruption is measured relative to two system-dependent times: t1
and t2. A load tolerates an interruption when the performance of the load is acceptable to the end user
during and after the interruption.
4.3.2 Reconfiguration time (t1)
Reconfiguration time (t1) is defined as the maximum time to reconfigure the distribution system without
bringing on additional generation capacity.
4.3.3 Generator start time (t2)
Generator start time (t2) is defined as the maximum time following an interruption in power to restore
sufficient generation capacity to serve loads from zonal generation or from the external power interfaces.
4.3.4 Mean time between service interruptions (MTBSI)
Different operating conditions may have different requirements for the MTBSI. These different operating
conditions are generally defined and the MTBSI calculated over an operating cycle. Associated with each
operating condition is a machinery concept of operation that details the expected policies for redundancy,
rolling reserve, etc., needed to achieve the customer-specified MTBSI.
4.3.5 Uninterruptible load
Uninterruptable loads are those that cannot tolerate service interruptions greater than t1.
The ZEDS shall provide the minimum achievable service interruption with a reliability in excess of the
customer-specified MTBSI to uninterruptible loads.
4.3.6 Short-term interrupt load
Loads that can tolerate service interruptions greater than t1 and cannot tolerate service interruptions greater
than t2 are categorized as short-term interrupt loads.
The ZEDS shall on average provide service interruptions longer than t1 in duration no more frequently than
the customer-specified MTBSI to short-term interrupt loads.
8
IEEE Std 1826-2012
4.3.7 Long-term interrupt loads
Loads that can tolerate service interruptions in excess of t2 are categorized as long-term interrupt.
With the exception of exempt loads, ZEDS shall on average provide service interruptions longer than t2 in
duration no more frequently than the customer-specified MTBSI to long-term interrupt loads.
4.3.8 Exempt loads
Exempt loads are a special case of long-term interrupt loads that do not require restoration within t2 for
design purposes. In operation of the power system, an exempt load is treated as long-term interrupt load.
4.4 Power system equipment general requirements
4.4.1 Power interfaces
Power system elements shall have one or more interfaces conforming to the applicable options in Clause 6.
For input interfaces, if multiple inputs are provided, the transition of supplied power from one interface to
another interface shall not result in an interruption of power to loads provided power from the power
system element.
4.4.2 Control power
Control power is used to operate the embedded control system, communicate with external communication
networks, operate the bus isolation devices or switches, and operate other ancillary components required by
the bus interface power conditioner.
Either control power for the power system shall be uninterruptible or each embedded control system shall
have built-in energy storage to enable continued operation upon loss of control power as required by the
application. If not otherwise specified, the default minimum time for continued operation shall be 30 min.
Control power can be provided by an external power connection or derived from the bus interface.
4.4.3 Inrush current
Power system elements shall limit the inrush current upon startup to be less than the values specified. This
function shall be performed automatically without operator intervention at startup.
4.4.4 Isolation devices
Power system elements shall be able to control and select the on/off status of the isolation devices or
switches for power interfaces to the equipment.
4.4.5 Power converters
Unless otherwise specified, the design of power conversion equipment shall comply with IEEE Std 1662.
9
IEEE Std 1826-2012
Power converters shall provide:
 Galvanic isolation between the input and output

 Current limiting
 Time-limited current withstanding capability
 Catastrophic failure due to overcurrent events prevention
 Maintenance lock-out or bypass
 Load break capability at input and output
 Self-monitoring and protection
 Internal energy discharge in accordance with applicable safety regulations
Power converters may be required to provide bidirectional power flow.
4.4.6 Energy storage
4.4.6.1 Float
Energy storage shall be capable of remaining in a float mode when it is connected to the in-zone
distribution bus without drawing or supplying appreciable power until commanded to transition to another
mode or until pre-established criteria are met to transition to another mode.
4.4.6.2 Discharge
Energy storage shall be able to supply power when commanded to do so or when pre-established criteria
are met for as long as its internal energy supply is available.
4.4.6.3 Bus voltage support
When energy storage is allowed or commanded to be in bus voltage support mode, the energy storage shall
export power to raise the interface bus voltage to a minimum voltage setpoint and import power to lower
the interface bus voltage to a maximum voltage setpoint. The desired interface bus voltage setpoints shall
be adjustable. The bus voltage support function is similar to the droop function used in generators where
more power is supplied when the interface bus voltage is low. This function shall supply sufficient power
up to the energy storage power and energy ratings to raise and maintain the interface bus voltage, and
frequency if applicable, as specified in IEEE Std 1662.
4.4.6.4 Charge
Energy storage shall be capable of charging and maintaining a commanded energy level (up to the rated
level) by drawing power from the in-zone distribution bus when commanded to do so or when pre-
established criteria are met.
The rate of charge power or charge current shall be controllable by the energy storage to meet the specified
power charge or current limit setpoint. This function allows the energy storage recharge cycle time to be
optimized with respect to overall system power limitations or constraints. The power limit function set
point shall be adjustable between 0% and 100%.
10
IEEE Std 1826-2012
4.5 Architectural principles

The systems interfaces in zonal distribution systems shall be based on the architectural principles in Table 1
that are derived from IEEE Std 2030.
Table 1 —Open zonal architectures principles

Principle Description
The elements of the zone and the ways in which they interrelate shall be clearly defined, published,
Standardization
useful, open, and stable over time.
Openness The zones shall be based on technology that is available on a nondiscriminatory basis.
The standardization of interfaces within the power system shall be organized such that
 The system can be easily customized for particular geographical, application-specific, or
Interoperability business circumstances, but
 Customization does not prevent necessary interactions among elements of the zone to
maximize stability and acceptable system behavior
The zone shall be protected against unauthorized access and interference with normal operation. It
Security
shall consistently implement information privacy and other security policies.
The zone shall not be designed with built-in constraints to extending its capabilities as new
applications are discovered and developed. Toward this goal,
Extensibility  Its data shall be defined and structured according to a common information model
 It shall separate the definition of data from the methods used to deliver it
 Its components shall announce and describe themselves to other components
The use of zones shall be expandable throughout the power system with no inherent limitations on
Scalability
the power system size.
The components of the zone shall have their configuration assessed and managed, faults shall be
Manageability
identified and isolated, and the components shall be otherwise remotely manageable.
The configuration, software, algorithms, and security credentials of the zone shall be capable of
Upgradeability
being upgraded safely and securely with minimal remote site visits.
The zone shall operate at a high level of availability, performance, and reliability. It shall re-route
Integrity communications automatically, operate during power outages, and store data for intervals sufficient
to recover from failure events.
5. Monitoring, information exchange, control, and protection interfaces
5.1 Introduction
The overall control of ZEDS is achieved by arranging elemental control functions to produce a desired
control. This applies within a power electronics converter and at its local system control as well as at the
zonal and multizone control levels (see Figure 3). The interfaces shall accommodate at least three operating
control states:
 Centralized: The central control system provides commands to the entire system in what is
effectively a master-slave configuration between the central system and distributed devices.
 Distributed: Control is accomplished with independent controls communicating with one another.
This strategy uses intelligent devices that are strategically located to detect the conditions and
initiate the required actions.
 Autonomous: Control is accomplished with independent controls without communication with
other devices.
The interfaces shall accommodate the timing of the control architecture in IEEE Std 1676. Figure 3
indicates example timings that correspond to control layers that are higher in the control hierarchy than the
local device control layers of a power electronic converter that implement faster functionality, such as
protection. The timings in Figure 3 do not apply to protection.
11
IEEE Std 1826-2012
Figure 3 — Control logic block diagram

In order to partition a zonal control system and, subsequently, to define interfaces between those partitions,
it is necessary to determine the control functions of the system. A basic description and criteria for
establishing the contents and boundary of each zonal control layer follows.
5.2 Functionality
The three functional layers are multizone control, zonal control, and in-zone control.
5.2.1 Multizone control
Multizone control is hierarchically the highest layer of control. When multizone control is operational, the
layer below (the zonal control layer) shall respond appropriately to all commands. All functions involved in
the operation of the overall system mission and the allocation of duties to each zone or to a group of zones
supporting that mission shall belong to the multizone control layer. The multizone control layer shall
include human-machine interfaces (HMIs).
For multizone layer controllers, the following control functionality shall be required at minimum:
 Determine and set the operating state of a zone

 Coordinate zones, when applicable
 Receive health/status from, and provide control commands to, zonal level control
 Provide an HMI
12
IEEE Std 1826-2012
5.2.2 Zonal control
Zonal control is hierarchically the next layer of control. When zonal control is operational, the layer below
(the in-zone control layer) shall respond appropriately to all commands. All functions involved in the
determination of the zone mission and the method of coordination of in-zone controls shall belong to this
layer. Management of all energy at the layer boundaries shall be performed within the zonal control layer.
This layer shall include HMIs to support coordination and protection functions.
Zonal layer controllers shall be required, at minimum, to provide the following control functionality:
 Control of energy flow at the boundary of a zone

 Health/status to, and receive control commands from, overall system level control
 Coordination for fault detection, isolation, and reconfiguration
 Inter-zonal coordination, when applicable
 An HMI that provides a means for the operator to handle each type of alert and to review alert
status for all equipment that manages the zonal boundary
5.2.3 In-zone control
The in-zone control layer shall manage the power electronic equipment for zonal sources, zonal loads, and
energy conversion. All functions involved in performing the zone mission and the duties of the power
electronics systems shall belong to this layer. This layer may also include HMIs.
In-zone layer controllers shall be required, at minimum to provide the following control functionality:
 Autonomous control of itself and equipment served

 Health/status to and receive control commands from zonal level control
 Autonomous fault detection, isolation, and reconfiguration coordinated with a zonal controller
 Power flow management in accordance with allocations provided by zonal control
 An HMI that provides a means for the operator to handle each type of alert and to review alert
status for itself and equipment served
 Built-in test capability
 Changing load conditions response.
When the in-zone control layer loses communications with the zonal control layer, the in-zone control layer
shall operate autonomously.
5.3 Interfaces
Each boundary between the functional layers of control shall contain interfaces that transport control,
monitoring and protection information between the respective layers.
The communication interfaces described in IEC 61850 shall be followed unless otherwise specified.
5.3.1 Multizone system interface requirements
The multizone system control layer shall provide digital communication links to numerous zonal layer
control systems and, if applicable, to other multizone system control layers. The communication links shall
13
IEEE Std 1826-2012
transmit status information to and shall receive commands from the zonal layer control and protection
system.
The data exchange across the digital communication link between multizone system layer and zonal layer
controllers shall include at a minimum:
 Data to define the mission of a zone

 Status information for coordination of zones
 Receive health/status from and provide control commands to zonal level control
 Data used by an HMI that provides a means for the operator to handle each type of alert and to
review alert status for the zones as a whole
5.3.2 Zonal interface requirements
The zonal layer control systems shall provide a digital communication link to other supervisory control
systems located in or out of the zone. The communication link shall transmit status information to and shall
receive commands from the multizone control layer. It shall provide commands to the power converters at
the zonal boundary and to the system in the in-zone control layer.
The zonal control interface shall provide the capability for a control panel interface or HMI. The HMI shall
display at a minimum the following data items:
 Operating mode
 Open or closed status of isolation switches
 Power flow at the zone boundaries
 Voltages at the zone electrical interfaces
 Currents at the zone electrical interfaces
 Input frequency and phase (for ac power sources)
 Control and regulation set-points
 Operating status of zone interface converters
 Environmental parameters of the zone interface power converters
 Operating status of zonal energy storage and generation
 Other parameters that are specific to the zone power equipment
The HMI shall be capable of implementing the following commands:
 Transition between control modes

 Transition between local and remote modes of control
 Manual control of isolating switches
 Adjustment of control and regulation set-points
5.3.3 In-zone interface requirements
In-zone layer control systems shall provide a digital communication link to the zonal control layer. The
communication link shall transmit control and monitoring information to and shall receive commands from
14
IEEE Std 1826-2012
the zonal control layer. Controllers within the in-zone layer shall receive control and monitoring
information and shall provide control commands to power converters within the zone except those power
converters that are part of external-to-bus conversion, as shown in Figure 2 and Figure 3.
5.3.4 Equipment emergency shutoff interfaces
In-zone electrical system equipment shall have emergency shutoff interfaces. At a minimum, the following
interfaces shall be provided:
 A pushbutton mechanical switch accessible to operating personnel

 Through device HMI
 Command shutdown initiated by the embedded controller or external communication link
5.3.5 Special Interfaces
There may be special interfaces needed that are not addressed in this document. For example, phasor
measurement units require very fast and precise time synchronization systems, or some emergency
response power systems require hardwired fast interlocking. For these special interfaces, verification and
validation (V&V) activities of Clause 7 shall be established based on applicable IEC and IEEE standards.
6. Electric power interfaces
6.1 Introduction
Electric power interfaces shall be defined as:
 Interfaces at the zonal boundary with external power systems and other zone(s)
 Interfaces with the in-zone distribution bus
 Interfaces between bus-to-internal conversion and distribution panels
 Interfaces with end-use devices
6.2 Power interface standards
The subsections below and the references cited therein are concerned primarily with the electrical aspects
of the power interface, such as voltage and frequency. Equally important to the electric system designer are
the physical aspects of the power interface. These aspects include number of poles, location of entry point,
system grounding considerations, voltage, conductor configuration, system configuration, zone criticality,
power quality, QoS, environmental impact and requirements, environment, safety, etc. These aspects of the
power interface must be considered for any of the different interfaces discussed below.
The system designer shall comply with the regulatory and contractual requirements to meet the specific
application.
15
IEEE Std 1826-2012
6.2.1 50/60-Hz medium-voltage interface standards
The 50/60 Hz, medium-voltage power interface standards shall be based on IEC 60038:2009.
The medium-voltage dc input power interface standards shall be based on IEC 60038:2009 or IEEE Std
1709-2010.
6.2.2 Low-voltage ac interface standards
The low-voltage ac power interface standards shall be based on IEC 60038:2009.
6.2.3 Low-voltage dc interface standards
The low-voltage option shall provide power based on IEC 60038:2009.
6.3 Electrical power interface ratings
6.3.1 Power
The rating of each electrical power interface shall comply with applicable standards for its components and
shall be equal to or greater than the highest anticipated power flow through the interface. For ac systems,
the rating shall be stated in volt-amps (kVA or MVA).
6.3.2 Operating voltage tolerances
The voltage at any power interface within the in-zone electrical distribution system shall remain within the
envelope shown in Figure 4 unless otherwise specified. In-zone electrical distribution system equipment
shall operate satisfactorily and without damage with voltages within the specified envelope. The specified
envelope shall account for lightning withstand level, switching surge withstand level, temporary
overvoltages, continuous overvoltages and undervoltages, and fault clearing. Figure 4 is adopted from
IEEE Std 1709-2010 and shall be applied to both dc and ac systems. While IEEE Std 1709-2010 applies
only to dc systems, Figure 4 is extended to ac systems to account for the characteristics of power
electronics.
16
IEEE Std 1826-2012
3.0
2.6
2.0
PU
1.0
0.75
t1 = reconfiguration time
0.0
Tf
10-6 10-5 10-4 10-3 10-2 10-1 10+0 10+1
Time (seconds)
Figure 4 — Voltage tolerances worst-case envelope (from IEEE Std 1709-2010)
6.3.3 Reconfiguration time
Reconfiguration time, t1, shall be no greater than 10-2 s.
6.3.4 Rated continuous current
The rated continuous current of each electrical power interface shall comply with applicable standards for
its components and shall be equal to or greater than the highest anticipated current through the interface.
6.3.5 Rated short-time withstand current
The rated short-time withstands current of the power interface shall be greater than or equal to the
maximum expected short-circuit current. Equipment shall withstand its rated short-time withstand current
for a time period equal to the reconfiguration time, t1.
6.4 Power interfaces at the zonal boundary
6.4.1 Bidirectional interfaces at the zonal boundary
External-to-bus conversion shall normally accommodate bidirectional power flow at the zonal boundary.
17
IEEE Std 1826-2012
Converters shall implement a current-limiting feature; these ratings shall consider emergency, overload,
short-circuit, charge, and discharge conditions.
6.4.2 Unidirectional interfaces at the zonal boundary
Zones without energy storage or in-zone generation may use unidirectional power flow at the zonal
boundary.
6.5 Power interfaces for the in-zone distribution bus
6.5.1 Bidirectional interfaces to the in-zone distribution bus
Power conversion equipment connected to the in-zone distribution bus shall normally accommodate
bidirectional power flow at external-to-bus conversion and in-zone energy storage interfaces and some in-
zone generation and bus-to-internal conversion interfaces.
6.5.2 Unidirectional interfaces to the in-zone distribution bus
Some interfaces may only require unidirectional power flow, e.g., in-zone generation, bus-to-internal
conversion, etc. Zones without energy storage or in-zone generation may use unidirectional power flow for
external-to-bus conversion.
7. Verification and validation (V&V)
7.1 General
The V&V process determines whether the power electronics open system interfaces in zonal power systems
conform to international and IEEE standards and satisfy its intended use and the electrical power system
requirements needs. The determination includes assessment, analysis, evaluation, review, inspection, and
conformance testing.
This standard defines the V&V processes to conform to life cycle process standards such as ISO/IEC/IEEE
Std 15288-2008 [B18], ISO/IEC 26702 (IEEE Std 1220 TM -2011) [B17], and ISO/IEC 9646 [B16], as well
as the entire family of IEEE system engineering standards. V&V shall be performed at the level of the
system, software element, hardware element, or on any combination of these for the initial system
development and any modernization efforts.
The verification process reviews the design in detail to establish to a reasonable degree of certainty that the
design meets the customer’s performance requirements (plus regulatory requirements). Verification
generally involves the review of design documentation. Designs reviews are generally part of the
verification activities.
The validation process reviews the delivered hardware and software in detail to establish to a reasonable
degree of certainty that they meet the customer’s performance requirements (plus regulatory requirements).
Validation generally involves the review of test results. In many cases, if verification were “perfect,” then
validation would consist of ensuring the end product conforms to the design. In reality, design defects are
often not discovered until validation efforts are conducted on the first units. Once the design is finalized
18
IEEE Std 1826-2012
after prototype testing, and the product is in serial production, validation is often equivalent to conformance
testing. In power systems, however, the products generally are unique to some degree for each customer;
hence, conformance testing is generally not sufficient.
Every power electronics interface in zonal power systems shall be subjected to the verification and
validation plan (VVP) that establishes minimum criteria for V&V processes, activities, and tasks. The VVP
shall include all relevant activities as approved by the acquiring organization in the following subclauses,
which are adapted from IEEE Std 1012-2012.
7.2 Activity: Concept Verification
The objectives of Concept Verification are to verify that all system requirements assigned to the
configuration items are addressed in their design and to verify that the selected hardware and software
concepts satisfy the system needs (i.e., performance, schedule, and cost). During the concept process,
different concepts are investigated, and trade studies are conducted on each concept before a final concept
is selected. Models and prototypes may be constructed to conduct these trade studies in conjunction with
simulations and analytic analyses. Concept Verification shall be performed as specified in the VVP using
relevant tasks (see Table 2).
Table 2 —Concept Verification

V&V tasks Required inputs Required outputs
1) Concept Documentation Evaluation Concept documentation Task report(s) –
a) Verify that the concept documentation satisfies user needs Concept
and is consistent with acquisition needs. System architectural design documentation
b) Verify constraints of interfacing systems and constraints or evaluation
limitations of proposed approach. Supplier development plans
c) Analyze system requirements and verify that the following and schedules Anomaly report(s)
satisfy user needs
i) System functions User needs
Acquisition needs
ii) End-to-end system performance
iii) Feasibility and testability of the functional requirements
iv) System architecture design
v) Operation and maintenance requirements and
environments
vi) Migration requirements from an existing system where
applicable
2) Criticality Analysis Concept documentation Task report(s) –
a) Document the integrity level assigned to individual (system requirements) Criticality analysis
components (e.g., requirements, detailed functions,
hardware components, subsystems, or other partitions). For Developer integrity level Anomaly report(s)
verification planning purposes, the system shall be assigned assignments
the same integrity level as the highest level assigned to any
individual element.
b) Verify whether any component influences individual
components assigned a higher integrity level, and if such
conditions exist, then assign that component the same
higher integrity level.
3) Interfaces Requirements Allocation Analysis: Verify the User needs Task report(s) –
correctness, accuracy, and completeness of the concept Interfaces
requirement allocation to power and user interfaces against user Concept documentation requirements
needs. allocation analysis
a) Correctness: Verify that performance requirements (e.g.,
timing, response time, and throughput) satisfy user needs. Anomaly report(s)
b) Accuracy
c) Verify that the internal and external interfaces specify the
19
IEEE Std 1826-2012
Table 2—Concept Verification (continued)

data formats, interface protocols, frequency of data
exchange at each interface, and other key performance
requirements to demonstrate satisfaction of user
requirements.
d) Completeness
i) Verify that application specific requirements such as
functional diversity, fault detection, fault isolation, and
diagnostic and error recovery satisfy user needs.
ii) Verify that the user’s maintenance requirements for the
system are completely specified.
iii) Verify that the migration from existing system and
replacement of the system satisfy user needs.
4) Traceability Analysis Concept documentation Task report(s) –
a) Identify all system requirements. Traceability analysis
b) Verify that these system requirements are traceable to
acquisition needs. Anomaly report(s)
c) Start the requirements traceability analysis with system
requirements.
5) Hazard Analysis Concept documentation Task report(s) –
a) Analyze the potential hazards to and from the conceptual Hazard analysis
system. The analysis shall
i) Identify the potential system hazards Anomaly report(s)
ii) Assess the consequences of each hazard
iii) Assess the probability of each hazard
iv) Identify mitigation strategies for each hazard
6) Security Analysis Concept documentation Task report(s) –
a) Review the system owner’s definition of an acceptable Preliminary threat and risk Security analysis
level of security risk. assessment (TRA)
b) Analyze the system concept from a security perspective to Anomaly report(s)
minimize the potential security risks with respect to
confidentiality (disclosure of sensitive information/data),
integrity (modification of information/data), availability
(withholding of information or services), and
accountability (attributing actions to an individual/
process) have been identified. Include an assessment of
the sensitivity of the information/data to be processed.
c) Analyze security risks introduced by the system itself as
well as those associated with the environment with which
the system interfaces.
7) Risk Analysis Concept documentation Task report(s) –
a) Identify the technical and management risks. Supplier development plans Risk analysis
b) Provide recommendations to eliminate, reduce or mitigate and schedules
the risks. Hazard analysis report Anomaly report(s)
Security analysis
Verification task results
7.3 Activity: Requirements Verification
The objectives of the Requirements Verification are:
a) Verify that the requirements correctly, completely, and accurately satisfy the system requirements
allocated to the configuration item.
b) Verify that the requirements, in total, satisfy the system needs.
20
IEEE Std 1826-2012
Any constraints or limitations imposed by the requirements on the system performance are identified, and
the system acquirer has verified that these limitations or constraints are acceptable. Requirements
Verification shall be performed as specified in the VVP using relevant tasks (see Table 3).
Table 3 —Requirements Verification

1) Requirements Evaluation: Evaluate the requirements (e.g., Concept Task report(s) –
functional, capability, interface, qualification, safety, security, documentation Interfaces
human factors, data definitions, user documentation, installation requirements
and acceptance, user operation, and user maintenance) of the SRS SRS evaluation
and IRS for correctness, consistency, completeness, accuracy,
readability, and testability. IRS Anomaly report(s)
2) Interfaces Analysis: Verify that the requirements for power Concept Task report(s) –
electronics hardware interfaces with software, user, operator, other documentation Interfaces
hardware, and other systems are correct, consistent, complete, SRS requirements
accurate, and testable. IRS specification
Anomaly report(s)
3) Interfaces Qualification Test Plan Development Concept V&V interfaces
a) Plan interfaces Qualification Testing to validate power documentation qualification test plan
electronics hardware requirements (e.g., static, transient, or System
dynamic loads), interface compatibility, electromagnetic requirements Anomaly report(s)
compatibility, electromagnetic interference, thermal,
mechanical, electrical, acoustic, environmental (humidity, HRS
water, saltwater, acceleration, vibration, shock, pressure).
b) Plan tracing of system requirements to test designs, cases, IRS
procedures, and results.
c) Plan documentation of test designs, cases, procedures, and User documentation
results.
d) The interfaces qualification test plan shall address the Developer’s
following: hardware
qualification test
i) Conformance to all system requirements (e.g., functional,
plan
performance, security, operation, and maintenance) as
complete hardware end items in the system environment
ii) Adequacy of user documentation (e.g., training materials,
procedural changes)
iii) Performance at boundaries (e.g., data, interfaces) and
under stress conditions
e) Verify that the interfaces qualification test plan satisfies the
following criteria:
i) Conformance to project-defined test document purpose,
format, and content
ii) Test coverage of system requirements
f) Verify that the qualification test plan satisfies the following
criteria:
i) Appropriateness of test methods and standards used
ii) Conformance to expected results
iii) Feasibility of system Qualification Testing
iv) Feasibility and testability of operation and maintenance
requirements.
4) Interfaces Acceptance Test Plan Concept V&V interfaces
a) Plan interfaces Acceptance Testing to verify that the documentation acceptance test plan
interfaces correctly implement system and power electronics
hardware requirements [e.g., static, transient, or dynamic HRS Anomaly report(s)
loads, interface compatibility, electromagnetic compatibility,
electromagnetic interference, thermal, mechanical, electrical, IRS
acoustic, environmental (humidity, water, saltwater, etc.),
acceleration, vibration, shock, pressure)] in an operational User documentation
environment.
21
IEEE Std 1826-2012
Table 3—Requirements Verification (continued)

b) Plan tracing of acceptance test requirements to test design, Interfaces
cases, procedures, and execution results. acceptance test plan
c) Plan documentation of test tasks and results.
d) The interfaces acceptance test plan shall address the
following:
i) Conformance to acceptance requirements in the operational
environment
ii)Adequacy of user documentation
e) Verify that the interfaces acceptance test plan satisfies the
following criteria:
i) Conforms to project-defined test document purpose,
format, and content
ii) Provides complete test coverage of acceptance
requirements
iii) Measures conformance to expected results
iv) Demonstrates feasibility of operation and maintenance
(e.g., capability to be operated and maintained in
accordance with user needs)
5) Hazard Analysis HRS Task report(s) –
a) Determine interfaces contributions to system hazards. The IRS Hazard analysis
hazard analysis shall: Hazard analysis
i) Identify the interfaces requirements that contribute to each report Anomaly report(s)
system hazard.
ii)Verify that the design addresses, controls, or mitigates each
hazard.
7.4 Activity: Design Verification
Design Verification will assist in ensuring that the design solution satisfies the system performance, safety,
and reliability requirements and that no unintended or undesired consequences are introduced into the
system. Design Verification shall be performed as specified in the VVP using relevant tasks (see Table 4).
Table 4 —Design Verification

1) Traceability Analysis: Trace design elements to requirements HRS Task report(s) –
(HRS and IRS), and requirements to design elements. Analyze HDD Traceability analysis
relationships for correctness, consistency, and completeness. IRS Anomaly report(s)
IDD
2) Design Evaluation: Evaluate the design elements (HDD and IRS Task report(s) –
IDD) for correctness, consistency, completeness, accuracy, Design standards Anomaly reports
readability, testability, and design margins.
3) Interface Analysis: Verify that the hardware design interfaces System requirements Task report(s) –
with software, user, operator, other hardware, and other systems for HRS Interfaces design
correctness, consistency, completeness, accuracy, and testability. IRS document
Anomaly reports
4) Criticality Analysis: Review and update the existing criticality Criticality task report Task report(s) –
analysis results from the prior Criticality Task Report using the HDD Criticality analysis
HDD and IDD. IDD Anomaly report(s)
22
IEEE Std 1826-2012
Table 4—Design Verification (continued)

5) Interfaces Component Test Plan Assessment Hardware drawings Task report(s) –
a) Verify that the developer’s interfaces component test plan Integration test
conforms to project-defined test document purpose, format, Hardware component plan assessment
and content. test plan
b) Verify that the test plan satisfies the following criteria: Anomaly report(s)
i) Traceable to the requirements and design IRS
ii) External consistency with the requirements and design
iii) Internal consistency between unit requirements
iv) Test coverage of units
v) Feasibility of integration and testing
vi) Feasibility of operation and maintenance (e.g., capability to
be operated and maintained in accordance with user needs)
6) Integration Test Plan Assessment HRS Task report(s) –
a) Verify that the developer’s hardware integration test plan IRS Integration test plan
conforms to project-defined test document purpose, format, HDD assessment
and content IDD
b) Verify that the developer’s hardware integration test plan Hardware drawings Anomaly report(s)
satisfies the following criteria: Integration test plan
i) Traceable to the system requirements
ii) External consistency with the system requirements
iii) Internal consistency
iv) Test coverage of the hardware requirements
v) Appropriateness of test standards and methods
vi) Measures conformance to expected results
vii) Feasibility of hardware Qualification Testing
viii) Feasibility of operation and maintenance (e.g., capability
to be operated and maintained in accordance with user
needs)
7) Test Design Assessment HDD, IDD Task report(s) –
a) Verify that the developer’s test designs for power electronics Hardware drawings Component test
hardware component testing conform to project-defined test User documentation design assessment
document purpose, format, and content. Test plans & designs Anomaly report(s)
b) Verify that the developer’s hardware component test designs
satisfy the criteria in Design Verification Activity Task 5.
8) Integration Test Design Assessment HDD Task report(s) –
a) Verify that the developer’s test designs for power electronics Hardware drawings Integration test
Integration Testing conform to project-defined test document User documentation design assessment
purpose, format and content. Test designs
b) Verify that the developer’s hardware integration test designs Anomaly report(s)
satisfy the criteria in Design Verification Activity Task 6.
9) Qualification Test Design Assessment HDD Task report(s) –
a) Design tests for qualification testing. IDD Validation hardware
b) Continue tracing required by the verification qualification test Hardware drawings qualification test
plan. Verify that the verification qualification test designs User documentation design(s)
conform to project-defined test document purpose, format, and Test designs
content. Anomaly report(s)
c) Verify that the verification qualification test designs satisfy the
criteria in Design Verification Activity Task 5; IEEE Std
1547.1-2005, Clause 5, Clause 6, and Clause 7; IEEE Std 1662,
9.1 and 9.2; and IEEE Std 1709-2010, 8.2 and 8.5.
23
IEEE Std 1826-2012
Table 4—Design Verification (continued)

10) Hardware Acceptance Test Design Assessment HDD Task report(s) –
a) Design tests for validation hardware acceptance testing. IDD Validation hardware
b) Continue tracing required by the validation hardware Hardware drawings acceptance test
acceptance test plan. Verify that the validation power User documentation design(s)
electronics acceptance test designs conform to project-defined Test designs
test document purpose, format, and content. Anomaly report(s)
c) Verify that the validation power electronics acceptance test
designs satisfy criteria in Design Verification Activity Task 6;
IEEE Std 1547.1-2005, Clause 5, Clause 6, and Clause 7;
IEEE Std 1662, 9.1 and 9.2; and IEEE Std 1709-2010, 8.2 and
8.5.
11) Hazard Analysis HDD, IDD Task report(s) –
a) Verify the design elements that implement critical Hardware drawings Hazard analysis
requirements introduce no new hazards. Hazard analysis Anomaly report(s)
b) Update the hazard analysis. report
7.5 Activity: First Article V&V
The objectives of First Article V&V are to confirm that:
a) The first fabricated article complies with the design

b) There are no design defects
c) Each fabricated component satisfies the overall system performance, safety, and reliability
requirements
This activity shall be performed as specified in the VVP using relevant tasks (see Table 5).
Table 5 —First Article V&V

V&V Tasks Required Inputs Required Outputs
1) Traceability Analysis HDD, IDD Task report(s) –
a) Trace the fabricated component(s) to the design, and the design Hardware drawings Traceability analysis
to the fabricated component(s). Component
b) Analyze identified relationships for correctness, consistency, documentation Anomaly report(s)
and completeness.
2) Fabricated Component Documentation Evaluation: Evaluate the Component Task report(s) –
fabricated component documentation for correctness, consistency, documentation Component
completeness, accuracy, and readability. HDD, IDD documentation
Hardware drawings evaluation
User documentation Anomaly report(s)
3) Interface Analysis: Validate the fabricated component interfaces Concept Documents Task report(s) –
with software, user, operator, other hardware, and other systems for System requirements Interface analysis
correctness, consistency, completeness, accuracy, and testability. HDD, IDD
Hardware drawings Anomaly report(s)
User documentation
24
IEEE Std 1826-2012
Table 5—First Article V&V (continued)

4) Criticality Analysis: Review and update the existing criticality Criticality Task Report Task report(s) –
analysis results from the prior criticality task report using the Component Criticality analysis
fabricated component and its associated documentation. documentation
Anomaly report(s)
5) Power Electronics Component Test Case Assessment HRS, IRS, HDD, IDD Task report(s) –
a) Verify that the developer’s hardware component test cases Hardware drawings Hardware
conform to project-defined test document purpose, format, and User documentation component test case
content. Hardware component assessment
b) Verify that the developer’s hardware component test cases test cases
satisfy the criteria in Design Verification Activity Task 5; Anomaly report(s)
IEEE Std 1547.1-2005, Clause 5, Clause 6, and Clause 7; IEEE
Std 1662, 9.1 and 9.2; and IEEE Std 1709-2010, 8.2 and 8.5.
6) Power Electronics Integration Test Case Assessment HRS, IRS, HDD, IDD Task report(s) –
a) Verify that the developer’s hardware integration test cases Hardware drawings Hardware
conform to project-defined test document purpose, format, and User documentation integration test case
content. Hardware integration assessment
b) Verify that the developer’s hardware integration test cases test cases
satisfy the criteria in Design Verification Activity Task 6; Anomaly report(s)
IEEE Std 1547.1-2005, Clause 7 and Clause 8; IEEE Std 1662,
7) Power Electronics Qualification Test Case Validation HRS, IRS, HDD, IDD Task repport(s) –
a) Develop test cases for validation power electronics Hardware drawings Validation hardware
qualification Testing. User documentation qualification test
b) Continue tracing required by the validation hardware Hardware qualification cases
qualification test plan. test cases
c) Verify that the validation power electronics qualification test Anomaly report(s)
cases conform to project-defined test document purpose,
format, and content.
d) Verify that the validation hardware qualification test cases
satisfy the criteria in Design Verification Activity Task 5;
IEEE Std 1547.1-2005, Clause 7 and Clause 8; IEEE Std 1662,
8) Power Electronics Acceptance Test Case Validation HRS, IRS, HDD, IDD Task report(s) –
a) Develop test cases for validation power electronics Acceptance Hardware drawings Validation hardware
Testing. User documentation acceptance test cases
b) Continue tracing required by the validation hardware Hardware acceptance
acceptance test plan. test cases Anomaly report(s)
c) Verify that the validation power electronics acceptance test
cases conform to project-defined test document purpose,
d) Verify that the validation power electronics acceptance test
cases satisfy the criteria in Design Verification Activity Task 6;
IEEE Std 1547.1-2005, Clause 5, Clause 6, and Clause 7; IEEE
Std 1662, 9.1 and 9.2; and IEEE Std 1709-2010, 8.2 and 8.5.
9) Hardware Component Test Procedures Assessment HRS, IRS, HDD, IDD Task report(s) –
a) Verify that the developer’s hardware component test Hardware drawings Hardware
procedures conform to project-defined test document purpose, User documentation component test
format, and content. Component test cases procedures
b) Verify that the developer’s hardware component test Component test assessment
procedures satisfy the criteria in Design Verification Activity procedures
Task 5; IEEE Std 1547.1-2005, Clause 5, Clause 6, and Clause Anomaly report(s)
7; IEEE Std 1662, 9.1 and 9.2; and IEEE Std 1709-2010, 8.2
and 8.5.
25
IEEE Std 1826-2012
Table 5—First Article V&V (continued)

10) Hardware Integration Test Procedure Assessment HRS, IRS, HDD, IDD Task report(s) –
a) Verify that the developer’s hardware integration test Hardware drawings Hardware
procedures conform to project-defined test document purpose, User documentation integration test
format, and content Hardware integration procedures
b) Verify that the developer’s hardware integration test test cases assessment
procedures satisfy the criteria in Design Verification Activity Hardware integration
Task 6; IEEE Std 1547.1-2005, Clause 5, Clause 6, and test procedures Anomaly report(s)
Clause 7; IEEE Std 1662, 9.1 and 9.2; and IEEE Std 1709-
2010, 8.2 and 8.5.
11) Hardware Qualification Test Procedure Validation HRS, IRS, HDD, IDD Task report(s) –
a) Develop test procedures for validation hardware qualification Hardware drawing V&V hardware
testing. User documentation qualification test
b) Continue tracing required by the validation hardware Hardware qualification procedures
qualification test plan. test cases
c) Verify that the validation hardware qualification test Hardware qualification Anomaly report(s)
procedures conform to project-defined test document purpose, test procedures
d) Verify that the validation hardware qualification test
procedures satisfy the criteria in Design Verification Activity
Task 5; IEEE Std 1547.1-2005, Clause 5, Clause 6, and
Clause 7; IEEE Std 1662, 9.1 and 9.2; and IEEE Std 1709-
2010, 8.2 and 8.5.
12) Hardware Component Test Execution Assessment: Use the Component Task report(s) –
developer’s hardware component test results to validate that the documentation Hardware
hardware component satisfies the test acceptance criteria. HDD, IDD component test
Hardware drawings execution
Component test plans assessment
Hardware component
test procedures Anomaly report(s)
Hardware component
test results
13) Hazard Analysis Component Task report(s) –
a) Validate that the fabricated component correctly implements documentation Hazard analysis
the critical requirements and introduces no new hazards. HDD, IDD
b) Update the hazard analysis. Hardware drawings Anomaly report(s)
Hazard analysis report
14) Security Analysis: Validate that the fabricated component is Component Task report(s) –
completed in accordance with the security features of the system documentation Risk analysis
design and that the fabricated component does not introduce new HDD, IDD
security risks. Hardware drawings Anomaly report(s)
7.6 Activity: Integration Testing
Integration Testing occurs in parallel with hardware fabrication. As fabrication progresses, hardware parts
are integrated into components, components are integrated into the hardware elements, and a series of tests
are conducted to validate conformance with requirements. Integration Testing shall be performed as
specified in the VVP using relevant tasks (see Table 6).
26
IEEE Std 1826-2012
Table 6 —Integration Testing

1) Traceability Analysis: Analyze relationships in the validation test V&V test plans Task report(s) –
plans, designs, cases, and procedures for correctness and V&V test designs Traceability analysis
completeness. The task criteria are: V&V test
a) Correctness: Verify that there is a valid relationship between the procedures Anomaly report(s)
validation test plans, designs, cases, and procedures.
b) Completeness: Verify that all validation test procedures are
traceable to the validation test plans.
2) Hardware Integration Test Execution Assessment: Use the Component Task report(s) –
developer’s hardware integration test results to validate that the specifications Hardware integration
hardware satisfies the test acceptance criteria. Hardware test execution
integration test plan assessment
Hardware Anomaly report(s)
integration test
procedures
Hardware
integration test
results
a) Verify that the test instrumentation does not introduce new specifications Hazard analysis
hazards. Test results
b) Update the hazard analysis. Hazard analysis Anomaly report(s)
report
4) Security Analysis: Validate that the implemented system does not Component Task report(s) –
increase security risk. specifications Security analysis
Anomaly report(s)
7.7 Activity: Qualification Testing
On contractually agreed terms, a qualified, and preferably certified per ANSI/NETA ATS-2009 [B2], third
party shall perform Qualification Testing to confirm that contractual requirements are met and no
unintended or undesired consequences are created by equipment under test. Qualification Testing shall be
performed as specified in the VVP using relevant tasks (see Table 7).
27
IEEE Std 1826-2012
Table 7 —Qualification Testing

1) Traceability Analysis: Analyze relationships in the validation test Validation test plans Task report(s) –
plans, designs, cases, and procedures for correctness and Validation test Traceability analysis
completeness. The task criteria are: designs
a) Correctness Validation test Anomaly report(s)
Verify that there is a valid relationship between the validation procedures
test plans, designs, cases, and procedures.
b) Completeness
Verify that all validation test procedures are traceable to the
validation test plans.
2) Hardware Integration Test Execution Assessment Hardware component Task report(s) –
a) Perform validation hardware qualification testing. specifications Validation hardware
b) Analyze test results to validate that the hardware satisfies the Hardware qualification test
system requirements. qualification test plan results
c) Validate that the test results trace to test criteria established by Hardware
the test traceability in the test planning documents. qualification test Anomaly report(s)
d) Document the results as required by the validation hardware procedures
qualification test plan. Hardware
qualification test
e) Use the validation hardware qualification test results to validate
results
that the hardware satisfies the test acceptance criteria.
f) Document discrepancies between actual and expected test
results.
b) Update the hazard analysis. Hazard analysis Anomaly report(s)
report
4) Security Analysis: Verify that the implemented system does not Component Task report(s) –
increase security risk specifications Security analysis
Anomaly report(s)
7.8 Activity: Commissioning Testing
Commissioning testing supports the system installation activities and assists in ensuring that the hardware
and software are capable of delivering their required services. Commissioning testing shall be performed as
specified in the VVP using relevant tasks (see Table 8). If contractually agreed, Integration and
Commissioning Testing could be combined.
28
IEEE Std 1826-2012
Table 8 —Commissioning Testing

1) Installation Configuration Audit Installation package (user Task report(s) –
a) Verify that all products required to correctly install and documentation, HDD, Installation
operate are present in the installation package. IDD, HRS, IRS, hardware configuration audit
b) Verify that all site-dependent parameters or conditions to drawings, concept
verify supplied values are correct. documentation, Anomaly report(s)
installation procedures,
site-specific parameters,
installation tests, and
configuration management
data)
2) Installation Checkout User documentation Task report(s) –
a) Conduct analyses and tests to check that the installed Installation checkout
hardware and software correspond to the hardware and Installation package
software subjected validation. Anomaly report(s)
b) Validate that the hardware initializes, executes, and Hardware acceptance
terminates as specified. procedures
c) Validate the requirements are met for continuous operation
and service during commissioning, including requirements
for user notification.
3) Periodic Interconnection Tests Procedure Validation HDD, IDD Task report(s) –
a) Develop tests procedure for validation periodic Hardware drawings Validation periodic
interconnection testing. Component specifications interconnection tests
b) Continue the tracing required by the validation hardware User documentation procedures
acceptance test plan. Hardware acceptance test
c) Verify that the Validation periodic interconnection tests plan Anomaly report(s)
conform to Clause 7 of IEEE Std 1547.1-2005. Hardware acceptance test
d) Verify that the validation hardware acceptance test procedures
procedures satisfy the criteria in Design Verification
Activity Task 6; IEEE Std 1547.1-2005, Clause 5, Clause 6,
and Clause 7; IEEE Std 1662, 9.1 and 9.2; and IEEE Std
1709-2010, 8.2 and 8.5.
4) Hazard Analysis Installation package Task report(s) –
a) Verify that the installation procedures and installation Hazard analysis
environment does not introduce new hazards. Hazard analysis report
b) Update the hazard analysis. Anomaly report(s)
5) Security Analysis: Validate that the installed hardware does Component specifications Task report(s) –
not introduce new or increased vulnerabilities or security risks to Security analysis
the overall system. Anomaly report(s)
7.9 Activity: Acceptance Testing
Acceptance testing occurs with the hardware working with all other hardware and software in the actual
operating environment. Acceptance testing shall be performed as specified in the VVP using relevant tasks
(see Table 9). Normally, successful completion of Acceptance Testing results with the customer accepting
ownership of the system, but the customer and supplier may agree to a different time and/or method for
acceptance.
29
IEEE Std 1826-2012
Table 9 —Acceptance Testing

1) Traceability Analysis: Analyze relationships in the validation Validation test plans Task report(s) –
test plans, designs, cases, and procedures for correctness and Validation test designs Traceability analysis
completeness. The task criteria are: Validation test
a) Correctness: Verify that there is a valid relationship between procedures Anomaly report(s)
the validation test plans, designs, cases, and procedures..
b) Completeness: Verify that all validation test procedures are
traceable to the validation test plans.
2) Hardware Acceptance Test Procedure Validation HDD, IDD Task report(s) –
a) Develop test procedures for validation hardware acceptance Hardware drawings Validation hardware
testing. Component acceptance test
b) Continue the tracing required by the validation hardware specifications procedures
acceptance test plan. User documentation Anomaly report(s)
c) Verify that the validation hardware acceptance test procedures Hardware acceptance test
conform to project-defined test document purpose, format, and plan
content (e.g., see IEEE Std 829 TM -2008 [B4]). Hardware acceptance test
d) Verify that the validation hardware acceptance test procedures procedures
satisfy the criteria in Design Verification Activity Task 6;
IEEE Std 1547.1-2005, Clause 5, Clause 6, and Clause 7;
IEEE Std 1662, 9.1 and 9.2; and IEEE Std 1709-2010, 8.2 and
8.5.
3) Hardware Acceptance Test Execution Validation Component Task report(s) –
a) Integrity Levels 3 and 4 specifications Validation hardware
i) Perform validation hardware Acceptance Testing. User documentation acceptance test results
ii) Analyze test results to validate that the hardware satisfies Hardware acceptance test
the system requirements. plan Anomaly report(s)
iii) Validate that the test results trace to test criteria established Hardware acceptance test
by the test traceability in the test planning documents. procedures
Hardware acceptance test
iv) Document the results as required by the validation hardware
results
acceptance test plan.
v) Use the validation hardware acceptance test results to
validate that the hardware satisfies the test acceptance
criteria.
vi) Document discrepancies between actual and expected test
results.
b) Update the hazard analysis. Hazard analysis report Anomaly report(s)
5) Security Analysis: Verify that the implemented system does not Component Task report(s) –
increase security risk. specifications Security analysis
Anomaly report(s)
8. Maintenance of open systems interfaces

Maintenance of open systems interfaces shall comply with IEEE Std 3007.2.
30
IEEE Std 1826-2012
Annex A
(informative)
Examples of applications of zonal electrical distribution systems (ZEDS)
A.1 Naval Destroyer ZEDS
Figure A.1—Notional Naval Destroyer ZEDS
Figure A.1 is an example of a power electronics based zonal electrical distribution system (ZEDS). In this
system, the external power system consists of the primary power generation system which produces 4160-
Vac 3-phase 60-Hz power with gas turbine generators. Within each zone, the external power system
interface is 4160-Vac 60-Hz power. The external-to-bus conversion is a transformer rectifier that produces
1000-Vdc power. This 1000-Vdc bus serves as an in-zone distribution bus and also provides power to
adjacent zones. A set of dc-dc converters serves as bus-to-internal conversion devices that either provide dc
power to loads directly or provide power to an inverter to produce 60-Hz power for ac loads. This inverter
and associated switchgear serve functionally as a zonal distribution panel.
31
IEEE Std 1826-2012
A.2 Distributed resources islands in the terrestrial power grid
Figure A.2—Substation island in the terrestrial power grid
Figure A.2, adapted from IEEE Std 1547.4TM, is an example of a ZEDS implemented as a substation island
in the terrestrial power grid. In this system, the external power system consists of the terrestrial power
system. The external power system interface is 60-Hz power 3-phase power. The external-to-bus
conversion devices are the substation step-down transformers. The bus and circuits in Figure A.2 serve as
the in-zone distribution bus. Distributed generators serve as in-zone generation. IEEE Std 1547.4 has
additional examples.
32
IEEE Std 1826-2012
Annex B
(informative)
Bibliography
Bibliographical references are resources that provide additional or helpful material but do not need to be
understood or used to implement this standard. Reference to these resources is made for informational use
only.
[B1] Abbott, J. W.; Levine, A.; and Vasilakos, J., “Modular/Open Systems to Support Ship Acquisition
Strategies,” presented at ASNE Day 2008, June 23–25, 2008, Arlington, VA.
[B2] ANSI/NETA ATS-2009, Standard for Acceptance Testing Specifications for Electrical Power
Equipment and Systems. 7
[B3] IEC 61968, Application Integration at Electric Utilities – System Interfaces for Distribution
Management. 8
[B4] IEEE Std 829TM-2008, IEEE Standard for Software and System Test Documentation. 9,10
[B5] IEEE Std 902TM-1998, IEEE Guide for Maintenance, Operation, and Safety of Industrial and
Commercial Power Systems.
[B6] IEEE Std 946TM, IEEE Recommended Practice for the Design of DC Auxiliary Power Systems for
Generating Stations.
[B7] IEEE Std 1100TM-2005, IEEE Recommended Practice for Powering and Grounding Electronic
Equipment.
[B8] IEEE Std 1409TM, IEEE Guide for Application of Power Electronics for Power Quality Improvement
on Distribution Systems Rated 1 kV through 38 kV.
[B9] IEEE Std 1547.3TM, IEEE Guide for Monitoring, Information Exchange, and Control of Distributed
Resources Interconnected with Electric Power Systems.
[B10] IEEE 1547.6TM, IEEE Recommended Practice For Interconnecting Distributed Resources with
Electric Power Systems Distribution Secondary Networks.
[B11] IEEE Std 3007.1TM, IEEE Recommended Practice for the Operation and Management of Industrial
and Commercial Power Systems.
[B12] IEEE Std 3007.3TM, IEEE Recommended Practice for Electrical Safety in Industrial and Commercial
Power Systems.
[B13] IEEE Std C37.20.1TM, IEEE Standard for Metal-Enclosed Low-Voltage Power Circuit Breaker
Switchgear.
[B14] IEEE Std C37.100TM-2007, IEEE Standard of Common Requirements for High Voltage Power
Switchgear Rated Above 1000 V.
[B15] ISO 15745-1:2003, Industrial Automation Systems and Integration—Open Systems Application
Integration Framework – Part 1: Generic Reference Description. 11
7
ANSI publications are available from the Sales Department, American National Standards Institute, 25 West 43rd Street, 4th Floor,
New York, NY 10036, USA (http://www.ansi.org/).
8
ISO/IEC publications are available from the ISO Central Secretariat, 1, ch. de la Voie-Creuse, CP 56, CH-1211 Geneva 20,
Switzerland (http://www.iso.org/). ISO/IEC publications are available in the United States from the American National Standards
Institute, 25 West 43rd Street, 4th Floor, New York, NY 10036, USA (http://www.ansi.org/
9
The IEEE standards or products referred to in this clause are trademarks of The Institute of Electrical and Electronics Engineers, Inc.
10
IEEE publications are available from The Institute of Electrical and Electronics Engineers, 445 Hoes Lane, Piscataway, NJ 08854,
USA (http://standards.ieee.org/).
11
See Footnote 8.
33
IEEE Std 1826-2012
[B16] ISO/IEC 9646, Information Technology — Open Systems Interconnection — Conformance Testing
Methodology and Framework.
[B17] ISO/IEC 26702 (IEEE Std 1220TM-2005), Systems Engineering — Application and Management of
the Systems Engineering Process.
[B18] ISO/IEC/IEEE Std 15288-2008, Systems and Software Engineering — System Life Cycle Processes.
[B19] Levine, A.; Mish, W.; and Lynch, T., “Application of Physical Modular Open Systems to Meet
Technological Requirements and Capabilities – a Modular Reconfigurable Space,” presented at ASNE Day
2008, June 23–25, 2008, Arlington, VA.
[B20] MIL-STD-704F, Department of Defense Interface Standard, Aircraft Electric Power
Characteristics. 12
[B21] MIL-STD-1399, Military Standard, Interface Standard for Shipboard Systems, Section 300A,
Electric Power, Alternating Current (Metric).
[B22] MIL-STD-1399, Military Standard, Interface Standard for Shipboard Systems, Section 390, Electric
Power, Direct Current (Other than Ship’s Battery) for Submarines (Metric).
[B23] MIL-STD-1399, Military Standard, Interface Standard for Shipboard Systems, Section 680, High
Voltage Electric Power, Alternating Current.
12
MIL publications are available from Customer Service, Defense Printing Service, 700 Robbins Ave., Bldg. 4D, Philadelphia, PA
19111-5094, USA.
34

Ieee Standard For Power Electronics Open System Interfaces in Zo

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Ieee Standard For Power Electronics Open System Interfaces in Zo

Încărcat de

Drepturi de autor:

Formate disponibile

IEEE Standard for Power Electronics

Open System Interfaces in Zonal

IEEE Industry Applications Society

IEEE Standard for Power Electronics

Petroleum and Chemical Industry Committee

Approved 8 June 2012

IEEE-SA Standards Board

The Institute of Electrical and Electronics Engineers, Inc.

Copyright © 2012 by The Institute of Electrical and Electronics Engineers, Inc.

PDF: ISBN 978-0-7381-7283-5 STD97258

Comments on standards should be submitted to the following address:

Secretary, IEEE-SA Standards Board

Laws and regulations

Updating of IEEE documents

Yuri Khersonsky, Chair

John Amy Narain Hingorani Kevin Peterson

John Amy Herbert Ginn Joseph Piff

Dwight Alexander Mohammed Islam Iulian Profir

Richard H. Hulett, Chair

Satish Aggarwal Alex Gelman Oleg Logvinov

Richard DeBlasio, DOE Representative

3. Definitions, abbreviations, and acronyms .................................................................................................. 3

4. Zonal electrical distribution system (ZEDS) fundamentals ........................................................................ 4

5. Monitoring, information exchange, control, and protection interfaces ......................................................11

6. Electric power interfaces ...........................................................................................................................15

7. Verification and validation (V&V) ............................................................................................................18

8. Maintenance of open systems interfaces ...................................................................................................30

Annex B (informative) Bibliography............................................................................................................33

1.3 Application and limitations

IEC 60038:2009, IEC Standard Voltages. 3

IEEE Std 1709TM-2010, IEEE Recommended Practice for 1 kV to 35 kV Medium-Voltage DC Power

3. Definitions, abbreviations, and acronyms

community: a logical and physical grouping of neighborhoods.

3.2 Abbreviations and acronyms

HDD hardware design description

HMI human-machine interface

HRS hardware requirements specification

IDD interface design document

IRS interface requirements specification

MTBSI mean time between service interruptions

QoS quality of service

SRS systems requirements specification

TRA threat and risk assessment

VVP verification and validation plan

V&V verification and validation

ZEDS zonal electrical distribution system

4. Zonal electrical distribution system (ZEDS) fundamentals

Figure 1 —Power system versus zone (graphic)

Figure 2 —Electrical power block diagram

4.2 Zonal distribution system elements

4.2.1 External-to-bus conversion

The external-to-bus conversion element has the following functions:

4.2.2 In-zone distribution bus

4.2.3 In-zone energy storage

4.2.4 In-zone generation

4.2.5 Bus-to-internal conversion

4.2.6 Distribution panel

4.2.7 End-use device

4.3 Quality of service (QoS)

4.3.1 Service interruption

4.3.2 Reconfiguration time (t1)

4.3.3 Generator start time (t2)

4.3.4 Mean time between service interruptions (MTBSI)