Every robot type needs its own site data.
An inspection robot needs to know which gauge is which. An AMR needs zones and docks. A field robot needs boundaries and headlands. Here is what each one depends on.
Pick a robot. See what it needs.
Each page explains how the robot works, how it is set up on a site today and the site data it needs to keep working when the site changes.
Inspection robots
Legged, wheeled and crawler robots that carry cameras and sensors on inspection rounds.
Site data it depends on- Asset tags placed in 3D
- Viewpoints for each check
- Hazardous zones and temporary changes
Autonomous mobile robots
AMRs that move goods and materials around warehouses, factories and hospitals without tracks in the floor.
Site data it depends on- A current base map
- Zones with their reasons
- Positions, docks and clearances
Agricultural robots
Autonomous tractors, weeding robots and greenhouse robots working fields and crops.
Site data it depends on- Field boundaries and headlands
- Obstacles and no-go areas
- Crop rows and how they change
The site data is shared. The robots are not.
When a site runs robots from more than one maker, each maker's software keeps its own picture of the site. Kaiinos keeps one current model of the site, so the layout, the assets, the zones and the changes are recorded once.
Tell us which robots. We'll map the site they share.
One site, one robot, one round or route to start with.
Start a pilothello@kaiinos.ai