Nothing is built in any more

Your workspace decides what it schedules. Resource types come from a catalog you switch on, the floorplan holds every machine, and the reference data your shop keeps is yours to shape.

Published

Orkyo used to ship three resource types — Spaces, People and Tools — and everything else was something you added beside them. That model decided what a workspace was allowed to be good at. A machine shop had to call a mill a Space and work around the word.

This release removes the built-in set. Nothing is privileged, and the kinds of resource your workspace schedules are the ones you choose.

Your types come from a catalog

Configuration → Type catalog holds pre-configured types: mills, lathes, drills, CNC machines, assembly and test stations, workstations, people, tools and forklifts. Switch one on and it arrives with the fields that kind usually carries.

  • An activated type is an ordinary type. No built-in badge, no locked fields. Rename it, re-icon it, change what it can do, or remove it.
  • Hiding is not deleting. A type in use asks which you mean. Hiding keeps every resource and can be undone; deleting removes the type with its resources, their assignments and booking history, its groups, and its request targets, behind a second confirmation naming what goes.
  • Nothing is activated for you. A new workspace schedules nothing until you say what it runs, and the product says so where it matters instead of failing quietly.

Documentation: Type catalog

Stations and Assets replace the per-type pages

The sidebar has two resource entries now, and they do not grow when you add a type.

  • Stations — “Resources with a fixed location, placeable on a floorplan”. Machines, cells, benches.
  • Assets — “Mobile resources, planned by availability”. People, tools, vehicles.

A type picker at the top of each page chooses which type you look at. The Utilization board follows the same shape: three tabs, with a type filter on the two resource tabs.

Documentation: Stations and Assets

The floorplan belongs to the site

The plan is no longer a tab about one type. It holds every station type at once, and a circle tool joins the rectangle and polygon.

Finishing a shape now asks what it is for. A machine you registered by import, or from its own list, can take the shape and keep everything it already carries — you no longer have to draw a second copy and delete the first. Where nothing is waiting to be placed, the shape goes straight to the create form as before.

Click selects a shape, drag moves it, and a handle resizes it. A click that does not travel no longer nudges the machine it selected.

Documentation: The floorplan

Lists, and the department tree

The reference data a shop keeps beside the schedule is now one mechanism. A list definition sets typed columns — text, number, yes/no, date, link, choice, or a reference to another row of the same list — and any resource type can carry a list of that shape. A maintenance log per machine is the common case.

Departments and job titles moved to a new Organization page, built on the same mechanism.

  • The department tree is back. Parent is a picker, not a typed-in name: the department you point at has to exist, and a department cannot end up its own ancestor. Orkyo refuses a loop when you save it.
  • Job title and department are lookups on a person, resolving to rows you maintain in one place. Rename a job title once and everyone who holds it follows.

Documentation: List definitions and Organization

Fields on your resources

A resource type carries its own fields: text, number, yes/no, date, link, a choice from options you define, or a lookup into a shared list. A mill records a spindle speed and a tool changer count while a bench records neither.

Criteria still exist and still do their own job. A field records what a resource is; a criterion is the vocabulary scheduling matches on.

Documentation: Resource types

Import and export

Your list definitions, their columns, and the rows of every shared list travel in the workspace export. A department tree exports with its references intact.

Exports are also complete. Where a large workspace previously received the first thousand records with nothing to say so, it now receives all of them.

Documentation: Import and export

Availability by plan

The quota that counted Spaces now counts Stations — resources with a fixed location, across all sites. The numbers are unchanged. Types you define yourself, lists and custom fields carry no plan restriction on either edition.

Upgrade notes

Workspace databases migrate automatically at deploy. The set is large: it adds the lists tables, moves departments and job titles into them, converts the department parent from a name to a reference, retires the built-in resource types, and drops three tables that never got an implementation.

Two of those steps remove tables. Orkyo Community operators cannot roll a deployment back past this release once it has run — move forward instead. Take a backup before deploying, as usual.

Since 0.14

Also in this period: tenant-defined custom fields on resource types arrived as the groundwork this release builds on; the requests importer was repaired and reads the capacity-planning template; spreadsheet import dropped its dependency and reads .xlsx directly; public forms gained challenge verification; and the documentation adopted ASD-STE100 Simplified Technical English as its language standard.