ISO/IEC FDIS 29110-5-6-3 · stage 50.00Planning date 18 Feb 2027, our estimateOfficial record
ISO
29110
ISO 29110 Revision CheckerThe Intermediate profile, before publication

Home / Register / SR-09

SR-09 · our practice ref · series-structure

Deliver the system and the evidence pack

Practice SR-09 in the System Definition and Realisation group. The basis is series-structure, and the row asks for 3 pieces of evidence.

At a glance

Ref
SR-09
Process
System Definition and Realisation
Basis
series-structure
Source
Public abstract, process list
Evidence
3 items
Gaps
2 common

Evidence to keep

  • System Definition and RealisationThe delivery record and the handover list
  • System Definition and RealisationThe as-built configuration and the test records
  • System Definition and RealisationThe operating limits and the known issues

Questions before you sign

  • What does the acquirer need to operate the system?
  • Who received the pack, and what did they acknowledge?
  • Which known issue is not written down?

The practice, in our words

Deliver the system with the evidence the acquirer needs to operate and maintain it: the as-built configuration, the verification and validation records, the operating limits and the known issues. Delivery is a handover, not a file transfer.

What it means in a VSE

Walk the acquirer through the pack. Record what they received and what they asked for. A delivery that leaves the acquirer unable to operate the system without calling the VSE has not delivered the evidence.

In a firm of 25 people or fewer, deliver the system and the evidence pack has to earn its time. The test for SR-09 is not whether the team understands it but whether the artefact exists at the end of the project. Shrink the meeting. Shrink the document. Keep the record.

How to evidence it

Attach the artefacts above to the Deliver the system and the evidence pack row with the project name, the owner and the date. The anchor for SR-09 is The delivery record and the handover list. A named person must produce it on request.

For SR-09, the reviewer will sample one live decision and ask for The as-built configuration and the test records. No artefact, no evidence. A file that depends on one person's mailbox is not a file for deliver the system and the evidence pack.

What an assessor samples

An assessor reads the deliver the system and the evidence pack practice, asks for its evidence and tests one project against it. For SR-09, the useful sample is the most recent project that used the practice, not the best one. A reconstruction written for the visit is a finding for SR-09 if the practice cannot be shown to have happened when it mattered.

Common gaps

  • The evidence pack assembled after the final invoice
  • Known issues left out of the handover
What changes from the 2019 report. For SR-09, system definition and realisation holds most of the evidence. The transition work is to keep the record as the work proceeds, not to reconstruct it at the end.

Where the draft fits

The public abstract places deliver the system and the evidence pack inside one of the four processes the Intermediate profile covers. For SR-09, the draft clause numbering and wording are not public, so this page cites Public abstract, process list and does not quote the draft. The basis label for SR-09 says whether the practice is stated in the public record, named as a process in the series, or our reading.

Related practices

Source for this page: Public abstract, process list. Open the record and compare it with the SR-09 statement above. Retrieved 2026-10-22.