Availability and Time Tracking
Work calendars, absence and available capacity; actual time records and their approval. Allocation of capacity across work items is a separate model.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 4 findings · 10 questions
Availability Calendars, absences and available capacity.
Calendar and schedule
Working calendars with time zone and engagement share.
Schedule basis
The calendar, time zone and part-time share behind capacity.
- Which working calendar and time zone apply to this person?
- Is the person on a part-time or partial engagement, and from when?
- How does a daylight saving change affect the hours in this period?
Absence
Absences recorded with only the reason consumers need.
- Which absence category does an operational consumer need to see?
- Is a medical reason kept out of the shared availability calendar?
Actual time Worklogs, timesheets and their approval.
Worklog
Recorded time with period, time zone and work item.
Record completeness
What missing or overlapping records mean.
- Does a missing record here mean zero hours or simply no data?
- Do overlapping records double count time across projects?
Approval
Timesheet approval and later corrections.
Timesheet approval
Who approved the hours and what was corrected later.
- Who approved this timesheet, and when?
- Which corrections were made after approval, and are originals kept?
- Is this time record being used for anything beyond time accounting?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterprisePEO
- Industry
- Cross-industry
- Tags
- EM-PEO-07W2subjectWorkCalendarAbsenceAvailabilityWorklogTimesheet
What it is Filled
Work calendars, absence and available capacity; actual time records and their approval. Allocation of capacity across work items is a separate model.
Why it exists Filled
Work calendars, absence and available capacity; actual time records and their approval. Allocation of capacity across work items is a separate model.
Distinguishing features Filled
- Hours always carry a period and a time zone.
- A missing time record means unknown, not zero.
- Planned availability, assigned load and actual time are three separate quantities.
- Distinct from capacity allocation across work items, which is a separate model.
What robots and AI may and may not do Filled
Must not
- Use a worklog as proof of presence or of the quality of work.
- Show a medical absence reason in the shared availability calendar.
- Treat missing records as zero hours in capacity or billing.
- Overwrite an approved timesheet without keeping the original.
- Ignore time zones when summing hours across locations.
Only with a human decision
- Approving or rejecting timesheets used for pay or billing.
- Changing approved time after a period is closed.
May
- Compute available capacity from calendars, engagement share and absences.
- Flag overlapping or negative time records.
- Remind people and approvers about missing timesheets.
Moral aspects Filled
- Time data can become a surveillance tool if used beyond its purpose.
- Health-related absence data is sensitive and needs strict access limits.
- Errors in time records affect pay and overtime rights.
Who is affected
- Employees and contractors
- Approving managers
- Clients billed for time
Owners Filled
Steward
The head of HR or the person accountable for workforce records.
Master systems
- HRIS
- Time and attendance system
- Project time tracking tool
Links to other meta-models Filled
references
- WM-ACT-008 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by person, date range and time zone for availability, and by person, period and version for timesheets.
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 person, a period, a time zone and hours or an absence category.
- Often confused with capacity allocation or with presence logs.
Capabilities and actions required Filled
- Handle part-time schedules, time zones and daylight saving transitions.
- Keep corrections as new versions with approval.
Hazards and failure modes required Filled
- Double capacity from overlapping projects.
- Disclosure of medical reasons through calendars.
Standards and interfaces required Filled
- ISO 8601 date and time representation.
- IANA Time Zone Database.
- IETF RFC 5545 iCalendar for calendar data.
Context of use required Filled
- Used in resource planning, payroll, client billing and working time compliance.
- Working time rules such as the EU Working Time Directive set limits on hours.
Sources Filled
- HR Open: exchange of HR data
- W3C ORG and ESCO/SFIA: relationships, skills and levels of responsibility
- HRIS/ATS/LMS practice and independent verification of outcome measurement via SPACE
- RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar) - Carried over from the published world model wm-act-008-plan-schedule; checked live (HTTP 200) on 2026-10-09.
- RFC 5546: iCalendar Transport-Independent Interoperability Protocol (iTIP) - Carried over from the published world model wm-act-008-plan-schedule; checked live (HTTP 200) on 2026-10-09.
- RFC 8984: JSCalendar: A JSON Representation of Calendar Data - Carried over from the published world model wm-act-008-plan-schedule; checked live (HTTP 200) on 2026-10-09.
Open questions
- How are planned availability, assigned load and actual time distinguished?
- How are time zones, part-time schedules and overlapping records handled?
- Which absence reasons does an operational consumer need?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-peo-07/brief.json, ver-cy/world-models/card-supplements/em-peo-07.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.