Capacity and Resource Allocation
Demand, available capacity and assignments of human and other resources to work. Human engagement, money and compute have different units.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 4 findings · 9 questions
Demand and capacity What work needs and what resources can provide.
Demand
Resource demand stated with units, competencies and calendar.
Resource demand
A demand with unit, quantity, competency and interval.
- Which competency or resource kind is demanded, in which unit and for which interval?
- Which work item, project or product does the demand come from?
Capacity
Available capacity in pools, on a calendar.
Resource pool
A pool with its unit, calendar and indivisibility rules.
- Which pool supplies the resource, in which unit and under which calendar?
- Is the resource shared across teams or indivisible, such as one specialist or one machine?
Allocation Assignments of capacity to demand within scenarios.
Plan and scenario
Allocations checked within one scenario and interval.
Allocation conflict
An overlap or over-allocation within a single scenario and interval.
- Does the allocation exceed capacity within this scenario and interval?
- Is an apparent over-allocation actually the sum of two alternative scenarios?
- Which projects compete for the same specialist or pool?
Plan versus actual
Planned allocation kept apart from recorded actuals.
- What actual time or usage was recorded against the allocation?
- Does the allocation change any term of employment or contract?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseWRK
- Industry
- Cross-industry
- Tags
- EM-WRK-05W2subjectResourceDemandResourcePoolCapacityPlanResourceAllocationAllocationScenario
What it is Filled
Demand, available capacity and assignments of human and other resources to work. Human engagement, money and compute have different units.
Why it exists Filled
Demand, available capacity and assignments of human and other resources to work. Human engagement, money and compute have different units.
Distinguishing features Filled
- Every demand and capacity figure carries a unit and a calendar; person time, money and compute hours are never added together.
- A conflict is only meaningful within one scenario and one interval, so alternative scenarios are not over-allocation.
- An allocation plan is a forecast and does not replace recorded actual time or usage.
- Allocating a person to work does not change their employment terms, which belong to the work relationship.
What robots and AI may and may not do Filled
Must not
- Sum FTE, compute hours and money budget into one capacity figure.
- Report an allocation plan as actual time worked.
- Change a person's working hours or contract terms through an allocation.
- Flag a conflict by adding allocations from different scenarios.
- Allocate a person beyond their recorded availability without a visible warning.
Only with a human decision
- Resolving a conflict between projects over one person or pool.
- Approving allocations that exceed normal working time.
- Assigning a named person to work outside their agreed role.
May
- Detect over-allocation within one scenario and interval and name the competing demands.
- Convert units within one resource kind, such as hours to days on a stated calendar.
- Compare planned allocations with recorded actuals.
- Propose alternative allocation scenarios for human review.
Moral aspects Filled
- Over-allocation of people leads to overwork, so limits on working time must be respected.
- Allocation data can expose individuals to unfair comparison when context is missing.
Who is affected
- People whose time is allocated
- Project and product leads competing for capacity
- Owners of shared equipment and compute pools
Owners Filled
Steward
The project management office or execution lead who answers for capacity plans and resource allocations.
Master systems
- Task tracker
- Project portfolio management system
- Plans and acceptance records
Links to other meta-models Filled
neighbor
- EM-PRD-01
- EM-WRK-01
- EM-WRK-02
references
- WM-ORG-016 - conceptual-candidate
- WM-ECO-012 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- An allocation is identified by scenario, resource or pool, demand and interval.
- A pool is identified by its own code, resource kind and unit.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- An allocation record states a unit, a quantity, an interval and a scenario.
- Often confused with an employment assignment, a budget or a timesheet entry.
Capabilities and actions required Filled
- Overlaps can be computed per scenario and interval across projects.
- Shortfalls can be traced back to the demands that cause them.
Hazards and failure modes required Filled
- Meaningless totals when different units are summed.
- Phantom conflicts when scenarios are mixed.
- Burnout when planned allocations ignore availability and working time limits.
Standards and interfaces required Filled
- ISO 8601 for intervals, durations and recurring calendars.
- UN/ECE Recommendation No. 20 from UN/CEFACT for codes of units of measure.
- iCalendar, IETF RFC 5545, for availability calendars.
Context of use required Filled
- Used in project, product and shared service organisations that plan people and equipment.
- Labour law and collective agreements limit how much time may be allocated to a person.
Sources Filled
- PMI: project/program/portfolio
- Process-based and flow-based organization of work; compare Scrum/Kanban against primary sources
- Tracker object practice: container, issue, workflow and binding to the business initiative
- The Scrum Guide - Checked live (HTTP 200) on 2026-10-07.
- The Organization Ontology (org:Membership, org:Post, org:Role, org:memberDuring) - Carried over from the published world model wm-org-016-work-assignment; checked live (HTTP 200) on 2026-10-09.
- FHIR Release 5 - PractitionerRole resource - Carried over from the published world model wm-org-016-work-assignment; checked live (HTTP 200) on 2026-10-09.
- Web Services - Human Task (WS-HumanTask) Specification Version 1.1 - Carried over from the published world model wm-org-016-work-assignment; checked live (HTTP 200) on 2026-10-09.
Open questions
- How are a competency demand and available capacity matched?
- How are shared teams and indivisible resources accounted for?
- When is exceeding 100% an error, and when different scenarios?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-wrk-05/brief.json, ver-cy/world-models/card-supplements/em-wrk-05.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.