Orkyo schedules jobs onto the workstations, people, and tools that run them. That's the whole job. Several established software categories sound like that from the outside and aren't, so here is where each boundary sits.
Not an MES or shop-floor control system
Orkyo does not drive machines, collect signals from the floor, dispatch work to terminals, or track operation-by-operation progress. In German terms: it is Produktionsplanung, not Fertigungssteuerung.
Not a CMMS, tool crib, or inventory system
Orkyo does not track stock levels, consumables, spare parts, tool wear, calibration records, or maintenance work orders. If you're looking for machine-shop tool management or inventory management, that's a different product.
Not an ERP or MRP system
No bills of material, purchasing, invoicing, payroll, or accounting. If your planning already happens inside SAP, Oracle, or a DATEV-connected suite, you have committed to ERP-embedded planning and Orkyo is not the tool to bolt on.
Not a floor-plan or CAD drawing tool
Orkyo is not for designing a layout, drafting blueprints, or producing an architectural floor plan. It won't help you lay out a new building.
Not an APS or fine-scheduling optimizer
Orkyo does not sequence operations minute-by-minute on a line or solve for the mathematically optimal order of jobs. Day-granularity planning is a deliberate choice, not a missing feature.
What Orkyo does do
- Schedules jobs onto workstations, people, and tools in one plan
- Surfaces capacity conflicts the moment they're created, not on the floor
- Tracks utilization so you can see which resource is actually the bottleneck
- Plans several sites in one place, with roles controlling who can change what
The feature list covers this in detail, the documentation covers how it's modelled, and machine shop scheduling walks through one concrete case.