Services and infrastructure landscape
Support incident response, change planning and continuity decisions by connecting services to operational dependencies, responsible owners and evidence of resilience.
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 11 questions
Services and instances This bundle connects consumer services to running instances and accountable operational roles.
Service map
This layer records service identity, supported outcomes and operational responsibility.
Service versus instance
This finding distinguishes a service from the instances that deliver it.
- Which instance records are linked to this service record?
- Which business outcome does this service support?
Operational responsibility
This finding identifies accountable roles and authoritative incident records.
- Which role is operationally accountable for this service?
- Which authoritative incident system and responsible role are referenced by this service record?
Dependencies and failure This bundle qualifies dependency evidence and the consequences of node failure.
Dependency graph
This layer distinguishes asserted and observed dependencies and records failure conditions.
Dependency evidence
This finding records evidence status and separates assertion dates from observation dates.
- What evidence status and supporting source are recorded for this dependency?
- When was this dependency assertion recorded?
- What observation date is recorded for this dependency, or is it explicitly unobserved?
Shared points of failure
This finding assesses potential disruption subject to dependency conditions and resilience evidence.
- Which services are linked as potentially affected by failure of this node?
- Which business outcomes are potentially disrupted in this node failure assessment?
- Under which operating conditions does this dependency become necessary for service delivery?
- What redundancy and failover evidence supports the impact estimate in this failure assessment?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise landscape
- Entry kind
- landscape
- Domain
- EnterpriseLND
- Industry
- Cross-industry
- Tags
- EM-LND-12W2landscapeServiceLandscapeServiceDependencyGraph
What it is Filled
Links between consumer services, applications, instances, infrastructure and operational responsibility.
Why it exists Filled
Support incident response, change planning and continuity decisions by connecting services to operational dependencies, responsible owners and evidence of resilience.
Distinguishing features Filled
- A service and the instances that serve it are separate records.
- Every topology statement distinguishes observed evidence with its observation date from an assumption with its assertion date and basis.
- A link to a server shows possible dependency, not full dependency of the service.
- The landscape maps running services and remains distinct from the software product landscape.
What robots and AI may and may not do Filled
Must not
- Treat a link to a server as proof that the service fully depends on it.
- Present an assumed dependency as observed or present observed topology as current without dated evidence supporting its currency.
- Treat an assumption's assertion date as an observation date.
- Claim uninterrupted service from redundancy without accounting for failover conditions and supporting evidence.
- Store incidents in the landscape instead of with their domain owner.
- Change production configuration based on the landscape view alone.
Only with a human decision
- A responsible human must accept an impact assessment used for a major incident or change decision.
- A responsible human must confirm dependencies and resilience assumptions that drive continuity planning.
May
- Assess possible node failure impacts on services and business outcomes using dependency evidence, redundancy and failover conditions.
- Highlight dependencies that are assumed rather than observed.
- Point to the owner who holds the incident record for an affected service.
Moral aspects Filled
- Understated impact can leave customers and staff without critical services during an outage.
- Clear operational responsibility protects on-call staff from blame for systems they do not own.
Who is affected
- Service consumers
- Operations and on-call staff
- Service owners
Owners Filled
Steward
The service configuration steward is accountable for dependency information and its reconciliation with service and infrastructure owners.
Master systems
- Service catalogues govern service identities and accountable ownership.
- Configuration management systems govern declared infrastructure and dependency records.
- Infrastructure inventory systems govern deployed resource identities and configuration records.
- Observability systems govern dated evidence of runtime dependencies and operating conditions.
- Incident management systems govern incident records and assigned responsibility.
- Continuity management repositories govern approved redundancy and failover requirements.
Links to other meta-models Filled
references
- WM-XCT-039 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- The dependency graph has a stable identifier independent of snapshot dates.
- Each snapshot has a version and assembly date, while its statements retain their own evidence status and dates.
- Services and instances retain their own authoritative identifiers.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- The landscape connects services, applications, instances and infrastructure nodes with responsible owners.
- It can be confused with a configuration management database extract or a network diagram.
Capabilities and actions required Filled
- Shared points of failure can be identified subject to dependency evidence and resilience assumptions.
- Impact assessments distinguish observed dependencies from assumptions and account for redundancy, available capacity and failover conditions.
Hazards and failure modes required Filled
- Outdated topology can misdirect incident decisions.
- Unverified links can overstate or understate service impact.
- Unverified failover assumptions can conceal a shared point of failure.
Standards and interfaces optional Filled
- ISO/IEC 20000-1 from the International Organization for Standardization and the International Electrotechnical Commission provides service management requirements relevant to configuration information.
- ArchiMate from The Open Group supports representation of application and technology layers.
- OpenTelemetry semantic conventions maintained by the OpenTelemetry project under the Cloud Native Computing Foundation support observed service identity.
Context of use required Filled
- The landscape supports incident management, change planning and continuity planning.
- It is relevant where services run on shared infrastructure.
Sources Filled
- Vercy composition and whole-object: a separate landscape object and delegation
- ArchiMate/ISO 42010: views, questions and representation rules
- Compare participant subject models and the practical assembly of a permitted context
- Vercy Whole-Object Description Profile - Checked live (HTTP 200) on 2026-10-07.
- OASIS Topology and Orchestration Specification for Cloud Applications Version 1.0 - Checked live (HTTP 200) on 2026-10-07.
Open questions
- Which business outcome would the loss of a node disrupt?
- Which services share a common point of failure?
- Which links are merely assumed?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-lnd-12/brief.json, ver-cy/world-models/card-supplements/em-lnd-12.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.