Annex A.2.1: OpsCon: general, title and preface
An OpsCon document carries a title and a revision block that identifies it uniquely, including the project, version, release date, approval signatures, changed clauses and previous versions.
What annex A.2.1 asks
An OpsCon document carries a title and a revision block that identifies it uniquely, including the project, version, release date, approval signatures, changed clauses and previous versions. The approved document is placed under configuration control. The preface states the document's purpose, the scope of the activities that produced it, who wrote it and why, the intended audience and the expected evolution. A table of contents, list of figures and list of tables are included.
Annex A is normative content and part of a full conformance claim.
Why it matters
The general content is what makes an OpsCon usable as a controlled information item. The preface is not decoration: it tells a new reader why the document exists and how it will change. The configuration control requirement is part of the Annex A content, so an OpsCon outside configuration control does not meet the content requirement.
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
Use the same title and revision template as the requirement specifications. Write the preface last, when the audience and the evolution are known. Put the approved version under the same configuration control as the SyRS.
Evidence an assessor asks for
The assessor will check that the OpsCon is under configuration control. An unapproved concept document is not the baselined information item.
- Title and revision notice The title, version, release date, approval signatures and change list
- Preface Purpose, scope, authorship, audience and expected evolution
- Front matter Table of contents, list of figures and list of tables
- Configuration record The approval and the configuration control entry for the approved version
Where it commonly fails
- The OpsCon has no revision notice and is edited in place
- The preface describes the document but not its audience
- The approved version is not the version in the repository
What to do before the revision
Put the OpsCon on the configuration item list at the same time as the SyRS. The two documents are used together and should move together.
Read across
- A.2.2 OpsCon: scope and system overview
- 6.6.2.2.2 Configuration identification
- 7 The required information items
- 9.2 General content
Source for annex A.2.1: ISO/IEC/IEEE 29148:2018, Annex A.2.1, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.