Environment, infrastructure and service instance
Deployed instance, environment, infrastructure resource, configuration item and technical topology. VM image, physical asset and product are kept separate.
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 9 questions
Instance and environment This bundle records deployed instance identity, placement and resource observations.
Deployed instance
This layer separates stable instance identity from changing placement and lifecycle observations.
Instance identity
This finding identifies the running artifact, environment and identity continuity of an instance.
- Which artifact version does this instance run?
- Which environment and region does this instance belong to?
- Does the recorded address change alter the identity of this instance?
Ephemeral resources
This finding records evidence of a short-lived resource and its retained lifecycle history.
- Which lifecycle observations and retained history document this short-lived resource?
- Which observation, source and observation time establish that this resource existed?
Topology and assets This bundle records hosting relationships and links between configuration items and distinct asset records.
Hosting topology
This layer captures cluster membership, service dependencies and resource relationships.
Cluster and nodes
This finding records time-specific cluster membership and dependent services.
- Which nodes belong to this cluster at the recorded time, and which nodes were replaced?
- Which services depend on this cluster, and in which regions?
Configuration item and asset
This finding distinguishes a configuration item from related financial assets, physical assets, images and products.
- Does this configuration item represent the same entity as a financial asset record or only reference one?
- Which virtual machine image, physical asset and product does this resource relate to?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseTEC
- Industry
- Cross-industry
- Tags
- EM-TEC-04W1subjectDeployedInstanceRuntimeEnvironmentInfrastructureResourceConfigurationItemHostingRelation
What it is Filled
Deployed instance, environment, infrastructure resource, configuration item and technical topology. VM image, physical asset and product are kept separate.
Why it exists Filled
Deployed instance, environment, infrastructure resource, configuration item and technical topology. VM image, physical asset and product are kept separate.
Distinguishing features Filled
- An IP address or hostname is an attribute, not the permanent identity of a server.
- Every instance references the artifact version it runs.
- A VM image, a physical asset and a software product are separate records from the instance.
- Distinct from the business application, which describes use rather than technical placement.
What robots and AI may and may not do Filled
Must not
- Use an IP address as the sole permanent identifier of a server.
- Delete history of ephemeral resources when they are destroyed.
- Change production infrastructure on its own initiative.
- Merge a logical cluster with one of its nodes.
- Record secrets or credentials as configuration item attributes.
Only with a human decision
- Changing production topology or decommissioning resources.
- Linking or unlinking configuration items from financial assets.
May
- Build a historical impact graph from hosting relations and observations.
- Report which instances run an outdated artifact version.
- Flag configuration items with no recent observation.
Moral aspects Filled
- Wrong topology records can delay recovery of services people depend on.
- Infrastructure records reveal attack paths and need restricted access.
Who is affected
- Service owners and operators
- Users of affected services
- Finance teams tracking assets
Owners Filled
Steward
The CTO, the CIO or the service owner accountable for the system.
Master systems
- Software catalogue
- Source control
- CI/CD pipeline
- CMDB
- Observability platform
Links to other meta-models Filled
neighbor
- EM-FIN-05
- EM-PRD-02
- EM-RSK-01
- EM-RSK-04
- EM-TEC-01
- EM-TEC-03
- EM-TEC-05
- EM-TEC-06
- EM-WRK-06
references
- WM-SFT-010 - conceptual-candidate
- WM-SFT-002 - conceptual-candidate
- WM-XCT-039 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a stable instance or resource identifier; addresses, hostnames and cloud IDs are recorded as time-bound attributes.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A record names an environment, an artifact version, a host or cluster and an observation time.
- Often confused with the physical server, the VM image or the product.
Capabilities and actions required Filled
- Historical topology supports impact analysis for changes and incidents.
- Observations with time and source keep the record honest about what was seen.
Hazards and failure modes required Filled
- Stale CMDB entries that misdirect incident response.
- Identity loss when addresses are reused by other resources.
- Exposure of topology details to unauthorised readers.
Standards and interfaces required Filled
- ISO/IEC 20000-1 for service management including configuration management.
- DMTF Common Information Model for managed resources.
- OASIS TOSCA for topology and orchestration descriptions.
- OpenTelemetry resource semantic conventions from the CNCF.
Context of use required Filled
- Used by operations, SRE and IT asset teams across cloud and on-prem estates.
- Ephemeral cloud and container resources dominate modern estates.
Sources Filled
- AISMM/WM-SFT and ArchiMate: product, system and architecture
- CSDM: business application, service and runtime instance
- SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary
- OpenTelemetry Resource Semantic Conventions - Checked live (HTTP 200) on 2026-10-07.
- SPDX Specification 2.3 - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to model ephemeral resources without losing history?
- When do a CI and a financial asset coincide?
- How to distinguish a logical cluster from its nodes?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-tec-04/brief.json, ver-cy/world-models/card-supplements/em-tec-04.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.