Assets

An asset is a resource that moves. A person, a hand tool, a gauge, a forklift: it travels to the work rather than the work coming to it, so it has no place on the site plan.

Assets in the sidebar (“Mobile resources, planned by availability”) holds every asset type your workspace activated. One page for all of them; the selector at the top right picks the type. Types that stand still belong to Stations instead.

The tabs

• {Type name} — the list of resources of the selected type.
• Groups — clusters of those resources.
• Lists — the reference lists this type carries. The tab appears only when the type has one.

The list

The list sorts and filters from its column headers, like every list in Orkyo — see Sorting and filtering lists.

Open a resource to edit it:

• Name (required) and Description.
• Allocation Mode — how its time is consumed: Exclusive (one assignment at a time) or Fractional (assignments consume a percentage of availability, so several can coexist until the budget is spent).
• Base Availability (%) — how much of the working calendar this resource is available. A half-time colleague is 50.
• Home Site and Available for other sites — where it normally is and whether cross-site assignments are allowed. Site mismatches surface in validation.
• Custom fields — the fields the type declares.

People

A type can carry a directory profile. When it does, its resources also hold an Email and Notes, and can be linked to a user account. Notes are encrypted at rest.

Job title and department are not columns on the person. They are lookup fields: the value is a row in an organization list, chosen from a picker. Maintain the lists themselves on the Organization page, and the department tree comes with them.

Skills

A person’s Skills section assigns criteria — the same shared vocabulary stations use. A request requiring Forklift license will only validate against people who carry it.

Absences

Record time away from the asset’s own schedule (below): select the empty time and choose Block time. An absence carries a Type — Vacation, Sickness, Unavailable, Training, Maintenance, or Custom — and an optional Reason. Absences flow straight into scheduling: assignments that overlap one are flagged, and auto-scheduling plans around them. See Scheduling and availability.

The schedule of one asset

Every row carries a Manage Schedule action, and the row name opens the same view from the Utilization board. It shows one asset’s own time on a calendar: the work booked on it, and the periods it is not available.

Drag or resize a booking to move the work. This reschedules the request itself, so the board and the conflict list agree with what you see here. Bookings carry the conflict colours the board uses.

Select an empty slot to choose between two things: assign a request to this asset, or block the time as an absence. Select an absence to change it.

Viewers see the calendar and can not change it.

Groups

Groups cluster assets by crew, shift, or function. They keep large lists navigable and can carry shared capabilities, the same way station groups do. Groups belong to one type.

Where assets show up

• Utilization — one timeline row per resource, showing assignments against availability. Filter the board by type.
• Requests — the People section assigns who is needed, and the resource pickers cover every other type the request targets. Orkyo validates continuously (“No issues found” when clean).
• Insights — every active type gets a utilization card and a trend chart.