# 3.3.2 Solution entity, ISO 42024 ## Published contents Contents1 Scope2 Normative references3 Terms and definitions4 Architecture concepts4.1 Overview4.2 Architecture and architecting4.3 Architecture design and solution design4.4 Architecture definition and communication4.5 Stakeholder concerns and architectural aspects4.6 Architecture viewpoints and architecture views4.7 Architecture frameworks and architecture description languages4.8 Architecture descriptions and architecture models4.9 Reference architectures and reference models4.10 Life cycle and life history4.11 Architecting precepts5 Architecting principles5.1 Introduction to the principles5.2 Principles about the purpose of an architecture5.3 Principles about the focus of an architecture5.4 Principles about architecting outcomesTerms 3.2 Architecting concepts 3.2.1 Architecture3.2.2 Architecture feature3.2.3 Architecting3.2.4 Architecting principle3.2.5 Architecture principle3.2.6 Architecture framework3.2.7 Reference architecture3.3 Entity related concepts 3.3.1 Entity of interest3.3.2 Solution entity3.3.3 Environment3.3.4 Context3.3.5 Enterprise3.3.6 System3.3.7 Aspect3.3.8 Dimension3.4 Architecture design concepts 3.4.1 Design (noun)3.4.2 Architecture design3.4.3 Architecture information package3.4.4 Engineering effort3.4.5 Solution design3.4.6 Solution information package3.4.7 Stakeholder3.4.8 Stakeholder perspective3.4.9 Concern3.5 Architecture description concepts 3.5.1 Architecture description3.5.2 Solution description3.5.3 Architecture view3.5.4 Architecture viewpoint3.5.5 Model3.5.6 Metamodel3.5.7 Reference model3.6 Entity life cycle concepts 3.6.1 Life cycle3.6.2 Life cycle phase3.6.3 Life cycle stage3.6.4 Life historyAnnexes A.1 Architecture design and solution related entitiesA.2 Architecture expressed as a set of modelsA.3 Life cycle and life history conceptsA.4 Enterprise and system conceptsA.5 Duality of architectural decomposition and architectural synthesisB.1 BackgroundB.2 Aligning architecture in designB.3 Duality of architectureB.4 Pursuit of opportunities Home / Glossary Entity related concepts · 3.3.2 # Solution entity The entity of interest plus the other entities that keep it running across one or more contexts over its life, as the realisation of the architectural entities of interest. Keeping it running covers affordability, continued viability, adaptability, evolvability, operational assurance and logistics support. - definition - Term - ISO/IEC/IEEE DIS 42024 - Last updated: 2026-10-21 ## What this term settles The solution entity is wider than the entity of interest. It includes what is needed to keep the entity alive: support, logistics, funding, operations. That wider view is what auditors and finance teams actually care about, because an architecture that cannot be sustained is not a solution. ## What to do in your practice For each entity of interest, list the sustainment entities and the context they serve. Mark which are in the firm control and which depend on a supplier or a shared service. The dependencies are the risks that a design review usually misses. ## Who it binds The role that owns the practice area the term governs. A definition binds nobody on its own; it binds the reader who adopts the term in a method, a description or a contract. ## Evidence an auditor or regulator asks for - A sustainment map from the entity of interest to the entities that keep it viable. Shows the architecture was designed for operation, not only for delivery. - A dependency list with supplier and contract references. An auditor asks what the entity relies on outside the firm control. - A cost of sustainment estimate per life cycle stage. Connects the architecture to affordability, one of the named properties. - A record of the contexts the solution must work in. Prevents a solution that works in one context being assumed to work in all. Ask your teamWhat does this entity need in order to still be viable in five years, and which of those needs is outside our control? ## Common gaps this page catches - The design stops at go live and sustainment is planned by a different team. - Supplier dependencies are known to operations but absent from the architecture record. - No one has stated the contexts the solution must work in. ## What to prepare before publication Add a sustainment section to the description template: affordability, viability, evolvability, adaptability, operational assurance and logistics support. Fill it once for a live entity and the missing rows will show where the practice is thin. ## Common questions What does Solution entity mean in ISO 42024? The entity of interest plus the other entities that keep it running across one or more contexts over its life, as the realisation of the architectural entities of interest. Keeping it running covers affordability, continued viability, adaptability, evolvability, operational assurance and logistics support. What evidence should we keep for 3.3.2? A sustainment map from the entity of interest to the entities that keep it viable. A dependency list with supplier and contract references. A cost of sustainment estimate per life cycle stage. ## Related units - 3.3.1 - 3.3.4 - 3.6.1 Source. ISO/IEC/IEEE DIS 42024, Clause 3.3.2, Terms and definitions. Open the official record. Retrieved 21 October 2026. https://www.iso.org/obp/ui/en/#iso:std:iso-iec-ieee:42024:dis:ed-1:v1:en ISO catalogue record 87510, the status, stage and page count. Claim level: definition. The definition is in the public preview. This page states it in our own words and does not reproduce the text. Last updated: 2026-10-21 · Markdown version · Check your practice Source: https://iso-42024-revision-checker.theartofservice.com/glossary/solution-entity/