← Back to catalogue
Published

Organizational structure

EM-LND-01 · em-lnd-01

Support organizational planning and accountable reporting by maintaining dated views of units, positions, teams and assignments across distinct structural axes.

Enterprise profiles Enterprise landscape EnterpriseLND

Bundle → Layer → Finding → Questions Filled

3 bundles · 3 layers · 4 findings · 11 questions

Structure axes Each axis defines its purpose and independent relationship constraints.

Axis definitions

Axis rules distinguish parent cardinality from cycle restrictions.

Axis definition

An axis specifies the structural relationships and constraints it governs.

  1. What organizational purpose does this axis serve?
  2. What parent cardinality does this axis permit, including any single-parent requirement?
  3. Does this axis require acyclic relationships independently of its parent cardinality rule?
Snapshots and history Dated views preserve historical structures and distinguish proposed future changes.

Structure snapshots

Each snapshot identifies its axis, effective date and referenced relationships.

Structure snapshot

A snapshot presents one dated structural view without overwriting earlier views.

  1. Which axis, effective date and relationship references define this snapshot?
  2. Which planned change reference, approval status and proposed effective date are recorded in this snapshot?
Structure assignments Dated links connect authoritative person, unit, position and team records.

Assignment links

Assignments retain their axis, validity period and source references.

Assignment record

Each assignment describes one relationship on one structural axis.

  1. Which person and unit references, axis and validity period does this assignment connect?
  2. Does this assignment comply with the parent cardinality rule of its recorded axis?
  3. Which position and unit or occupant references, relationship type and validity period does this position link record?
  4. Which team and member or unit references, relationship type and validity period does this team link record?

Reference integrity

Validation records identify reference and structural constraint failures.

  1. Does this link reference authoritative entity records without duplicating their attributes?
  2. Does this axis validation record identify a cycle that violates the applicable acyclicity rule?

Classifiers Filled

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

What it is Filled

A versioned graph of organizational units, positions, teams and assignments along independent axes.

Why it exists Filled

Support organizational planning and accountable reporting by maintaining dated views of units, positions, teams and assignments across distinct structural axes.

Distinguishing features Filled

  • Structure is described along independent axes with dated relationships.
  • Parent cardinality and acyclicity are separate rules, so an acyclic hierarchy may permit multiple parents.
  • Person, unit, position and team records are referenced from their authoritative records rather than copied.
  • This contour arranges organizational relationships while the workforce landscape counts people.

What robots and AI may and may not do Filled

Must not

  • Apply a single-manager rule to the whole organisation because of one matrix assignment.
  • Copy person or unit data into the landscape instead of referencing it.
  • Overwrite past structure when a reorganisation takes effect.
  • Expose reporting lines to viewers outside the permitted context.

Only with a human decision

  • Approving a reorganisation.
  • Changing reporting lines that affect employment terms.

May

  • Render the structure on one axis as of a chosen date.
  • Detect cycles on hierarchical axes.
  • Compare structures before and after a planned reorganisation.

Moral aspects Filled

  • Reporting lines influence people's careers and evaluations.
  • Organisation charts can reveal personal data beyond what viewers need.

Who is affected

  • Employees and managers
  • HR and organisation design staff
  • Auditors

Owners Filled

Steward

The organizational design lead is accountable for structure definitions, approved relationships and dated organizational views.

Master systems

  • A human resources information system maintains authoritative person and position assignments.
  • An organizational unit register maintains authoritative unit identities and relationships.
  • A team management system maintains authoritative team identities and memberships.
  • An organizational change register maintains approved reorganizations and effective dates.

Links to other meta-models Filled

references

  • WM-ORG-002 - conceptual-candidate
  • WM-ORG-003 - conceptual-candidate
  • WM-ORG-004 - conceptual-candidate
  • WM-ORG-016 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by the landscape identifier, the axis and the snapshot date.

Direct properties not applicable Not applicable

Not applicable

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

Recognition optional Filled

  • Marked by units, positions and dated links on named axes.
  • Often confused with a single organisation chart or with the HR master data itself.

Capabilities and actions required Filled

  • Consistent views of one history can be produced per axis and date.
  • Future reorganisations can be modelled without changing the present.

Hazards and failure modes required Filled

  • Mixing axes into one tree and losing matrix relations.
  • Duplicated person data drifting from the source.
  • Past structures lost after reorganisation.

Standards and interfaces required Filled

  • W3C Organization Ontology for units, posts and memberships.
  • ISO/IEC/IEEE 42010 for views and viewpoints.
  • ArchiMate by The Open Group for organisation views.

Context of use required Filled

  • Used for organisation design, access planning and management reporting.
  • Composed from organisation and people contours by reference.

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 participants' domain models and the practical assembly of the permitted context
  4. Vercy Whole-Object Description Profile - Checked live (HTTP 200) on 2026-10-07.
  5. W3C The Organization Ontology - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • How to distinguish the administrative, functional and project axes?
  • Where is a single parent admissible?
  • How to see the structure as of a date before a reorganization?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

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

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