Edition 3 at DIS ballot, stage 40.20/ Planning date 12 September 2027, an estimate/ ISO/IEC/IEEE 29148:2018 applies today
ISO 29148 Revision CheckerThe requirements record, clause by clause, and the edition that follows it
A.2.2
ISO/IEC/IEEE 29148:2018
Annex A

Annex A.2.2: OpsCon: scope and system overview

Current editionISO/IEC/IEEE 29148:2018, Annex A, A.2.2Edition 3 at DIS ballotNo public change recorded

The scope section gives an overview of the OpsCon and the system it applies to.

What annex A.2.2 asks

The scope section gives an overview of the OpsCon and the system it applies to. The identification subsection gives the number, title and abbreviation of the system or subsystem, and describes the position of this OpsCon relative to other OpsCons in a ranked or networked structure. The document overview summarizes the purpose and audience, the security and privacy considerations, and the remaining parts. The system overview states the purpose of the proposed system, its general nature, the sponsors, user agencies, suppliers, support agencies, certifiers and operating sites, and the related documents. A graphical overview is strongly recommended.

Annex A is normative content and part of a full conformance claim.

Why it matters

The scope section is the map of the concept. The requirement to describe the position relative to other OpsCons matters in a system of systems, where a concept that looks complete on its own can conflict with a sibling. The system overview is also where the certifying bodies are named, which is useful for a regulated system.

In the public record

No clause level change is public for this unit; the DIS keeps the title and scope, and the requirement text is not released.

What good looks like

Write the identification and the system overview before the detailed sections. Name the certifying bodies and the operating sites explicitly. Use a context diagram as the graphical overview and reference it from the text.

Evidence an assessor asks for

The assessor will look for the certifying body and the operating site. A concept that names neither is not specific enough to bound the system.

  • Identification The system number, title, abbreviation and the position relative to related OpsCons
  • Document overview Purpose, audience, security and privacy considerations and the document map
  • System overview Purpose, nature, sponsors, users, suppliers, support agencies, certifiers and sites
  • Context diagram A graphical view of the system and its environment

Where it commonly fails

  • The OpsCon does not say how it relates to the system-level OpsCon
  • The system overview lists the supplier but not the user agency
  • There is no diagram and the text does not identify the external systems

What to do before the revision

Name one certifying body and one operating site, even if the list is provisional. The names force the boundary conversation.

Read across

← A.2.1 OpsCon: general, title and preface A.2.3 OpsCon: referenced documents →

Full register / Revision record

Source for annex A.2.2: ISO/IEC/IEEE 29148:2018, Annex A.2.2, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.