Organizational Unit and Mandate
A unit as a stable unit of responsibility. The org chart is a separate landscape; a team may be an independent collective.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 3 findings · 8 questions
Unit identity The organisational unit as a stable unit of responsibility.
Unit and mandate
What the unit answers for and what makes it a unit.
Unit mandate
The responsibility the unit holds, independent of its current name.
- What responsibility does this unit hold, and who approved its mandate?
- Which unit type is it, and does that type carry rules?
- Did a renaming keep the same unit identifier?
Placement Where the unit sits on each structural axis and in each period.
Axes
Administrative, functional and legal affiliation kept apart.
Axis placement
A parent stated per axis, scenario and period.
- Which parent does the unit have on the administrative axis, and for which period?
- Does the unit's functional parent differ from its administrative one?
- Which legal entity employs the people working in this unit?
Restructuring
As-is and to-be structures and the transitions between them.
Scenario integrity
Planned structures that preserve history and avoid cycles.
- Does the to-be scenario create a cycle on any axis?
- Are past assignments still attached to the unit as it was at the time?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseORG
- Industry
- Cross-industry
- Tags
- EM-ORG-04W1subjectOrganizationalUnitUnitMandateUnitTypeStructuralPlacement
What it is Filled
A unit as a stable unit of responsibility. The org chart is a separate landscape; a team may be an independent collective.
Why it exists Filled
A unit as a stable unit of responsibility. The org chart is a separate landscape; a team may be an independent collective.
Distinguishing features Filled
- A unit has a lasting identity and mandate that survives renaming.
- Each parent link belongs to one axis, one scenario and one period.
- The unit a person reports to does not determine which legal entity employs them.
- Distinct from collectives and teams, which may cut across units without a parent.
What robots and AI may and may not do Filled
Must not
- Force a cross-department product team under one administrative parent.
- Issue a new unit identifier because the unit was renamed.
- Infer the employer of a person from their reporting line.
- Overwrite past placements when a restructuring takes effect.
- Merge two axes into one hierarchy to simplify a chart.
Only with a human decision
- Approving a restructuring scenario for activation.
- Closing a unit that still holds assignments or budget.
May
- Report a unit's parent on a stated axis as of a requested date.
- Detect cycles in a proposed structure before it is applied.
- Compare as-is and to-be structures and list affected assignments.
Moral aspects Filled
- Restructuring records shape reporting lines and can affect jobs and pay.
- Wrong employer inference can misstate employment rights and obligations.
Who is affected
- Employees in affected units
- Unit managers
- HR and finance functions
Owners Filled
Steward
The corporate secretary or owner of the organisational model who answers for these records.
Master systems
- Corporate registry
- HRIS
- Public business registers
Links to other meta-models Filled
neighbor
- EM-ORG-01
- EM-ORG-06
- EM-PEO-02
references
- WM-ORG-002 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a stable unit identifier that does not change on renaming, with axis and period on each placement.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A record names a unit type, a mandate and placements on one or more axes.
- Often confused with cost centres, teams or the drawn org chart.
Capabilities and actions required Filled
- Hold several structural axes and planning scenarios side by side.
- Answer structure questions as of any past or planned date.
Hazards and failure modes required Filled
- Cycles introduced by restructuring on one axis.
- Loss of historical assignments when units are rebuilt instead of versioned.
Standards and interfaces required Filled
- W3C Organization Ontology for organisational units and sub-organisation links.
- HR Open Standards for exchanging organisation structure between HR systems.
Context of use required Filled
- Used in reorganisations, reporting lines, access scoping and cost allocation.
- HR, finance and IT each read the same unit for different purposes.
Sources Filled
- W3C ORG: collectives, roles, membership and posts
- GLEIF: registered identity and consolidation relationships
- Comparison of corporate governance, the actual org structure and the HR/ERP representation
- W3C The Organization Ontology - Checked live (HTTP 200) on 2026-10-07.
- FHIR R5 Resource Organization - Carried over from the published world model wm-org-002-organizational-unit; checked live (HTTP 200) on 2026-10-09.
- Core Public Organisation Vocabulary (CPOV) - Carried over from the published world model wm-org-002-organizational-unit; checked live (HTTP 200) on 2026-10-09.
- RFC 4519: Lightweight Directory Access Protocol (LDAP): Schema for User Applications - Carried over from the published world model wm-org-002-organizational-unit; checked live (HTTP 200) on 2026-10-09.
Open questions
- What makes a unit an independent object?
- How are administrative, functional and legal affiliation kept apart?
- How are OUMM and the current WM-ORG-002 reconciled without two owners of unit?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-org-04/brief.json, ver-cy/world-models/card-supplements/em-org-04.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.