Annex A.2.7: OpsCon: impacts and analysis
The section summarizes the impacts of the proposed system and analyses it against the current situation.
What annex A.2.7 asks
The section summarizes the impacts of the proposed system and analyses it against the current situation. It covers the operational, organizational, cost, schedule and risk impacts, the affected user classes and interfaces, and the analysis that supports the choice. The level of detail should be enough for a reader to see why the proposed system is viable and what it displaces.
Annex A is normative content and part of a full conformance claim.
Why it matters
The impact summary is what a decision maker reads. The clause expects the analysis to connect the proposed system back to the current one, not to stand alone. The organizational impact is often the largest and the least documented.
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
List the impacts by category, with a named owner and a mitigation where the impact is adverse. Keep the analysis tied to the scenarios and the requirements. Record the impacts that fall on other systems and other organizations.
Evidence an assessor asks for
The assessor will ask who is affected outside the project. An impact summary that names only the project team is incomplete.
- Impact summary Operational, organizational, cost, schedule and risk impacts, with an owner for each
- Affected interfaces The systems, organizations and user classes affected by the change
- Analysis The assessment that supports the proposed system and the alternatives considered
- Mitigation record The adverse impacts and the mitigation or acceptance
Where it commonly fails
- The impact is described as positive only, with no adverse effects
- The analysis repeats the justification without assessing the effect
- Other systems and organizations affected by the interface are not named
What to do before the revision
Add an external impact row for every interface. The row is the one that prevents a surprise at integration.
Read across
- A.2.6 OpsCon: concepts for the proposed system
- A.2.8 OpsCon: appendices and glossary
- A.2.8 OpsCon: appendices and glossary
- 6.2.3.5 Evaluate alternative solution classes
← A.2.6 OpsCon: concepts for the proposed system A.2.8 OpsCon: appendices and glossary →
Source for annex A.2.7: ISO/IEC/IEEE 29148:2018, Annex A.2.7, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.