An Apogee software update, the German Bionic Connect app and the German Bionic IO dashboard serve different purposes. An update can change how assistance behaves. Connect presents activity information to the wearer and provides a feedback channel. IO supports reporting and fleet management. Keeping these roles separate makes it easier to understand what a connected exoskeleton deployment actually includes.
German Bionic’s January 7, 2025 Apogee ULTRA announcement describes these components together. It also says existing Apogee customers can access the latest enhancements through over-the-air updates. The announcement is useful for understanding the architecture, while the exact update available to a particular device needs its own version and eligibility information.
An assistance update changes behavior during a task
The enhancements named in the announcement include Ultra Mode, smoother transitions between support modes and increased sensitivity to small movements. These concern the behavior of the powered wearable while a person moves. They are different from adding a new chart to an app.
For someone evaluating an update, “new software” is therefore an incomplete description. Ask which assistance behavior changes, which device models and software versions receive it, and which user settings or onboarding material change with it. The announcement supplies feature names but does not provide a firmware-by-model eligibility table or an installation procedure.
Imagine an operator comparing a device before and after an approved update. A sensible comparison would keep the task and device setup consistent and identify the changed assistance mode. A higher activity total on a dashboard would answer another question: how much recorded activity occurred. This is a proposed way to separate observations, not a test performed for this article.
Connect puts activity and wearer feedback together
German Bionic describes Connect metrics including steps taken, weight lifted and usage time. It also describes a channel through which wearers can provide qualitative feedback. Those two forms of information complement each other: a usage record can show when the device was used, while a comment can describe a particular task or transition that the wearer wants reviewed.
Suppose a wearer reports an awkward transition during a recurring handling task. A useful report would identify the device, software version, task and approximate time alongside the comment. Those identifiers would help the deployment team relate the feedback to the right configuration. They are a suggested reporting practice; the announcement does not specify that Connect automatically captures every field.
Activity totals should retain their labels. “Weight lifted” is a recorded metric described by the vendor. It is not the same quantity as the assistance applied at every instant, and it should not be relabeled as a measured reduction in bodily strain. Understanding how a metric is calculated belongs in the dashboard and data-definition discussion.
IO is the fleet view
The announcement places German Bionic IO alongside the wearable and Connect, describing activity monitoring, reporting and fleet management. The practical shift is from one wearer’s interaction to the devices and activity being reviewed across an operation.
| Component | What the announcement describes | Question to ask during deployment |
|---|---|---|
| OTA update | Delivery of assistance enhancements | Which device and version receive which behavior change? |
| Connect | Wearer activity metrics and qualitative feedback | What does each metric mean, and how is feedback reviewed? |
| IO | Activity reporting and fleet management | Which devices, users and time periods appear in each report? |
A fleet report and an individual report may both contain activity data, but their scope needs to be explicit. When comparing periods around an update, identify which devices were updated and when. Otherwise a change in the devices or usage included in the report can be confused with a change in assistance behavior.
Request the update note and the metric definitions together
For an existing Apogee deployment, ask the provider for the applicable update note, device eligibility, rollout instructions and metric definitions. Include who receives wearer feedback and who reviews the fleet view. That produces a clear chain from a named software change to the people using and supporting it.
The robot joint control guide explains lower-level position, velocity and torque terminology. Apogee’s named support modes sit at a different level of description: the announcement describes assistance offered to the wearer, rather than exposing a motor-control interface. Keep the product behavior, the activity record and the fleet report distinct when deciding what to ask the supplier to demonstrate.