Capacity and Resource Allocation
Demand, available capacity and assignments of human and other resources to work. Human engagement, money and compute have different units.
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 Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
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 Derived, awaiting review
- Units and a calendar are mandatory
- A plan does not substitute for the actuals
- A conflict is checked within one scenario and interval
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: FTE, GPU hours and a money budget are summed into one capacity.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
PMO / руководитель исполнения
Master systems
- Трекер задач
- PPM
- планы и протоколы приёмки
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 Incomplete
Identity and identifiers required Derived, awaiting review
- ResourceDemand
- ResourcePool
- CapacityPlan
- ResourceAllocation
- AllocationScenario
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
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
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
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.