| Acronym | Title | Acronym | Title |
| MPAI-AIF | AI Framework | MMM-TEC | MPAI Metaverse Model Technologies |
| AIH-HSP | AI for Health – Health Secure Platform | MPAI-MMC | Multimodal Conversation |
| MPAI-PRF | AI Module Profiles | NNW-NNT | Neural Network Watermarking – Neural Network Traceability |
| CUI-CPP | Compression and Understanding of Industrial Data – Company Performance Prediction | NNW-TEC | Neural Network Watermarking – Technologies |
| CAV-TEC | Connected Autonomous Vehicle – Technologies | MPAI-OSD | Object and Scene Description |
| CAE-USC | Context-based Audio Enhancement – Use Cases | MPAI-PAF | Portable Avatar Format |
| MPAI-TFA | Data Types, Formats, & Attributes | MPAI-SPG | Server-based Predictive multiplayer Gaming |
| MPAI-GME | Governance of the MPAI Ecosystem | EVC-UFV | Up-sampling filter for Video applications |
| MPAI-HMC | Human and Machine Communication |
Several MPAI Technical Specifications have been adopted by IEEE without modification and more are in the pipeline:
| MPAI name | Version | Number | Last approved | Resubmitted | Version |
| MPAI-MMC | V2.2 | 3300 | 2024 | ||
| MPAI-AIF | V2.0 | 3301 | 2024 | ||
| CAE-USC | V1.4 | 3302 | 2023 | 2026 | V2.4 |
| MPAI-CUI | V1.1 | P3303 | 2023 | ||
| MPAI-NNW | V1.0 | 3304 | 2023 | ||
| MMM-ARC | V1.0 | 3305 | 2024 | ||
| MPAI-PAF | V1.3 | 3306 | 2024 | ||
| CAV-ARC | V1.0 | 3307 | 2024 | ||
| MPAI-OSD | V1.5 | 3308 | 2024 | ||
| NNW-NNT | V1.0 | 3309 | 2026 | ||
| MPAI-HMC | V2.0 | 3310 | 2026 | ||
| CAV-TEC | V1.1 | P3311 | |||
| MMM-TEC | V2.2 | P3312 | |||
| EVC-UFV | V1.0 | P3314 | |||
| NNW-TEC | V1.0 | P3315 | |||
| AIH-HSP | V1.0 | P3316 |
Two MPAI Technical Specification are in the process of being adopted and two more are being submitted.
The table report all current AI projects. The first column gives the project status: Version of the Standard (Vx.y), Community Comments (CC), Under Development (Dev), Call for Technologies (CfT), and Exploration (Exp).
Currently, MPAI has a total of 17 projects at different stages of development. The first column of the table gives the status of the project: V (version of standard), CfT (Call for Technologies), Dev (under development CC (draft published for Community Comments). The second column gives the title of the project and a link to the project’s web page. The third column gives the project acronym.
See also the MPAI Work Plan and MPAI Timeline. See a succinct Introduction to MPAI.
MPAI develops mostly AI-based standards following a well-defined sequence of steps (see Annex I of the Statutes for more details)
| # | Acr | Name | Description |
| 0 | IC | Interest Collection | New project is identified, proposal submitted, interested parties found |
| 1 | UC | Use cases | Proposals of use cases, their description and merger of compatible use cases. |
| 2 | FR | Functional Requirements | Identification of the functional requirements that the standard should satisfy. |
| 3 | CR | Framework Licence | Development of the Framework Licence of the standard by the IPR SAC. |
| 4 | CT | Call for Technologies | Preparation and publication of a document calling for technologies supporting the requirements. |
| 5 | SD | Standard development | Development of the standard in a specific Development Committee (DC). |
| 6 | CC | Community Comments | Publication of the draft Technical Specification with a request from comments on the part of anybody. |
| 7 | TS | Technical Specification | The standard has been successfully completed and all Members have made the appropriate declarations. |
The MPAI General Assembly approves promotion of a project from a stage to the next stage.
