What uGo+ is¶
uGo+ is the platform. Everything else in this documentation is a capability within it — transport, laboratory automation, human interaction, building access, and the connection to a laboratory information system.
That is a deliberate statement, and it is the reason this site is organised the way it is. A customer buys one technology from United Robotics Group and expects to reach all of it through one software. Nobody wants to learn six systems because the vendor happens to have six teams. A documentation site that lists six products side by side contradicts that claim in its navigation before the first sentence is read.
What that means in practice¶
A hospital or laboratory that works with us does not operate "a transport robot and a door controller and a lift connector and a laboratory interface". It operates one process: a sample is collected, it travels, a door opens, a lift is called, the sample arrives, the laboratory system is told. Every one of those steps is a capability of the same platform, and the interesting engineering lives at the joins between them.
So the structure here follows the capabilities, and each capability page ends where the next one begins.
| Capability | What it covers | The components involved |
|---|---|---|
| Transport and Delivery | moving something from A to B inside a building | uLog and uServe chassis, the uGo operator interface, the kiosk |
| Laboratory Automation | sample handling and the laboratory's own systems | uLab cobots, LIS connection, device couplings |
| Human Interaction | speaking with people, and being spoken to | uMe humanoid, voice, language models, personas |
| Building Access | getting through the building | doors, lifts, the u-IoT module, call buttons |
What this page will not do¶
It will not claim an integration that does not exist yet. The platform is the direction we are building in, and parts of it are genuinely there today while others are still separate systems that happen to be ours.
Presenting the target picture as the current state would be the easiest way to lose the trust of exactly the partners this site is written for. So every capability page states plainly whether it is reachable through the platform today or still runs standalone, and Integration Status collects that in one table.
The honest version is also the more useful one: it turns the gaps into a roadmap instead of hiding them.