Second edition at FDIS, stage 50.00, 23 July 2026/ Planning date 15 February 2027, an estimate/ ISO/IEC 25059:2023 applies today
25059ISO 25059 Revision CheckerThe AI quality model, clause by clause, and the edition that follows it
7.1
ISO/IEC 25059
AI service quality model

Clause 7.1: General

New in the second editionISO/IEC DIS 25059:2025 (public draft), Clause 7.1Published edition 2023Second edition at FDIS

New in the second edition.

What clause 7.1 is

New in the second edition. The clause introduces the AI service quality model, which is based on the service quality models standard. It exists because many AI systems are consumed as a service, where quality includes the people, the process and the support around the model, not only the model itself.

What the 2023 edition said

No equivalent. The first edition had no service model.

What the second edition changes

The clause and the model are new. The public draft adds three AI-specific elements: traceability, service adaptability and customizability.

What is not public

The FDIS text is not public. The change line above is read from the public draft, which is not the FDIS and may differ. No clause level diff is invented here. The ISO stage record is the authority for the dates.

Why it matters to the buyer

A product model asks whether the model is good. A service model asks whether the service around it is good: can a result be traced, can the service be adapted, can the user get what they asked for. Buyers of AI as a service need the second question answered.

What to write in the requirement

Describe the service as a service: the parties, the responsibilities, the support, the change route and the exit. Then write requirements against the three service characteristics. If the AI is embedded in a product with no service wrapper, record why the clause is not applicable.

Evidence a reviewer asks for

A reviewer will ask whether the contract describes a service or a product. The answer decides whether this clause applies.

  • Service descriptionThe parties, responsibilities, support model and service boundary
  • Applicability recordThe decision that the system is a service, a product or both, with the reason
  • Service requirementsOne requirement for each service characteristic in scope, with a measure

Where it commonly fails

  • The service is described in marketing language
  • No support responsibilities are recorded
  • The service model is ignored because the system is called a product

What to do before publication

Classify each AI system and write the service description where it applies.

Read across

← 6.3 Societal and ethical risk mitigation 7.2 Traceability →

Full record / Revision record

Source for clause 7.1: ISO/IEC 25059, Clause 7.1, retrieved 20 October 2026. The change line rests on the public draft of the second edition and ISO page 88234. The requirement, evidence and gaps are written from our record. Every source.