Four stages, and nothing hidden in the middle
We sell a solved job, not a licence: what you buy is the state where your cell makes your part. Below is how we get there, what we need from you at each step, and what it costs.
- Milling proven in production
- Current adapter: ABB IRC5
- Two robots at once
- Browser, nothing installed
From the first call to a running cell
The conversation, and a survey of the job
We start with the job, not with software. Which robot — already installed, ordered, or still being chosen. Which part, which process, how many robots share the cell, and what already exists: controller backups, CAD and CAM, fixtures, the machine tool it has to work alongside. Most of this you can answer from memory; the rest we ask for in writing.
- The part and the process, described in your own words
- How many robots the cell has, or will have
- What is already in place — robot, controller, CAM, fixtures
- A straight answer on whether this is a job we should take
- The open questions written down rather than smoothed over
The stage ends when both of us describe the same job in the same words — or we say it is not ours to do.
Feasibility, on your own data
We take your real part and your real toolpath — not a demo file — and run them through the same solver that runs in production: cell model, inverse kinematics, soft axis limits that turn a future controller error into a failure during conversion, collision checking, cycle time with dynamics. You get a result, not a presentation. Batch collision checking samples the path at a stride, so a very brief interference between samples can be missed; we say where that matters for your geometry.
- Part geometry (STEP) and a toolpath — APT, NC, or the CAM job
- A controller backup, if the robot already exists
- Cell dimensions, track length, fixture positions
- How many points solve, and where reach or an axis limit fails
- Collisions found: robot↔robot and robot↔part
- A cycle-time estimate, and the scope and price of the pilot
The stage ends when you hold a written result and a pilot scope — or a documented no. Either one is worth the step.
The pilot
This is the delivery. Cell model built from your controller backups and measurements; TCP and work-object calibration on the real machine; a post-processor that writes programs your controller accepts; an operator window per robot, running in a browser with nothing installed on the shop PC; collision checking; commissioning on the real cell; training for the people who will run it.
- Access to the cell for calibration and commissioning
- One person on your side who owns the result
- The operators, for training on the real cell
- A cell making your part, and the software that got it there
- Programs on your controller, in its own language, readable without us
- Roles, signed tokens and an audit record of every write to the controller
The stage ends when your operator runs the job with us out of the room.
Running it
A yearly subscription per robot: updates, fixes, and someone to call when the cell does something it did not do yesterday. What you have stays readable and stays yours — the program modules on the controller, the cell described in plain JSON, window settings exportable. If you stop paying, the programs on the controller keep running: the subscription buys change, not permission.
- A named contact, and access when something needs looking at
- Updates, fixes and support on the cell you already run
- New parts and new processes quoted as work, not sold as an upgrade
The stage ends when you decide it does: the subscription is renewed yearly by a decision, not by silence.
The limits, before you ask for them
One engineer does the survey, the code and the commissioning. For a shop that size, stating the limits first is not modesty — it is the whole trust argument.
Proven is not the same as possible
Milling is proven in production, on a real cell. Polishing, finishing, coating and large-format printing are the same class of motion and are scoped as work. Machine tending is a different class — points, grippers, I/O handshakes with the machine tool — and we price it as new work, never as “the same thing, only different”.
Two robots at once is proven; more is project work
The architecture is natively multi-robot: a roster in the cell document, an address per robot, and a check that refuses to send a command to the wrong controller. But the neighbour ghost and the proximity guard are pairwise today. Three robots or more means making them all-pairs first — that goes in the quote, not in a promise.
Geometry today is the IRB 6650S
Any other robot model means building its kinematics from the manufacturer’s data and re-verifying the tool centre point on the real machine. That is real work with a real risk of a TCP shift. It is priced, tested and stated — not absorbed quietly.
Nothing that matters depends on the internet
The operator window talks to the cell over your own network, and the application runs stand-alone — no backend, no bridge required. Emergency stop is deliberately outside the token check and outside any cloud link: a stop must never depend on a setting being right or a connection being up.
The simulator is not a safety function
It is an auxiliary engineering tool. It is not a safety function within the meaning of the Machinery Directive and does not replace the cell’s own safety systems, its guarding, or its CE conformity. Every write to the controller is logged before the controller is touched, because who tried matters as much as who succeeded.
What it costs, and what it does not include
€6,000 – €10,000
The whole software side, commissioning and training included.
€1,500 – €3,000 / year
Updates, fixes and support once you are in production.
These are indicative figures, not a price list. Every project is quoted separately, and the number that matters is the one in your quote — it comes after the feasibility stage, when we both know the job.
VAT
All figures above are without VAT. Where Slovenian VAT (DDV) applies it is added at the statutory rate; for a company with a valid VAT number in another EU member state, the reverse charge normally applies. Every quote states the net amount, the VAT and the total, so there is nothing left to work out afterwards.
Not included in the figure
- A post-processor and live driver for a controller we have not written one for yet. Everything above the controller is vendor-neutral; the current production adapter is ABB IRC5 with RAPID. Porting is real engineering, verified on your cell, and is always a separate line in the quote.
- The robot, the spindle, tooling, fixtures, and any mechanical or electrical work in the cell.
- Safety equipment, guarding, and the CE conformity of the cell itself.
- Travel and time on site outside Slovenia, quoted separately.
Contracted and invoiced by Kyrylo Beliaiev s.p., Slovenia · VAT number SI88261042. Company details →
The seat licences you stop buying
Every robot maker sells its own offline-programming suite, licensed per seat and renewed every year — RobotStudio at ABB, and its equivalent at every other brand. On the cell in the case study, nobody opens one to make a part.
That is the line worth comparing, and it is worth being exact about it. You still use the vendor tools for what they are for: controller system administration, controller software updates, backups, safety configuration. What you stop paying for is a seat for every person who programs a part — because the programming happens in a browser window, on any machine on your network, with nothing installed. The other honest alternative is a third-party offline-programming licence plus your own engineer. That is a different purchase, not a cheaper one: there you buy a tool and supply the engineering; here the engineering is the deliverable and the software is what stays behind once the cell runs.
Tell us about the robot and the part
A few specifics get to a useful answer faster than a call. The first reply comes from the person who would do the work, usually within a day or two.
Tell us about the job