Welcome
to the second IEEE Computer Society Standards Activity newsletter. Thank you to
the committee members for forwarding around the first issue – it achieved its
intention, and generated a number of enquiries and expressions of interest in
standards under development. Let’s hope for more of the same this time! It is
a shorter list as there was a shorter period for accumulating new applications,
and naturally more tend to be submitted at the end/beginning of the year. As
per last time, please can all Standards Committee Chairs/Vice-Chairs cascade
this to the membership, so that we can improve the communication and awareness
across our different working groups. If there is anything that is of interest,
then please either contact the WG leads, the standards committee chairs or
myself, so that we can put you in contact as needed. Thank
you for all of your efforts in developing new standards – together we can be
even more successful. Darren
Galpin
2026
SAB VP for Standards Activities
New PARs
1. Artificial Intelligence Standards Committee
|
Project Number
|
Project Title
|
Scope
|
Purpose
|
|
P3931
|
Standard for Agent
Description, Discovery, and Registry (ADDR) Interoperability
|
This standard specifies
a description model, registry mechanisms, and discovery protocols for
intelligent agents operating across platforms, organizations, and ecosystems.
It defines an agent metadata schema—a machine-readable model for describing
agent capabilities, input/output types, semantic and syntactic bindings,
version and compatibility policies, a runtime environment, resource
constraints, and service bindings. It also specifies registry and lifecycle
interfaces, including Application Programming Interfaces (APIs) and data
models for agent registration, update, and revocation, together with digital
signatures, timestamps, and integrity verification to help ensure traceable
and verifiable lifecycle management within interoperable registries.
The standard further defines discovery and matching protocols—methods for
querying, filtering, ranking, and negotiating agent capabilities based on
semantic tags, performance metrics, and version compatibility, as well as
support for fallback and degradation strategies. It specifies registry
aggregation and consistency—mechanisms for federated and decentralized
registry synchronization, caching, conflict resolution, access control, and
rate-limiting (ledger-agnostic design). It also defines validation and security
mechanisms to detect and mitigate risks arising from invalid, misleading, or
malicious agent descriptions, as well as conformance and interoperability
testing—including test suites, compliance assertions, and plugfest
procedures—for evaluating cross-platform compatibility.
Identity frameworks, trust scoring systems, collaborative governance
policies, or domain-specific business semantics are beyond the scope of this
standard.
|
The rapid growth of
agent ecosystems has resulted in fragmentation in the way intelligent agents
are described, registered, and discovered. In the absence of a standardized
registry and discovery protocol, agents cannot be consistently identified or
reused across platforms; capability and version metadata remain incompatible;
Service Level Agreement (SLA) and performance characteristics are neither
declared nor verifiable; and automatic agent composition and orchestration
are hindered.
In addition, agent-to-agent interaction introduces challenges that differ
fundamentally from traditional human–computer or system security models. An
agent’s declared description may not accurately reflect its actual
capabilities, behavior, or performance characteristics. While such
discrepancies can often be detected by human users through contextual
judgment, they are significantly harder to identify in fully automated
agent-to-agent interactions that rely solely on machine-readable
descriptions. Without standardized mechanisms for verifiable description,
registry validation, and performance signaling, malicious or misconfigured
agents may misrepresent their capabilities and disrupt agent networks,
undermining trust, safety, and interoperability at scale.
The purpose of this standard is to define a common, machine-readable schema
for agent description and registration, to enable cross-ecosystem discovery
and compatibility negotiation, and to provide verifiable SLA and capability
declarations to support trustable automation. The standard serves as a
foundational interoperability layer for higher-level agent frameworks and
domain-specific applications.
|
|
P3971
|
Standard for
Interoperability Specification for Scientific Intelligent Agent Systems
|
This standard specifies
interoperability requirements for scientific intelligent agent systems. The
standard encompasses a standardized description of interoperability and
fundamental components of the execution framework. This standard applies to
providers, operators, and users of scientific intelligent agent systems
(including artificial intelligence agents and intelligent wet-lab equipment),
while also supporting technological advancements based upon such systems.
|
|
|
P4502
|
Standard for a Physical Artificial Intelligence (AI) Framework for
Smart Mandibular Advancement Devices (Smart MADs)
|
This standard specifies the architectural framework and data interface
requirements for Physical Artificial Intelligence (AI)-enabled Smart
Mandibular Advancement Devices (Smart MADs), designed to perform autonomous,
closed-loop therapeutic adjustments for sleep apnea and related breathing
disorders. The scope encompasses the definition of logical structures and
data communication protocols among the device's core functional layers:
• the perception layer that is responsible for real-time physiological sensing
and pre-processing,
• the cognition layer that includes AI-based state inference and a
deterministic safety supervisor, and
• the actuation layer that executes physical mandibular positioning.
Specifically, this document standardizes the internal data flows and command
formats between modules to help ensure interoperability across heterogeneous
sensors and algorithms, while establishing mandatory control limits and
fail-safe mechanisms to protect patient safety during automated physical
interventions. This standard does not include clinical diagnostic criteria
for specific medical conditions or the validation of the clinical efficacy of
individual therapeutic algorithms.
|
This standard establishes a technical foundation that helps ensure
interoperability and enhance patient safety in the application of Physical AI
to Smart MADs for treating sleep breathing disorders. Currently, the absence
of a unified architecture for integrating sensors, AI algorithms, and
actuation mechanisms in smart healthcare devices leads to technological
fragmentation and potential safety risks associated with unverified
autonomous physical control. By defining clear interfaces and deterministic safety
protocols among sensing, cognition, and actuation modules, this standard
enables manufacturers to develop and exchange reliable, modular components,
and algorithms. Ultimately, this standard aims to accelerate the evolution of
passive oral appliances into intelligent therapeutic robots, thereby
facilitating the widespread adoption of dynamic, personalized treatment
solutions and enhancing clinical confidence in automated therapies.
|
|
P3998
|
Standard for Time Series Applied to Artificial Intelligence
Systems—Part 1: Definition and Format of Temporal Data Records
|
This standard defines fundamentals, requirements, and methodologies
for time series data produced internally by Artificial Intelligence Systems
(AIS) across their lifecycle. It establishes a unified temporal reference
framework specifying formats for internal temporal data records. This
standard excludes time series external to AIS, synthetic time series, and
derived data computed from AIS internal time series.
|
|
|
Project Number
|
Project Title
|
Scope
|
Purpose
|
|
P3931
|
Standard for Agent
Description, Discovery, and Registry (ADDR) Interoperability
|
This standard specifies
a description model, registry mechanisms, and discovery protocols for
intelligent agents operating across platforms, organizations, and ecosystems.
It defines an agent metadata schema—a machine-readable model for describing
agent capabilities, input/output types, semantic and syntactic bindings,
version and compatibility policies, a runtime environment, resource
constraints, and service bindings. It also specifies registry and lifecycle
interfaces, including Application Programming Interfaces (APIs) and data
models for agent registration, update, and revocation, together with digital
signatures, timestamps, and integrity verification to help ensure traceable
and verifiable lifecycle management within interoperable registries.
The standard further defines discovery and matching protocols—methods for
querying, filtering, ranking, and negotiating agent capabilities based on
semantic tags, performance metrics, and version compatibility, as well as
support for fallback and degradation strategies. It specifies registry
aggregation and consistency—mechanisms for federated and decentralized
registry synchronization, caching, conflict resolution, access control, and
rate-limiting (ledger-agnostic design). It also defines validation and security
mechanisms to detect and mitigate risks arising from invalid, misleading, or
malicious agent descriptions, as well as conformance and interoperability
testing—including test suites, compliance assertions, and plugfest
procedures—for evaluating cross-platform compatibility.
Identity frameworks, trust scoring systems, collaborative governance
policies, or domain-specific business semantics are beyond the scope of this
standard.
|
The rapid growth of
agent ecosystems has resulted in fragmentation in the way intelligent agents
are described, registered, and discovered. In the absence of a standardized
registry and discovery protocol, agents cannot be consistently identified or
reused across platforms; capability and version metadata remain incompatible;
Service Level Agreement (SLA) and performance characteristics are neither
declared nor verifiable; and automatic agent composition and orchestration
are hindered.
In addition, agent-to-agent interaction introduces challenges that differ
fundamentally from traditional human–computer or system security models. An
agent’s declared description may not accurately reflect its actual
capabilities, behavior, or performance characteristics. While such
discrepancies can often be detected by human users through contextual
judgment, they are significantly harder to identify in fully automated
agent-to-agent interactions that rely solely on machine-readable
descriptions. Without standardized mechanisms for verifiable description,
registry validation, and performance signaling, malicious or misconfigured
agents may misrepresent their capabilities and disrupt agent networks,
undermining trust, safety, and interoperability at scale.
The purpose of this standard is to define a common, machine-readable schema
for agent description and registration, to enable cross-ecosystem discovery
and compatibility negotiation, and to provide verifiable SLA and capability
declarations to support trustable automation. The standard serves as a
foundational interoperability layer for higher-level agent frameworks and
domain-specific applications.
|
2. Software & Systems Engineering Standards Committee
|
Project Number
|
Project Title
|
Scope
|
Purpose
|
|
P1012 (Revision)
|
Standard for System,
Software, and Hardware Verification and Validation
|
This verification and
validation (V&V) standard is a process standard that addresses all
system, software, and hardware life cycle processes. The standard includes clauses addressing
the following process groups: Agreement (of an Acquirer and a Supplier),
Organizational Project-Enabling, Project, Technical, Software Implementation,
Software Support, and Software Reuse.
This standard is compatible with all life cycle models (e.g., system,
software, and hardware); however, not all life cycle models use all of the
processes listed in this standard. V&V processes determine whether the
development products of a given activity conform to the requirements of that
activity and whether the product satisfies its intended use and user needs.
This determination may include the analysis, evaluation, review, inspection,
assessment, and testing of products and processes.
|
The purpose of this
standard is to:
- Establish a common framework of the V&V processes, activities, and
tasks in support of all system, software, and hardware life cycle processes.
- Define the V&V tasks, required inputs, and required outputs in each
life cycle process.
- Identify the minimum V&V tasks corresponding to a four-level integrity
schema.
- Define the content of the Verification and Validation Plan.
|
3. Digital Content Technology Standards Committee
|
Project Number
|
Project Title
|
Scope
|
Purpose
|
|
P2888.8
|
Standard for an
Integrated Interoperability Framework for Virtual Garment Fitting Service
Ecosystems
|
This standard defines
the physical–cyber interface for realizing interactions between the user’s
physical body (physical entity) and virtual garments (cyber entity) in a
smart mirror–based clothing fitting environment.
The standard defines the synchronization and communication framework between
actuators including lighting units, rotating stands, and adjustable display
modules in the physical world and the virtual fitting simulation modules in
the cyber world.
Digital garment rendering, Artificial Intelligence (AI)-based correction
algorithms, and user interface design are excluded from the scope of
standard.
|
The purpose of this
standard is to establish an integrated framework that minimizes the gap
between physical and virtual fitting experiences while helping ensure
cross-platform interoperability among devices and systems from different
manufacturers.
|
|
P2888.3a (Amend)
|
IEEE Standard for
Orchestration of Digital Synchronization Between Cyber and Physical
Worlds—Amendment: Security Requirements
|
This amendment defines
security requirements based on zero trust principles to enable secure
synchronization and interaction between cyber and physical worlds within the
IEEE 2888.3 framework.
|
|
|
P3079.2.3
|
Standard for Service
Framework for Motion Training
|
This standard defines a
service framework for mixed reality-based motion training systems. The
standard specifies service management, user account handling, content
distribution, payment interfaces, and a personalized recommendation logic. It
describes in- and output interfaces, data formats, and integration points
with basic and User Interface / User eXperience (UI/UX) frameworks,
facilitating standardized, efficient development, and interoperability across
various training scenarios.
|
This standard aims to
enhance interoperability and consistency across various training
applications, enabling developers to effectively deliver personalized,
interactive, and commercially viable training services.
|
4. Blockchain and Distributed Ledgers Standards Committee
|
Project Number
|
Project Title
|
Scope
|
Purpose
|
|
P3232.03
|
Standard for Framework
of Blockchain-Based Digital Provenance
|
The standard defines
digital provenance concepts, principles, and requirements in the context of
blockchain and distributed ledger technologies. The standards establishes a
reference architecture framework that includes data models, trust mechanisms,
interoperability requirements, and technical specifications for provenance
tracking across the complete lifecycle including creation, transformation,
transfer, and verification of digital artifacts.
|
|
|
P3240.23
|
Standard for Trusted
Material Management Framework for Electric Power Construction Sites
|
This standard specifies
a distributed ledgers technology (DLT) based trusted framework for the
life-cycle management of materials at electric power construction sites,
including procurement, transportation, storage, and usage. The electric power
construction sites refer to transmission and distribution construction sites
characterized primarily by scattered work areas, covering transmission line
projects and distribution network renovation projects; they do not include
sites with relatively fixed work areas such as power plants and substations.
This standard includes a three-layer architecture (perception, connection,
application), node roles, smart contract systems, data formats, and security
requirements, which is suitable for remote, mountainous, and cross-terrain
environments.
|
|
|
P3241.09
|
Standard for
Tamper-Resistant Carbon Accounting and Green Energy Attribution Using Synergy
of Metering Data and Distributed Ledger Technology
|
This standard specifies
a tamper-resistant framework for carbon accounting and green energy
attribution by integrating smart metering data and distributed ledger
technology. It covers data collection protocols, trusted execution
environment-based computation models, tamper-proof green certificate issuance
and transfer, and audit interfaces. Tamper resistant technology utilizes
reinforced materials, advanced locking mechanisms, and digital security
(cryptography, blockchain) to help prevent or detect unauthorized access to
physical and digital assets.
|
|
5. Design Automation Standards Committee
|
Project Number
|
Project Title
|
Scope
|
Purpose
|
|
P1076 (Revision)
|
Standard for
Verification and Hardware Design Language (VHDL)
|
This standard defines
the syntax and semantics of the Verification and Hardware Description
Language (VHDL). VHDL is a formal notation for use in all phases of the
creation of electronic systems. VHDL is both machine and human readable and
supports the design, development, verification, synthesis, and testing of
hardware designs; the communication of hardware design data; and the
maintenance, modification, and procurement of hardware.
This document addresses implementers of tools supporting the language and
advanced users of the language. In addition, this standard includes IEEE
1076.2, IEEE 1076.3, IEEE 1076.4, and IEEE 1164 into a single document.
|
|
6. Digital Tust Standards Committee
|
Project Number
|
Project Title
|
Scope
|
Purpose
|
|
P5002
|
Standard for Trusted
Digital Energy-Usage Recording Architecture for Computing Centers
|
This standard
establishes technical requirements for an energy supply and distribution
architecture for computing centers (including data centers, artificial
intelligence (AI) computing hubs, and edge computing nodes) to enable digital
and trusted recording of energy usage. The standard encompasses the
architectural framework, key components, and interfaces from the grid
connection or local energy source point to the Information Technology (IT)
load.
|
|
|
P5001
|
Guide for Extreme
Weather Flood Prevention Assessment of Power Facilities Based on Multi-Source
Trusted Data
|
This guide provides a
multi-source trusted data framework for the flood prevention assessment of
power facilities under extreme weather conditions. Extreme weather refers to
hydro-meteorological events that exceed the original design basis of
in-service power facilities, or events where flood risks are exacerbated by
changes in the external environment. The framework includes: 1) metadata
models and quality baselines for data sources; 2) guides for log recording
and auditing of data processing; 3) digital signature and verifiable
credential formats for assessment results; and 4) structural content
considerations for risk assessment reports. This guide applies to
station-type facilities such as substations, switching stations, and power
distribution rooms, but does not include transmission lines, power plants, or
user-side equipment. Conformance test cases are provided as informative
appendices to support implementation verification.
|
The purpose is to
provide power companies, assessment service institutions, and regulatory
authorities with a standardized basis for establishing consensus-based trust
in power facility flood prevention assessment results.
|
7. Standards Activities Board Standards Committee
|
Project Number
|
Project Title
|
Scope
|
Purpose
|
|
P3964
|
Standard for Intelligent
Operation and Maintenance System for Photovoltaic Power Generation
|
This standard provides
an intelligent operation and maintenance (O&M) specification for
photovoltaic (PV) power generation systems. The standard specifies hardware
configuration, system functions, data management, performance indicators,
security protection, and acceptance requirements.
|
|
8. Test Technology Standards Committee
|
Project Number
|
Project Title
|
Scope
|
Purpose
|
|
P1450.5 (Revision)
|
Standard Test Interface
Language (STIL)—Extensions for Test Flow Specification
|
This standard specifies
extensions to IEEE Std 1450 (Standard Test Interface Language; STIL.0) that
define the description of certain test flow and binning components of an
Integrated Circuit (IC) test program in a test-hardware-independent manner.
The flow and binning constructs in this standard allow for developing a test
program description in a common language. This common description (STIL.4)
can either be used as input to a test program generator that translates the
description into the native language of specific IC Automated Test Equipment
(ATE) systems or be run directly on IC ATE systems.
The extensions provide language constructs and semantics necessary to
describe both the test program flow and the sequencing data needed to compose
a test program to run on an ATE platform. The language constructs defined
include structures for specifying the following:
• Order of execution of test program components,
• Hierarchical test flow structures to facilitate automated modification or
maintenance,
• Common interfaces between the test flow environment and test program
components,
• Test flow variables to facilitate concurrent and serial test flow
interactions, and
• Binning or categorization of tested ICs.
The following aspects integral to test execution are specifically not
addressed by this standard:
• The standardization of the interface between the prober or handler and
tester is beyond the scope of this standard.
• Input/output operations and exception handling.
• The definition of test methods is beyond the scope of this standard.
|
This standard overcomes
the lack of test flow extensions in IEEE Std 1450 (Standard Test Interface
Language; STIL)
|
Completed Standards
|
Standard Number
|
Committee
|
Project Title
|
|
3536
|
Cybersecurity &
Privacy Standards Committee
|
IEEE Draft Standard for
Space System Cybersecurity Design
|
|
3161.5
|
Data Compression
Standards Committee
|
IEEE Draft Standard for
Algorithm and Model Repository of Digital Retina Systems
|
|
3161.6
|
Data Compression
Standards Committee
|
IEEE Draft Standard for
Storage System of Digital Retina Systems
|
|
802.15.4ae
|
LAN/MAN IEEE 802 Standards Committee
|
IEEE Draft Standard for
Low-Rate Wireless Networks Amendment: Ascon cryptographic algorithms
|
|
802.3dk
|
LAN/MAN IEEE 802 Standards Committee
|
IEEE Draft Standard for
Ethernet Amendment 11: Bidirectional 100 Gb/s Optical Access PHYs
|
|
26512
|
Software & Systems Engineering Standards Committee
|
IEC/IEEE Draft
International Standard - Systems and software engineering - Requirements for
acquirers and suppliers of information for users
|
Computer Society Standards Website |