Back to News
ProductAI Understanding briefing

Gix’s deliverz.ai platform adds Ottonomy robot to hybrid fleet at Sheba Medical Center

Gix Internet Ltd. announced that its Ottonomy autonomous delivery robot is now operating alongside existing robots at Israel’s Sheba Medical Center, managed through the company’s AI‑powered deliverz.ai orchestration layer.

4 min readRead the linked source
Source-page capture accompanying Gix’s deliverz.ai platform adds Ottonomy robot to hybrid fleet at Sheba Medical Center

What happened

Gix Internet Ltd. (Nasdaq: GIXI) reported that its Ottonomy autonomous delivery robot has entered operational service at Sheba Medical Center, Israel’s largest hospital and a top‑10 global facility. The robot joins the hospital’s existing fleet and is coordinated through deliverz.ai, Gix’s AI‑driven, robot‑agnostic orchestration platform. The platform provides a single SaaS/RaaS layer that assigns logistics missions, monitors robot status, and integrates human transport teams, allowing the hospital to manage multiple robot manufacturers from one control system. Gix says the deployment demonstrates real‑time, multi‑vendor coordination in a live clinical environment and is part of a broader rollout that includes chemotherapy medication, blood, and bone‑marrow transport.

The press release, dated November 17, 2026, states that the Ottonomy robot is now active at Sheba Medical Center and operates under deliverz.ai’s unified operational layer. The platform assigns delivery missions based on priority, location, and resource availability, and it coordinates both robots and human couriers in real time.

Deliverz.ai’s architecture is described as robot‑agnostic, meaning it does not rely on vendor‑specific fleet‑management software. Instead, the system provides a single interface for mission planning, monitoring, and oversight across heterogeneous hardware.

Gix positions the deployment as a proof‑of‑concept for broader commercial use. The company notes that the platform is offered via Software as a Service (SaaS) and Robotics as a Service (RaaS) models and is being introduced to U.S. healthcare organizations.

Quotes from Sheba’s Head of Innovation, Michal Kaplansky, and Gix CEO Amir Nardimon emphasize the strategic goal of freeing hospitals from dependence on a single robot supplier and creating a scalable, unified logistics workforce.

Source details: manilatimes.net

Why it matters

The deployment marks a concrete step toward robot‑agnostic logistics in complex, high‑traffic facilities like hospitals. By abstracting control away from any single hardware vendor, deliverz.ai could reduce reliance on proprietary fleet‑management systems, lower integration costs, and enable hospitals to select the most suitable robot for each task. If the model scales, it may accelerate adoption of autonomous mobile robots across healthcare, improving throughput, cutting labor expenses, and freeing staff to focus on patient care. The approach also showcases a practical use case for “Physical AI” – the combination of AI software with autonomous hardware – and could influence how other large institutions (e.g., universities, airports) design their internal logistics. However, the rollout remains limited to one site; broader adoption will depend on technical compatibility, regulatory approvals, and demonstrated cost‑benefit outcomes.

Robot‑agnostic orchestration could lower barriers to entry for new robot manufacturers, fostering competition and innovation in the autonomous logistics market.

Hospitals face intense pressure to improve operational efficiency while controlling costs; a unified AI layer that optimizes routing and resource allocation may deliver measurable savings and faster delivery of critical supplies.

The deployment serves as a real‑world validation of Gix’s claim that “Physical AI creates real value only when robots, people and workflows are orchestrated as one system,” potentially influencing procurement strategies in other high‑density facilities.

Regulatory scrutiny of autonomous systems in clinical settings remains a hurdle; successful operation at a top‑ranked hospital could help shape industry standards and safety guidelines.

Interactive Mechanism

Interactive Mechanism: How It Actually Works

Explore the underlying technology behind this development interactively.

Agent Lifecycle Stage:
1
User Intent & Planning: "Audit customer refund request #4092 and settle payment."
2
Tool Calling: Emits structured JSON call crm_get_transaction(id='4092').
3
Guardrail & Verification:Paused: High-value action requires human operator sign-off.
4
Final Settlement: Refund recorded, email receipt dispatched, and audit log stored.
Core takeaway: An AI agent is not just a language model—it is a closed loop of planning, tool invocation, and environment feedback. Production systems require self-healing retries and strict human approval guardrails.
Interactive Concept Check+10 Points
AI Models Explained Quiz

Which component of an AI application is the machine-learning model itself?

What to watch next

Key indicators to monitor include: (1) additional hospital deployments of deliverz.ai, especially in the United States where Gix is targeting new customers; (2) performance data on mission completion times, error rates, and cost savings compared with traditional human‑only logistics; (3) integration challenges with other robot brands and any required hardware or software modifications; and (4) regulatory or safety reviews specific to autonomous robots operating in patient‑care environments.

Expansion of deliverz.ai to additional hospitals, particularly in the United States, will test the platform’s scalability and cross‑regional compliance.

Quantitative performance metrics (e.g., delivery speed, error reduction, labor cost impact) released by Gix or Sheba will indicate whether the technology delivers on its promised efficiencies.

Compatibility with other robot brands beyond Ottonomy will be critical; any integration challenges could limit the platform’s robot‑agnostic promise.

Regulatory developments concerning autonomous robots in healthcare, such as FDA guidance or local health‑authority approvals, could affect rollout speed.

Related guides & quizzes

Found this useful?