Path A: selling a robot for valuation
1. Submission and identification
You provide photos, the model, a description of the condition and the location. If you do not know all the parameters, the engineer uses the nameplates and the photos to indicate the missing information.
2. Technical assessment
We check the available data on the manipulator, the controller, completeness and equipment. If needed, we ask for additional photos, documents or an explanation of the service history.
3. Presentation of the terms
With complete data it is possible to discuss the terms appropriate to the submission. The form itself does not decide the transaction model, the way of settling or the organisation of collection.
4. Organisational arrangements
The documents, the scope of preparing the unit, the logistics and the schedule require the acceptance of the parties. With a complex cell, the boundaries of the work and the responsibilities must also be described.
Go to the robot valuation form
Path B: purchase and deployment
1. Description of the task
The conversation starts from the process, not from a specific robot model. We discuss the part, the current work, the machine, the cycle time, the most common problems and the expected result.
Useful materials: photos, a short recording of the cycle, part drawings, information about variants, machine data and examples of defects in quality control.
2. Assessment of feasibility and gaps
The engineer assesses whether the key operations can be performed repeatably. We check the grip points, feeding, access, feature visibility, variation and safety requirements.
At this stage there are three possible conclusions:
- the scope is suitable for further design;
- the data must be extended or the process organised;
- the chosen direction is not recommended.
3. Concept and scope
If the grounds are confirmed, we compare solution variants. We define the elements of mechanics, robot, vision, integration and error handling. We also define what the scope does not cover.
| Project decision | What should be clear |
|---|---|
| Mechanics | How the part is fed, gripped, clamped and collected |
| Robot and tooling | What requirements arise from the cycle and the environment |
| Vision or AI | What data we record and what decision we make |
| Integration | Which signals and interfaces are actually available |
| Safety | Which hazards and rules of work must be taken into account |
| Acceptance | Which samples, conditions and results will be assessed |
4. Tests before commissioning
The scope of testing depends on the project. It should cover typical conditions and the agreed borderline cases. In machine tending this may be a missing part or bad positioning, and in quality control a new defect variant or an ambiguous result.
We do not automatically transfer the result from one sample to the whole process. The conclusions concern the tested range of data and conditions.
5. Schedule and delivery
Only with the scope, access to the cell and the way of acceptance known do we set the schedule and the terms of work. Changes in the process or input data may require a new assessment.
A common principle: we do not hide the limits
A robot will not by itself improve an unstable part, and an AI model will not fix unclear quality criteria. If the feeding, the marking of samples or the organisation of work must be changed before deployment, we point this out before the scope is set.