What Orkyo Is Not – Scope & Fit

Orkyo schedules jobs onto the machines, 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.

Orkyo decides what runs where and when, at day granularity, and shows the conflicts. Execution stays with your floor.

Not a CMMS, tool crib, or inventory system

Orkyo does not track stock levels, consumables, spare parts, tool wear, or maintenance work orders. You can keep a maintenance or calibration log on a machine as a list of entries — Orkyo will hold that record, but it will not raise the work order, order the part, or tell you when the next service is due. If you're looking for machine-shop tool management or inventory management, that's a different product.

Orkyo schedules time on your machines, equipment and tools — booking the fixture a job needs for the days it needs it — rather than counting what you own.

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.

Orkyo is built for teams too small for an ERP and too big for the spreadsheet — typically 10 to 250 people.

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. The shapes you draw are there to be booked, not to be dimensioned.

Orkyo takes the layout you already have and makes what stands on it bookable. Draw a shape for a machine, or hand the shape to a machine you already registered.

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. It does record the order you already know: a task can wait for the ones before it, and the plan respects that at day granularity. What it will not do is search for the optimal sequence on your behalf. Day-granularity planning is a deliberate choice, not a missing feature.

Orkyo keeps the plan something a person can hold in their head and change in seconds, which is what a spreadsheet got right.

What Orkyo does do

Schedules jobs onto machines, 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.

Not sure which side of the line you're on? Take the two-minute fit check — about ten questions, a plain answer. Or tell us what you're planning today and we'll say it in person: get in touch. A fast "no" is worth more to both of us than a slow trial.