← Back to catalogue
Published

Enterprise landscape

EM-LND-18 · em-lnd-18

A composition of selected domain landscapes for specific management questions. Not a universal copy of all enterprise data and not a kernel.

Enterprise profiles Enterprise landscape EnterpriseLND

Bundle → Layer → Finding → Questions Filled

2 bundles · 2 layers · 4 findings · 8 questions

Composition Which domain landscapes are combined and why.

Selected contours

Contours included for stated management questions.

Inclusion basis

The question that justifies each included contour.

  1. Which management question justifies including this contour?
  2. Which contours are left inactive, and is that recorded as a choice?

Completeness

How complete the composition is for its questions.

  1. Can the stated questions be answered with the contours included?
  2. Which gaps remain without installing every domain?
Cross-context rules How meanings, ownership and restrictions cross domains.

Ownership and meaning

Facts stay with their domains; conflicts are handled explicitly.

Fact ownership

Which domain owns each fact shown in the view.

  1. Which domain owns this fact, and is the view only referring to it?
  2. How is a conflict between local meanings resolved or shown?

Restrictions in transit

Access and use limits that travel with facts.

  1. Do restrictions on a fact still apply when it appears in another context?
  2. Who may see this combined view?

Classifiers Filled

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

What it is Filled

A composition of selected domain landscapes for specific management questions. Not a universal copy of all enterprise data and not a kernel.

Why it exists Filled

A composition of selected domain landscapes for specific management questions. Not a universal copy of all enterprise data and not a kernel.

Distinguishing features Filled

  • The composition is chosen per management question, not copied from all enterprise data.
  • Facts stay owned by their domains; the enterprise view only refers to them.
  • Restrictions travel with a fact across contexts.
  • Distinct from the composition foundation, which defines the rules; this view applies them to one enterprise.

What robots and AI may and may not do Filled

Must not

  • Require an enterprise to install every subject model in the registry.
  • Take over ownership of facts from the domain that holds them.
  • Drop access or use restrictions when a fact crosses into another context.
  • Present the enterprise view as a universal copy of all enterprise data.

Only with a human decision

  • Choosing which contours to include for a given set of management questions.
  • Resolving a conflict between domain meanings that affects decisions.

May

  • Assemble different enterprise views for different organisations from the same registry.
  • Leave unneeded domains inactive and record that choice.
  • Show conflicts between local meanings instead of resolving them silently.

Moral aspects Filled

  • Over-collection into one view raises privacy and security risk for staff and customers.
  • Small organisations should not carry the cost of models they do not need.

Who is affected

  • Managers asking the questions
  • Domain owners
  • Staff and customers whose data appears

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

neighbor

  • EM-KRN-01 - The composition rules this view applies are set in the composition foundation.
  • EM-XCT-02 - Fact ownership across domains follows the fact ownership contour.
  • EM-LND-02 - A holding view usually includes the group-of-companies landscape.

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by an enterprise view scope identifier and version listing its included contours.

Direct properties not applicable Not applicable

Not applicable

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

Recognition optional Filled

  • A composition naming its management questions and the contours selected for them.
  • Often confused with an enterprise data warehouse or a full enterprise architecture repository.

Capabilities and actions required Filled

  • The same registry can serve a small service business and a holding with different views.
  • Completeness can be judged against stated questions rather than all domains.

Hazards and failure modes required Filled

  • Scope creep into a single store of all enterprise data.
  • Loss of restrictions when facts cross contexts.

Standards and interfaces required Filled

  • ISO/IEC/IEEE 42010 for views, viewpoints and stakeholder concerns.
  • ArchiMate from The Open Group for enterprise architecture models.
  • TOGAF from The Open Group for enterprise architecture method.

Context of use required Filled

  • Used by management to answer cross-domain questions without a central copy of data.
  • Relevant for organisations of any size, from small firms to holdings.

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. Vercy model agent protocol - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • Which questions justify including each contour?
  • How to act when local meanings conflict?
  • How to assess completeness without mandatorily installing all domains?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

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

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