The MPAI Ecosystem is composed of the following cooperating entities:

  1. MPAI
    1. Acts as the root of trust of the MPAI Ecosystem.
    2. Defines the rules of Governance.
    3. Develops the 4 components of an MPAI Standard.
    4. Establishes the MPAI Store.
    5. Appoints Performance Assessors.
  2. MPAI Store
    1. Operates on a cost-recovery basis based on a mandate received from MPAI.
    2. Identifies implementers of MPAI Standards (see Annex 4).
    3. Establishes distribution agreements with Implementers.
    4. Tests implementations submitted by implementers for:
      1. Security Validation.
      2. Conformance with MPAI-AIF.
      3. Conformance with an Application-Oriented Technical Specification.
      4. Conformance with an Accessory Specification (if applicable).
    5. May receive notifications from Performance Assessors.
    6. Labels Implementations as:
      1. Level 1, if d.i and d.ii tests have been passed.
      2. Level 2, if d.iii tests have been passed.
      3. Level 3, if a Performance Assessor has notified that the Implementation has a Grade above the minimum level.
    7. Posts software Implementations for download.
    8. Manages a reputation system where the MPAI Store publishes report of their user experience of an Implementation, after moderation, if this becomes necessary.
    9. Manages the Implementer ID Registration Authority (IIDRA).
    10. The MPAI Store is a not-for-profit commercial organisation.
    11. However, the MPAI Store may recover the costs (e.g., ICT infrastructure, personnel, consultants) deriving from MPAI Store operation from Implementers, Service Providers and Users.
  1. Implementers
    1. Obtain an Implementer ID (IID).
    2. Make implementations.
    3. Submit implementations to the MPAI Store.
    4. May submit Implementations to Performance Assessors.
  2. Performance Assessors assess the Grade of an Implementation.
    1. May be implementers or qualified companies.
    2. May not Assess the Performance of their Implementations if Implementers.
    3. Are appointed for a particular domain and Performance category (Reliability, Replicability, Robustness, and Fairness) for an indefinite duration but MPAI may revoke the appointment.
    4. May charge Implementers, Service Providers, and Users for their services.
    5. The Performance Assessment process is confidential, unless the Implementor and the Assessor decide otherwise.

Table 2 gives the operations of the actors enabling the MPAI ecosystem to operate.

Table 2 – The players of the MPAI ecosystem

Player Role
MPAI Store 1.     Independent commercial not-for-profit entity established by MPAI.

2.     Assigns ImplementerID’s to Implementers as ImplementerID Registration Authority.

3.     Charges Implementers, Service Providers and Users on a cost recovery basis.

4.     Receives Implementations from Implementers.

5.     Tests Implementations submitted by Implementers for security and Conformance.

6.     Receives results of Performance Assessment of Implementations from Performance Assessors.

7.     AIWs and AIMs may be implementations of MPAI standards or independently developed but suitable to be executed in AIFs.

8.     Assigns AIWs and AIMs to security experts for testing (either employees or consultants).

9.     Receives commercial distribution licences of AIFs, AIWs and AIMs Implementations from Implementers.

10.  Distributes to Service Providers and Users Implementations that are approved by security experts and Tested for Conformance after assigning:

a.     A Level 1 label to non-MPAI-specified AIWs and AIMs.

b.     A Level 2 label to AIWs and AIMs Conforming to an MPAI Application Standard.

c.     Assign a Level 3 label to AIWs and AIMs Conforming to an MPAI Application Standard and whose Performance has been Assessed.

11.  Undertakes to make Implementations available through high availability ICT infrastructure.
Standard developer An expert contributing to the development of MPAI Standards.
Implementer An entity providing Implementations of AIFs, AIWs and AIMs.
Performance Assessor An entity certified by MPAI to determine whether an AIW or AIM:

1.     Conforms with one or more MPAI standards.

2.     Offers a Performance Grade.
Security expert An entity authorised by MPAI to develop tests establishing whether an AIF or an AIW or an AIM presents security issues.
Service Provider An entity running AIWs e.g., a private or public cloud. A Service Provider does not acquire the right to redistribute Implementations.
End User The ultimate beneficiary of the execution of AIWs. They may execute AIWs and AIMs in a local environment.