← Back to catalogue
Research draft

Sites and assets landscape

EM-LND-17 · em-lnd-17

Placement, ownership, usage and maintenance of assets in space.

Enterprise profiles Enterprise landscape EnterpriseLND

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

Bundle → Layer → Finding → Questions Filled

2 bundles · 2 layers · 4 findings · 8 questions

Sites and assets Where assets are and who answers for them.

Placement

Assets placed at locations over periods.

Actual placement

Where the asset physically is, and since when.

  1. Where is the asset physically located, and since when?
  2. Is this a planned placement or a recorded actual one?

Responsibility

Owner and custodian at each placement.

  1. Who owns the asset and who is responsible for it at this site?
  2. Is the asset leased, and from whom?
Use and availability Occupancy and availability of sites for tasks.

Occupancy

Use of sites and the policies that govern location data.

Site availability

Whether a site can host a given task.

  1. Which sites are unavailable for this task, and why?
  2. Which maintenance or occupancy limits apply at the site?

Personal location

Location data about people, governed by policy.

  1. Does this view include the location of identifiable people?
  2. Which policy allows that location data to be shown?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise landscape
Entry kind
landscape
Domain
EnterpriseLND
Industry
Cross-industry
Tags
EM-LND-17W2landscapeAssetPlaceLandscapeOccupancyView

What it is Filled

Placement, ownership, usage and maintenance of assets in space.

Why it exists Filled

Placement, ownership, usage and maintenance of assets in space.

Distinguishing features Filled

  • A location and an asset are separate records joined by a placement with a period.
  • Planned placement and actual placement are kept apart.
  • The location of people is protected by policy and is not a by-product of asset tracking.
  • Distinct from the asset maintenance contour, which follows one asset through its life.

What robots and AI may and may not do Filled

Must not

  • Treat the registered address of a company as the location of all its assets.
  • Overwrite past placements when an asset moves.
  • Show the location of identifiable people without a policy that allows it.
  • Mark a leased asset as owned by the lessee.

Only with a human decision

  • Authorising tracking that reveals where people are.
  • Confirming transfer of responsibility for a high-value or hazardous asset.

May

  • Show the placement and responsibility history of an asset across sites.
  • Flag assets whose planned and actual placements differ.
  • List sites available for a task with their constraints.

Moral aspects Filled

  • Asset tracking can turn into surveillance of the staff who carry or use the assets.
  • Wrong placement data can send people to hazardous or unavailable sites.

Who is affected

  • Staff using or carrying assets
  • Site managers
  • Lessors and owners of assets

Owners Filled

Steward

The curator of the meta-model catalogue who decides which landscape views are assembled and from which sources.

Master systems

  • Model registry
  • Source manifest
  • Version lock file
  • Policy repository

Links to other meta-models Filled

references

  • WM-BLT-006 - conceptual-candidate
  • WM-BLT-008 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by a landscape identifier and as-of date; assets by asset or serial number and sites by their own identifiers.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A map of sites and assets with placements, owners and periods.
  • Often confused with a fixed asset register or a floor plan.

Capabilities and actions required Filled

  • Placement history can be reconstructed for any asset.
  • Availability of sites can be checked for a task.

Hazards and failure modes required Filled

  • Covert tracking of people through assigned equipment.
  • Lost responsibility when an asset moves without a placement record.

Standards and interfaces required Filled

  • ISO 55000 for asset management concepts and terminology.
  • ISO 16739 Industry Foundation Classes from buildingSMART for building and site data.
  • ISO 6709 for representing geographic point locations.

Context of use required Filled

  • Used in facility management, equipment logistics and lease administration.
  • Relevant for organisations with assets spread across several sites.

Sources Filled

  1. Vercy composition and whole-object: a separate landscape object and delegation
  2. ArchiMate/ISO 42010: views, questions and representation rules
  3. Compare participant subject models and the practical assembly of a permitted context
  4. Vercy Whole-Object Description Profile - Checked live (HTTP 200) on 2026-10-07.
  5. 5.4.3.25 IfcFacility — IFC 4.3.2 Documentation - Carried over from the published world model wm-blt-006-facility; checked live (HTTP 200) on 2026-10-09.
  6. IfcFacilityPart — IFC 4.3.2 Documentation - Carried over from the published world model wm-blt-006-facility; checked live (HTTP 200) on 2026-10-09.
  7. D2.8.III.2 INSPIRE Data Specification on Buildings — Technical Guidelines - Carried over from the published world model wm-blt-006-facility; checked live (HTTP 200) on 2026-10-09.

Open questions

  • Where is the asset physically located and who is responsible?
  • How to distinguish a placement plan from the actual placement?
  • Which sites are unavailable for a task?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-lnd-17/brief.json, ver-cy/world-models/card-supplements/em-lnd-17.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.