The Orkyo planning model

Five ideas carry the whole product. Every page in Orkyo is a view onto some combination of them.

Requests — the work

A request is a piece of work to place onto your resources: a production run, a training session, a maintenance job. Requests carry:

• Requirements — criteria the hosting resource must satisfy (a minimum capacity, a certification, a piece of equipment).
• A schedule — a start and end once placed; unscheduled requests wait in the backlog.
• Constraints — optional time windows (“Earliest Start”, “Latest End”) limiting when the request may be scheduled.
• Children — requests nest. A parent acts as a container whose children can be bounded by a shared window, so a project’s tasks stay inside the project’s timeframe.

Resources — the capacity

A resource is anything you schedule work onto or with. Orkyo treats spaces, people, and tools as resources of different types:

• Spaces — rooms, areas, zones. They can carry a floorplan geometry, a capacity, and live at a site.
• People — resources with skills, working availability, and absences. People carry an allocation mode: Exclusive (one thing at a time) or Fractional (a percentage of their availability).
• Tools — equipment tracked and matched like any other resource.

Resources are organized into groups — by site, team, or function — to keep large catalogs navigable and to manage related resources together.

Criteria — the matching language

Criteria are typed attributes — Boolean, Number, String, or Enum — defined once in Settings and used on both sides of the match: on a resource they are capabilities (“this space has a crane”), on a request they are requirements (“this job needs a crane”). One vocabulary, two roles. That is what lets Orkyo validate placements automatically. The details live in How capability matching works.

Sites — the geography

A site is a physical location: a plant, a campus, a building. Spaces belong to sites; people have a home site and can be marked available for other sites. The site selector in the top bar scopes the boards to one site, and scheduling settings — working hours, weekends, holiday regions — are defined per site.

Schedules — where it all meets

A schedule is the placement of requests onto resources over time. The Utilization board is where you build it — by dragging, or by letting auto-scheduling propose placements. When a placement violates the model — an overbooked resource, a missing capability, an absence — Orkyo raises a conflict rather than silently accepting it.

How the pieces mesh

Criteria ──── as capabilities ────▶ Resources (spaces · people · tools)
   │                                    │  grouped, sited, with availability
   └──── as requirements ────▶ Requests │
                                   │    │
                                   ▼    ▼
                              Schedule (Utilization board)
                                   │
                                   ▼
                    Conflicts · Utilization · Insights

Define criteria first; describe resources with them; capture requests against them; schedule; let conflicts and insights tell you how reality is tracking the plan. That ordering is why the setup path looks the way it does.