For surgical robotics training teams, simulation companies & clinical educators

What does it take to turn a device spec and a curriculum into a trainer built on your own instruments?

Send the device specs and the training requirements. Ziva builds the procedure on your instruments, energy devices, and console behavior, with the safety checks your curriculum requires and rules that keep a trainee from skipping one. When an instrument, a software release, or a protocol changes, the change lands in the same trainer instead of a rebuild.

Review your trainer

See the clip tool stay locked until the safety check passes.

This Unreal Engine example walks a trainee through retracting the gallbladder, dissecting to the critical view of safety, then clipping and dividing, with per-tissue force limits, bipolar coagulation, a safety fence around the bile duct, and ICG fluorescence. The force values are illustrative. In a real trainer, tissue parameters, force limits, and pass criteria come from your clinical and engineering teams, who approve them.

Start from whatever you already have

Most projects start from one or two of these. None of them is required. Send what you have and the review identifies what is missing.

  • The device specs: instruments, energy devices, and console behavior.
  • The training requirements: procedure steps, the safety checks a trainee must pass, and what each attempt should record.
  • The hardware trainees use: console, hand controllers, or headset.

What you get back

  • An editable trainer in your engine, built on your instruments, energy devices, and console behavior.
  • Procedure steps with the safety checks your curriculum requires, and rules that stop a trainee from skipping one.
  • A record of each attempt, such as forces, errors, and time, against pass criteria your clinical team sets.

Ziva for Godot 4.2 and later is available to download today. Unity is in beta. Unreal Engine and Isaac Sim begin with a scoped enterprise pilot.

How the work is priced

Enterprise pricing is custom to your organization, engine, and use case. There is no public price list. Send what you have through the project inquiry and the quote follows that review. Support and commercial terms are written into the engagement.

Questions to resolve before production.

Does the trainer validate skills or certify surgeons?
No. Ziva builds the training software. Tissue parameters, force limits, and pass criteria come from your clinical and engineering teams, who approve them. Validation studies, credentialing, and any regulatory clearance stay with you.
Will it run on our console, hand controllers, or headset?
That is scoped at the review. Bring the hardware trainees use; what is delivered and checked on it before handoff is written into the scope.
Who owns the project after handoff?
You do. You retain all rights to the code and content you create using Ziva, the project is handed over as editable source in your engine, and Ziva never uses your code to train AI models. Read the terms of service.