Annex A.2.4: OpsCon: the current system or situation
The section describes the system or situation as it exists, whether automated or manual.
What annex A.2.4 asks
The section describes the system or situation as it exists, whether automated or manual. Where there is no current system, it describes the situation behind the proposed system and tailors the subsections accordingly. It covers the background, objectives and scope; the operational policies and constraints; a description of the current system, including environment, elements, interfaces, capabilities, data and control flows, cost, risk, performance and quality attributes; the modes of operation; the user classes and anyone else involved; and the support environment.
Annex A is normative content and part of a full conformance claim.
Why it matters
The current-system description is the baseline against which the change is justified. The clause asks for the degraded, backup and emergency modes, which are the ones a new design most often forgets. It also asks for the support environment, because a system that cannot be supported is not a viable option.
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
Describe the current system in the users' terms. Include the modes, the user classes and the support arrangements. Use diagrams where they clarify the flows. Keep the cost and performance data with their source and date.
Evidence an assessor asks for
The assessor will ask for the emergency mode and the support arrangement. A current-system description without them is incomplete.
- Current system description The environment, elements, interfaces, capabilities, flows and quality attributes
- Modes of operation Normal, degraded, backup, emergency, maintenance and training modes, as applicable
- User classes Each class, its profile, responsibilities and interactions with the current system
- Support environment The support agencies, facilities, equipment, maintenance levels and supply arrangements
Where it commonly fails
- Only the normal mode is described, so the new system inherits the same blind spot
- User classes are listed by job title with no profile or interaction
- The support environment is omitted because the project is about acquisition
What to do before the revision
Walk one emergency scenario through the current system. It will surface the modes, the users and the support gaps in a single pass.
Read across
- A.2.2 OpsCon: scope and system overview
- A.2.5 OpsCon: justification and nature of changes
- 6.3.3.3 Define stakeholder needs
- 6.3.3.4 Develop the operational concept
← A.2.3 OpsCon: referenced documents A.2.5 OpsCon: justification and nature of changes →
Source for annex A.2.4: ISO/IEC/IEEE 29148:2018, Annex A.2.4, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.