Integration Status¶
One table, kept honest. It answers a single question per capability: can you reach this through the platform today, or is it still a system of its own?
This page exists because the rest of this site describes uGo+ as one platform, which is what we are building and what a customer should experience. Some of it is true today and some of it is not yet, and a reader who cannot tell the two apart cannot plan.
Status as of 12.09.2026, evening.
| Capability | Through the platform today? | What is actually there |
|---|---|---|
| Transport — chassis movement | Partly | The operator interface drives the chassis directly over its REST interface. That works without any cloud service, which is the point — but it is a direct coupling, not a platform call. Consolidating every movement command onto a single writer is in progress; see Safety. |
| Transport — operator interface | Standalone | Runs on the tablet at the robot. Six languages, capability-driven task tiles. It does not yet obtain its jobs from the platform. Described screen by screen in the Operating Manual. |
| Transport — fleet | Partly | Robots arbitrate destinations, chargers and narrow passages among themselves over a signed local heartbeat, without any server. A package exists that puts a non-URG on-board computer into the same fleet. Measured between processes on one host; not yet measured between two separated devices in a building. See Fleet. |
| Transport — handover station | Pilot | Two devices share one place: one waits, the other works and then releases. Seven steps, five states, and a tour stop that waits for the partner and moves on by itself; two stations in one tour. Built and running in the test set-up. Pilot in September 2026, not a series state. |
| Transport — kiosk shell | Yes, as a device application | Version 1.0.3 (frozen 10.09.2026). Full kiosk with Device Owner on a fresh board, reduced kiosk over the home screen otherwise. Configuration file, service code as a hash only. See Kiosk mode of the tablet. |
| Building access — doors | Yes, as a service | Door control runs and decides from map geometry when a door opens. Doors are held per map and nothing is actuated until the current map is known. Service description uGate Door Control 1.0 in six languages since 12.09.2026; the door chapters of the building interface description are on Building integration 1.1 § 9. |
| Building access — lifts | Yes, as a service | The level-change orchestrator runs the whole chain: waiting position, ride request, map switch, relocalisation, continue. In production since 04.08.2026. Service description uGo Elevator Integration 1.0 in six languages since 12.09.2026; interface description 1.1 of 12.09.2026 with the port rule of 11.09., now readable in full on Building integration 1.1. A requirements document for an elevator interface partner (1.0, EN, 11.09.2026) is out for mark-up: Elevator interface — requirements. Two field cases in early September — an accepted request discarded at the floor, and one expired by a 30 s timeout with the robot in the cabin — are unresolved at interface level; the interim arrangement is 120 s timeouts. See Integrations. |
| Building access — u-IoT | Yes, as a device service | REST interface with digital I/O, four operating roles, an action engine and a call-me queue. Its interface description is still outstanding, so our own proxy passes the raw response through rather than interpreting it. Data sheet and user manual 1.0 now in six languages. |
| Building access — pneumatic tube | Planned | There is a requirements specification 0.1, draft of 12.09.2026 in six languages, with two expansion stages: stage 1 hands over by staff and needs no connection to the tube system at all; stage 2 would exchange arrival, occupancy and release with the system's control computer. Nothing is built. Our own two gaps (a service key sent by the module firmware, a state query for machines without a browser session) are open, the assumptions stage 2 rests on are unconfirmed, and there is no target installation. An internal note of 20.08.2026 states that a connection exists and is in operation; the market review of 10.09.2026 finds no evidence for one. That contradiction is unresolved — until it is, treat the pneumatic tube as planned. The full specification — requirements A1–A30, tests T01–T30, ten open decisions — is on Pneumatic tube — requirements 0.1. See also Integrations. |
| Laboratory — LIS connection | Yes, per site | CLSI LIS 1-A and LIS 2-A over TCP/IP, implemented per laboratory. Not yet one shared implementation — that is where consolidation would pay off most, and it has no date. Service description uGo+ LIS Integration 1.0 in six languages since 12.09.2026; the message protocol page on this portal is still planned. |
| Laboratory — cobots | Partly | Device couplings exist over gRPC. The core contract exists as several diverging copies rather than one source. Products are documented: uLab Duo (manual 1.1, data sheet 1.0), uLab Mobile (manual 1.0, data sheet 1.2). |
| Laboratory — connected analysers | Yes, per device | Classified in two levels from data sheet 1.2: Robotics Proven where a coupling is demonstrated in service, Robotics Ready where the interface is prepared and proof at a customer is still open. See Connected analysers. |
| Human interaction — humanoid | Standalone | uMe speaks through its own gateway on the robot. A first platform building block, not yet a platform capability. The SDK documentation is one page again since 12.09.2026 — see uMe — Humanoid and uMe SDK. |
| Human interaction — voice and language models | Early | The service, the proxy and the browser side of the seam exist and are measured. The shell side of the seam does not, so the tile stays hidden. See Voice. |
| Operations — remote support | Partly | The read-only second socket is built and measured (27.08.2026). The tunnel itself has not yet run against a device in a building. See Remote Support. |
| Operations — cloud enrolment, telemetry, updates | Yes | Certificate per device, topic tree per device, four-stage rollout with automatic rollback. No driving command from the cloud, by construction. |
| Operations — uSuite console | Yes, growing | The operator console at https://usuite.unitedrobotics.group. Since 14./15.09.2026: device master data, product series with type records and superseded editions, decommissioning in two paths, certificate-expiry cases, version distribution, preselection before release, per-version change lists, silent session renewal. Data in Europe, Frankfurt data centre. Enrolment by one-time join code; the device generates its own key. What the cloud deliberately cannot do — drive, record a map, set the pose, raise driving values — is unchanged, see URG cloud (uSuite); the new functions are on uSuite console and administration. |
| Operations — uSuite next stages | Planned | Simulation and digital twin, skill marketplace, online training, one sign-in for everything. None of these is built and none has a date. They are listed so that nobody mistakes them for present. |
How to read this¶
Standalone does not mean unfinished. The uMe gateway is a working, documented interface — it simply is not reachable through uGo+ yet. A partner can build against it today; they just should not assume that a uGo+ credential opens it.
Pilot means it is built and running, but at one place and under observation. It is not a series state, and it is not something to plan an installation around yet.
Planned means exactly that and nothing more: no build, no date, no commitment. A released document about a capability does not change its row: the pneumatic tube has six language versions of a requirements specification and is still Planned, because a specification is not an implementation.
Partly means the capability works but the seam is a direct coupling rather than a platform call. Those are the places where bringing things together actually pays off, and they are where this platform gets built next.
Why this page is worth the discomfort¶
It would be easy to leave it out. Every entry that says Standalone is an admission.
But the alternative is worse. A partner who builds against a platform promise and then discovers a direct coupling underneath does not conclude that the documentation was optimistic — they conclude that they cannot rely on anything else on this site either. One honest table protects every other page here.