uGo+ Platform Documentation¶
One platform. uGo+ brings together what a hospital or laboratory actually needs to run a process end to end: moving something through a building, getting through doors and lifts, handling samples, talking to the laboratory's own systems, and speaking with the people in the corridor.
A customer buys one technology from United Robotics Group and reaches it through one software. This site is organised the same way — by what the platform can do, not by which team built which part.
Read this first
Parts of this platform are integrated today and parts are still separate systems of ours. Integration Status says which is which, per capability, in one table. The target picture is shown here; it is never presented as already reached.
What do you need?¶
-
Transport and Delivery
Move a tray, a compartment or a rack through the building. Chassis of the uLog and uServe ranges, the uGo operator interface, the kiosk.
-
Laboratory Automation
Sample handling and the laboratory's own systems. uLab cobots, the LIS connection, device couplings.
-
Human Interaction
Speaking with people and being spoken to. The uMe humanoid, voice, language models and the persona.
-
Building Access
Doors, lifts and the hardware that operates them. Door control, the level-change orchestrator, the u-IoT module.
Or start from a question¶
| I want to… | Start here |
|---|---|
| Understand what uGo+ actually is | What uGo+ is |
| Know what is integrated today and what is not | Integration Status |
| Talk to a transport robot's chassis | AXBot REST API |
| Connect a laboratory information system | Laboratory Systems (LIS) |
| Move a robot between floors | Lifts |
| Open a door from a robot | Doors |
| Drive a humanoid from my own code | Humanoid (uMe) |
| Find every machine-readable contract we publish | Interface Index |
| Add or correct a page | Contributing |
A note on what you will and will not find here¶
This site publishes protocols and contracts, not customer installations. You will find the LIS message structure; you will not find the field layout of a particular laboratory. You will find the requirement that the u-IoT module belongs in a protected network segment; you will not find a list of what can be reached if it is not.
Everyone at URG can contribute¶
This documentation lives in GitLab and every colleague can open a merge request against it. If a page is wrong, incomplete or missing, the fastest fix is to change it — not to write to someone about it.
The pages are plain Markdown; the pipeline builds and publishes them. mkdocs build --strict
runs on every branch, so a broken link fails the build instead of quietly reaching a reader.
Please read Contributing first. It is one page, and it exists because this site is read beyond the people who write it.